Define repositories
Lifecycle Manager (LCM) uses the repository model to configure target nodes to download DataStax Enterprise (DSE) software packages using apt or yum.
LCM supports provisioning DSE on target nodes that do not have direct, unfettered internet access with which to download software. Proxies, private-repositories, and manually configured repositories are all important tools in such environments.
You must download DSE and OpsCenter packages from IBM Fix Central to your own local mirror or self-hosted repository that you manually configure and update outside of LCM.
Repositories are only applied at the cluster level in the Clusters workspace. Datacenters and nodes inherit the repository from the cluster.
Workaround for datacenter specific repositories
Datacenter-specific repositories aren’t supported in OpsCenter 6.0.
If you need the nodes in one datacenter to download from a different repository, you can simulate datacenter-specific repositories using proxies and local cache packages.
-
Outside of LCM, deploy caching https proxies at each datacenter site.
-
Optional: Outside of LCM, deploy a single package mirror that is network accessible to the proxies at each datacenter. Alternately, ensure that each proxy is able to reach both the official
datastax.comrepositories and an official package repository for the operating system running on your intended target nodes. -
Add a repository to LCM, and select Use Configured HTTP Proxy.
-
Add a
config-profilefor each datacenter. For each datacenter andconfig-profile, configure the proxy in the Package Proxy setting.
Now, the target nodes download DEB or RPM packages through the caching proxy.
If you need to provision a target with limited internet access, see Use LCM for online and offline DSE deployments.
To continue with repository configuration, see Add a repository.
