Create a caching HTTP PROXY server on the selected host.
Engage your network security specialist. Your proxy server has requirements unique to your data center network security policy.
For basic information on the Apache HTTPD server, install httpd, using the instructions provided here, and then adding the mod_proxy and mod_cache modules, as stated here.
Activate this proxy server and configure its cache storage location.
Set the firewall settings (if any) to let inbound HTTP access from your cluster nodes to your mirror server, and outbound access to the desired repo sites, including public-repo-1.hortonworks.com.
![[Note]](../common/images/admon/note.png)
Note If you are using EC2, make sure that SELinux is disabled.
Depending on your cluster OS, configure the
yumorzypperclients on all the nodes in your cluster.For RHEL and CentOS:
Note The following description is taken from the CentOS documentation here.
On each cluster node, add the following lines to the /etc/yum.conf file.
(For example, the settings below enable yum to use the proxy server mycache.mydomain.com, connecting to port 3128, with the following credentials yum-user/qwerty.
# proxy server:port number proxy=http://mycache.mydomain.com:3128
# account details for secure yum proxy connections proxy_username=yum-user proxy_password=qwerty
After all nodes have their /etc/yum.conf file updated with appropriate configuration info, you can proceed with the HDP installation just as though the nodes had direct access to the Internet repositories.
If this proxy configuration does not seem to work, try adding a / at the end of the proxy URL. For example:
proxy=http://mycache.mydomain.com:3128/
For SLES:
Configure the zypper clients on all the nodes in your cluster, to use the proxy server.
Consult with your system administrator to do this correctly in your environment.
