Hi Drew, Generally you need to create a new api extention and make some changes in the main servers.py
The scheduler-hints API extension does this kind of thing, so if you look at: api/openstack/compute/contrib/scheduler_hints.py for how the extension is defined, and look in api/poenstack/compute/servers.py code for "scheduler_hints" (e.g. _extract_scheduler_hints() ) then that should point you in the right direction. Hope that helps, Phil > -----Original Message----- > From: Drew Fisher [mailto:drew.fis...@oracle.com] > Sent: 25 October 2013 16:34 > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] extending nova boot > > Good morning! > > I am looking at extending nova boot with a few new flags. I've found enough > examples online that I have a working extension to novaclient (I can see the > new flags in `nova help boot` and if I run with the --debug flag I can see the > curl requests to the API have the data. > > What I can't seem to figure out is how nova-api processes these extra > arguments. With stable/grizzly bits, in > nova/api/openstack/compute/servers.py, I can see where that data is > processed (in Controller.create()) but it doesn't appear to me that any > leftover flags are handled. > > What do I need to do to get these new flags to nova boot from novaclient > into nova-api and ultimately my compute driver? > > Thanks for any help! > > -Drew Fisher > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
