Importing existing infrastructure into MetalSoft

It is possible to import existing infrastructure into MetalSoft with some caveats.

Importing servers already in use, with operating systems

You may want to import existing servers in order to:

• have them shown in the same Infrastructure as other newly deployed servers
• in order to monitor them
• in order to be able to change the network connections to them

To add an in-use server follow the following steps:

1. Go to Servers → Add Server
2. In the Registration type select “Production (in use)”
3. Input the credentials and the IP of the BMC of the server
4. Select the infrastructure on which the server will be added. The infrastructure should not be in the deployment process at this time.
5. (optional) If network provisioning is needed, input the network connections. These can also be added later, after the server is registered. The system will also attempt to determine the information automatically if not already inserted.
6. (optional) You can select an Operating system just as an indication in the UI for the users but there will be no installation done except when the ‘reinstall’ command is issued.

Importing switches with existing configuration, running a supported NOS

Any switch can be registered in MetalSoft with no impact on existing configuration, with some caveats.

1. Register the switches
2. Add VLANs that need to be preserved When first deployed the system will cleanup unused VLANs, VNIs and port channels unless they are configured in the “Prevent cleanup” section of the respective Fabric.

• List all VLANs that need to be preserved Fabrics → fabric → Configuration → Prevent VLAN Cleanup.
• If they only need to be preserved on the Uplinks use Fabrics → fabric → Configuration → Prevent Cleanup from Uplinks.

3. Create Endpoints or Register servers as usual

• Endpoints → Add Endpoints
• Servers → Add Server (or use ZTP)

4. Create Logical Networks for all VLANs/VNIs that are needed.
5. Add the endpoints/servers to the Infrastructures
6. Deploy the infrastructures

Migration from non-supported switches to MetalSoft supported ones

MetalSoft can help migrate network configurations from old hardware to new hardware, with the help of AI. The following are the the steps that we typically apply:

1. Scanning the configuration files of existing systems and generating new logical networks, infrastructures and endpoints in a format called OID (Open Intent Definition).
2. Adding the new switches with a base configuration via Add Switch form or via ZTP
3. Importing the OID format into MetalSoft via the CLI
4. Deploying the newly created infrastructures effectively generating all the required configuration to mimic the original configuration.

Importing storage systems

Storage systems can be safely added to MetalSoft as there is no impact on existing clusters. Volumes managed by MetalSoft will be tracked by MetalSoft. Volumes created outside of MetalSoft will not be tracked (or imported).

Importing virtualization systems

Existing virtualization systems (such as Incus or VMWare) can be added safely in the system. By default only newly created VMs will be tracked by MetalSoft.

A process similar to the intent reconstitution presented above is also possible for VM migration in most cases. Contact the MetalSoft team for organizing this import process.

Refer to VMWare alternative if you are looking for alternatives to the the VMWare stack or looking to run more than one hypervisor at the same time.