yahoo-eng-team team mailing list archive

[bjolo <bjorn.lofdahl@xxxxxxxxx>]

Public bug reported:

There seems to be limitation for a compute node to only have interface
on one segment in a multisegment network. This feels wrong and limits
the compute resources since they can only be part of one segment.

The purpose of multi segment networks is to group multiple segments
under one network name. i.e. operators should be able to expand the IP
pool without having to create multiple network for it like internet1,
internet2, etc.

The way it should work is that a compute node can belong to one or more
segments. It should be up to the operator to decide how they want to
segment the compute resources or not. It should not be enforced by the
simple need to add IP ranges to a network.

way to reproduce.
1. configure compute nodes to have bridges configured on 2 segments
2. create a network with 2 segments.
3. create the segments
2018-04-17 15:17:59.545 25 ERROR oslo_messaging.rpc.server
2018-04-17 15:18:18.836 25 ERROR oslo_messaging.rpc.server [req-4fdf6ee1-2be3-49c5-b3cb-62a2194465ab - - - - -] Exception during message handling: HostConnectedToMultipleSegments: Host eselde03u02s04 is connected to multiple segments on routed provider network '5c1f4dd4-baff-4c59-ba56-bd9cc2c59fa4'.  It should be connected to one.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  There seems to be limitation for a compute node to only have interface
  on one segment in a multisegment network. This feels wrong and limits
  the compute resources since they can only be part of one segment.
  
  The purpose of multi segment networks is to group multiple segments
  under one network name. i.e. operators should be able to expand the IP
  pool without having to create multiple network for it like internet1,
  internet2, etc.
  
  The way it should work is that a compute node can belong to one or more
  segments. It should be up to the operator to decide how they want to
  segment the compute resources or not. It should not be enforced by the
  simple need to add IP ranges to a network.
  
  way to reproduce.
  1. configure compute nodes to have bridges configured on 2 segments
  2. create a network with 2 segments.
  3. create the segments
  2018-04-17 15:17:59.545 25 ERROR oslo_messaging.rpc.server
- 2018-04-17 15:18:18.836 25 ERROR oslo_messaging.rpc.server [req-4fdf6ee1-2be3-49c5-b3cb-62a2194465ab - - - - -] Exception during message handling: HostConnectedToMultipleSegments: Host eselde03u02s04.seld.rnd.ericsson.se is connected to multiple segments on routed provider network '5c1f4dd4-baff-4c59-ba56-bd9cc2c59fa4'.  It should be connected to one.
+ 2018-04-17 15:18:18.836 25 ERROR oslo_messaging.rpc.server [req-4fdf6ee1-2be3-49c5-b3cb-62a2194465ab - - - - -] Exception during message handling: HostConnectedToMultipleSegments: Host eselde03u02s04 is connected to multiple segments on routed provider network '5c1f4dd4-baff-4c59-ba56-bd9cc2c59fa4'.  It should be connected to one.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1764738

Title:
  routed provider networks limit to one host

Status in neutron:
  New

Bug description:
  There seems to be limitation for a compute node to only have interface
  on one segment in a multisegment network. This feels wrong and limits
  the compute resources since they can only be part of one segment.

  The purpose of multi segment networks is to group multiple segments
  under one network name. i.e. operators should be able to expand the IP
  pool without having to create multiple network for it like internet1,
  internet2, etc.

  The way it should work is that a compute node can belong to one or
  more segments. It should be up to the operator to decide how they want
  to segment the compute resources or not. It should not be enforced by
  the simple need to add IP ranges to a network.

  way to reproduce.
  1. configure compute nodes to have bridges configured on 2 segments
  2. create a network with 2 segments.
  3. create the segments
  2018-04-17 15:17:59.545 25 ERROR oslo_messaging.rpc.server
  2018-04-17 15:18:18.836 25 ERROR oslo_messaging.rpc.server [req-4fdf6ee1-2be3-49c5-b3cb-62a2194465ab - - - - -] Exception during message handling: HostConnectedToMultipleSegments: Host eselde03u02s04 is connected to multiple segments on routed provider network '5c1f4dd4-baff-4c59-ba56-bd9cc2c59fa4'.  It should be connected to one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1764738/+subscriptions