Bug 488876

Summary:	Review Chapter 5: Setting up multi-master replication
Product:	[Retired] freeIPA	Reporter:	David O'Brien <daobrien>
Component:	Documentation	Assignee:	David O'Brien <daobrien>
Status:	CLOSED DUPLICATE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	benl, dpal, jgalipea, rcritten
Target Milestone:	v2 release	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_IPA/1.1/html/Installation_and_Deployment_Guide/chap-Installation_and_Deployment_Guide-Setting_up_Multi_Master_Replication.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	646209 (view as bug list)		Environment:
Last Closed:	2010-11-29 00:48:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	431020, 431022, 489811, 646209, 646217

Description David O'Brien 2009-03-06 02:05:22 UTC

Description of problem:
What's new and changed for v2.0?
Anything missed from 1.1?
Improvements?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David O'Brien 2009-03-08 21:55:20 UTC

Version set to 1.1 by  mistake. Resetting to 2.0

Comment 3 Rob Crittenden 2010-09-14 22:06:01 UTC

The only significant change to replication in v2 is that some management can be done without the DM password.

If the user is in the replicaadmin rolegroup then they can list current agreements and delete agreements.

They cannot add, init or cause a resync.

It is but a small step forwards.

If no ticket is available then it will fall back to prompting for the DM password like in v1.

Comment 4 David O'Brien 2010-11-29 00:48:12 UTC


*** This bug has been marked as a duplicate of bug 646209 ***