Difference between revisions of "TripleO/TuskarJunoInitialDiscussion"
< TripleO
(Created page with "== Overview == == Re-Architecture == == Feature Improvement ==") |
|||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
+ | |||
+ | This information is based on discussions from the TripleO mid-cycle Icehouse meetup in San Francisco. | ||
+ | |||
+ | One concept independently stressed by many people is: Tuskar should take advantage of existing OpenStack services. Although we have made strides in following this philosophy in the Icehouse development cycle, several discussions described how we might go further down this path. If we were to follow those suggestions, consequences would be felt both in current architecture and future feature planning. | ||
== Re-Architecture == | == Re-Architecture == | ||
+ | |||
+ | * Template Storage | ||
+ | |||
+ | * Tuskar's Place * | ||
+ | |||
+ | Jay's Picture | ||
== Feature Improvement == | == Feature Improvement == | ||
+ | |||
+ | * Service | ||
+ | |||
+ | * Role | ||
+ | |||
+ | Develop what we can based on what exists; don't over-design within Tuskar. | ||
+ | |||
+ | == User Workflow == |
Revision as of 18:36, 6 March 2014
Overview
This information is based on discussions from the TripleO mid-cycle Icehouse meetup in San Francisco.
One concept independently stressed by many people is: Tuskar should take advantage of existing OpenStack services. Although we have made strides in following this philosophy in the Icehouse development cycle, several discussions described how we might go further down this path. If we were to follow those suggestions, consequences would be felt both in current architecture and future feature planning.
Re-Architecture
- Template Storage
- Tuskar's Place *
Jay's Picture
Feature Improvement
- Service
- Role
Develop what we can based on what exists; don't over-design within Tuskar.