logan- | one thing I'm noticing on 3.1, with authenticated_only: true, the config check job fails because it cannot download _defconf.tgz (it provides a redirect to the login gateway) | 00:58 |
---|---|---|
logan- | i'm also seeing a traceback/500 error when attempting to login with the local admin user on a new install http://paste.openstack.org/raw/725381/ | 00:58 |
tristanC | logan-: arg, it sounds like this option doesn't work anymore, i don't think we have tested it in a long time... | 01:12 |
tristanC | i can have a look. was it working in 3.0 ? | 01:13 |
logan- | yup | 01:40 |
gundalow | morning tristanC | 01:40 |
tristanC | gundalow: o/ | 01:42 |
gundalow | fbo|off: I corrected the tenant name, thanks for pointing that out https://github.com/ansible/zuul-config/commit/5485ede6e761305e7d781ccf8cbf2d728718cb02 | 01:46 |
gundalow | tristanC: So is the question: Should we have a single tenant called "ansible" which is used for github/ansible-network and github/ansible? | 01:47 |
tristanC | gundalow: the secret also needs to be re-encrypted, there is one private key per repo (https://github.com/ansible/zuul-config/blob/master/zuul.d/secrets.yaml needs to be changed too) | 01:48 |
gundalow | tristanC: I think I just copied that from network-engine | 01:49 |
tristanC | gundalow: i think a single ansible tenant would make sense | 01:49 |
gundalow | What could the potential downsides be? | 01:50 |
tristanC | gundalow: hum, conflict on the gate requirements pipeline | 01:50 |
sfbender | Logan V created software-factory/sf-config master: Allow _defconf.tgz download without authentication https://softwarefactory-project.io/r/12954 | 01:53 |
gundalow | If that's an issue in the future could it be worked around by defining the gate requirements in the individual repos (gh/ansible-network/zuul-network-jobs and gh/ansible/ansible)? | 01:55 |
tristanC | gundalow: well, there can only be one pipeline named "gate", but there could be a "gate-ansible-network" if needed | 01:56 |
tristanC | gundalow: having a single tenant would make the user interface simpler, there will be only one status page for both organization | 01:56 |
gundalow | Would having a single tenant mean if we have $vendorA added, then they could run ansible-network & and ansible/ansible Zuul jobs? | 01:58 |
gundalow | ie, only need one time setup and we'd have the ability to run jobs against all repos under the "ansible" tenant? | 01:58 |
tristanC | gundalow: any tenant could add a zuul-jobs project and be able to re-use the job. so it hink a $vendorA would still needs its own tenant | 01:59 |
tristanC | gundalow: the tenant scope mostly define 2 things, the base job (which handle logs server fqdn), and the pipelines (which define the github app to use) | 02:00 |
tristanC | those things are defined by the config projects of the tenant, e.g. that section: https://softwarefactory-project.io/cgit/config/tree/zuul/ansible_networking.yaml#n6 | 02:01 |
gundalow | ah, OK | 02:02 |
gundalow | How do you think we proceed? | 02:02 |
gundalow | How much of an issues is/could conflict on gate be? | 02:03 |
tristanC | gundalow: so if we want to do this, e.g. https://softwarefactory-project.io/r/12955 | 02:03 |
tristanC | gundalow: then I think we just have to move the pipelines and base jobs to ansible/zuul-config | 02:04 |
tristanC | and if we are going to do that refactor, then we should take this opportunity to create an ansible-zuul bot (e.g. attached to the ansible org) and configure it in sf-project.io zuul | 02:05 |
tristanC | e.g. move: | 02:06 |
tristanC | https://github.com/ansible-network/zuul-config/blob/master/zuul.d/jobs.yaml#L22-L61 | 02:07 |
tristanC | https://github.com/ansible-network/zuul-config/blob/master/zuul.d/pipelines.yaml#L1-L116 | 02:07 |
tristanC | https://github.com/ansible-network/zuul-config/blob/master/zuul.d/projects.yaml#L10-L13 | 02:07 |
tristanC | https://github.com/ansible-network/zuul-config/blob/master/zuul.d/secrets.yaml#L2-L51 | 02:07 |
gundalow | Yup, got most of that in https://github.com/ansible/zuul-config already | 02:08 |
tristanC | then the remaining bits can stay in a-n/z-c | 02:08 |
gundalow | Ah, cool, was going to ask if the a-n specific things can stay in that GH Org, ace | 02:08 |
tristanC | gundalow: yes, those shouldn't conflict as they are specifics to a-n | 02:09 |
tristanC | gundalow: so do you want to begin with re-using that softwarefactory-project-zuul default bot, or would it be better if the ansible org create its own bot that we configure in sf-project zuul? | 02:10 |
tristanC | (we'll just need a copy of its private key) | 02:11 |
tristanC | either way sound good to me, re-using the bot is easier to begin with, but since we are going to refactor, then it may be a good time to do that change now too | 02:13 |
*** corvus_ has joined #softwarefactory | 02:17 | |
*** corvus has quit IRC | 02:19 | |
*** rcarrillocruz has quit IRC | 02:19 | |
gundalow | tristanC: I added `softwarefactory-project-zuul` from your link last week and it's got permissions on ansible/{zuul-config,zuul-test-repo}` | 02:21 |
gundalow | I believe GH bots are linked to GH Orgs, so unsure how it can be shared across a-n and a. Or is that done on the SF side? | 02:22 |
tristanC | alright, then we should begin with that bot since it's already configured in sf's zuul | 02:23 |
tristanC | gundalow: iirc, the bot creator define who can install it where | 02:23 |
tristanC | e.g. the sf-p-zuul bot can be installed by anyone | 02:24 |
tristanC | it has been created in the softwarefactory-project org | 02:24 |
gundalow | and under "@ansible Repository access" it lists the two repos I mentioned | 02:24 |
tristanC | anyway, changing the botname can be done later down the road if needed | 02:25 |
gundalow | ack | 02:25 |
*** rcarrillocruz has joined #softwarefactory | 02:25 | |
tristanC | so, would you like to proceed with the ansible-network tenant rename and pipeline migration over to a/z-c today? | 02:26 |
gundalow | tristanC: I'm here for an hour or so (I'm west coast for the next ~6 weeks) | 02:26 |
gundalow | rcarrillocruz: Hi, you there? | 02:27 |
gundalow | hum, actually it's 04:30, so I hope he isn't | 02:27 |
tristanC | gundalow: what we can do is begin with a new ansible tenant to setup the zuul-config, then we can migrate ansible-network in a second step | 02:28 |
gundalow | tristanC: I think there will be some releases from network-engine withing the next 24 hours, so phased approach would be good if possible | 02:28 |
gundalow | cool | 02:29 |
gundalow | What should I do? | 02:29 |
tristanC | gundalow: i'm going to propose a couple change, one minute | 02:29 |
gundalow | Thanks :) | 02:29 |
tristanC | gundalow: https://github.com/ansible/zuul-config/pull/4 | 02:32 |
gundalow | What's `runc-fedora`? | 02:33 |
gundalow | oh, that's the default, so will be overritten by specific `nodeset` in later definitions. Merged | 02:34 |
tristanC | gundalow: i rewrote your config patch to use the new tenant resources definition, here is how it looks like: | 02:41 |
tristanC | remote: https://softwarefactory-project.io/r/12896 Add the ansible tenant | 02:41 |
tristanC | gundalow: the idea is that if we change the ansible tenant resource url to ansible.softwarefactory-project.io/manage | 02:43 |
tristanC | gundalow: then we'll be able to move that file directly in ansible/zuul-config, so that updating the zuul config can be managed directly from github, without needing to use sf-project gerrit config repo | 02:44 |
tristanC | gundalow: in the config-check logs, you can see what zuul configuration this generate, see the top of https://softwarefactory-project.io/logs/96/12896/5/check/config-check/5157305/logs/build/main.yaml | 02:45 |
tristanC | which sounds like what we proposed initialy | 02:45 |
gundalow | Should `projects: Ansible` be `ansible`, not sure if that's just a "friendly name", or it needs to match else where | 02:46 |
tristanC | gundalow: sure, let me update that | 02:47 |
gundalow | How in gerrit can I generate a diff between my last commit and the head of that branch? | 02:48 |
tristanC | there is a "Diff against" in the panel-title on top of the file list | 02:48 |
tristanC | or on the upper-right, you can load previous patchset | 02:49 |
gundalow | ah, got it, thanks | 02:49 |
tristanC | PS6 adds the missing exclude-unprotected-branch settings, it should be good now | 02:50 |
tristanC | let's approve this? | 02:52 |
gundalow | +1 | 02:53 |
tristanC | scheduler reconfiguration now begins | 02:56 |
tristanC | arg, ERROR zuul.Scheduler: Reconfiguration failed: ... github3.exceptions.NotFoundError: 404 Not Found | 02:58 |
tristanC | full stacktrace is https://ansible.softwarefactory-project.io/paste/show/14/ | 02:59 |
tristanC | are branch protections set for ansible/zuul-test-repo? | 03:00 |
tristanC | gundalow: ^ | 03:00 |
gundalow | tristanC: ah, no they were not. You may need to force it to re-read it. I don't think at the moment Zuul get's a reconfiguration event | 03:01 |
tristanC | ok, i removed the setting directly in scheduler configuration, reconfiguration is now resumed | 03:02 |
tristanC | though there have been a config error: https://ansible.softwarefactory-project.io/paste/show/15/ | 03:02 |
gundalow | ah, so that's my fault | 03:03 |
gundalow | Do I need to remove `sqlreporter:`? | 03:03 |
tristanC | it's ok, it just needs s/github/github.com/ | 03:03 |
tristanC | gundalow: now that the the project is registered in zuul, i'll proopose a change to add the logserver secret and fix those issue, one moment | 03:04 |
gundalow | ack | 03:04 |
tristanC | ah success, tenant is created https://softwarefactory-project.io/zuul/t/ansible/status.html | 03:07 |
tristanC | with the test-repo https://softwarefactory-project.io/zuul/t/ansible/project.html?project_name=ansible%2Fzuul-test-repo | 03:07 |
gundalow | \o/ | 03:08 |
tristanC | gundalow: PR in progress | 03:09 |
tristanC | https://github.com/ansible/zuul-config/pull/5 | 03:13 |
tristanC | (post_failure is normal since it needs the secret for logs upload) | 03:15 |
gundalow | tristanC: Thanks, merged | 03:17 |
tristanC | nice, no more config-errors, see https://softwarefactory-project.io/zuul/api/tenant/ansible/config-errors | 03:18 |
gundalow | \o/ | 03:18 |
tristanC | and the affected pipeline is now loaded, see https://softwarefactory-project.io/zuul/t/ansible/status.html | 03:18 |
gundalow | cool, got `third-party-check` now | 03:19 |
tristanC | and ansible/zuul-test-repo is now running jobs through the in-repo zuul.yaml | 03:19 |
gundalow | Yup, so now secrets have been added we should have uploaded logs | 03:21 |
tristanC | gundalow: so, the next step is to add the ansible-network project to the ansible tenant (excluding pipeline and base job) | 03:21 |
tristanC | gundalow: then we could drop ansible-network tenant and make the ansible.sf-project.io a white-label deployment for the ansible network | 03:21 |
tristanC | so that ansible.sf-project.io/zuul/ webui shows the ansible tenant status, jobs and builds | 03:22 |
gundalow | tristanC: What of "add the ansible-network project to the ansible tenant (excluding pipeline and base job)" can I do without impacting a-n? | 03:22 |
tristanC | white-label deployment for the ansible tenant* | 03:22 |
gundalow | ah, white-label = FOO.sf-project | 03:22 |
tristanC | gundalow: yes, this can live in parallel of ansible-network tenant configuration | 03:22 |
tristanC | gundalow: it can actually be any DNS, it's just the "/zuul/" that is scoped to a tenant | 03:23 |
gundalow | So I believe I've already got the base parent jobs in that were in a-n also in a, so not sure what's left for me to do there | 03:23 |
gundalow | since we said the a-n specific jobs & roles would stay in a-n/ansible-zuul-jobs/ | 03:24 |
tristanC | gundalow: well, we got that ansible tenant up and running, now let's wait for rcarrillocruz and maybe we should draft a story to explain the ins and outs of such merge | 03:24 |
gundalow | ah, as expected linters will fail on `zuul-test-repo/` | 03:24 |
tristanC | gundalow: you probably want a more custom linters job for the ansible project, that PR is to test zuul | 03:26 |
gundalow | Yup, just raising one | 03:26 |
gundalow | raised https://github.com/ansible/zuul-test-repo/pull/2 | 03:30 |
gundalow | hum, though nothing running, do I need `check` here https://github.com/ansible/zuul-test-repo/pull/2/files#diff-4b5c72a5ee79a9e4660a42ce20d9265fR6 | 03:31 |
tristanC | gundalow: the third-party-check should have kicked | 03:32 |
tristanC | gundalow: i wonder if adding non zuul configuration files to zuul.d cause problems | 03:32 |
gundalow | oh, the readme? | 03:33 |
*** Guest61318 has quit IRC | 03:34 | |
tristanC | and the playbooks, iirc only zuul configuration stanza should be present in the zuul.d folder | 03:34 |
tristanC | also iirc roles needs to be at the root of the projects | 03:35 |
*** Guest61318 has joined #softwarefactory | 03:35 | |
*** corvus_ is now known as corvus | 03:36 | |
gundalow | ok, I'll move .zuul.d/playbooks to test/utils/zuul/playbooks | 03:36 |
*** corvus is now known as Guest78457 | 03:37 | |
*** Guest78457 is now known as jeblair | 03:38 | |
gundalow | tristanC: hum, that's annoying if I have to have `./roles/` in the root of the repo | 03:38 |
tristanC | gundalow: i think we need a zuul feature to be able to support custom path | 03:40 |
tristanC | gundalow: perhaps those zuul jobs roles could exists in a ansible/zuul-jobs project? | 03:40 |
gundalow | My hope was to keep as much in a/a, so the tests are versioned along side what they are testing | 03:40 |
tristanC | https://zuul-ci.org/docs/zuul/user/config.html#attr-job.roles | 03:41 |
gundalow | I'm happy to have it in the root of `ansible-zuul-jobs/`, though it can't go in the root of ansible/ansible | 03:41 |
tristanC | gundalow: it's a frequent request, i think we could add a "path" to the job.roles attribute to be able support role not stored at the root of the project | 03:42 |
*** jeblair is now known as corvus | 03:43 | |
gundalow | Updated https://github.com/ansible/zuul-test-repo/pull/2 | 03:49 |
tristanC | gundalow: could you try adding the job to "check" instead? i have to go afk now, i'll have a look at that third-party-check pipeline configuration | 03:52 |
gundalow | Sure | 03:53 |
gundalow | tristanC: Thanks again for all your help! | 03:55 |
gundalow | tristanC: I need to head off now, I've given you commit powers on the two repos. You should be able to push changes to my PRs. | 04:41 |
tristanC | gundalow: alright, i'll write a story with a merge plan to make sure it make sense and works for everyone | 04:45 |
gundalow | tristanC: Sounds like a plan, thanks again :) | 04:46 |
tristanC | you're welcome! | 04:49 |
tristanC | gundalow: rcarrillocruz: here is an initial migration plan draft: https://tree.taiga.io/project/morucci-software-factory/us/1484 | 05:06 |
*** Guest61318 has quit IRC | 05:44 | |
*** Guest61318 has joined #softwarefactory | 05:53 | |
*** apevec has joined #softwarefactory | 06:57 | |
*** apevec has joined #softwarefactory | 06:57 | |
*** fbo|off is now known as fbo | 07:28 | |
*** Guest61318 has quit IRC | 09:10 | |
*** jangutter has quit IRC | 09:15 | |
rcarrillocruz | tristanC , gundalow : wfm | 09:25 |
*** Guest61318 has joined #softwarefactory | 09:25 | |
*** jangutter has joined #softwarefactory | 09:35 | |
*** Guest61318 has quit IRC | 10:03 | |
sfbender | Merged software-factory/sf-docs master: Add GitHub deployment guide. https://softwarefactory-project.io/r/12105 | 10:15 |
*** yassine has joined #softwarefactory | 11:09 | |
*** yassine is now known as Guest88425 | 11:09 | |
sfbender | Merged software-factory/sf-config master: repos: add patch and review sync strategy https://softwarefactory-project.io/r/12929 | 13:52 |
gundalow | tristanC: looks good. Is it worth adding a) white-label b) role custom path (need this before it can go into a/a) | 14:16 |
*** EmilienM is now known as EvilienM | 14:42 | |
jruzicka | I have a bounty for person who reveals to me why OrderedDict is acting non-deterministically on python3 only here: https://softwarefactory-project.io/r/#/c/12882/ | 14:57 |
jruzicka | mhu, heeeey buddy ^^ | 14:57 |
*** Guest88425 has quit IRC | 16:00 | |
*** fbo is now known as fbo|off | 16:44 | |
sfbender | Fabien Boucher created software-factory/sf-config master: sf-config depends on PyYAML make sure it is installed https://softwarefactory-project.io/r/12965 | 16:57 |
sfbender | Merged software-factory/sf-config master: log-classify: add a dedicated component https://softwarefactory-project.io/r/12930 | 17:18 |
sfbender | Fabien Boucher created software-factory/sf-docs master: doc: fix remaining references to OCI instead of RunC https://softwarefactory-project.io/r/12966 | 17:24 |
*** apevec_ has joined #softwarefactory | 20:43 | |
*** apevec_ has quit IRC | 20:43 | |
*** apevec_ has joined #softwarefactory | 20:43 | |
*** apevec has quit IRC | 20:45 | |
*** Guest88425 has joined #softwarefactory | 20:54 | |
*** apevec_ has quit IRC | 21:08 | |
gundalow | tristanC: Any ideas why https://github.com/ansible/zuul-test-repo/pull/2 isn't triggering? It's using `check` (rather than `third-party-check`) | 23:16 |
pabelanger | gundalow: possible you have a syntax error in your job configuration, but zuul isn't reporting it back. You could add https://zuul-ci.org/docs/zuul/user/config.html#attr-project.%3Cpipeline%3E.debug to the pipeline to get extra debug information | 23:41 |
pabelanger | gundalow: basically, if you add a simple job to check pipeline first, then rebase pull/2 once merged, zuul should report back why it is failing | 23:41 |
pabelanger | something we need to fix in zuul | 23:42 |
gundalow | ah, I'll change to `noop` with debug, great idea, thanks | 23:42 |
pabelanger | I'm not sure i have access to zuul logs, otherwise I'd dive into it more | 23:43 |
*** Guest88425 has quit IRC | 23:51 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!