Monday, 2017-06-12

*** yolanda has quit IRC00:48
openstackgerritTristan Cacqueray proposed openstack-infra/zuul feature/zuulv3: bubblewrap: adds --die-with-parent option  https://review.openstack.org/47316400:59
mordredtristanC: ^^ is that supposed to be "sleep && disown" rather than "sleep & disown" ?02:53
mordredor is the & correct?02:53
mordredtristanC: ah! the & is correct - I have learned something!02:53
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Support booting cloud-images by name or id  https://review.openstack.org/47295902:57
tristanCmordred: heh :-) disown is like nohup without the pts redirection to a file03:04
tristanCwell I'm not super happy with that test, but since bwrap double fork it's not trivial to detect process leak03:06
*** yolanda has joined #zuul03:11
*** yolanda has quit IRC04:35
openstackgerritTristan Cacqueray proposed openstack-infra/zuul feature/zuulv3: zuul_stream: do not collect delegated task  https://review.openstack.org/47321905:53
openstackgerritTristan Cacqueray proposed openstack-infra/zuul feature/zuulv3: zuul_stream: harden log processing  https://review.openstack.org/47322206:01
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement a static driver for Nodepool  https://review.openstack.org/46862406:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Extend Nodepool configuration syntax to support multiple drivers  https://review.openstack.org/46875106:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Collect request handling implementation in an OpenStack driver  https://review.openstack.org/46875006:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Abstract Nodepool provider management code  https://review.openstack.org/46874906:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Abstract Nodepool request handling code  https://review.openstack.org/46874806:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Add support for custom ssh port  https://review.openstack.org/46875206:11
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool feature/zuulv3: Implement an OpenContainer driver  https://review.openstack.org/46875306:11
*** jiaohaolin1 has joined #zuul06:13
jiaohaolin1hi ,everybody , I set up my CI with zuul 2.5.2 ,it works, but I can not open zuul page (master ip),it jump to https://jenkins and still can't open it06:17
jiaohaolin1the last version of zuul can show the page, what should I do ?06:18
tristanCjiaohaolin1: did you setup the vhost like http://git.openstack.org/cgit/openstack-infra/puppet-zuul/tree/templates/zuul.vhost.erb ?06:19
jiaohaolin1I'm not sure , I setup it follow https://docs.openstack.org/infra/openstackci/third_party_ci.html06:23
jiaohaolin1tristanC: what should I do ? setup the vhost? how to do it ? Thank you very much06:25
jiaohaolin1tristanC: :-D06:26
*** yolanda has joined #zuul06:28
tristanCthe "zuul page" isn't listening by default on port 80, it needs a redirection like the one in zuul.vhost06:35
*** isaacb has joined #zuul07:13
*** yolanda has quit IRC07:22
*** yolanda has joined #zuul07:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul feature/zuulv3: github: handle ping event  https://review.openstack.org/47324907:44
*** yolanda has quit IRC08:03
*** bhavik1 has joined #zuul08:10
*** isaacb has quit IRC08:12
*** lennyb has joined #zuul08:15
openstackgerritTristan Cacqueray proposed openstack-infra/zuul feature/zuulv3: github: retry pull_request()  https://review.openstack.org/47330108:20
*** isaacb has joined #zuul08:21
*** hashar has joined #zuul08:41
*** smyers has quit IRC09:02
*** smyers has joined #zuul09:13
*** yolanda has joined #zuul09:23
*** bhavik1 has quit IRC09:30
*** jkilpatr has quit IRC10:45
*** _ari_ is now known as _ari_|conf10:45
*** yolanda has quit IRC10:48
*** jkilpatr has joined #zuul11:05
*** hashar has quit IRC11:21
*** hashar has joined #zuul12:20
*** yolanda has joined #zuul12:24
*** yolanda has quit IRC14:45
*** isaacb has quit IRC15:02
*** isaacb has joined #zuul15:12
openstackgerritMerged openstack-infra/zuul-jobs master: Add extra-test-setup role  https://review.openstack.org/47247216:10
openstackgerritMerged openstack-infra/zuul-jobs master: Add python unit test jobs  https://review.openstack.org/47248416:10
rcarrillocruzyo yo16:15
rcarrillocruzhttp://38.145.33.129:9191/reports/16:15
rcarrillocruzautomated integration tests of ansible OVS16:16
rcarrillocruzpowered by nodepool v3 cloud-images16:16
rcarrillocruzand ARA16:16
rcarrillocruzwhere's dmsimard dammit16:16
rcarrillocruzi'll tweet him later16:16
mordredperiodic jobs with nodepool as a stop-gap til you can spin up the v3, yeah?16:16
*** isaacb has quit IRC16:16
rcarrillocruzyeah16:16
mordredrcarrillocruz: I bet since you have that, transitioning to periodic jobs in v3 will be a decently easy next step16:17
rcarrillocruzi need to find time to poke at zuul github stuff16:17
rcarrillocruzright16:17
rcarrillocruzthe playbook should be just the same16:17
mordredyup16:17
rcarrillocruzansible all the way down \o/16:17
mordred\o/16:17
rcarrillocruzso kudos folks for all the work you're doing16:17
mordredit's almost like this ansible idea is gonna work out :)16:17
rcarrillocruzhaha, indeed16:17
gundalow\o/16:42
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add 'description' field to jobs  https://review.openstack.org/47248316:43
Shrewsrcarrillocruz: v3 builder _and_ launcher?16:43
rcarrillocruzno builds, just launcher with cloud-images16:44
rcarrillocruzbut yeah, v3 branch16:44
Shrewsawesome16:44
Shrewspabelanger: you had requested this I think? https://review.openstack.org/470364   Would be nice to get that merged16:45
clarkbrcarrillocruz: you are using the as of yet unreleased feature on the v3 branch to supprot launching off of existing cloud images?16:46
rcarrillocruzyup16:47
clarkbgood to hear that is working, maybe you can respond to the nodepool + arm64 thread with how you set that up?16:48
clarkbI think they would be interested16:48
pabelangerShrews: thanks16:48
clarkbhttp://lists.openstack.org/pipermail/openstack-infra/2017-June/005397.html that thread16:48
jeblairclarkb: i'm not sure i'd recommend that someone try to use the v3 nodepool with a v2 openstackci setup.  are you sure you want to do that?16:52
clarkbjeblair: I think paul already did? he mentioned teh change at least16:52
clarkbit was more of "heres a thing that exists it works for some people and this is how they are using it"16:53
clarkbperhaps that would make them interested in backporting the feature to master?16:53
jeblairclarkb: i'm not aware of anyone using v3 nodepool with v2 zuul.  in fact, i think we've even shelved the idea of doing that in infra...16:54
rcarrillocruzalthough, not sure if i read that correctly, i'm running off feature/zuulv3, i mean , support for that is already in that branch16:55
rcarrillocruznot running a local patch16:55
clarkbrcarrillocruz: yes the feature you are using is only on zuulv3 branch, not on master16:55
rcarrillocruzyep16:55
rcarrillocruzgah16:56
rcarrillocruzwifi died16:56
rcarrillocruzclarkb: was that arm comment to me16:56
rcarrillocruz?16:56
rcarrillocruzah yeah16:58
rcarrillocruzgmail refreshed16:58
rcarrillocruzi'll respond with a paste for my nodepool.yaml16:58
clarkbya was just thinking it might be useful information to them. And maybe we can suggest they backport the feature?16:58
clarkbjeblair: ^16:58
jeblairi don't think we should backport the feature16:58
pabelangerhttps://review.openstack.org/#/c/472861/ is an easier review for missing bindep.txt dependencies on openstack-zuul-roles16:58
jeblairit's not straightforward, and it sends some pretty mixed signals about nodepool development16:58
jeblair(also, reviewer time is at a premium right now)16:59
rcarrillocruzhas nova servers metadata tags ever been considered and asked? from docs I see meta cna be put on images, but not in a server-by-server basis ?17:01
rcarrillocruzfor nodepool i mean17:01
clarkbrcarrillocruz: we use it for leak detection. Nodepool adds metadata that says nodepool launched this node so it can check for them later17:02
*** hashar has quit IRC17:02
clarkbrcarrillocruz: we also use it for key management now17:02
rcarrillocruzhmm, so you can put a meta param on a label?17:02
clarkbrcarrillocruz: I don't know if we expose the ability to add arbitrary meta data if that is what you mean17:03
openstackgerritMerged openstack-infra/zuul-jobs master: Add documentation to jobs  https://review.openstack.org/47248517:03
clarkbbut we do use metadata in nodepool on nova instances17:03
openstackgerritMerged openstack-infra/zuul-jobs master: Add Sphinx module for Zuul jobs  https://review.openstack.org/47274317:03
rcarrillocruzyeah, that's what i'm after17:03
*** morgan is now known as mordgan17:03
pabelangerI thought we did have a meta field at one point17:03
rcarrillocruzyeah, but for images17:03
*** mordgan is now known as morgan17:03
pabelangerah, right17:04
rcarrillocruzwould people be opposed to it ? I think it can be useful on just nodepool scenarios, thinking of getting automatic group form Ansible openstack.py via metadata17:05
rcarrillocruzlike label name for example17:05
clarkbrcarrillocruz: I think it would likely be fine. The biggest thing to watch out for is conflicting with the keys nodepool already needs to use and adding so much metadata that an instance exceeds its metadata limit17:09
jeblairrcarrillocruz: provider name and image name are already automatic group entries17:09
jeblairrcarrillocruz: also, note that zuulv3 (which i know you aren't using) has support for inventory groups17:09
rcarrillocruzyeah saw that, but no label right?17:09
jeblairrcarrillocruz: right, i don't think label is included17:09
rcarrillocruzmaybe auto adding label instad of arbitrary  meta is a better compromise17:10
rcarrillocruzi'll get a look at the code17:10
jeblairrcarrillocruz: yeah, i suspect if we were to write the automatic group metadata stuff today, we would have included label; i think it may have been a v3 oversight.17:11
rcarrillocruz++17:11
jlko/17:28
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add log streaming test  https://review.openstack.org/47107917:41
Shrews^^^ that *might* actually work now17:41
Shrewsheavily commented because computers are hard17:42
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Enhance sphinx plugin  https://review.openstack.org/47354417:42
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add log streaming test  https://review.openstack.org/47107917:46
Shrewsgah. pep817:46
Shrews\o/ for green things18:00
*** cinerama` is now known as cinerama18:24
*** Thelo_ has joined #zuul18:26
*** Thelo_ has left #zuul18:27
mordredShrews: \o/19:00
mordredShrews: btw - don't know if you saw in scrollback - but starting https://review.openstack.org/#/c/437764 I did a bit of work on getting finger urls into the status page19:01
Shrewsmordred: sweet. will begin looking at those19:03
Shrewsmordred: responded to your call for HALP on that one20:10
clarkbjeblair: while I'm poking at log related items I recall that zuul 2.5 emits the job compelte event after all logs are completely copied. Is that accurate? and that behavior will carry through to zuul v3? wondering if I can simplify the logstash workers20:49
jeblairclarkb: v2.5: yes20:55
jeblairclarkb: v3: there are no zmq events in v3.  instead, we will write a post playbook to deal with log processing.  first, we'll probably just have it either send a compatible zmq event, or maybe submit a background gearman job.  later, i think it can perhaps take on some of the actions we actually do in the processors.  the timing will depend on which job we attach the post-playbook to.  i'm guessing our base job since we want to include console logs.20:57
*** harlowja has quit IRC21:02
clarkband we can assume that happens after the console iw copied right?21:06
clarkbbasically no more need to delay21:06
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Default bubblewrap to work_root  https://review.openstack.org/47309921:23
pabelangerjeblair: left comment on 47309921:25
jeblairclarkb: i think that's correct in both cases, yes.21:26
mordredjeblair: most of our tests do not define a success_url or a url_pattern, so the final url reported is the status_url - do you have thoughts on what you think we _should_ be doing there?21:27
jeblairmordred: define it if it's important for the test?21:29
*** jkilpatr has quit IRC21:30
jeblairpabelanger: thanks; replied.  https://review.openstack.org/473164 is also related.21:30
mordredjeblair: indeed. lemme ask better questions: is url_pattern still a thing? do you think we should prefer a zuul-level url_pattern? or a pipline-level success_url?21:30
mordredjeblair: (like, I'm looking at test_json_status which righ tnow has thesame values in url and report_url and I'd like to improve it a little bit to have different values21:31
pabelangerjeblair: thanks21:32
jeblairmordred: neither zuul-level url_pattern nor pipeline success-url are things anymore; success-url is job-levl only now21:32
mordredjeblair: gotcha. so defining a success-url on the base job in that test would be the thing I shoujld do21:32
jeblairmordred: yep i think so21:32
jeblairmordred: looking at the test21:32
jeblairmordred: yep21:33
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Make logging helper method in zuul_stream  https://review.openstack.org/47296321:34
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Change log streaming link to finger protocol  https://review.openstack.org/43776421:34
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Move streaming url formatting to model  https://review.openstack.org/47309021:34
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Only prepend hostname on multi-node plays  https://review.openstack.org/47296421:34
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Support finger ports in finger URL  https://review.openstack.org/47310321:34
mordredjeblair: ok. I'll add that to this stack21:34
mordredjeblair: also - paul pointed me at the proposed rfc for finger urls, which is finger://{host}[:{port}]/{resource} rather than finger://{resource}@{host}[:{port] - you good with that?21:35
jeblairmordred: that makes me sad... does anyone implement it?  (but i think we should probably follow the rfc or implementations on this, not make up our own)21:37
mordredjeblair: lynx implements support for both forms21:38
mordredjeblair: I do sort of like host/resource if for no other reason that it should make requests of specific files not look as strange21:39
mordredjeblair: although I agree with the sad feeling21:39
jeblairmordred: 'links' seems to send "/W foo" when you finger://foo@host/.  and it sends "/W" when you finger://host/foo.21:41
jeblairmordred: i'm not sure that helps us?21:41
mordredhrm21:41
jeblairwhat does "/W" mean?21:42
jeblairhttps://tools.ietf.org/html/rfc1288#section-2.5.421:43
jeblairaha21:43
jeblairmordred: that makes me think that 'links' supports only foo@host, and sends "/W foo" as the query, meaning additional verbosity.21:43
jeblairfungi: you may want in on this bikeshed21:44
fungimmm21:50
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add a success-url for status.json test  https://review.openstack.org/47360421:52
fungiso was /resource in a ietf draft then, or is there an accepted numbered rfc?21:54
mordredfungi: just a draft21:55
fungii've seen so many (sometimes directly conflicting!) drafts about extending other protocols i tend not to give them much weight21:55
mordredhttps://tools.ietf.org/html/draft-ietf-uri-url-finger-0321:55
mordredfungi: I believe that's the only thing we've found that defines this at all21:55
fungikeeping in mind that even rfcs are not necessarily "standards" in the strictest sense21:55
mordredfungi, jeblair: also: http://lynx.browser.org/lynx2.8.8/lynx_help/lynx_url_support.html#finger_url21:56
fungidraft-ietf-uri-url-finger-03 expired more than 20 years ago without gaining consensus21:57
mordredso if we emit as resource@host, we'll work with both links and lynx - if we emit as host/resource we'll be consistent with an expired non-adopted rfc21:57
fungiyup. in the ensuing 20 years, consensus emerged on its own in my opinion21:58
mordredfungi: there is an o'reilly HTTP book that lists the host/resource form:21:59
mordredhttps://books.google.com/books?id=qEoOl9bcV_cC&pg=PT518&lpg=PT518&dq=rfc+finger+url&source=bl&ots=zxuYVpNzbj&sig=S7x_lyrd-Fg1tfwcu_9Sn1vqswE&hl=en&sa=X&ved=0ahUKEwiG4N_JprnUAhXDz4MKHc64DFsQ6AEIUzAI#v=onepage&q=rfc%20finger%20url&f=false21:59
fungi(even though finger != http)21:59
mordredyah21:59
* mordred is mostly trolling to see what, if anything, we might reasonably break if we choose one over the other22:00
fungilooks like rfc 1738 is the reason why they didn't go with user@host22:01
fungiooh, meeting time22:01
jeblairzuul meeting time in #openstack-meeting-alt22:01
mordredfungi: http://tidbits.com/article/1632 says that Peter's MacTCP based finger client supports finger://resource@ format directly22:02
jeblairjlk: are you around for the zuul meeting?22:03
*** harlowja has joined #zuul22:06
*** yolanda has joined #zuul22:34
Shrewsmordred: so, i that check for py35 in that streaming test is unintentionally left in. I meant it for a future test of the websocket stuff. There's actually nothing py3 specific there23:02
tristanCpython3 is actually not really an issue on centos... but how about nodepoolv3, can it run py3 too?23:02
clarkbya use software collections23:04
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add log streaming test  https://review.openstack.org/47107923:04
pabelangerclarkb: from emails I have seen for Red hat, that is not an option.23:04
Shrewsmordred: ^^^ just corrected that23:04
pabelangerit is missing a lot of python dependencies23:04
clarkbpabelanger: you mean system packages for python deps?23:05
jamielennoxcan someone tell me if i really must run zuul-executor as root? i know it drops privs but is the only reason so that it can get the finger port?23:07
pabelangerclarkb: right. If I understand the base python3-devel packages is that but only python packages related to django (I think) have actually been packaged as RPMs.  I would expect pip install to work, but obviously red hat like RPMs23:07
pabelangerjamielennox: right, finger port is the only reason IIRC23:07
jamielennoxi don't really plan on exposing 79 directly anyway so if that's the only problem i can skip that23:08
pabelangeryes, should be. I haven't tested it yet23:08
jlkjeblair: sorry no my kid had a school event.23:11
jlkCould I get some reviews of https://review.openstack.org/#/c/472468/ ?23:20
*** dkranz has quit IRC23:30

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