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

Compare with Current View Page History

Version 1 Next »

Security

  • Credentials

Versioning

  • How can we support deploying multiple versions of the same service?

Project Admin GUI

 Prerequisite:

  • Project has been approved, namespace username/password available
  • A service can only be deployed once in a given a project? (or stack) but may be restarted/reconfigured.

  1. The project admin can login to the GUI:
    1. Session and token?
    2. "Keep me logged in to this computer"
  2. The project admin can logout of the GUI
  3. View a list of available services
  4. Search the list of available services by name? or by tags? related components?
  5. Add = Configure  a service the first time – launches a configuration wizard
    1. Display description/introduction information
    2. List required and optional dependencies
    3. Select or deselected optional dependencies (required are checked by default)
    4. Display volume requirements: If a service requires a volume: (1 volume per service)
      1. Display the limits to the project
      2. Minimum recommended for each service (default)
      3. Reuse existing volumes, re-initialize
    5. Confirmation
      1. Display dependencies of dependencies 
      2. final summary of what's will be deployed
      3. Notion of stacks? 
    6. Finish: 
      1. Selected services are added to the "inactive" part of namespace (not started status)
      2. "Configured Services" panel displays:
        1. "Configured services" grouped by "stack" name
        2. Project admin can play/stop/remove "stack"
        3. Project admin can add optional services to existing stack. (Add service to stack – "wrench" icon)
  6. "Save" saves your configuration? Do we need it?
  7. Deploy starts a stack
  8. Status:
    1. Polling/watching individual service statuses
  9. Endpoints
  10. Logs
  • No labels