Add action to unregister neutron agent

Bug #1921144 reported by Martin Kalcok
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron Open vSwitch Charm
Confirmed
Undecided
Unassigned

Bug Description

This is a followup bug based on comment in this bug https://bugs.launchpad.net/charm-nova-compute/+bug/1691998 . The comment mentions that when nova-compute unit is removed, neutron agent (that was originally subordinate charm of this unit) remains registered in the Openstack and needs to be removed manually.

Similar issue was solved in nova-compute charm by adding a action `remove-from-cloud` that unregisters nova-compute service from nova-cloud-controller which allows for cleaner removal of the unit.

I think that similar approach could be used in neutron-ovs charm.

Changed in charm-neutron-openvswitch:
assignee: nobody → Gabriel Angelo Sgarbi Cocenza (gabrielcocenza)
Changed in charm-neutron-openvswitch:
status: New → In Progress
Revision history for this message
Frode Nordahl (fnordahl) wrote :

This does indeed sound useful. Just wanted to point out that we have multiple SDN alternatives that might benefit from this, the traditional Neutron ML2/OVS, the Neutron ML2/OVN and possibly other third party offerings. So please do take reusability into account when implementing this, perhaps it makes sense to add the action to the neutron-api charm for everyone to use from the start?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-openvswitch (master)
Revision history for this message
Frode Nordahl (fnordahl) wrote :

Alvaro pointed out OOB that having the action centralized is undesirable because in a large deployment it would be cumbersome for the end user to feed the correct agent names into action parameters to the neutron-api charm. If the n-ovs or other SDN charm initiates the operation it will be able to provide the correct agent names automatically.

Another suggestion was to host the logic within the neutron-api charm and have some inter-charm communication happen between SDN-charm and the neutron-api charm. The benefit of this approach is that we will avoid putting credentials where they may not currently be required.

However, for this to work we would have to figure out if this would work in a synchronous manner. I.e. the charm operator would want to run `juju run-action --wait SDN-UNIT/0 remove-agents; do the next thing after the agent has been removed`

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-openvswitch (master)

Change abandoned by "Gabriel Angelo Sgarbi Cocenza <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-neutron-openvswitch/+/808482

Changed in charm-neutron-openvswitch:
assignee: Gabriel Angelo Sgarbi Cocenza (gabrielcocenza) → nobody
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.