Chris Dent 09905baab2 Use both unit and functional for coverage testing
Placement has always relied heavily on functional testing for both API
and database testing, so not including those tests in 'coverage' leads
to misleading results.

This change adjusts the cover job in tox to use a test path of
placement/tests, resulting in all the tests running.

In the process .coveragerc is updated to be placement oriented
and make sure we do not ignore branches.

This is in preparation for turning on a check job for coverage.
See this email for more on that:

http://lists.openstack.org/pipermail/openstack-dev/2018-September/134385.html

A followup patch will turn on a check job for it.

Change-Id: I6c122facc9c9f6e0b2a1d69c6aaf5faeee7cf253
2018-09-14 13:30:14 -06:00
2018-09-06 11:45:11 -05:00
2018-09-14 16:12:49 +00:00
2018-08-31 14:24:59 +00:00
2018-09-06 11:45:11 -05:00
2012-02-08 19:30:39 -08:00
2018-01-12 17:05:11 +08:00
2018-09-13 16:45:23 -06:00
2010-05-27 23:05:26 -07:00
2018-09-10 11:11:26 -06:00
2017-03-02 11:50:48 +00:00

Warning: This repository is currently in a state of flux as the placement service is extracted from nova. While that is happening this repository is not yet fully working.

If you are viewing this README on GitHub, please be aware that placement development happens on OpenStack git and OpenStack gerrit.

Team and repository tags

image

OpenStack Placement

OpenStack Placement provides an HTTP service for managing, selecting, and claiming providers of classes of inventory representing available resources in a cloud.

API

To learn how to use Placement's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure OpenStack Placement, consult the documentation available online at:

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:

For the time being bugs in placement should be created in the Nova bug tracker with a tag of ``placement``.

Developers

For information on how to contribute to Placement, please see the contents of CONTRIBUTING.rst.

Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all tests.

Further developer focused documentation is available at:

Description
OpenStack resource provider inventory allocation service
Readme 22 MiB
Languages
Python 94.4%
PHP 4.3%
Shell 1.2%