Current documentation for “tripleo”
To classify a blueprint as documentation, set the Implementation status to “Informational” When the blueprint's Definition status is marked “Approved”, it will appear in this listing.
|
Making the overcloud deployment fully HA
for tripleo
We need to basically implement HA across the board.
|
|
|
Scaling work to do during icehouse
for tripleo
What does scaling mean at the tripleo level; where do we do well, where are lacking, what do we need to design? For both the deployment activity itself as well as the deployed cloud...
|
|
|
We need to deliver UI which tells complete overcloud installation story. It has to be slick, user friendly and functional.
|
|
|
Currently once you do a deployment with TripleO, you are unable to change or rotate any of the passwords used in the overcloud.
For day 2 operations we need to be able to change all passwords in the environment in a case where an Operator leaves, or as part of standard security protocol (passwords rotated every 6 m...
|
|
|
Tuskar infrastructure modelling
for tripleo
Goal: To gain consensus on a suitable infrastructure model in Tuskar.
|
|
|
Add Support for building Windows Images
for tripleo
Background
OpenStack Ironic Service provides support for image based deployments to baremetal servers. This blueprint proposes adding Windows Image generation capability to diskimage-builder.
Windows Disk Image Builder
A separate windows Disk image builder tool will be added to the Disk Image Builder proje...
|
|
|
Workload based windows images
for tripleo
Background
This blueprint proposes to extend the functionality of windows image builder [1] for Workload/Role based Windows Disk Image generation.
Windows Disk Image Builder
Once the basic tool [1] is in place, it will be extended to provide hooks where user can plugin custom scripts to automate tasks. Usin...
|
|
|
This blueprint sets out a common method using TripleO Image Elements to install and configure a simple monitoring solution for TripleO-deployed Openstack installations and is based on Icinga and Check_MK. The system should automatically configure itself from heat and nova and checks should be automatically added fr...
|
|
|
Re-assert System State
for tripleo
At present we do not have a way to re-assert system state in the manner of other configuration management tooling to ensure that changes made outside of HEAT/Tripleo Image Elements are reset to the appropriate value.
This blueprint aims to address this issue through the provision of a method for regularly re-assert...
|
|
|
Ocata Milestone 1A
for tripleo
This blueprint will be used to track user stories and defects for openstack mistral and TripleO-Common.
|
10 blueprint(s) listed.
