yahoo-eng-team team mailing list archive

[Pavlo Shchelokovskyy <1544195@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When booting a nova instance with baremetal flavor, one can not provide
a pre-created neutron port to "nova boot" command.

The reason is obvious - to successfully deploy, mac address of the port
must be the same as mac address of the ironic port corresponding to the
ironic node where provisioning will happen, and although it is possible
to specify a mac address during port create, a user can not know to
which exactly ironic node provisioning will be assigned to by nova
compute (more over, ordinary user has no access to list of ironic
ports/macs whatsoever).

This is most probably a known limitation, but the big problem is that it
breaks many sorts of cloud orchestration attempts. For example, the most
flexible in terms of usage approach in Heat is to pre-create a port, and
create the server with this port provided (actually this is the only way
if one needs to assign a floating IP to the instance via Neutron). Some
other consumers of Heat extensively use this approach.

So this limitation precludes Murano or Sahara to provision their
instances on bare metal via Nova/Ironic.

The solution might be to update the mac of the port to correct one (mac
address update is possible with admin context) when working with
baremetal nodes/Ironic.

** Affects: nova
     Importance: Undecided
         Status: Confirmed


** Tags: ironic

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1544195

Title:
  User can not provision ironic node via nova when providing pre-created
  port

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  When booting a nova instance with baremetal flavor, one can not
  provide a pre-created neutron port to "nova boot" command.

  The reason is obvious - to successfully deploy, mac address of the
  port must be the same as mac address of the ironic port corresponding
  to the ironic node where provisioning will happen, and although it is
  possible to specify a mac address during port create, a user can not
  know to which exactly ironic node provisioning will be assigned to by
  nova compute (more over, ordinary user has no access to list of ironic
  ports/macs whatsoever).

  This is most probably a known limitation, but the big problem is that
  it breaks many sorts of cloud orchestration attempts. For example, the
  most flexible in terms of usage approach in Heat is to pre-create a
  port, and create the server with this port provided (actually this is
  the only way if one needs to assign a floating IP to the instance via
  Neutron). Some other consumers of Heat extensively use this approach.

  So this limitation precludes Murano or Sahara to provision their
  instances on bare metal via Nova/Ironic.

  The solution might be to update the mac of the port to correct one
  (mac address update is possible with admin context) when working with
  baremetal nodes/Ironic.

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