A key difference between Satellite 5 and Satellite 6 is in the area of "disconnected" content management. Both versions of Satellite can provision and keep hosts synchronized without direct connection to the internet, but the way they achieve this is slightly different.
2.2.1. Satellite 5 Proxies
Red Hat Satellite Proxy Server is a package-caching mechanism that reduces the bandwidth requirements for Red Hat Satellite and enables custom package deployment. The Satellite Proxy acts as a go-between for client systems and the Satellite Server.
From the client's perspective, there is no difference between a Satellite Proxy and a Satellite . From the Satellite server's perspective, a Satellite Proxy is a special type of Satellite client.
Satellite Proxy servers are a feature of Satellite 5; you cannot use Satellite Proxy servers with Satellite 6. Instead, Satellite 6 introduces the concept of Capsules, which provide much the same functionality.
2.2.2. Satellite 6 Capsules
Satellite 6 deployments use Capsule servers to provide a similar level of functionality for Satellite 6 that Proxy servers provide for Satellite 5.
The first release of Capsule servers, delivered with Satellite 6.0, can provide the following functionality:
Mirror content (Pulp Node). Content can be staged on a Pulp Node before it is used by a host.
Mirror Puppet content (Puppet Master)
Integrate with DHCP, DNS, TFTP, and IPA.
In Satellite 6.0, Capsule servers do not proxy all data. Consequently, managed systems need connectivity up to Satellite 6, or an HTTP Proxy in place to provide a network bridge if required. Further, you cannot tier Capsule servers like you can with Proxy servers. This is illustrated in the following diagram.
Figure 2.3. Comparison of Satellite 5 Proxy and Satellite 6 Capsule Servers