...
- JOC is turning towards its end of life and shall will be replaced by a new component.
- The scope of requirements management for the new JOC Cockpit is currently in discussionhas started.
Cockpit
Functional Requirements
- Basically the existing functionality shall be provided to monitor and control jobs, job chains etc. and to access logs.
- Visualisation of more details, e.g. for history.
- Support for multiple any number JobScheduler instances
- Active and Passive Cluster Instances
- Supervisor and Workload Instances
- Master and Slave InstancesAgent Instances
- Of specific concern will be the management of lager numbers of Agents
- Authentication and Authorization via Apache Shiro
- Integration with Directory Services
- Management of permissions, e.g. for folders and GUI operations.
- Grouping of permissions to roles .Associating and associating roles to users.
- Workload visualisation
- Calendar preview
...
- Improved navigation.
- Improved graphical presentation.
- Better responsiveness of the GUI. The GUI will receive events from JobScheduler instances.
- Responsive Design for use with mobile devices as e.g. tablestablets.
Architecture
- JOC will be completely re-written.
- A new framework will be is introduced that currently is being decided onwill replace the existing XML Interface.
- Introduction Implementation of an a web service interface between JOC and JobSchedulerPresumably the Jetty Web Server will operate that interface.
Milestones
- July 2015: requirements collection
- August 2015: web service interface
- November 2015: Release Candidate targeted for release 1.11