Wednesday, 2018-10-10

*** rlandy is now known as rlandy|bbl00:01
*** ianychoi has joined #zuul00:31
dmsimardI don't want to get into the implementation details but TripleO is doing some pretty cool things with ara.. they're exporting data from ara to influxdb and then they have graphs for things that interest them. I wonder what it would take to do this kind of thing at scale in Zuul.01:14
*** ianychoi has quit IRC01:16
dmsimardHost and task granular metrics about all tasks in every jobs ?01:16
*** ianychoi has joined #zuul01:16
dmsimardIn case you're curious what it looks like, it's open source :D https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/collect-logs/library/ara_influxdb.py01:17
dmsimardhttp://38.145.35.97/d/poOr-d0mk/ansible-exploration?orgId=101:17
tristanCit seems like ansible/awx deleted a tag, and zuul-executor are now unable to start a job because of https://ansible.softwarefactory-project.io/paste/show/21/01:27
tristanCaccording to zuul/merger/merger.py it seems like the only solution is to restart merger and executors?01:29
tristanCwell, closing and re-opening the PR seems to also be a solution01:32
*** openstackgerrit has quit IRC01:37
*** tristanC has quit IRC01:37
*** mugsie has quit IRC01:37
*** dkehn has quit IRC01:37
*** logan- has quit IRC01:37
*** tflink has quit IRC01:37
*** odyssey4me has quit IRC01:37
*** dmellado has quit IRC01:37
*** rlandy|bbl has quit IRC01:37
*** D0han has quit IRC01:37
*** Diabelko has quit IRC01:37
*** jhesketh has quit IRC01:37
*** che-arne has quit IRC01:37
*** gundalow has quit IRC01:37
*** eumel8 has quit IRC01:37
*** maxamillion has quit IRC01:37
*** snapiri has quit IRC01:37
*** jiapei has quit IRC01:37
*** AJaeger has quit IRC01:37
*** spsurya has quit IRC01:37
*** sdake has quit IRC01:37
*** clarkb has quit IRC01:37
*** snk has quit IRC01:37
*** sdoran has quit IRC01:37
*** mgagne has quit IRC01:37
*** jimi|ansible has quit IRC01:37
*** smyers has quit IRC01:37
*** persia has quit IRC01:37
*** gouthamr has quit IRC01:37
*** ssbarnea_ has quit IRC01:37
*** Shrews has quit IRC01:37
*** pleia2 has quit IRC01:37
*** corvus has quit IRC01:37
*** jamielennox has quit IRC01:37
*** sshnaidm|afk has quit IRC01:37
*** jpena|off has quit IRC01:37
*** _ari_ has quit IRC01:37
*** hogepodge has quit IRC01:37
*** jbryce has quit IRC01:37
*** kmalloc has quit IRC01:37
*** mrhillsman has quit IRC01:37
*** cmurphy has quit IRC01:37
*** EmilienM has quit IRC01:37
*** fdegir has quit IRC01:37
*** mattclay has quit IRC01:37
*** panda has quit IRC01:37
*** SpamapS has quit IRC01:37
*** pabelanger has quit IRC01:37
*** jlk has quit IRC01:37
*** eventingmonkey has quit IRC01:37
*** lennyb has quit IRC01:37
*** adam_g has quit IRC01:37
*** bramwelt has quit IRC01:37
*** samccann has quit IRC01:37
*** fungi has quit IRC01:37
*** ttx has quit IRC01:37
*** timrc has quit IRC01:37
*** dcastellani has quit IRC01:37
*** bstinson has quit IRC01:37
*** gothicmindfood has quit IRC01:37
*** mnaser has quit IRC01:37
*** TheJulia has quit IRC01:37
*** mordred has quit IRC01:37
*** tobiash has quit IRC01:37
*** fbo has quit IRC01:37
*** swest has quit IRC01:37
*** rcarrillocruz has quit IRC01:37
*** evrardjp has quit IRC01:37
*** ssbarnea has quit IRC01:37
*** mmedvede has quit IRC01:37
*** anticw has quit IRC01:37
*** timburke has quit IRC01:37
*** ianychoi has quit IRC01:37
*** quiquell|off has quit IRC01:37
*** dmsimard has quit IRC01:37
*** zigo has quit IRC01:37
*** leifmadsen has quit IRC01:37
*** mhu has quit IRC01:37
*** j^2 has quit IRC01:37
*** jesusaur has quit IRC01:37
*** chandankumar has quit IRC01:37
*** ianw has quit IRC01:37
*** jlvillal has quit IRC01:37
*** aluria has quit IRC01:37
*** mestery has quit IRC01:37
*** andreaf has quit IRC01:37
*** robcresswell has quit IRC01:37
*** SotK has quit IRC01:37
*** ChanServ has quit IRC01:37
*** andreaf has joined #zuul01:43
*** mestery has joined #zuul01:43
*** aluria has joined #zuul01:43
*** jlvillal has joined #zuul01:43
*** ianw has joined #zuul01:43
*** jesusaur has joined #zuul01:43
*** chandankumar has joined #zuul01:43
*** j^2 has joined #zuul01:43
*** odyssey4me has joined #zuul01:43
*** tflink has joined #zuul01:43
*** logan- has joined #zuul01:43
*** dkehn has joined #zuul01:43
*** mugsie has joined #zuul01:43
*** mhu has joined #zuul01:43
*** leifmadsen has joined #zuul01:43
*** dmsimard has joined #zuul01:43
*** zigo has joined #zuul01:43
*** quiquell|off has joined #zuul01:43
*** ianychoi has joined #zuul01:43
*** timburke has joined #zuul01:43
*** mmedvede has joined #zuul01:43
*** ssbarnea has joined #zuul01:43
*** anticw has joined #zuul01:43
*** evrardjp has joined #zuul01:43
*** rcarrillocruz has joined #zuul01:43
*** swest has joined #zuul01:43
*** jimi|ansible has joined #zuul01:44
*** smyers has joined #zuul01:44
*** persia has joined #zuul01:44
*** samccann has joined #zuul01:44
*** fungi has joined #zuul01:44
*** ttx has joined #zuul01:44
*** gouthamr has joined #zuul01:44
*** ssbarnea_ has joined #zuul01:44
*** Shrews has joined #zuul01:44
*** corvus has joined #zuul01:44
*** pleia2 has joined #zuul01:44
*** jamielennox has joined #zuul01:44
*** openstackgerrit has joined #zuul01:45
*** robcresswell has joined #zuul01:45
*** SotK has joined #zuul01:45
*** sshnaidm|afk has joined #zuul01:45
*** mrhillsman has joined #zuul01:45
*** _ari_ has joined #zuul01:45
*** jpena|off has joined #zuul01:45
*** hogepodge has joined #zuul01:45
*** jbryce has joined #zuul01:45
*** kmalloc has joined #zuul01:45
*** cmurphy has joined #zuul01:45
*** EmilienM has joined #zuul01:45
*** fdegir has joined #zuul01:45
*** mattclay has joined #zuul01:45
*** che-arne has joined #zuul01:45
*** eumel8 has joined #zuul01:45
*** maxamillion has joined #zuul01:45
*** gundalow has joined #zuul01:45
*** dmellado has joined #zuul01:46
*** rlandy|bbl has joined #zuul01:46
*** D0han has joined #zuul01:46
*** Diabelko has joined #zuul01:46
*** jhesketh has joined #zuul01:46
*** gothicmindfood has joined #zuul01:46
*** bstinson has joined #zuul01:46
*** mnaser has joined #zuul01:46
*** TheJulia has joined #zuul01:46
*** mordred has joined #zuul01:46
*** dcastellani has joined #zuul01:46
*** timrc has joined #zuul01:46
*** panda has joined #zuul01:46
*** adam_g has joined #zuul01:46
*** pabelanger has joined #zuul01:46
*** SpamapS has joined #zuul01:46
*** jlk has joined #zuul01:46
*** eventingmonkey has joined #zuul01:46
*** bramwelt has joined #zuul01:46
*** lennyb has joined #zuul01:46
*** fbo has joined #zuul01:46
*** tobiash has joined #zuul01:46
*** rlandy|bbl has quit IRC01:47
*** ChanServ has joined #zuul01:47
*** card.freenode.net sets mode: +o ChanServ01:47
*** tristanC has joined #zuul01:48
*** mgagne has joined #zuul01:49
*** snapiri has joined #zuul01:49
*** rlandy has joined #zuul01:49
dmsimardpabelanger: what was the name of the fedora packaging test thing that was sort of similar to zuul ? we heard about it sometime thursday02:04
dmsimardhttps://pagure.io/standard-test-roles/ I think02:10
*** rlandy has quit IRC02:21
pabelangerdmsimard: that looks right, I didn't really dig into it02:32
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix multiple builds query parameters for a single column  https://review.openstack.org/59360502:33
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: prevent filter being cleaned on status reload  https://review.openstack.org/60919002:44
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: prevent filter being cleaned on status reload  https://review.openstack.org/60919003:05
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix zuul-build-dashboard homepage setting  https://review.openstack.org/60920003:05
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix support for comma/space separated status filter  https://review.openstack.org/60920103:11
tristanC609190 and 609201 should fix the two reported issues about the new dashboard03:12
dmsimardtristanC: the other one that came up was the hamburger menu that didn't work properly (i.e, on mobile or when resizing the browser window to be very small)03:26
tristanCoh right, let me fix that now03:26
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix hamburger menu collapse  https://review.openstack.org/60920503:47
tristanCdmsimard: there ^03:47
*** bhavikdbavishi has joined #zuul03:58
*** nilashishc has joined #zuul03:59
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix support for comma/space separated status filter  https://review.openstack.org/60920104:02
*** AJaeger has joined #zuul04:25
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861004:30
openstackgerritMerged openstack-infra/zuul master: web: fix zuul-build-dashboard homepage setting  https://review.openstack.org/60920004:37
openstackgerritMerged openstack-infra/zuul master: web: prevent filter being cleaned on status reload  https://review.openstack.org/60919004:38
*** spsurya has joined #zuul04:52
*** quiquell|off is now known as quiquell05:22
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix support for comma/space separated status filter  https://review.openstack.org/60920105:35
tobiashtristanC: what's the filter expected to match?05:41
tobiashtristanC: when I filter for 'nova,neutron' in that change ^ then I also get a tempest item05:42
tobiashdoes it also filter for job names?05:42
tristanCtobiash: it's because that tempest is a in a queue shared by neutron05:44
tobiashah ok05:44
tristanCwell we could change that behavior, but that's how it used to work iiuc05:45
tobiashif it was like that before, it's fine, just wondered05:46
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement a Kubernetes driver  https://review.openstack.org/53555705:47
*** swest has quit IRC05:49
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066705:52
*** bhavikdbavishi1 has joined #zuul06:00
*** bhavikdbavishi has quit IRC06:01
*** bhavikdbavishi1 is now known as bhavikdbavishi06:01
*** quiquell is now known as quiquell|brb06:12
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861006:26
*** pcaruana has joined #zuul06:50
*** quiquell|brb is now known as quiquell06:54
*** odyssey4me has quit IRC07:07
*** odyssey4me has joined #zuul07:08
*** mugsie has quit IRC07:08
*** mgagne has quit IRC07:09
*** logan- has quit IRC07:09
*** tflink has quit IRC07:09
*** mgagne has joined #zuul07:10
*** tflink has joined #zuul07:10
*** jiapei has joined #zuul07:11
*** logan- has joined #zuul07:11
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add install and deploy openshift roles.  https://review.openstack.org/60861007:13
*** panda has quit IRC07:30
*** panda has joined #zuul07:32
*** electrofelix has joined #zuul07:33
*** mgagne has quit IRC07:34
*** mgagne has joined #zuul07:36
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066707:55
*** swest has joined #zuul07:59
*** swest has quit IRC08:05
*** nilashishc_ has joined #zuul08:13
*** sshnaidm|afk is now known as sshnaidm08:22
*** swest has joined #zuul08:22
*** logan- has quit IRC08:23
*** logan- has joined #zuul08:27
*** rcarrillocruz has quit IRC08:30
*** swest has quit IRC08:34
*** nilashishc has quit IRC08:45
*** nilashishc_ is now known as nilashishc08:45
*** nilashishc has quit IRC08:47
*** nilashishc has joined #zuul08:48
*** swest has joined #zuul08:51
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066708:53
*** bhavikdbavishi has quit IRC08:54
*** themroc has joined #zuul09:04
*** bhavikdbavishi has joined #zuul09:38
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066709:48
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: expand status panels only when the header is clicked  https://review.openstack.org/60934810:15
openstackgerritMerged openstack-infra/zuul master: web: fix hamburger menu collapse  https://review.openstack.org/60920510:17
*** _KaszpiR_ has joined #zuul10:29
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066710:41
openstackgerritMerged openstack-infra/zuul master: web: fix support for comma/space separated status filter  https://review.openstack.org/60920110:53
*** dkehn has quit IRC10:55
*** jpena|off has quit IRC10:58
*** swest has quit IRC10:59
*** sshnaidm is now known as sshnaidm|afk11:04
quiquellHello looks like running jobs are returning wrong stream url in their json11:10
*** dkehn has joined #zuul11:10
*** dkehn has quit IRC11:15
*** swest has joined #zuul11:22
tobiashquiquell: do you have a link?11:23
*** sshnaidm|afk is now known as sshnaidm11:24
quiquelltobiash: http://zuul.openstack.org/api/status11:25
quiquellstream.html?uuid=e82d0b12b9784cee82cb2ebe1bd44f42&logfile=console.log11:26
quiquelldoes not work11:26
openstackgerritSimon Westphahl proposed openstack-infra/zuul master: Include enqueue and report timestamps in MQTT msg  https://review.openstack.org/60935511:26
quiquellzuul.openstack.org/stream.html?uuid=e82d0b12b9784cee82cb2ebe1bd44f42&logfile=console.log11:26
tobiashtristanC, mordred, corvus: I got the feedback from my users that the fonts in the new web ui are a little bit too small (I also have the impression), would you agree with that?11:26
quiquelltobiash: I think the stream url has change but the API is still composing it wrong11:26
tobiashquiquell: do you know if that changed (I think there was no change to this related to the new web ui)?11:27
quiquelltobiash: Yep just after the new web ui11:27
quiquelltobiash: was working fine before11:27
quiquelltobiash:  I can open a bug for it11:27
tobiashso it's an api problem as the ui is working right?11:28
quiquelltobiash: If I click on the ui it's working fine11:28
tobiashah, the stream url is relative now11:28
quiquelltobiash: It's like this now http://zuul.openstack.org/stream/0f34a011be214e5ba3796694dc6e33d1?logfile=console.log11:28
tobiashquiquell: hrm, I don't see something in the react change that could explain that this changed: https://review.openstack.org/#/c/607479/411:30
tristanCtobiash: i have no opinions related to css ;)11:34
tristanCShrews: here, launcher logs of openshift project and pod creation: http://logs.openstack.org/67/570667/22/check/nodepool-functional-openshift/cb06572/launcher/nodepool/launcher.log11:34
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement an OpenShift resource provider  https://review.openstack.org/57066711:37
tristanCcorvus: would be nice to move on the openshift driver, please let me know what else is needed ^11:37
tristanCcorvus: about adding a zuul/nodepool/zuul-jobs integration test, do you think we could use the new quickstart?11:42
mordredtristanC: I'll see if I can figure it out - but if you look at the status page on mobile, the check box for "expand by default" strangely shifts down to the next line11:52
ShrewstristanC: corvus: neat! I still have concerns that testing with playbooks isn't going to allow for more substantial testing of the driver. I think all that you have is great, except maybe we should replace the small portion where you wait for nodes, show the nodes/pods, with a tox role that runs functional tests11:52
mordredtristanC: I'm jetlagged and my brain doesn't work - but I do think it would be great to have some CI on the quickstart so that we make sure it still works - I think corvus has some thoughts on that11:53
tristanCShrews: you would mind bootstraping a tox env and test class, i'm not sure to understand how you want to do this...11:53
tristanCmordred: about css, i don't really understand how all this stuff work tbh...11:54
tristanCmordred: corvus: i guess the trick is to be able to build the zuul/nodepool image before running the docker-compose, and make sure the quickstart can use speculative content11:55
mordredtristanC: me either :) - but I'll see what I can figure out11:56
mordredquiquell: I just tried a stream from the web and it worked for me - http://zuul.openstack.org/stream/58381873fcab468896a02ce02b1bf5b3?logfile=console.log ... so I agree, the value in the status.json itself is wrong11:57
mordredquiquell: are you using that value from something?11:57
ShrewstristanC: i just mean having your testing playbook include this role (http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/tox/README.rst) which would run a 'tox -ek8s' suite of tests11:58
Shrewswouldn't that give a developer more ways to test the driver?11:59
tristanCShrews: what would be the k8s content of tox.ini?12:00
tristanCmordred: quiquell: yes, the interface is cheating to accomodate with the legacy links returned from status api, now that it is deployed we can fix that12:00
quiquellmordred: Yep, the greasy monky stuff that show you the progress of gerrit12:01
dmsimardThere's some funky rewrite rules too, maybe it's that12:01
dmsimard¯\_(ツ)_/¯12:01
quiquellmordred: it's taking the link of running from the json12:01
tristanCthe cheat logic is: http://git.zuul-ci.org/cgit/zuul/tree/web/src/containers/status/ChangePanel.jsx#n22612:02
quiquelltristanC: Thanks so much, do I have to write a bug or something to track progrress ?12:02
ShrewstristanC: something along the lines of:  stestr --test-path ./nodepool/tests/k8s run12:02
ShrewstristanC: Consider this only a suggestion. You know k8s much better than I and would likely be the lead on fixing any bugs. If you think ansible playbooks give you the flexibility you need, then maybe my suggestion can be ignored.12:04
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix stream url from status json  https://review.openstack.org/60936512:07
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: remove legacy stream.html url support  https://review.openstack.org/60936612:07
tristanCmordred: quiquell: ^ those should make status build url consistent12:08
quiquelltristanC: thanks !12:08
quiquellso fast12:08
tristanCquiquell: it has been quite sometime i refactored that web interface, there may be some more left-over cleanup to do :-)12:09
*** jesusaur has quit IRC12:10
quiquelltristanC: cool12:11
*** quiquell is now known as quiquell|lunch12:11
dmsimardtristanC: great work!12:11
tristanCdmsimard: thanks!12:12
dmsimardI need someone to help me out with the ARA 1.0 interface if you get bored :p12:12
tristanCShrews: shouldn't we need a new BaseTestCase class to setup zk but not start launcher thread, or should we also drop the "command: nodepool-launcher" and run the service from tox?12:13
tristanCShrews: could we start doing that with tox -eopenstack ?12:15
ShrewstristanC: there would have to be a new base class, yes12:15
ShrewstristanC: we could do it for the openstack-driver specific tests, but that would be a lot of work to redo the tests12:16
Shrewsthis is new territory, so i'm not exactly sure what the trade offs are12:17
*** jesusaur has joined #zuul12:17
mordredtristanC, tobiash: first patch looks great- I think we should wait for $time to land the second one, since it would mean someone updating web app without having their scheduler updated would be broken12:18
mordredtristanC, tobiash: so I'm going to drop a -2 on it just so it doesn't accidentally land - but I'm actually +2 on it :)12:18
tobiashmordred: so $time is like 2 days?12:18
ShrewstristanC: but if the new base class is created generically enough, it could be reused for other in-flight drivers. so maybe it could assume that the launcher is already started with the correct driver setup in nodepool.yaml12:19
mordredtobiash: I'm thinking we need to wait until we've cut a new tag12:19
tristanCtobiash: scheduler needs to be restarted though12:19
EmilienMtristanC: good work on http://zuul.openstack.org UI - it's crazy fast, thanks a lot12:20
tobiashmordred: that long? I think with a new tag you should restart all services anyway12:20
tobiashand everyone following master should know what he's doing ;)12:20
mordredso - honestly, landing the second patch isn't as important as the first one - it's just a cleanup -so we could even wait for a few weeks or a month without negative impact - other than forgetting about it :)12:20
tristanCEmilienM: you're welcome, it can still be improved if needed, the change indents is still done globally12:21
tobiashok, I'm just concerned about the latter ;)12:21
mordredtobiash: indeed - but it's fairly safe to run completely CD for the web app and still be careful about scheduler restarts12:21
mordredtobiash: ++12:21
mordredtobiash: maybe we should make a topic we use for things like this - like 'merge-after-release'12:21
tobiashmordred: ok, from that perspective fine so let's wait until the next tag12:21
mordredtobiash: and then when we cut tags we can go look at anything we've marked?12:21
tobiashthat's a great idea12:22
mordredk. I updated the topic12:22
tobiashmaybe add a zuul job in the release pipeline that sends a notification about this ;)12:22
ShrewstristanC: I wouldn't change what you have yet though. Let's get input from corvus first.12:24
Shrewsi mean, the openstack functional tests don't do more than what you already have, so maybe that's enough  :)12:25
tristanCShrews: I still think the ultimate test is to run zuul/nodepool/zuul-jobs, and to do that, it seems easier to do go with ansible12:26
Shrewsnow that i think about it, the tox tests are more about testing the launcher code itself12:26
tristanCShrews: ftr, here is the sf-ci test for openshift integration: https://softwarefactory-project.io/cgit/software-factory/sf-ci/tree/health-check/zuul-openshift.yaml12:27
ShrewstristanC: that's fine. i defer to your expertise here  :)12:28
tristanCimo, we should make that playbook work with the quickstart deployment12:28
*** bhavikdbavishi has quit IRC12:30
*** quiquell|lunch is now known as quiquell12:30
tristanCShrews: well there is value to use tox/python client to test the code, it maybe easier to do fault-injection12:30
tristanCbut i would be more confortable if there is a test that demonstrate a zuul-job can run openshift as well as one that build an image and test it too.12:31
tristanCand now that there will be a gerrit deployment process in quickstart doc, it doesn't seems overly complicated to do that12:32
tristanCbut i'll defer to corvus regarding to what is expected/needed to get that driver moving :)12:33
Shrewsmaybe we need both? maybe create a FakeKubernetesDriver for the tox tests12:33
Shrewsand just piggy back on top of the py35 tox env12:35
*** rlandy has joined #zuul12:39
*** bhavikdbavishi has joined #zuul12:41
*** bhavikdbavishi has quit IRC12:41
*** bhavikdbavishi1 has joined #zuul12:41
*** bhavikdbavishi1 has quit IRC12:46
mordredtristanC, Shrews: it also might make sense to make another deployment similar to the quickstart but more tuned for being usable for testing features - for feature testing we might need/want a different set of presets that would make the quickstart more complex12:54
mordredbut I'm also just saying random words12:54
Shrewscorvus: i didn't give https://review.openstack.org/608344 a second run through, but the new contents lgtm so +2'd. Didn't approve in case someone else wants to give this version a try13:07
*** swest has quit IRC13:17
*** quiquell is now known as quiquell|off14:14
*** che-arne has quit IRC14:18
Shrewshttps://review.openstack.org/608700   <-- enable py36 testing on nodepool... can haz reevuuu?14:21
tristanChttps://review.openstack.org/593605  <-- multi filters on build page can haz review too?14:25
*** SotK has quit IRC14:27
mordredShrews, tristanC: +2 from me14:28
*** clarkb has joined #zuul14:42
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Reorganize admin manual  https://review.openstack.org/60943214:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-website master: Switch the "Get Started" button to quick-start  https://review.openstack.org/60943414:46
*** nilashishc has quit IRC14:48
*** nilashishc has joined #zuul14:48
corvusShrews, tobiash, mordred, clarkb, tristanC, j^2: https://review.openstack.org/#/q/topic:zuul-quickstart  has 3 changes which i think are ready to review/land.14:48
corvusthe build output from 609432 should show the admin manual in a coherent state14:49
corvustristanC, Shrews: do i understand correctly that earlier you were discussing something like using the docker-compose file to set up a system for functional testing that would replace part of what is in 605803 (the nodepool k8s functional test change)?14:53
*** chandankumar is now known as chkumar|off14:55
Shrewscorvus: no. i think mordred suggested that as something to ponder15:06
clarkbI think that would work fine for the existing tests fwiw15:07
clarkbthough we might want some way of disabling subsets of services (like does nodepool functional testing need a gerrit or even a zuul?)15:07
Shrewsi think we just need a consensus on what type of testing is required for new drivers15:07
Shrewsis what tristanC has in his ansible playbooks enough? or do we also want deeper, unit testing via tox? or both?15:08
Shrewsor the 3rd thing15:08
clarkbShrews: I think for many drivers we won't be able to do functional testing because it isn't practical to require we have working azure credentials for example15:09
clarkbShrews: that probably means unit testing via tox is a minimum we can rely on using faked services15:09
clarkbthen if we can functionally test it do our best within reason (openstack, k8s, maybe a generic container driver if that happens)15:10
*** bhavikdbavishi has joined #zuul15:11
*** panda has quit IRC15:13
*** panda has joined #zuul15:14
clarkbI do think the functional testing that was added way back when for openstack helped significantly to ensure both the driver and nodepool were workign as expected15:14
clarkbso having as much functional testing as possible is a win imo15:15
corvusShrews, tristanC: i think the functional testing needs to happen with tox.  it's hard to simulate the full lifecycle of a request with just ansible and min-ready.  i think we can use the playbooks/roles in 605803 to do the setup, but then we should run 'tox -e functional_k8s' to run tests which submit node requests, and return nodes, so that we can test deletion too.15:24
*** SotK has joined #zuul15:25
*** techraving has joined #zuul15:28
Shrewscorvus: that's sort of what i was pushing for15:33
Shrewss/sort of/pretty much exactly/15:33
Shrewsi'll try to play around with the BaseTestCase class to see if I can come up with something generic tristanC can use15:34
*** bhavikdbavishi1 has joined #zuul15:41
*** bhavikdbavishi1 has quit IRC15:41
*** bhavikdbavishi has quit IRC15:42
*** themroc has quit IRC15:48
*** bhavikdbavishi has joined #zuul15:50
*** sshnaidm has quit IRC15:58
*** sshnaidm has joined #zuul15:59
*** caphrim007_ has joined #zuul16:00
*** techraving has quit IRC16:25
clarkbcorvus: or maybe even tox -e functional and depending on the setup you get k8s or openstack or $otherthing16:34
clarkbbut maybe you need enough job specific setup that there needs to be different envs16:34
corvusclarkb: yeah, i'm thinking there may be enough variations within a driver that just one label might not be enough for testing.  in other words, the functional tests for each driver may need a unique set of labels and things to test.  especially if nodepool grows more complexity.16:36
*** bhavikdbavishi has quit IRC16:36
clarkbcorvus: brainstorming topic: talked to tripleo folks a bit this morning about how to communicate and work together with openstack infra better. One of the topics that came up was Zuul isn't always very clear on why it took actions (or didn't take action). We might want to prioritize stuff like user feedback (cycle detection reporting for example) in the near future?16:37
clarkbI think that fits into the get bootstrapped and running work you are doing as it is in the name of user experience16:37
corvusclarkb: any examples other than cycle reporting?16:39
clarkbcorvus: when the gate resets we've seen a lot of confusion around why jobs are restarting that have already passed (it is because zuul has a new future state and the old one is invalid)16:41
clarkbcorvus: I'm not sure how to communicate that through the dashboard but that was another one16:41
clarkbanother is when changes are inactive due to being outside of the window16:41
corvusclarkb: hrm, those last two sound less like a zuul ui problem and more like some people don't understand what zuul is doing.  i'm not sure there's a tweak we can make to the status page that can actually explain the theory behind gating.  perhaps we can suggest that users who wish to understand what zuul is doing should read https://zuul-ci.org/docs/zuul/user/gating.html ?16:45
clarkbcorvus: ya one idea was to make links to how gating works more conspicuous in the UI16:46
clarkbnot necessarily solve that problem directly, but have appropriate breadcrumbs to the docs16:46
corvusthat's a good idea... i don't think there are any links to the docs in the web ui now :)16:47
chkumar|offclarkb: corvus Hello16:47
corvusoh, er, i stand corrected, there is now that the new dashboard merged :)16:47
clarkbcorvus: oh neat16:47
chkumar|offclarkb: corvus I was in PyCon India 2018 last week talking about zuul16:48
chkumar|offthey basically like zuul depends on feature when I was talking with people16:48
corvuschkumar|off: thanks!  that's great to hear :)16:49
chkumar|offbut on doc side, they find it is very hard to understand like how it is different from jenkins16:49
chkumar|offlike a feature comparison page with various CI tools would be great to have16:49
corvuschkumar|off: yeah, people at ansiblefest were asking similar things16:50
corvusconsidering that there are no other project gating systems, it can be tricky to do a comparison.  :)16:50
chkumar|offcorvus: it would be great if we get a something quickstart like stuff which can be easily installable and ready to use for demo purpose16:51
corvuschkumar|off: we should have one within a few hours i think:  https://review.openstack.org/60834416:51
chkumar|offjust running a single shell script or one or two command everything will be ready16:51
corvuschkumar|off: yep, that's what that does -- it does it with docker, and you can have a full system with 'docker-compose up'16:52
chkumar|offcorvus: I will try and let you know :-)16:52
corvuschkumar|off: you can see the doc preview rendered here: http://logs.openstack.org/44/608344/13/check/tox-docs/931664e/html/admin/tutorial.html16:53
corvusclarkb: did you want to look at that, or should we go ahead and +W it?16:53
clarkbcorvus: I'm ok with yall +W'ing it. I still plan to run it and see how it goes for me and can provide followup changes or feedback if necessary16:53
chkumar|offcorvus: can we change this tutorial with github as people are not much fan of gerrit?16:54
clarkbI'm dealing with post conference administrivia for multiple conferences right now so want to get that done (so I can get paid for expenses :) )16:54
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Reorganize admin manual  https://review.openstack.org/60943216:54
corvuschkumar|off: no -- there is no way to install a copy of github in a container since it's not free software.16:54
chkumar|offcorvus: hehe, may be we need some one to write integration for gitlab then which will deploy gitlab ce and do the integration :-)16:55
corvuschkumar|off: that would be an option.  someone at ansiblefest volunteered to write a gitlab driver; hopefully they will, and once that's done we could do the same with gitlab.16:56
chkumar|offcorvus: great :-)16:56
corvuschkumar|off: but as the docs say -- the idea is to teach folks about zuul -- the concepts apply equally to github16:56
corvuschkumar|off: and if we want, we can extend the tutorial for how to connect to github (you can still use the same docker-compose file and modify zuul.conf -- the config files are bind-mounted into the containers)16:57
corvuschkumar|off: the main thing is that i wanted something completely self-contained where someone can get started quickly.16:59
clarkbcorvus: looking at the new ui maybe link to gating docs in the gate pipeline description? I think that is actually configuration right? I'll push that change up now16:59
corvusclarkb: yeah... i'm not sure if we can do html in that though16:59
chkumar|offcorvus: I will try the tutorail tomorrow and have the feedback :-)16:59
corvuschkumar|off: great, thanks!  we might merge the change before then, so just let us know in here if you have comments after it merges.17:00
clarkbcorvus: https://review.openstack.org/609497 something like that maybe17:03
corvusclarkb: yeah, i'm not sure what we need to do to make it a hyperlink though17:10
clarkbya that will had to be edited int he context of the surrounding html? maybe an href would just work (tm) though?17:11
corvusi'd try it in my sandbox, but i don't think the web stuff is working in the container images yet17:11
clarkbI was going to say maybe that is more motivation to run the sandbox sooner than later :P17:12
corvuslet me double check that17:12
corvusyeah, localhost:9000 is still 404 on /17:15
corvustristanC, Shrews, mordred: ^ if one of you has a chance to look at the current status of javascript in the container images, that would be great :)17:15
clarkbdid shrews change for the hook merge?17:15
SpamapSoff topic: I'm in search of laptop recommendations. Any suggestions are appreciated.17:16
clarkbSpamapS: I like the modern lenovo x200 series. The latest one isn't super happy with linux though so might have to go to previous gen (x270 iirc). There are also the x210 and x330 lcdfans fabricobbled older but new thinkpads17:17
corvuscause right now, the container tutorial curiously omits any mention that there is a web interface :(17:18
SpamapSclarkb: no offense, but that.. just added confusion. thanks? ;)17:25
clarkbSpamapS: there is at least one person that takes old thinkpads and puts modern hardware in them so that you can have old school keyboard with new cpu and stuff17:28
clarkbotherwise if you find the keyboard acceptable on modern thinkpads I would get an x270 myself17:28
pabelangerSpamapS: so far X1 carbon has been nice, made the switch 6 weeks ago17:30
pabelangerusing fedora-28, only finger scanner seems to no work17:31
SpamapSclarkb: ahh17:31
SpamapSpabelanger: don't want thin or big. I like the form factor I had with my x260... I'd prefer the keyboard of the x220 tho. ;)17:31
pabelangerack17:32
openstackgerritMerged openstack-infra/nodepool master: Add tox-py36 job  https://review.openstack.org/60870017:38
SpamapSpabelanger: looking closer at the X1 now.. 3 recommendations so far. ;)17:55
*** pcaruana has quit IRC17:55
pabelangernice17:55
dmsimardSpamapS: I have a t480s which has basically the same specs as the x1 but it has pci-e nvme instead of ssd and has like one more usb port or something :p17:56
dmsimardIf you can, get the high res display option17:56
ShrewsI chose the X1 for my work laptop replacement, but I haven't received it yet17:58
clarkbmy issue with the x1 is battery life. the x200 series has much better battery life (in part because the screen has fewer pixels)18:01
*** techraving has joined #zuul18:02
SpamapSYeah the x260 that I had (or was it x250?) had the external bump battery and lasted like 9 - 10 hours for non-intensive stuff18:10
*** pcaruana has joined #zuul18:12
*** panda has quit IRC18:20
*** panda has joined #zuul18:23
*** techraving has quit IRC18:27
*** electrofelix has quit IRC18:28
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951418:32
corvusShrews, mordred, tristanC, clarkb: ^ that job is a bit of a milestone.  :)18:33
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add tox functional testing for drivers  https://review.openstack.org/60951518:34
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951418:34
ShrewsI have no idea if something like 609515 will work, btw. Just seeing what happens when it runs18:35
corvusnow we need to figure out how to build and use docker images from the change under test18:35
corvusShrews: looks plausible :)18:35
Shrewsi don't think much of our base test classes (if anything) needs to change18:36
Shrewsmaybe just add some new waitForTHING() calls18:36
Shrewscorvus: oh, that's neat18:38
Shrewscorvus: next we'll have zuul coding it's own bug fixes18:38
corvusShrews: i really don't want the quick-start to break :)18:39
corvusthe re-organized admin guide is at http://logs.openstack.org/32/609432/2/check/tox-docs/c8dd910/html/admin/index.html18:39
Shrewstricky part will be keeping the doc and playbook in sync18:39
corvusShrews: yep.  i didn't think auto-extracting commands would work.  however, since most of the content is inlined files, just copying the files and committing them gets us a lot of functional testing.18:40
Shrewswe could drop the nodepool-zuul-functional test (or replace it) with that18:43
tobiashtristanC, mordred: with the new web ui I get xss problems with our authentication provider (saml based) which works with redirects18:56
*** caphrim007_ has quit IRC18:57
clarkbtobiash: this is authentication to the zuul ui loading external resources?18:57
tobiashwhen the index.html is in the cache18:57
tobiashyes18:57
clarkbin that case you probably need to set CORS rules that allow your external resources. I doubt we make that configurable in zuul today though18:57
tobiashclarkb: our zuul api routes set the cors header18:58
tobiashbut maybe not the static stuff18:58
clarkbtobiash: for openstack I see access control allow origin * for the cherrypy handled requests19:00
clarkbtobiash: but not for the js and css files. I wonder if that is the problem19:00
tobiashit fails when downloading the service-worker.js19:02
tobiashI'll try to exclude that from authentication19:02
*** pcaruana has quit IRC19:03
clarkbtobiash: or set the CORS headers in your proxy too?19:05
tobiashI tried that, but that seems to fail within a redirect chain in the auth provider :/19:05
*** ssbarnea has quit IRC19:29
*** pcaruana has joined #zuul19:55
*** pcaruana has quit IRC20:06
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add tox functional testing for drivers  https://review.openstack.org/60951520:06
corvustobiash: maybe you can add a cors header here: http://git.zuul-ci.org/cgit/zuul/tree/zuul/web/__init__.py#n455  ?20:17
tobiashcorvus: that doesn't work (tried to inject cors header to everything in the proxy)20:18
tobiashwhat gets blocked is a redirect of a redirect within the other domain (which doesn't send cors headers)20:18
tobiashwhat I'm trying now is to enforce that index.html is never loaded from disk as the redirect is triggered on the first network call20:19
tobiashbut cache headers don't work because the request for index.html is serviced by the service worker (didn't know yet that something like that exists)20:20
tobiashso my next try is to short-circuit the registration of the service worker: https://git.zuul-ci.org/cgit/zuul/tree/web/src/registerServiceWorker.js#n3320:21
tobiashthat will hopefully force index.html to be the first network call which gets redirected (and should work because it's no xss then)20:22
corvusShrews: would you mind re-adding your +2 to https://review.openstack.org/609432 ?  (i missed a git add earlier)20:27
clarkbcorvus: I'm working through the docker compose doc and there is a missing step to add yourself to the docker group or run docker compose with sudo20:30
* clarkb uses sudo because throwaway VM20:31
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951420:33
pabelangerclarkb: there is a pretty large warning about doing that in documentation: https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user we should add the same warning, if we do that20:34
clarkbcorvus: my only other comment so far is making a new image just to run ansible seems like overkill? but maybe I like bash more than others20:34
clarkbpabelanger: I'd be fine with just adding sudo to the command in the doc too20:34
clarkbpabelanger: it works either way20:34
corvusclarkb: yeah, we should add a step like that.  i assume the quick-start job i'm writing is about to run into that.20:35
clarkbpabelanger: just pointing out we don't document that step (either way)20:35
corvusclarkb: re ansible, you mean for gerritconfig?20:35
clarkbcorvus: ya the setup playbook appears to be stuff that simple shell script could do then you don't need another image20:35
clarkbssh keygen and file copies and such20:35
pabelangerclarkb: ack20:35
corvusclarkb: the uri module in ansible is *life changing*.  take a closer look at the setup playbook.  i think writing that kind of thing in ansible is amazing.20:36
tobiashcorvus, tristanC: disabling the service worker fixed the issue for me ;)20:37
corvusclarkb: i'm especially a fan of the wait_for pattern, but also the bit at the bottom with the user creation rest api.  the yaml->json stuff there is great.20:39
clarkbya some bits would be more verbose in shell for sure. Just wondering if building an image just for that is worth it? I guess if it makes it easier to understand what is happening then probalby (intended to be instructional afterall)20:40
corvusclarkb: anyway, the world actually needs an ansible container image.  but, lacking an upstream image, we should at least be re-using the centos image that gerrit is based off of, so the build shouldn't take long...20:40
corvusclarkb: if it is taking too long, maybe we should look into that20:41
clarkbin theory its only long the first time too20:41
clarkbunless your VM had a tiny disk to start and you had to start over then its the first two times >_>20:42
corvusyep.  oh, i guess it's possible the ansible image is being created first, in which case the time would be allocated to it rather than gerrit...20:42
corvusand gerrit is more specific in version numbers, so if that happens we might end up with two different centos images20:42
corvusmaybe we should see if we can use the ubuntu image instead20:43
corvus(which would be shared with the 'node' image)20:43
pabelangerif we are building on alphine for zuul, couldn't we also put ansible on that version and share the layer?20:44
corvusyes alpine would work too20:44
pabelangerI think the ubuntu idea too20:44
pabelangererr20:44
pabelangerI think the ubuntu idea is great too20:44
corvusi'll try alpine real quick20:46
clarkboh and something I think mordred pointed out is each RUN entry gives you a new layer (which may or may not be desireable) I think figuring that stuff out now is probably the wrong order of operations though. Get it working reliably an dthen worry about too many layers later20:46
pabelangerI think our 2 step build process helps cut down on a lot of waste also20:48
corvusyes i tried to use && liberally, but can fix cases where i missed that in a followup20:48
clarkbfor the zuul containers themselves yes20:48
corvusoh i know why we picked centos -- it already has all the python stuff installed (because of rpm/yum)20:52
clarkbah right20:52
corvus(still working on alpine, just a bit more trial/error to get all the packages)20:53
clarkbcorvus: gerritconfig_1  | fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/usr/sbin/udevadm info --query property --name /dev/vda1", "msg": "Timer expired after 10 seconds", "rc": 257}20:55
clarkbthis happened when gathering facts20:55
clarkbthis prevented setup.yaml from running20:55
clarkbI think we may not need to gather facts in that playbook. But I wonder if that is a side effect of running ansible in a container?20:55
corvusweird... i have not run into that20:56
clarkbI'm running on ubuntu xenial because I had a VM available to run on that platform20:56
corvusso am i, because i haven't upgraded yet20:56
corvusclarkb: can you 'docker exec' into that container and try that out?20:57
clarkbhrm which says its /sbin/udevadm not /usr/sbin/udevadm20:58
clarkboh irght its in a container derp20:58
corvus(i destroyed all my containers for the alpine thing so it's not easy for me right now)20:58
clarkbI stopped docker-compose but I should be able to rerun it? /me tries20:58
corvusyeah, the whole process should be idempotent (at least if it works), so you can keep stopping/starting the same containers20:59
clarkblooks like it happened again on another compose up so at least it is consistnet. Going to test directly now21:00
corvusoh, since it's gerritconfig, it's going to exit, so you may need to restart it with a command or something21:00
clarkbya I'm going to use docker run to run commands on the same image21:01
clarkbok there is no such device node when run directly. I'm guessing because I am not attaching the docker volumes /me will start the existing containerwith a different command21:03
clarkbok I think that started it without volumes attached and then it worked?21:08
corvusclarkb: i changed the command in the compose file to "/bin/bash -c 'sleep 99999999999'" and then did 'docker exec /bin/bash' and i see the volumes but i don't see any devices like that21:10
clarkbcorvus: ya my volumes have content in them implying they were present when the setup.yaml actually ran21:11
clarkbbut I too saw no such volumes when manually execing into it21:11
clarkbthe host node has a /dev/vda121:12
clarkbI wonder if the container is leaking somehow with ansible fact gathering21:12
corvusthat's a really reassuring thought21:12
clarkbcorvus: running `sudo docker run examples_gerritconfig ansible localhost -m setup` shows a vda device (but returns relatively quickly) that does not show up if you change the command to ls -l /dev21:16
corvusi'll try that21:16
corvusclarkb: i see my host system devices there21:17
clarkbcorvus: ya, this is kind of trippy21:18
clarkbkernel says "nothing to see here" if you ls /dev, but ansible fact gathering finds it anyway21:18
*** ssbarnea has joined #zuul21:18
clarkbif we don't need facts maybe we start by disabling fact gathering?21:18
clarkbI'm going to delete things and try with playbook updated to not gather facts21:19
corvusclarkb: yeah, want to add 'gather_facts: no' to all the playbooks?21:19
clarkbcorvus: ya I'll do that and test it in a moment21:19
corvusclarkb: you should probably add that to all the playbooks in examples/playbooks/*.yaml21:19
corvusscheduler and executor run similar playbooks before starting services to aid in sequencing21:20
clarkbyup I see them too21:20
clarkbexamples_gerritconfig_1 exited with code 021:24
corvusclarkb: i'll incorporate that into this alpine change21:24
clarkbcorvus: ok21:24
clarkbdefinitely seems happier with that chnage made21:24
clarkbI'll leave review notes in gerrit too just to make sure we don't miss anything21:26
clarkbbut sounds like you are on top of it21:26
corvusclarkb: yeah, i'm doing the alpine image change, gather_facts, and some general tidying of the playbooks21:30
clarkbcorvus: don't forget sudo to run docker-compose too21:30
corvusclarkb: ah yeah.  so just 'sudo docker-compose up' is the only thing we need to change there?21:32
clarkbyup21:32
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Fixes for quick-start playbooks  https://review.openstack.org/60955121:36
corvusclarkb: omnibus fixes ^21:36
corvusclarkb: and yes, i think my zuul job just ran into the sudo issue :)21:37
corvus2018-10-10 20:57:52.850586 | ubuntu-xenial | Couldn't connect to Docker daemon. You might need to install Docker:21:37
clarkbyup thats the error21:38
clarkbI'll pull down the fixes change and rerun it shortly21:39
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951421:40
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Fixes for quick-start playbooks  https://review.openstack.org/60955121:40
clarkbhrm does docker compose not notice when a dockerfile has changed? I guess not21:42
clarkbI cleaned up everything but the images themselves21:42
*** ssbarnea has quit IRC21:45
corvusclarkb: no, i think 'docker-compose build $imagename' is needed if you change an image21:50
clarkbya I went and ran rmi on the images that were built recently and am rerunning21:50
corvusthat works too21:51
clarkbalso volume prune so that the full setup.yaml playbook runs21:51
corvusclarkb: any idea why docker-compose up still failed?  http://logs.openstack.org/51/609551/2/check/zuul-quick-start/61b39f8/ara-report/21:51
corvusclarkb: oh i guess i need to start the docker service?21:52
corvusoh wait i don't see docker itself being installed here: http://logs.openstack.org/51/609551/2/check/zuul-quick-start/61b39f8/ara-report/result/21e7ffab-7579-4a10-a7e9-d757e3c1bf7c/21:52
clarkbcorvus: on debuntu it should start automatically, at least it did for me using the package docker.io on ubuntu21:53
clarkbthe ombibus of fixes seems to work for me21:53
corvusclarkb: did you already have it installed?21:53
corvusit looks like 'sudo apt-get install docker-compose' isn't enough21:53
clarkbcorvus: that is what I did, it pulled in docker.io. Oh you know what I rebooted after package installs becaues I also did a dist-upgrade21:54
clarkbcould be set to start on boot but not after package install21:54
corvusclarkb: but if you look in that last link, it just says docker.io is recommended, not required21:55
clarkbcorvus: oh, by default ubuntu installs recommends but I think our test node images may disable that?21:55
clarkbthat may also explain it :)21:55
corvusooooh21:55
corvusokay, so i guess it's okay to omit that from the text instructions and just add it to the playbook21:55
clarkbyes, though shouldn't hurt to also add it to the text instructions21:56
corvushow do our images disable that?  (i'm wondering if we can/should re-enable that considering what we're trying to test here)21:58
clarkbits an /etc/apt/$file config option iirc /me looks21:58
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951421:58
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Fixes for quick-start playbooks  https://review.openstack.org/60955121:58
clarkbcorvus: /etc/apt/apt.conf.d/95disable-recommends is a file created by the dpkg element in dib that does it22:00
corvusclarkb: so just an rm of that should do it?22:01
clarkbsets APT::Install-Recommends "0"; and Apt::Install-Suggests "0"; my hunch is if you delete that file early in the test it will do what you want22:01
clarkbcorvus: yup may need an apt-get update too?22:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Remove disable-recommends in quick-start test  https://review.openstack.org/60955322:04
corvusclarkb: ^ that's a try without the update22:04
corvusdocker-compose is running in http://zuul.openstack.org/stream/48fde8a0be884622ab46cb0c8fde149c?logfile=console.log22:04
corvusi'm a dolt.  the zuul image has ansible installed, we could just use it.22:05
corvus(well, that will be true at least until we get to the point where zuul is installing ansible internally)22:06
corvusinstalling ansible takes a long time.  maybe it's worth it, and we'll deal with the fallout from that later (maybe by publishing our own ansible images or something)22:07
fungiinstalling via pip?22:07
clarkbfungi: ya it compiles things like paramiko bindings to openssl22:07
fungii see. looks like they only publish an sdist to pypi, no wheels22:08
clarkbya iirc mordred was going to try and track people down to make ansible wheels at ansiblefest22:08
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Quick-start: remove ansible Dockerfile  https://review.openstack.org/60955522:09
corvushopefully we're not using any post-2.5 things22:09
clarkbcorvus: I don't think so at least I didn't see anything that stood out to me22:10
clarkbalso the centos version of ansible is probably older ?22:10
corvusclarkb: we pip installed on the centos image22:10
clarkbah22:10
ShrewsFYI, they are expecting lots of power outages in my area tomorrow due to yet *another* hurricane headed this way. If I don't respond, that would be the reason why22:15
corvusShrews: stay safe!22:19
clarkband dry!22:23
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add a quick-start test job  https://review.openstack.org/60951422:26
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Fixes for quick-start playbooks  https://review.openstack.org/60955122:26
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Remove disable-recommends in quick-start test  https://review.openstack.org/60955322:26
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Quick-start: remove ansible Dockerfile  https://review.openstack.org/60955522:26
corvusclarkb: can you review https://review.openstack.org/609432 ?22:28
corvusit looks like we're ready to land the first cut of the tutorial, but if we can land that with it it'd be great22:28
clarkbya I'll look22:29
clarkbcorvus: we may also want to point https://zuul-ci.org/start at the new quick start stuff22:30
*** rlandy has quit IRC22:33
*** sshnaidm is now known as sshnaidm|afk22:33
clarkbcorvus: one comment on 609432, missed console -> shell conversion. I +2;d it bceause overall pretty minor but will let you decide if you want to approve at that case22:35
clarkbs/at/in/22:36
corvusyeah, i'll get that in a followup, thanks.22:38
corvusclarkb: re /start -- https://review.openstack.org/60943422:38
clarkb+222:39
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add tox functional testing for drivers  https://review.openstack.org/60951522:41
openstackgerritMerged openstack-infra/zuul master: Add docker-compose quickstart example  https://review.openstack.org/60834422:59
openstackgerritMerged openstack-infra/zuul master: Reorganize admin manual  https://review.openstack.org/60943223:06
clarkbcorvus: I approved the /start url because ^ wnt in23:06
clarkbI don't think that should cause any major issues since post has higher priority than gate now23:07
clarkb(so doc publishing should happen first)23:07
openstackgerritMerged openstack-infra/zuul-website master: Switch the "Get Started" button to quick-start  https://review.openstack.org/60943423:09
clarkbcorvus: left some comments on the test addition change. I think I figured out hwy git review is failing23:26
Shrewsq/c 223:42
Shrewsdoh23:42
Shrewscorvus: tristanC: ooh neat. the tox func test "works": http://logs.openstack.org/15/609515/3/check/nodepool-functional-k8s/3720d29/job-output.txt.gz#_2018-10-10_22_54_03_61277723:44
Shrewsby "works", i mean, the test that tests nothing other than stuff starts seems to not fall over dead23:45
clarkbShrews: seems like a good start23:47
Shrewsclarkb: i think so. we could conceivably replace  the tools/check_devstack_plugin.sh script with this23:54

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