Package com.eqixiac.equinix.design.optimizer.model


package 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).

Request types are assembled by MetroOptimizer.Builder into an OptimizationRequest; the engine returns an OptimizationResult whose parts - MetroRecommendation, MetroScore, DeploymentTopology, LatencyMatrix, RiskAssessment, CostEstimate - are all Lombok @Value types (get-prefixed accessors, builders, no setters).

Beta. MulticloudEnvironmentCatalog and MulticloudEnvironment are reference data, not request or result types: the pairs of cloud regions that two providers interconnect natively, each with a status (GA, PREVIEW, UNVERIFIED), its source URLs and the date they were read. The bundled catalog is a dated copy and goes stale; both the optimizer and the Deployment Wizard accept a caller-supplied one.

Cost figures are stamped per metro with their own currency and PriceSource; cross-currency totals are never fabricated (the aggregate total is null when metros span currencies).

See Also:
  • Class
    Description
    Aggregated cost estimate across all recommended metros.
    The recommended deployment topology: which workloads are placed in which metros.
    A single latency measurement between a metro and a user site.
    A metro-by-site latency grid.
    Estimated cost breakdown for a single metro.
    A single metro recommendation with composite score, placement rationale, provider availability, latency data, and cost estimates.
    Composite score for a metro recommendation, decomposed into individually inspectable ScoreComponent dimensions.
    One native provider-to-provider multicloud environment: a pair of cloud regions that two providers interconnect directly, with no Equinix resource on the path, together with the availability status observed for it, the source of that observation and the observation date.
    An immutable catalog of native provider-to-provider multicloud environments: the pairs of cloud regions that two providers interconnect directly, with no Equinix resource on the path.
    Human-readable explanation of the optimization methodology, assumptions, and data freshness for inclusion in reports.
    The run's DesignSpec restated in the shape the Deployment Wizard reads: sites, clouds (as ProviderRequirements labelled by the spec's cloud id) and workloads (as WorkloadSpecs whose dependencies carry the same labels).
    The result of a Metro Optimizer run.
    Indicates whether a specific provider is available at a metro, and if so, which seller regions are supported.
    Maps each recommended metro to the providers available there.
    A provider or service that must (or should) be reachable from the recommended metros.
    Aggregated risk assessment for the recommended deployment topology.
    A single risk identified in the recommended deployment topology.
    A single dimension of a metro's composite score.
    One candidate Fabric service profile for a given (provider, metro), carrying the bandwidth capability the deployment wizard needs to pick a profile that can actually carry a connection's speed.
    How the search went.
    A user-defined location representing a workforce concentration, customer market, or operational site.
    Assignment of a single workload to a specific metro with placement rationale.
    Defines the infrastructure characteristics of a workload type.
    Defines a workload to be placed by the optimizer, including its type, infrastructure requirements, and provider dependencies.