Thursday, 2018-05-31

mnasercorvus, clarkb: any easy way to run this stuff locally?00:00
clarkbthere are js dev docs in tree00:03
clarkbbut this quickly gets past my knowlefge set00:03
mnaseri think mordred did some stuff around this, let me dig00:04
mnaserok00:06
mnaser`yarn install` then `npm start`00:06
corvusmnaser: yeah https://zuul-ci.org/docs/zuul/developer/javascript.html00:11
mnaserok i'm doing it in a nice and clean way so that when you enter something and hit 'enter', it'll update the url in an angular-y way00:11
mnaserso we do things The Right Way(tm)00:12
corvusmnaser: also, iirc, you started some work to refactor the status page; i think that got deferred due to the angular structural changes, but i think that runway is clear now if you wanted to resume.  you know, in your copius spare time.  :)00:12
mnasercorvus: yeah i might hack on that sometime00:13
corvusmnaser: "npm run start:openstack" may be helpful for this.  or "npm run start:basic" or the other things mentioned in that doc.00:13
SpamapSthank the flying spaghetti monster that we have somebody who wants to javascript. ;)00:13
corvusi'm looking forward to doing more as things settle down there :)00:14
mnaserok this is a lot more complicated to do cleanly00:27
mnaserbecause the dashboard is semi-angular and semi-jquery00:27
mnaserok i'll get it to work for now but00:30
mnaseryeah some work will be needed to clean it up00:30
openstackgerritMohammed Naser proposed openstack-infra/zuul master: Remove unnecessary injections  https://review.openstack.org/57134100:34
openstackgerritMohammed Naser proposed openstack-infra/zuul master: Enable HTML5 mode and remove hash prefix for status  https://review.openstack.org/57134200:34
mnasercorvus, SpamapS, clarkb: ^ a clean up and a fix :)00:34
mnaserlengthy commit message because i wanted to explain what was going on00:34
clarkb++ tha ks00:36
ilya_mochalovhello here, I quite new to zuul and overall ecosystem. I need to integrate gitlab webhook for my zuul server. I am straggling to find a right steps to follow. before I only work with github. Thanks everyone in advance :)01:01
*** harlowja has quit IRC01:19
*** xinliang has quit IRC01:28
*** portdirect has joined #zuul01:33
*** D3VIATION has joined #zuul01:37
*** xinliang has joined #zuul01:40
*** D3VIATION has quit IRC01:41
openstackgerritBrian Rosmaita proposed openstack-infra/zuul-jobs master: Handle -/_ ambiguity in package names  https://review.openstack.org/57100501:43
*** D3VIATION has joined #zuul02:36
*** xinliang has quit IRC02:53
*** xinliang has joined #zuul02:54
*** xinliang has quit IRC02:54
*** xinliang has joined #zuul02:54
ilya_mochalovohhh...gitlab is not supported currently. Is there are anyone who works on integration?02:57
tristanCilya_mochalov: probably not, at least not in review.openstack.org... perhaps mordred knows more what is the gitlab driver status?03:23
ilya_mochalovmordred: do you know anything about gitlab integration status?03:26
*** ianychoi has quit IRC03:51
*** D3VIATION has quit IRC03:53
*** rlandy|rover|bbl is now known as rlandy|rover04:20
*** rlandy|rover has quit IRC04:20
*** sshnaidm_pto has quit IRC05:28
*** hashar has joined #zuul06:03
*** pcaruana has joined #zuul06:43
tobiashilya_mochalov: afaik no one has been working on gitlab integration yet06:50
tobiashIf you want to try it, the github driver is probably a good starting point for creating a gitlab driver06:52
*** D3VIATION has joined #zuul06:53
*** D3VIATION has quit IRC06:57
ilya_mochalovYeap, I will take a look at github driver07:06
*** ssbarnea_ has joined #zuul07:15
*** ianychoi has joined #zuul07:32
johanssoneilya_mochalov: Ping me if you need any help with a gitlab driver. I would love to have one as well.07:44
*** jpena|off is now known as jpena07:49
ilya_mochalovjohanddone: Alright08:10
ilya_mochalovanyone can help me with status_url... in zuul.conf I have `status_url=http://my_local_ip:9000/status`.. when I run zuul-web it's gives me 404 on request for ip:port/status08:12
ilya_mochalovip:port/api/tenant/quickstart/status works though08:13
*** GonZo2000 has joined #zuul08:17
*** sshnaidm_pto has joined #zuul08:25
*** electrofelix has joined #zuul08:35
*** GonZo2000 has quit IRC08:36
tristanCthe mqtt driver (https://review.openstack.org/535543) has four +2, can somebody +W ?08:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: docs: add Project Testing Interface guide  https://review.openstack.org/57142009:09
*** ttx has quit IRC09:52
*** ttx has joined #zuul10:11
*** ttx has quit IRC10:14
*** ttx has joined #zuul10:14
*** jpena is now known as jpena|lunch11:00
*** ttx has quit IRC11:07
*** ttx has joined #zuul11:08
*** ttx has quit IRC11:34
*** ttx has joined #zuul11:35
*** ttx has quit IRC11:47
*** ttx has joined #zuul11:47
*** ttx has quit IRC11:51
*** ttx has joined #zuul11:51
*** elyezer has quit IRC11:52
*** sshnaidm_pto has quit IRC12:02
*** elyezer has joined #zuul12:23
*** jpena|lunch is now known as jpena12:25
*** rlandy has joined #zuul12:28
*** rlandy is now known as rlandy|rover12:32
*** D3VIATION has joined #zuul12:48
*** Guest46098 is now known as robcresswell13:14
*** hughsaunders has joined #zuul13:15
*** sshnaidm_pto has joined #zuul13:31
*** acozine1 has joined #zuul14:23
*** hughsaunders has quit IRC14:28
*** D3VIATION has quit IRC14:38
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Move SQL web handler to driver  https://review.openstack.org/56802815:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add never_capture test decorator  https://review.openstack.org/56951515:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Replace use of aiohttp with cherrypy  https://review.openstack.org/56795915:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Convert streaming unit test to ws4py and remove aiohttp  https://review.openstack.org/56833515:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Use iterate timeout in streaming tests  https://review.openstack.org/57149815:01
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Use ZuulWebFixture in tests  https://review.openstack.org/57149915:01
corvusi found the problem which was causing the streaming tests to randomly fail; those patches should be good to go now.15:02
corvus(cherrypy re-uses the httpserver if you stop it and start it again, so if a single test runner process ran two zuulweb tests, and one of them listened on 127.0.0.1 and the other listened on :: (dual stack), the second would actually only listen on 127.0.0.1.  i added something to force cherrypy to create a new webserver each time, and i also made all of the zuulweb tests consistent so they all use :: now)15:04
openstackgerritMerged openstack-infra/zuul master: mqtt: add basic reporter  https://review.openstack.org/53554315:13
*** pcaruana has quit IRC15:28
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Move SQL web handler to driver  https://review.openstack.org/56802816:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add never_capture test decorator  https://review.openstack.org/56951516:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Replace use of aiohttp with cherrypy  https://review.openstack.org/56795916:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Convert streaming unit test to ws4py and remove aiohttp  https://review.openstack.org/56833516:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Use iterate timeout in streaming tests  https://review.openstack.org/57149816:10
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Use ZuulWebFixture in tests  https://review.openstack.org/57149916:10
corvusrebase since the mqtt change merged, and a couple fixes to the last 2 patches16:10
*** hughsaunders has joined #zuul16:15
*** jpena is now known as jpena|off16:16
corvusand the stack is all green now; it's ready to go16:44
*** sshnaidm_pto has quit IRC17:08
*** sshnaidm_pto has joined #zuul17:21
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Add driver interface documentation  https://review.openstack.org/57153817:45
pabelangertobiash: are you able to refresh your Dockerfile on nodepool / zuul? I haven't had time to look into pbrx yet and wanted to test docker things locally17:50
*** electrofelix has quit IRC17:54
*** myoung is now known as myoung|lunch17:57
*** electrofelix has joined #zuul17:57
*** electrofelix has quit IRC17:58
tobiashpabelanger: http://paste.openstack.org/show/722456/18:01
tobiashpabelanger: that's my current zuul-base dockerfile18:01
pabelangertobiash: great!18:01
openstackgerritMerged openstack-infra/zuul master: Fix new depends-on format matching for prefixed gerrit ui  https://review.openstack.org/57000618:02
tobiashpabelanger: you need to specify ZUUL_BASE_REVISION and ZUUL_SRC_URL during the build18:03
pabelangertobiash: just export as bash variable? or is it something docker build specific?18:04
tobiashpabelanger: it's docker build specific18:05
pabelangerack, I'll go read up on it now18:05
tobiashbut you also can just add ENV steps in the dockerfile locally18:05
tobiashpabelanger: you should be able to use --build-arg18:06
pabelangerthanks18:06
*** pwhalen has quit IRC18:24
*** pwhalen has joined #zuul18:33
*** ilya_mochalov has quit IRC18:36
*** toabctl has quit IRC19:33
*** myoung|lunch is now known as myoung19:34
*** toabctl has joined #zuul19:36
pabelangerso, trying to get RDOproject working with zuulv3 (under softwarefactory) but for some reason confguration syntax errors don't seem to be reported back to gerrit19:41
pabelangereg: 2018-05-31 18:42:06,645 INFO zuul.Pipeline.rdoproject.org.check: Configuration syntax error in dynamic layout19:41
pabelangerbut looking at debug log, I cannot see why19:42
pabelangerhttp://paste.openstack.org/show/722466/19:42
clarkbpabelanger: do you have the pipeline configured to report failure?19:46
pabelangerclarkb: I do, but I proposed https://review.rdoproject.org/r/#/c/13984/ to copypasta check from openstack-infra19:49
pabelangerfailure-message is missing19:50
*** harlowja has joined #zuul20:01
corvuspabelanger: failure-message shouldn't be required.  it's just to further customize what's already there.20:03
corvuspabelanger: however, it's entirely possible the case of the "verified" vote might be a problem; does reporting work at all?20:04
corvuspabelanger: oh, the reason it wasn't reporting is this:20:04
corvus2018-05-31 18:42:06,646 DEBUG zuul.Pipeline.rdoproject.org.check: Project rdo-jobs not in pipeline <Pipeline check> for change <Change 0x7f716815f0f0 13964,4>20:04
corvuspabelanger: in order for a change to report failure, the project has to be attached to the pipeline.  so you won't see a syntax error on a change which adds the project to the pipeline.20:05
pabelangercorvus: ah, so I am guessing that is why we require system-required template in openstack-infra?20:08
corvuspabelanger: yep, that's part of it20:08
pabelangerokay, that helps20:08
pabelangerthe part that confused me, is the previous patch in the stack has a noop check job, I guess that isn't enough for reporting back an error20:09
pabelangerokay, let me create a merge-check pipeline and systemd-required template and retest20:11
pabelangerthanks20:11
corvuspabelanger: we might be able to change that.  currently zuul falls back on the currently running layout when reporting if a change doesn't produce a valid configuration.  but we might be able to have it walk up the pipeline to find the most recent layout instead.  that's in _reportItem()20:36
pabelangercorvus: Sure, that would be helpful. As only a zuul user on RDO, I couldn't see why my jobs were failing... since I don't have root access to SF. I can try and see if I can patch the function and create a test20:39
*** harlowja has quit IRC21:00
*** sshnaidm_pto has quit IRC21:01
*** hashar has quit IRC21:30
*** ssbarnea_ has quit IRC21:41
*** acozine1 has quit IRC22:00
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Add driver interface documentation  https://review.openstack.org/57153822:11
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Directly link providers and request handlers  https://review.openstack.org/57158422:11
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Create a base Driver class  https://review.openstack.org/57158522:11
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Have Drivers create Providers  https://review.openstack.org/57158622:11
*** harlowja has joined #zuul22:21
*** rlandy|rover is now known as rlandy|rover|bbl23:09
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add container spec  https://review.openstack.org/56013623:18
corvustristanC, clarkb, tobiash, SpamapS, mordred, jhesketh, Shrews: ^ updated23:18
SpamapSmmmmm23:19
SpamapScontainer23:19
SpamapSspec23:19
* SpamapS consumes23:19
corvusi think that addresses the bulk of the comments and what we discussed in person.  i'd say the most notable thing is that it no longer favors openshift first, instead focusing on more generally applicable concepts which should be easier to get an initial implementation out the door, easier to adapt to other container techs, and still doesn't preclude building on them with something like openshift to make it23:20
corvusmore streamlined.23:20
corvusit's also more than probable i missed something from all the feedbacks; if i did, i apologize in advance for asking you to repeat yourself :)23:21
tristanCcorvus: so is the thingpool going to another spec?23:23
tristanCi really like the proposal of SpamapS, and it worked great and this prototype: https://review.openstack.org/#/q/topic:openshift-zuul-build-resource23:23
SpamapStristanC: cool!23:25
corvustristanC: that one still covers "request a k8s namespace", so i guess that's a little bit of thingpool.  i didn't take it any further than that.23:25
corvustristanC: at a really quick glance, that seems pretty compatible with what i wrote and was imagining.  :)23:25
corvusthat's creating a project.  a plain k8s driver would do the same thing but just create a namespace.23:26
corvus(so to try to summarize the spec in <512 chars: part 1 is "give me a container running /bin/sh" and part2 is "give me access to a container orchestration engine")23:29
tristanChum, i fail to see the "request a k8s namespace" part of the spec23:33
corvustristanC: line 17423:34
tristanCgot it, thanks23:35
tristanCthat workflow is really flexible since the core logic can be implemented in the job23:36
tristanCregarding secret sharing from nodepool to zuul, could we make the scheduler create a global key pair?23:37
corvusyeah, i like how we can probably get moving pretty quick on experimenting in-job, and then move things up the stack as we find them useful (eg, the openshift registry)23:37
corvustristanC: zk support encryption, so i think we should just rely on that23:38
corvustristanC: unless you want to make sure it's encrypted at rest?  in which i guess that would work.  it would be one more bit of state the scheduler (and later, multiple schedulers) need to have.  but i guess it's no more overhead than the existing keys for secrets?23:39
tristanCwell it's an extra bonus feature, not really important. I think the service account token are revoked when the project is deleted23:40
clarkbcorvus: you mean zk supports tls over the wire protocol but not on disk right?23:40
tristanCbut i liked the idea, and having a predicable location to fetch the public key would simplify the implementation23:41
corvusclarkb: i know it supports over the wire, i don't know about disk23:43
tristanCbtw, i recorded a video of the proposed openshift-base job in action here: http://www.softwarefactory-project.io/draft/zuul-openshift.html23:44
corvustristanC: in other news, i've been reviewing Shrews changes, and wanted to try to get a big-picture view of the driver api.  i wrote 571538 through 571586 to do help with that.  i think we know enough about dynamic drivers, static, and now containers to better shape the api.  i'm hoping with a few more changes we'll get to something where you can look at the docs and see how you would implement a new driver.23:46
tristanCcorvus: at a quick glance, those looks good to me. let me know when I should rebase my drivers23:47
corvustristanC: i think we're heading toward having the actual driver api be very simple, with most of the complexity of the dynamic drivers handled by a second api that builds on top of it.  after looking at your openshift driver, i imagine that will mostly mean we'll just remove some unused methods, and maybe rename a few things.  :)23:48
corvustristanC: will do.  i'm expecting we'll make a few more changes, then say it's good enough to start landing containers.23:49
clarkbcorvus: the getProviderHandler() and getConfig() et al being the second api?23:49
clarkbor rather the bits they are expected to return I guess23:49
corvusi think the ultimate test is if we all look at the docs and say "yep, that looks obvious" :)23:49
corvusclarkb: i think the second api is a bunch of stuff that the openstacknoderequesthandler does23:50
corvusor rather, the noderequesthandler23:50
corvusi think most of its methods are only needed for dynamic drivers, so i think the next thing to do is separate them out23:53
corvusi'm going to try to send out the status update email on monday, so if folks want to update https://etherpad.openstack.org/p/zuul-update-email  that's be great :)23:57
corvusi'm going to head out for the day now23:58

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