Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:e:edge_deployment [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:e:edge_deployment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Edge Deployment ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Edge Deployment is an [[public: | ||
| + | |||
| + | Deployment subjects may include: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Configuration | ||
| + | * Security controls | ||
| + | * Monitoring capabilities | ||
| + | * Operational data | ||
| + | |||
| + | An Edge Deployment may need to account for: | ||
| + | |||
| + | * Limited network bandwidth | ||
| + | * Intermittent connectivity | ||
| + | * Restricted external connectivity | ||
| + | * Limited computing capacity | ||
| + | * Limited storage capacity | ||
| + | * Local security controls | ||
| + | * Physical access constraints | ||
| + | * Local operational authority | ||
| + | * Dependency availability | ||
| + | * Local update and rollback procedures | ||
| + | |||
| + | An Edge Deployment differs from a cloud deployment: | ||
| + | |||
| + | * An Edge Deployment targets an Edge Environment | ||
| + | * A cloud deployment targets an Infrastructure Environment supplied through cloud capabilities | ||
| + | |||
| + | An Edge Deployment may also form part of a Hybrid-Cloud Deployment when related deployment subjects operate across cloud and Edge Environments. | ||
| + | |||
| + | An Edge Deployment does not necessarily imply disconnected or air-gapped operation. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The applicable deployment specification should identify: | ||
| + | |||
| + | * The target Edge Environment | ||
| + | * The deployment subjects | ||
| + | * The applicable environment constraints | ||
| + | * Required dependencies | ||
| + | * Required configuration | ||
| + | * Applicable [[public: | ||
| + | * Required deployment validation | ||
| + | * Required rollback behavior | ||
| + | |||
| + | The term does not prescribe a device class, edge platform, orchestration technology, provider, network architecture, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | Crucible performs an Edge Deployment by deploying a Containerized Workload, its configuration, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||