Adding a repository

Add a repository to use for automatically downloading Debian or RPM packages within the DataStax Enterprise repository.

Add a repository to use for automatically downloading DEB or RPM packages within the DataStax Enterprise (DSE) repository. In addition to providing repository 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, provided that DSE packages are available to apt or yum prior to running any LCM jobs.

Prerequisites

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

Procedure

  1. Click Repositories > Add Repository.

    The Add Repository dialog displays.

  2. 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 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 DSE 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.
      1. Enter the Repository URL.
      2. 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.
      3. Clear Use Configured HTTP Proxy to bypass the proxy used to download files from the internet when downloading DSE.
        Note: Select Use Configured HTTP Proxy when using a private repository within the proxy. If a proxy is not defined in any configuration profiles for the cluster topology, this option has no effect.

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

    • Select Manually configure DataStax repo if the repository is configured externally from LCM: Download DSE from a package repository configured externally from LCM. The target nodes are already able to download DSE 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 repository externally from LCM.
  5. For the DataStax repository, using the configured HTTP proxy is enabled by default. 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.
    Repository typeProxy selection
    Access DataStax repo Select Use Configured HTTP Proxy.
    Access private repo Unselect Use Configured HTTP Proxy if your private repository is on the same local area network as your target nodes, and you wish to bypass the proxy when downloading DSE.
    Manually configure DataStax repo The Use Configured HTTP Proxy option is unavailable when manually configuring a repository externally from LCM.
  6. Click Save.
    The newly defined repository credential is listed on the Repositories page along with edit and delete options.

What's next

Define the cluster topology for DSE at the cluster, datacenter, and node levels.