Skip to end of metadata
Go to start of metadata

Overview of "Deploy CI Software on CG Platform" Use Case

Deploy CI software on the CG remote platform environment before platform's final tests and deployment.


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

Metadata

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

Actors CG Application Developer, CG Marine Integrator, CI Application Developer, CI Marine Integrator
References UC.R2.09 Activate Instrument Driver
UC.R2.05 Register and Connect Instrument
UC.R2.15 Qualify Instrument Interface
Uses  
Is Used By  
Extends  
Is Extended By  
In Acceptance Scenarios None
Technical Notes The term 'remote platform' refers to systems not within the Integrated Observatory terrestrial network (hence, targets CG Surface Mooring platforms in R2).
This use case is not mapped to requirements, as it addresses development activities rather than operational system capabilities.
Lead Team MI
Primary Service Marine Observatory Facility Services
Version 2.5
UC Priority 4
UC Status Mapped + Ready
UX Exposure SYS

Summary

Deploy capability containers with instrument and platform agents, select CI services and data stream processes on CG remote platform. CI software deployment includes configuration for deployment, software and hardware integration, and subsequent testing on the platform.

Assumptions

  • A 'CG remote platform' during the R2 time frame is the CG Surface Mooring DCL platform.
  • One CG surface mooring (platform) has multiple DCL computational elements, locally connected via Ethernet (not always on) and always-on serial connection for time.
  • Activities occur during integration time, while the platform is on the shore.
  • Deploying CI software while the CG platform is deployed is not planned in R2.
  • The CG platform controller ICD exists.
  • The Capability Container for embedded platform exists (different from standard COI capability container but with similar capability for messaging).
  • Instrument and Platform Agents for embedded platform exist.
  • Services for embedded platform exist.

Initial State

All services, agents, and container software for the embedded platform exists (see Assumptions), and the platform hardware with computational components is ready for integration.

Scenario for "Deploy CI Software on CG Platform" Use Case

Note that these are not functional capabilities of the operating software. Therefore, the steps identify necessary activities, but not testable functionality.

  1. CG Application Developer configures embedded execution environment
    1. As needed for a specific remote platform deployment
    2. Specific platform environment can be one or multiple computational elements (e.g. one or more DCL modules on one CG surface mooring platform)
    3. Configure the operating system (as permissible by platform controller ICD)
    4. Configure the available disks and storage; create directory structure
    5. Includes installing or describing the installation of additional software packages needed (e.g. libraries needed by CI)
  2. CI Application Developer configures embedded integration environment
    1. Includes installing and configuring packages
    2. Install and configure messaging solution
    3. Install and configure storage solution
    4. Install and configure communication solution
  3. CI Application Developer configures embedded capability container to host CI software components
    1. As needed for a specific remote platform deployment
    2. CI software components include instrument agents, platform agents and services
    3. Can be one or multiple capability containers
  4. CI Application Developer adds startup and shutdown hooks
    1. Startup all CI software on one computational element from one entry point (e.g. hook in OS boot sequence)
    2. Shutdown all CI software on one computational element with one command
  5. Application Developers and Integrators perform local integration tests
    1. Using a platform test bed or a compatible hardware/software environment
    2. Using the Instrument development kit as applicable
  6. Application Developers and Marine Integrators participate in cross-IO integration activities, acceptance and commissioning
    1. Offline integration
    2. On-system test (pre burn-in)

Final State

Remote platform ready for burn-in test and physical deployment and connection to CI system

Comments

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

The CG platform for which the software is being developed will have the following characteristics when deployed:

  • CG platform intermittently connected to shore via broadband satellite
  • Satellite connection to shore at a schedule set by CGSN
  • Some DCL based platforms are connected via the RSN cable, providing always on communications and virtually unlimited power

It is likely to be possible to deploy updated CI software on a CG platform after the CG platform is deployed, but the manner in which this will be done is not defined.

(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

Labels

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.