| Task | Description | Goals
| Dependencies | Risks |
|---|
| Project setup (codebase, repo, JIRA, etc) |
|
|
|
M0: Project Setup done. 5.Feb
|
| UI Framework (both domain and standalone) - rough UI layout - maybe outer most domain tree (domain, profiles, server-groups, etc) - excluding subsystems and management operations | Explore outermost conceptual model |
| Might not reflect ambiguity in information design w/o example subsystem |
| Installation on Standalone Server - Integrated with AS build/deliverables |
|
|
|
M1: Core UI. Supports standalone scenario. Part of AS7 build/deliverable. 28.Feb
|
| Installation on Domain Controller - Integrated with AS build/deliverables |
|
|
|
| Server Group configuration - domain sceanario only - potential release candidate | Configure, launch, shutdown server instances | Management infrastructure in place and ability to install console |
|
M2: Core UI, supports domain scenario. Part of AS7 build/deliverable. 15. Mar
|
| Example subsystem management completed - complete functional set - distinction between domain and host level operations - potential release candiate | Explore detailed conceptual model, verify management API, remove ambiguity | Rough UI framework, extension hooks |
|
| Application Deployment | Deploy applications through the console | AS7 deployment API |
|
| Client Server API mature (pivot) - Match AS7 management API |
|
|
|
M3: Example subsystem management and metrics included. Supports application deployment. 30.Apr
|
| Authentication |
| Security components in place |
|
| Iterate over remaining subsystems - with each subsystem another potential release candiate | Complete management functionality | Example subsystem, rough UI framework | Might reveal issues with the overall conceptual model |
M4: Core Management Functionality available 30.May
|
| Integrate themes (.org & RH): - early in the game - provide means for design people to work on this | Introduce customization hooks, verify i18n issues, work towards JON |
|
|
| Example Metrics completed - covers a typical metric request (domain, host, subsystem) - re-use example subsystem | Verify management API exposes runtime state correctly/sufficiently | Example subsystem |
|
GA: Reasonable 1.0 Feature Set
15.Jun |
|
Beyond 1.0.0.GA
|
| Management Operation Plans | Enable composite (bulk) management operations on the whole domain. Verify error handling, consistency |
|
|
| Deployment Plans | Rollout applications to a domain. Verify error handling, consistency |
|
|
| User management | Create/Remove users that have access to the management infrastructure |
|
|
| Provide UI extension hooks - minimal API: i.e. GWT 2.1 PlaceManager, plus boiler plate magic (borrowed from Errai Workspaces) - Feedback from layered products (JON, Drools) | Baseline for subsystem integration, extensibility | Decision on UI Framework & Widgets Libraries |
|
| i18n | Full i18n support |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|