Describe the issue:
Table 1.3 and 1.4 appears to mix the use of "Server" and "Satellite Server".
Suggestions for improvement:
Considering the fact that we have up to 3 end points.
Client (Server), Capsule (Server), Satellite (Server), I'd suggest we stuck to listening them as Client, Capsule and Satellite, and avoid the user of "Server".
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Thank you for your feedback! I will be confirming whether "Satellite Server" vs "Server" as an Initiator and End Point are similar things with the developer. Once we have confirmed it, we'll definitely update you on what our action is.
Your suggestion will be implemented possibly in 6.1 or in a post-6.1 async. Thank you for the suggestion. We will update this ticket once we implement the changes.
(In reply to Douglas Furlong from comment #0)
> Title: Prerequisites
> Describe the issue:
> Table 1.3 and 1.4 appears to mix the use of "Server" and "Satellite Server".
Table 1.3, "Advanced Firewall Considerations with a Red Hat Satellite Server", in Sat 6.0 Docs is here:
Table 1.4, "Advanced Firewall Considerations without a Red Hat Satellite Capsule Server", in Sat 6.0 Docs is here:
In Sat 6.1, these table have been replaced by tables representing the direction of the packet flow.
The point is still valid, there is confusing use in general of the word "Server" in Satellite terminology.
We discussed this with the Technical Marketing Manager and we have been advised we should use "Satellite Server" and "Capsule Server" the first time in a chapter, but later occurrences can just be "Satellite" and "Capsule".
We hope you find the soon-to-be-published 6.2 Beta Guides more consistent.
This content is now live on the Customer Portal.