orcharhino Proxy Guide
We refer to orcharhino and orcharhino proxies throughout the documentation.
These terms describe the machines running your orcharhino (FQDN e.g.
An orcharhino proxy allows you to deliver content and manage hosts in additional networks. It may be configured to either mirror synced content from your orcharhino or pass-through content using Squid from your orcharhino to its hosts. This is called smart proxy functionality and includes DNS, DHCP, TFTP and CA capabilities.
The term smart proxy is used throughout the management UI. It describes the smart proxy functionality present on both your orcharhino as well as any attached orcharhino proxies.
When looking at the upstream documentation for Foreman and Katello, you might come across the terms smart proxy, Foreman proxy, and Katello proxy. These terms are used ambiguously to describe the software component or the attached host with smart proxy functionality in different variations. By contrast, Red Hat named their Foreman downstream product Satellite and any attached smart proxies Capsules.
Additionally, there are HTTP proxies as a way of relaying network traffic from one machine to another. They are often part of more advanced internal network architectures.
orcharhino proxies are autonomous orcharhino components that run on separate hosts from the orcharhino, interacting with it using a client-server model. The orcharhino installation will always come bundled with integrated smart proxy functionality, such that it can function as the sole orcharhino proxy for most use cases.
Separate orcharhino proxies are only needed in scenarios where orcharhino manages an IT infrastructure that spans across multiple networks. In such scenarios, orcharhino will require an orcharhino proxy in every network with a compute resource provider other than the network that the orcharhino is in.
There is a fully-featured orcharhino proxy installation guide to help you attach an orcharhino proxy to your orcharhino to manage hosts in additional networks. It also describes its feature set and usage scenario in more detail.
Other relevant documentation can found in the infrastructure menu section:
This usage guide is a stub. We are hoping to expand it into a full fledged usage guide in a future release of this documentation. In the meantime, we apologize for any inconvenience.