You need to set up a local repository, update the version repository base URLs, and edit the repository configuration file.

As a first step, you must set up a local repository for Ambari and HDP. For more information, see set up a local repository . In case the public repository (http://public-repo-1.hortonworks.com) is not available anymore you can get the files from the official archive: https://archive.cloudera.com

A case-study of setting up local repositories: case study for setting up local repository.

When the local repository is created, update the version repository base urls in Ambari. For more information, see update the version repository base urls.

Finally, edit the repository configuration file to use this new local repository. For more information, see edit the repository configuration file.

Updating Ambari repo files

Some services depend on components that are installed from the Ambari repository. It is not updated automatically. Also, Package Manager displays an error about the unavailable repository URL when you update the package lists. Cloudera recommends you to manually update the URLs located at /etc/yum.repos.d/ambari.repo on all hosts (including server host).

Updating HDP repo files

When the cluster settings for the HDP repository URL is updated, repository files on hosts are not immediately regenerated. The files are re-generated when you add a new component or service. But an inaccessible repository URL causes the Package Manager to display an error about the unavailable repository URL when you update the package lists. Cloudera recommends you to manually update the URLs in the HDP repository files (for example, /etc/yum.repos.d/ambari-hdp-1.repo) on all agent hosts.