Hyrax Admin Interface

This is a place to start discussing peoples desires/needs for a Hyrax Administrators Interface (HAI).

Background

Members of the Hyrax users community are developing robust, highly available data services in operational settings, and have asked for an administrators interface that will allow them to monitor, control, reconfigure, and debug the Hyrax frontend and backend servers from an operator's console. This page is the starting point for organizing the design work for the Hyrax Administrators Interface (HAI).

Definitions

Administrator

The administrator is the human that operates the HAI.

User

The user is a human that uses client software such as Kepler, Matlab OPeNDAP Ocean Toolbox, a web browser, and others to make requests (HTTP, SOAP, etc.) of the Hyrax server.

Operator Console

The 24x7 operators console to monitor and control the data services as well as the user data requests.

Administrator Console

The system administrators console to monitor, control, reconfigure, and debug the Hyrax frontend and backend servers.

Use Cases

The administrator uses the HAI to:

1. Turn on/off OLFS debugging and view/save(/stream?) the output.
2. Turn on/off BES debugging and view/save(/stream?) the output.
3. Compare Server output with debugging associated with the request.
4. View logs.
5. View list of BES's
6. Start/stop BES's
7. Start/stop BES logging
8. View BES logs.
9. Set BES logging output levels.

Design

Required features

1. Secure (SSL?) login and sessions.
2. Log viewing.
3. control and view debugging information.
4. User access management? What does that look like?