Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
This session will discuss some of the issues in the existing nova API (both core and extensions), and how to address them going forward.
There are at least three classes of issues:
1) outright bugs (i.e. deleting an already deleted floating ip returns 202, not 400)
2) inconsistencies in return codes (when is 200 used vs. 202)
3) holes in function (ip pools are gettable via API, but can only be created with nova-manage)
There is also the need to have a stable API.
What of these issues can we address in 2.0 without breaking anyone? What about a 2.1 which is limited to just return code cleanup? What is the plan for 3.0, both time frame, and adding new APIs to the core content?
Thursday October 18, 2012 9:50am - 10:30am PDT
Emma AB
