This is the documentation for Cloudera Manager 5.1.x. Documentation for other versions is available at Cloudera Documentation.

Creating and Using a Package Repository

This topic describes how to create a package repository and then how to direct hosts in your environment to use that repository. To create a repository, you simply put the repo files you want to host in one directory. Then publish the resulting repository on a website.

Continue reading:

Install a Web Server
Download Tarball and Publish Repository Files
Modify Clients to Find Repository

Install a Web Server

The repository is typically hosted using HTTP on a host inside your network. If you already have a web server in your organization, you can move the repository directory, which will include both the RPMs and the repodata/ subdirectory, to some a location hosted by the web server. An easy web server to install is the Apache HTTPD. If you are able to use an existing web server, then note the URL and skip to Download Tarball and Publish Repository Files.

Installing Apache HTTPD

You may need to respond to some prompts to confirm you want to complete the installation.

OS	Command
RHEL	[root@localhost yum.repos.d]$ yum install httpd
SLES	[root@localhost zypp]$ zypper install httpd
Ubuntu or Debian	[root@localhost apt]$ apt-get install httpd

Starting Apache HTTPD

OS	Command
RHEL	[root@localhost tmp]$ service httpd start Starting httpd: [ OK ]
SLES	[root@localhost tmp]$ service apache2 start Starting httpd: [ OK ]
Ubuntu or Debian	[root@localhost tmp]$ service apache2 start Starting httpd: [ OK ]

Download Tarball and Publish Repository Files

Download the tarball for your OS distribution from the repo as tarball archive.
Unpack the tarball, move the files to the web server directory, and modify file permissions. For example, you might use the following commands:
```
[root@localhost tmp]$ gunzip cm5.0.0-centos6.tar.gz
[root@localhost tmp]$ tar xvf cm5.0.0-centos6.tar
[root@localhost tmp]$ mv cm /var/www/html
[root@localhost tmp]$ chmod -R ugo+rX /var/www/html/cm
```
After moving files and changing permissions, visit http://<hostname>:80/cm to verify that you see an index of files. Apache may have been configured to not show indexes, which is also acceptable.

Modify Clients to Find Repository

Having established the repository, modify the clients so they find the repository.

OS	Command
RHEL	Create files on client systems with the following information and format, where `hostname` is the name of the web server you created in Install a Web Server: [myrepo] name=myrepo baseurl=http://`hostname`/cm/5 enabled=1 gpgcheck=0 See `man yum.conf` for more details. Put that file into `/etc/yum.repos.d/myrepo.repo` on all of your hosts to enable them to find the packages that you are hosting.
SLES	Use the `zypper` utility to update client system repo information by issuing the following command: $ zypper addrepo http://hostname/cm alias
Ubuntu or Debian	Add a new `list` file to `/etc/apt/sources.list.d/` on client systems. For example, you might create the file `/etc/apt/sources.list.d/my-private-cloudera-repo.list`. In that file, create an entry to your newly created repository. For example: $ cat /etc/apt/sources.list.d/my-private-cloudera-repo.list deb http://hostname/cm cloudera After adding your `.list` file, ensure `apt-get` uses the latest information by issuing the following command: $ sudo apt-get update

Command

RHEL

Create files on client systems with the following information and format, where hostname is the name of the web server you created in Install a Web Server:

[myrepo]
name=myrepo
baseurl=http://hostname/cm/5
enabled=1
gpgcheck=0

See man yum.conf for more details. Put that file into /etc/yum.repos.d/myrepo.repo on all of your hosts to enable them to find the packages that you are hosting.

SLES

Use the zypper utility to update client system repo information by issuing the following command:

$ zypper addrepo http://hostname/cm alias

Ubuntu or Debian

Add a new list file to /etc/apt/sources.list.d/ on client systems. For example, you might create the file /etc/apt/sources.list.d/my-private-cloudera-repo.list. In that file, create an entry to your newly created repository. For example:

$ cat /etc/apt/sources.list.d/my-private-cloudera-repo.list
deb http://hostname/cm cloudera

After adding your .list file, ensure apt-get uses the latest information by issuing the following command:

$ sudo apt-get update

After completing these steps, you have established the environment necessary to install a previous version of Cloudera Manager or install Cloudera Manager to hosts that are not connected to the Internet. Proceed with the installation process, being sure to target the newly created repository with your package management tool.

Page generated September 3, 2015.