Repositories Overview 

Repositories allow automatically downloading packages from a repository without repeatedly entering your credentials during a DataStax Enterprise install job.

Repositories allow automatically downloading packages from a repository without repeatedly entering your credentials during a DataStax Enterprise install job. Repositories use user-defined credentials to access and download all required packages for installing DataStax Enterprise from the DataStax Repository or from an internal private repository maintained by your organization. Add a repository to use for automatically downloading Debian or RPM packages within the DataStax Enterprise repository. In addition to repo credentials, you can define custom URLs that point to your own internal mirror of the DataStax Repository. If your organization has an internal mirror of the DataStax Repository, you could also create a DataStax Repo as an alternative repository resource to your private repo. Unless your organization has multiple local mirrors of the DataStax package repository, you probably only need to define one repository.

Optionally, configure a proxy to expedite package downloads for targets with limited internet connectivity, which is especially useful for offline installs accessing a custom repository. For a detailed example, see the Knowledge Base article.

Repositories are applied at the cluster level only in the Clusters workspace. Datacenters and nodes inherit the repository from the cluster. If you require a different repository per datacenter, you can read more about a potential workaround in this Knowledge Base article.
Note: The data (cluster topology models, configuration profiles, credentials, repositories, job history, and so forth) for Lifecycle Manager is stored in the lcm.db database. Your organization is responsible for backing up the lcm.db database. You must also configure failover to mirror the lcm.db.

lcm.db 

The location of the Lifecycle Manager database lcm.db depends on the type of installation:

  • Package installations: /var/lib/opscenter/lcm.db
  • Tarball installations: install_location/lcm.db
Note: The data (cluster topology models, configuration profiles, credentials, repositories, job history, and so forth) for Lifecycle Manager is stored in the lcm.db database. Your organization is responsible for backing up the database. You must also configure failover to mirror the lcm.db.