CloudCenter Package Store
Every CloudCenter deployment requires a CloudCenter Package Store (Package Store). The CloudCenter Package Store is a hosting location for all CloudCenter-supported service binaries and other required information. When you first install the CloudCenter platform using theAppliance Installation, all service binaries are automatically detected and picked up from the package store. You do not need to configure additional steps.
The only time that you need to configure the CloudCenter Package Store is if you do not have Internet access. In this case you can optionally change the repository location identified by the CUSTOM_REPO variable:
- WITH Internet Access: If your cloud region has internet access, the package store automatically syncs service framework binaries. No additional configuration is required.
- WITHOUT Internet Access: If your cloud region does not have internet access, change the repository location using the CUSTOM_REPO variable in the
- If you comment out this line, you must select packages via the Internet.
If you change the default repository (master) to a custom repository, update the CUSTOM_REPO variable with the new location.
CloudCenter Package Store Contents
The package store contains the following service binaries:
- Ubuntu12 APT repo
- Ubuntu14 APT repo
- Centos 6 RPM repo
- Ruby-on-Rails Gems repo
- Binaries related to service lifecycle
Master and Custom References
By default, the repo.cliqrtech.com URL refers and points to the master repository. Subsequently installed repositories become a slave of the master repository and syncs packages from the master repository. Once a slave repository syncs packages from the master repository, it can become a master (referred to as custom repository). At this point, subsequently installed repositories can use the slave-turned-master repository as their master.
After you setup a custom repository, you can make it the master repository. Custom repositories can use any master repository to sync packages. All repositories sync with the master repository periodically to perform the following functions:
- Sync new packages.
- Run scripts to update each repository with the latest changes.
Contact CloudCenter Support for setup and update instructions.
CloudCenter Package Store Deployment Considerations
Be aware of the following CloudCenter Package Store considerations:
The CloudCenter Package Store automatically detects and picks up service binaries (and other information) from repo.cliqrtech.com. In this scenario, this repository contains dependent data and is a required CloudCenter component.Icon
You do not need to access or login to the CloudCenter Package Store. Theautomatically syncs this information.
No additional configuration or access is required if you use the default master repository.
- If you change the default master directory to a local custom directory, you can use one of the following scenarios:
- Continue to sync your local custom repository (Internet connection) with the default master repository.
- Perform a one-time sync (with Internet connection) with the default master repository, export the binaries and other information to a local custom repository, and then switch over to the local custom repository (does not require Internet connection).
Disconnect from the default master repository and manage your own repository connection (does not require Internet connection).Icon
Be aware that incorrect configurations result in un-synced versions of service binaries and may also result in unknown failures.
Access to the CloudCenter Package Store
Access to the CloudCenter Package Store depends on your deployment considerations:
- Default master repository: The package store automatically detects and pick ups service binaries (and other information) from the repo.cliqrtech.com URL points. No additional configuration or access is required.
- Change the default repository: To change the location of the default master repository to a custom repository, contact CloudCenter Support.
- No labels