ha_per_neutron_agent

Bug #1497384 reported by Aleksey Chuprin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
Medium
Fuel Sustaining
Mitaka
Won't Fix
Medium
Fuel Library (Deprecated)
Newton
Triaged
Medium
Fuel Sustaining

Bug Description

Fuel 6.1/7.0/master

We have use case where we need to be able enable/disable ha separately for each neutron agent. In current implementation we are not able to do that, because we use one parameter ($ha_agents) for all neutron agents.

description: updated
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
Changed in fuel:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 8.0
assignee: Fuel Library Team (fuel-library) → Sergey Vasilenko (xenolog)
tags: added: feature
Changed in fuel:
status: Confirmed → Triaged
assignee: Sergey Vasilenko (xenolog) → Fuel Library Team (fuel-library)
Revision history for this message
Dmitriy Novakovskiy (dnovakovskiy) wrote :

Hi Aleksey,

Can you please explain the use case for per-agent HA enablement? What's the goal, when is it needed? Also, does it apply to L3 agent on controllers, DVR, both?

Thanks

Revision history for this message
Sergey Vasilenko (xenolog) wrote :

In the https://review.openstack.org/#/c/232141/

for l2, l3, dhcp and metadata agents I reserved flags name:
neutron_advanced_configuration/l2_agent_ha
neutron_advanced_configuration/l3_agent_ha
neutron_advanced_configuration/dhcp_agent_ha
neutron_advanced_configuration/metadata_agent_ha

This flags may be placed into neutron_advanced_configuration sub-tab into settings tab on UI

Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Changed in fuel:
milestone: 8.0 → 9.0
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.