Hi,
btw, we should also take into account the possibility to share networks in
Fuel-8.0. So if cluster is configured with shared public and management
networks then moving controllers into different network node groups (racks)
is fine and it will work out of the box [0] and we should not forbid su
Hi,
I would also prefer second solution. The only real downside of it is the
possibility to configure invalid cluster (for instance configure default
"controller" roles in different racks). But such invalid configuration is
possible only under some conditions:
- User should configure multi-rack en
> Random choices aren't good IMHO, let's use defaults.
What if neither of node is in default group? Still use default group?
And prey that some third-party plugin will handle this case properly?
AFAIU, default nodegroup is slightly artificial thing. There's no such
thing like *default* nodegroup.
On 15.01.2016 10:19, Aleksandr Didenko wrote:
> Hi,
>
> We need to come up with some solution for a problem with VIP generation
> (auto allocation), see the original bug [0].
>
> The main problem here is: how do we know what exactly IPs to auto
> allocate for VIPs when needed roles are in differe
Hi,
We need to come up with some solution for a problem with VIP generation
(auto allocation), see the original bug [0].
The main problem here is: how do we know what exactly IPs to auto allocate
for VIPs when needed roles are in different nodegroups (i.e. in different
IP networks)?
For example '
