RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 855327 - Describe recommended replication topologies
Summary: Describe recommended replication topologies
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-07 11:56 UTC by Dmitri Pal
Modified: 2014-07-29 20:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-29 20:25:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Topology diagram with 12 servers (80.72 KB, image/png)
2012-09-07 11:56 UTC, Dmitri Pal
no flags Details
Topology diagram with 16 servers (69.48 KB, image/png)
2012-09-07 11:56 UTC, Dmitri Pal
no flags Details

Description Dmitri Pal 2012-09-07 11:56:08 UTC
Created attachment 610701 [details]
Topology diagram with 12 servers

Describe what we recommend as replication typologies.

Here are several principals that need to be followed:

1) Put IPA servers into each of your main data centers.
If you have a small branch office you might put a replica there to or it can be connected using SSSD caching capabilities.
2) We recommend at least 2 servers per data center
3) We do not recommend more than 4 servers per data center
4) Each server should have replication agreements with at least two other servers so that if one of the servers goes down there are no orphans.
5) The recommended number of the replication agreements per server is 2-3. 4 is maximum recommended
6) The rules above lead to "cell based" configuration when a set of servers form a cell of more tightly replicated servers and then the cells are loosely coupled to each other.

The attached diagrams show the potential configuration. They are just an example that illustrates the rules and principles described above.

Comment 1 Dmitri Pal 2012-09-07 11:56:42 UTC
Created attachment 610702 [details]
Topology diagram with 16 servers

Comment 4 Deon Ballard 2014-07-29 20:23:10 UTC
Mass closure. These bugs were live in RHEL 6.5.


Note You need to log in before you can comment on or make changes to this bug.