Skip to end of metadata
Go to start of metadata

Overview of "Deploy Distributed Processes" Use Case

Define service and process instantiation location and scheduling

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Integrated Observatory Operator
Is Used By UC.R2.52 Manage ION Processes-Deprecated
Is Extended By  
In Acceptance Scenarios AS.R2.01C Operate Integrated Observatory Network
Technical Notes  
Lead Team CEI
Primary Service Process Management Services
Version 1.7
UC Priority 4
UC Status Mapped + Ready
UX Exposure ONC


This information summarizes the Use Case functionality.

The Integrated Observatory Operator defines which services and which processes are instantiated at which execution sites. This determination can be made at the time of each process or service launch, not at integration time. The Integrated Observatory Operator observes the processes running at each site.


  • A set of execution sites has been defined in the system and compatible Execution Engines are defined and activated at the site.
  • The processes to be deployed have been fully tested, validated, and configured for execution on a CC/EE.
  • The Integrated Observatory Operator makes, or can make, a final determination about the appropriate deployment of the processes.

Initial State

An Integrated Observatory Operator is logged in to the system.

Scenario for "Deploy Distributed Processes" Use Case

  1. <3> The Integrated Observatory Operator views the process environments on the system.
    1. The views are likely to need overview representations for each site, as well as representations drilling to finer detail (availability zones (AZ), execution engines (EE), capability containers (CC)), to look at the status and allocation of capability containers and their processes in each context.
    2. This may be supported by software external to the Integrated Observatory.
  2. A process or service is specified and made available for deployment.
    1. Typically, the purpose for the processes (data acquisition, data distribution, command and control) will determine the type of execution environment they are allocated to.
    2. Lacking any specific need to do otherwise, the system could automatically allocate the processes to a site/AZ/EE/CC (eventually, by policy, but manually at first).
    3. Under certain circumstances, human review of the process allocation to an execution environment, and possibly intervention, is appropriate.*
  3. <3> The Integrated Observatory Operator may specify desired allocation for the new process or service.
    1. By selecting a specific site, availability zone, or execution engine.
  4. <3> After final review of the intended deployment by the Integrated Observatory Operator, the processes are deployed as specified.

Final State

Processes have been deployed according to the request.


These comments provide additional context (usually quite technical) for editors of the use case.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
openissue openissue Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.