Thursday, 2019-07-25

openstackgerritMerged zuul/nodepool master: Add nodepool_debug flag to openstack functional jobs  https://review.opendev.org/66993900:15
openstackgerritIan Wienand proposed zuul/nodepool master: [wip] functional testing: test journal-to-console element  https://review.opendev.org/66978700:21
openstackgerritIan Wienand proposed zuul/nodepool master: Enable debug logs for openstack-functional tests  https://review.opendev.org/67241200:23
openstackgerritIan Wienand proposed zuul/nodepool master: [wip] functional testing: test journal-to-console element  https://review.opendev.org/66978700:23
*** igordc has quit IRC01:04
*** wxy-xiyuan has joined #zuul01:11
corvusmordred: i think the solution in https://review.opendev.org/672606 will be "good enough", but maybe the subquery idea would pay off for the job_name case?01:34
*** bjackman has joined #zuul02:47
*** bhavikdbavishi has joined #zuul02:51
*** bhavikdbavishi1 has joined #zuul02:54
*** bhavikdbavishi has quit IRC02:55
*** bhavikdbavishi1 is now known as bhavikdbavishi02:55
openstackgerritIan Wienand proposed zuul/nodepool master: Functional testing: add journal-to-console element  https://review.opendev.org/66978703:35
*** yolanda has quit IRC04:21
*** yolanda has joined #zuul04:22
*** jank has joined #zuul04:39
*** pcaruana has joined #zuul04:44
*** pcaruana has quit IRC04:56
*** swest has joined #zuul05:05
*** pcaruana has joined #zuul06:21
yoctozeptocorvus, Shrews, mordred: thanks for handling, I went to bed and failed to say goodbye :-(06:37
*** rlandy has joined #zuul06:46
*** jpena|off is now known as jpena06:52
*** jpena is now known as jpena|mtg06:53
-openstackstatus- NOTICE: The git service on opendev.org is currently down.06:53
*** ChanServ changes topic to "The git service on opendev.org is currently down."06:53
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul CLI: allow access via REST  https://review.opendev.org/63631506:56
openstackgerritMatthieu Huin proposed zuul/zuul master: Add Authorization Rules configuration  https://review.opendev.org/63985506:58
openstackgerritMatthieu Huin proposed zuul/zuul master: Web: plug the authorization engine  https://review.opendev.org/64088406:59
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul Web: add /api/user/authorizations endpoint  https://review.opendev.org/64109906:59
openstackgerritMatthieu Huin proposed zuul/zuul master: authentication config: add optional token_expiry  https://review.opendev.org/64240806:59
*** jamesmcarthur has joined #zuul07:04
*** rlandy is now known as rlandy|mtg07:07
flaper87what zuul services need to be restarted when the tenant definition is changed? Just web?07:20
flaper87https://github.com/openstack/project-config/blob/master/zuul/main.yaml <- this file here07:20
*** jank has quit IRC07:21
flaper87mmh, apparently the scheduler07:27
*** jank has joined #zuul07:50
*** jank has quit IRC07:53
*** panda has quit IRC08:28
*** tosky has joined #zuul08:30
*** panda has joined #zuul08:31
-openstackstatus- NOTICE: Services at opendev.org like our git server and at openstack.org are currently down, looks like an outage in one of our cloud providers.08:36
*** ChanServ changes topic to "Services at opendev.org like our git server and at openstack.org are currently down, looks like an outage in one of our cloud providers."08:36
*** sshnaidm has quit IRC08:38
*** sshnaidm has joined #zuul08:42
*** ChanServ changes topic to "Discussion of the project gating system Zuul | Website: https://zuul-ci.org/ | Docs: https://zuul-ci.org/docs/ | Source: https://git.zuul-ci.org/ | Channel logs: http://eavesdrop.openstack.org/irclogs/%23zuul/ | Weekly updates: https://etherpad.openstack.org/p/zuul-update-email"08:43
-openstackstatus- NOTICE: The problem in our cloud provider has been fixed, services should be working again08:43
*** jamesmcarthur has quit IRC08:48
openstackgerritFabien Boucher proposed zuul/zuul master: Return dependency cycle failure to user  https://review.opendev.org/67248709:12
*** swest has quit IRC09:13
*** swest has joined #zuul09:14
*** lennyb has joined #zuul09:16
*** hashar has joined #zuul09:48
*** hwangbo has quit IRC09:50
*** bhavikdbavishi has quit IRC09:52
openstackgerritFabien Boucher proposed zuul/zuul master: Fix reference pipelines syntax coloration for Pagure driver  https://review.opendev.org/67267709:54
openstackgerritFabien Boucher proposed zuul/zuul master: Add reference pipelines file for Gerrit driver  https://review.opendev.org/67268310:12
*** hashar has quit IRC10:15
*** AshBullock has joined #zuul10:23
AshBullockHey guys, in the openshift example there is a role variable called openshift_pods, is there a similar variable exposed when using the kubernetes driver? As we need a var that has the spun up pod names so we can run kubectl  thanks10:45
AshBullockthis is the openshift example https://www.softwarefactory-project.io/tech-preview-using-openshift-as-a-resource-provider.html10:45
AshBullockand the prepare workspace role I was looking at https://review.opendev.org/#/c/631402/3/roles/prepare-workspace-openshift/tasks/main.yaml10:46
*** hashar has joined #zuul11:32
*** pcaruana has quit IRC11:42
*** bhavikdbavishi has joined #zuul11:42
*** igordc has joined #zuul11:43
sshnaidmis there a correct way to inherit job from two parents?11:52
tristanCsshnaidm: yes, you can define two variants with different parent12:19
sshnaidmtristanC, do you have any example how to do it?12:20
tristanCsshnaidm: like so: http://paste.openstack.org/show/754848/12:20
sshnaidmtristanC, cool, thanks12:20
*** pcaruana has joined #zuul12:22
tristanCAshBullock: can't find openshift_pods in the blog post, what do you need it for?12:22
sshnaidmtristanC, do you know if cleanup is already available in o.o and rdo zuuls? https://review.opendev.org/#/c/662147/3/doc/source/user/config.rst12:24
*** hashar has quit IRC12:25
tristanCsshnaidm: looking at http://zuul.opendev.org/t/zuul/status, at the bottom it says the commit short sha that the scheduler is running12:27
tristanCsshnaidm: which should includes the cleanup phases12:27
tristanCsshnaidm: rdo is running tagged version, we would need a new zuul version12:28
*** hashar has joined #zuul12:28
AshBullocktristanC got a little further now, have the pod name and trying to run an exec command to create a directory in the pod, we are receiving this error: "main -> localhost | error: You must be logged in to the server (Unauthorized)", we have the task running localhost, here is our config: http://paste.openstack.org/show/754849/12:28
AshBullockany idea what I'm doing wrong?12:29
openstackgerritMonty Taylor proposed zuul/zuul master: Improve SQL query performance in some cases  https://review.opendev.org/67260612:31
tristanCAshBullock: is this using eks? and is your nodepool and zuul services from outside the cluster?12:33
AshBullockyes and yes12:34
AshBullockit looks like it is not correctly assuming the zuul-worker role12:34
AshBullockso is throwing a non authorised12:35
AshBullockwe can see the role and role bindings created12:35
tristanCAshBullock: perhaps the service account and token provided by nodepool needs some extra configuration to be usable by zuul with eks12:36
AshBullockwhere is that config set?12:36
tristanCiirc eks enforces special auth requirement for external api call12:36
tristanCAshBullock: the namespace is configured like so: https://opendev.org/zuul/nodepool/src/branch/master/nodepool/driver/kubernetes/provider.py#L15512:37
AshBullockwe are able to create the namespace and pod, it just seems we are unable to run the exec command12:37
AshBullockso it must be able to run commands against the cluster12:37
AshBullockwhat we're seeing is from a playbook when it assumes the zuul-worker user it is getting a permissions error12:38
tristanCAshBullock: nodepool and zuul doesn't use the same auth, so there may an issue with the zuul's token12:38
tristanCAshBullock: here is how we configure nodepool for our openshift integration test: https://softwarefactory-project.io/cgit/software-factory/sf-ci/tree/roles/health-check/openshift/tasks/config_repo_nodepool_configuration.yml12:39
tristanCAshBullock: and here is how we test zuul job running in pods: https://softwarefactory-project.io/cgit/software-factory/sf-ci/tree/roles/health-check/openshift/tasks/demo_project_zuul_configuration.yml12:39
AshBullockwhere in the code does the zuul worker token get set?12:40
AshBullockthe secondary kube config that zuul uses ?12:40
AshBullockfor the zuul-worker user12:40
AshBullockas our nodepool kube config has the correct aws auth command but I guess the zuul one does not12:41
openstackgerritFabien Boucher proposed zuul/zuul master: Add reference pipelines file for Github driver  https://review.opendev.org/67271212:41
openstackgerritFabien Boucher proposed zuul/zuul master: Add change replacement field in doc for start-message  https://review.opendev.org/66597412:44
*** bjackman has quit IRC13:00
*** bhavikdbavishi has quit IRC13:07
AshBullockI'm thinking I need to add the get-token logic that eks requires to the zuul-worker kube config, something like "aws eks get-token --cluster-name zuul-eks --region eu-west-1" to generate a token13:09
*** bhavikdbavishi has joined #zuul13:10
*** jhesketh has quit IRC13:22
*** jhesketh has joined #zuul13:26
flaper87what zuul services need to be restarted when the tenant definition is changed? Just scheduler? Is there a way to reload the tenant configs without restarting the service?13:31
pabelangerflaper87: yup, I believe it is zuul-scheduler reload13:33
pabelangeror kill -HIP pid13:33
pabelangerkill -HUP13:33
fungiyeah, no restart needed13:44
fungiit can just reload the config while remaining up13:44
fungirestarts should only be necessary to replace zuul software or its python dependencies13:45
mhuHi! In a multi-executor setup, is it possible to "tie" nodes to an executor? The use case would be running jobs on baremetal instances living in different geographical zones13:57
AshBullocki've tracked down the .kube config file in the zuuls working directory, this has a token set, but we need to pass in the aws token generation command, we've tried templating over it but the file seems to be protected, is there a way to set kube configuration to override the default?13:57
mhuso you want the executor closest to a given node to run the playbook13:57
tristanCmhu: iirc, in nodepol we can set an executor-zone to nodepool node, and then we can configure a zuul executor service to run job for that zone13:59
tristanCAshBullock: here is how the zuul executor service writes down the kube config: https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L169214:00
mhutristanC, thanks!14:00
tristanCcorvus: running the zuul-operator test playbooks with openshift, the operator pod starts successfully: http://paste.openstack.org/show/754853/14:09
tristanCcorvus: makes me wonder if the install-kubernetes correctly setup the operator framework... Could I start an openshift based integration job?14:10
corvustristanC: yeah, but i think we should have both, so i think we need to get the k8s one working14:20
corvustristanC: jeliu was looking into it and said it looked like it was running locally14:20
corvustristanC: but what do you mean "install-kubernetes correctly setup the operator framework" ?14:21
tristanCcorvus: looking at the pod logs in ci: http://logs.openstack.org/76/672576/1/check/zuul-operator-functional-k8s/2d0c442/ara-report/result/946eb628-8523-4d9b-b38b-d75267586010/14:22
tristanCcorvus: it looks like something is missing, logs shouldn't contains an usage output14:22
tristanCit does says "Watches established.", but then it fails to go into operator mode (e.g. select a leader, "starting to serve"14:23
corvustristanC: agreed --14:23
corvustristanC: agreed -- but also, it looks like maybe the output from the 2 containers are overwriting there?14:24
corvustristanC: because the first lines of the usage output are missing14:24
tristanCcorvus: the second container (named ansible) should be silent as watch are triggered by crd yet14:24
corvustristanC: check this out: http://logs.openstack.org/95/670395/7/check/zuul-operator-functional-k8s/2d74a66/ara-report/14:24
corvustristanC: jeliu split that up so we have the ouput from each container separately14:25
corvustristanC: so the operator container emitted help text, and the ansible container emitted logs about 'watches'14:26
corvustristanC: what made the watches output?14:26
tristanCcorvus: i see, well with openshift it seems to work out of the box: http://paste.openstack.org/show/754853/14:26
tristanCi guess we'll want both k8s & openshift integration test, so i could write one quickly to at least get the expected output in ci14:27
corvustristanC: yep, that might help us get the k8s one working14:27
corvusi also held a node if we want to look into it14:27
corvustristanC: i can add your key if you want14:28
corvusi didn't have time to look yesterday :|14:28
corvustristanC: what does the ansible container do?14:29
corvus(i was expecting only one container (the operator container) and for it to run a daemon which responded to k8s crd changes)14:30
tristanCcorvus: the ansible container is running ansible-runner and you'll have the task json output logs from it14:31
tristanCcorvus: the operator container are info logs about the operator process, *iirc*14:31
*** jeliu_ has joined #zuul14:32
corvusjeliu_: good morning!  tristanC and i were just talking about the operator14:32
tristanCjeliu_: here is what i got using a local oc cluster up setup: http://paste.openstack.org/show/754853/14:33
corvusjeliu_: you can catch up on what we were talking about here: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2019-07-25.log14:34
corvustristanC, jeliu_: that's still really weird that http://logs.openstack.org/95/670395/7/check/zuul-operator-functional-k8s/2d74a66/ara-report/result/1859a953-bbc8-4afe-901a-64723b115dea/ is missing some lines of output14:39
tristanCcorvus: it maybe that the command doesn't display an header and goes straight to cli options14:40
tristanCperhaps a badly designed failure mode...14:41
corvustristanC: well, when jeliu_ ran it on his local k8s, he got something like this: https://etherpad.openstack.org/p/zuul_commands14:41
corvustristanC: i guess it could be in the failure mode we're seeing, there's no error or header, but that would be weird too14:42
tristanCjeliu_: how did you deploy the local k8s?14:42
corvustristanC: aiui, he's done it both via a local build of k8s, and then also with minikube14:48
corvusif i open up a shell on the ansible container and try to run the operator, i get: Error: Get https://10.96.0.1:443/api?timeout=32s: dial tcp 10.96.0.1:443: connect: no route to host14:55
corvus(and then the full operator help output)14:55
*** dkehn has joined #zuul15:00
*** dkehn has left #zuul15:01
*** dkehn has joined #zuul15:01
corvustristanC, jeliu_: what if there's a firewall issue on our test nodes?15:05
*** rlandy|mtg has quit IRC15:05
*** jpena|mtg is now known as jpena|off15:07
corvusclarkb, mordred, fungi: ^ do you remember that weird docker firewall issue we ran into?15:07
clarkbit was ipv6 specific I think (since docker doesnt manage ipv6 by default?)15:08
fungialso docker wants to manage your firwewall unless you explicitly tell it hands off, right?15:08
corvusoh i thought it was something about how docker set the default policy of one of the chains?15:08
corvusit sets forward to drop15:09
corvusour firewall rules are still in place on the input chain, but it's last; so i'm not sure if it's an issue or not15:10
corvusthere's no telnet in the zuul-operator image; we should add that :)15:11
jeliu_corvus: I can help with that!15:17
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: test operator / iptables  https://review.opendev.org/67275515:17
corvusjeliu_: thanks!15:17
corvusclarkb, fungi: ^ do you think "/etc/init.d/iptables-persistent stop" will be enough to remove our iptables rules as a factor?15:18
clarkbcorvus: I cant remember if that does a drop of the rulesit knows about15:19
fungithat file doesn't seem to exist on bionic15:19
fungioh, right, /etc/init.d/netfilter-persistent15:19
corvusit's a xenial node15:19
clarkbyou may need to edit the rules files and start to load an emptier ruleset (then restart dockerd so it replaces ots rules)15:19
corvusi put that in before the docker install15:20
fungiruns `/usr/sbin/netfilter-persistent stop` to flush rules15:20
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275615:21
fungiif you follow the execution path through the plugin scripts, it basically does `/sbin/iptables -P $chain ACCEPT` for chains INPUT FORWARD OUTPUT15:21
fungiso essentially opens the rulset up wide15:22
fungithat ought to work15:22
fungithough i was looking at the bionic version. probably similar on xenial just simpler because that predates the netfilter plugins mechanism15:22
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275615:25
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Assure ensure-tox installs latest tox version  https://review.opendev.org/67276015:39
openstackgerritJames E. Blair proposed zuul/zuul master: Improve SQL query performance in some cases  https://review.opendev.org/67260615:39
AJaegercorvus: https://review.opendev.org/#/c/670133/ for zuul-jobs (skipping test-setup.sh in pep8) is now 14days old. Want to merge it and followup on zuul-announce?15:43
corvusAJaeger: done.  took me a minute to double check everything :)15:45
AJaegerthanks15:47
*** altlogbot_2 has quit IRC15:48
corvusmordred, tristanC, jeliu_: any more thoughts on the spec https://review.opendev.org/659180  ?  are you ready for me to start poking other folks to review it?15:50
*** altlogbot_3 has joined #zuul15:51
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: test operator / iptables  https://review.opendev.org/67275515:53
mordredcorvus: I think it's ready for poking15:53
openstackgerritMerged zuul/zuul-jobs master: Skip test-setup.sh in pep8 jobs  https://review.opendev.org/67013315:57
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Assure ensure-tox installs latest tox version  https://review.opendev.org/67276015:58
*** hwangbo has joined #zuul16:09
corvusfungi, clarkb: hrm that didn't work: http://logs.openstack.org/55/672755/2/check/zuul-operator-functional-k8s/471465a/ara-report/result/39faf412-62d6-4ea2-9959-3e626d679204/16:09
corvushttp://logs.openstack.org/55/672755/2/check/zuul-operator-functional-k8s/471465a/ara-report/result/49ee5cf7-856c-4d65-858c-dc1f1a141148/16:10
fungithat's after flushing via iptables-persistent stop?16:10
corvusyeah -- second link is the stop command16:11
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276016:12
fungiand the iptables -L is a couple seconds later, yeah16:12
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: test operator / iptables  https://review.opendev.org/67275516:13
corvusbrute force ^16:13
*** mattw4 has joined #zuul16:14
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275616:16
tristanCcorvus: the spec lgtm16:16
corvusSpamapS, tobiash, flaper87: can you look over https://review.opendev.org/659180 soonish?  i think it's close to ready to merge16:17
*** mattw4 has quit IRC16:23
*** mattw4 has joined #zuul16:23
flaper87corvus: well re-review tomorrow! Hope to make it in time before it merges16:25
flaper87:D16:25
corvustristanC, jeliu_: it looks like it was the firewall: http://logs.openstack.org/55/672755/3/check/zuul-operator-functional-k8s/54283ff/ara-report/result/d1174d83-4096-456b-86ff-2dc4da5c27f4/16:34
corvusjeliu_: if you want to incorporate https://review.opendev.org/672755 into your change, i think that's good for now16:36
mordredcorvus: awesome16:36
corvuswe should probably add a role to zuul-jobs to clear out the firewall16:36
corvusor, maybe talk with the opendev sysadmins about maybe possibly dropping the firewall from test nodes...16:36
*** AshBullock has quit IRC16:36
mordredcorvus: want me to extract that and make one? I'm at a lull where I could do that16:37
corvusmordred: yeah, that'd be great; i have to afk for few16:37
mordredkk16:37
fungithe risk with not firewalling by default is we have folks installing things like open recursive dns resolvers and elasticsearch api servers in their jobs, which get picked up by miscreants sweeping the internet looking for exploitable systems and then used in coordinated ddos attacks all before the builds conclude16:39
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: install-openshift: bump version to 3.11.0  https://review.opendev.org/67278516:40
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Add clear-firewall role  https://review.opendev.org/67278616:41
fungi(note this is not a theoretical risk, i've fielded a number of complaints from our providers in the past because folks running complex jobs took it upon themselves to turn off the firewalling in them since it was too hard to troubleshoot)16:41
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275616:41
fungi(in particular, it was deployment projects trying to do things with containers: kolla, openstack-helm, tripleo... i guess there's a common reason)16:43
openstackgerritTristan Cacqueray proposed zuul/nodepool master: DNM: test openshift version bump  https://review.opendev.org/67278816:43
Shrewscorvus: you don't need a separate index for just uuid in https://review.opendev.org/67260616:46
* mordred agrees with Shrews16:47
Shrewsmordred: see? i haven't forgotten *everything*16:47
Shrews:)16:47
Shrewsas much as tried to16:48
Shrewscorvus: it's because uuid is the _first_ column used in the index. if it were the buildset_id, that would be different16:49
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275616:50
*** chandankumar is now known as raukadah16:52
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add telnet to Docker Image  https://review.opendev.org/67279116:53
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add telnet to Docker Image  https://review.opendev.org/67279116:56
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: install-openshift: bump version to 3.11.0  https://review.opendev.org/67278516:57
*** igordc has quit IRC16:58
*** igordc has joined #zuul16:58
openstackgerritTristan Cacqueray proposed zuul/nodepool master: DNM: test openshift version bump  https://review.opendev.org/67278816:58
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275617:10
clarkbfungi: ya I would not be comfortable with removing the firewall17:11
clarkbI think instead we need to figure out how to make the fireawll ignore docker/k8s17:11
clarkb(perhaps with a local only addr that is open?)17:12
clarkbwell docker is supposed to do it for you17:13
clarkbnot sure about k8s17:13
clarkbcorvus: out of curiousity why "clear out the firwall" and not "update firwall so it works with k8s"?17:15
corvusclarkb, fungi: okay, we can just do the clear firewall thing in these jobs for now.  my suggestion re opendev was mostly in service of aligning our testing platform with vanilla installations.  but i'm not going to defend that hill.  :)17:15
corvusclarkb: if you have an idea of how to do that, great -- we can even test that it work now.17:16
corvusclarkb: but from my pov, minikube+k8s want to run the firewall, so i want to get out of their way and let them17:16
corvusclarkb: it's more or less the same conclusion we came to when we looked at running k8s in opendev17:16
clarkbcorvus: (this is from memory several months old so results may vary) I believe the issue is that k8s has internal network ranges that we'll block by default. Much like multinode testing we want t add rules that say those ranges can talk to that range on all ports17:17
corvus(but s/ansible-openstack/minikube/)17:17
clarkbI don't know what ranges minikube uses, but if we can identify those and allow all of them to talk to each other I expect it will be happier17:17
corvusclarkb: it's beyond my understanding.  my feeling is that clearing out the firewall is okay in this instance (it's being replaced by a sufficiently robust firewall).  and that's even desirable (because it's good to have the testing infra be similar to prod, and we don't want to have to eliminate the firewall as a cause of every problem we have).  so even if that approach would work, i'm still not sure it's17:21
corvuswhat we want in the long run.17:21
corvusShrews, mordred: replied17:22
mordredShrews: we aren't smart17:22
clarkbit is too bad it isn't easier to identify what is "external" networking in a cloud sense as we could change the ruleset to say "don't let any of that in except for ssh" and freely allow everything else to talk17:22
corvusyeah, i mean, i'm not happy about the way docker/k8s interact with the host :)17:23
clarkbAnother option is to lean more heavily on security groups17:24
clarkbsupposedly they have vastly improved the performance of how those rules are applied so I won't get 3am phone calls anymore17:24
clarkbThat is the proper way to express "don't let external in" in the openstack clodu context I think17:24
clarkbBut historically it caused the cloud to break when we booted hundreds of nodes an hour17:25
corvusclarkb: i'm confused -- if you're concerned about people abusing our test nodes -- we give them root.17:25
clarkbre security groups?17:26
corvusyeah17:26
clarkbthe issue was it thrashed the mysql database causing it to stop being performant which meant none of the cloud apis functioned and I got a phone call from the cloud operator saying please make it stop17:26
corvusokay this doesn't sound like a #zuul convo17:26
clarkbwell its realted to zuul in that that is one way we could potentially remove the on host firewalls as you suggested here17:26
corvushow does security groups help us remove the on-host firewall?17:27
clarkbwe would use the security groups to prevent open dns resolvers on the internet and remove the on host firwalls17:27
clarkbbasically use security groups to block that traffic instead of iptables17:27
corvuswhat do open dns resolvers have to do with this?17:27
clarkbcorvus: see fungi's concern17:27
*** igordc has quit IRC17:28
clarkb16:39:04           fungi | the risk with not firewalling by default is we have folks installing things like open recursive dns resolvers and elasticsearch api servers in their jobs17:28
corvusyeah i see that17:28
fungii think wiping the firewall off the test node is fine in this case, as long as people are mindful that there's not necessarily any preexisting protection in place any longer and it's up to them to secure what they're installing in jobs17:28
corvusdo you think i just wrote a job that installes an open dns resolver?17:28
clarkbcorvus: no but other people do?17:28
corvusokay, we're going to have to talk about this later17:28
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275617:30
fungiwith my opendev sysadmin hat on, we provide this mitigation by default but we don't really have a means of preventing jobs from turning it off. disabling that protection isn't something which should be taken lightly, but there are plenty of other ways for folks to cause similar problems with jobs17:30
clarkbfungi: yup. My suggestion is we can replace the host firewalls globally with security groups, then we can remove the iptables rules across the board as corvus suggested17:31
fungireplacing the firewall which is there with a different firewall seems reasonable, which is what is being proposed in this particular job17:31
clarkbThen jobs don't have to worry about the firwall and we still mitigate the risks17:31
Shrewsmordred: corvus: lol!17:31
fungidiscussion of security groups in the opendev donor environments is a much bigger topic, and better suited to #openstack-infra or #opendev17:32
Shrewscorvus: sorry. i made assumptions based on the tests you had me perform last night. so this is really your fault if you think about it  :-P17:33
webknjazHey folks! I recall you do automatic releases to PyPI. Now you can have a proper project-scoped upload token instead of putting a password there.17:47
webknjazRef: https://discuss.python.org/t/pypi-security-work-multifactor-auth-progress-help-needed/1042/3117:47
webknjazN.B. If you have 2FA enabled on PyPI, eventually you'll be forced to switch to using tokens.17:47
fungiwebknjaz: how does that work with unattended twine upload?17:47
fungiwebknjaz: ahh, i see, thanks17:48
webknjazI haven't tested it yet, but I assume that you'll need to replace password with that17:48
webknjazlemme check17:49
fungiso we need a human to generate a token for uploading... i still don't see where it's more secure than having a dedicated account for uploading but maybe this is useful to people who use the same account for webui on warehouse too17:49
fungilooks like the announcement about that just hit the pypa-dev ml as well17:52
tristanCcorvus: there is the same issue with openshift, the opendev default firewall prevent access to 172.30.1.1:5000 (the internal registry)17:54
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275617:54
webknjazfungi: just one acc less to maintain..17:56
clarkbwebknjaz: well I don't think we'd use a personal accoutn for zuul automated uploads17:57
fungiright, we'll use a dedicated account anyway17:58
fungiit'll just be an extra step now to use that account to generate a perpetual api token17:58
webknjazFWIW: use `@token` for a username and the token itself for a password when using Twine: https://github.com/pypa/warehouse/issues/994#issuecomment-51263422217:58
*** jeliu_ has quit IRC17:58
fungiwe'll want to test whether that's compatible with how privileges are delegated, since we expect to use one set of credentials to upload for multiple projects, including projects which don't exist yet or need access delegated at a later time17:59
fungianyway, the announcement doesn't indicate there's any breaking change on the way for how the job is currently defined18:01
fungias long as two-factor authentication isn't enabled for the account used, the indication is that it will continue to be able to upload via username+password with such an account18:02
fungionly accounts with two-factor authentication enabled are hinted at being forced to use api tokens to perform uploads in the future18:03
*** jeliu_ has joined #zuul18:03
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276018:03
clarkbfungi: and I'm guessing that is beacuse twine doesn't know how to 2fa so you ahve to 2fa to get a limited time/scope token18:03
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275618:05
fungitwine could be adapted to do interactive 2fa fairly easily. the bigger challenge is distutils, which is baked into python's stdlib, so a backward-compatible solution is needed there regardless18:05
clarkbah18:05
*** mattw4 has quit IRC18:11
*** mattw4 has joined #zuul18:11
*** jamesmcarthur has joined #zuul18:17
openstackgerritMerged zuul/zuul master: Improve SQL query performance in some cases  https://review.opendev.org/67260618:18
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275618:21
*** igordc has joined #zuul18:22
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276018:30
webknjazfungi: I'm pretty sure nobody will ever try to change distutils there. AFAIR it's scheduled to be removed from stdlib.18:37
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276018:42
fungiwebknjaz: yep, in... like... 3.918:43
fungibut older interpreters//stdlib will be in use for many, many years to come18:43
webknjaz`setup.py upload` is highly discouraged anyway so no need to care about it18:44
webknjaznot even sure whether still works18:44
webknjaz*it18:44
clarkbyup, we are sort of why twine exists :)18:44
fungiit's discouraged, but still supported (which is why the announcement mentions using api tokens with distutils)18:45
clarkbdstufft found out we were using curl instead of setup.py upload (because setup.py upload is scary for a few reasons) and that was the genesis of twine18:45
*** fdegir has quit IRC18:45
webknjazah18:46
*** fdegir has joined #zuul18:46
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275618:51
mordredsetup.py is scary for many reasons18:54
mordredregardless of which subcommand it runs18:54
* mordred quickly gets back off soapbox18:55
*** jeliu_ has quit IRC19:06
openstackgerritJeff Liu proposed zuul/zuul-operator master: [WIP] Verify Operator Pod Running  https://review.opendev.org/67039519:08
*** igordc has quit IRC19:09
*** jeliu_ has joined #zuul19:10
*** tosky has quit IRC19:10
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276019:13
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: WIP: Add zuul-operator-functional-openshift job  https://review.opendev.org/67275619:15
*** bhavikdbavishi has quit IRC19:18
*** jeliu_ has quit IRC19:23
*** igordc has joined #zuul19:25
*** igordc has quit IRC19:32
*** jamesmcarthur has quit IRC19:40
*** jamesmcarthur has joined #zuul19:41
*** armstrongs has joined #zuul19:43
*** jamesmcarthur has quit IRC19:46
armstrongsHey, we got eks up and running with zuul today. We had to patch the executor server.py to do this amoung some other things we were keen to document the steps for this as other users will be keen on this too. What would be the best way to do this?19:47
fungiarmstrongs: a commit (or commits) with your patches pushed up for review would be a great start19:56
fungithat should hopefully simplify the instructions19:56
armstrongsCool was also wanting to document the kubernetes pre stuff a little more as a new page. So was wondering where that should sit. As we had to ask a tonne of questions and pester you guys. So was thinking could do an end to end guide for newbies20:00
fungiif we add a third guide for newcomers (in addition to the quick-start and from-scratch guides) we'll likely need some way to disabmiguate them20:01
*** michael-beaver has joined #zuul20:02
fungiwould this fit as an alternate ending for from-scratch?20:02
armstrongsThis wasn't to replace them more a kubernetes driver section to supplement them20:02
armstrongsSo I think there was good coverage on the from scratch with static driver. But I had to ask questions on the nodepool aws and kubernetes ones. So thought could do those maybe as part of the from scratch with links?20:05
clarkbmaybe a mini guide for each nodepool driver as the step beyond quickstart20:06
clarkb"go here if using openstack, here if using k8s, etc"20:06
armstrongsYup was thinking that20:07
tristanCperhaps in the zuul/doc/source/user/howtos/ section?20:07
Shrewswe have the quickstart guide already divided up based on nodepool driver. seems logical to at least add *something* there20:07
Shrewsi.e. https://zuul-ci.org/docs/zuul/admin/zuul-from-scratch.html#nodepool20:08
*** igordc has joined #zuul20:08
Shrewsbut i could also see something going into nodepool itself, too20:08
armstrongsYeah was thinking 2 more links there20:09
*** jamesmcarthur has joined #zuul20:11
Shrewsarmstrongs: that makes the most sense to my brain. perhaps go with that and let's see how it looks?20:12
armstrongsThanks will do20:12
Shrewsarmstrongs: thx for the offer to do it20:12
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add clear-firewall role  https://review.opendev.org/67278620:15
*** armstrongs has quit IRC20:16
*** jamesmcarthur has quit IRC20:19
*** jeliu_ has joined #zuul20:28
*** jamesmcarthur has joined #zuul20:30
*** zbr_ has quit IRC20:35
*** zbr has joined #zuul20:37
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Update testing section  https://review.opendev.org/67282020:37
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add clear-firewall role  https://review.opendev.org/67278620:41
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276020:49
*** jamesmcarthur has quit IRC21:00
*** jamesmcarthur has joined #zuul21:01
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: Allow ensure-tox to upgrade tox version  https://review.opendev.org/67276021:02
corvusmordred, jeliu_: looks good!  http://logs.openstack.org/95/670395/8/check/zuul-operator-functional-k8s/68f041f/ara-report/result/3f3b7bbb-6daa-4dba-93c5-fb226f78ebc6/   and   http://logs.openstack.org/95/670395/8/check/zuul-operator-functional-k8s/68f041f/ara-report/result/73b10032-3c4b-4647-a41e-5ed412a335a3/21:08
mordredcorvus: woot!21:09
jeliu_corvus: sweet! finally running21:09
corvusmordred: i'll go ahead and fix up the linters issue and add a test job21:09
corvusjeliu_: and i made a suggestion for an update to your change if you want to take a look21:10
*** zbr has quit IRC21:11
openstackgerritJeff Liu proposed zuul/zuul-operator master: [WIP] Verify Operator Pod Running  https://review.opendev.org/67039521:12
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add clear-firewall role  https://review.opendev.org/67278621:13
mordredcorvus: awesome!21:13
corvusthat should be gtg now21:13
*** jamesmcarthur has quit IRC21:13
mordredcorvus: we should maybe get someone other than us to +2 that one21:14
corvusclarkb: ^ :)21:14
clarkb I'll look21:15
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Update testing section  https://review.opendev.org/67282021:17
openstackgerritClark Boylan proposed zuul/zuul-jobs master: Add note to clear-firewall docs  https://review.opendev.org/67282921:20
clarkbcorvus: mordred ^ do you think something like that makes sense there?21:20
clarkbI'm happy for it to be a follow on (I'm appriving the parent now)21:20
corvusi'd prefer to be as neutral as possible in zuul-jobs21:24
clarkbok21:26
*** zbr has joined #zuul21:26
corvusmaybe something more along the lines of "you may want to consult with your sysadmin blah blah policy" or something might accomplish what you want while not being opinionated?21:27
clarkbmight also be worth noting that ansible has an iptables module but I don't think it can express "clear everything"21:27
clarkbcorvus: let me a try a version of that21:27
corvusi think i'm tripping up on the "best option may be to modify the rules" because, wearing my opendev hat, i don't think we've ever promised that the "openstack-INPUT" chain is a stable interface :)21:28
*** pcaruana has quit IRC21:28
corvusmaybe i'm overthinking it though.  maybe that's okay.  it doesn't preclude "add your accept rule to the start of INPUT"21:29
openstackgerritClark Boylan proposed zuul/zuul-jobs master: Add note to clear-firewall docs  https://review.opendev.org/67282921:30
clarkbsomething like that maybe?21:30
corvusclarkb: +2.  i would also probably +2 PS1 at this point too.21:30
*** zbr has quit IRC21:32
*** panda has quit IRC21:34
*** panda has joined #zuul21:34
openstackgerritMerged zuul/zuul-jobs master: Add clear-firewall role  https://review.opendev.org/67278621:34
*** jamesmcarthur has joined #zuul21:46
openstackgerritJeff Liu proposed zuul/zuul-operator master: [WIP] Verify Operator Pod Running  https://review.opendev.org/67039521:48
openstackgerritMerged zuul/zuul-jobs master: Add note to clear-firewall docs  https://review.opendev.org/67282921:50
*** jamesmcarthur has quit IRC21:51
openstackgerritJeff Liu proposed zuul/zuul-operator master: [WIP] Verify Operator Pod Running  https://review.opendev.org/67039521:55
*** jeliu_ has quit IRC22:05
*** hwangbo has quit IRC22:17
openstackgerritJames E. Blair proposed zuul/zuul master: Remember tab location on build page  https://review.opendev.org/67283622:29
openstackgerritJames E. Blair proposed zuul/zuul master: Use base 1 line number anchors in log view  https://review.opendev.org/67283722:33
*** jamesmcarthur has joined #zuul22:38
*** jamesmcarthur has quit IRC22:44
mordredcorvus: https://www.npmjs.com/package/react-lazylog22:52
mordredcorvus: I was reading the convo between you and tristanC in https://review.opendev.org/#/c/671906/4/web/src/reducers/logfile.js@30 and it made me want to go trolling around a little bit22:54
*** jamesmcarthur has joined #zuul23:20
corvusmordred: that seems like it might be really close to what we want, but i'm not sure about things like adding support for severity23:20
corvusand the whole "only show me > debug" lines is apparently a well-liked feature of osla?23:21
corvusmaybe that's something that could be added?23:22
corvusi really like the chunked responses and "23:22
corvusAble to load large files upwards of 100MB without crashing the browser"23:22
*** jamesmcarthur has quit IRC23:24
corvusmordred: i wonder how close we could get the search/filtering feature of that to mimic it?23:24
corvuslike, have a button which does a search for "(?!DEBUG)"23:25
corvusmordred: i was just starting on importing some of the osla stuff, but since you found that, i'm going to clean up what i've done and push it up, and i think next step should be to replace the existing thing with that and see what it does23:26
corvusi'm going to EOD, so you or tristanC are welcome to try that tomorrow before i wake up if you want :)23:26
openstackgerritJames E. Blair proposed zuul/zuul master: Parse log file in action module  https://review.opendev.org/67283923:30
corvusmordred, tristanC: ^ if you want to stick lazylog on that and see how it looks, ++; if you don't get to it first, i can try that tomorrow.23:31
*** tjgresha has quit IRC23:31
*** sshnaidm is now known as sshnaidm|off23:43
*** hashar has quit IRC23:43
*** armstrongs has joined #zuul23:48
*** jamesmcarthur has joined #zuul23:50
*** jamesmcarthur has quit IRC23:55
*** smcginnis has quit IRC23:56
*** armstrongs has quit IRC23:58

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