yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #04973
[Bug 1180454] Re: Cannot orchestrate PXE booting from nova
(This was in H3).
** Changed in: nova
Assignee: Devananda van der Veen (devananda) => dkehn (dekehn)
** Changed in: nova
Status: Incomplete => Fix Released
** Changed in: nova
Milestone: None => havana-rc1
--
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/1180454
Title:
Cannot orchestrate PXE booting from nova
Status in OpenStack Compute (Nova):
Fix Released
Status in tripleo - openstack on openstack:
Triaged
Bug description:
Nova baremetal requires PXE booting of nodes, but the network code in
nova doesn't arrange for PXE DHCP options to be supplied [by quantum].
In the same manner that the MAC address limitations are exported by
the driver, DHCP options should be exported by the driver and then
passed onto the network provider - and for the quantum driver we can
pass these onto the port for quantum.
In nova/compute/manager.py:
def _build_instance(self, context, request_spec, filter_properties,
...
macs = self.driver.macs_for_instance(instance)
network_info = self._allocate_network(context, instance,
requested_networks, macs, security_groups)
I suggest changing that to be something like
macs = self.driver.macs_for_instance(instance)
dhcp_options = self.driver.dhcp_options_for_instance(instance)
network_info = self._allocate_network(context, instance,
requested_networks, macs, security_groups, dhcp_options)
that calls _allocate_network which calls
self.network_api.allocate_for_instance
- and self.network_api for quantum environments is
nova/network/quantumv2/api.py's API instance - so once dhcp_options
gets down to there, you can use the Quantum API's directly and poke it
in when the port is allocated/updated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1180454/+subscriptions