Monday, 2016-11-14

*** yolanda has quit IRC04:18
*** bhavik1 has joined #zuul05:28
tobiashjeblair: hi, I have a question about https://review.openstack.org/#/c/396719/05:49
tobiashis snapshot support really going to be removed?05:49
tobiashI currently have two use cases which rely on this mechanism05:50
tobiashI didn't manage to prepopulate docker images during diskimage build05:51
tobiashand creating windows images is also not quite easy with diskimage builder05:51
tobiashmy current workflow for linux nodes is creating them via diskimage builder and use that as base image05:56
tobiashthe setup scripts then iterate over a specific tag in a docker registry and fetch all images with this tag05:57
tobiashfor that step docker needs to run which I didn't get to work during diskimage creation05:58
*** abregman has joined #zuul06:05
*** pabelanger has quit IRC06:28
*** pabelanger has joined #zuul06:34
*** yolanda has joined #zuul07:33
*** abregman_ has joined #zuul08:37
*** abregman has quit IRC08:39
*** abregman_ has quit IRC08:47
*** abregman has joined #zuul08:47
*** hashar has joined #zuul08:51
*** abregman has quit IRC09:12
*** abregman has joined #zuul09:18
*** openstackgerrit has quit IRC09:47
*** openstackgerrit has joined #zuul09:48
*** bhavik1 has quit IRC09:54
*** bcoca has joined #zuul13:37
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable TestMergerRepo() class for testing  https://review.openstack.org/39718913:40
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable TestMergerRepo() class for testing  https://review.openstack.org/39718913:42
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_head_is_dequeued_once test  https://review.openstack.org/39680313:42
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_noop_job test  https://review.openstack.org/39680713:42
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_merger_repack_large_change test  https://review.openstack.org/39680513:42
openstackgerritPaul Belanger proposed openstack-infra/zuul: Remove includes and parameter functions  https://review.openstack.org/39464413:47
openstackgerritPaul Belanger proposed openstack-infra/zuul: Add tenant support to zuul client  https://review.openstack.org/39385013:47
*** abregman is now known as abregman|mtg15:44
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_gate test  https://review.openstack.org/39727716:19
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_gate / test_crd_multiline / test_crd_gate_reverse  https://review.openstack.org/39727716:26
*** abregman|mtg is now known as abregman16:27
*** abregman has quit IRC17:08
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_check job  https://review.openstack.org/39731717:32
pabelangerjeblair: clarkb: mordred: ^ was a little tricky, in getting access to the JobDir of a build. Let me know what you think of that approach17:32
*** rattboi has joined #zuul17:34
mordredpabelanger: it doesn't seem extra crazy to me17:34
clarkbthats because zuul is cleaning up the jobdir on its own when job completes?17:35
pabelangerYa17:36
pabelangerwe could override the JobDir path, maybe place it into the test_root path for ZuulTestCase.  Use JobDir(keep=True), then let the ZuulTestCase handler did the test_root folder17:38
pabelangerthen we don't need to hold_jobs_in_build17:38
clarkbI think thats probably more invasive17:38
pabelangerfor sure17:39
clarkbthe upside to this is its fairly minimal, basically just don't execute tests while we check things17:39
clarkbI like this solution17:40
pabelangerack17:44
*** hashar is now known as hasharAway17:51
*** Shuo has joined #zuul17:55
Shuohow to start participating in zuul v3 and take a task from the storyboard? https://storyboard.openstack.org/#!/story/200079118:09
pabelangerShuo: we should be having a meeting today at 22:00UTC for zuul, I suspect we'll be going over a few things18:31
Shuopabelanger: what time is 22:00UTC  for Pacific Time? And also, is the meeting conducted through this channel? (Love to participate)18:32
clarkbShuo: it is 1833UTC right now18:33
pabelangerShuo: http://eavesdrop.openstack.org/#Zuul_Meeting for more info18:33
pabelangerlists time and location18:33
Shuopabelanger: clarkb: cool, thanks.18:35
Shuopabelanger: looks like today the first meeting? Link from "Logs from past meetings" is empty (not accessible).18:39
pabelangerShuo: yup!18:40
pabelangerShuo: prior to todays meeting, we used the project infrastructure meeting timeslot for some zuulv3 discussions.18:41
* Shrews wonders about the agenda18:41
jeblairShrews: 'create an agenda' is on the agenda.  it's a real bootstrapping meeting.  :)18:46
jeblairtobiash: that's the plan -- at least for the work we're doing in preparation for zuulv3.  we stopped using snapshot image builds a long time ago.... maybe greghaynes or one of the other dib folks could help address the docker issue you have?18:51
jeblairtobiash: however, if folks really want a snapshot image builder, and are willing to step up and do some work on it, it *is* compatible with the new design of nodepool, and i would be happy to help describe how to implement it.18:53
clarkb(I am going to guess the docker daemon and needing a socket are the problems with doing that in dib, likely solveable by using "outer" docker to populate store in chroot)18:55
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_branch test  https://review.openstack.org/39733718:59
Shuojeblair: regarding image-base or not, are we talking about the zuul installation itself?18:59
jeblairShuo: no, that's an unrelated topic about how nodepool gets the images it uses to launch worker nodes.  we used to use a snapshot approach (launch a server, do stuff, snapshot the vm, then use that to launch the worker nodes).  but we switched to diskimage-builder because the image ended up being different in every cloud we used (because they started out different).19:01
Shuopabelanger: saw your update at https://storyboard.openstack.org/#!/story/2000791, where is your repo on github? (you gave the openstack git endpoint, but not github one)19:05
pabelangerShuo: we don't do any development on github, just a best effort to mirror there. I'd recommend using git.o.o. The mirror is http://github.com/openstack19:06
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_cycle_join test  https://review.openstack.org/39734019:13
*** phschwartz has joined #zuul19:23
openstackgerritMerged openstack-infra/nodepool: Transition ZK API from dict to object model  https://review.openstack.org/39459219:23
Shuopabelanger: does your ansible script assume an all-in-one situation?19:23
openstackgerritMerged openstack-infra/nodepool: Combine ZKTestCase with DBTestCase  https://review.openstack.org/38396219:24
pabelangerShuo: no, I've done my best to make the role multi host19:24
openstackgerritMerged openstack-infra/nodepool: Supply ZK connection information to test configs  https://review.openstack.org/38396319:25
openstackgerritMerged openstack-infra/nodepool: Add getMostRecentBuildImageUpload method to zk  https://review.openstack.org/38396419:25
openstackgerritMerged openstack-infra/nodepool: Assume diskimage and image names are the same  https://review.openstack.org/38396519:25
openstackgerritMerged openstack-infra/nodepool: Update waitForImage test method for ZK  https://review.openstack.org/38396619:25
openstackgerritMerged openstack-infra/nodepool: Use diskimage name when looking up image on disk  https://review.openstack.org/39642219:25
openstackgerritMerged openstack-infra/nodepool: Override the cleanup interval in builder fixture  https://review.openstack.org/39642319:26
openstackgerritMerged openstack-infra/nodepool: Add __repr__ methods to ZK objects  https://review.openstack.org/39642419:26
Shrewsyay for merging the things19:26
pabelangerhttp://git.openstack.org/cgit/openstack/windmill/tree/playbooks/group_vars/zuul-merger.yaml would be an example of how to only setup zuul-merger19:26
openstackgerritMerged openstack-infra/nodepool: Re-enable test_dib_image_list  https://review.openstack.org/38396719:26
pabelangerShrews: exciting19:27
jeblairShrews: yeah, my last change failed in zuul, but that test passes when i run locally.  :/19:28
openstackgerritMerged openstack-infra/nodepool: Re-enable test_image_list_empty  https://review.openstack.org/39644919:28
jeblairi rechecked to see if it's transient19:28
Shrewsi do not know how to make my sb TODO go away, but maybe SpamapS can do things with it19:28
SpamapSShrews: did you add a Task: header?19:29
Shuopabelanger: quite a while ago, I did something of Vagrant + Ansible (for a different stack we used back end, and a lot of further work has been moved to internal development) https://github.com/shuoy/logging-for-openstack. Basically, the idea/goal of that was bring up a demo from a laptop. Let me explain a bit to see if the idea is compatible to your work...19:29
ShrewsSpamapS: i can basically do nothing with storyboard since i have no permissions. i'm failing to see its usefulness, tbh19:29
SpamapSwhhherrrrt?19:29
SpamapSoh the board19:29
SpamapSShrews: I said in the email, just ask for perms if you want to move the cards.19:29
Shuo1. we'd like to isolate the demo environments from what kind of hosts the demo runs on. So, all the ansible work are on top of vagrant VMs.19:30
SpamapSShrews: you have card moving access.19:30
Shuopabelanger: 1. we'd like to isolate the demo environments from what kind of hosts the demo runs on. So, all the ansible work are on top of vagrant VMs.19:30
SpamapSShrews: but all that I really want to make sure is that people claim work so we don't re-work stuff19:31
pabelangerShuo: I have been toying around with the idea of using lxc to further isolate things, for testing / demo at least.19:31
Shuopabelanger: 2. the kind of VMs cluster (be it a single node or multiple nodes) is configurable by the demo-er (simpley change a yaml file)19:32
pabelangerShuo: otherwise, I use a cloud for my local testing, where I spin up multiple VMs19:32
Shuopabelanger: after the 'substrate' VM cluster is setup through vagrant up, run the ansible script in the bootstrap machine and the ansible script can automatically reflect the nature of the vagrant cluster.19:33
Shuopabelanger: in this idea, we can easily migrate the work from vagrant to AWS instnaces.19:34
pabelangersure, that works. That is great thing about ansible, just need an SSH connection and things should work as expected. Assuming both are running the same OS19:34
clarkbansible can even spin up the VMs/containers19:35
clarkbno need for vagrant19:35
pabelangeryup19:35
pabelangerI haven't had time to use the lxc task, but the ansible openstack team uses it I believe19:35
pabelangerobviously, os_server works well too :)19:36
*** abregman has joined #zuul19:38
jeblairpabelanger: i left a comment on the tenant/json change19:38
pabelangerjeblair: ack, just looking now19:39
ShrewsI find it odd that our Backlog list on our board does not list all tasks within an individual story, only one.19:44
ShrewsIs that how it's supposed to work?19:44
ShrewsIf so, it should just use the story title and not a random task title from the story, IMO19:45
Shrewsperhaps i should take this to #storyboard  :)19:45
jeblairShrews: i think a list can have either stories or tasks in it19:47
jeblairShrews: and i believe they were/are manually populated19:47
jeblairShrews: i would expect a story entry to have the story title, though.  does one not?19:47
Shrewsjeblair: https://storyboard.openstack.org/#!/story/2000768, for example19:48
Shrewsshows up as "Nodepool changes" in our Backlog, though i just manually edited that one. Perhaps i missed a step19:48
Shrewssame with https://storyboard.openstack.org/#!/story/2000767, which i did not change19:50
ShrewsI've yet to see one that isn't using a task title, TBH19:51
jeblairShrews: which task title in 2000767 do you see in the backlog?19:53
Shrewsjeblair: "switch nodepool...", though i moved it to In Progress from Todo19:54
jeblairShrews: i believe that is a task entry19:55
Shrewsjeblair: yep, which is my point19:55
Shrewswhere are the other tasks?19:55
jeblairShrews: they have not been added.  but can be added manually19:55
jeblairShrews: (there is nothing automatic about this workboard)19:56
Shuopabelanger: after cloning the repo, what am I suppose to do -- the doc does not seem to instruct it? (I am on an ec2 instance)19:58
greghaynestobiash: Hey, dib should be able to make docker images just fine, if it cant for some reason I'd be happy to look in to it. The windows thing is wierd, I dont know what making a windows image would even mean since MS releases them, dib is totally capable of wgeting an image and outputting it though...20:01
clarkbgreghaynes: I think in this case its not making a docker image, its fetching docker images from a docker registry as part of the dib image build20:03
greghaynesaha20:04
clarkbgreghaynes: but that likely doesn't work due to socket and docker daemon20:04
greghaynesI wonder if theres some way to just cache the image data and feed it in to docker later20:04
greghaynesthe docker image data, that is20:05
pabelangerShuo: it is an ansible role, so you'll need to build up a playbook to consume it20:05
greghaynestobiash: one option is we could make an element which docker save's a bunch of images from the hypervisor, copies them in to the image, then docker load's them on boot20:09
clarkbgreghaynes: tobiash or maybe use an external docker process to write into the chroot20:10
greghaynesooo20:10
clarkba lot of our caching setup works that way so you get a cache :)20:10
greghaynesYea, if someone has the docker-fu to know how to do that it'd be awesome20:10
SpamapSShrews: many of the stories didn't have any tasks broken out, so they were just added as a single task. The ones that were added as stories were those that, by working, would naturally generate more tasks.20:18
SpamapSShrews: I think we'll work on a better set of instructions (something shorter than a 6 paragraph email) that explains what we're tryign to do with the board, and maybe relieves you from feeling uncertain about what to do with it.20:22
pabelangerjeblair: I'm going to rebase away the tenant/json change, since there might be some back and forth on that change. And don't want to spam 15 patches at a time20:32
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_check job  https://review.openstack.org/39731720:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_check_smtp_pool test  https://review.openstack.org/39670720:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable TestMergerRepo() class for testing  https://review.openstack.org/39718920:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_live_reconfiguration test  https://review.openstack.org/39348820:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_disable_at test  https://review.openstack.org/39678520:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_check_reconfiguration test  https://review.openstack.org/39678820:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_head_is_dequeued_once test  https://review.openstack.org/39680320:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_gate / test_crd_multiline / test_crd_gate_reverse  https://review.openstack.org/39727720:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_cycle_join test  https://review.openstack.org/39734020:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_repo_deleted test  https://review.openstack.org/39670320:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_check_unknown test  https://review.openstack.org/39679820:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_gate_unknown / test_crd_undefined_project  https://review.openstack.org/39679920:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_noop_job test  https://review.openstack.org/39680720:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_crd_branch test  https://review.openstack.org/39733720:34
openstackgerritPaul Belanger proposed openstack-infra/zuul: Re-enable test_merger_repack_large_change test  https://review.openstack.org/39680520:34
*** abregman has quit IRC20:55
openstackgerritPaul Belanger proposed openstack-infra/zuul: Update webapp status json to support tenants  https://review.openstack.org/39168121:00
jheskethMorning21:26
*** rcarrillocruz has joined #zuul21:30
jeblairreminder: our first meeting is in ~30 mins21:31
rcarrillocruz++21:36
mordredmorning jhesketh !21:37
jlkjeblair: which channel?21:53
*** rmoe has joined #zuul21:56
jeblairjlk: #openstack-meeting-alt   (http://eavesdrop.openstack.org/#Zuul_Meeting  for reference)21:57
jeblairhey everyone! zuul meeting now in #openstack-meeting-alt  yay!22:00
pabelangeryay22:00
jheskethsigh, my teleconf is running late (sorry I didn't join earlier)22:18
jeblairpabelanger: my thought is that if you have run into a test where you tried to enable it, but found it too complex -- how do we make sure people can see that?23:01
*** rcarrillocruz has quit IRC23:03
pabelangerjeblair: Good question, I've been trying to hack on them locally. But likely need a place to track them23:03
pabelangertest_client_enqueue_ref is a good example23:03
pabelangerI have code for it, but don't understand why right now23:03
pabelangertest_crd_cycle_join was another one, but I just figured that out this morning.  I was working on it off and on for the last 3 days23:05
pabelangerJobDir() location for git_root23:05
jeblairpabelanger: how about you make a task for it, and add some notes to it?  feel free to assign yourself or not depending on whether you want to claim it, but at least this way, there will be some history and shared information23:05
jeblairpabelanger: also, i think at some point, you should work with me on the issues23:06
pabelangerjeblair: sure, I can make a few issues in the morning, dump some history into it.23:07
Shuoto understand how zuul serializes the incoming commits and speculative executing it, which piece of code should I start reading?23:07
pabelangerjeblair: agreed, I don't think it will take long to dive into the issues. Like you said, just scheduling the time for it.23:07
jeblairbasically, i should have a work queue.  so when you hit a wall, put something into my queue and i'll pop things off23:07
jeblairpabelanger: ^23:08
pabelangerjeblair: okay23:08
jeblairShuo: that's the pipeline managers.  independentpipelinemanager and dependentpipelinemanager share a parent class basepipelinemanager23:08
clarkbjeblair: re https://review.openstack.org/#/c/396719/ and cleaning things up, that might be a good opportunity to rename the snapshot image db table?23:12
clarkbthough probably needs to be a followup change since thats probably not the smallest change23:12
jeblairclarkb: well, actually it needs to go away23:12
jeblairsince it's replaced by zookeeper23:13
clarkboh right nodepool will check zk for those uuids23:13
jeblairyeah, so building on that change should include changes which switch to using the zk api to get the image uuid and also remove the snapshot db table23:14
jeblairShrews, pabelanger: ^23:14
mordredjeblair: didn't I already see a patchto use the zk api to get the image uuid? or am I imagining that?23:14
jeblair(as well as changes to make the commands work, and changes to make the tests work)23:14
clarkbmordred: I think that was just enough change to make a single test pass, likely needs much more updatse like that23:15
jeblairmordred: i wrote the method that will be used (the "get me the right image" method), and yeah, used it in a test as clarkb says23:15
pabelangerI have to step away now, but will catch up on the backscroll when I return23:15
jeblairclarkb: though honestly, that's just about the only interaction nodepoold needs to have with it23:15
clarkbjeblair: I think there are other places like command to list images23:16
clarkbalso I think allocation may have somethign that double checks it can create instances if an image exists for it?23:16
jeblairclarkb: yes, the commands need updating, but i'm pretty sure nodepoold (note the d) only needs that single interface with zk.23:16
jeblairclarkb: i think the allocator will use that same method23:18
clarkbah ok23:18
jeblairthe successor to getCurrentSnapshotImage(provider, image)23:19
jeblairwhich shows up 4 times in nodepoold (launch node, launch subnode, allocator, and, weirdly, right before launching a node)23:21
Shuojeblair: how does this queue, i.e., the final source of truth for the sequence, get persisted?  so that the enqueue and dequeue with mutex can operate on this central piece of information?23:28
jeblairShuo: it's just an in-memory data structure; it doesn't persist at all23:33
jeblairShuo: the triggers (ie, gerrit) push events into an event queue, and the scheduler processes those events in order, some of which may cause items to be enqueued into the pipelines23:34
jeblairShuo: (the pipeline managers then handle the sequencing inside of the pipeline and running jobs in parallel)23:35
Shuojeblair: thanks. if zuul scheduler process gets bogged down for some reason, would that cause any issue (e.g., lose some tests)?23:36
jeblairShuo: no, it just gets very slow23:36
Shuojeblair: I may used the wrong term. I meant when the server/process holding that piece of in-memory data structure (which is 'pipelines' I think) is restarted, the items that triggers/clients believe they have successfully enqued for future processing will be lost along with that restart, but the clients/triggers does not know 'something is lost'23:41
Shuojeblair: what effect this restart would cause? out-of-order or some commits won't be processed for a period of time?23:42
*** phschwartz has quit IRC23:49
*** phschwartz has joined #zuul23:49
*** phschwartz has quit IRC23:50
*** phschwartz has joined #zuul23:51
*** hasharAway has quit IRC23:52
jeblairShuo: oh yeah, when it's restarted all state is lost23:57
jeblairwe should improve that in v323:57
*** Shuo has quit IRC23:58

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