portal UI - experiment states and transitions buttons

[mjstealey]

Experiment states and transitions buttons

Define the buttons and logic that are displayed to an experimenter at each state as defined below

• Add Refresh button to experiment detail page (eliminates need for polling)

• define dict of buttons to toggle experiment button choices on UI

  "dashboard_buttons": {
      "b_dev_init": true,
      "b_dev_save": false,
      "b_dev_save_exit": false,
      "b_sandox_submit": false,
      "b_sandbox_cancel": false,
      "b_sandbox_save": false,
      "b_sandbox_save_exit": false,
      "b_emu_submit": false,
      "b_emu_cancel": false,
      "b_testbed_submit": false,
      "b_testbed_cancel": false
  }

Possible states - button(s)

• ACTIVE_DEVELOPMENT - Save, Save & Exit
• ACTIVE_EMULATION - n/a
• ACTIVE_SANDBOX - Save, Save & Exit
• ACTIVE_TESTBED - n/a
• SAVED - Initiate Development, Submit to Sandbox, Submit to Emulation, Submit to Testbed
• WAIT_DEVELOPMENT_DEPLOY - n/a
• WAIT_EMULATION_DEPLOY - Cancel
• WAIT_EMULATION_SCHEDULE - Cancel
• WAIT_SANDBOX_DEPLOY - Cancel
• WAIT_TESTBED_DEPLOY - Cancel
• WAIT_TESTBED_SCHEDULE - Cancel

Possible state transitions

ACTIVE_DEVELOPMENT

• ACTIVE_DEVELOPMENT --> SAVED - save development session - Flags 000 (e.g. experimenter logged out of all VMs for one hour)
  • Button: Save & Exit
• ACTIVE_DEVELOPMENT --> ACTIVE_DEVELOPMENT - save development session but do not exit
  • Button: Save

ACTIVE_EMULATION

• ACTIVE_EMULATION --> SAVED - emulation complete - Flags 100 or 101
  • Button: n/a

ACTIVE_SANDBOX

• ACTIVE_SANDBOX --> SAVED - save sandbox session - Flags 000 (e.g. end of scheduled sandbox session)
  • Button: Save & Exit
• ACTIVE_SANDBOX --> ACTIVE_SANDBOX - save sandbox session but do not exit
  • Button: Save

ACTIVE_TESTBED

• ACTIVE_TESTBED --> SAVED - execution complete - Flags 010
  • Button: n/a

SAVED

• SAVED --> WAIT_DEVELOPMENT_DEPLOY - start development session
  • Button: Initiate Development
• SAVED --> WAIT_SANDBOX_DEPLOY - schedule sandbox session
  • Button: Submit to Sandbox
• SAVED --> WAIT_EMULATION_SCHEDULE - reqeust emulation session
  • Button: Submit to Emulation
• SAVED --> WAIT_TESTBED_SCHEDULE - request testbed session (allowed if (E&&P)|T
  • Button: Submit to Testbed

WAIT_DEVELOPMENT_DEPLOY

• WAIT_DEVELOPMENT_DEPLOY --> ACTIVE_DEVELOPMENT - deployment on development VMs complete
  • Button: n/a
• WAIT_DEVELOPMENT_DEPLOY --> SAVED - failure to deploy
  • Button: n/a

WAIT_EMULATION_DEPLOY

• WAIT_EMULATION_DEPLOY --> ACTIVE_EMULATION - scheduled deployment of emulation complete
  • Button: n/a
• WAIT_EMULATION_DEPLOY --> SAVED - cancel
  • Button: Cancel

WAIT_EMULATION_SCHEDULE

• WAIT_EMULATION_SCHEDULE --> WAIT_EMULATION_DEPLOY - schedule
  • Button: n/a
• WAIT_EMULATION_SCHEDULE --> SAVED - cancel pending emulation session
  • Button: Cancel

WAIT_SANDBOX_DEPLOY

• WAIT_SANDBOX_DEPLOY --> ACTIVE_SANDBOX - scheduled deployment on sandbox complete
  • Button: n/a
• WAIT_SANDBOX_DEPLOY --> SAVED - cancel pending sandbox session
  • Button: Cancel

WAIT_TESTBED_DEPLOY

• WAIT_TESTBED_DEPLOY --> ACTIVE_TESTBED - scheduled deployment of testbed complete
  • Button: n/a
• WAIT_TESTBED_DEPLOY --> SAVED - cancel
  • Button: Cancel

WAIT_TESTBED_SCHEDULE

• WAIT_TESTBED_SCHEDULE --> WAIT_TESTBED_DEPLOY - schedule
  • Button: n/a
• WAIT_TESTBED_SCHEDULE --> SAVED - cancel pending testbed session
  • Button: Cancel

[mjstealey]