cc47acaf8d
Confirm and correct list methods and response codes in os-cells. This is mostly just checking, correcting and adding methods, but in the process of doing that it became clear that there was quite a bit missing so several TODO notes have been left in place so that the next stages of work are a bit more obvious. * 405 has been removed everywhere as we don't send that response * 400 badRequest is required anywhere, as that's what you'll get if tenant_id does not match the context's project_id * 503 does not happen as there's no application controlled proxying in this api * the URL for listing cells with details was incorrect * the example response for cells with details was an empty list, this is now a todo suggesting an as yet non-existent file * capacities was not listed, now is * not clear what capacities really are, so a TODO * creating a new cell (via POST) was not there, so that is now added as a method * for that POST, request and response bodies, parameters currently a TODO * Update (PUT) and DELETE of a cell has been added, but details are TODO Part of bp:api-ref-in-rst Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast