Skip to content

Mantle 2.0 Guide: Asset Management

Overview

Assets are the files, packages, templates, scripts, and supporting artifacts that power Mantle 2.0 workflows. They provide the reusable inputs behind datacenter builds, physical network automation, mobile provisions, and Mantle Flow runs.

Use this guide when you need to:

  • Upload new files into the global asset library
  • Choose the correct asset type and subtype during ingestion
  • Apply group tags for organization and filtering
  • Remove obsolete assets safely
  • Prepare script assets for reuse across teams

1. Asset Types in Mantle 2.0

Mantle supports several asset families, each aligned to a workflow:

Asset Family Common Examples Typical Use
Platform install media ISO, OVA, VM Disk Image, VM Config VMware, Linux, and VM provisioning
Automation content Playbook, Script, DAG Post-build setup, validation, orchestration
Reusable configuration Template, Kickstart, File Network builds, unattended installs, reusable config output
Offline or grouped content Collection, Offline Package Disconnected delivery, bundled multi-file uploads
Mobile assets Configs, APK, ATAK PREFS, BASELINE, COMMON, UNIQUE Device onboarding and mission packages

Some screens also refer to Mantle, Mobile, and Enterprise as grouping contexts. Those are organizational labels, not separate asset types.

2. Upload Global Assets

Follow this workflow to upload one or more assets into the global library:

  1. Open Assets from the left navigation. Assets category in left nav
  2. Click the green Add button to open the upload modal. Add global asset button
  3. Use Click to upload to select one or more files from your workstation. Click to upload area
  4. Confirm the files appear in the upload list, then open the Upload Assets tab. Selected files visible in upload modal
  5. For each file, choose the correct Asset Type and Asset Subtype. Asset type and subtype selection
  6. Click Upload All to begin ingestion.
  7. Use Monitor Assets to track upload, install, completion, or failure states. Monitor assets button Assets uploading monitor state Assets installing monitor state Completed assets in monitor

Tip: Set the asset type carefully before upload. Several asset families perform validation based on both extension and subtype, and retagging after ingestion may not be available.

3. File Types and Validation

Mantle validates uploaded files against the selected asset type. Use the following as a practical reference:

Asset Type Typical Extensions Notes
ISO .iso Bootable media for ESXi, Linux, VCSA, or general VM installs
OVA .ova Virtual appliance packages
VM Disk Image .vmdk, .img, .qcow2 Raw or imported virtual disks
VM Config .vmx, .nvram, .mf Hypervisor configuration artifacts
Kickstart .ks, .cfg Unattended Linux installation definitions
Playbook .yml, .yaml Ansible playbooks or task-only content
Script .sh, .ps1, .py, .json, .yml, .yaml Script and automation fragments
Template .json, .yaml, vendor configs Reusable configuration baselines
Collection / Offline Package .zip, .tar, .tar.gz Bundled multi-file content
Mobile bundles .zip, .json, .xml, .apk Mobile configs, apps, and mission packages
DAG .json, .yaml Workflow graph definitions

Validation normally includes:

  • Extension checks against the selected type
  • Archive or package signature checks for supported binary formats
  • Metadata extraction for APKs, DAGs, templates, and similar structured uploads
  • Subtype enforcement when the asset family requires vendor, model, or content classification

If a file relies on companion content, compress the full folder and upload it as a Collection or Offline Package rather than uploading isolated fragments.

4. Delete Global Assets

Remove obsolete or incorrect uploads from the global library with the asset action menu:

  1. Locate the asset in Assets and open its Action menu. Asset action menu
  2. Select Delete. Delete action in dropdown
  3. Wait for the delete status to complete, especially for larger uploads such as VCSA images or large archives. Deleting asset status message

Delete activity may be temporarily serialized for large assets. Avoid repeated clicks while the platform is removing a file.

5. Tag and Classify Group Assets

Tags help operators classify group-scoped assets by mission, environment, or package role.

  1. Open Groups and select the target group. Groups tab in left nav Select target group
  2. Open the Tags tab and click the green Add button. Group tags tab Add tag button
  3. Enter a tag name, optional description, and color, then submit. Create tag form Newly created tag in list
  4. Switch to the group's Assets tab, open the asset Action menu, and choose Tag. Group assets tab after tag creation Asset action menu with tag option
  5. Select one or more tags from the dropdown to apply them. Apply tag dropdown Applied tag confirmation Multiple tags selected
  6. Click an applied tag again to remove it when no longer needed. Remove applied tag

Use a small, stable taxonomy for tags. Broad labels such as prod, staging, ios, vmware, or baseline are easier to maintain than one-off labels for every upload.

6. Manage Script Assets

Scripts are one of the most common reusable asset types in Mantle 2.0. Keep them portable and predictable:

  • Validate syntax locally before upload with tools such as shellcheck, python -m py_compile, or a PowerShell parser check
  • Parameterize inputs so the same script can run across multiple environments
  • Document dependencies and assumptions in header comments
  • Avoid embedding secrets directly in the script body

Supported script extensions include:

  • .sh
  • .ps1
  • .py
  • .yml
  • .yaml
  • .json

When a script depends on helper files, upload the full package as a Collection or Offline Package so supporting content stays together.

Next Steps

After your shared asset library is in place:

  1. Use Group Management to scope assets to the right teams.
  2. Use Build Management to launch template-driven workflows.
  3. Use VMware & Linux Builds or Physical Network Builds to consume those assets in deployment workflows.