| *** Adri2000_ is now known as Adri2000 | 10:25 | |
| Moha_ | "OSA was a long dark twisting road to climb. Outdated documentation, a few hand patches to roles here and there to suit our deployment but now we're at the top of the mountain, I definitely prefer it over Triple O. And we really don't have the staff to maintain a k8s cluster properly" | 12:33 |
|---|---|---|
| Moha_ | ^ https://www.reddit.com/r/openstack/s/62esOslbMb | 12:33 |
| jrosser | Moha_: if you feel the docs are outdated please do contibute to fix that | 12:37 |
| mgariepy | i'd love to have some details on the ""patches here and there"" most of the configuration have a possibility to override part of config without having to modify the roles. | 12:38 |
| jrosser | yeah, that really should not be necessary otherwise it's a bug or missing feature | 12:39 |
| Moha_ | jrosser: oh, no I don't :)) | 12:39 |
| Moha_ | Just forwarded an opinion; not to bad to know how things are propagated on the web. Don't take it sth serious! | 12:40 |
| jrosser | oh - thats someone else? | 12:40 |
| mgariepy | wow. some ppl seems to ask for help on reddit.. | 12:41 |
| mgariepy | https://www.reddit.com/r/openstack/comments/1avjj1t/trying_to_deploy_openstack_zed_with_ansible_and/ | 12:41 |
| Moha_ | Jrosser: Yes. The topic itself is mine, not that comment | 12:42 |
| jrosser | probably we underestimate the barrier of IRC and mailing lists | 12:43 |
| mgariepy | yeah, we are getting too old.. | 12:43 |
| mgariepy | LOL | 12:44 |
| mgariepy | maybe we all need to create a facebook account.. LOL | 12:44 |
| noonedeadpunk | lol | 12:46 |
| noonedeadpunk | but I'm really don't know how to deal with reddit | 12:46 |
| noonedeadpunk | and how to track things there | 12:46 |
| mgariepy | i'm not too sure myself either | 13:01 |
| mgariepy | lol | 13:01 |
| noonedeadpunk | Moha_: but feel free to bring such comments/notes here - it's really interesting and valuable to be aware about | 13:15 |
| Moha_ | +1 | 13:16 |
| f0o | noonedeadpunk: that's the good part of Reddit, you dont :P | 13:41 |
| f0o | jokes aside, I can see how/why comments like the one pasted by Moha_ can occur. Unless you know the big picture and how things work it's hard to get started. At very least the example yamls aren't working out of the box (specially now with OVN as default) | 13:42 |
| nixbuilder | I am fighting with OVN myself... almost got it going... but still have problems. | 13:57 |
| f0o_ | OVN is a bumpy opaque road | 13:58 |
| mgariepy | openstack is not a oneclick deploy thing either. there are a lot of moving part. | 13:58 |
| f0o_ | but I guess I only say that because I enjoyed the simplicity of linuxbridges for so long | 13:58 |
| jrosser | i think really the only thing we guarantee out-of-the-box is that the AIO config works | 13:59 |
| jrosser | particularly with neutron you have to either follow the reference architecture in os_neutron role docs or know enough to step outside that | 14:01 |
| jrosser | and very quickly things change from "make OSA settings to generate a working config" to "know what config I want and make OSA settings to achieve that" | 14:02 |
| f0o_ | ^word | 14:03 |
| f0o_ | what set me back quite a bit was that I started working off the prod-example, assuming that this would losely follow some production blueprint. However that example is simply nonfunctional as it is due to the new OVN default. | 14:04 |
| jrosser | yeah, we can improve that i am sure | 14:04 |
| f0o_ | Coming from non-OVN I honestly didnt know that OVN became the default either, so I started debuging the wrong thing until I finally got the hint from you guys that I'm barking at the wrong tree | 14:04 |
| f0o_ | I think many will take those examples and then try to form their own configs, so a faulty example can have a demotivating effect very early on | 14:05 |
| f0o_ | oh wow both commas at the same spot | 14:05 |
| f0o_ | shoot all 3 ar at the same spot! | 14:06 |
| *** f0o_ is now known as f0o | 14:06 | |
| mgariepy | needs to read the release notes when deploying / upgradging | 14:07 |
| jrosser | we are still on linuxbridge and migrating to OVN seems like a totally gigantic thing | 14:08 |
| mgariepy | well it's not a simple step either. switching prodution workload to another network stack without too much downtime and having a pretty good idea how it will react with a lot of unknown.. | 14:09 |
| jrosser | for sure - i won't have the possibility to build a new environment so whatever we do has to be in-place | 14:10 |
| mgariepy | the cloud i have to migrate to ovn is ovs based i didn't took any time to look at it tho. | 14:11 |
| nixbuilder | Hopefully once I get my system functional I can share my config files with you guys... hope it will contribute to the cause! | 14:13 |
| mgariepy | i do have an ovn based cloud running | 14:14 |
| mgariepy | but i don't have much exotic services running on it :D | 14:14 |
| nixbuilder | mgariepy: I don't have any exotic services running on mine either | 14:17 |
| nixbuilder | mgariepy: I think...depends what you consider exotic :-D | 14:17 |
| mgariepy | i do have base + manila and that's it. | 14:18 |
| mgariepy | all ceph backed | 14:19 |
| spatel | jamesdenton__ Hey! | 14:20 |
| spatel | around | 14:20 |
| nixbuilder | mgariepy: I think I just have base... no manila. Storage is all on fiber channel using the Dell EMC driver. | 14:20 |
| f0o | I have a somesort of exotic setup by using bleeding edge OVS on my TOR Routers which are my OVS GatewayNodes and have full tables hah - finding so many hidden gotchas with that | 14:20 |
| f0o | I thought this was straightforward when I started and here I am ~3 weeks later | 14:21 |
| mgariepy | with my ovn setup i have floating ip down to the compute nodes. but that's only a vlan that needs to be attached to the compute. | 14:22 |
| nixbuilder | mgariepy: My only unusual thing is that my clouds are in a lab... so my 'internal' and 'external' VIP addresses are the same. | 14:22 |
| nixbuilder | mgariepy: Sound like your setup is similar to mine... floating IP addresses are on the compute nodes. | 14:23 |
| nixbuilder | mgariepy: All floating IP addresses are on VLAN based networks. | 14:24 |
| f0o | mgariepy: yeah that's what we try to avoid and instead have the actual router-boxes do stuff instead of being pretty. So our network is a traditional North/South where the Gateway Nodes do full-table IBGP to the rest of the lot. Spares us dragging a vlan across all chassis, we did that for linuxbridge and we had too much noise on the wire eventually | 14:24 |
| mgariepy | nixbuilder, what are your issue then ? maybe we can help you figure it out. | 14:25 |
| mgariepy | my fip gateway are on the network switches/router | 14:26 |
| nixbuilder | mgariepy: Well... I just blew away the installation... so the problem went away :-D | 14:26 |
| mgariepy | LOL | 14:26 |
| nixbuilder | mgariepy: So I have decided to just install one infra node and one compute node and see if I can get that working... then press on from there. | 14:26 |
| nixbuilder | mgariepy: If you want to look at the relevant portions of my config and see if there is anything wrong https://paste.openstack.org/show/bfFCPsq7MqFsqx0IxIbX/ | 14:46 |
| mgariepy | nixbuilder, what wasn't working ? | 15:09 |
| nixbuilder | mgariepy: I was getting errors from the compute nodes that they could not bind a port whenever I tried to bring up and instance. | 15:13 |
| nixbuilder | mgariepy: Getting this as well in the logs... "Mar 19 14:45:19 compute012 ovn-nbctl[51783]: ovs|00001|db_ctl_base|ERR|unix:/var/run/ovn/ovnnb_db.sock: database connection failed (No such file or directory)" | 15:16 |
| mgariepy | https://paste.openstack.org/show/b2i6jAyJhZUoaz2103oa/ | 15:20 |
| mgariepy | that's my config | 15:20 |
| mgariepy | what os are you using ? | 15:20 |
| mgariepy | i'm on ubuntu 22.04 | 15:21 |
| mgariepy | are your agent up and running in openstack ? | 15:29 |
| f0o | there is a bug in 2023.2 where a patch to the ovn requirement didnt make it into the branch. call it a forward-port... because it did make it into 2023.1. The bug makes neutron-* not reconnect on connection loss to the northd. This might be happening here? | 15:30 |
| f0o | I had some "random" neutron-* error-looping because of that and had to systemctl restart those to get them connected to northd again (or patch the upper-constraints) | 15:31 |
| nixbuilder | mgariepy: I'm using Rocky 9.3. And yes the agents were up. | 15:34 |
| hamburgler | mgariepy: these are some things i noticed you did not have https://paste.openstack.org/show/b3QHlf3PJNDBV7qxeeMS/ (examples only from my lab) | 16:47 |
| hamburgler | just noticed i should have added container bridge type to my dbaas section :p - also we install openvswitch driver version using UCA, I don't recall OSA keeping that in line with latest version from UCA page but that is likely non issue | 16:49 |
| hamburgler | also running full SSL for internal services but again maybe just those group_binds are missing on your end? maybe not just didn't see them | 16:50 |
| hamburgler | running 22.04 also | 16:52 |
| noonedeadpunk | I'm pretty sure we install from UCA ovs by default | 16:52 |
| hamburgler | I don't remember this happening had to add it later, back in zed and antelope it was always running 2.17 or something, but I'm often wrong ;D | 16:54 |
| hamburgler | does look like it is there in os_neutron, can't remember if there was another reason, but we moved it to happen during setup_hosts | 16:57 |
| jrosser | hamburgler: there is not always a UCA release that exactly matches the OS / openstack version combinations. you might find in OSA so sometimes that changes slightly unexpectedly | 16:59 |
| hamburgler | yeah definitely noticed that, luckily these: https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/bobcat_versions.html don't seem to change for us duing openstack release cycles | 17:01 |
| hamburgler | or if they do have not noticed, but only rely on that for a few things | 17:02 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Deploy default policy files https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/910726 | 17:04 |
| hamburgler | nixbuilder: shoot sorry meant to tag you above not mgariepy | 17:12 |
| nixbuilder | hamburgler: :) | 17:29 |
| spotz[m] | And feel free to tag me on doc reviews! Sorry was in another discussion in another channel when the docs discussion was taking place here | 17:40 |
| noonedeadpunk | we just need to write them first :D | 17:47 |
| noonedeadpunk | I;'m really struggling to have a prio for that | 17:48 |
| spotz[m] | If I had enough notes I can write them but I figure by the time you wrote notes yo could have already written enough for me to edit in a patch | 17:54 |
| spotz[m] | I just don't have the hardware for anything more then an AIO at best | 17:55 |
| noonedeadpunk | ++ | 18:02 |
| noonedeadpunk | like biggest issue right now is to replace old lxb diagrams with ovn ones as users really struggle today with that part | 18:03 |
| noonedeadpunk | but hopefully will cover that sooner then later | 18:03 |
| noonedeadpunk | and add you for review :) | 18:03 |
| spotz[m] | I've been reviewing some in the main docs someone has been submitting the last week or so | 18:04 |
| opendevreview | Amy Marrich proposed openstack/openstack-ansible-os_neutron master: [doc] Expand documentation on OVN useful commands https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/913588 | 18:16 |
| noonedeadpunk | thanks! | 18:17 |
| spotz[m] | You're welcome:) It's what I'm here for! | 18:20 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Imporove Jinja indentation for service templates https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/913925 | 19:05 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Do not resolve all host_vars when haproxy_backend_node is a mapping https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/913927 | 19:22 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: [doc] Expand documentation on OVN useful commands https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/913588 | 20:17 |
| opendevreview | Merged openstack/openstack-ansible-os_horizon master: Deploy default policy files https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/910726 | 22:07 |
| opendevreview | Amy Marrich proposed openstack/openstack-ansible-os_neutron master: [doc] Expand documentation on OVN useful commands https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/913588 | 23:16 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!