Tuesday, 2018-05-29

*** threestrands has quit IRC02:05
*** threestrands_ has joined #zuul02:05
*** threestrands_ has quit IRC02:05
*** threestrands_ has joined #zuul02:05
*** jhesketh has quit IRC02:37
*** jhesketh has joined #zuul02:37
*** pabelanger has quit IRC02:40
*** pabelanger has joined #zuul02:40
*** yolanda_ has quit IRC02:41
*** lennyb has quit IRC02:41
*** aspiers[m] has quit IRC02:41
*** yolanda_ has joined #zuul02:42
*** lennyb has joined #zuul02:42
*** swest has quit IRC02:44
*** jimi|ansible has quit IRC02:44
*** elyezer has quit IRC02:44
*** spsurya has quit IRC02:44
*** persia has quit IRC02:44
*** dkranz has quit IRC02:44
*** _ari_ has quit IRC02:44
*** myoung has quit IRC02:44
*** spsurya has joined #zuul02:45
*** persia has joined #zuul02:45
*** dkranz has joined #zuul02:45
*** _ari_ has joined #zuul02:45
*** myoung has joined #zuul02:45
*** swest has joined #zuul02:45
*** jimi|ansible has joined #zuul02:45
*** elyezer has joined #zuul02:45
*** jpena|off has quit IRC02:46
*** ssbarnea has quit IRC02:46
*** pwhalen has quit IRC02:46
*** openstackgerrit has quit IRC02:46
*** gouthamr has quit IRC02:46
*** pleia2 has quit IRC02:46
*** jpena|off has joined #zuul02:47
*** ssbarnea has joined #zuul02:47
*** pwhalen has joined #zuul02:48
*** openstackgerrit has joined #zuul02:48
*** gouthamr has joined #zuul02:48
*** pleia2 has joined #zuul02:48
*** mgagne has quit IRC02:50
*** smyers has quit IRC02:50
*** bstinson has quit IRC02:50
*** jesusaur has quit IRC02:50
*** dtruong has quit IRC02:50
*** snapiri has quit IRC02:50
*** weshay_pto has quit IRC02:50
*** threestrands_ has quit IRC02:50
*** ianychoi_ has quit IRC02:50
*** sshnaidm has quit IRC02:50
*** electrofelix has quit IRC02:50
*** mhu has quit IRC02:50
*** corvus has quit IRC02:50
*** rcarrillocruz has quit IRC02:50
*** tobasco has quit IRC02:50
*** mgagne has joined #zuul02:50
*** smyers has joined #zuul02:50
*** bstinson has joined #zuul02:50
*** jesusaur has joined #zuul02:50
*** dtruong has joined #zuul02:50
*** snapiri has joined #zuul02:50
*** weshay_pto has joined #zuul02:50
*** threestrands_ has joined #zuul02:51
*** ianychoi_ has joined #zuul02:51
*** sshnaidm has joined #zuul02:51
*** electrofelix has joined #zuul02:51
*** mhu has joined #zuul02:51
*** corvus has joined #zuul02:51
*** rcarrillocruz has joined #zuul02:51
*** tobasco has joined #zuul02:51
*** jesusaur has quit IRC02:55
*** D3VIATION has joined #zuul03:00
*** aspiers[m] has joined #zuul03:13
*** jesusaur has joined #zuul03:22
*** D3VIATION has quit IRC03:39
*** D3VIATION has joined #zuul04:06
*** CrayZee has joined #zuul05:31
*** yolanda has joined #zuul05:33
*** yolanda_ has quit IRC05:35
*** Wei_Liu has joined #zuul05:52
*** zxiiro-away is now known as zxiiro06:25
*** pcaruana has joined #zuul06:37
*** D3VIATION has quit IRC06:40
*** jimi|ansible has quit IRC06:47
*** D3VIATION has joined #zuul06:54
*** jimi|ansible has joined #zuul07:04
*** jimi|ansible has joined #zuul07:04
*** ssbarnea_ has joined #zuul07:10
*** dmellado has joined #zuul07:12
*** threestrands_ has quit IRC07:14
*** hashar has joined #zuul07:16
*** D3VIATION has quit IRC07:27
*** myoung is now known as myoung|zzz07:28
*** GonZo2000 has joined #zuul07:41
*** GonZo2000 has quit IRC07:42
*** GonZo2000 has joined #zuul07:44
*** jpena|off is now known as jpena07:46
*** gtema has joined #zuul07:59
*** GonZo2000 has quit IRC07:59
*** GonZo2000 has joined #zuul08:00
*** GonZo2000 has quit IRC08:01
*** yolanda has quit IRC08:01
*** GonZo2000 has joined #zuul08:01
*** GonZo2000 has quit IRC08:01
*** GonZo2000 has joined #zuul08:01
*** yolanda has joined #zuul08:17
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: Add support for specifying security_group in nodepool  https://review.openstack.org/57085708:18
*** xinliang has joined #zuul08:19
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: https://review.openstack.org/#/c/570857/  https://review.openstack.org/57086108:27
*** ianychoi_ is now known as ianychoi08:40
*** GonZo2000 has quit IRC08:52
*** GonZo2000 has joined #zuul09:01
*** GonZo2000 has quit IRC09:01
*** GonZo2000 has joined #zuul09:01
*** Rohaan has joined #zuul09:14
*** jesusaur has quit IRC09:14
*** jesusaur has joined #zuul09:18
*** pcaruana has quit IRC09:23
*** GonZo2000 has quit IRC09:24
*** GonZo2000 has joined #zuul09:27
*** pcaruana has joined #zuul09:27
*** GonZo2000 has quit IRC09:38
*** GonZo2000 has joined #zuul09:39
*** GonZo2000 has quit IRC09:39
*** GonZo2000 has joined #zuul09:39
*** GonZo2000 has quit IRC09:44
*** pcaruana has quit IRC09:54
*** pcaruana has joined #zuul10:10
*** yolanda has quit IRC10:38
*** yolanda has joined #zuul10:42
*** jpena is now known as jpena|lunch11:02
*** tommymcguiver has joined #zuul11:09
*** myoung|zzz is now known as myoung11:33
andreafHello Zuul team11:37
*** GonZo2000 has joined #zuul11:38
*** GonZo2000 has quit IRC11:38
*** GonZo2000 has joined #zuul11:38
andreafhas anyone thought about or is anyone working on a helm chart to deploy Zuul in a k8s cluster?11:39
andreafI found this work by jamielennox https://github.com/BonnyCI/charts as part of bonnyCI but nothing else11:39
*** pcaruana has quit IRC11:42
*** GonZo2000 has quit IRC11:50
*** GonZo2000 has joined #zuul11:53
andreafit looks like the folks at EasyStack did some work in this area but it's not clear whether it's opensourced or not https://www.openstack.org/videos/vancouver-2018/devops-implementation-for-openstack-on-kubernetes11:58
*** tommymcguiver has quit IRC12:02
*** pcaruana has joined #zuul12:02
*** jpena|lunch is now known as jpena12:03
*** GonZo2000 has quit IRC12:04
*** sshnaidm has quit IRC12:06
*** GonZo2000 has joined #zuul12:10
*** GonZo2000 has quit IRC12:10
*** GonZo2000 has joined #zuul12:10
*** sshnaidm has joined #zuul12:10
*** sshnaidm has quit IRC12:15
*** sshnaidm has joined #zuul12:18
*** sshnaidm has quit IRC12:24
*** rlandy has joined #zuul12:28
*** rlandy is now known as rlandy|rover12:29
Wei_Liuandreaf: we did not open the source right now.12:30
*** hughsaunders has quit IRC12:42
*** D3VIATION has joined #zuul13:02
RohaanHi everyone, I was going through Zuul documentation. Does Zuul support CI containerized builds? I mean does it have any support for Docker/Kubernetes. I could not find any such thing in documentation. Is there any plan to support Docker/Kubernetes/Openshift?13:08
*** sshnaidm has joined #zuul13:10
andreafWei_Liu: I see - do you have any plan to, or is it definitely not going to happen?13:11
andreafThat's something I would be interested in working on, but I'd rather not start from scratch if there is a production ready implementation already done :)13:12
Wei_Liuandreaf: yes, after the new production released, it could be July.13:13
andreafok cool13:14
ShrewsWei_Liu: why not develop it in the open?13:15
Shrewsthe nodepool driver API is not yet fully developed, so it would be helpful to see how you are using it13:16
ShrewsRohaan: there are plans, yes. and some not-yet-merged-in-master attempts at such things13:18
RohaanShrews: Oh great. Could you please share those changes?13:20
RohaanI'm reviewing Zuul CI as a potential engine for our build system. Would be great if I could get some help :)13:21
mordredRohaan: https://review.openstack.org/#/c/560136/ is the first draft of a spec for container support. we discussed it some last week at the openstack summit, so I believe another draft is coming13:23
ShrewsRohaan: well, one we do not have access to (thus my question to Wei_Liu). mordred posted the other13:24
mordred(also, several of us were out all last week at the openstack summit so might be slower to respond than normal this week while catching up)13:24
Shrewshttps://review.openstack.org/570667 and https://review.openstack.org/535557 are sample implementations13:25
fungithere's also tristanC's https://review.openstack.org/570667 for an openshift resource provider in nodepool13:25
Shrewsfungi: too slow13:25
fungioh, heh, Shrews beat me to it13:25
*** sshnaidm has quit IRC13:25
*** D3VIATION has quit IRC13:27
*** sshnaidm has joined #zuul13:27
RohaanShrews fungi: Thanks guys :) . I would take a look at these patches. Is this feature request getting tracked somewhere?13:37
*** yolanda_ has joined #zuul13:40
*** yolanda has quit IRC13:42
*** gundalow has quit IRC14:09
*** Rohaan has quit IRC14:14
*** gundalow_ has joined #zuul14:17
*** gundalow_ is now known as gundalow14:20
*** gundalow has quit IRC14:22
*** gundalow has joined #zuul14:26
*** GonZo2000 has quit IRC14:50
*** CrayZee has quit IRC15:02
*** GonZo2000 has joined #zuul15:12
*** GonZo2000 has joined #zuul15:12
*** acozine1 has joined #zuul15:12
*** GonZo2000 has quit IRC15:17
*** GonZo2000 has joined #zuul15:19
*** GonZo2000 has quit IRC15:22
gtemaguys, theoretical question: tox playbook is revoking sudo and will not proceed with it. Now if on the static node another project starts and need to install packages through bindep it of course fails without sudo. What is the best solution here?15:34
clarkbgtema: on static nodes I would probably not allow root access at all to avoid a job breaking the static instance. Instead you would want to have the necessary packages preinstalled as part of the static node creation15:36
gtemaclarkb: agree. This is what I did. But then adding each new project might require installing additional stuff, what is not always clear (or the project changes)15:38
gtemaclarkb: isn't it possible, that also on dynamic node 2 jobs would be started on the same node and have the same issue?15:39
clarkbgtema: I'm not sure that the existing dynamic node drivers allow for cohabitation of jobs15:39
clarkbif they did then yes that would be a concern there as wel15:40
gtemaok, don't we have a dynamic node reuse?15:40
clarkbgtema: grepping the source on nodepool only the static job supports max-parallel-jobs15:42
clarkb*static drive15:42
gtemait's not really question of parallel jobs, but a reuse of single node by different projects15:42
clarkbgtema: the dynamic drivers are explicitly set up to not reuse nodes15:43
* clarkb greps docs more15:43
clarkbah it is a request parameter so must be documetned on the zuul side15:43
clarkbopenstack driver seems to hardcode reuse to False15:45
clarkbShrews: is the reuse request parameter just not really used at this point?15:45
Shrewsclarkb: that's used by min-ready15:47
Shrewserr, zuul rather15:47
Shrewsmin-ready set it to False to force a new node15:47
clarkband the openstack driver seems to hard code it as well to False15:48
clarkbbut the base NodeRequest in nodepool sets it to True and the model in Zuul doesn't set it at all15:48
Shrewswell, that's where the min-ready request comes from15:49
Shrewsit defaults to True iirc15:49
clarkbShrews: on the nodepool side it does but on the zuul side it isn't set so I think the default there is None or undefined15:49
Shrewswait, what is the question15:50
clarkbShrews: can you reuse nodes from dynamic node providers in nodepool15:51
clarkband my reading of the code is the reuse parameter isn't really exposed in a way that would allow that15:51
Shrewsthat flag has a different meaning15:51
Shrewsreuse = True means "give me a node that is READY if available, otherwise launch a new one"15:51
clarkbgotcha15:51
clarkbwithin the context of dynamic node providers that means you will always get a new previously unused node right?15:52
Shrewsit depends on the driver, but for openstack driver, yes15:52
clarkbgtema: ^15:52
Shrewsstatic driver is weird in that it supports parallel jobs, but it is dependent on the base job to separate jobs.15:53
Shrewsi'm currently struggling with how to handle that my static driver changes15:53
gtemathanks guys15:54
clarkbgtema: as for handling the static node case specifically the way we did that when we had static nodes was to have a list of packages to isntall on them in config management then users could propose updates to that list15:55
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Don't capture stderr in siblings logic  https://review.openstack.org/57095615:55
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: WIP Support building pdfs of sphinx docs  https://review.openstack.org/57095715:55
clarkbgtema: once the update was merged the static nodes would get new packages installed and jobs would function on them15:55
clarkbgtema: In general I think we prefer the dynamic nodes and projects control their own package lists but that definitely has some challenges when nodes are intended to be reused15:55
gtemathanks15:56
*** jdandrea has left #zuul15:56
clarkbthinking out loud here, this is probably a good use case for the "machine" like containers16:00
clarkbyou could run a minimal static node providing containers that look like machines allowing the jobs to do things like install the packages they want16:00
gtemayeah, agree16:00
clarkbwhile having reasonable assurance that unintended mistakes won't break the entire test node16:00
*** hashar is now known as hasharAway16:01
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Remove errant comma  https://review.openstack.org/57096216:02
fungiright, we (in the openstack community) worked really hard to move all our static node jobs to dynamic nodes. we found that reusing nodes tended to leak state over time even if it was just accumulating cruft workspaces, but was particularly dangerous if we missed a regex to accidentally run jobs on them which we didn't intend to authorize for access to their contents16:10
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Don't capture stderr in siblings logic  https://review.openstack.org/57095616:10
gtemafungi: agree. I would have not used static (probably). But now I need it, since security_group is not available so far and I am sharing zuul installation with 90 other servers from different people. https://review.openstack.org/#/c/570857/ address the issue, so reviews are welcome16:14
gtemabut agree with clarkb: containers on static node would be a very pleasant feature16:17
gtemaclarkb: isn't it what Tristan did in https://review.openstack.org/#/c/535556/ ?16:22
rcarrillocruzi believe that's what oci driver is16:22
clarkbgtema: reviewed. looks good, left some small nits if you end up needing to update the change.16:22
rcarrillocruzyah, tristanC16:23
clarkbgtema: rcarrillocruz yes, we just haven't managed to get the container work merged yet but I think with the summit behind us this is now a priority for many16:23
clarkbI would expect things to start moving in that space16:23
rcarrillocruzyup16:23
gtemaclarkb: thanks16:23
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: Add support for specifying security_group in nodepool  https://review.openstack.org/57085716:27
*** gtema has quit IRC16:33
*** pcaruana has quit IRC16:39
corvusgtema seems gone... but clarkb, i left a comment on 570857 which touched on a line you previously left a comment on in openstack/handler.py ; can you take a look?16:41
clarkbcorvus: sure16:41
clarkbcorvus: oh that is a good point, I'm not sure how actionable that is from the consumer side which would be why we would put it in zk I think16:42
clarkbpossibly if a job wanted to update security groups that would be useful but in that cse it can just look up the group from the cloud api directly16:42
clarkbI'll leave a note on the change16:42
openstackgerritMerged openstack-infra/zuul-jobs master: Don't capture stderr in siblings logic  https://review.openstack.org/57095616:42
*** gtema has joined #zuul16:46
Shrewsyeah, i don't see any need to store the secgroup in zk16:51
gtemaok, removing it16:51
gtemaShrews: should I leave a test, which at least tries to start with security-group configuration? (not checking SG on the node)16:53
gtemaI think it still make sense to test this16:53
*** eandersson has quit IRC16:53
corvusgtema: yeah, leave the test so that at least the test runner is exercising the code16:54
corvus(you'll just need to remove the validation that checks the znode)16:54
gtemasure. it's clear16:54
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: Add support for specifying security_group in nodepool  https://review.openstack.org/57085717:06
gtemaremoved SG from ZK, added reno17:07
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: Add support for specifying security_group in nodepool  https://review.openstack.org/57085717:10
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow templates to be optional for zuul-migrate  https://review.openstack.org/57097917:15
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow for projects only names in zuul-migrate  https://review.openstack.org/57098017:15
*** gtema has quit IRC17:22
clarkbmordred: corvus for setting up zuul with kata is there an order of operations that must be followed on the github setup or can I ask for that to be done now then we can follow up with config changes for zuul afterwards?17:32
clarkbalso have we written down directions for what app needs to be added to a project?17:32
clarkboh I found docs neat17:33
corvusclarkb: https://docs.openstack.org/infra/manual/drivers.html#hosted-on-github17:33
clarkbI think that answers my questions, I'm going to ask for teh github side setup now and then we can do the zuul side configuration17:34
corvusclarkb: we'll need a new zuul tenant17:34
clarkbcorvus: should that be done prior to adding the app to the kata project?17:34
corvusclarkb: nope17:34
corvuswe will need to figure out how to rejigger our zuul hosting, since zuul.openstack.org is currently a whilelabel tenant17:35
clarkbah17:35
clarkbmaybe we want ot start it as a third party check under the existing tenant like we do with ansible?17:36
clarkbthen move to its own tenant when they want to switch more globally to zuul (assuming that happens?)17:36
corvusi'd say the easiest thing is to have zuul.yet-to-be-named-open-infrastructure-hosting-service.tld be the root, and optionally have whitelabel tenant vhosts if we want.  but of course we don't have a name for that.17:36
corvusclarkb: hrm.  i dunno.  i'm not sure how long we should keep kicking cans down the road.  zuul should be in its own tenant too.17:37
corvusclarkb: how about this -- i could get behind adding it to third-party-check if we first at least agree on a plan for what we will do long term :)17:39
clarkb++17:39
*** pcaruana has joined #zuul17:43
*** jpena is now known as jpena|off17:51
fungii like the proposed plan, though likely more a topic for #openstack-infra17:56
corvusi have forgotten how to read irc channel titles.  sorry.18:12
*** rlandy|rover is now known as rlandy|rover|brb18:21
*** pcaruana has quit IRC18:39
*** dtruong_ has joined #zuul18:43
*** snapiri- has joined #zuul18:44
*** Wei_Liu1 has joined #zuul18:45
*** Wei_Liu has quit IRC18:52
*** dtruong has quit IRC18:53
*** snapiri has quit IRC18:53
*** weshay_pto has quit IRC18:53
*** Wei_Liu1 is now known as Wei_Liu18:53
*** weshay has joined #zuul18:54
*** rlandy|rover|brb is now known as rlandy|rover19:03
*** hasharAway has quit IRC19:21
openstackgerritBrian Rosmaita proposed openstack-infra/zuul-jobs master: WIP - Handle -/_ ambiguity in package names  https://review.openstack.org/57100519:24
*** harlowja has joined #zuul20:00
*** acozine1 has quit IRC20:31
*** acozine1 has joined #zuul21:00
*** acozine1 has quit IRC21:04
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Implement a Runc driver  https://review.openstack.org/53555621:05
tristanCrcarrillocruz: clarkb: gtema: i renamed the oci driver into "runc", it's less confusing like that. Note that it doesn't enable root access, so you still have to pre-install bindep requirements21:07
*** GonZo2000 has joined #zuul21:09
*** ssbarnea_ has quit IRC21:16
*** D3VIATION has joined #zuul22:29
*** D3VIATION has quit IRC23:41
*** openstackstatus has joined #zuul23:44
*** ChanServ sets mode: +v openstackstatus23:44
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: builder: support setting diskimage env-vars in secure configuration  https://review.openstack.org/56468723:48

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