[library] Optionally separate L3 Agent role

Bug #1322587 reported by Jesse Pretorius
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Jesse Pretorius

Bug Description

This is a wishlist item.

We'd like to see an optional separation of the L3 Agent deployment from the Controller role. We'd prefer to implement the L3 Agents on separate hardware to help with scaling, especially with provider network traffic, and to help with security.

Tags: library
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :
Changed in fuel:
milestone: none → 5.1
Changed in fuel:
importance: Undecided → Wishlist
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

If it's part of a feature it should be a blueprint, not a bug.

Changed in fuel:
status: New → Incomplete
assignee: nobody → Jesse Pretorius (jesse-pretorius)
Revision history for this message
Mike Scherbakov (mihgen) wrote :

anyway, please feel free to propose the code. It is something which we definitely need in Fuel and always have to postpone due to other items.

Dmitry Ilyin (idv1985)
summary: - Optionally separate L3 Agent role
+ [library] Optionally separate L3 Agent role
tags: added: library
Changed in fuel:
status: Incomplete → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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