Difference between revisions of "TripleO/TuskarJunoPlanning"
< TripleO
m (→Overview) |
|||
| Line 14: | Line 14: | ||
* an explanation of the various OpenStack interactions needed | * an explanation of the various OpenStack interactions needed | ||
* a list of project requirements and/or blueprints needed to achieve those interactions | * a list of project requirements and/or blueprints needed to achieve those interactions | ||
| + | |||
| + | == Overcloud Stack Management == | ||
| + | |||
| + | == Cloud Service Representation == | ||
| + | |||
| + | == Advanced Cloud Deployment == | ||
| + | |||
| + | == Ironic == | ||
| + | |||
| + | == Metric Graphs == | ||
Revision as of 08:35, 23 March 2014
Contents
Overview
This planning document is born from discussions from the TripleO mid-cycle Icehouse meetup in Sunnyvale (TripleO/TuskarJunoInitialDiscussion). The ideas iterated there were then individually fleshed out and detailed, with much input coming from conversations with other OpenStack projects.
Our principal concerns duing the Juno cycle are:
- integrating further with other OpenStack services, using their capabilities to enhance our TripleO management experience
- ensuring that Tuskar does not try to implement functionality that is better located in other projects
This document details our high-level goals for Juno. It does so at multiple levels; for each we provide:
- a description of the goal
- an explanation of the various OpenStack interactions needed
- a list of project requirements and/or blueprints needed to achieve those interactions
