| *** gtema has joined #openstack-ansible-sig | 00:34 | |
| *** spatel has joined #openstack-ansible-sig | 00:34 | |
| *** gtema has quit IRC | 00:38 | |
| *** gtema has joined #openstack-ansible-sig | 02:34 | |
| *** gtema has quit IRC | 02:40 | |
| *** spatel has quit IRC | 03:23 | |
| *** evrardjp has quit IRC | 05:34 | |
| *** evrardjp has joined #openstack-ansible-sig | 05:34 | |
| *** gtema has joined #openstack-ansible-sig | 06:37 | |
| *** gtema has quit IRC | 06:41 | |
| *** gtema has joined #openstack-ansible-sig | 07:46 | |
| *** gtema has quit IRC | 07:51 | |
| *** gtema has joined #openstack-ansible-sig | 07:52 | |
| *** priteau has joined #openstack-ansible-sig | 08:28 | |
| *** dtantsur|afk is now known as dtantsur | 09:12 | |
| *** sshnaidm|afk is now known as sshnaidm | 09:25 | |
| *** priteau has quit IRC | 10:28 | |
| odyssey4me | hey folks, I've updated https://review.opendev.org/#/c/697278/ to reflect the new meeting time - please review when you have the chance | 10:40 |
|---|---|---|
| noonedeadpunk | +1 | 10:53 |
| *** priteau has joined #openstack-ansible-sig | 11:03 | |
| *** dtantsur is now known as dtantsur|brb | 12:27 | |
| *** gtema has quit IRC | 13:35 | |
| *** dtantsur|brb is now known as dtantsur | 13:49 | |
| *** gtema has joined #openstack-ansible-sig | 14:13 | |
| *** spatel has joined #openstack-ansible-sig | 14:37 | |
| *** gtema has quit IRC | 14:37 | |
| *** gtema has joined #openstack-ansible-sig | 14:38 | |
| *** spatel has quit IRC | 14:41 | |
| sshnaidm | openstack ansible modules meeting in a few mins, please feel free to add your topics to agenda: https://etherpad.openstack.org/p/openstack-ansible-modules | 14:57 |
| sshnaidm | #startmeeting ansible-sig | 15:01 |
| openstack | Meeting started Tue Feb 11 15:01:39 2020 UTC and is due to finish in 60 minutes. The chair is sshnaidm. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| *** openstack changes topic to " (Meeting topic: ansible-sig)" | 15:01 | |
| dtantsur | o/ | 15:01 |
| openstack | The meeting name has been set to 'ansible_sig' | 15:01 |
| sshnaidm | who is available today | 15:02 |
| sshnaidm | dtantsur, hey | 15:02 |
| gtema | me in 10 minutes | 15:02 |
| sshnaidm | ack | 15:03 |
| dtantsur | sshnaidm: I suggest you ping people explicitly | 15:03 |
| dtantsur | it's easy to forget about the changed time | 15:03 |
| sshnaidm | ok, maybe we need to maintain a list of people :) | 15:03 |
| dtantsur | ping whoever responded about the time :) | 15:04 |
| sshnaidm | mordred, mnaser cloudnull odyssey4me noonedeadpunk jrosser | 15:04 |
| jrosser | o/ hello | 15:04 |
| noonedeadpunk | o/ | 15:04 |
| mordred | sshnaidm: this is the new time then I suppose? :) | 15:04 |
| sshnaidm | I'm taking names from etherpad, maybe not all are in this channel | 15:04 |
| sshnaidm | mordred, yes! | 15:04 |
| sshnaidm | new time, convenient for all now | 15:05 |
| sshnaidm | and new place | 15:05 |
| dtantsur | yeah, the API SIG slot was occupied temporarily :) | 15:05 |
| cloudnull | o/ | 15:06 |
| sshnaidm | just a reminder, the agenda is in | 15:06 |
| sshnaidm | #link https://etherpad.openstack.org/p/openstack-ansible-modules | 15:06 |
| sshnaidm | feel free to add there | 15:06 |
| sshnaidm | so moving on | 15:06 |
| sshnaidm | first item - pushing a first version of collection to galaxy | 15:07 |
| *** gtema_ has joined #openstack-ansible-sig | 15:07 | |
| sshnaidm | I'd propose to do it manually now so people can start testing/using it | 15:07 |
| dtantsur | does galaxy have any sort of alpha versions? | 15:07 |
| mordred | sshnaidm: oh yeah - I was gonna connect with you on getting that set up once I was back in real life | 15:08 |
| sshnaidm | mordred, great | 15:08 |
| sshnaidm | dtantsur, well, it has versioning | 15:08 |
| sshnaidm | dtantsur, but if you want to install something before 1.0.0 you need to set an explicit version | 15:08 |
| dtantsur | ah! nice | 15:08 |
| mordred | cool., so we can install this manual test one as 0.1 | 15:09 |
| sshnaidm | (there is a request to change it from Paul to have *) | 15:09 |
| dtantsur | (sorry, my knowledge of ansible is very spotty) | 15:09 |
| sshnaidm | mordred, yeah, maybe not to release it until it's removed from ansible upstream | 15:09 |
| * sshnaidm stairs on gundalow | 15:09 | |
| dtantsur | they don't conflict, do they? | 15:10 |
| *** gtema has quit IRC | 15:10 | |
| sshnaidm | dtantsur, if shortly - it's complicated | 15:10 |
| dtantsur | I think it's actually good to collect feedback before ansible presses the big red button? | 15:10 |
| noonedeadpunk | I'd say it would be great to have some migration time on hands | 15:10 |
| sshnaidm | dtantsur, absolutely, the sooner we can use collection the better | 15:10 |
| sshnaidm | noonedeadpunk, sorry, what do you mean? | 15:11 |
| noonedeadpunk | Like be able to start using some "stable" collections before ansible got modules dropped from their root | 15:11 |
| sshnaidm | noonedeadpunk, I'm not sure people use devel branch of ansible | 15:12 |
| sshnaidm | noonedeadpunk, but for better safety - yes, of course | 15:12 |
| sshnaidm | btw the patch to do this: | 15:12 |
| sshnaidm | #link https://github.com/ansible/ansible/pull/66790 | 15:13 |
| sshnaidm | noonedeadpunk, it affects 2.10 only and currently it's devel branch | 15:13 |
| sshnaidm | ok, so I think we have an agreement here | 15:13 |
| odyssey4me | o/ | 15:13 |
| sshnaidm | #action sshnaidm to be in touch with mordred to push the first version of collection to galaxy | 15:14 |
| sshnaidm | mordred, let's please schedule a time for it | 15:14 |
| sshnaidm | mordred, just ping me whenever you're available | 15:14 |
| sshnaidm | any objections, comments about this topic? | 15:15 |
| mordred | sshnaidm: will do - we can do it this week - first step is I need to make sure I know how to log in myself :) | 15:15 |
| sshnaidm | mordred, ack :) | 15:15 |
| sshnaidm | mordred, I pushed something to my accounts, so should be fine | 15:15 |
| sshnaidm | we also have stage version of galaxy to play there | 15:15 |
| sshnaidm | (nice thing, btw ^^ ) | 15:16 |
| sshnaidm | ok, moving on | 15:16 |
| sshnaidm | I need an advice from infra or people that did releases, how do I run job after patch is merged? Should I use something like post-merge pipeline..? | 15:16 |
| sshnaidm | I'd happy to receive examples of tag/release jobs in openstack to learn from, or link to docs | 15:17 |
| dtantsur | the release team has a release pipeline, dunno if we can use it | 15:17 |
| mordred | yes - release pipeline - or we might want to use the promote pipeline instead | 15:18 |
| sshnaidm | as I understand we need to run build job, pass artifacts to child functional jobs, then merge it, but then to push collection to galaxy | 15:18 |
| mordred | release pipeline is for running jobs after a tag event | 15:18 |
| sshnaidm | mordred, so we agreed to use tags before, maybe release pipeline is what we want here? | 15:18 |
| sshnaidm | mordred, to define pushing job in release pipeline? | 15:19 |
| mordred | yes- if we're going to be pushing to galaxy on tag events, it should go in release pipeline | 15:19 |
| sshnaidm | ok | 15:19 |
| sshnaidm | so I'll focus on build&test jobs right now, we still have time before pushing anything.. | 15:20 |
| sshnaidm | dtantsur, do you use tagged releases in ironic? | 15:20 |
| dtantsur | sshnaidm: all official projects do, I think | 15:20 |
| dtantsur | and most non-official | 15:20 |
| sshnaidm | dtantsur, I see | 15:21 |
| sshnaidm | any other ideas how to organize jobs for build & push or related topics? | 15:22 |
| sshnaidm | if no, then moving on | 15:22 |
| dtantsur | sshnaidm: similarly to upstream release procedure, create a check job to verify you can release | 15:22 |
| dtantsur | I mean, do most of verifications before you try to build and upload something | 15:23 |
| dtantsur | (for python projects it's stuff like setup.cfg validation) | 15:23 |
| sshnaidm | dtantsur, what kind of verifications? | 15:23 |
| sshnaidm | dtantsur, I think in this case it will be galaxy.yml verification | 15:24 |
| dtantsur | yeah, for example this | 15:24 |
| *** spatel has joined #openstack-ansible-sig | 15:24 | |
| dtantsur | I'm not familiar with ansible packaging to be sure | 15:24 |
| sshnaidm | it's actually responsible for pushing | 15:24 |
| sshnaidm | yeah, it's kind of setup.cfg+requirements.txt, but for ansible | 15:24 |
| dtantsur | right | 15:24 |
| sshnaidm | ack, noted | 15:25 |
| sshnaidm | ok, moving on | 15:25 |
| sshnaidm | Openstack Ansible modules on PTG - is there intererest to have a discussion/session/track there? Should it be part of SDK session or other? | 15:25 |
| dtantsur | 1. Yes, 2. Depending on the overall format? | 15:25 |
| gtema_ | 1 - yes | 15:26 |
| sshnaidm | as I saw, and mordred can confirm, we have something like "Tracks" now..? Maybe it can be used? | 15:26 |
| mordred | shrug - I do not know ... I'd be more than happy for there to be some sort of meeting if people will be in vancouver | 15:26 |
| mordred | otoh - if people are not going to be in vancouver, then it's not super awesome :) | 15:27 |
| dtantsur | sshnaidm: if we can, say, dedicate 1-2 slots, then we can go independent | 15:27 |
| dtantsur | if it must be a part of some wider track, I guess we can go with the SDK | 15:27 |
| dtantsur | mordred: many of us won't know until much later :( | 15:27 |
| sshnaidm | mordred, let's hope and plan for good | 15:27 |
| sshnaidm | it's easier to remove tracks than to search for adding them later | 15:28 |
| mordred | good point | 15:28 |
| sshnaidm | do you know if SDK has its own space? | 15:29 |
| sshnaidm | like room and hours | 15:29 |
| mordred | and I agree with dtantsur - either just grab 1-2 slots, or we can make an SDK track | 15:29 |
| mordred | sshnaidm: I don't think we've requested anything | 15:29 |
| sshnaidm | mordred, how to "grab slots" actually? | 15:29 |
| sshnaidm | what is the procedure | 15:30 |
| sshnaidm | ok, I think we can discover this later then | 15:30 |
| sshnaidm | I think we agree on 1-2 slots and that's fine | 15:31 |
| sshnaidm | ok, open discussion then | 15:31 |
| sshnaidm | do you have something to talk about? | 15:31 |
| dtantsur | I think the first step is to say "yes, we're going to be present" out loud | 15:32 |
| sshnaidm | dtantsur, and together | 15:32 |
| sshnaidm | ok, so if no other topics, I think we're good? | 15:33 |
| sshnaidm | thanks everyone to participation | 15:34 |
| mordred | sshnaidm: I'll see what I can find out about getting track slots | 15:34 |
| sshnaidm | mordred, great, thanks | 15:34 |
| sshnaidm | #endmeeting | 15:34 |
| *** openstack changes topic to "OpenStack Ansible SIG | https://etherpad.openstack.org/p/ansible-sig" | 15:34 | |
| openstack | Meeting ended Tue Feb 11 15:34:23 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:34 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ansible_sig/2020/ansible_sig.2020-02-11-15.01.html | 15:34 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ansible_sig/2020/ansible_sig.2020-02-11-15.01.txt | 15:34 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ansible_sig/2020/ansible_sig.2020-02-11-15.01.log.html | 15:34 |
| sshnaidm | gtema_, did you have a chance to check the issue with tags and images patch? | 15:35 |
| gtema_ | not yet | 15:35 |
| sshnaidm | gtema_, ack | 15:35 |
| sshnaidm | gundalow, when you're available, tell please if you have any updates from ansible about migration and removing code, if there're such of course | 15:37 |
| jrosser | in openstack-ansible we're currently blocked moving beyond ansible 2.8 due to ansible bugs | 15:38 |
| jrosser | thats going to get in the way of testing out any of the new modules - any help we can get there to unstick things would be great | 15:38 |
| sshnaidm | jrosser, can you use collections with 2.8? | 15:39 |
| sshnaidm | I think it was introduced in 2.8 | 15:40 |
| jrosser | yeah thats when the collections keyword came in | 15:40 |
| sshnaidm | jrosser, so I think you can still enjoy new modules when they appear as collection? | 15:42 |
| jrosser | probably, if everything needed / bugs are fixed in 2.8 | 15:43 |
| sshnaidm | jrosser, just curios, which OS modules do you use from ansible? | 15:45 |
| noonedeadpunk | can you remind me if collections names will differ from old style modules? I can recall some naming convention discussion but do not recall it results | 15:45 |
| jrosser | sshnaidm: lots of them - i pick one file out of many many roles we have here https://github.com/openstack/openstack-ansible-os_glance/blob/master/tasks/service_setup.yml | 15:46 |
| noonedeadpunk | also we do use os_image in many places and much more in specific roles (like working on adding os_coe_cluster_template to magnum role) | 15:47 |
| jrosser | i figured here was a good a place as any to raise general issues we're having with ansible in the context of openstack | 15:48 |
| gundalow | sshnaidm: hi. 1) We (Ansible) are currently working out what the final steps are before we can start deleting content from ansibe/ansible:devel. 2) Ansible-base (what Ansible/ansible will become) is taking change, once that's stable you can use that for CI, rather than devel. | 16:07 |
| sshnaidm | gundalow, thanks a lot for an update | 16:08 |
| gundalow | Nps | 16:09 |
| *** dtantsur is now known as dtantsur|afk | 16:34 | |
| sshnaidm | jrosser, I'd suggest to check the option to run your jobs that use os_image on changes of os_image modules in collections | 16:39 |
| *** priteau has quit IRC | 17:00 | |
| odyssey4me | jrosser: well, if you're able to start posting fixes into the collection then we can help get those reviewed and merged right here (and you get to review in gerrit) | 17:34 |
| *** evrardjp has quit IRC | 17:34 | |
| *** evrardjp has joined #openstack-ansible-sig | 17:34 | |
| odyssey4me | jrosser: once that's done, we've got support to get backports merged quite quickly into 2.9 when they're proposed and merged in the collection | 17:34 |
| odyssey4me | jrosser: so, if OSA is able to jump over 2.8 to 2.9 then we'll be able to help get past the stall | 17:35 |
| odyssey4me | jrosser: also, if some of the stall are non OpenStack modules then I know gundalow is keen to find maintainers for modules, they'll be moved into collections and handled much the same way to increase review velocity and enable independent releasing | 17:37 |
| *** gtema_ has quit IRC | 17:39 | |
| *** spatel has quit IRC | 17:50 | |
| jrosser | odyssey4me: we can't get to 2.9 becasue of ansible bug in rabbitmq modules, as OSA is now on rabbit 3.8 | 18:08 |
| jrosser | we're on 2.8.8 right now but there is a risk thats where we will still be for V cycle | 18:09 |
| odyssey4me | jrosser: that's bothersome - perhaps gundalow can share whether there've been volunteers to pick up those modules in a collection yet tomorrow... otherwise him and I spoke about the plans for shifting 'orphaned' modules into collections too, and maybe we can get that going to get you guys fixed up faster | 19:00 |
| odyssey4me | jrosser: otherwise there is the option of vendoring the modules in the OSA rabbitmq role and carrying that for a while... but it is a slippery slope | 19:01 |
| jrosser | indeed it is | 19:04 |
| jrosser | we sit triage it and noonedeadpunk made a PR with a fix | 19:05 |
| jrosser | *did | 19:05 |
| jrosser | rabbitmqctl output has changed and the module trips up parsing the different text | 19:05 |
| *** gtema has joined #openstack-ansible-sig | 19:15 | |
| noonedeadpunk | Actually there's even better PR there which is also not merged (but it's not passing CI iirc) - which moves module from using cli to a more reliable API. | 19:46 |
| noonedeadpunk | but yeah - it would be great to find volunteers for it. otherwise.... maybe we can try adding it to opendev as well? As carrying inside OSA is pretty much the same, except missing possible contributions... | 19:48 |
| *** gtema has quit IRC | 20:23 | |
| *** owalsh has quit IRC | 20:30 | |
| *** owalsh has joined #openstack-ansible-sig | 20:44 | |
| *** spatel has joined #openstack-ansible-sig | 21:18 | |
| *** spatel has quit IRC | 21:22 | |
| mordred | noonedeadpunk, jrosser: if we want to adopt the collection, it should be easy enough to suck into opendev | 21:51 |
| mordred | (as we're figuring out the pattern for that with openstack) | 21:51 |
| odyssey4me | mordred noonedeadpunk jrosser we could, but it might make sense to reach out to the folks who make rabbitmq to help contribute/review | 21:56 |
| odyssey4me | it would be possible to actually make them owners with the collection model, and we could contribute while they review & maintain | 21:57 |
| mordred | totally | 21:59 |
| mordred | whichever way makes sense for people | 21:59 |
| jrosser | if the rabbit folk were up for it that would be he most obvious route | 21:59 |
| mordred | also - the two things aren't mutually exclusive - we can host or not host the code and CI over here in opendev, and we can do that with or without the participation of the rabbit folks ... all of the options are workable depending on what various humans want | 22:00 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!