• Created by Unknown User (mfreemon), last modified on Jun 20, 2015

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Block Diagram

Version 3 (6/16/2015).  Click to enlarge.

Design/Implementation

Code

  • Use the OpenStack nova API to perform the calls to the OpenStack management functions.

Repositories

  • What should be repository name be for the NDS Web Services web application?
  • Should the NDS Explorer and NDS Web Services repositories be combined into one?

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).
  •  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:

 

  • No labels