Package com.eqixiac.equinix.design.optimizer.wizard

package com.eqixiac.equinix.design.optimizer.wizard

The Deployment Wizard: turns a metro OptimizationResult into an executable DeploymentPlan — Cloud Routers, provider connections, inter-metro backbone links, and routing protocols, with bandwidth-aware profile selection and honestly-reconciled pricing.

The pipeline is plan → validate → execute:

• Plan — DeploymentWizard.Builder (reached via fabric.deploymentWizard(result)) configures packages, topology, bandwidth strategy, ASN/BFD, notifications, and pricing; plan() produces an immutable plan. Nothing is provisioned by planning.
• Validate — PlanValidator runs in three layers (structural/catalog checks, a live self-contained Cloud Router dry-run, and the connection endpoint dry-run where an endpoint already exists) and sorts every finding into three buckets that are never conflated: errors (validated now; a hard defect or genuine API rejection — invalidates the plan), deferred to provisioning (the connection endpoint dry-run that must wait for the A-side router to exist), and skipped (could not be attempted — offline gateway or a non-rejection API failure — each with a reason, never invalidating the plan). DeploymentPlan.dryRun() re-runs validation and returns a new plan with refreshed state.
• Execute — DeploymentPlan.execute(ExecutionInputs) refuses an invalid plan (IllegalStateException), fails fast on missing customer authorization keys, then provisions in dependency order: Cloud Routers (awaiting PROVISIONED), provider connections (each pre-flighted with a live dry-run against its now-real router), backbone links, then routing protocols. State waits distinguish ready / real terminal failure / timeout; a genuine dry-run or create rejection aborts the run and unwinds everything already created in LIFO order, and rollback(outcome) offers the same best-effort teardown for partial deployments.

The safety model is plan-only-until-execute: plans, dry-runs, repricing, value realization, and export are all side-effect free; only execute() creates billable resources, and only after validation, input checks, and per-connection pre-flights.

Sub-packages: model (the plan and its parts), enums (topology, bandwidth strategy, connection purpose).

See Also:

• DeploymentWizard
• DeploymentPlan
• PlanValidator

Related Packages

Package	Description
com.eqixiac.equinix.design.optimizer	The Metro Optimization Engine: scores, ranks, and selects Equinix metros for a deployment from user sites, provider requirements, workloads, and constraints, against live Fabric catalog data.
com.eqixiac.equinix.design.optimizer.wizard.enums	Configuration enums for the Deployment Wizard: BackboneTopology (how the recommended metros are meshed with inter-metro backbone links), BandwidthStrategy (how provider connections are sized from workload requirements), and ConnectionPurpose (what role a planned connection plays in the plan).
com.eqixiac.equinix.design.optimizer.wizard.model	Value types for the Deployment Wizard — the plan itself and everything it is made of, plus the execution-side inputs and outcomes.
com.eqixiac.equinix.design.optimizer.enums	Enumerations that parameterize the Metro Optimization Engine: OptimizationStrategy (scoring weight presets), WorkloadType (workload archetypes with built-in profiles), LatencySensitivity (default per-workload placement ceilings), SiteRole (site importance multipliers), RedundancyTier (metro-count floors and region-diversity selection), ComplianceZone (region-based data-sovereignty zones with deployment-level AND semantics), ScoreCategory (the five scoring dimensions), and RiskSeverity (risk-finding levels).
com.eqixiac.equinix.design.optimizer.model	Immutable value types for the Metro Optimization Engine — the request side (sites, provider requirements, workload specs, constraints, scoring weights) and the result side (ranked recommendations, scores, topology, latency matrix, risk assessment, cost estimates).

Class	Description
DeploymentWizard	Entry point for the Deployment Wizard.
DeploymentWizard.Builder	Fluent builder for configuring a deployment plan.
PlanValidator	Layered, plan-time validation for the Deployment Wizard.
PlanValidator.LiveFailure	The classification of a single live-layer failure.
PlanValidator.LiveFailureKind	Whether a live-layer failure is a genuine rejection (a plan defect) or an infeasibility (a skip).
PlanValidator.Result	The outcome of validating a plan, in three distinct buckets — hard/rejection errors (which invalidate the plan), deferred validations (which do NOT — they run at provisioning), and skipped validations (which do NOT — they could not be attempted now, each with a reason) — plus the per-connection customer inputs a first-time customer must gather.