You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Scope

  • JOC is turning towards its end of life and shall be replaced by a new component.
  • The scope of the new JOC Cockpit is currently in discussion.

Cockpit

Functional Requirements

  • Basically the existing functionality shall be provided.
  • Improved navigation should be provided.
  • More details, e.g. for history.
  • Suppot for multiple JobScheduler instances
    • Cluster Instances
    • Supervisor and Workload Instances
    • Master and Slave Instances
  • Authentication via Apache Shiro
  • Authorisation via Apache Shiro
    • Management of permissions, e.g. for folders and GUI operations.
    • Grouping of permissions to roles.
    • Associating roles to users.
  • Workload visualisation
  • Calendar preview

Non-Functional Requirements

  • Improved graphical presentation.
  • Better responsiveness of the GUI.
  • Responsive Design for use with devices as e.g. tables
  • Reduced impact of JOC operations on the JobScheduler main process.

Architecture

  • JOC will be completely re-written.
  • A new framework will be introduced that currently is being decided on. 
  • Introduction of an interface between JOC and JobScheduler
    • Presumably the Jetty container will operate that interface.

 

 

  • No labels