ha_per_neutron_agent
Bug #1497384 reported by
Aleksey Chuprin
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) |
tags: | added: area-library |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
To post a comment you must log in.
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