| *** csmart has quit IRC | 00:24 | |
| *** csmart has joined #openstack-ansible | 00:30 | |
| *** markvoelker has joined #openstack-ansible | 00:46 | |
| *** markvoelker has quit IRC | 00:51 | |
| *** poopcat has quit IRC | 01:02 | |
| *** poopcat has joined #openstack-ansible | 01:12 | |
| *** radeks has quit IRC | 01:15 | |
| *** threestrands has joined #openstack-ansible | 01:37 | |
| *** poopcat has quit IRC | 03:12 | |
| *** poopcat has joined #openstack-ansible | 03:14 | |
| *** gkadam has joined #openstack-ansible | 03:50 | |
| *** raukadah is now known as chandankumar | 04:59 | |
| *** udesale has joined #openstack-ansible | 04:59 | |
| *** Garyx has quit IRC | 05:07 | |
| *** Garyx has joined #openstack-ansible | 05:09 | |
| *** dr_feelgood has joined #openstack-ansible | 05:18 | |
| *** ivve has joined #openstack-ansible | 05:35 | |
| *** prometheanfire has quit IRC | 05:39 | |
| *** dr_feelgood has quit IRC | 05:55 | |
| *** prometheanfire has joined #openstack-ansible | 05:57 | |
| *** dr_feelgood has joined #openstack-ansible | 06:04 | |
| *** miloa has joined #openstack-ansible | 06:04 | |
| miloa | Morning | 06:04 |
|---|---|---|
| *** dr_feelgood has quit IRC | 06:05 | |
| *** dr_feelgood has joined #openstack-ansible | 06:06 | |
| *** cshen has joined #openstack-ansible | 06:23 | |
| jrosser | Morning | 06:26 |
| *** radeks has joined #openstack-ansible | 06:31 | |
| evrardjp | miloa: I have seen it :) | 06:44 |
| evrardjp | mnaser: my exact point :) | 06:44 |
| evrardjp | the only thing you should be caring if you are on queens is the time to upgrade :) | 06:45 |
| evrardjp | let me post something on the ML maybe? | 06:45 |
| evrardjp | jrosser: oh noes | 06:45 |
| evrardjp | jrosser: we need to check with infra how mirroring is done for those maybe? | 06:46 |
| jrosser | I dig around the system-config repo but imho someone who knows that stuff could do it quickly | 06:47 |
| jrosser | And yes, we should, this isn’t the first time the erlang repo has broken, I expect their update process is flawed | 06:48 |
| evrardjp | jrosser: I think things have been reshuffled recently with a new role that's why I am asking | 06:48 |
| evrardjp | I am not really sure what's going on, I didn't get the chance to look at it | 06:48 |
| evrardjp | worth asking in infra | 06:48 |
| *** tridde has quit IRC | 07:00 | |
| *** pcaruana has joined #openstack-ansible | 07:06 | |
| *** trident has joined #openstack-ansible | 07:09 | |
| *** threestrands has quit IRC | 07:18 | |
| ChosSimbaOne | Morning | 07:21 |
| miloa | evrardjp: ok :) | 07:23 |
| prometheanfire | probably too late now, but no one is running for PTL? | 07:27 |
| *** jbadiapa has quit IRC | 07:40 | |
| *** luksky has joined #openstack-ansible | 07:40 | |
| *** kopecmartin|off is now known as kopecmartin | 07:44 | |
| *** jbadiapa has joined #openstack-ansible | 07:56 | |
| *** omegapoint has joined #openstack-ansible | 08:11 | |
| *** mgoddard has joined #openstack-ansible | 08:13 | |
| *** chandankumar has quit IRC | 09:18 | |
| *** chandankumar has joined #openstack-ansible | 09:19 | |
| *** SmearedBeard has joined #openstack-ansible | 09:31 | |
| *** dr_feelgood has quit IRC | 09:32 | |
| noonedeadpunk | hi everyone | 09:55 |
| *** dr_feelgood has joined #openstack-ansible | 09:57 | |
| jrosser | hello | 10:06 |
| *** cshen has quit IRC | 10:06 | |
| *** cshen has joined #openstack-ansible | 10:07 | |
| noonedeadpunk | so, we still have broken gates due to rdo? | 10:18 |
| jrosser | this seems to be going ok so far https://review.opendev.org/#/c/678121/ | 10:21 |
| noonedeadpunk | It's more lucky than https://review.opendev.org/#/c/679487/ :) | 10:25 |
| *** SmearedBeard has quit IRC | 10:31 | |
| *** SmearedBeard has joined #openstack-ansible | 10:32 | |
| *** sep has quit IRC | 10:43 | |
| *** sep has joined #openstack-ansible | 10:44 | |
| *** tosky has joined #openstack-ansible | 10:45 | |
| *** dave-mccowan has joined #openstack-ansible | 11:00 | |
| *** SmearedBeard has quit IRC | 11:02 | |
| *** SmearedBeard has joined #openstack-ansible | 11:03 | |
| *** SmearedBeard has quit IRC | 11:05 | |
| *** dave-mccowan has quit IRC | 11:06 | |
| *** luksky has quit IRC | 11:08 | |
| *** markvoelker has joined #openstack-ansible | 11:09 | |
| *** markvoelker has quit IRC | 11:14 | |
| *** nicolasbock has joined #openstack-ansible | 11:19 | |
| *** udesale has quit IRC | 11:37 | |
| *** Garyx has quit IRC | 11:38 | |
| *** Garyx has joined #openstack-ansible | 11:41 | |
| *** Garyx has quit IRC | 11:41 | |
| *** Garyx has joined #openstack-ansible | 11:41 | |
| *** udesale has joined #openstack-ansible | 11:51 | |
| *** ansmith_ has quit IRC | 11:57 | |
| openstackgerrit | Merged openstack/openstack-ansible stable/stein: Generate static ARA report when necessary https://review.opendev.org/678121 | 12:11 |
| *** markvoelker has joined #openstack-ansible | 12:18 | |
| *** grabes has joined #openstack-ansible | 12:28 | |
| *** weshay has joined #openstack-ansible | 12:34 | |
| *** gkadam has quit IRC | 12:37 | |
| *** ansmith_ has joined #openstack-ansible | 12:40 | |
| *** redrobot has quit IRC | 12:55 | |
| *** dmsimard has quit IRC | 12:56 | |
| *** dmsimard has joined #openstack-ansible | 12:58 | |
| *** pcaruana has quit IRC | 13:03 | |
| *** nikparasyr has joined #openstack-ansible | 13:08 | |
| *** spatel has joined #openstack-ansible | 13:10 | |
| *** luksky has joined #openstack-ansible | 13:16 | |
| *** Garyx has quit IRC | 13:30 | |
| *** pcaruana has joined #openstack-ansible | 13:34 | |
| *** redrobot_ has joined #openstack-ansible | 13:36 | |
| *** redrobot_ is now known as redrobot | 13:37 | |
| *** KeithMnemonic has joined #openstack-ansible | 13:44 | |
| *** pcaruana has quit IRC | 13:47 | |
| *** pcaruana has joined #openstack-ansible | 13:59 | |
| guilhermesp | ahr i think trunk.rdoproject.org is pretty broken https://0d4c1f60ed6964ae5421-db27ff2acfdeb419005f6fa604a629e4.ssl.cf5.rackcdn.com/679496/6/check/openstack-ansible-deploy-aio_lxc-centos-7/e6ce5f7/job-output.txt | 14:00 |
| dmsimard | guilhermesp: the server's disks were destroyed by an outage, the data is being sync'd back and there's a DNS change in flight to point to a new machine | 14:03 |
| *** Garyx has joined #openstack-ansible | 14:03 | |
| guilhermesp | ahh that explains then. Thanks for the update dmsimard | 14:03 |
| noonedeadpunk | guilhermesp: yeah, I'd say that we still have these problems... | 14:03 |
| guilhermesp | i guess it's time to wait the sync | 14:03 |
| dmsimard | See this thread for details: https://lists.rdoproject.org/pipermail/dev/2019-September/009134.html | 14:04 |
| guilhermesp | ++ | 14:05 |
| *** pcaruana has quit IRC | 14:07 | |
| *** omegapoint has quit IRC | 14:09 | |
| *** pcaruana has joined #openstack-ansible | 14:10 | |
| *** udesale has quit IRC | 14:20 | |
| *** udesale has joined #openstack-ansible | 14:21 | |
| *** spatel has quit IRC | 14:41 | |
| *** Garyx has quit IRC | 14:47 | |
| *** Garyx has joined #openstack-ansible | 14:52 | |
| *** cshen has quit IRC | 14:57 | |
| noonedeadpunk | does anyone use your barbican role? | 15:02 |
| noonedeadpunk | s/your/our/ | 15:02 |
| noonedeadpunk | Since I'd say that https://opendev.org/openstack/openstack-ansible-os_barbican/src/branch/master/defaults/main.yml#L52 are missing worker and keystone-listener.... | 15:04 |
| noonedeadpunk | So I'm trying to get if it's a bug or these services are not required... | 15:04 |
| noonedeadpunk | While they are present for a while https://docs.openstack.org/barbican/rocky/install/install-ubuntu.html#finalize-installation | 15:05 |
| openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_barbican master: Start using uWSGI role https://review.opendev.org/679804 | 15:09 |
| *** luksky has quit IRC | 15:13 | |
| redrobot | noonedeadpunk, I'm not sure what the default config for Barbican is on #openstack-ansible. Barbican can do order processing immediately or they can be queued. If orders are configured to be queued (eg. via rabbit) then barbican-worker is requried, or else the orders will be pending forever. | 15:18 |
| redrobot | noonedeadpunk, keystone-listener is optional. It cleans up database entries, e.g. when a project is deleted from Keystone, resources in barbican can be cleaned up. | 15:18 |
| noonedeadpunk | redrobot: so our template for barbican is following https://opendev.org/openstack/openstack-ansible-os_barbican/src/branch/master/templates/barbican.conf.j2 | 15:19 |
| noonedeadpunk | Can you point me please to options in docs how to enable/disable orders queue? | 15:20 |
| *** kaiokmo has joined #openstack-ansible | 15:23 | |
| noonedeadpunk | Ad do I need to enable https://docs.openstack.org/barbican/latest/configuration/keystone.html for usage of keystone-listener? | 15:26 |
| *** pcaruana has quit IRC | 15:27 | |
| *** chandankumar is now known as raukadah | 15:32 | |
| *** kaiokmo has quit IRC | 15:33 | |
| redrobot | noonedeadpunk, no, that config doc is for Barbican to be able to verify incoming (client) tokens. | 15:33 |
| redrobot | noonedeadpunk, keystone-listener consumes CADF events from Keystone | 15:33 |
| *** kaiokmo has joined #openstack-ansible | 15:36 | |
| *** tosky_ has joined #openstack-ansible | 15:40 | |
| *** tosky has quit IRC | 15:41 | |
| *** tosky_ is now known as tosky | 15:41 | |
| redrobot | noonedeadpunk, I can't remember how the async order stuff is configured. Let me dig into it a bit and get back to you. | 15:44 |
| *** udesale has quit IRC | 15:47 | |
| noonedeadpunk | yeah sure. I just want patch OSA top allow deployers easily enable these services since now it might be really very tricky | 15:52 |
| guilhermesp | noonedeadpunk: I used recently the role in a deployment but I haven't tested at all tbh | 15:58 |
| evrardjp | o/ | 16:03 |
| tiffanie | #startmeeting openstack_ansible_meeting | 16:03 |
| openstack | Meeting started Tue Sep 3 16:03:59 2019 UTC and is due to finish in 60 minutes. The chair is tiffanie. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:04 |
| *** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)" | 16:04 | |
| openstack | The meeting name has been set to 'openstack_ansible_meeting' | 16:04 |
| mnaser | Hi all | 16:04 |
| noonedeadpunk | o/ | 16:04 |
| tiffanie | #topic office hours | 16:04 |
| *** openstack changes topic to "office hours (Meeting topic: openstack_ansible_meeting)" | 16:04 | |
| mnaser | How's everyone | 16:05 |
| evrardjp | so, I haven't got the chance to continue my work on cleaning up the 42.3, but it's still pending | 16:05 |
| evrardjp | I see noonedeadpunk guilhermesp mnaser jrosser helped, so thanks! | 16:05 |
| evrardjp | I also still have the job state matrix to finish | 16:06 |
| evrardjp | but that will have to wait a little | 16:06 |
| guilhermesp | o/ | 16:06 |
| evrardjp | that's all I had for today. | 16:06 |
| mnaser | i wanted to bring up killin old branches | 16:07 |
| evrardjp | mnaser: what's up on your side? ptl letter ready? | 16:07 |
| mnaser | its already sent out hehe | 16:07 |
| evrardjp | oh that's a good topic | 16:07 |
| noonedeadpunk | So I have linters check done for integrated tests https://review.opendev.org/#/c/679101/ It was failing only linters check before issue with gastes | 16:07 |
| evrardjp | mnaser: great! | 16:07 |
| *** macz has joined #openstack-ansible | 16:07 | |
| evrardjp | oh yeah I also wanted to discuss killing magnum queens | 16:07 |
| evrardjp | but go ahead mnaser :) | 16:07 |
| mnaser | ok so | 16:08 |
| evrardjp | (FYI kolla and triple O have started killing branches, we can do too, there is precedent) | 16:08 |
| mnaser | right now we have | 16:08 |
| mnaser | stable/ocata-stable/stein | 16:08 |
| mnaser | thats a lot of branches | 16:08 |
| mnaser | i think the only reason we cared about ocata was rax folks mentioned it | 16:08 |
| mnaser | but no one is really stepping up at this point | 16:09 |
| evrardjp | you want me to propose to tag everything and mark everything EOL for Ocata? | 16:09 |
| noonedeadpunk | I'm wondering if we still need to carry pike as well... | 16:09 |
| evrardjp | I would say Pike and Ocata are in the same boat | 16:09 |
| evrardjp | I would wait for queens | 16:09 |
| mnaser | yeah i was gonna go release by release | 16:09 |
| evrardjp | it's not even EM yet | 16:09 |
| jamesdenton | Is there harm in carrying the branch? | 16:10 |
| mnaser | ci is broken for it | 16:10 |
| mnaser | so really unless someone is gonna push a patch and start fixing that | 16:10 |
| mnaser | and even then tbh i have no interest in reviewing patches to fix stable/ocata. | 16:10 |
| evrardjp | it's kinda setting a wrong expectation | 16:10 |
| evrardjp | because it's still under extended "maintenance" where we actually don't do any maintenance | 16:11 |
| jamesdenton | Yeah Ocata, IDGAF. But Pike might be important. I'll have to ask | 16:11 |
| evrardjp | :D | 16:11 |
| mnaser | if someone is out here pushing patches and making it happy, id be happy | 16:11 |
| mnaser | but so far, i havent seen anything | 16:11 |
| jamesdenton | how frequently does CI run for those old things? Only on patches? | 16:11 |
| evrardjp | I can start by killing ocata, and wait for your answer. In the meantime, we can disable functional testing in Pike if it doesn't pass anymore (but in that case, I would prefer going for EOL sooner rather than later) | 16:12 |
| mnaser | https://review.opendev.org/#/q/projects:openstack/openstack-ansible+is:open+branch:stable/pike | 16:12 |
| mnaser | and there is a lot of them | 16:12 |
| mnaser | ok by a lot its 27 patches | 16:12 |
| *** gyee has joined #openstack-ansible | 16:12 | |
| evrardjp | For killing the branch I will close all of those | 16:12 |
| mnaser | but they demonstrate that everything is clearly broken | 16:12 |
| jamesdenton | fair enough | 16:12 |
| jamesdenton | I am asking now and will get back to ya | 16:13 |
| mnaser | this is why i wanted to go release by release | 16:13 |
| mnaser | seems like we have consensus that ocata can go | 16:13 |
| noonedeadpunk | mnaser: humm, I'd say mainly suse42 is broken there | 16:13 |
| jamesdenton | yeah, sorry to interject | 16:13 |
| evrardjp | jamesdenton: you're right to do so | 16:13 |
| evrardjp | noonedeadpunk: which links to my first topic... I am removing it :p | 16:13 |
| noonedeadpunk | If we drop suse for pike, I'd say it will be passing ci | 16:13 |
| mnaser | suse42 broken in pike? | 16:14 |
| evrardjp | noonedeadpunk: we are passing CI in the integrated in pike that's for sure | 16:14 |
| mnaser | or ocata? | 16:14 |
| evrardjp | for ubuntu* | 16:14 |
| noonedeadpunk | mnaser: pike | 16:14 |
| mnaser | ah ok | 16:14 |
| *** spatel has joined #openstack-ansible | 16:14 | |
| evrardjp | but it doesn't mean that some projects are fine | 16:14 |
| noonedeadpunk | yeah, agree | 16:14 |
| noonedeadpunk | like magnum:) | 16:14 |
| *** BjoernT has joined #openstack-ansible | 16:14 | |
| evrardjp | it's not the only one, I don't want to do finger pointing in pike right now | 16:15 |
| evrardjp | but the state is bad | 16:15 |
| evrardjp | let's work on the cleanup of 42.3 for pike, and recheck all of those subporjects | 16:15 |
| evrardjp | projects* | 16:15 |
| noonedeadpunk | ++ | 16:15 |
| *** nikparasyr has quit IRC | 16:15 | |
| evrardjp | if they don't work, we'll reduce the testing there and write that down somewhere in an etherpad. Then we send a summary message on the ML saying "If you care about Pike, here is what should be done", else we'll just drop it in x weeks | 16:16 |
| evrardjp | is that fine for everyone? | 16:16 |
| jamesdenton | Alright - so I think our official line is "feel free to purge Pike whenever" | 16:16 |
| noonedeadpunk | I think it fair | 16:17 |
| logan- | o/ | 16:17 |
| evrardjp | jamesdenton: that or be ready to fix it :) | 16:17 |
| jrosser | o/ | 16:17 |
| jamesdenton | :D | 16:17 |
| * jamesdenton looks around - not it | 16:17 | |
| evrardjp | hahaha | 16:17 |
| logan- | yeah ocata and pike seem reasonable to drop if no one is maintaining them or using them | 16:17 |
| evrardjp | when tagging EOL ppl will review if there are pending patches, so it makes sense to clean the complete state before asking the EOL tag | 16:18 |
| jamesdenton | We simply need the 16.x tags | 16:19 |
| mnaser | yeah those arent going anywhere | 16:19 |
| jamesdenton | k | 16:19 |
| mnaser | jamesdenton: we = platform9? | 16:19 |
| jamesdenton | :| | 16:19 |
| jamesdenton | we = RAX | 16:19 |
| mnaser | oh | 16:19 |
| jamesdenton | long story | 16:19 |
| mnaser | lol | 16:19 |
| mnaser | okay | 16:19 |
| mnaser | well good to know | 16:19 |
| mnaser | didn't seem to add up :p | 16:19 |
| jamesdenton | hehe | 16:19 |
| mnaser | alright | 16:20 |
| mnaser | something that concerns me is that sustainability of the project | 16:20 |
| mnaser | there's a lot of users but not a lot of poeple pushing patches and reviewing etc | 16:20 |
| mnaser | Do people not want to use Ansible anymore? Do they prefer other tooling (aka containers?) Over this? | 16:21 |
| noonedeadpunk | also I'd say we have pretty big docs debt right now... | 16:21 |
| noonedeadpunk | it's in addition | 16:21 |
| noonedeadpunk | not the root cause:) | 16:21 |
| mnaser | I've spoken to some million core scale cloud users and they didn't seem that interested by trying to use it more. Containers made a lot of sense to them. | 16:22 |
| jamesdenton | These were former OSA users? | 16:23 |
| jamesdenton | or operators | 16:23 |
| mnaser | Other distros have done a lot of platform evolution like moving the control plane to containers like tripleo | 16:23 |
| mnaser | No just operators looking to change tooling for deployment | 16:23 |
| mnaser | I just don't want us to be stuck in where we started forever until the project is irrelevant.. or we can just decide to stick to it till the very end | 16:24 |
| mnaser | I'd love to hear maybe other operators like jrosser or logan- chime in too from a deployers pov | 16:24 |
| evrardjp | I think the simplest tech make it very appealing. | 16:25 |
| noonedeadpunk | I'd say that it's pretty controversial and really depends... And this might be really good thing to ask on some opendev summit... | 16:25 |
| evrardjp | (And I think there are other tools doing other way of deploying, like kolla or osh... it's just different dna) | 16:25 |
| jrosser | OSA does what I need it to do | 16:26 |
| evrardjp | mnaser: shouldn't the foundation poll data help here? | 16:26 |
| noonedeadpunk | I kinda remember really big interest to OSA in Berin | 16:26 |
| evrardjp | I think OSA is boring for many, but it's good boring :) | 16:26 |
| logan- | i'd say the same as jrosser | 16:26 |
| jrosser | i'm not sure what 'irellevant' means in this context, just cause we don't use a currently fashoinable texh isnt a bad thing | 16:27 |
| mnaser | Right but is this a sustainable DNA? I'm worried that with time as technology evolves it won't make sense and be a crutch | 16:27 |
| *** kopecmartin is now known as kopecmartin|off | 16:27 | |
| mnaser | Say like: I want to do ci/cd to deliver my cloud | 16:27 |
| mnaser | Raise your hand if you'd trust running OSA every X minutes to ensure state. It's just so many moving parts | 16:27 |
| evrardjp | then git clone logan-'s work | 16:27 |
| mnaser | I get it. It's different DNA. I agree to an extent. This isn't a comfortable conversation | 16:28 |
| miloa | Not all organisations want/could adopt the new tech as "docker" containers. And LXC is easier for some operators than docker for example, so it make OSA rlevant :) | 16:29 |
| mnaser | But as a project do we want to "ride it out till the end" or do we want to start looking at ways to improve things. | 16:29 |
| evrardjp | I think openstack is hard, but if you're saying that you don't trust to ci/cd osa, maybe that's what we need to fix. | 16:29 |
| guilhermesp | I agree about following the tendency of the IT marked for example: k8s is becoming a preferable way for lots of dev/ops and I've been hearing this since ocata release... but tbh, we need more concrete data to analyze OSA role in the openstack ecosystem | 16:29 |
| noonedeadpunk | For example I know companies, that still do not trust docker, that's was the root for choosing osa | 16:30 |
| guilhermesp | market* | 16:30 |
| mnaser | I agree to an extent. Not trusting docker and containers was a thing many years ago | 16:31 |
| evrardjp | also I don't think it's a good idea to change the DNA of OSA -- if we want to do something else, maybe we should add efforts to the other projects already in place, instead of us changing, except if we do something not existing | 16:31 |
| mnaser | That's fair enough | 16:31 |
| jamesdenton | In the survey, Is OSA called out specifically, or does it fall under the generic "Ansible" umbrella? I also found past surveys not to reflect OSA usage accurately - especially when managed hosting providers have hundreds of clouds under management but count as "One Deployment" for survey purposes. | 16:31 |
| evrardjp | mnaser: I kinda like the idea of docker for some part of the infra -- for example, tempest -- why do we need to care | 16:31 |
| guilhermesp | yes indeed | 16:31 |
| evrardjp | jamesdenton: I think I fixed that | 16:32 |
| evrardjp | but that might have changed | 16:32 |
| jamesdenton | Great, evrardjp! Been a while | 16:32 |
| evrardjp | we first call out the techs involved (so Ansible) | 16:32 |
| evrardjp | then the projects | 16:32 |
| evrardjp | (OSA/Kolla/whatever) | 16:32 |
| evrardjp | tbc | 16:32 |
| evrardjp | To summarize I understand the concern of mnaser. We are a very small team | 16:33 |
| mnaser | I think that the decreased amount of contributions and traction means we're sitting in a very niche thing | 16:33 |
| jrosser | i think that is the issue more than any particular tech choice | 16:33 |
| evrardjp | it seems by being working and boring, we don't convert new ppl to be contributors | 16:33 |
| evrardjp | jrosser: go on? :D | 16:34 |
| mnaser | It works for us, the group of people who are running and maintaining it, but we can't grab new users cause they have many other options that they'd prefer which work for them | 16:34 |
| mnaser | Which is slowly putting us in a corner | 16:34 |
| jrosser | evrardjp: the active group having shrunk so much | 16:34 |
| noonedeadpunk | probably they don't what to cotnribute much, because we have really big codebase and it needs more time to cover it? Moreover, if everything is working as expected there might bew no need for contributions | 16:35 |
| guilhermesp | that's exactly the case of the lab I was working on in the past noonedeadpunk | 16:36 |
| mnaser | But there is a big need. Our upgrades to train don't work and that has to be fixed. There is a lot of technical debt (uwsgi work for example), there's many tiny little quirks that come up | 16:36 |
| mnaser | Heck we don't even know if our Stein upgrade scripts work | 16:36 |
| mnaser | Jesse used to be the one who took care of all of that | 16:36 |
| jrosser | it's a problem that the rax folks put a disproportionate amount of effort in | 16:37 |
| noonedeadpunk | btw, can you remind me what's wrong with upgrade to train? Since we didn't backport standalone placement iirc... | 16:37 |
| jrosser | and it's hard for the rest of us to fill that space | 16:37 |
| noonedeadpunk | disregard, just will take a look | 16:37 |
| BjoernT | Seems like https://review.opendev.org/#/c/672078 was back-ported in the stable stein branch that breaks db online migration. I had to manually move all volumes so new service_uuids as the cinder-manage volume update_host does not update the service uuids | 16:37 |
| mnaser | Train upgrade is because you need to have placement deployed externally so all the upgrade code that exports the placement db and imports it into new placement doesn't exist | 16:37 |
| mnaser | Because it uses a seperate db | 16:37 |
| mnaser | And by no means is that an easy upgrade step either | 16:38 |
| openstackgerrit | Vadim Kuznetsov proposed openstack/openstack-ansible-os_octavia master: Octavia certificate distribution https://review.opendev.org/657662 | 16:38 |
| mnaser | jrosser: true but I feel like that goes to contribute to the idea that were in this little niche that served a certain company wel | 16:38 |
| noonedeadpunk | I thought that built-in placement still exist for stein... Ok... | 16:38 |
| mnaser | Now that they're gone, there's a few other users but for the main part it doesn't seem like where people want to go | 16:39 |
| mnaser | noonedeadpunk: it is in Stein but in train it's gone | 16:39 |
| mnaser | Aka master | 16:39 |
| mnaser | So Stein to master/train is broken | 16:39 |
| mnaser | And I don't know if rocky to Stein is tested much.. | 16:39 |
| noonedeadpunk | ah, yep, that's absolutelly true | 16:39 |
| evrardjp | looking at the stats of review diversity on stein for our deployment project, we don't have to be ashamed | 16:40 |
| mnaser | Review diversity is easy | 16:40 |
| mnaser | It's the commits | 16:40 |
| jrosser | i would like there to be a more obvious todo list | 16:40 |
| mnaser | And the sustainability | 16:40 |
| jrosser | PTG doesnt really address having a living backlog of stuff that needs doing, or allow prioritisation | 16:41 |
| jrosser | so for example, if i hire someone to work on OSA full time - what do they do? | 16:41 |
| noonedeadpunk | centos-8? :p | 16:42 |
| mnaser | I think we can totally start something like that.. but I also don't want us to sit and spend a whole document on backlog | 16:42 |
| noonedeadpunk | yeah, and python3 | 16:42 |
| mnaser | Only to kinda have it sit there | 16:42 |
| jrosser | btw i don't expect an answer - just i think we can do better at that | 16:42 |
| evrardjp | jrosser: there are so many things to make it sustainable: like having multi node jobs and upgrade jobs | 16:42 |
| evrardjp | that's the thing you care about | 16:42 |
| mnaser | evrardjp: like the lists we have in the tc | 16:42 |
| mnaser | It's a list that doesn't get used.. I don't think making a work list will make people come and pick it up imho | 16:43 |
| mnaser | OSA isn't cool enough for people to contribute to it on their free time. The only people contributing are users | 16:43 |
| noonedeadpunk | btw, we have really full bugtracker and I'm not sure if it's being reviewed | 16:43 |
| evrardjp | that's fair but here it's more on the battlefield, so I would expect that ppl would have an incentive on making things work upstream before having to do the battle testing in their environment :) | 16:43 |
| noonedeadpunk | Since I don't feel like some work is happening there | 16:43 |
| evrardjp | It used to be a very active thing, but as soon as you don't answer to bugs, the ppl start to disappear indeed | 16:44 |
| noonedeadpunk | yeah, that what I did some time at horizon | 16:45 |
| miloa | evradjp: +1 | 16:45 |
| noonedeadpunk | I just opened bug tracker and decided even not to fill another bug there | 16:45 |
| guilhermesp | yeah that's true... maybe we need to plan another bug track day :P | 16:46 |
| jrosser | these things have to be continuous though | 16:46 |
| evrardjp | We might want to clean up stuff there, and return to the regular bug triage + bug squash day | 16:46 |
| jrosser | like review | 16:46 |
| mnaser | Right but its just us that go and fix bugs with no one stepping up | 16:46 |
| noonedeadpunk | I'd say it stopped being active right after we stopped doing bug triage | 16:46 |
| mnaser | Anyone remember what bug triage was like? As someone doing meetings it was just killing the whole thing | 16:46 |
| mnaser | Struggled to get an answer from anyone in the meeting... | 16:46 |
| evrardjp | it always was like that | 16:47 |
| mnaser | And to be honest, there's plenty of stuff to fix that we need. | 16:47 |
| evrardjp | from day 0 I joined the project | 16:47 |
| mnaser | I'm all for.helping others but do we really have time to sit and fix reported bugs by people when we struggle to get stuff that we know is fundamental for the project to work | 16:47 |
| mnaser | Aka fixing some bug vs fixing the ticking placement time bomb for example | 16:47 |
| evrardjp | yeah we got an interrupt based way of working that's on IRC. That works but that's not perfect for an outsider. But I am not sure ppl fixing bugs will bring new contributors here. But neither is a new tech | 16:47 |
| mnaser | It would bring new users, imho. But that's just an opinion. I could be completely wrong | 16:48 |
| noonedeadpunk | I'd say that at least we need to look through them and prioritise | 16:48 |
| noonedeadpunk | Since there might be more bomb than placement one | 16:48 |
| mnaser | That's pretty valid tio | 16:48 |
| mnaser | Too | 16:49 |
| jrosser | personally i dont think things are as bad as they seem | 16:49 |
| evrardjp | I agree with jrosser | 16:49 |
| jrosser | a lot of other openstack components are in worse way | 16:49 |
| jrosser | in terms of review, irc activity and so on | 16:49 |
| jrosser | we do quite well imho | 16:50 |
| noonedeadpunk | Almost all of opensatck projects have problems with new contributors now afaik | 16:50 |
| evrardjp | looking at heat and glance, which are core parts of openstack IMO, we are not that bad :) | 16:50 |
| noonedeadpunk | yeah, agree with jrosser | 16:50 |
| evrardjp | which is why I think we should focus on a few things, making sure they are working fine | 16:50 |
| jrosser | this contains wise words https://docs.openstack.org/openstack-ansible/latest/contributor/core-reviewers.html | 16:50 |
| evrardjp | jrosser: I know, right? :p | 16:51 |
| mnaser | In full transparency, personally I think an architecture running OpenStack on top of kuberenetes opens up the door for a lot of things (nest monitoring powered by daemonsets), simplified ci and cd, simplified network architecture and overall mgmt | 16:51 |
| evrardjp | it's not that green in OSH world, I can tell you :) | 16:52 |
| evrardjp | we are by far in a better shape, due to our simplicity | 16:52 |
| mnaser | While I think we'll continue in OSA for a while, I think eventually that's where we will go.. and I just worry that if we do that then the project gets a tough hit.. | 16:52 |
| mnaser | I don't think we will deploy on OSA forever. Kuberenetes is def the future because of the scale of deployments and advantages it brings operationally | 16:53 |
| mnaser | And I personally feel that if that's how I think, maybe there might be others that think of kuberenetes. And rather than perhaps losing more, we can adopt a new direction. Or we dont | 16:53 |
| noonedeadpunk | maybe we can add things like an extra with nspawn? | 16:54 |
| evrardjp | what's missing in the k8s openstack world is operators to deal with things | 16:54 |
| noonedeadpunk | * like nspawn | 16:54 |
| jrosser | evrardjp: i agree completely - theres no-one here who could even start with that | 16:55 |
| mnaser | Brb driving (I already got s ticket for using my phone a while back hah) | 16:55 |
| evrardjp | there are ppl who technically can, but the question is "why would they?" if there is something like OSA already working :p | 16:56 |
| *** ansmith has joined #openstack-ansible | 16:56 | |
| miloa | Diversity is important :) for any ecosystems LXC/Docker/kubernetes. Let users the choice :) Because their environnement and background are differents. | 16:57 |
| evrardjp | I think as an action point, it would be nice to know why ppl love OSA, focus on this to make it stronger. | 16:57 |
| miloa | Their is already many deployement tools using Kubernetes. | 16:57 |
| evrardjp | miloa: totally agreed :) | 16:58 |
| jrosser | i chose it becasue there was no magical element that would jump up and fubar my stuff randomly | 16:58 |
| *** ansmith_ has quit IRC | 16:58 | |
| jrosser | everything is understandable and debuggable | 16:58 |
| noonedeadpunk | +1 | 16:58 |
| evrardjp | ok, so, is there still black magic in OSA, like we used to have? :p | 16:58 |
| jamesdenton | If anyone is gonna FUBAR my environment, it's gonna be me! | 16:58 |
| jrosser | too right :) | 16:58 |
| evrardjp | jamesdenton: :) | 16:58 |
| evrardjp | jamesdenton: with the mighty strength of my PEBKACs! | 16:59 |
| jamesdenton | :D | 16:59 |
| tiffanie | #endmeeting | 17:00 |
| *** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: http://bit.ly/2xA1eZC" | 17:00 | |
| openstack | Meeting ended Tue Sep 3 17:00:11 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-09-03-16.03.html | 17:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-09-03-16.03.txt | 17:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-09-03-16.03.log.html | 17:00 |
| miloa | We choose OSA because it use ansible and we train people to use ansible and LXC because it is easy for ops to manage it as they can ssh in and use it as normal system with systemctl | 17:00 |
| evrardjp | so basically simplifying things is great for OSA, and making sure things are reliable at all times | 17:00 |
| evrardjp | miloa: that was indeed the DNA of OSA :) | 17:00 |
| guilhermesp | We have a nice thing now to make things simpler: no_container flag . Thx mnaser and noonedeadpunk | 17:01 |
| jrosser | so who wants to help me with the galera and rabbit port binding stuff? | 17:01 |
| miloa | evrardjp: was ? :) | 17:02 |
| noonedeadpunk | jrosser: I'd love to but right now working on uwsgi and upgrade stuff... | 17:02 |
| guilhermesp | I can try to help you out with this jrosser just need to get more context | 17:03 |
| guilhermesp | I do remember the topic | 17:03 |
| *** vakuznet has joined #openstack-ansible | 17:03 | |
| guilhermesp | But it's been a while I don't iterate | 17:03 |
| noonedeadpunk | btw evrardjp don't you know how to reach requirements team? | 17:04 |
| * jrosser heads home | 17:04 | |
| vakuznet | https://review.opendev.org/#/c/679304/ - review please | 17:04 |
| noonedeadpunk | regarding https://review.opendev.org/#/c/679238/ | 17:04 |
| *** cshen has joined #openstack-ansible | 17:13 | |
| *** miloa has quit IRC | 17:19 | |
| *** miloa has joined #openstack-ansible | 17:19 | |
| *** cshen has quit IRC | 17:27 | |
| *** miloa has quit IRC | 17:28 | |
| guilhermesp | all right jrosser I will take a look at the topic and I think I can work on it with you | 17:28 |
| *** pcaruana has joined #openstack-ansible | 17:29 | |
| openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_barbican master: Add extra barbican services https://review.opendev.org/679832 | 17:30 |
| jrosser | guilhermesp: the galera one is not my expertise so I don’t know what the right approach is there | 17:31 |
| jrosser | And the rabbit patch is mostly there except some left over erlang port bound to 0.0.0.0 - needs fresh eyes | 17:31 |
| *** cshen has joined #openstack-ansible | 17:33 | |
| guilhermesp | do you have the topic handy ? | 17:37 |
| jrosser | https://review.opendev.org/#/q/status:open+bind-to-mgmt | 17:38 |
| *** cshen has quit IRC | 17:38 | |
| * guilhermesp looking | 17:38 | |
| jrosser | This one brings everything g together https://review.opendev.org/#/c/670051/ | 17:39 |
| guilhermesp | yeah.. in fact, we need to fix galera and rabbit patch to try a recheck in that one right? | 17:40 |
| jrosser | I think rabbit doesn’t break it, there’s just a residual port binding that’s wrong | 17:41 |
| jrosser | Afaik it’s gamers breaking it | 17:41 |
| jrosser | Argh phone | 17:41 |
| jrosser | Galera | 17:41 |
| guilhermesp | ah the epmd port | 17:41 |
| jrosser | Yeah, I wondered if it was worth scratching around other projects to see if there’s a trick for that | 17:42 |
| guilhermesp | yeah... I will spend some time this afternoon/night with it | 17:43 |
| jrosser | It was quite quick/easy to spin up a metal AIO and hack on this | 17:43 |
| openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-tests master: Set no_log for sensitive tasks https://review.opendev.org/679836 | 17:50 |
| *** luksky has joined #openstack-ansible | 17:52 | |
| *** markvoelker has quit IRC | 18:03 | |
| *** ansmith_ has joined #openstack-ansible | 18:12 | |
| *** ansmith has quit IRC | 18:15 | |
| *** markvoelker has joined #openstack-ansible | 18:20 | |
| *** tosky has quit IRC | 18:24 | |
| *** markvoelker has quit IRC | 18:24 | |
| *** markvoelker has joined #openstack-ansible | 18:43 | |
| *** gyee has quit IRC | 18:53 | |
| vakuznet | https://review.opendev.org/#/c/657662/ - review please | 18:55 |
| *** gyee has joined #openstack-ansible | 19:07 | |
| *** alvinstarr has joined #openstack-ansible | 19:21 | |
| *** masterp6 has joined #openstack-ansible | 19:48 | |
| openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_barbican master: Add extra barbican services https://review.opendev.org/679832 | 19:59 |
| openstackgerrit | Guilherme Steinmuller Pimentel proposed openstack/openstack-ansible-rabbitmq_server master: Add defaults for rabbitmq managment and erlang bind addresses https://review.opendev.org/670394 | 19:59 |
| *** pcaruana has quit IRC | 20:00 | |
| guilhermesp | noonedeadpunk: seeing some of your rechecks... do you know if the mirrors are ok now? | 20:03 |
| noonedeadpunk | so recent jobs were failing for suse only, so I hoped that dns things are better now | 20:08 |
| noonedeadpunk | like https://review.opendev.org/#/c/679304/ | 20:09 |
| *** spatel has quit IRC | 20:34 | |
| *** michielp has joined #openstack-ansible | 20:36 | |
| *** radeks has quit IRC | 20:37 | |
| *** ansmith_ has quit IRC | 20:37 | |
| *** masterp6 is now known as masterp8 | 20:37 | |
| michielp | hi, I try to use os-rally-install.yml but after a while I get the error https://gist.github.com/mpiscaer/713cdbea5b9934cde14edc0ac1ed7f2a | 20:43 |
| *** markvoelker has quit IRC | 20:45 | |
| michielp | I get the same error when I do in the utility container source openrc; /openstack/venvs/rally-18.1.4/bin/rally deployment create --fromenv --name=existing | 20:48 |
| michielp | But when I do the rally deployment command without the source I get: bd596b8e-82fa-4ac1-a525-b04d9727bf38 | 2019-09-03T20:48:14 | existing | deploy->finished | 20:50 |
| jrosser | michielp: is this an AIO? or a proper deployment | 20:51 |
| *** trident has quit IRC | 20:52 | |
| michielp | between AIO and proper deployment | 20:52 |
| michielp | It is voor testing. it has 1 controller 1 compute and 3 ceph nodes | 20:53 |
| *** masterp8 has quit IRC | 20:57 | |
| jrosser | looks like this is the patch to rally which introduced that code which fails https://github.com/openstack/rally/commit/14a8b0f931424d42543c100c9deb409eaded86d3 | 20:58 |
| jrosser | michielp: it's not much help but it looks like something os broken either is rally, or OSA use of rally there | 21:01 |
| michielp | jrosser: thanks | 21:03 |
| *** trident has joined #openstack-ansible | 21:03 | |
| jrosser | michielp: oh hmm this too https://review.opendev.org/#/c/659197/4/upper-constraints.txt | 21:04 |
| *** masterpe1 has joined #openstack-ansible | 21:05 | |
| jrosser | it adds python_version=='3.4' - if thats a requirement i think we will fail as OSA is still python 2 | 21:05 |
| *** ansmith_ has joined #openstack-ansible | 21:10 | |
| jrosser | michielp: so looking at this i would start checking which version of rally-openstack you have installed there - i'd maybe expect it to be 1.5.0 for a recent install | 21:14 |
| jrosser | you can see that here https://pypi.org/search/?q=rally-openstack | 21:14 |
| jrosser | and the bit of code that has failed should only run for versions less that 1.4.0, tested here https://github.com/openstack/rally/commit/14a8b0f931424d42543c100c9deb409eaded86d3#diff-0acd842fee21f9ad413f310ce442aef5R92 | 21:15 |
| *** rmcall has joined #openstack-ansible | 21:17 | |
| *** luksky has quit IRC | 21:27 | |
| *** rmcall has quit IRC | 21:28 | |
| *** markvoelker has joined #openstack-ansible | 21:31 | |
| *** markvoelker has quit IRC | 21:35 | |
| *** BjoernT has quit IRC | 22:33 | |
| *** mgoddard has quit IRC | 22:47 | |
| *** masterpe1 is now known as masterpe2 | 22:55 | |
| *** masterpe2 is now known as mp | 22:55 | |
| *** mp is now known as masterp4 | 23:02 | |
| *** masterp4 is now known as masterpe | 23:15 | |
| *** threestrands has joined #openstack-ansible | 23:26 | |
| *** macz has quit IRC | 23:41 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!