====== 4.0 DIDO Data Lifecycle Language (DDLL) ======
[[dido:public:s_cli:05_contents:01_prt:start| Return to Part I]]

The DIDO Lifecyle Language (DDLL) is responsible for controlling the Lifecycle of the DIDO instances distributed across the [[dido:public:ra:1.2_views:3_taxonomic:3_node_tax:start| Nodes]] in the [[dido:public:ra:1.2_views:2_tech_views:2-nodenet:2_net | DIDO Network]]. The DidoLL does not cover the [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle]] which is responsible for the system conception, design and development, production and/or construction, distribution, operation, maintenance and support, retirement, phase-out and disposal. Although there is some overlap, the System Lifecycle covers also covers the development of the [[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform|DIDO Platform]] while the DidoLL only covers the deployment and execution of the DIDO software on the individual nodes.

Although there is no [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] for a DIDO to be implemented as a [[dido:public:ra:1.4_req:1_func:platform:virtnodes | Virtual Node]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:v:vm]] or [[dido:public:ra:xapend:xapend.a_glossary:a:app_container]]), the basic steps would be the similar. MeGee ((
Jason McGee, 
IBM, 
__The 6 steps of the container lifecycle__, 
8 February 2016, Accessed: 29 March 2021,
[[https://www.ibm.com/blogs/cloud-computing/2016/02/08/the-6-steps-of-the-container-lifecycle/]]
)) has proposed the following steps for application containers (i.e., [[dido:public:ra:xapend:xapend.a_glossary:d:docker]]).

<figure containerLifecycle>
{{  dido:public:s_cli:05_contents:screen_shot_2021-03-30_at_7.23.00_pm.png?600  |}}
<caption>The 6 steps of a [[dido:public:ra:xapend:xapend.a_glossary:c:container|container's]] lifecycle.</caption>
</figure>

  - **Acquire** - Gathering the products (i.e, requirements, laying out a system plan, hardware, software or content)
  - **Build** - Assemble the acquired products in to system that can be deployed.
  - **Deliver** - The assembled system is delivered for [[dido:public:ra:xapend:xapend.a_glossary:v:validation|validation]] and verification 
  - **Deploy** - is the distribution of the approved system to the initial set of nodes nd the verification and validation that the system id properly deployed.
  - **Run** - The deployed system is started and the nodes are working as a system. The operating states (starting, running, shutdown, etc) are reported. 
  - **Maintain** - Anomalies and faults are detected, reported for further remediation. 

  * **Note:** Although the steps are presented as a linear progression from steps 1-6, the steps 3-6 (i.e., **Deploy**, **Run**, and **Maintain**) are repeated for every node within the DIDO network. If a flaw is repaired as a result of an anomaly or fault reported and a fix is identified, then the **Build** Step might need to be repeated. Sometimes, the flaw might require that the **Acquire** step be repeated.  

The DidoLL needs to support the entire Lifecycle of the DIDO on each individual Node.

<nspages dido:public:s_cli:05_contents:01_prt:04_dll -tree -r -exclude -subns -pagesInNs -h1 -textNs="DDLL Commands">

/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~