Difference between revisions of "Meetings/TechnicalCommittee/Horizon Gap Coverage"
David Lyle (talk | contribs) (Created page with "=== Gap 0: Mission Statement === Horizon has documented the project's core values here http://docs.openstack.org/developer/horizon/intro.html#id1. Our mission statement shoul...") |
David Lyle (talk | contribs) |
||
| Line 5: | Line 5: | ||
To provide an extensible unified web based user interface for all integrated OpenStack services. | To provide an extensible unified web based user interface for all integrated OpenStack services. | ||
| − | timeframe: Juno-1 | + | * timeframe: Juno-1 |
| − | owner: david-lyle | + | * owner: david-lyle |
=== Gap 1: No major Architectural Changes === | === Gap 1: No major Architectural Changes === | ||
| Line 12: | Line 12: | ||
Planned since the Icehouse Summit, Horizon is planning on splitting the current repository into a toolkit repo and a django app repository. The current repository is already split along these lines, but having them combined creates problems for projects in incubation and requires special casing by infra. The only code not already split is JavaScript and CSS that straddles both sides, this has been the main impediment for finishing the split. | Planned since the Icehouse Summit, Horizon is planning on splitting the current repository into a toolkit repo and a django app repository. The current repository is already split along these lines, but having them combined creates problems for projects in incubation and requires special casing by infra. The only code not already split is JavaScript and CSS that straddles both sides, this has been the main impediment for finishing the split. | ||
| − | timeframe: Juno-2 | + | * timeframe: Juno-2 |
| − | owner: mrunge | + | * owner: mrunge |
=== Gap 2: Refresh of horizon-coresec === | === Gap 2: Refresh of horizon-coresec === | ||
| − | timeframe: Juno-1 (complete) | + | * timeframe: Juno-1 (complete) |
| − | owner: david-lyle | + | * owner: david-lyle |
=== Gap 3: Exhaustive list of API calls not supported === | === Gap 3: Exhaustive list of API calls not supported === | ||
| Line 24: | Line 24: | ||
There is ongoing work to expose support for as much of the service APIs that make sense in Horizon. An exhaustive list is difficult and harder to maintain across all services as they progress. Better coordination with other PTLs/Projects will help insure that key new functionality is covered. The other limiting factor is people to address these gaps. | There is ongoing work to expose support for as much of the service APIs that make sense in Horizon. An exhaustive list is difficult and harder to maintain across all services as they progress. Better coordination with other PTLs/Projects will help insure that key new functionality is covered. The other limiting factor is people to address these gaps. | ||
| − | timeframe: ongoing | + | * timeframe: ongoing |
| − | owner: david-lyle | + | * owner: david-lyle |
=== Gap 4: Integration Framework Tied to Gate === | === Gap 4: Integration Framework Tied to Gate === | ||
| Line 31: | Line 31: | ||
In late Icehouse, Horizon added an integration test framework. There is a very limited number of tests currently implemented for this framework. The goal is to continue to grow the number and extent of the tests in Juno and hopefully tie this framework into the gating of Horizon at least and potentially cross-project gating as makes sense. Horizon will need to coordinate with infra and QA to understand what adds the most value. | In late Icehouse, Horizon added an integration test framework. There is a very limited number of tests currently implemented for this framework. The goal is to continue to grow the number and extent of the tests in Juno and hopefully tie this framework into the gating of Horizon at least and potentially cross-project gating as makes sense. Horizon will need to coordinate with infra and QA to understand what adds the most value. | ||
| − | timeframe: Juno-3 | + | * timeframe: Juno-3 |
| − | owner: jpich | + | * owner: jpich |
Revision as of 19:03, 27 May 2014
Contents
Gap 0: Mission Statement
Horizon has documented the project's core values here http://docs.openstack.org/developer/horizon/intro.html#id1. Our mission statement should highlight Core Support, Extensibility, and Consistency.
Proposal: To provide an extensible unified web based user interface for all integrated OpenStack services.
- timeframe: Juno-1
- owner: david-lyle
Gap 1: No major Architectural Changes
Planned since the Icehouse Summit, Horizon is planning on splitting the current repository into a toolkit repo and a django app repository. The current repository is already split along these lines, but having them combined creates problems for projects in incubation and requires special casing by infra. The only code not already split is JavaScript and CSS that straddles both sides, this has been the main impediment for finishing the split.
- timeframe: Juno-2
- owner: mrunge
Gap 2: Refresh of horizon-coresec
- timeframe: Juno-1 (complete)
- owner: david-lyle
Gap 3: Exhaustive list of API calls not supported
There is ongoing work to expose support for as much of the service APIs that make sense in Horizon. An exhaustive list is difficult and harder to maintain across all services as they progress. Better coordination with other PTLs/Projects will help insure that key new functionality is covered. The other limiting factor is people to address these gaps.
- timeframe: ongoing
- owner: david-lyle
Gap 4: Integration Framework Tied to Gate
In late Icehouse, Horizon added an integration test framework. There is a very limited number of tests currently implemented for this framework. The goal is to continue to grow the number and extent of the tests in Juno and hopefully tie this framework into the gating of Horizon at least and potentially cross-project gating as makes sense. Horizon will need to coordinate with infra and QA to understand what adds the most value.
- timeframe: Juno-3
- owner: jpich
