| opendevreview | yangjianfeng proposed openstack/python-openstackclient master: Add router ndp proxy commands https://review.opendev.org/c/openstack/python-openstackclient/+/749038 | 00:53 |
|---|---|---|
| opendevreview | Arx Cruz proposed openstack/ansible-collections-openstack master: Update routers_info for the new SDK https://review.opendev.org/c/openstack/ansible-collections-openstack/+/838489 | 08:11 |
| opendevreview | Artem Goncharov proposed openstack/ansible-collections-openstack master: Switch project_info to new SDK https://review.opendev.org/c/openstack/ansible-collections-openstack/+/845782 | 09:42 |
| *** tosky_ is now known as tosky | 09:42 | |
| opendevreview | Arx Cruz proposed openstack/ansible-collections-openstack master: Update routers_info for the new SDK https://review.opendev.org/c/openstack/ansible-collections-openstack/+/838489 | 10:07 |
| *** tosky_ is now known as tosky | 11:55 | |
| *** tosky__ is now known as tosky | 13:17 | |
| *** tosky is now known as Guest2169 | 13:29 | |
| *** tosky__ is now known as tosky | 13:29 | |
| slaweq | gtema hi, regarding neutron-vpnaas support in OSC - I asked about it on our Neutron team meeting yesterday | 13:43 |
| slaweq | and amotoki told me that support for that should be there through neutronclient plugin | 13:43 |
| slaweq | it's like that for all neutron advanced services according to what amotoki told me | 13:43 |
| slaweq | can You check that maybe? | 13:43 |
| gtema | the point was that you can't abandon neutronclient with this done this way | 13:46 |
| opendevreview | mbu proposed openstack/python-openstackclient master: Wait for volume being available to set bootable or readonly https://review.opendev.org/c/openstack/python-openstackclient/+/845991 | 13:48 |
| gtema | ah, wait | 13:48 |
| gtema | I maybe confusing neutronclient and `neutron` cli | 13:49 |
| slaweq | gtema yes, we don't want to abandon python-neutronclient python bindings | 13:50 |
| slaweq | we only want to get rid of the CLI part of it | 13:50 |
| slaweq | as python bindings from it are used e.g. by heat AFAIK | 13:50 |
| slaweq | so there's no plan to remove it currently | 13:51 |
| gtema | yeah, but this is now this way | 13:51 |
| gtema | okay, but this part is a CLI, so are you going to get rid of that? | 13:53 |
| slaweq | hmm, I think I will need to talk about it with amotoki once again :) | 13:54 |
| gtema | anyway - we can move this into OSC | 13:54 |
| slaweq | but we would need to move it also to SDK first, right? | 13:56 |
| gtema | we can reuse most of the code just adding required bits in SDK | 13:56 |
| gtema | sending messages through matrix bridge seems really stuck for a while | 13:56 |
| *** tosky__ is now known as tosky | 13:58 | |
| gtema | so repeating broken sync communication: we need add few things to SDK; we can move CLI stuff for vpnaas into OSC making it use SDK; I got over summit some other user saying some of router agents were also not supported by OSC - will check that also; Once this done you can drop CLI part of neutronclient | 13:58 |
| opendevreview | Artem Goncharov proposed openstack/ansible-collections-openstack master: Switch project_info to new SDK https://review.opendev.org/c/openstack/ansible-collections-openstack/+/845782 | 14:01 |
| amotoki | gtema: slaweq: I just looked thru what are discussed above. | 14:03 |
| amotoki | the python-neutronclient repo contains three parts: neutron CLI, OSC plugin and python-bindings. | 14:03 |
| gtema | right, that is now also my understanding of the code | 14:04 |
| amotoki | OSC plugin mainly convers advanced services like vpnaas, fwaas and dynamic-routing | 14:05 |
| amotoki | in addition the OSC plugin covers some experimental/addtional features in the neutorn repo. | 14:05 |
| gtema | do you want them to stay in neutronclient or should we move it under OSC? | 14:05 |
| amotoki | the laster is a verytricky part | 14:05 |
| amotoki | gtema: IMHO at least neutron features in OSC neutornclient plugin should be moved to OSC | 14:06 |
| gtema | which ones? | 14:06 |
| * slaweq is in the meeting now, I will catch up later | 14:06 | |
| amotoki | gtema: this lists the commands covered by OSC neutronclient plugin https://docs.openstack.org/python-neutronclient/latest/cli/osc_plugins.html | 14:07 |
| amotoki | for example, "openstack network trunk create" is covered not by OSC but by OSC neutronclient plugin | 14:08 |
| amotoki | it is a feature in the main neutorn repo. | 14:08 |
| gtema | so we should move them to core OSC, right? | 14:08 |
| amotoki | yes | 14:08 |
| amotoki | I believe it is less confusing | 14:09 |
| gtema | okay. afaik only vpnaas is not currently covered by sdk | 14:09 |
| amotoki | of course advanced services like vpnaas can be moved to OSC/SDK, but I think features in neutron repo should be moved to OSC first. | 14:09 |
| gtema | once we move things into OSC I do not want to reintroduce dep on neutronclient, so need to cover things in SDK first | 14:10 |
| gtema | I will work on that | 14:10 |
| amotoki | sounds good. I will help it. | 14:13 |
| gtema | cool. Pls find out how to enable vpnaas in devstack and you can make change to add it to the devstack-networking jobs. We have currently vpnservice resource, but it is untested (in func jobs) | 14:13 |
| amotoki | at a quick look of the sdk repo, fwaas is covered by sdk. vpnaas, dynamic-routing, bgpvpn and sfc are not covered by SDK | 14:14 |
| gtema | ok, then eventually we should add enable them all in devstack | 14:14 |
| amotoki | gtema: sure. I will check how to enable vpnaas in the jobs. I know how to enable vpnaas in devstack. | 14:15 |
| gtema | sound great, thanks amotoki | 14:15 |
| amotoki | gtema: we first need to make them enabled in the SDK gate, right? | 14:16 |
| gtema | yes | 14:16 |
| amotoki | thanks | 14:17 |
| gtema | thank you | 14:17 |
| amotoki | the summit sounds a great trigger to revive pending topics :) | 14:17 |
| gtema | yeah, right | 14:20 |
| gtema | people eventually get rid of frustration ;-) | 14:20 |
| * gtema talks about himself | 14:21 | |
| frickler | dynamic-routing doesn't work with OVN, so it would need an alternative OVS-based job | 14:21 |
| gtema | oh, and that is where whole fun starts again ;-) | 14:22 |
| slaweq | gtema frickler I'm not sure about which job You are talking now but osc-functional-devstack job now runs with ml2/ovs https://github.com/openstack/python-openstackclient/blob/master/.zuul.yaml#L83 | 14:32 |
| opendevreview | mbu proposed openstack/python-openstackclient master: Wait for volume being available to set bootable or readonly https://review.opendev.org/c/openstack/python-openstackclient/+/845991 | 14:32 |
| slaweq | so we should be good to run dynamic-routing there too probably | 14:33 |
| gtema | we will see if it fails ;-) | 14:33 |
| frickler | slaweq: oh, I wasn't aware of that. then we maybe need to add a job to test things on ovn instead | 14:38 |
| frickler | in theory it shouldn't matter for clients, but there's theory and then there's reality ;) | 14:38 |
| slaweq | frickler true, in theory it shouldn't matter :) | 14:46 |
| gtema | the theory not matching reality was clearly visible through the summit ;-) | 14:47 |
| opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Add VPNaaS Endpoint Group resource https://review.opendev.org/c/openstack/openstacksdk/+/846016 | 15:46 |
| opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Reorg existing vpnaas content https://review.opendev.org/c/openstack/openstacksdk/+/846017 | 15:46 |
| opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: DNM: Test setting sdk version in build_test_packages https://review.opendev.org/c/openstack/ansible-collections-openstack/+/844859 | 17:16 |
| opendevreview | Artem Goncharov proposed openstack/ansible-collections-openstack master: Switch project_info to new SDK https://review.opendev.org/c/openstack/ansible-collections-openstack/+/845782 | 18:18 |
| opendevreview | Thiago Paiva Brito proposed openstack/openstacksdk master: Add update capabilities to Snapshots https://review.opendev.org/c/openstack/openstacksdk/+/778760 | 19:19 |
| opendevreview | mbu proposed openstack/python-openstackclient master: Wait for volume being available to set bootable or readonly https://review.opendev.org/c/openstack/python-openstackclient/+/845991 | 19:40 |
| opendevreview | mbu proposed openstack/python-openstackclient master: Wait for volume being available to set bootable or readonly https://review.opendev.org/c/openstack/python-openstackclient/+/845991 | 21:23 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!