Comment 0 for bug 1473047

In a deployment with multiple network segments (https://docs.mirantis.com/openstack/fuel/fuel-6.0/reference-architecture.html#mcn-arch) there is no way to assign node interfaces ((private), public, management, storage, and fuelweb_admin) to different Node Groups.

Use cases:
1) (Most probable) Customer has two different network infrastructures (the one with multiple L2 domains, the other with single L2 to which admin or storage network is connected). In that case some of interfaces needs to belong to one Node Group while the others to different Node Group.

2) (Less probable - AT&T case) Customer connects specific node interface to different Node Group.

Secondly, there should be a possibility to assign whatever number of Node Groups to one, particular node.

[FUEL_SERVER ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
    - experimental
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "521"
  build_id: "2015-06-08_06-13-27"
  nailgun_sha: "4340d55c19029394cd5610b0e0f56d6cb8cb661b"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "7766818f079881e2dbeedb34e1f67e517ed7d479"
  fuel-library_sha: "f43c2ae1af3b493ee0e7810eab7bb7b50c986c7d"
  fuel-ostf_sha: "7c938648a246e0311d05e2372ff43ef1eb2e2761"
  fuelmain_sha: "bcc909ffc5dd5156ba54cae348b6a07c1b607b24"