Local Repo Appliance 

Overview

The Workload Manager local repo appliance is based on CentOS 7 and has an Apache web service and a version of the package store and bundle store preinstalled. You would deploy this appliance to your target VM-based cloud if either of these two conditions is true: 

  • Your workload VMs cannot access the Cisco-hosted package store and bundle store.
  • Your want to reduce the latency associated with downloading files from the package store or bundle store.

There are four tasks associated with the installing and using the local repo appliance:

  • Deploy the appliance appropriate to your cloud type
  • Configure the appliance using the repo wizard script
  • Configure the Cloud Settings section of the associated region with the appliance's package store and bundle store urls. 
  • Periodically update the bundle store

If using an unhardened version of CentOS 7 for the local repo appliance is not permitted or desired in your environment, you can build your own local repo appliance on your own Linux OS by following the instructions in Local Package Store (Conditional) and Local Bundle Store (Conditional).


Deploy the Appliance

The local repo appliance comes in different form factors corresponding the following cloud types:

Cloud TypeAppliance Form Factor
vCenterOVA file downloaded from http://software.cisco.com
OpenStackqcow2 file downloaded from http://software.cisco.com
AzureRMzip file downloaded from http://software.cisco.com
AWSprivate image shared with your AWS account upon your request
GCPprivate image shared with your GCP account upon your request

Deploy the appliance per the convention for your cloud region. Note the VM's IP address. 

Configure the Appliance

  1. Once your appliance is powered on, establish an SSH session to it using IP address you noted above.
  2. From the appliance command prompt, run the repo configuration shell script at /usr/bin/repo_config_wizard.sh. This invokes a text UI. Dismissing the welcome message displays the configuration menu. The menu has three choices: Proxy_Settings, Repo_Syncup, and Exit.
  3. Selecting Proxy_Setting brings up a new menu allowing you to specify a SOCKS proxy URL. Enter the address of your proxy server if you have one.
  4. Selecting Repo_Syncup displays a confirmation message. Agreeing to the confirmation message causes the script to sync the local package store the latest package store at repo.cliqrtech.com.

The local repo appliance is configured with a cron job that will automatically attempt to sync with the package store at http://repo.cliqrtech.com every day at midnight. It is therefore necessary that the local repo appliance have at least occasional internet access.

Configure Cloud Settings

In order for your workload VMs to access the local repo appliance, the URLs of the appliance's package store and bundle store must be entered into the appropriate fields in the Cloud Settings section of the corresponding region. For a vCenter cloud, this section is at the top of the Details tab (see figure below). For all other clouds this section is displayed in the Regions tab after selecting the appropriate region.

Click the Edit Cloud Settings link in the upper right to bring up the Cloud Settings dialog box as shown below. Note that the fields in this dialog box will vary based on the cloud type.

For the Agent Custom Repository field enter the address of the local repo appliance:

http://<local _repo_ip_address>

For the Agent Bundle Store field enter the Agent Custom Repository URL followed by "/" and the directory name of the bundle store. To get the directory name of the bundle store, connect to the appliance's console, navigate to the http root directory, which is /repo/,  and perform a directory listing. Look for directory with a name in the following format: 

cloudcenter-<release_version>

The bundle store directory will be found here in a subdirectory named "bundle". In this case, the Agent Custom Repository URL you should use would be in the format:

http://<local _repo_ip_address>/cloudcenter-<release_version>/bundle

If you later download a newer bundle store to the appliance, and place it in a new directory, you will need to update the Agent Bundle URL for this region with a URL that points to the new directory.

Periodically Update the Bundle Store

The local repo appliance automatically syncs the package store with repo.cliqrtech.com. However the bundle store contents on the appliance must be updated manually. You would do this whenever a new version of the bundle store is posted on software.cisco.com which is typically every minor software release cycle. It is recommended that you create a new directory for the new bundle store under /repo/ and name that directory using the a format that includes the release number, for example: release-<release_number>.

After creating the new directory, download the bundle store corresponding to your cloud type to the new directory. Workload Manager has bundle stores for these cloud types: AzureRM, OpenStack, vCenter. These bundle stores are listed at software.cisco.com using the following naming convention: <cloud_type>-cc-bundle_artifacts.zip.

After downloading the bundle store zip file, unzip the contents and delete the original zip file.

Make sure to update the Agent Bundle Store URL field in the Cloud Settings dialog box as explained above.


  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved