Setting up a Harbor repository to synchronize container images
Repository content
The images required for BMC Helix Service Management installation are located in the following repositories in BMC DTR:
BMC Repository | Repository content |
---|---|
bmc | BMC Helix Service Management images. This repository includes all components of BMC Helix Service Management such as AR System server, BMC Helix Innovation Studio, Mid Tier, BMC Helix ITSM: Smart IT, BMC Digital Workplace, BMC Digital Workplace Catalog, and BMC Helix Innovation Suite applications. Important: Each component has a separate repository such as ars, midtier, cmdb, and virtualchat. These repositories contain the images for the respective component, such as the AR System images are located in the ars repository and the Mid Tier images are located in the midtier repository. |
bmc/lp0lz | BMC Helix Platform images. |
Process to access container images from a local Harbor repository
Set up a Harbor repository and synchronize your Harbor repository with BMC DTR by using the access key. The following images shows the actions to synchronize your Harbor repository with BMC DTR.
Before you begin
- Download the following files:
These files contain the list of images that are synchronized from BMC DTR. You can use these files to verify your Harbor repository after you synchronize it with BMC DTR.
- Make sure that you have downloaded the key to access the container images, image_pull_push.sh and image_sync_to_private_registry.sh files from the BMC Electronic Product Distribution (EPD) site.
See Downloading-the-installation-files. - Make sure that you meet the Harbor repository requirements.
Task 1: To create a Harbor registry
In your local system, download the latest version of Harbor by using the following command:
wget https://github.com/goharbor/harbor/releases/download/v2.1.4/harbor-offline-installer-v<version>.tgzExample:
wget https://github.com/goharbor/harbor/releases/download/v2.1.4/harbor-offline-installer-v2.1.4.tgzUnzip the TAR file by using the following command:
tar xvzf harbor-offline-installer*.tgzNavigate to the harbor directory by using the following command:
cd harborCopy the configuration template by using the following command:
cp harbor.yml.tmpl harbor.ymlEdit the harbor.yml file and add the values for the following parameters:
Parameter
Description
hostname
Name of the host where you want to install Harbor.
harbor_admin_password
Password for the Harbor application admin username.
In the harbor.yml file, uncomment the https related config section, and add the values for parameters such as port, certificate, and private_key.
For example:# https related config
https:
# https port for harbor, default is 443
port: 443
# The path of cert and key files for nginx
certificate: /data/cert/dsmlab.bmc.com.crt
private_key: /data/cert/dsmlab.bmc.com.keyRun the following command:
sudo ./install.sh- Verify that you can access the Harbor registry by using the admin username and password to log in.
Task 2: To configure a Harbor registry endpoint
- In the Harbor admin UI, navigate to the Administration menu, and click Registries.
Click NEW ENDPOINT, and specify the following field values:
- Provider—Docker Registry
- Endpoint URL—https://containers.bmc.com
- Access ID—Support user ID that you use to log in to EPD.
- Access Secret—Container image access key specified in the container-token.bmc file that you downloaded from EPD.
The following image shows an example configuration:
- To verify the connection, click TEST CONNECTION.
Click OK.
The configuration is saved and the configuration status is displayed as Healthy as shown in the following image:
- Navigate to the Administration menu, and click Projects.
- Create a new project and specify the project name as bmc.
This project is used to synchronize the container images.
Task 3: To synchronize a Harbor repository with BMC DTR
You must synchronize your Harbor repository with BMC Helix Innovation Suite and BMC Helix Platform services container images in BMC DTR.
- Log in to a Linux system.
- Copy the image_pull_push.sh, image_sync_to_private_registry.sh, 23304006_ITSM_Platform_Images.txt, 23304006_ITSM_SmartApps_Images.txt, 23304006_ITSM_Pipeline_Images.txt, and 23304006_SupportAssistTool_Images.txt files to the system.
- Based on the BMC Helix Platform Common Servicesversion you want to use, copy the 251_Helix_Platform_Images.txt, 244_Helix_Platform_Images.txt, or 243_Helix_Platform_Images.txt file to the system.
- Create a new file named images.txt.
- Synchronize the BMC Helix Service Management platform container images:
- Copy the 23304006_ITSM_Platform_Images.txt to the images.txt file.
Open the image_sync_to_private_registry.sh file and update the following parameter values:
Parameter
Description
SOURCE_REGISTRY_HOST
Specify the value as containers.bmc.com
SOURCE_REGISTRY_USER
Support user ID that you use to login to EPD.
SOURCE_REGISTRY_PASSWORD
The container image access key specified in the container-token.bmc file that you downloaded from EPD.
IMAGE_REGISTRY_HOST
Host name of your local registry.
IMAGE_REGISTRY_USERNAME
Specify the user name to log in to your local registry.
IMAGE_REGISTRY_PASSWORD
Specify the password to log in to your local registry.
IMAGE_REGISTRY_PROJECT
Specify the value as bmc
Convert the images.txt file to UNIX format by using the following command:
dos2unix images.txtRun the image_sync_to_private_registry.sh file by using the following command:
./image_sync_to_private_registry.sh
- Synchronize the smart application, pipeline, BMC Helix Platform services, and Support Assistant tool container images by performing the following steps:
- Copy the file to the images.txt file.
Run the image_sync_to_private_registry.sh file by using the following command:
./image_sync_to_private_registry.sh
To access images from an air-gapped environment
The following image describes the process to access the BMC Helix Innovation Suite platform and application container images from an air-gapped environment:
Perform the following steps to access images from an air-gapped environment:
- Create and configure a local Harbor registry in your network.
- Create and configure a Harbor registry in a demilitarized zone (DMZ).
- Set up a proxy to enable communication between the local Harbor registry in your network and the Harbor registry in a DMZ.
- Synchronize your local Harbor repository in your network with BMC DTR.
- Synchronize your Harbor repository in a DMZ with your local Harbor repository in your network.
Perform the steps in To synchronize a Harbor repository with BMC DTR by modifying the following fields:- Source registry—Name of the DMZ Harbor registry that you configured to synchronize with your local Harbor repository.
- Source resource filter: Name—Path of the image in your local Harbor repository that you want to synchronize to your DMZ Harbor repository.
Where to go from here
Next task | Proceed with preparing a database based on the database that you want to use: |
---|---|
Back to process | If you are finished preparing the database, return to the appropriate installation, update, or upgrade process: |