c1ffc35d56
.gitreview must be updated to move to the openstack namespace. boto==2.5.1 being in the requirements also prevents that change from merging. There is no usage of the boto library anywhere in tuskar. None of the binaries that boto ships are executed. It is unclear why boto was even added to requirements.txt. Meanwhile we are under stricter global requirements due to being moved into the official openstack namespace, so having boto==2.5.1 listed here causes our gate to fail. Change-Id: Ie54f5418dff31caf8f25c01c252839a56747518c |
||
---|---|---|
contrib | ||
docs | ||
etc/tuskar | ||
tools | ||
tuskar | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.travis.yml | ||
CONTRIBUTING.rst | ||
INSTALL.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Tuskar
What is Tuskar?
Tuskar gives administrators the ability to control how and where OpenStack services are deployed across the datacenter. Using Tuskar, administrators divide hardware into "resource classes" that allow predictable elastic scaling as cloud demands grow. This resource orchestration allows Tuskar users to ensure SLAs, improve performance, and maximize utilization across the datacenter.
Tuskar services are available via a RESTful API and management console through which administrators are able to classify their hardware and define their datacenters. In addition, Tuskar components provide administrators with performance monitoring, health statistics, and usage metrics, aiding in capacity planning and hardware procurement decisions.
For additional information, take a look at the Tuskar documentation.
Installation Information
Please see INSTALL.rst for an installation guide.
Contributing
Interested in contributing? Take a look at CONTRIBUTING.rst for details on how to do so.
Contact Us
Join us on IRC (Internet Relay Chat):
Network: Freenode (irc.freenode.net/tuskar)
Channel: #tuskar