Hyrax Admin Interface: Difference between revisions
| Line 3: | Line 3: | ||
== Background == | == 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 a single console. Additionally, Hyrax will need a method for external services to read the catalog or add new data sets to a catalog. External services may be an organisation's digital library service for registering and maintaining access to data products. This page is the starting point for organizing the design work for the Hyrax Administrators Interface (HAI). | 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 a single console. | ||
Additionally, Hyrax will need a method for external services to read the catalog or add new data sets to a catalog. External services may be an organisation's digital library service for registering and maintaining access to data products. | |||
This page is the starting point for organizing the design work for the Hyrax Administrators Interface (HAI). | |||
== Definitions == | == Definitions == | ||
Revision as of 13:11, 9 June 2009
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 a single console.
Additionally, Hyrax will need a method for external services to read the catalog or add new data sets to a catalog. External services may be an organisation's digital library service for registering and maintaining access to data products.
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:
- Turn on/off OLFS debugging and view/save(/stream?) the output.
- Turn on/off BES debugging and view/save(/stream?) the output.
- Compare Server output with debugging associated with the request.
- View list of OLFS and BES's services
- Start/stop OLFS and BES's services
- Start/stop OLFS and BES logging
- View OLFS and BES logs.
- Set OLFS and BES logging output levels.
- OLFS and BES service status and heartbeat signal
- View OLFS and BES configuration settings
- Modify OLFS and BES service configuration settings and update
- Modify OLFS and BES data catalog configuration settings and update
- View data requests, job status, and statistics
- Manage user and service access rights, quotas, thresholds, and priorities
- Modify service notification features and thresholds.
Design
Required features
- Secure (SSL, grid certificates?) login and sessions.
- Data request and transaction log viewing.
- control and view debugging information.
- control and view service settings.
- control and view data catalog settings
- control and view service statistics information
- control and view service state information
Desired features
- control and view user access management
- control and view service notification features and thresholds
Deliverables
Period of use
The API features are to be permanent features in the Hyrax data service for use in building administrator and operator console applications to support an operational data service. The operational Hyrax data service is to support various service level access (SLA) requirements and provide timely, reliable data delivery with transaction logging.
