| noonedeadpunk | damiandabrowski: mgariepy jrosser NeilHanlon - here's the voting link for bug fighting day selection: https://doodle.com/meeting/organize/id/enGV50Wa | 08:50 |
|---|---|---|
| noonedeadpunk | Will also send a ML | 08:50 |
| noonedeadpunk | huh, 40% loss to gerrit :( | 09:09 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Do not configure RPC for Neutron with OVN driver https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/907245 | 09:17 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Add VPNaaS OVN support https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/908341 | 09:21 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Add VPNaaS OVN support https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/908341 | 09:22 |
| opendevreview | Jonathan Rosser proposed openstack/openstack-ansible master: Allow zuul pre playbook bootstrap to be skipped https://review.opendev.org/c/openstack/openstack-ansible/+/905290 | 09:26 |
| opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Add job to test Vexxhost cluster API driver https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 10:11 |
| jrosser | noonedeadpunk: any thoughts about auto-running playbooks/openstack-resources.yml so we can leverage it in the AIO? | 10:17 |
| jrosser | or we could use a hook for that? | 10:19 |
| noonedeadpunk | I was thinking about hook... But we can add the playbook pre-tempest | 10:19 |
| noonedeadpunk | to setup-openstack. for instance | 10:19 |
| jrosser | maybe it's just complicated and there is not one specific place to call it | 10:20 |
| noonedeadpunk | I don't have any strong opinion here frankly speaking | 10:20 |
| jrosser | ok, i'll have a go and see what looks tidy | 10:21 |
| noonedeadpunk | LIke indeed, it feels that it might be needed all over the board | 10:21 |
| jrosser | right, and there is issues of ordering as well which might var depending on what the scenario is | 10:21 |
| noonedeadpunk | so calling it from service roles might be still valid | 10:21 |
| jrosser | as you need flavors and public network to exist before making coe template, for example | 10:22 |
| jrosser | and images | 10:22 |
| noonedeadpunk | Hm. But that's ordering of includes inside the role | 10:22 |
| noonedeadpunk | Coe is right now the last one | 10:23 |
| damiandabrowski | noonedeadpunk: voted on doodle! | 10:23 |
| jrosser | if we factor out creating of the public network from os_tempest to $elsewhere then that would have to be done before whatever thing then subsequently makes the coe template | 10:23 |
| noonedeadpunk | damiandabrowski: that was not helpful vote lol | 10:23 |
| noonedeadpunk | but thanks! | 10:23 |
| noonedeadpunk | also apparently, I can't change my voting - all suggested slots can be marked only green by me | 10:24 |
| noonedeadpunk | yeah, but if we call openstack_resources just once - it will be like that? | 10:25 |
| noonedeadpunk | I mean - coe template is really very last thing in the role: https://opendev.org/openstack/openstack-ansible-plugins/src/branch/master/roles/openstack_resources/tasks/main.yml#L69 | 10:25 |
| noonedeadpunk | so all images/networks/flavors will be created before anyway, even if it's single run? | 10:25 |
| noonedeadpunk | or we're talkign about different aspects?:) | 10:26 |
| jrosser | well like you say i think there need to be multiple calls | 10:26 |
| jrosser | as coe template can't be made until (for example) the capi install has completed via a hook | 10:26 |
| noonedeadpunk | yeah, ok, right | 10:27 |
| spatel | did you guys configured gnocchi with grafana? | 14:03 |
| spatel | I am doing this but none of option working - https://ibb.co/VVTyNyt | 14:09 |
| noonedeadpunk | spatel: I did but like .... 5 years ago | 14:25 |
| noonedeadpunk | a lot of changed since then.... | 14:25 |
| spatel | Hmm! let me see what I can do.. | 14:26 |
| noonedeadpunk | spatel: and, um, have you tried to paste keystone url as a first field? | 14:26 |
| spatel | I did used keystone also but nothing is working | 14:27 |
| noonedeadpunk | as it should ideally discover gnocchi from keystone | 14:27 |
| noonedeadpunk | there was also smth cors related.... | 14:27 |
| noonedeadpunk | or maybe not... | 14:28 |
| spatel | I am reading about CORS | 14:28 |
| spatel | feels like something is hidden there | 14:28 |
| spatel | so if I am using keystone auth then I have to use keystone URL right? | 14:31 |
| noonedeadpunk | yeah. for sure we did cors with overrides.... | 14:31 |
| noonedeadpunk | Yes | 14:31 |
| noonedeadpunk | I think so... | 14:32 |
| noonedeadpunk | you use gnocchi url only if auth via a token | 14:32 |
| spatel | I am following this doc and seems nothing working - https://gnocchi.osci.io/grafana.html | 14:40 |
| spatel | anyway leave it :( | 14:40 |
| noonedeadpunk | it totally worked some time ago :D | 14:44 |
| noonedeadpunk | But yeah | 14:44 |
| spatel | haha.. | 14:51 |
| spatel | may be stupid version issue or something | 14:51 |
| opendevreview | OpenStack Release Bot proposed openstack/openstack-ansible master: reno: Update master for unmaintained/yoga https://review.opendev.org/c/openstack/openstack-ansible/+/908499 | 15:01 |
| * jrosser wonders why we make the public network in the `tempest` project in an AIO rather than admin project | 15:22 | |
| noonedeadpunk | because nobody cared enough | 15:59 |
| jrosser | i'll try and tidy this up | 16:00 |
| jrosser | but why.... https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio.j2#L154-L155 | 16:19 |
| jrosser | https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/openstack_user_config.yml.aio.j2#L189-L190 | 16:19 |
| jrosser | /o\ | 16:19 |
| jamesdenton | IIRC, OVN won't allow you to have multiple provider networks referencing the same bridge | 16:26 |
| noonedeadpunk | yeah. not sure, my ovn sandbox having only vlan and geneve | 16:27 |
| jrosser | i would really really like to give the net_name something that is not vlan and not flat | 16:28 |
| jrosser | as this is so totally confusing | 16:28 |
| jrosser | becasue i think i understand, that in OVS/OVN we can refer to the same container_bridge thing (br-provider) more than once and use it to define a flat and vlan network off the same underlying interface | 16:29 |
| jamesdenton | i don't mind changing the name from vlan to something like physnet1, to match upstream docs | 16:30 |
| jrosser | another wierdness is using br-provider for project networks | 16:31 |
| jrosser | jamesdenton: what do the upstream docs say about this ^ | 16:32 |
| jamesdenton | but IIRC, here: https://github.com/openstack/openstack-ansible-os_neutron/blob/master/tasks/providers/setup_ovs_ovn.yml#L88-L93 ... if you have a physnet1:br-ex and physnet2:br-ex it will fail. So vlan:br-ex and flat:br-ex fails | 16:32 |
| jamesdenton | well the lines are blurred with provider and tenant VLAN networks... they're essentially the same | 16:33 |
| * jrosser runs liknuxbridge here still so is looking for some guidance to disambiguate all this | 16:33 | |
| jamesdenton | br-provider == br-ex | 16:34 |
| jamesdenton | that's the upstream name for that interface | 16:34 |
| jrosser | socan we use physnet1 rather than flat/vlan for the net_name, or are you saying there is going to be brokennes in the OVN bridge mappings if i do that | 16:35 |
| jamesdenton | i think i'm saying you CAN use physnet1 instead. And physnet1 can carry N vlans and a single flat | 16:36 |
| jamesdenton | the flat being native/untagged | 16:36 |
| jrosser | yeah | 16:37 |
| jrosser | ok | 16:37 |
| noonedeadpunk | fwiw, reminder to fill in poll: https://doodle.com/meeting/organize/id/enGV50Wa | 17:40 |
| mgariepy | done. | 18:01 |
| mgariepy | should be mostly ok | 18:01 |
| mgariepy | but things can pop up before the date :D | 18:02 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Disable RPC configuration for Neutron with OVN in CI https://review.opendev.org/c/openstack/openstack-ansible/+/908521 | 20:28 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Do not configure RPC for Neutron with OVN driver https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/907245 | 20:29 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Disable RPC configuration for Neutron with OVN in CI https://review.opendev.org/c/openstack/openstack-ansible/+/908521 | 20:30 |
| NeilHanlon | ouch. looks like there is some cve in ovs | 20:52 |
| NeilHanlon | saw on oss-security list | 20:53 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Add VPNaaS OVN support https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/908341 | 21:00 |
| noonedeadpunk | ugh | 21:12 |
| noonedeadpunk | that's maybe it's failing in centos? | 21:12 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!