Ladislav Smola 0d31548886 Using flavors from Roles
-flavors defined in roles are now written into parameters that
 are fed to heat
-association for image name and flavor param are stored in
 template tools by hard, for Icehouse
-exceptions for processing stack erros set to 400
-fixed docs of the helper functions

Change-Id: I0e3e8dcd78a36fc1e008eedfa6ec793015e3ac1e
2014-03-12 10:21:37 +01:00
2014-02-18 13:50:14 -05:00
2014-02-24 23:11:05 +00:00
2014-03-12 10:21:37 +01:00
2013-05-02 17:32:04 -04:00
2013-05-02 14:55:43 -04:00
2014-02-25 21:45:31 +09:00
2014-02-18 13:50:14 -05:00
2013-09-30 10:45:06 -04:00
2014-02-14 17:57:06 +00:00

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.

Building the Docs

From the root directory:

python setup.py build_sphinx

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
Description
RETIRED, A service for managing OpenStack deployments
Readme 5.8 MiB