Skip to content

Getting Started with Mantle 2.0

Use this guide immediately after deploying the Mantle 2.0 appliance. It walks through the first console login, web access, licensing, and core user/group setup so you can move directly into VMware, Linux, network, or automation workflows.

1. Sign in to the Appliance Console

  1. Open the VM console (VMware Workstation, ESXi, etc.).
  2. Log in with the default OS account:
  3. Username: mantle
  4. Password: M@NtleUser123!@#
  5. Change the password when prompted, then log back in with the updated credential.
  6. From the GNOME desktop, set a static management IP if DHCP is not available:
  7. Select the network icon -> Wired Settings -> gear icon.
  8. Switch the IPv4 method to Manual and enter the IP, subnet, gateway, and DNS values.
  9. Toggle the adapter off/on to apply the change.

Configure management IP

Tip: Record the IP address; you will use it for web access in the next step.

2. Access the Web UI and Secure the Admin Account

  1. Browse to https://<mantle-ip> and accept the certificate warning if one appears.
  2. Sign in with the default web credentials:
  3. Username: admin
  4. Password: admin
  5. Complete the forced password reset. Choose a strong passphrase that meets your organization's requirements.
  6. Avoid daily use of the Global Admin account, then create role-based accounts for routine tasks later in this guide.

Web login and password reset

3. Assign a Friendly Hostname

  1. Select the Settings gear -> Appliance tab.
  2. Locate Set Hostname (Reboot Required) and enter a fully qualified name (for example, mantle2.lab.local).
  3. Requirements:
  4. 1-253 characters
  5. At least two labels separated by a dot
  6. Letters, numbers, and hyphens only
  7. Click Set Hostname & Reboot. Mantle reboots and applies the new identity.
  8. After reboot, return to Settings -> Appliance to confirm the hostname update.

Set host name

Note: Ensure the hostname is resolvable in DNS before registering nodes or enabling Mantle Flow.

4. Upload Licenses

  1. Go to Settings -> Licenses.
  2. Select the green + button.
  3. Upload the Mantle 2.0 license file provided by NTS.
  4. Repeat for Mantle Flow or other feature licenses if applicable.
  5. Verify the license table lists the uploaded keys.

License upload

5. Create Groups

Groups define RBAC boundaries and asset scope.

  1. Open Groups from the left navigation.
  2. Select the green + icon, provide a name (for example, Edge-Lab), and save.
  3. Repeat for each team, customer, or deployment program.

Create group

6. Create User Accounts

  1. Navigate to Users.
  2. Click the green + icon and provide the username, email, and role (Viewer, Operator, Admin, etc.).
  3. Share initial passwords securely or enforce password resets at first login.

Create user

7. Upload Core Assets

Assets include templates, playbooks, OVAs, APKs, and other files used by builds or provisions.

  1. Open Assets -> +.
  2. Choose the asset category tab (Files, Scripts, Templates, etc.).
  3. Drag-and-drop or browse for the files.
  4. Use Upload Assets to set the correct type/subtype for each item.
  5. Select Upload All and watch the notifications for success or duplicate warnings.

Upload assets

8. Map Membership and Assets to Groups

Add Users to Groups

  1. Open Groups, select a group, then choose the Users tab.
  2. Use the white edit icon to add or remove members and set group roles.

Add user to group

Add Assets to Groups

  1. While viewing the same group, select the Assets tab.
  2. Click the green + icon, choose the required assets, and add them to the group.

Add asset to group

This ensures only authorized operators can run builds and that each group has the templates, ISOs, or APKs it needs.

Next Steps

With the appliance secured and baseline data in place, continue with the workflow that matches your deployment:

  1. VMware Datacenter Builds: Import hosts, deploy vCenter, and automate vSAN or DVS creation. See VMware & Linux Builds Section 4.
  2. Enterprise Linux Builds: Render and deploy the provided kickstart templates for bare-metal servers. See VMware & Linux Builds Section 5.
  3. Physical Network Builds: Push Jinja2 templates over serial connections to routers and switches. See Physical Network Builds.
  4. Mantle Flow Automation: Upload DAGs/playbooks and run post-deployment workflows. See Mantle Flow.

When those workflows are complete, return to the Templates Library for reusable kickstarts, network configs, and DAG skeletons.