Saturday, 2019-12-14

clarkbcorvus: k. left one other note. I think some unrelated code snuck in00:00
corvusclarkb: i think if you were in the fully-local case, you would just not get an external ip; in that case there's a fallback so it uses private automatically00:00
corvusclarkb: yes, but it's intentional00:01
clarkboh I see that in the commit message now00:01
clarkb+200:01
clarkbsorry my brain is apparently not working great after a bike ride00:01
*** mhu has quit IRC00:09
clarkbas a heads up I think I found an ansible 2.7 to 2.8 upgrade issue in the OpenStack Helm zuul jobs. Long story short you can't use become_user on include_role tasks00:12
clarkbfigured I'd mention it here in case anyone else runs into it with their zuul upgrades00:13
corvusclarkb: maybe related: https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/use-buildset-registry/tasks/main.yaml#L96-L10300:26
corvus(i don't know how long zuul-jobs has been on 2.8; it's possible i did that because of the behavior you describe)00:27
*** sgw has joined #zuul00:57
*** rfolco has quit IRC01:08
*** fbo has quit IRC01:10
*** jamesmcarthur has joined #zuul01:18
*** jamesmcarthur has quit IRC01:25
*** Goneri has quit IRC02:09
*** Goneri has joined #zuul02:17
*** jamesmcarthur has joined #zuul02:43
*** jamesmcarthur has quit IRC03:43
*** jamesmcarthur has joined #zuul03:56
*** zbr has quit IRC04:00
*** zbr has joined #zuul04:01
*** jamesmcarthur has quit IRC04:49
*** jamesmcarthur has joined #zuul04:49
*** jamesmcarthur has joined #zuul04:50
*** jamesmcarthur has quit IRC04:56
*** jamesmcarthur has joined #zuul05:21
*** jamesmcarthur has quit IRC05:26
*** jamesmcarthur has joined #zuul05:54
*** jamesmcarthur has quit IRC05:59
*** jamesmcarthur has joined #zuul06:55
*** jamesmcarthur has quit IRC06:59
*** jamesmcarthur has joined #zuul07:56
*** jamesmcarthur has quit IRC08:01
*** spsurya has joined #zuul08:07
*** jamesmcarthur has joined #zuul08:57
*** armstrongs has quit IRC08:59
*** jamesmcarthur has quit IRC09:01
*** swest has quit IRC09:14
*** yolanda has joined #zuul09:14
*** swest has joined #zuul09:29
*** yolanda has quit IRC09:52
*** jamesmcarthur has joined #zuul09:58
*** jamesmcarthur has quit IRC10:02
*** yolanda has joined #zuul10:05
*** jamesmcarthur has joined #zuul10:54
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #zuul11:55
*** jamesmcarthur has quit IRC12:00
*** pcaruana has joined #zuul12:28
*** jamesmcarthur has joined #zuul12:30
*** AJaeger has quit IRC13:12
*** AJaeger has joined #zuul13:26
*** jamesmcarthur has quit IRC13:33
*** Goneri has quit IRC14:44
pabelangercorvus: clarkb: with new use-internal-ip option in nodepool, what do we see the process for zuul-executor to be able to SSH into node (or setup ssh host keys)?  I ask, because this is something we deal with today for some network appliances14:49
pabelangerI assume something like regional executor?14:50
openstackgerritMerged zuul/nodepool master: GCE: add use-internal-ip option  https://review.opendev.org/69904115:04
*** gmann_afk is now known as gmann15:27
corvuspabelanger: yes, if the executor has access to that network, you can use it.  note, i only implemented that for the gce driver; but we can add it to others15:28
pabelangerack, thanks15:29
*** jamesmcarthur has joined #zuul15:31
clarkbits doable in openstack via clouds.yaml config I think15:31
*** Goneri has joined #zuul15:32
pabelangerYah, kinda. The gets complicated if you only have a single node in the cloud that you want to be private15:33
pabelangerbut, right now our executor is still public, so zuul-executors cannot talk to the nodepool node. We hop to it via nested ansible (2 nodes in nodeset)15:34
*** jamesmcarthur has quit IRC15:36
*** goneri_ has joined #zuul15:40
*** Goneri has quit IRC15:44
mordredtobiash: +2 with a comment on your /ready patch15:53
mordredtobiash: feel free to hit the +A if my comment doesn't make sense15:53
*** goneri_ is now known as Goneri16:08
*** jamesmcarthur has joined #zuul16:32
*** jamesmcarthur has quit IRC16:36
*** jamesmcarthur has joined #zuul16:58
*** Goneri has quit IRC17:02
*** jamesmcarthur has quit IRC17:11
*** jamesmcarthur has joined #zuul17:12
*** jamesmcarthur_ has joined #zuul17:21
*** jamesmcarthur has quit IRC17:21
*** jamesmcarthur_ has quit IRC17:31
*** jamesmcarthur has joined #zuul19:10
*** jamesmcarthur has quit IRC19:20
*** jamesmcarthur has joined #zuul19:35
*** jamesmcarthur has quit IRC19:40
*** jamesmcarthur has joined #zuul19:55
*** jamesmcarthur has joined #zuul19:58
*** jamesmcarthur has quit IRC20:07
*** spsurya has quit IRC20:08
*** jamesmcarthur has joined #zuul20:14
*** jamesmcarthur has quit IRC20:17
*** pcaruana has quit IRC20:17
*** jamesmcarthur has joined #zuul20:21
*** jamesmcarthur has quit IRC20:34
*** jamesmcarthur has joined #zuul20:48
*** jamesmcarthur has quit IRC20:51
*** jamesmcarthur has joined #zuul20:59
*** jamesmcarthur has quit IRC21:05
*** Goneri has joined #zuul21:33
*** jamesmcarthur has joined #zuul21:34
*** jamesmcarthur has quit IRC21:36
*** jamesmcarthur has joined #zuul21:38
*** jamesmcarthur has quit IRC21:42
*** jamesmcarthur has joined #zuul21:44
*** jamesmcarthur has quit IRC21:47
*** hashar has joined #zuul22:24
*** jamesmcarthur has joined #zuul22:43
*** jamesmcarthur has quit IRC22:46
*** hashar has quit IRC23:16
SpamapSI would be able to make use of priate IPs in AWS if we had an executor in each VPC. Right now we use the same method for our zuul nodes to punch through as we do for our laptops... which is great for making sure your deploys can be done manually.. but also means the zuul nodes get a key that can enable internet access from any AWS subnet.. which isn't the best thing.23:41
*** jamesmcarthur has joined #zuul23:47
*** jamesmcarthur has quit IRC23:51

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