Internal structures warehouse installation yum cm
Creating a Permanent Internal Repository
1, install httpd
yum install httpd
删除/etc/httpd/conf/httpd.conf 里的include
2, download the source files cm
Download the tarball for your OS distribution from the repo-as-tarball archive:
Cloudera Manager 5: https://archive.cloudera.com/cm5/repo-astarball/
CHR 5: https://archive.cloudera.com/cdh5/repo-as-tarball/
Decompression
Unpack the tarball, move the files to the web server directory, and modify filepermissions. For example, you might use the following commands
$ tar xvfz cm5.14.0-centos7.tar.gz
$ sudo mv cm /var/www/html
$ sudo chmod -R ugo+rX /var/www/html/cm
3, configure the client to use repo
Modifying Clients to Use the Internal Repository
Create /etc/yum.repos.d/cloudera-repo.repo files on clusterhosts with the following content, where
$ [cloudera-repo]
$ name=cloudera-repo
$ baseurl=http://<web_server>/cm/5
$ enabled=1
$ gpgcheck=0
4, configuration parcel warehouse
Hosting an Internal Parcel Repository
Configuration httpd
1,Download the parcel and manifest.json files for your OS distribution from:
CDH 5: Impala, Kudu, Spark 1, and Search are included in the CDH parcel.
CDH - https://archive.cloudera.com/cdh5/parcels/
Accumulo - - https://archive.cloudera.com/accumulo-c5/parcels/
GPL Extras - https://archive.cloudera.com/gplextras5/parcels/
You can not do. "
CDS 2 Powered by Apache Spark for CDH 5:
The exact parcel name is dependent on the OS. You can find all the parcels athttps://archive.cloudera.com/spark2/parcels/ .
Cloudera Navigator Key Trustee Server:
Go to the Key Trustee Server download page (http://www.cloudera.com/content/www/enus/downloads/navigator/key-trustee-server.html) . Select Parcels from the Package or Parcel drop-down menu, and click
2,Move the .parcel and manifest.json files to the web server directory, and modify the file permissions. The hosted .sha1 files
are not used by Cloudera Manager when it obtains the parcels from a web server. Instead, it extracts the SHA1 hashes provided in
manifest.json . For example
sudo mkdir -p /var/www/html/cloudera-parcels/cdh5/<cdh5_version>/
sudo mv *.parcel* /var/www/html/cloudera-parcels/cdh5/<cdh5_version>/
sudo mv manifest.json /var/www/html/cloudera-parcels/cdh5/<cdh5_version>/
sudo chmod -R ugo+rX /var/www/html/cloudera-parcels/cdh5/<cdh5_version>/
Replace
http://
anything, your web server may have been configured to not show indexes.
Configuring the Cloudera Manager Server to Use the Parcel URL for Hosted Repositories
In the Remote Parcel Repository URLs list, click the addition symbol to open an additional row.
- Enter the path to the parcel. For example: http://
/ Cdh5 / - Click Save Changes to commit the changes
Configured to use a local parcel warehouse
To use a local parcel repository, complete the following steps:
- Open the Cloudera Manager web UI and navigate to the Parcels page.
- Select Configuration and verify that you have a Local Parcel Repository path set. By default, the directory is /opt/cloudera/parcelrepo .
- Remove any Remote Parcel Repository URLs you are not using, including ones that point to Cloudera archives.
- Add the parcel you want to use to the local parcel repository directory that you specified.
- In the command line, navigate to the local parcel repository directory.
- Create a SHA1 hash for the parcel you added and save it to a file named
.parcel.sha .
For example, the following command generates a SHA1 hash for the parcel CDH-5.14.0-1.cdh5.14.0.p0.24-el7.parcel :
sha1sum CDH-5.14.0-1.cdh5.14.0.p0.24-el7.parcel | awk '{ print $1 }' > CDH-5.14.0-1.cdh5.14.0.p0.24-el7.parcel.sha
Change the ownership of the parcel and hash files to cloudera-scm :
sudo chown cloudera-scm:cloudera-scm *.parcel.*
In the Cloudera Manager web UI, navigate to the Parcels page
- Click Check for New Parcels.
When the new parcel appears, download, distribute, and activate the parcel