Repositories

Manages provider’s repository for database servers and clusters. You can have three types of repositories when deploying a database server/cluster using ClusterControl:

1. Use Vendor Repositories
   • Provision software by setting up and using the database vendor’s preferred software repository. ClusterControl will always install the latest version of what is provided by the database vendor repository.
2. Do Not Setup Vendor Repositories
   • Provision software by using the pre-existing software repository already set up on the nodes. The user has to set up the software repository manually on each database node and ClusterControl will use this repository for deployment. This is good if the database nodes are running without internet connections.
3. Use Mirrored Repositories (Create new repository)
   • Create and mirror the current database vendor’s repository and then deploy using the local mirrored repository.
   • This allows you to “freeze” the current versions of the software packages used to provision a database cluster for a specific vendor and you can later use that mirrored repository to provide the same set of versions when adding more nodes or deploying other clusters.
   • ClusterControl sets up the mirrored repository under {wwwroot}/cmon-repos/, which is accessible via HTTP at http://{clusterControl_host}/cmon-repos/.

Only Local Mirrored Repository will be listed and manageable here.

• Remove Repositories
  • Remove the selected repository.
• Filter by cluster type
  • Filter the repository list by cluster type.

For reference purposes, the following is an example of yum definition if Local Mirrored Repository is configured on the database nodes:

$ cat /etc/yum.repos.d/clustercontrol-percona-5.6-yum-el7.repo
[percona-5.6-yum-el7]
name = percona-5.6-yum-el7
baseurl = http://10.0.0.10/cmon-repos/percona-5.6-yum-el7
enabled = 1
gpgcheck = 0
gpgkey = http://10.0.0.10/cmon-repos/percona-5.6-yum-el7/localrepo-gpg-pubkey.asc