Add a repository
Add a repository to automatically download DEB or RPM packages to install DataStax Enterprise (DSE).
If you set up repositories before December 2025 that used the public DataStax downloads repositories, you must create a mirror repository that downloads packages from Fix Central, as explained on this page.
Prerequisites
-
An active DSE and OpsCenter license.
-
An IBMid.
-
If you are an existing IBM customer with an IBMid, you can continue to use your established account.
-
If you don’t have an IBMid, you can create one.
-
If your company uses Enterprise Federation (EF) for authentication with corporate credentials, see the EF documentation.
-
-
Downloaded DSE and OpsCenter packages from Fix Central.
-
A local repository mirror that hosts the DSE and OpsCenter packages.
Configure a repository
To configure a repository, you must first set up a local repository mirror that hosts the DSE and OpsCenter packages.
See the following resources for more information about setting up repositories:
-
Apache
-
nginx
-
Red Hat Satellite
-
Debian APT
See Apache in the Red Hat documentation for more information.
See nginx in the Red Hat documentation for more information.
See Uploading content to custom RPM repositories in the Red Hat Satellite documentation for more information.
-
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 private repo
-
Manually configure DataStax repo
Select Access private repo to use your own internal repository for software packages.
You must download DSE and OpsCenter packages from IBM Fix Central and set up your own local repository mirror before configuring this option.
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. You must ensure that the mirror is compatible with Apt or Yum, depending on the operating system of your target nodes.
If you select this option, 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 download DSE through their package manager, and LCM doesn’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 configures 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.
