[library] Optionally separate L3 Agent role

[Jesse Pretorius]

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.

[Vladimir Kuklin (vkuklin)]

this is a part of granular deployment feature. https://blueprints.launchpad.net/fuel/+spec/fuel-pluggable-architecture

[Dmitry Borodaenko (angdraug)]

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

[Mike Scherbakov (mihgen)]

Jesse,
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.