Uses of Package
com.eqixiac.equinix.design.plan
Packages that use com.eqixiac.equinix.design.plan
Package
Description
Value types for the Deployment Wizard - the plan itself and everything it is made of, plus the
execution-side inputs and outcomes.
The deployment-plan lifecycle: plan as data, drift detection, idempotent and resumable reconcile,
and safe rollback.
-
Classes in com.eqixiac.equinix.design.plan used by com.eqixiac.equinix.design.optimizer.wizard.modelClassDescriptionWhere reconcile keeps its
Checkpoints.How a plan is executed or reconciled.A plan compared with live state: oneResourceDriftper planned element, the live resources that carry the plan's marker but are not in it, and notes on anything that could not be read.What a rollback removed and what it had to leave behind. -
Classes in com.eqixiac.equinix.design.plan used by com.eqixiac.equinix.design.planClassDescriptionThe progress of one plan's execution: every step known to exist, by logical key.Where reconcile keeps its
Checkpoints.A step recorded in aCheckpoint: the resource exists (or its create was accepted) under this uuid.How a planned resource compares with what is live.How a plan is executed or reconciled.What execution does when a create step fails: a Cloud Router, connection or routing-protocol create that is rejected, a pre-flight dry-run that is rejected (HTTP 4xx validation), or a resource that lands in a terminal failure state or does not reachPROVISIONEDwithin the timeout.One field that differs between the plan and the live resource.A connection as read from Fabric: the fields drift detection compares.A Cloud Router as read from Fabric: the fields drift detection compares.A routing protocol as read from Fabric.A snapshot of the live Fabric resources relevant to one plan, asLiveStateReaderread them (or as a test builds them).A resource a rollback could not remove.A plan compared with live state: oneResourceDriftper planned element, the live resources that carry the plan's marker but are not in it, and notes on anything that could not be read.One element of a plan in its uniform, dependency-ordered form: whatPlanSteps.of(DeploymentPlan)derives from aDeploymentPlanfor execution, reconcile, drift detection and checkpoints.A resource a rollback deleted and confirmed gone (DEPROVISIONEDor HTTP 404).The drift verdict for one planned resource.The kinds of element a deployment plan holds, in the order they are created.What a rollback removed and what it had to leave behind.What execution or reconcile did with one plan step.A live resource that carries the plan's marker (its deployment name inadditionalInfo, or the plan's name prefix) but matches no planned resource: left over from an earlier version of the plan, or created by hand.