yahoo-eng-team team mailing list archive

[Harald Jensås <harald.jensas@xxxxxxxxx>]

** Summary changed:

- Unable to create port with fixed-ips allocation for 'baremetal' ironic instance
+ Routed Networks - Ironic Port Binding - baremetal node on remote non-local subnet

** Description changed:

  When using routed networks and a subnet is associated with a segment ip-
  allocation will be deferred unless binding:host_id is provided. This is
  all fine for ports that will end up on a nova host, we want to make sure
  the ip-allocation is for a subnet on a segment that is local to the
  target host.
  
- For the Ironic, baremtal, usecase this is however an issue since the
- port will not actually bind to any host. With the current implementation
- I think the only way to make this work would require a seperate Ironic
- node in each network segment.
+ For the Ironic, baremtal, usecase the 'host_id' used for port binding is the node running the Ironic services.
+ https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/network/flat.py#L64
+ 
+ 
+ This would require a separate ironic node in each segment of a routed network? e.g one per rack in a spine-and-leaf datacenter?

** Also affects: ironic
   Importance: Undecided
       Status: New

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

Title:
  Routed Networks - Ironic Port Binding - baremetal node on remote non-
  local subnet

Status in Ironic:
  New
Status in neutron:
  In Progress

Bug description:
  When using routed networks and a subnet is associated with a segment
  ip-allocation will be deferred unless binding:host_id is provided.
  This is all fine for ports that will end up on a nova host, we want to
  make sure the ip-allocation is for a subnet on a segment that is local
  to the target host.

  For the Ironic, baremtal, usecase the 'host_id' used for port binding is the node running the Ironic services.
  https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/network/flat.py#L64

  
  This would require a separate ironic node in each segment of a routed network? e.g one per rack in a spine-and-leaf datacenter?

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