For the reference, this was fixed under this bug: https://bugs.launchpad.net/fuel/+bug/1272349
Here's a fuel-docs review updating the release notes for 5.1, I've added a note about this there: https://review.openstack.org/117672 On Fri, Sep 12, 2014 at 1:07 AM, Aleksey Kasatkin <akasat...@mirantis.com> wrote: > Yes, 'public' is not assigned to all nodes in case of Neutron. Though it can > be assigned optionally. Documentation is to be fixed. > > > Aleksey Kasatkin > > > On Fri, Sep 12, 2014 at 10:41 AM, Jesse Pretorius > <jesse.pretor...@gmail.com> wrote: >> >> The release notes in master have this note under 'Other limitations': >> >> Deployments done through the Fuel UI create all of the networks on all >> servers even if they are not required by a specific role. For example, a >> Cinder node has VLANs created and addresses obtained from the public >> network. >> >> >> I don't think that this is true for 5.1 onwards - there was some work done >> recently to change this behaviour... well, I think it's all merged now? >> >> -- >> Mailing list: https://launchpad.net/~fuel-dev >> Post to : fuel-dev@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~fuel-dev >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : fuel-dev@lists.launchpad.net > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > -- Dmitry Borodaenko -- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp