Add a repository
Add a repository to automatically download DEB or RPM packages from the DataStax Enterprise (DSE) repository.
You must provide repository credentials. Optionally, you can provide custom URLs for your own mirror of the DataStax repository.
Additionally, you can manually configure the DataStax repository to prevent LCM from attempting to configure external package repositories. However, this requires that the DSE packages are available to Apt or Yum before running any LCM jobs.
-
In LCM, select Repositories, and then click Add Repository.
-
Enter a unique Name for your repository credential.
-
Optional: Enter a Comment that describes the repository credential.
-
For Repository, select the desired option:
-
Access DataStax repo (default)
-
Access private repo
-
Manually configure DataStax repo
Select Access DataStax repo to use the DataStax Repository for packages, and download DSE from the official DataStax-hosted package repositories.
All target nodes must have outbound internet access to the DataStax domain, either directly or through an HTTPS proxy.
Leave the Use Configured HTTP Proxy option selected to use the default HTTP proxy configuration that is automatically enabled or a proxy configuration set in the nodes' configuration profiles.
Select Access private repo to use your own internal repository for software packages, and download DSE from a local mirror of the official package repositories.
This scenario is common in cases where outbound internet access is restricted, or where policy requires software to be installed from locally-managed sources.
LCM automatically configures target nodes to access the local mirror, but you must manually create and update the mirror and its software packages outside of LCM. The mirror must be compatible with Apt or Yum, depending on the operating system of your target nodes.
If you select this option, you must also do the following:
-
Enter the Repository URL and the Repository Key URL.
The repository key URL is the address of the package repository’s public key. You can download the key and use it to verify that packages downloaded from the repository haven’t been tampered with.
-
If your private repository is on the same local area network as your target nodes, you can clear the Use Configured HTTP Proxy option to bypass the mirror’s proxy when downloading DSE.
Otherwise, select Use Configured HTTP Proxy to ensure the package manager on your target nodes uses the HTTP proxy configuration given in their configuration profiles. For information on configuring Lifecycle Manager to forward requests to your proxy, see configuring a proxy for package downloads.
If there are no proxies defined in any of the configuration profiles in your cluster topology, then this option has no effect.
Select Manually configure DataStax repo to use a repository that is configured externally from LCM, and download DSE from a package repository configured externally from LCM.
The target nodes can download DSE through their package manager, and LCM shouldn’t attempt to automatically configure package repositories.
This option is useful in the following circumstances:
-
DataStax packages are mirrored to a Red Hat Satellite channel.
-
A configuration management system other than LCM is used to configure package repositories.
-
LCM isn’t compatible with your repository setup.
-
Your organization requires configuring its repository externally from LCM.
If you select the manual repo option, then the Use Configured HTTP Proxy option is unavailable.
-
-
Click Save.
After you configure repositories, define the cluster topology for DSE at the cluster, datacenter, and node levels.
