For the complete documentation index, see llms.txt. This page is also available as Markdown.
Support

V/OS Bundle

This section discusses the V/OS Bundle in VHQ.

Keywords

Also called: bundle of bundles, V/OS packaging. Search terms: control file, bundle container, secure installer.

What is a V/OS Bundle?

A V/OS bundle is a collection of one or more packages, signed and downloaded as a single unit on V/OS-based devices. It's simply an archive containing one or more signed packages (optionally including signer certificates and a special Remove file). In the example below, there are 2 bundles — Bundle1.TGZ and Bundle2.TGZ — each with a corresponding signature file (.p7s).

Multiple bundles are further compressed and wrapped in a bundle container (BundleContainer.TGZ) to form a bundle of bundles, which can contain one or more bundles.

A single bundle or bundle of bundles can be imported into VHQ and set up as a VHQ package. The contained V/OS packages (Package1.tar and Package2.tar) are extracted and set up as VHQ applications. Control File#1 defines the bundle name and version of Bundle1.TGZ; Control File#1.1 and Control File#1.2 define the package name and version for Package1.tar and Package2.tar, respectively.

Bundles are built by the corresponding SE (Sales Executive) using Secure Installer.

Structure of bundle of bundles (V/OS based devices)

Structure of a V/OS bundle of bundles
  • A V/OS bundle is configured as a package in VHQ, and a package contained in the bundle is configured as an application.

  • For devices enabled for automated download, VHQ downloads bundles that don't match the bundles on the device. Bundle name and version, as defined in the control files, form the basis for evaluating the software version set up on VHQ — only bundles with control files qualify for automated downloads.

  • Only VHQ packages qualified for automated download are available when creating a reference set.

Last updated

Was this helpful?