Package com.eqixiac.equinix.design.optimizer.wizard.model
The centrepiece is DeploymentPlan
(immutable; dryRun() returns a refreshed copy, execute(ExecutionInputs) does the
provisioning). Its parts are the planned resources -
PlannedCloudRouter,
PlannedConnection,
PlannedBackboneLink,
PlannedRoutingProtocol - with the
sizing/selection evidence
(BandwidthAllocation,
ProfileSelection,
ProfileCandidate) and
currency-honest pricing
(PlanPricing - cross-currency totals
are withheld, never fabricated).
Beta. A fifth kind of planned entry,
PlannedMulticloudInterconnect, is a
native provider-to-provider link between two clouds. It has no Fabric request body: the plan
carries and prices it
(MulticloudLinkPricing: native quote,
Equinix-path cost for the same flow, break-even sustained rate in Mbps), execution never
provisions it, and DeploymentOutcome.getInformational() lists it.
Execution consumes ExecutionInputs
(the customer-supplied authorization keys enumerated by
ConnectionInputRequirement) and yields
a DeploymentOutcome of
ProvisionedResources and
ProvisioningErrors.
RouterBodies and
ConnectionBodies are the single home
of the wire-body shapes, so dry-runs and real creates send identical requests.
Most types here are Lombok @Value (get-prefixed accessors, builders, no setters).
- See Also:
-
ClassesClassDescriptionBandwidth sizing breakdown for a single connection, showing how the total bandwidth requirement was derived from individual workload requirements under the configured
BandwidthStrategy.Assembles a complete Fabric connection body from aPlannedConnection- both endpoints, encapsulation, and cloud authorization - so a live dry-run or a real create sends the whole request the API needs, not the endpoint-less name + bandwidth shell that Fabric rejects withEQ-3142501 "Null value for aSide access point".The per-connection authorization a customer must gather before a provider connection can be provisioned.The result of executing a deployment plan.A deployment plan produced by the Deployment Wizard: the Cloud Routers, provider connections, backbone links and routing protocols to create, the native multicloud links and Fabric Interconnects the design relies on but the SDK does not create, pricing, and the layered validation state.The customer-supplied, per-connection authorization aDeploymentPlan.execute(ExecutionInputs)run needs to provision cloud provider connections: the cloud-specific authentication key, the DOT1Q VLAN tag, and (for Azure ExpressRoute) the peering type.The cost of one cloud-to-cloud flow over each of its two paths: the native multicloud link (billed by the two cloud providers) and the Equinix path the same flow would use (two Fabric virtual connections plus the cloud providers' own port fees), with the sustained rate at which the two cost the same.An inter-metro Fabric backbone link between two Cloud Routers, enabling private connectivity between deployment metros.A Cloud Router (FCR) to be created as part of a deployment plan.A Fabric connection to be created as part of a deployment plan.A Fabric Interconnect (the managed routed network behind Fabric One) that a deployment plan includes, but that this SDK cannot create.A native provider-to-provider multicloud link carried on aDeploymentPlan: a direct connection between two clouds (for example AWS Interconnect - multicloud paired with a Google Cloud Partner Cross-Cloud Interconnect transport) that uses no Equinix resource.One Cloud Router to cloud connection of the Equinix path for the flow.A routing protocol configuration to be applied to a planned connection.Aggregated pricing breakdown for a complete deployment plan, including Cloud Router costs, provider connection costs, and backbone link costs.Fluent builder, returned byDeploymentPlan.valueRealization(), that computes the egress savings a deployment plan produces once the caller declares their per-provider monthly egress volumes, net of the plan's cost.The value-realization view of aDeploymentPlan: the monthly cloud-egress saving the plan's private interconnects produce (versus public-internet egress), netted against the plan's actual Equinix interconnect cost.The egress-saving row for one declared cloud provider: the internet-egress cost the declared volume would incur, the private-interconnect cost the plan enables instead, and the difference.One service profile that can carry a given connection's bandwidth, as a typed decision point the wizard exposes instead of silently picking.How the wizard chose a service profile and a billable bandwidth for one provider connection - the bandwidth-aware selection made visible rather than hidden.A single resource that was created during deployment execution - the audit-trail entry aDeploymentOutcomecarries for every create that succeeded, including resources that were subsequently torn down by an abort-and-rollback.An error recorded while executing a deployment plan - a resource that could not be provisioned, a pre-flight or waiter observation, or a rollback deletion that failed.Assembles a complete Fabric Cloud Router body from aPlannedCloudRouter- name, metro, package, the optional account/project references, and the mandatory notification recipients - mirroringConnectionBodiesfor connections.