[openstack-dev] [nova] [baremetal] Devstack support appears broken - how can I help?

Devananda van der Veen devananda.vdv at gmail.com
Thu Jan 10 20:14:45 UTC 2013


Hi Maru!

Glad to hear others are starting to poke at this :)

Yes, devstack support is just slightly lacking. A lot of parts of baremetal
have been developed outside trunk during the last six months and only just
merged in the last two weeks. We have been maintaining a separate testing
branch, but I'm trying to get away from that now that (almost) everything
is in trunk! Unfortunately, the nova-baremetal-manage command got split up
at the last minute and merged with only the "db sync" command in place,
whereas the "node" and "interface" commands were implemented as a new API
extension, which didn't land in time for Grizzly-2. It's here:

https://review.openstack.org/#/c/19077/

Until the new API extension lands -- and we build a python-novaclient
extension and update devstack to use those -- there are two ways to go
about adding nodes.

a) pull the last revision of nova-baremetal-manage which had node/interface
commands from here:
   https://review.openstack.org/#/c/11366/17/bin/nova-baremetal-manage
b) manually insert the record into the nova_bm.bm_nodes table.

At the moment, within devstack, if you leave the BM_FIRST_MAC and
BM_SECOND_MAC variables empty, it should still start everything necessary
for baremetal support. You can then manually insert one record in the
bm_nodes table, and during the next periodic_update (happens every 60
seconds) nova-compute will pick up the new information and you should be
good to go.


Regards,
Devananda



On Thu, Jan 10, 2013 at 10:55 AM, Maru Newby <mnewby at internap.com> wrote:

> I have tried the preliminary devstack support for the new baremetal
> framework only to find it apparently broken.  Specifically, lib/baremetal
> calls nova-baremetal-mange with an as-yet unsupported 'node' command.  It
> appears that all patches associated with the blueprint (
> http://wiki.openstack.org/GeneralBareMetalProvisioningFramework) have
> merged, yet the blueprint documentation and devstack configuration both
> depend on functionality that has yet to be implemented.
>
> For those of you who are working on baremetal and have working
> configurations, is there anything (code and documentation) you can point me
> to?
>
> Also, as I am currently tasked with ensuring baremetal support for nova
> here at Internap, I would be happy to assist in the development effort.
>  How can I get involved?
>
> Thanks!
>
>
> Maru
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130110/b5e56214/attachment.html>


More information about the OpenStack-dev mailing list