Adding a repository

Add a repository to use for automatically downloading Debian or RPM packages within the DataStax Enterprise repository. In addition to providing repo credentials, you can define custom URLs that point to your own mirror of the DataStax Repository. Manually configuring the DataStax repository so that LCM does not attempt to configure external package repositories is also an option.

Add a repository to use for automatically downloading Debian or RPM packages within the DataStax Enterprise repository. In addition to providing repo credentials, you can define custom URLs that point to your own mirror of the DataStax Repository. Manually configuring the DataStax repository so that LCM does not attempt to configure external package repositories is also an option.

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.

Prerequisites

Optionally configure a proxy for package downloads for targets with limited internet connectivity.

Procedure

  1. Click Repositories > Add Repository.
    The Add Repository dialog appears.

    Configure the repo for downloading DSE in the Add Repository dialog

  2. Required: Enter a unique Name for the repository credential.
  3. Optional: Enter a Comment that describes the repository credential.
  4. Select a Repository option. Click the i (information) icon to view a tooltip for each option:
    • Select Access DataStax repo if using the DataStax Repository for packages (default): Download DataStax Enterprise from the official package repositories hosted at datastax.com.
    • Select Access private repo if your organization has an internal repository for software packages: Download DataStax Enterprise from a local mirror of the official package repositories. LCM automatically configures target nodes to access the local mirror but the mirror itself must be manually created and updated externally from LCM.
      • Enter the Repository URL.
      • Enter the Repository Key URL to retrieve a public key from. A repository key URL is the address of the public key of a package repository. You can download the key and use it to verify that packages downloaded from the repository have not been tampered with.

      Enter the repository URL and its key if downloading from a private repo rather than the DataStax repo

    • Select Manually configure DataStax repo if the repo is configured externally from LCM: Download DataStax Enterprise from a package repository configured externally from LCM. The target nodes are already able to download DataStax Enterprise through their package manager and LCM should not attempt to automatically configure package repositories. This option is useful if DataStax packages have been mirrored to a Red Hat Satellite channel, if a configuration management system other than LCM is used to configure package repositories, or if LCM is not compatible with your repository setup and your organization requires configuring its repo externally from LCM.
  5. For the DataStax repository, using the configured proxy is enabled by default. If you are not using the DataStax repo, the Use Configured HTTP Proxy option is disabled. The proxy option is not applicable when manually configuring a repo externally from LCM. Custom package repositories are commonly located internal to the HTTP proxy. If your custom package repository is external to your proxy, select Use Configured HTTP Proxy to ensure the package manager on your target nodes uses your configured HTTP proxy. For information on configuring Lifecycle Manager to forward requests to your proxy, see configuring a proxy for package downloads.
  6. Required: Enter the Username and Password for accessing the DataStax Repository. Re-enter the password for confirmation.
    The username and password must be specified if authentication is enabled on the repository. The DataStax Repository always has authentication enabled. For the DataStax Repository, the username and password are the DataStax Academy account credentials you created on the registration page. The repository username and password are used when downloading packages (they are not used when fetching the repository public key).
    Note: When configuring credentials in a repository, special characters such as #, $, and so forth are supported, but non-ascii unicode characters are not. If you have further questions, please contact DataStax Support and reference ticket OPSC-8921.
  7. Click Save.
    The newly defined repository credential is listed on the Repositories page along with edit and delete options.

What's next

Edit the cluster in the Clusters workspace to select the repository. The datacenters and nodes inherit the cluster repository.