This is a preliminary set of use cases for the NDS Labs systems.
What is NDS Labs?
NDS Labs is an experimental development platform for hosting NDS pilot projects that emerged out of the NDS2 and NDS3 consortium workshops. NDS Labs is intended to provide consortium developers access to significant storage, virtual machines for hosting, and a variety of existing, commonly used data tools (e.g., databases, iRODS, Globus services, etc). NDS Labs enables developers to try out new ideas for tools, services, and standards. Developers working in labs have the ability to create a virtual cluster of machines and launch applications within each node. Developers are encouraged to package new applications and, if appropriate, share them with other projects within Labs. NDS Labs should provide high-level architecture documentation, summaries of key technologies used, and examples of use. NDS Labs should support different scenarios based around the different types of projects we expect to support.
Users/Actors:
- Site administrator: Infrastructure and cluster administration at NCSA, TACC, SDSC.
- NDS cluster administrator: Internal administrator that provisions approved projects and assigns quotas
- NDS project admin: External user of NDS Labs services. Access the GUI/CLI to manage services within a project.
- End user: External user of services deployed via NDS Labs (e.g., Dataverse, Clowder)
- NDS developers: Local development staff and community members
...
- NDS cluster administrator manages services library (TBD). Tentatively, admin must be able to add, modify, and remove NDS Labs services available to project administrators.
- NDS cluster administrator provisions NDS Labs projects (TBD). Tentatively, approved project users will be allocated a Kubernetes namespace, assigned credentials and storage/compute quotas. They will be given an endpoint URL for GUI/CLI access (see below).
Project admin
Prerequisites:
...