In Kilo the installation guide did contains the section of installing a
dedicated network node.
in current Pike release it mentioned to configure controller as network
node.
https://docs.openstack.org/neutron/pike/install/controller-install-option2-
ubuntu.html
is this for a particular reason ?
I think that indeed make sens as because now a day most the installations
tend to either be within a dockerized solution or a relatively fair amont
(3/4) of large hw nodes.
One situation that would require dedicated hw would be a very large
installation requiring you to lower the network pression
> On 1. Feb 2018, at 19:42, Flint WALRUS wrote:
>
> I think that indeed make sens as because now a day most the installations
> tend to either be within a dockerized solution or a relatively fair amont
> (3/4) of large hw nodes.
>
> One situation that would require dedicated hw would be a ve
Don’t get it, are you talking about the Neutron FWaaS ? If so, yes it would
avoid the so called High traffic situation that I talked about on baremetal.
Docker is less subject to such issue as the workload would so be
distributed among multiple nodes thanks to LBaaS, LB Solution such as
HAProxy/Ve
Interesting, could you provide an example ?
Le jeu. 1 févr. 2018 à 22:48, Christian Berendt <
[email protected]> a écrit :
>
>
> > On 1. Feb 2018, at 21:42, Flint WALRUS wrote:
> >
> > Don’t get it, are you talking about the Neutron FWaaS ? If so, yes it
> would avoid the so called H
> On 1. Feb 2018, at 21:42, Flint WALRUS wrote:
>
> Don’t get it, are you talking about the Neutron FWaaS ? If so, yes it would
> avoid the so called High traffic situation that I talked about on baremetal.
I expressed myself in a misleading way.
Depending on the firewall / security concept
