On Fri, 2016-01-08 at 15:40 +0000, Mayberry, Alexander wrote: > William, we plan to have RH Engineers come on site to help with the > planning/deployment of RHDS. I'm planning to use RHEL7 and whatever > the latest RHDS version is, unless someone tells me of some reason > why an older version would be better suited. Actually, I wanted to ensure you were planning to move to RHEL7 : The version of 389-ds in RHEL7 should support the SSL features I discussed that are key to your concerns. > > I need to get my head around what actually needs to happen before > they arrive, and hopefully minimize the time it takes for them to > explain things to me. > If it makes sense to wait for this event, and ensure the new RHDS > systems are up to spec, and leave the existing systems alone until > they are decommissioned, that's a very clean and manageable way to > proceed in my view. I'll let the RH engineers / consultants advise you on this, but I would assume (and hope) the upgrade path they suggest is: You have you existing Masters A and B. You create new Masters C and D. You put all 4 into replication group. Apply the SSL settings discussed here to C and D. Then you would put C and D into production alongside A and B. Wait and test. Then remove A and B from production for a period of time before you decommision them. > > Thanks for your insight, and info, I appreciate it. > Any time! -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
-- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
