(re-sending to fuel-dev) Roman
On Tuesday, January 21, 2014, Aleksey Kasatkin <[email protected]> wrote: > Hi team, > > This bug https://launchpad.net/bugs/1262149 (Fixed networks-to-nics > assignment) and PR https://review.openstack.org/#/c/66618/ (Flexible > networks-to-nics assignment) were created to address the problem that > networks-to-nics assignment is now fixed, i.e. it doesn't depend on > cluster's networking configuration. Assignment was done assuming that > networks tagging for cluster is set by default. But networks tagging can be > altered before we add node into the cluster. We will get wrong assignment > in this case. > > Networks-to-nics assignment is made flexible and that leads to some > differences in networking configuration behaviour. > > Adding nodes to default configuration. > > Netw.configuration > > Netw-to-nics map (FIX) > > Netw-to-nics map (FLEX) > > Nova default (public and floating are untagged) pxe = eth0 > > eth0: admin > > eth1: public, floating, management, storage, fixed > > eth0: admin, management, storage, fixed > > eth1: public, floating > > Neutron default (gre) pxe = eth0 > > eth0: admin > > eth1: public, management, storage > > same as “fix” > > Neutron default (vlan) pxe = eth0 > > eth0: admin > > eth1: public, management, storage > > eth2: private > > same as “fix” > > Adding nodes to changed configuration. > > Netw.configuration > > Netw-to-nics map (FIX) > > Netw-to-nics map (FLEX) > > Nova (all networks are tagged) pxe = eth0 > > eth0: admin > > eth1: public, floating, management, storage, fixed > > eth0: admin, management, storage, fixed, public, floating > > Nova (management, public and floating are untagged) pxe = eth0 > > eth0: admin > > eth1: public, floating, management, storage, fixed > > eth0: admin, storage, fixed > > eth1: public, floating > > eth2: management > > So, “fix” mapping is always the same for given provider and PXE NIC. > “Flex” one is sensitive to current networks tagging. Other mapping features > (map “public” to the first free NIC which is not PXE, predictable mapping > for the given networking configuration, map “private” to dedicated NIC, > etc.) are preserved. > > When you press “Load Defaults” button on “Configure interfaces ...” tab > you will also get mapping that is sensitive to current networks tagging > (“flex”). > > Please note that you will get different netw-to-nics mappings for nodes > which were added before and after change of networks tagging (“flex”) > instead of equal default mappings for all cluster nodes (“fix”). I consider > that is not a problem as an operator must change netw-to-nics mappings in > both cases (i.e. for “fix” and “flex”) to get it work because of changed > networks tagging. > > Please feel free to pass your questions and concerns here. > > > Aleksey Kasatkin > > S. Software Developer | Mirantis, Inc. | http://www.mirantis.com > cell: +380938330852 | skype: alexeyk_ru > > -- > You received this message because you are subscribed to the Google Groups > "fuel-core-team" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:_e({}, > 'cvml', 'fuel-core-team%[email protected]');>. > For more options, visit > https://groups.google.com/a/mirantis.com/groups/opt_out. >
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
