
This patch adds support for a REST API for CRUD operations on traits. GET /traits: Returns all resource classes. PUT /traits/{name}: To insert a single custom trait. GET /traits/{name}: To check if a trait name exists. DELETE /traits/{name}: To delete the specified trait. GET /resource_providers/{uuid}/traits: a list of traits associated with a specific resource provider PUT /resource_providers/{uuid}/traits: Set all the traits for a specific resource provider DELETE /resource_providers/{uuid}/traits: Remove any existing trait associations for a specific resource provider Partial implement blueprint resource-provider-traits Change-Id: Ia027895cbb4f1c71fd9470d8f9281d2bebb6d8a2
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
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.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
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: