Export operation fetches data from remote repositories to local as sync operation. Instead of pushing images to local harbor, export downloads images into tar packages, packaged in a bundle for import to any other Airgap Appliance.
Prerequisites
The TCA Airgap Appliance must be reachable to Broadcom official websites on the Internet.
Procedure
- Login to the TCA Airgap Appliance using SSH admin account then switch to root with
su
to useagctl
command. - Prepare the parameters and trigger the export.
Edit
/usr/local/airgap/scripts/vars/user-inputs.yml
using the following command:vi /usr/local/airgap/scripts/vars/user-inputs.yml
Modify the following parameters on demand:
product.name
Artifacts of product name to download and export. The value could be
tca
orphoton
.Note:The Photon repositories that you wish to fetch irrespective of TCA release defined in product versions, it is must always be the latest.
product.versions
versions of the products to download and export. Currently, the version is only meaningful when the product name is
tca
. It could be a range of versions, or a single version string with format<major version number>.<minor version number>.<patch version number>
.product.baseline
Only the artifacts after a baseline are exported. Currently, the version is only meaningful when the product name is “photon”. The baseline can be a previous VMware Telco Cloud Automation release version starting from 2.3.0. TCA made a snapshot on the photon package list after a TCA version was released. Without the baseline version specified, the full set of photon packages will be mirrored, otherwise only the incremental packages will be exported.
build_sync
This field is required to be specified for the highest TCA release supported. It is formatted with
<tca version>-<build number>
. The build number could be found on the release note of VMware Telco Automation product.local_only
If this flag is True, only the TCA artifacts belonging to the specified TCA releases will be exported. TCA dependent TKG artifacts and photon repositories are skipped.
TCA releases bom files are downloaded automatically to folder
/usr/local/airgap/bom
during the operation, and then the artifacts listed in the bom files will be downloaded and exported.ran_bom_images
Set to
True
when exporting a RAN BOM bundle. Default value is False.ranbom_images_list
Comma separated list. The default value is ranbom-tcp.3.0.0-image to export TCP 3.0 images.
Examples:
Exporting full artifacts of TCA releases, and their dependent TKG releases, and all the packages of current photon repositories.
products: - name: "tca" versions: "2.3.0-3.2.0" build_sync: "3.2.0-<build number>" local_only: False
Exporting artifacts of TCA 3.2.0 and only the incremental photon packages added after the time TCA 3.1.1 released
products: - name: "tca" versions: "3.2.0" - name: "photon" baseline: "3.1.1" build_sync: "3.2.0-<build number>" local_only: False
Exporting only the TCA artifacts of certain releases, and skipping TKG and Photon.
products: - name: "tca" versions: "3.2.0" build_sync: "3.2.0-<build number>" local_only: True
Exporting the adhoc ran bom images.
ran_bom_images: Trueran_bom_images_list: ranbom-tcp.3.0.0-image
Save and run
agctl export
command to trigger the operation.
- Monitor the export progress.
Run
agctl status
to check the operation status, or the export log files under/user/local/airgap/logs
directory.Note:It may take a long time to export the artifacts. You can run
agctl cancel
command to abort it in the middle. - Verify the completion and locate the generated bundle.
Once the operation is completed, the
agctl status
will report all the Image Repositories asCompleted
Status and the ansible export log under/user/local/airgap/logs/
folder end withfailed=0
The exported bundle is located at
/photon-reps/export-bundle/
, and the ran bom image bundle is generated with named asairgap-ranbom-export-bundle*tar.gz in /photon-reps/export-bundle/ran-bom
folder.