5f887d851e
Recently there was some confusion caused by the fact the gabbi tests
used by the placement API have names like this:
gabbi.suitemaker.test_placement_api_usage_create_provider
This means that the names cannot be matched against tox interactions
like:
tox -efunctional -- nova.tests.functional.api.openstack
This change makes it so the tests are generated with names like:
nova.tests.functional.api.openstack.placement.test_placement_api.usage_create_provider
So this change is submitted for review if people care. The other
option is to:
tox -efunctional placement
gabbi was updated to allow this functionality in a clean form, so
this depends on a change to global requirements but can work
without it if required.
Depends-On: Ie93c0e680a80fc7f157e2b5b9dfc2ab17f934f10
Change-Id: I8579bf7529a7298c4d049e47cc3cde1731a5e666
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: