Create a caching HTTP PROXY server on the selected host.
It is beyond the scope of this document to show how to set up an HTTP PROXY server, given the many variations that may be required, depending on your data center’s network security policy. If you choose to use the Apache HTTPD server, it starts by installing
httpd
, using the instructions provided here, and then adding themod_proxy
andmod_cache modules
, as stated here.Please engage your network security specialists to correctly set up the proxy server.
Activate this proxy server and configure its cache storage location.
Ensure that the firewall settings (if any) allow 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 If you are using EC2, make sure that SELinux is disabled.
Depending on your cluster OS, configure the yum clients on all the nodes in your cluster.
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.
(As an example, the settings below will 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
Once 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/