Import and Export Functionality
Import
Import a Simulation from a JSON Simulation Manifest File
Import from Data
Import and Export Placement Groups
For a supporting Air API deployment, put placement_group on each grouped node in
JSON topology content.nodes. The SDK forwards this content unchanged. A JSON export
contains membership for grouped nodes and omits the field for ungrouped nodes.
The export is a manifest with format and content, suitable for
import_from_simulation_manifest (as a dictionary or saved JSON file).
Cloning with grouped_sim.clone() delegates copying node membership to the API;
there is no separate SDK placement-group argument for cloning. DOT import forwards
its topology text unchanged, including a node attribute such as
placement_group="rack-a" when present. Server parsing and placement still require
a supporting Air API deployment.
Import a Topology That Declares Services and Instructions
A JSON topology may declare top-level services (exposed ports) and
instructions (setup commands run on nodes) lists, alongside nodes and
links. They are top-level (rather than nested under a node) so that the
oob-mgmt-server can be targeted too. When present, they are imported with the
simulation.
Export
Export an Existing Simulation
Export including Instructions and Services
By default an export omits instructions and services. Opt in with
include_instructions (an InstructionExportChoice — NONE, REPEATABLE, or
REPEATABLE_OR_NOT_READY) and include_services=True. The exported topology
then carries top-level services and instructions lists, so it round-trips
back through import_from_data / import_from_simulation_manifest.