Red Hat Bugzilla – Bug 1264037
Capsules now encapsulates the whole traffic with hosts
Last modified: 2016-04-27 20:07:59 EDT
Section Number and Name:
2.2.2. Satellite 6 Capsules
Describe the issue:
"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."
This is not true any more since 6.1.x
Suggestions for improvement:
Remove the sentence altogether, and adapt the following one, which starts with "Further...".
Alternatively you might want to hint at the fact that the communication between Satellite and Capsule needs more port under 6.x than under 5.x.
Assigning to David for review.
If I understand correctly, we should have something like this:
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.
Rewrite the above to just:
"You cannot tier Capsule Servers in Satellite 6 the way you can with Proxy Servers in Satellite 5."
To be honest I'm not sure how much value the diagram provides, beyond illustrating the lack of tier support.
Also, do we need to update the list of functionality that Capsules provide:
- 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
thanks a lot.
Emailed Eric to bump this along.
(In reply to David O'Brien from comment #2)
Sorry, David, I didn't realise that the question was aimed at me...
There were 3 points in your comment:
- rewrite to ... => fine with me!
- interest of the diagram => well, it doesn't disturb, and looks neat, I would keep it.
- Update the list of functionality => I'm nitpicking but I would suggest following improvements:
> - Mirror _repository_ content (Pulp Node) and serve it to the hosts.
(not all customers might understand what a Pulp node is)
> - Mirror Puppet content and act as Puppet Master and CA
> - Integrate with DHCP, DNS, TFTP, and Kerberos realms (IPA / IdM)
(DHCP, DNS and TFTP are protocols, whereas IPA is a project; IdM is the product name and is used by the user guide instead of IPA)
I'm neither a native speaker nor a technical writer, feel free to take my comments as what they are: suggestions!
Thanks and sorry again for the delay in responding, Eric
This content is now live on the Customer Portal.