MID software released and deployed in the software "operations sandbox"

As part of SPO-1775 , 

At the end of PI15, users will be able to operate the SKA software from a dedicated Software Operations Sandbox that will be available in the HQ Operations Monitoring Centre room. 

This environment will have to give access to the relevant configuration information and allow navigation to the most relevant existing dashboards for the various subsystems.

The different products available in this initial configuration will be: 

• COMMON:
  • Landing Page (Is this Telescope Web UI 0.1 Home Screen?) that also contains
    • Links to Logging (Kibana - perhaps Dashboards specific to the deployed environment such as MID/LOW, PSI, sITF, STFC etc)
    • Links to Grafana Dashboards (also if possible specific dashboards for the deployed env such as MID/LOW, PSI, sITF, STFC etc)
  • Taranta Dashboards - high-level for each of the Products listed below
  • Taranta Auth - think about role-based AAA perhaps?
  • iTango Console access (an embedded shell in the Landing Page might be investigated)
  • BinderHub / JupyterHub deployment with simple example Notebooks as part of deployment
•  MID:
  • All products with functionality related to the first PSI System Integration Test as per end-of-PI14 requirements:
    • TMC
      • including real devices (`ska-tmc-mid` v0.5.1 or higher)
    • CSP LMC
    • CBF MCS
    • Dishmaster-Sim (`ska-sim-dishmaster`)
    • SDP
  • Optionally and if achievable, all products with functionality related to the first PSI System Integration Test as above and as per end-of-PI15 requirements:
    • DISH LMC
    • DS Controller Emulator
    • SPF Controller Emulator

Starting from the landing page the user has access to: 

• Configuration information of the software deployed. This will have to follow a representation that maps at high level to the SKA PBS at L2, possibly including lower level products where necessary. Ideally this will relate each element described to named Release of the software product.

• Aggregated health information for the various subsystems as described in the above configuration. Early full access of Product Health reporting (SW and HW, e.g. buffer overflows, temperatures, failures, etc.) as central AIV view of the SUT and its active components. No alarms required.
  • A hierarchy for reporting availability is agreed
  • One or more policies for aggregation of aggregated status (on the adminMode, healthState, obsState triplet) are agreed, and can be used for reporting against the hierarchy above.
• Subsystem dashboards and control pages. These shall include or link relevant information about how to operate and use the interfaces and what functionalities are available.