[jboss-dev-forums] [JBoss AS7 Development] - ManagementConsoleRoadmap

[Heiko Braun]

Heiko Braun [http://community.jboss.org/people/heiko.braun%40jboss.com] modified the document:

"ManagementConsoleRoadmap"

To view the document, visit: http://community.jboss.org/docs/DOC-16376

--------------------------------------------------------------
h1. Roadmap for the AS7 Management Console



|| Key
 || *Description* || *Goals
* || *Dependencies* || *Risks* ||
| M1 | Project setup (codebase, repo, JIRA, etc) | 
 | 
 | 
 |
| M2 | 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 |
| M3 | Authentication | 
 | 
 | 
 |
| M4 |  Server Group configuration
     - domain sceanrio only   
     - potential release candidate | configure, launch, shutdown server instances | management infrastructure in place and console being deployable | 
 |
| M5 | 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 | 
 | 
 |
| M6 | 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 | 
 |
| M7 |  Example Metrics completed
     - covers a typical metric request (domain, host, subsystem)
     - re-use example subsystem | verify management API exposes runtime state correctly/sufficiently | 
 | 
 |
| M8 | Client Server API mature (pivot)
     - Match AS7 management API | 
 | 
 | 
 |
| M9 |  Deployment on Domain Controller
     - Integrated with AS build/deliverables | 
 | 
 | 
 |
| M10 | Deployment on Standalone Server
   - Integrated with AS build/deliverables | 
 | 
 | 
 |
| M11 | 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 | 
 | 
 |
| M12 | 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 |
| M13 | Management Operation Plans | 
 | 
 | 
 |
| M14 | Deployment Plans | 
 | 
 | 
 |
| M16 |  User management | 
 | 
 | 
 |
| 
 | 
 | 
 | 
 | 
 |
| 
 | 
 | 
 | 
 | 
 |
| 
 | 
 | 
 | 
 | 
 |
| 
 | 
 | 
 | 
 | 
 |
| 
 | 
 | 
 | 
 | 
 |



h4. Rough categorization of building blocks:

- Project setup (codebase, repo, JIRA, etc)

- UI Framework (both domain and standalone)
     - rough UI layout 
     - maybe outer most domain tree (domain, profiles, server-groups, etc)
     - excluding subsystems and management operations
     - goal: explore outermost conceptual model
     - risk: might not reflect ambiguity in information design w/o example subsystem
     - depends: project setup

- Authentication

- Server Group configuration
     - goal: configure, launch, shutdown server instances
     - domain sceanrio only    
     - depends: management infrastructure in place and console being deployable
     - potential release candidate

- Provide UI extension hooks
     - minimal API: i.e. GWT 2.1 PlaceManager, plus boiler plate magic (borrowed from Errai Workspaces)
     - goal: baseline for subsystem integration, extensibility  
     - Feedback from layered products (JON, Drools)

- Example subsystem management completed 
     - complete functional set
     - distinction between domain and host level operations
     - goal: explore detailed conceptual model, verify management API, remove ambiguity
     - depends: rough UI framework, extension hooks
     - potential release candiate

- Example Metrics completed
     - covers a typical metric request (domain, host, subsystem)
     - re-use example subsystem
     - goal: verify management API exposes runtime state correctly/sufficiently

- Client Server API mature (pivot)
     - Match AS7 management API

- Deployment on Domain Controller
     - Integrated with AS build/deliverables

- Deployment on Standalone Server
   - Integrated with AS build/deliverables

- Integrate themes (.org & RH):
     - early in the game
     - provide means for design people to work on this
     - goal: introduce customization hooks, verify i18n issues, work towards JON

- Iterate over remaining subsystems
     - goal: complete management functionality
     - risk: might reveal issues with the overall conceptual model
     - depends: example subsystem, rough UI framework
     - with each subsystem another potential release candiate

- Management Operation Plans

- Deployment Plans

- User management
--------------------------------------------------------------

Comment by going to Community
[http://community.jboss.org/docs/DOC-16376]

Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2225]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20110125/aed130a0/attachment.html