Block Diagram
Version 3 (6/16/2015). Click to enlarge.
Design/Implementation
NDS Explorer Code
- angular.js
NDS Web Services Code
- Use the OpenStack nova API to perform the calls to the OpenStack management functions.
- Python only?
- What do the REST calls actually look like?
- What framework/libraries, if any, should be used to make the REST implementation easier?
Repositories
- The repository name for the NDS Web Services web app will be nds-web-services
- The repository name for the NDS Explorer user interface web app will be nds-explorer (no change)
- These two repositories will remain separate repositories
Authentication/Authorization
- For the initial version, we will use a service account for OpenStack. Users credentials will not be OpenStack credentials.
- The OpenStack credentials are used by the REST API logic and are not provided by (nor known to) the user. This will need to be specified in such a way that it will not be accidentally committed to the repository.
Application State
- How to tell what Environments exist?
- If they were created by NDS Web Services (and have not been deleted), then they exist. Ignore any NDS Environments that have been created manually (not using NDS Web Services).
- If they were created by NDS Web Services (and have not been deleted), then they exist. Ignore any NDS Environments that have been created manually (not using NDS Web Services).
- How to store info about the existing Environments?
- How to store the Service definitions?
- Use the easiest and most straightforward solution for the first prototype.
Prior Versions of the Block Diagram
From 6/12/2015 meeting:
From 6/10/2015 meeting: