Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBenjamin Chardi
2016-07-11 07:33:44 UTC
Description of problem:
We need a confirmation from Red Hat side that the Satellite HA architecture that we have implemented our Satellite 6.1.9 deployment is compliant with Satellite HA reference architecture and also we need to be sure that it will be compliant in future releases.
Our satellite infra for the moment is composed of one satellite central server + 3 capsules with RHEL6 and RHEL7 channels + some custom content (~ 250G on /var/lib/pulp). For the moment we have ~50 clients attached to it but in the next year we will reach more that 30K clients attached.
We are using a F5 load balancer in order to provide an Active-Active HA for the following Capsules service to the clients: puppetmaster, rpm repo (pulp), access to puppet CA and access to tftpboot services. We have written some documentation about the details in how we have do it:
[1] https://mojo.redhat.com/docs/DOC-997168 (just chapter CAPSULES HA, ACTIVE – ACTIVE LOAD BALANCE CLUSTER)
[2] https://mojo.redhat.com/docs/DOC-1059147
[3] https://mojo.redhat.com/people/sgarciam/blog/2015/09/24/pulp-certificate-with-cnames-alt-names-for-satellite-6-capsules
[1] and [2] explains how to do it, but for generating LB ssl certificates we have used [3] as explained in [2] instead of modifying the satellite installation scripts as described in [1].
So taking into account all this information, we need the confirmation that this Satellite HA architecture is (and will be) fully soported by Red Hat.
We are not doing any kind of HA for satellite server itself
Version-Release number of selected component (if applicable):
Satellite 6.1.9
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: