From f73b655466092169abac34833fb628fce1fcdebe Mon Sep 17 00:00:00 2001
From: jcduff <jcduff@localhost>
Date: Thu, 23 Oct 2008 14:04:24 +0000
Subject: [PATCH] The commit will bring the following features : - An updated version of the underlying database. BDB JE 3.3 is now used. - Attribute API refactoring providing a better abstraction and offering improved performances. - A new GUI called the Control-Panel to replace the Status-Panel: the specifications for this GUI are available on OpenDS Wiki and contains a link to a mockup. See <https://www.opends.org/wiki/page/ControlPanelUISpecification>. - Some changes in the replication protocol to implement "Assured Replication Mode". The specifications are on OpenDS Wiki at <https://www.opends.org/wiki/page/AssuredMode> and section 7 described some of the replication changes required to support this. Assured Replication is not finished, but the main replication protocol changes to support it are done. As explained by Gilles on an email on the Dev mailing list (http://markmail.org/message/46rgo3meq3vriy4a), with these changes the newer versions of OpenDS may not be able to replicate with OpenDS 1.0 instances. - Support for Service Tags on the platforms where the functionality is available and enabled. Specifications are published at <https://www.opends.org/wiki/page/OpenDSServiceTagEnabled>. For more information on Service Tags see <http://wikis.sun.com/display/ServiceTag/Sun+Service+Tag+FAQ>. - The Admin Connector service. In order to provide agentry of the OpenDS server at any time, a new service has been added, dedicated to the administration, configuration and monitoring of the server. An overview of the Admin Connector service and it's use is available on the OpenDS wiki <https://www.opends.org/wiki/page/ManagingAdministrationTrafficToTheServer> - Updates to the various command line tools to support the Admin Connector service. - Some internal re-architecting of the server to put the foundation of future developments such as virtual directory services. The new NetworkGroups and WorkFlow internal services which have been specified in <https://www.opends.org/wiki/page/BasicOperationRoutingThroughNetworkGroup> are now implemented. - Many bug fixes...
---
opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml | 147 +++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 147 insertions(+), 0 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
index 6d993f5..363c9a9 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
@@ -193,4 +193,151 @@
</ldap:attribute>
</adm:profile>
</adm:property>
+ <adm:property name="assured-type" mandatory="false" advanced="true">
+ <adm:synopsis>
+ Defines the assured mode of the replicated domain.
+ </adm:synopsis>
+ <adm:description>
+ The assured mode can be disable or enabled. When enabled, two sub modes
+ are available: Safe Data or Safe Read modes.
+ </adm:description>
+ <adm:default-behavior>
+ <adm:defined>
+ <adm:value>not-assured</adm:value>
+ </adm:defined>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:enumeration>
+ <adm:value name="not-assured">
+ <adm:synopsis>
+ Updates sent for replication (for being replayed on other LDAP
+ servers of the topology) are sent without waiting for any
+ aknowledgement and the LDAP client call returns immediately.
+ </adm:synopsis>
+ </adm:value>
+ <adm:value name="safe-data">
+ <adm:synopsis>
+ Assured mode is enabled in Safe Data sub mode: updates sent for
+ replication are subject to acknowledgement defined by the
+ assured-sd-level property. After acknowlegement is received, LDAP
+ client call returns.
+ </adm:synopsis>
+ </adm:value>
+ <adm:value name="safe-read">
+ <adm:synopsis>
+ Assured mode is enabled in Safe Read sub mode: updates sent for
+ replication are subject to acknowledgement of LDAP servers of the
+ topology having the same group id than us (defined with
+ assured-sr-group-id property). After acknowlegement is received,
+ LDAP client call returns.
+ </adm:synopsis>
+ </adm:value>
+ </adm:enumeration>
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-assured-type</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
+ <adm:property name="assured-sd-level" mandatory="false" advanced="true">
+ <adm:synopsis>
+ The level of acknowledgment for Safe Data assured sub mode.
+ </adm:synopsis>
+ <adm:description>
+ When assured mode configured in Safe Data mode, this value defines the
+ number of replication servers that should acknowledge the sent update
+ before the LDAP client call can return.
+ </adm:description>
+ <adm:default-behavior>
+ <adm:defined>
+ <adm:value>1</adm:value>
+ </adm:defined>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:integer lower-limit="1" upper-limit="127"></adm:integer>
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-assured-sd-level</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
+ <adm:property name="assured-timeout" mandatory="false" advanced="true">
+ <adm:synopsis>
+ The timeout value when waiting for assured mode acknowledgements.
+ </adm:synopsis>
+ <adm:description>
+ Defines the amount of milliseconds the server will wait for assured
+ acknowledgements (in either Safe Data or Safe Read assured sub modes)
+ before returning anyway the LDAP client call.
+ </adm:description>
+ <adm:default-behavior>
+ <adm:defined>
+ <adm:value>1000ms</adm:value>
+ </adm:defined>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:duration base-unit="ms" lower-limit="1" />
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-assured-timeout</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
+ <adm:property name="group-id" mandatory="false" advanced="true">
+ <adm:synopsis>
+ The group id associated with this replicated domain.
+ </adm:synopsis>
+ <adm:description>
+ This value defines the group id of the replicated domain. The replication
+ system will preferably connect and send updates to replicate to a
+ replication server with the same group id as him.
+ </adm:description>
+ <adm:default-behavior>
+ <adm:defined>
+ <adm:value>1</adm:value>
+ </adm:defined>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:integer lower-limit="1" upper-limit="127"></adm:integer>
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-group-id</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
+ <adm:property name="referrals-url" multi-valued="true" mandatory="false"
+ advanced="true">
+ <adm:synopsis>
+ The URLs other LDAP servers should you to refer to us.
+ </adm:synopsis>
+ <adm:description>
+ URLs used by peer servers of the topology to refer to us through LDAP
+ referrals. If this attribute is not defined, every URLs available to
+ access this server will be used. If defined, only URLs specified here will
+ be used.
+ </adm:description>
+ <adm:default-behavior>
+ <adm:undefined/>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:string>
+ <adm:pattern>
+ <adm:regex>^ldap://.+$</adm:regex>
+ <adm:usage>LDAP URL</adm:usage>
+ <adm:synopsis>
+ A LDAP URL compliant with RFC 2255.
+ </adm:synopsis>
+ </adm:pattern>
+ </adm:string>
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-referrals-url</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
</adm:managed-object>
--
Gitblit v1.10.0