Repositories Overview

LCM uses the repository model to configure target nodes to download DataStax Enterprise software packages using apt or yum.

LCM uses the repository model to configure target nodes to download DataStax Enterprise software packages using apt or yum.

The following options are available for configuring a repository:
  • Access DataStax repo: DataStax provides official package repositories hosting the DataStax Enterprise software packages for all supported platforms. To access the official repository, all target nodes must have outbound internet access to datastax.com, either directly or through an https proxy. Credentials for a DataStax Academy account are required to download software from the official repository.
  • Access private repo: Some customers choose to locally mirror the official DataStax repository and host the DataStax Enterprise software packages in their own apt- or yum-compatible repository. This scenario is common in cases where outbound internet access is restricted, or where policy requires software to be installed from locally managed sources. Mirrors of the DataStax Enterprise software packages must be created and updated externally from LCM, but LCM is able to configure target nodes to access such a pre-existing repository. This type of repository supports custom URLs for the repository root and for the package signing key. When an http/https proxy is configured for outbound network access, it may optionally be bypassed for this type of repository, as private repositories are often on the same LAN as target nodes. An optional username and password may be provided, and whether those fields are necessary depends on how the customer-managed repository mirror is configured.
  • Manually configured repo: Manually configuring the DataStax repository so that LCM does not attempt to configure package repositories is also an option. Organizations that use a configuration management system other than LCM to configure package repos, those that require configuring a repo externally from LCM, or if their DataStax packages are mirrored to a Red Hat Satellite channel can operate their repos independently of LCM.

LCM supports provisioning to 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. For a complete discussion of provisioning to targets with limited internet access, 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
Important: 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.