Monday, 2017-03-27

*** jesusaur has quit IRC00:26
*** jesusaur has joined #zuul00:30
*** jesusaur has quit IRC00:31
*** jamielennox is now known as jamielennox|away01:01
*** jesusaur has joined #zuul01:15
*** jamielennox|away is now known as jamielennox01:19
*** jesusaur has quit IRC01:34
*** jesusaur has joined #zuul01:40
*** tflink has quit IRC03:21
*** tflink has joined #zuul03:55
*** jamielennox is now known as jamielennox|away04:14
*** jamielennox|away is now known as jamielennox04:22
*** tflink has quit IRC04:28
*** tflink has joined #zuul04:57
*** bhavik1 has joined #zuul05:33
*** bhavik1 has quit IRC05:36
*** isaacb has joined #zuul06:43
*** hashar has joined #zuul06:46
*** bhavik1 has joined #zuul06:49
*** bhavik1 has quit IRC06:53
*** rcarrillocruz has joined #zuul07:45
*** openstackgerrit has quit IRC08:33
*** rcarrillocruz has quit IRC09:57
*** openstackgerrit has joined #zuul11:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Silence command warnings  https://review.openstack.org/44874811:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Replace ssh-keyscan with host keys from node  https://review.openstack.org/44678511:43
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add entry for ref-replication-scheduled event  https://review.openstack.org/44625111:43
*** isaacb_ has joined #zuul12:01
*** isaacb has quit IRC12:04
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Add a test for multiple provider pools  https://review.openstack.org/45018312:07
Shrewsjeblair: I took the liberty of creating a multi-pool test ^^^^ (mainly b/c I felt bad about asking for it), but it does point out an issue where you aren't setting the 'pool' attribute on new nodes.12:08
*** isaacb_ has quit IRC12:33
*** isaacb_ has joined #zuul12:35
rbergeronshrews: i am in the office today and tomorrow if you are bored and want to get in a car and say hello at some point :)14:35
Shrewsrbergeron: neat! today is probably no good, especially with the late zuul meeting time. tomorrow maybe?14:36
rbergeronshrews: suuuuure, maybe in morningish + meeting + lunchtime? I get to sit in meetings tomorrow afternoon about open sourcing that one thing :)14:40
rbergeroni fly out at 6 or 7pm or something14:40
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Add debian-jessie DIB for dsvm testing  https://review.openstack.org/44993815:01
jeblairShrews: oh cool.  i would have happily written one, but thanks!  i'll go fix up the patch now.15:14
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove SSH support from nodepool  https://review.openstack.org/44668315:22
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove keypair from provider section  https://review.openstack.org/44767315:31
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove legacy openstack settings from nodepool.yaml  https://review.openstack.org/44764715:31
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update nodepool config syntax  https://review.openstack.org/44881415:31
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update nodepool config syntax  https://review.openstack.org/44881415:32
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Add a test for multiple provider pools  https://review.openstack.org/45018315:33
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove api-timeout and provider.image-type  https://review.openstack.org/44934215:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970515:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935415:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update docs for configuration syntax change  https://review.openstack.org/44933915:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973715:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978115:34
jeblairmordred: did you start on the shade get az list thing?15:35
mordredjeblair: no! I knew there was a thing I was suppposed to be doing in shade - I will do that as soon as I finish the patch I'm working on now15:41
jeblairmordred: cool, thx15:41
*** isaacb_ has quit IRC15:43
*** hashar is now known as hasharAway15:57
*** tobiash has joined #zuul16:02
*** tobiash has quit IRC16:02
*** MapspaM is now known as SpamapS16:08
*** hashar has joined #zuul16:10
*** cinerama has joined #zuul16:12
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Refactor nodepool apps into base app  https://review.openstack.org/44839516:21
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Add check for valid zk attribute before disconnect  https://review.openstack.org/44911016:22
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Do not require secure file for nodepoold  https://review.openstack.org/44911816:23
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Docs: Remove "jenkins" reference  https://review.openstack.org/44912916:23
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Docs: Clarify secure file usage  https://review.openstack.org/44913016:23
jeblairharlowja: i responded to your question on https://github.com/python-zk/kazoo/pull/41916:28
jeblairharlowja: i also pushed up a new commit with an improvement (detailed in my response)16:28
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove api-timeout and provider.image-type  https://review.openstack.org/44934216:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970516:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935416:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update docs for configuration syntax change  https://review.openstack.org/44933916:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update nodepool config syntax  https://review.openstack.org/44881416:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973716:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978116:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Add a test for multiple provider pools  https://review.openstack.org/45018316:34
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Add a test for multiple provider pools  https://review.openstack.org/45018316:37
SpamapSwhoa16:37
SpamapSgo jim go16:37
jeblairmostly rebases and minor fixes; it's a big stack :/16:38
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove api-timeout and provider.image-type  https://review.openstack.org/44934216:39
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970516:39
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935416:39
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update docs for configuration syntax change  https://review.openstack.org/44933916:39
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973716:39
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978116:39
*** hashar has quit IRC16:54
jeblairmordred: http://git.openstack.org/cgit/openstack-infra/nodepool/tree/nodepool/nodepool.py#n132516:55
jeblairmordred: essentially, if the user doesn't specify a list of azs, instead of setting None there to let nova decide, we want to pick one from the full list16:57
jeblairmordred: (i know that doesn't sound like much of a difference, but if we choose the az instead of nova, it means we know the az early enough to request the same az for the rest of the nodes which are launched)16:58
jeblairmordred: (if we wait for nova to choose, it's too late for us to pick the same az for the other nodes)16:58
mordredjeblair: ++16:58
jeblairmordred, Shrews: my guess is we want to put something on the providermanager to cache that (like flavors, networks, etc)17:00
mordredjeblair: hrm. I guess so17:06
mordredI'm sad we're not consuming shade caching yet, as we _also_ have caching for it there - but such is life :)17:06
openstackgerritMonty Taylor proposed openstack-infra/nodepool feature/zuulv3: Fetch list of AZs from nova if it's not configured  https://review.openstack.org/45034517:12
SpamapSis there some big reason we aren't just using shade's caching?17:12
mordredjeblair: that won't pass tests right now, because I bumped the requirement for shade in the patch17:12
mordredSpamapS: we haven't dug in to it recently - last time we tried there was an issue, and it hasn't come back around to figuring out what was up with that17:13
mordredSpamapS: other things have been at the top of the list17:14
mordred:)17:14
SpamapSsomanythings17:16
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935417:18
*** harlowja has quit IRC17:18
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970517:19
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973717:19
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978117:19
jeblairmordred: jhesketh had a question on https://review.openstack.org/44875017:20
Shrewsmordred: thanks for that AZ patch17:23
*** harlowja has joined #zuul17:24
mordredjeblair: that's a good question. I believe the answer is "no"17:25
mordredalthough if we decided that was important, we could likely write in a special case to our callback plugins17:25
SpamapSjeblair: After seeing pabelanger's comments on the security spec about nodepool-builder, I had a thought. What if we just do this bubblewrap work in nodepool as "container enablement" ?17:26
jeblairmordred: yeah, i think i'm okay with the "let's see what the errors look like" approach.17:26
SpamapSWe still end up with 'ansible running ansible', but I wonder if it's a shorter path since we git rid of the duplication efforts around managing images and contexts.17:27
mordredSpamapS: I don't fully understand what you mean by "container enablement"17:27
jeblairSpamapS: you mean your earlier suggestion of having zuul request a container from nodepool from which to run ansible?17:27
SpamapSjeblair: Right, instead of requesting a VM based node, Zuul would request a container.17:28
SpamapSAnd then do the Ansible execution there.17:28
SpamapSSo we don't get the added cost of extra vms for every concurrent job.17:28
jeblairSpamapS: yeah, i think that's a good idea that we should look into in the future, but i think that adding container support to nodepool is a major endeavor.  i'd guess add 1-2 months onto our effort.  i think bubblewrap on the launcher is a much shorter path.17:29
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Create zuul.executor.hostname ansible variable  https://review.openstack.org/44882017:29
SpamapSjeblair: I hope you're right. I don't have a good estimate on how long the work will take, but I do believe it's not something to continue investing in once in place.17:32
Shrewsjeblair: i had a -1 on 449339. not sure if you missed the comments in the rebase bomb17:35
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove legacy openstack settings from nodepool.yaml  https://review.openstack.org/44764717:35
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove keypair from provider section  https://review.openstack.org/44767317:35
jeblairSpamapS: well, investment as far as features go -- sure -- it's not really a feature of the system, it should really be as invisible as possible to operators and users.  investment in maintenance?  i think we will need to keep it working for some time, possibly indefinitely.  growing an explicit dependency on a container technology in nodepool is a big change.  we've agreed having it as an option in nodepool would be good.  but requiring it ...17:37
jeblair... would place a larger burden on operators.17:37
jeblairShrews: thanks17:38
SpamapSjeblair: Investment in features is definitely what I mean. :)17:39
SpamapSThese things tend to grow legs.17:39
pabelangerlook at all the new merges :)17:39
jeblairSpamapS: then yeah, i agree this is basically an "implementation detail" as far as that goes.  :)17:39
pabelangerneed to catch up and see where we are17:39
SpamapSLike if we initially run w/o a MAC.. and we're comfortable with the security implications of that, we probably just need to live with that until we get container support in nodepool.17:39
SpamapS(hypothetical.. Rob Clark suggests we'll want a MAC)17:40
* clarkb wonders why zuul security eg MAC is related to nodepool supporting containers (whcih it does today via nova flavor choice fwiw))17:40
SpamapSclarkb: that's assuming nova has a container flavor. ;)17:40
SpamapSsome do I'm sure17:41
SpamapSclarkb: perhaps read the spec? there's a vibrant discussion in patchset 8 (I'll be pushing #9 shortly) 44449517:41
SpamapSwe're all wrestling with our overactive engineer desire to practice DRY while also needing to get things done. :)17:42
SpamapSor at least.. I am. :)17:44
clarkbI think the trap to avoid here is conflating orthogonal needs/features even if there is some overlap because doing so greatly increases the time to getting anything working (just look at how long it took us to get off of snapshot images)17:44
pabelangerThe big thing for me, was having nb01 / nb02 build the container. So we didn't have to install and manage disk-image-builder on zuul-executor systems17:46
SpamapSIf we can spin up cheap throw-away containers for running untrusted playbooks, it negates the need for the executor security enhancements.17:46
SpamapSAnd assuming people start using Zuul v3, they're all going to want containers. :)17:47
clarkbSpamapS: but only if you run them in non shared kernels that are also throwaway right? (eg just run a VM?)17:47
SpamapSs/people/more people/17:47
Shrewspabelanger: yeah, lots of merging (and conflicting). which worries me because nodepool-launcher has been running like a champ the last few days  :)17:47
pabelangerShrews: :) I'm cleaning up our nodepoolv3.yaml file right now17:47
SpamapSclarkb: They still have to be secured regardless of where they run. But that security work is already happening in the container world and is more intense than what we're suggesting.17:47
clarkbSpamapS: or you are back to run a MAC17:47
SpamapSThere's no other security model for containers.17:48
clarkbI mean proper selinux17:48
clarkbwhich aiui docker and friends don't do17:48
SpamapSdocker does17:48
SpamapSvery well17:48
SpamapSevery docker container gets its own special SELinux context and you can basically throw that context into the "you get NOTHING"17:49
SpamapSbin17:49
SpamapShttp://www.projectatomic.io/docs/docker-and-selinux/ <-- easy read on the subject17:49
pabelangerI still think zuul-executor should call bubblewrap directly for now, otherwise, that seem like lot of work to build out a container thing (ks8?) on the control plane17:49
SpamapSpabelanger: me too17:49
SpamapSI just keep having to shake off the "but nodepool does that too.." twitch17:50
SpamapSI think the eventual answer _is_ going to be a k8s of executors.17:50
rbergeronspamaps: is that *all* distros or just the red hat family which requires a special / forked docker versiom?17:50
rbergeronbecause $yaydrama17:50
SpamapSrbergeron: I thought it was any docker built with --enable-selinux .. but maybe I'm being naive.17:51
SpamapSI'm not focusing on that. :)17:52
SpamapSBut, when we can circle back and add container support to nodepool, I think the way it happens is we teach nodepool to talk to k8s (and scale it with nodes from clouds?) and when somebody asks for container node types we give them containers and run playbooks inside said containers.17:54
rbergeronyeah -- i just wonder if the context ofvthat article makes assumptions (atomic amd all) which may not be universally truthy17:54
clarkbSpamapS: just for the record you can totally do that today if you need ti :)17:54
SpamapSrbergeron: I sense you have some experience in this realm and I defer to your pain.17:55
SpamapSclarkb: where would the containers run?17:55
clarkbSpamapS: wherever the nova scheduler puts them17:55
SpamapSwhat nova?17:55
SpamapSyou have access to a nova with container flavors?17:55
clarkbthe one your nodepool is talking to17:55
SpamapSI don't17:56
clarkbSpamapS: I;m not actually sure (I haven't listed all the flavors in the clouds to check)17:56
SpamapSI believe there's an IBM BlueMix container service that is a nova-docker17:56
rbergeronspamaps: all i know is i tried installing opebshift once on top of a standard opebstack deployment and woubd up discovering i needed thecred hat version of docker, which was not the one ibstalled, and i learned many things, lol17:56
SpamapSthat one can sign up for as a beta. I know it's possible. But it's not actually useful for Infra's clouds.17:57
jeblairwhile it's true that we want zuul v3 to be friendly to users who are not openstack-infra, i also think that if we construct something that openstack-infra can't run, we have probably failed.17:57
SpamapSjeblair: s/probably/mightily/ :)17:57
jeblairSpamapS: it's possible i have a fondness for understatement.  ;)17:58
clarkbSpamapS: I just want to clarify that because there is and has bee na lot of fud especially in third party ci land of "nodepool can't do x"17:58
jeblairmaybe17:58
SpamapSLike flexing after you break the door handle to your car. It's not.. really helping. ;)17:58
rbergeronspamaps: but -- ppl are working on improved kube modules right now (https://github.com/ansible/ansible-kubernetes-modules ) and i think things will be fine when we get to that point in time.17:58
clarkband it absolutely can... you just have to work with the api that is currently supported, nova17:58
clarkb(this was a big deal for third party ci and baremetal for a while)17:58
SpamapSrbergeron: Oh neat!17:58
SpamapSthat might come in handy around July-ish :)17:59
rbergeroni suspect the shade of kubernetes will come to help with the variations btwn kube implementations / providers (since everyone now has their own e terprise k8s versions)17:59
SpamapSJust guessing that's around the time we get good at running VM based nodepool and try to scale BonnyCI up and realize we need containers nao.17:59
rbergeron(something something, why bother learning from other projects...)17:59
SpamapSclarkb: respect, very true. However, if I, the user of Zuul, can't add the pieces I need to all computer-providing-clouds, from outside, as a user, it's a much less useful thing.18:00
SpamapSare kubernetes's diverging?18:01
SpamapSthat would be... ironic18:01
rbergeronim sure some are opinionated ;)18:02
rbergeronand god help us when kubevirt is a thing (launch vms from a kubernetes pod / cluster / whatever it is called)18:03
rbergeron*old lady shakes fist at cloud*18:03
SpamapSIt's the Go rewrite of Nova we've all been resisting writing ourselves.18:03
jeblairSpamapS: regarding bubblewrap -- why create a chroot image vs bind-mount /usr ?18:04
Shrewsrbergeron: i think you just broke my brain with that foreshadowing18:04
SpamapSjeblair: to take sharp objects away from attackers.18:04
clarkbrbergeron: k8s already has a vm option18:04
SpamapSprobably worth noting in spec18:04
rbergeronclarkb: ah, i thought it was still in wip18:05
clarkbrbergeron: I think it only supports kvm but ya you can tell it to make "containers" that are actually VMs18:05
SpamapSNot sure how much mileage we get out of that since we still have to give them python though.18:05
* SpamapS furiously battles his internal desire to rewrite Ansible in rust again.18:05
SpamapSbattles again, not rewrites again.18:05
jeblairSpamapS: ok.  just wondering whether it's worth the extra complexity.  or even whether bind mount could be an interim step with chroot image as a followup.18:05
SpamapSjeblair: yeah now that you ask.. it's entirely possible it's not that much of a win18:06
SpamapSjeblair: because we still have to give them python.. rsync.. internet access.. so.. yeah.18:06
rbergeronclarkb: ah. not sure if thats same or diff from https://github.com/kubevirt/kubevirt/blob/master/README.md18:06
jeblairSpamapS: like: "python -c 'download binary from internet and run it'"18:07
SpamapSor just python -c "exploit_stuff()"18:09
SpamapSNot much you can't do w/ python18:09
clarkbrbergeron: I'm trying to find it I thought it was in kubernets itself as a container deployment option but my googling is failing me18:09
SpamapSWe could mount noexec and nosuid and probably get some protection from 'download binary' but we still have to let the python binary run python code.18:10
SpamapSI guess we could write an ansible-playbook that just shoves its CLI args into a local socket, teach ansible-playbook to read its args from said socket,  and rm python once that has spawned. But zomg is this realy helping?18:11
SpamapSjeblair: yeah bind mount /usr is sounding more practical.18:11
jeblairya18:11
SpamapSgoing to revise spec18:12
* SpamapS once again resists urge to add "Rewrite Ansible in Rust" to Alternatives section18:12
* jeblair imagines a truly infinite array of alternatives18:13
jeblair"Go to the movies"  "Take a nap"18:13
Shrewspabelanger: Any chance you take a peek at the remaining np doc changes today? https://review.openstack.org/#/q/status:open+project:openstack-infra/nodepool+branch:feature/zuulv3+topic:docs18:16
rbergeronspamaps: im sure the rust folks would like that, since they use ansible to manage rust's infra ;)18:17
SpamapSjeblair: "Play Peter Molyneux's landmark 1989 game, Populous, in an Amiga emulator", is my favorite.18:18
rbergeroni generally recommend "think different / moar future" rather than think parallel ;)18:18
pabelangerShrews: yes, looking at the stack now18:18
SpamapSrbergeron: I like the idea of compiling modules into little native binaries locally, but... python does make a wee bit more sense. :)18:19
* mordred drives friend to airport and returns having missed all sorts of fun conversation!18:25
Shrewspabelanger: looking at it, i suspect that my docs changes may conflict with jeblair's stack of changes. it would be easier for me to rebase, so let's get his changes merged first.18:25
pabelangerShrews: sure18:25
pabelangerI think jeblair stack is ready, for the most part18:26
Shrewsjeblair: do you want anyone else to review https://review.openstack.org/448814 ?18:26
*** hasharAway is now known as hashar18:27
jeblairShrews: i think since it didn't really diverge from the email, we're probably good.18:28
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Update nodepool config syntax  https://review.openstack.org/44881418:33
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Add a test for multiple provider pools  https://review.openstack.org/45018318:33
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove api-timeout and provider.image-type  https://review.openstack.org/44934218:35
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970518:35
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935418:35
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Update docs for configuration syntax change  https://review.openstack.org/44933918:36
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973718:36
openstackgerritJames E. Blair proposed openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978118:36
jeblairShrews: addressed your comments18:36
*** eventingmonkey has quit IRC18:36
*** eggshell has quit IRC18:36
pabelangerworking on updating nodepoolv3.yaml now18:37
Shrewsjeblair: k. putting that one through since it's a doc change that was already +2'd18:38
*** eventingmonkey has joined #zuul18:42
*** eggshell has joined #zuul18:43
mordredShrews, jeblair: if the three heatclient-ectomy patches I just pushed up pass the dsvm tests, I'll land them and then cut a new shade release so that we can consume that az's method19:00
mordredif they don't pass dsvm we can cut a release without them19:00
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Update docs for configuration syntax change  https://review.openstack.org/44933919:21
jlkjesusaur: I took at look at your patch. Other than the pep8 thing, it looks right. Not sure why the tests are failing.19:39
jlkGiven that this is all one big series, I'm not sure what to do. I can't make my next patch on top of yours, because tests will fail. But I can't skip yours as it changes some things, so not sure what the next step is.19:39
jesusaurjlk: I'm looking at one of the failures now, and I think it's related to not ignoring formatting exceptions anymore19:41
jesusaurspecifically, I think test_json_status has a working report_url now, so I need to change the test to build a correct url to check19:42
jlkah19:45
jlkIt's pretty annoying that a subtle error can generate huge amounts of test output to examine.19:46
jesusaurjeblair: when you replaced the use of build number with the build url, you failed to notice that the build number was a component of the build url19:46
jesusaurjeblair: I'm replacing the number with the uuid in the url, but I can re-add the number if you would prefer shorter log urls19:47
jeblairjesusaur: oh hi19:47
jeblairjesusaur: which build url?19:47
jeblairjesusaur: the one that the executor reports for log streaming while a job is running?19:48
jesusaurjeblair: url_pattern in the test configs19:48
jesusauryeah19:48
jesusaurer, no, not the streaming, but the url that gets reported along with the success or failure message19:50
jeblairjesusaur: i think that is still somewhat in flux -- we're planning on having a websocket-based web stream of the ansible log; that doesn't exist yet, but that is where the build url will eventually point.  i'm not sure of the final format for that, but it will probably be based on the uuid, so if that's what we're doing now, it's probably close enough in spirit for tests, i'd think...19:50
jeblairjesusaur: (that was for the streaming thing ^)19:50
jeblairjesusaur: as for success and failure urls, i think we're just about able to remove the url_pattern from the zuul server config and instead replace it with success-url and failure-url in the job config19:51
jeblair(the idea being that becomes something a site admin sets on the "base" job)19:52
jesusauroh, ok, I didn't realize that was getting shuffled to another config location19:52
jesusaurbut that makes a ton of sense (setting it in a base job as a site admin)19:52
jeblairjesusaur: yeah, it was sort-of already in the job config since you could override it, so it seemed to make sense to just make that the standard way of doing it19:53
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Correct availability-zones documentation.  https://review.openstack.org/44914720:13
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Remove refs to removed nodepool commands  https://review.openstack.org/44915220:13
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Remove cron references  https://review.openstack.org/44914020:13
*** jamielennox is now known as jamielennox|away20:13
jeblairmordred: https://review.openstack.org/448913 may be of interest to you20:18
jeblairmordred: (and child)20:19
mordredjeblair: why yes it is - I was looking at that  afew days ago in fact20:19
mordredjeblair: it's a remarkably small patch20:20
pabelangerjeblair: if you want to add 450416 to your review queue, I believe that is the correct syntax for nodepool now20:20
jeblairmordred: yeah, it's good.  :)20:21
jeblairpabelanger: lgtm thanks!20:22
*** jamielennox|away is now known as jamielennox20:24
jheskethMorning20:24
pabelangerShrews: we'll need 450416 before we restart nl01.o.o20:25
Shrewspabelanger: now, if i +A that, it will be copied over via puppet, right?20:27
Shrewspabelanger: because the problem is, nodepool will notice it changed, then fail b/c it's still running the old code20:27
Shrewsso i think we need to stop n-l, approve the change, wait for puppet, then restart20:28
jeblair++20:28
jeblair(though i think it'll just spam the logs for a while and otherwise not do anything, so it's not super critical)20:28
pabelangerShrews: right. and agree with your statement20:29
Shrewspabelanger: going to stop n-l, then +A20:29
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove api-timeout and provider.image-type  https://review.openstack.org/44934220:30
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove deprecated networks syntax  https://review.openstack.org/44935420:30
Shrewsoh, those are convenient merges20:30
jeblairjhesketh: i copy/pasted some earlier irc discussion to answer your question in https://review.openstack.org/44875020:32
jheskethjeblair: thanks (looking)20:32
jheskethjeblair: sure, that's fair enough.. Shall I +w?20:33
jeblairjhesketh: ++20:34
* Shrews shakes fist at too many conflicting changes20:36
jeblairjesusaur: https://review.openstack.org/438028 and child are the changes i was thinking of20:36
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Refactor out Changeish  https://review.openstack.org/44891320:37
jeblairi'm about to rebase that on the nullchange removal20:37
jeblairwhich is imminent :)20:37
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Remove NullChange  https://review.openstack.org/44993520:38
jlkhopefully that won't throw all my patch set into whack :)20:39
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Stop logging git repo rsync output  https://review.openstack.org/44875020:43
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Correct availability-zones documentation.  https://review.openstack.org/44914720:43
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Remove refs to removed nodepool commands  https://review.openstack.org/44915220:44
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Docs: Remove cron references  https://review.openstack.org/44914020:44
Shrewsif those ^^^ conflict again, i give up20:44
mordredShrews: I knoew the feeling20:45
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Exercise statsd in tests and fix  https://review.openstack.org/44973720:45
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove ipv6-preferred and rely on interface_ip  https://review.openstack.org/44970520:45
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Remove mention of non-clouds.yaml from docs  https://review.openstack.org/44978120:45
*** hashar has quit IRC20:46
jeblairjhesketh: what's the intent for sqlalchemy reporter when 'score' is not specified?  store a 0 or NULL in the db?20:47
jheskethjeblair: currently it stores a 0.. Null might make more sense though20:48
jheskethjeblair: want me to update that?20:48
jeblairjhesketh: i was just updating it for other reasons, so i'll throw that in.20:49
jheskethcool, thanks20:49
jheskethjeblair: probably want to delete line 3120:49
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove url_pattern config parameter  https://review.openstack.org/44716520:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Simplify the log url  https://review.openstack.org/43802820:50
jeblairjhesketh: i went the other way actually -- kept 31 and dropped 41... (see comments i just posted)20:50
jeblairjhesketh: is there a reason we should do that in the report method instead of the initializer?20:50
jheskethjeblair: nope, just pointing out the useless line20:51
jeblairjhesketh: cool, hopefully that's gtg then.  :)20:51
jheskethyep, looking20:51
jheskethjeblair: I wonder if we should do a getSafeAttirbutes on Pipeline, Job and Build objects (like Changes) to be consistent?20:53
jeblairjhesketh: sounds like a good idea -- followup patch?20:54
Shrewspabelanger: i have to afk for a few minutes before the meeting. can i leave it to you to restart n-l when it's ready?20:55
pabelangerShrews: sure20:55
Shrewscool20:55
jheskethjeblair: sure, I'll do that now20:55
jheskethjeblair: we'll need to update the sa model to make the score nullable... I'll do that too if you like20:56
jheskethjeblair: I don't think we need a new migration though unless we're back porting this to zuulv2?20:57
jheskethor expecting to support an upgrade path20:57
jeblairjhesketh: it's in zuulv2, so we should do a schema upgrade (in both branches) or decide to keep it as 021:00
jeblairi'm happy with 0 for now if that's what's in the schema :)21:01
jheskethjeblair: okay, I think we should do it as a follow up change21:01
jheskethjeblair: it is, but I can fix it up21:01
jeblairok21:01
jeblairjhesketh: how about we switch https://review.openstack.org/447165 to 0, then change it to null along with the schema migration?21:02
jheskethjeblair: yep, just did that21:02
jeblairok cool21:02
jeblairjhesketh: were you pushing up a new ps to 447165?21:11
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Re-enable test_stuck_job_cleanup  https://review.openstack.org/44678321:13
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Remove url_pattern config parameter  https://review.openstack.org/44716521:14
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Implement getSafeAttributes for other objects  https://review.openstack.org/45045921:14
jheskethjeblair: ^21:14
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Make sql reporter score null when not set  https://review.openstack.org/45046021:14
jeblairw00t21:14
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Make sql reporter score null when not set  https://review.openstack.org/45046021:15
pabelangerstarting nl01.o.o21:15
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Consume interface_ip from nodepool node  https://review.openstack.org/44970621:17
jeblairmordred, jhesketh: ^ updated that to fix a merge conflict (and added a doc TODO)21:17
jheskethjeblair: lgtm21:18
jesusaurjeblair: ah, thanks, 438028 is definitely going to change how I handle 44979421:25
jeblairjhesketh: i'm fixing pep8 in 16521:26
jheskethjeblair: ack21:26
jesusaurjhesketh: would you be willing to copy my formatUrlPattern exception handling from 449794 into 438028?21:27
jesusaur(note: it exposes some bugs)21:27
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Make sql reporter score null when not set  https://review.openstack.org/45046021:28
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Implement getSafeAttributes for other objects  https://review.openstack.org/45045921:28
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove url_pattern config parameter  https://review.openstack.org/44716521:28
pabelangerShrews: we look to be collecting Gathering host keys properly21:28
jheskethjesusaur: I think we could do that as a follow up instead21:29
jheskethjeblair: unless you disagree ^21:29
jheskethjesusaur: I'm happy to do that if you'd like though21:30
jeblairfollowup sounds good21:32
jesusaurjhesketh: yeah, it would be great if you could write that follow-up; it would let me go back to debugging 44627521:34
pabelangerShrews: and confirmed by using zk_shell21:34
jheskethjesusaur: sure, will do21:34
Shrewspabelanger: we've been doing that for a few days21:35
Shrewsat least, i thought we were21:35
pabelangerShrews: Oh, neat.21:36
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Make sql reporter score null when not set  https://review.openstack.org/45046021:41
openstackgerritJoshua Hesketh proposed openstack-infra/zuul feature/zuulv3: Catch and log url pattern formatting errors  https://review.openstack.org/45046821:47
jheskethjesusaur: ^21:47
jesusaurjhesketh: awesome, thanks21:50
jesusaurjlk: I think we should rebase the github stack on top of 45046821:50
jesusaurjlk: and I can help debug that stack if we start getting a ton of new failures21:55
SpamapS'bout meeting time eh?21:59
jeblairyep! zuul meeting time in #openstack-meeting-alt22:00
jlkjesusaur: alrighty I will give it a shot.22:57
jlkjesusaur: looks like I have to rebase anyway since all my PRs just got a merge failure.23:06
jlkjesusaur: sadly 450468 is failing.23:08

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!