Drift
Desired State Versus Observed State.
Drift is the difference between what a Deployment Manifest asked for and what observation found on the deployed surface instance.
ARCHITECTURE / DEPLOYMENT PREVIEW
| Object | Desired | Observed | Result |
|---|---|---|---|
| Template Drift | TPL-CITY v8 | TPL-CITY v7 | DRIFT DETECTED |
| Configuration Drift | CFG-CITY-MN v12 | CFG-CITY-MN v11 | DRIFT DETECTED |
| Record Drift | BR-88213 present | BR-88213 missing | DRIFT DETECTED |
| Surface Drift | SMF-CITY-0042 | SMF-CITY-0039 | DRIFT DETECTED |
| Schema Drift | SCHEMA v5 | SCHEMA v4 | DRIFT DETECTED |
| Namespace Drift | NS-GEO-US-MN-DULUTH | unresolved | DRIFT DETECTED |
| Graph Drift | Surface LOCATED_IN Node | relationship absent | DRIFT DETECTED |
| Data Drift | DATA-v22 | DATA-v20 | DRIFT DETECTED |
| Deployment Drift | REL-15 | REL-14 | DRIFT DETECTED |
Detection is described as architecture. No automatic remediation currently exists.
Closed loop
Observation hands the deployed object to The USA OS
Deployment changes state. The OS governs and observes state. Drift becomes an approved action, which becomes another deployment.
- 01DEPLOYMENT MANIFESTExpected
- 02DEPLOY
- 03SURFACE INSTANCE
- 04OBSERVE
- 05ACTUAL
- 06COMPARE
- 07IN SYNC or DRIFT DETECTED
- 01USA OS
- 02DESIRED VS ACTUAL
- 03DRIFT
- 04POLICY
- 05APPROVED ACTION
- 06DEPLOYMENT
- 07VERIFY
- 08AUDIT