Difference between revisions of "TripleO/TripleOCloud"
| Line 1: | Line 1: | ||
| − | TripleO developers run a production-ready cloud as part of ensuring they are delivering something usable. | + | TripleO developers run a production-ready cloud as part of ensuring they are delivering something usable. We treat this as a production CD environment: Kanban for the folk working on it is at https://trello.com/b/0jIoMrdo/tripleo and https://trello.com/tripleo. We iterate and evolve in response to OpenStack as a whole, while improving the deployment mechanisms and code. |
= Seed = | = Seed = | ||
Revision as of 00:50, 27 September 2013
TripleO developers run a production-ready cloud as part of ensuring they are delivering something usable. We treat this as a production CD environment: Kanban for the folk working on it is at https://trello.com/b/0jIoMrdo/tripleo and https://trello.com/tripleo. We iterate and evolve in response to OpenStack as a whole, while improving the deployment mechanisms and code.
Contents
Seed
The seed is a manually installed machine, reachable over ssh. Until we've done an audit, access to the machine is restricted to HP employees who are TripleO ATC's.
Undercloud
The API endpoint for the undercloud that deploys the cloud is: <coming soon>.
Access
API access to the Undercloud is available to TripleO ATC's, with the intent of facilitating debugging/correction of overcloud deployments. Contact the TripleO PTL to request credentials.
Overcloud
The overcloud is deployed per commit, and access is currently restricted to TripleO ATC's. They may use the cloud as desired - having users on the cloud helps validate that the cloud is usable! File all bugs on the tripleo bug tracker.
