This process prepares the updated repository.
Check to see if you have a
conf.save
directory for Ambari server and agents. If you do, move them to a back-up location:mv /etc/ambari-server/conf.save/ /etc/ambari-server/conf.save.bak
mv /etc/ambari-agent/conf.save/ /etc/ambari-agent/conf.save.bak
Get the new Ambari bits. Use
wget
to fetch the repository file and replace the old repository file with the new repository file on every host.Important Check your current directory before you download the new repository file to make sure that there are no previous versions of the file. If you do not, and a previous version exists, the new download is saved with a numeric extension such as
ambari.repo.1
. Make sure that the version you copy is the new version.For RHEL/CentOS/Oracle Linux 5
wget http://public-repo-1.hortonworks.com/ambari/centos5/1.x/updates/1.6.0/ambari.repo cp ambari.repo /etc/yum.repos.d/ambari.repo
For RHEL/CentOS/Oracle Linux 6
wget http://public-repo-1.hortonworks.com/ambari/centos6/1.x/updates/1.6.0/ambari.repo cp ambari.repo /etc/yum.repos.d/ambari.repo
For SLES 11
wget http://public-repo-1.hortonworks.com/ambari/suse11/1.x/updates/1.6.0/ambari.repo cp ambari.repo /etc/zypp/repos.d/ambari.repo
Note If your cluster does not have access to the Internet, you need to set up a local repository with this data before you continue. See Configure the Local Repositories for more information.