fb512cd3ab
Part of support for nested stacks and updates story To add nested stack support to Valet, make up for missing Heat resource Orchestration IDs in nested resources by generating a subset of Heat stack lifecycle scheduler hints for each resource in advance, store them as opaque metadata in Valet, then leverage the metadata at Nova scheduling time. Make additional accommodations in anticipation of complexities brought about by adding support for stack updates. To add a minimally viable amount of Heat `stack-update` support to Valet, significantly restrict the number of update use cases using a set of acceptance criteria. Skip holistic placement at `stack-update` time in favor of Valet's existing re-plan mechanism, placing or replacing resources one at a time, albeit still in consideration of other resources in the same stack hierarchy. Change-Id: I4654bcb4eacd5d64f76e262fe4c29553796e3f06 Story: #2001139 Task: #4858 |
||
|---|---|---|
| api-ref/source | ||
| bin | ||
| debian | ||
| devstack | ||
| doc | ||
| etc | ||
| plugins | ||
| releasenotes/source | ||
| tools/utils | ||
| valet | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| babel.cfg | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.md | ||
| requirements.txt | ||
| run_all_tests.sh | ||
| run_examples.sh | ||
| run_test.sh | ||
| run_until_fail.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Valet
Valet is a cloud resource placement optimization service. Valet gives OpenStack the ability to optimize cloud resources while simultaneously meeting a cloud application's QoS requirements. Through model driven orchestration, the target state of Valet is to provide “holistic OpenStack data-plane resource placement”. Valet provides an api service, a placement optimizer (Ostro), a high availability data storage and persistence layer (Music), and a set of OpenStack plugins.
Why Valet exists:
For large-scale, multi-tenant cloud operators, there is a large demand for tenant specific service requests. This demand drives the growth of the number of cloud availability zones and compartmentalization of the cloud, which then leads to increased provisioning and sub-optimal use of cloud and staff resources. Also, security requirements lead us to place specialized network appliances of these tenants separately into “exclusive” hosts that do not have internet connectivity.
Valet responds to the challenges outlined above by enhancing OpenStack Nova scheduling to develop resource management optimization. By planning the placement of all the cloud resources for an application in a holistic manner, there is opportunity to reduce cross-rack traffic, reduce resource fragmentation, and save on operating costs.
Learn more about Valet:
- OpenStack Newton Summit Presentation (Austin, TX, 27 April 2016)
- Presentation Slides (PDF)
Valet consists of the following components:
- valet-openstack: a set of OpenStack plugins used to interact with Valet
- valet-api: an API engine used to interact with Valet
- Ostro: a placement optimization engine
- ostro-listener: a message bus listener used in conjunction with Ostro and Music
Additional documents:
- OpenStack Heat Resource Plugins: Heat resources
- Placement API: API requests/responses
- Using Postman with valet-api: Postman support
License:
Valet 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.