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 is part of http://
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 here: https:/
Project information
- Licence:
- Apache Licence
View full history Series and milestones
trunk series is the current focus of development.
All bugs Latest bugs reported
-
Bug #1487067: Replace 'nova_overcloud_config.yml' with 'nova_overcloud_config.yaml'
Reported -
Bug #1481370: system logging module is still in use in many places
Reported -
Bug #1452752: keystone_authtoken section is wrong in default shipped tuskar.conf.sample
Reported -
Bug #1422470: Installation instruction contains wrong description
Reported -
Bug #1387487: tripleo-image-elements/elements/tuskar-ui /os-refresh-config /post-configure.d/101-tuskar-ui needs authentication from Keystone
Reported
All blueprints Latest blueprints
-
Plan REST API Refinements for Template Backed Storage
Registered -
Use Keystone Trusts to avoid storing user credentials
Registered -
Update documentation to reflect recent API changes
Registered -
Enable py33 voting in jenkins gating
Registered -
Allow tagging of nodes
Registered