Skip to content

Install Guide (Mantle 2.0)

Overview

Use this guide to deploy Mantle 2.0 on VMware Workstation (Edge/Lab/Demo) or VMware ESXi/vCenter (production). It covers appliance import, network preparation, first-boot configuration, licensing, asset upload, and build-interface enablement. Review the definitions below for quick reminders of common terminology that appears throughout the Mantle 2.0 documentation set.

Definitions

  • Mantle: The core automation appliance that manages assets, orchestrates builds, and provides the web UI.
  • Mantle 2.0: The enterprise/edge release of Mantle that adds datacenter PXE workflows, Mantle Flow, and expanded orchestration features.
  • Mantle Flow: The Flow engine embedded in Mantle 2.0 for post-deployment automation.
  • Appliance Settings: The configuration area inside Mantle where you map interfaces, serial ports, and other system-level options.
  • Build Interface: The secondary NIC Mantle uses for PXE/build traffic, typically isolated from the management network.
  • Management Network: The VLAN/VMnet that provides administrative access to the Mantle UI and APIs.
  • PXE Network: The VLAN/VMnet that carries DHCP/TFTP/HTTP traffic for automated OS installs and must reach both Mantle and target devices.
  • Port Group / VMnet: VMware logical networks (e.g., VMnet0, VMnet1, ESXi port groups) that Mantle NICs attach to.
  • OVA: Open Virtual Appliance package that contains the Mantle VM image for import into VMware platforms.
  • Asset: Files uploaded to Mantle (templates, playbooks, OVAs, configs, APKs) that are assigned to groups or builds.
  • Baseline / Provision: Reusable instructions plus assets used to configure devices (datacenter builds, mobile provisions, etc.).
  • Node: A registered Mantle Mobile or appliance endpoint that executes tasks/provisions on behalf of Mantle 2.0.
  • Kit ID: Optional identifier used to track a collection of devices/builds through a deployment workflow.
  • DAG (Directed Acyclic Graph): The workflow definition used by Mantle Flow to describe task order and dependencies.
  • Playbook / Collection: Ansible automation content invoked during builds or Mantle Flow runs.
  • Serial Device Profile: A mapping of serial console settings that Mantle uses when automating physical network gear.

Requirements

This section outlines the minimum hardware, software, and network requirements needed to deploy and run Mantle 2.0. Ensure your system meets or exceeds these specifications for optimal performance and compatibility.

  • CPU: 4 dedicated vCPUs (2 sockets x 2 cores) minimum. Mantle runs multiple services (web UI, orchestration, PXE, database); more cores improve dashboard responsiveness and parallel builds.
  • Memory: 8 GB RAM minimum. Plan for 12-16 GB if you expect to host PXE services, Mantle Flow, or large asset uploads so caching and Ansible runs do not swap.
  • Storage: 500 GB SSD/HDD for the appliance disk. Use SSD whenever possible to accelerate database writes, log ingestion, and PXE image access. Mantle supports expanding the appliance VMDK later (see the storage expansion step in the Workstation tab), so leave additional datastore capacity for snapshots or future disk growth.
  • Network Interfaces: At least one physical NIC for management traffic; two NICs recommended if you will isolate the PXE/build network. Ensure the host NICs can map cleanly to the VMware port groups you created in the software requirements above.
  • Virtualization Software:
    • VMware Workstation Pro 17+ (Windows/Linux): Ideal for laptop or desktop labs. Ensure the host can dedicate at least 4 CPU cores, 8 GB RAM, and a bridged NIC to the Mantle VM. Workstation also lets you add a second VMnet for the PXE/build network if needed.
    • VMware ESXi or vCenter/vCSA: Recommended for production. Deploy Mantle as an OVA on a managed cluster so you can take advantage of HA, snapshots, and dedicated port groups. Give the appliance two port groups when you plan to run PXE workflows (one for management, one for build traffic).
  • Management Network: Allocate a dedicated management VLAN/port group for Mantle. In VMware Workstation this usually maps to VMnet0; decide up front whether it should bridge to production (recommended) or run Host-only (lab use) and reserve a static IP, subnet, gateway, and DNS values so you can configure them immediately after first boot.
  • Build / PXE Network (if you plan to run PXE-driven datacenter builds): Provide a second vSwitch/VMnet that reaches your PXE infrastructure. This network must supply DHCP during PXE boots and allow HTTP/TFTP traffic back to the Mantle host. Isolate this VLAN if Mantle will host its own DHCP scope.
  • Internet / Repository Access (optional but helpful): Mantle can run air-gapped, but outbound Internet makes it easier to download licenses, OS packages, and support tools. Without egress, plan on importing licenses and assets manually via the UI.

Installation

Mantle 2.0 is packaged as a VMware OVA and can run on either VMware Workstation (Edge/Lab/Demo) or VMware ESXi/vCenter (production). Use the tabs below to follow the workflow that matches your hypervisor.

Overview

Use this workflow to deploy Mantle 2.0 on VMware Workstation Pro 17. It walks through importing the OVA, preparing VMnet networking, configuring the appliance IP, signing in to the web interface, applying licenses, uploading assets, and enabling the build interface.

Important

Before You Begin

Confirm the following items are available before starting:

  • VMware Workstation Pro 17
  • The Mantle 2.0 OVA file
  • A target location with sufficient disk space for the virtual machine
  • A network plan for the Management interface and, if required, the Build (PXE) interface
  • A Mantle 2.0 license file provided by your administrator
  • Any automation assets that will need to be uploaded after initial setup

Deployment Procedure

1. Import the Mantle 2.0 appliance

  1. Open VMware Workstation Pro 17.
  2. Select Open a Virtual Machine.

VMware Workstation home screen with Open a Virtual Machine selected

  1. Select the Mantle 2.0 OVA file.

Selecting the Mantle 2.0 OVA file in VMware Workstation

  1. Enter the desired name for the Mantle 2.0 virtual machine and select the storage location for the VM.

Naming the virtual machine and choosing the storage path

  1. Wait for the appliance import to complete.

Import in progress for the Mantle 2.0 virtual machine

2. Configure VMware virtual networks

  1. Before powering on Mantle 2.0, open Edit > Virtual Network Editor in VMware Workstation.

Opening the Virtual Network Editor from the VMware Workstation menu

  1. Select Change Settings so the network configuration can be modified.

Virtual Network Editor with Change Settings highlighted

  1. Map VMnet0 to the desired network adapter in the VMnet Information bridge section.

For local-only access, you can instead select Host-only, then enable: - Connect a host virtual adapter to this network - Use local DHCP service to distribute IP address to VMs

Define the desired subnet or use the default subnet.

VMnet0 mapped to a bridged adapter in the Virtual Network Editor

Host-only network configuration options for local access

  1. For datacenter builds, configure a second interface for the build or PXE network by selecting VMnet1 and mapping it to the appropriate network adapter.

Second virtual network configured for the build or PXE interface

  1. Select Apply, then OK to save the network configuration.

3. Assign virtual network adapters to the Mantle VM

  1. Return to the main VMware Workstation screen and select Edit virtual machine settings for the Mantle 2.0 VM.

Opening virtual machine settings for the Mantle VM

  1. If your deployment requires the build interface, select Add..., choose Network Adapter, and then select Finish.

Adding a second network adapter in virtual machine settings

  1. In the virtual machine settings:
  2. Network Adapter is used for the Management network.

  3. Network Adapter 2 is used for the Build (PXE) network.

  4. Map Network Adapter to VMnet1 under Custom: Specific virtual network.

Management adapter mapped to a custom VMware virtual network

  1. Map Network Adapter 2 to VMnet2 under Custom: Specific virtual network.

Build adapter mapped to a custom VMware virtual network

4. Expand virtual disk capacity if needed

  1. If additional storage is required, select Hard Disk (SCSI) and then select Expand.
  2. Enter the desired virtual disk size and select Expand.
  3. Wait for the disk expansion process to finish.

Expanding the Mantle virtual disk capacity in VMware Workstation

  1. Select OK after the Expand Disk Capacity window closes.

This completes the initial VMware configuration for Mantle 2.0.

5. Power on the appliance

  1. Select Power on this virtual machine.

Powering on the Mantle virtual machine

  1. If the disk was expanded, allow additional time for the initial startup.
  2. Once the AlmaLinux or Red Hat Enterprise Linux (RHEL) graphical interface appears, Mantle 2.0 is ready for network configuration and browser access.

Mantle appliance booted to the AlmaLinux or RHEL graphical interface

6. Configure a static IP address on the management interface

  1. Sign in to the operating system using the default local account:

  2. Username: mantle

  3. Password: M@NtleUser123!@#

  4. Change the password when prompted, then sign in again with the new password.

Operating system login prompt for the mantle account

Password change prompt after initial login

  1. When the AlmaLinux or RHEL welcome prompt appears, select No Thanks.

Welcome prompt with No Thanks selected

  1. In the upper-right corner of the desktop, select the network icon, choose Ethernet (eth0) Connected, then select Wired Settings.
  2. In the Wired (eth0) section, select the gear icon.

Opening network options from the desktop menu

Selecting Wired Settings from the Ethernet menu

Opening detailed settings for Wired eth0

  1. Select IPv4, change the method to Manual, and enter the required IP address, subnet mask, gateway, and DNS server values.
  2. Select Apply.

Manual IPv4 configuration for the management interface

  1. Toggle the wired connection off and back on again to apply the updated network settings.
  2. Exit the AlmaLinux or RHEL desktop after the network configuration is complete.

7. Access the Mantle 2.0 web interface

  1. Open a web browser and browse to https://<mantle-ip-address>.
  2. If the browser displays a certificate warning, select Advanced and then proceed to the appliance IP address.

Browser certificate warning when accessing the appliance by IP address

Proceeding past the certificate warning to the appliance IP address

  1. Sign in to the Mantle 2.0 web interface using the default administrative credentials:

  2. Username: admin

  3. Password: admin

  4. Change the password when prompted.

Initial Mantle web login and password change prompt

  1. Enter a new password for the local administrative account, confirm it, and select Reset Password.
  2. When the login page reappears, sign in with the updated credentials.

8. Upload the license

  1. In the main Mantle dashboard, use the prompt in the lower-left corner to open Settings > Licenses.

Dashboard prompt directing the user to license configuration

  1. Select the green + button in the upper-right corner and choose the Mantle 2.0 license file provided by your administrator.
  2. Upload any additional feature licenses required for the deployment.

Adding a Mantle license from the Licenses page

  1. Return to Home in the left navigation pane.
  2. Confirm that the licensed features now appear as enabled on the dashboard.

Dashboard showing licensed features after activation

9. Upload automation assets

  1. In the left navigation pane, select Assets and then choose the appropriate asset category.
  2. Select the green + button in the upper-right corner.
  3. Drag and drop the file or files into the upload window, or use the Uploads icon to browse manually.

Uploading assets from the Assets page

  1. On the Upload Assets tab, assign the correct type and subtype for each uploaded asset.
  2. Select Upload All.

Asset type and subtype assignment before upload

  1. Close the upload window when the transfer completes.

10. Configure the build interface and review serial ports

  1. Select the Settings gear icon in the lower-left corner to open the settings page.

Opening the appliance settings page in Mantle

  1. Open the Appliance tab and expand the Build Interface section.
  2. Select the unused network adapter for the build interface.
  3. Select Save Build Interface.

Build Interface configuration within the Appliance settings tab

  1. Expand the Serial Ports section.
  2. Confirm that any connected serial or USB serial devices appear in the list. If no devices appear, continue with the applicable troubleshooting procedure.

Serial Ports section displaying available serial connections

At this stage, Mantle 2.0 is ready for use.

Deployment summary

The appliance is fully imported and configured when all of the following are complete:

  • The VMware virtual networks are assigned correctly
  • The Mantle VM has the required management and optional build interfaces
  • The management interface has a reachable static IP address
  • Administrative passwords have been changed
  • Licensing has been applied
  • Required automation assets have been uploaded
  • The build interface is selected in Settings > Appliance

Overview

Deploy the Mantle 2.0 appliance directly on VMware ESXi or vCSA, add the optional build interface, adjust storage, and configure a static management IP before handing the system to operators.

Prerequisites

  • ESXi Host Client or vSphere access
  • Mantle 2.0 OVA file on local storage
  • Datastore capacity for the appliance and any disk expansion
  • Management and build port groups
  • Static IP information (IP, mask, gateway, DNS) for the management interface

Procedure

  1. Sign in to the ESXi Host Client and open Virtual Machines.
  2. Add the build port group. In Networking, click Add port group, then supply the port group name and upstream switch. Add build port group Name the build port group
  3. Create / Register the VM. Return to Virtual Machines and click Create / Register VM. Create / Register VM
  4. Deploy from OVA. Choose Deploy a virtual machine from an OVF or OVA file and click Next. Deploy from OVA
  5. Select the OVA. Name the VM, browse to the Mantle 2.0 OVA, and click Next. Select Mantle OVA
  6. Choose a datastore. Pick the datastore that hosts Mantle. Select datastore
  7. Map the management network. Select the management port group, choose the disk provisioning method, and leave Power on automatically unchecked. Select management port group
  8. Finish the import. Review the summary and click Finish. Finish OVA import
  9. Open the VM card once the import completes. Open VM
  10. Edit the VM settings. Click Edit in the action bar. Edit settings
  11. Attach the build NIC. Click Add network adapter and select the build port group created earlier. Add build adapter
  12. Expand storage (optional). Adjust Hard disk 1 to the desired size and click Save. Expand disk
  13. Power on the appliance. Initial boot can take several minutes, especially after expanding storage. Power on Boot sequence
  14. Log in to the OS console. Use mantle / M@NtleUser123!@#, change the password when prompted, and sign in again. Console login Password change Re-authenticate
  15. Dismiss the welcome prompt by clicking No Thanks. Welcome prompt
  16. Open network settings. Click the network icon, choose Ethernet (eth0) Connected, select Wired Settings, and then open the gear icon for eth0. Open Wired Settings eth0 details
  17. Set a static management IP. On the IPv4 tab select Manual, enter the IP, mask, gateway, and DNS values, and click Apply. Manual IPv4
  18. Bounce the interface. Toggle the wired connection off and back on so the new settings take effect, then exit the desktop. Toggle connection
  19. Open the Mantle web UI. Browse to https://<mantle-ip-address>, bypass the temporary certificate warning, and continue to the site. Certificate warning Proceed past warning

Result

Mantle 2.0 now runs on ESXi/vCSA with dedicated management and build networks, optional disk expansion applied, and a static IP that operators can reach via HTTPS.

Notes

  • Leave Power on automatically unchecked until the build adapter and disk sizing are finalized.
  • The first boot is slower after disk expansion; allow several minutes before interacting with the console.
  • Change the default local credentials immediately after the first login.

Next Steps: Expand Your Deployment

Once the management appliance is online, continue with the workflows below to round out Mantle 2.0 operations. Each link opens the detailed guide with every screenshot and field reference.

Physical Network Builds

  • Reset routers or switches with the Write/Erase utility before pushing production configs.
  • Upload approved Jinja2 templates and map each serial port to the correct device.
  • Track every serial session output for after-action validation.

Serial port readiness check

Read the full Physical Network Builds guide for the complete operator checklist.

Mobile Device Provisions

  • Import devices from nodes or spreadsheets so every phone is tracked in its Mantle group.
  • Assign APKs, configs, baselines, and optional files before launching a provision.
  • Enable Node Mode inside Mantle Mobile so the desktop agent pulls active jobs automatically.

Create a new mobile provision

See the Mobile Device Provisions guide for the full provisioning workflow.

Mantle Flow Automation

  • Upload Mantle Flow licenses plus DAG, playbook, and collection assets.
  • Assign flows to the proper group and run them through the Mantle Flow Deployment Wizard.
  • Monitor executions on the Track Flow page and download configuration objects for reuse.

Mantle Flow wizard

Visit the Mantle Flow guide for an in-depth automation walk-through.