This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:s_cli:05_contents:01_prt:04_dll:start [2021/08/18 11:03] murphy |
dido:public:s_cli:05_contents:01_prt:04_dll:start [2021/10/06 14:02] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:s_cli:05_contents:01_prt:start| Return to Part I]] | [[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 | 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. | + | 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 (( | 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 (( | ||