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/NetworkGroupConfiguration.xml | 74 ++++++++++++++++++++++++++++++++++++-
1 files changed, 72 insertions(+), 2 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/NetworkGroupConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/NetworkGroupConfiguration.xml
index 91d77fe..35c5eff 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/NetworkGroupConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/NetworkGroupConfiguration.xml
@@ -42,6 +42,55 @@
<ldap:superior>top</ldap:superior>
</ldap:object-class>
</adm:profile>
+
+ <adm:relation name="network-group-criteria"
+ managed-object-name="network-group-criteria">
+ <adm:synopsis>
+ Specifies the set of criteria associated to this network group.
+ </adm:synopsis>
+ <adm:description>
+ A client connection can belong to a <adm:user-friendly-name /> only
+ if it matches all the criteria defined for this
+ <adm:user-friendly-name />.
+ </adm:description>
+ <adm:one-to-zero-or-one />
+ <adm:profile name="ldap">
+ <ldap:rdn-sequence>cn=Criteria</ldap:rdn-sequence>
+ </adm:profile>
+ </adm:relation>
+
+ <adm:relation name="network-group-resource-limits"
+ managed-object-name="network-group-resource-limits">
+ <adm:synopsis>
+ Specifies the set of resource limits enforced by this
+ <adm:user-friendly-name />.
+ </adm:synopsis>
+ <adm:description>
+ All client connections belonging to a <adm:user-friendly-name />
+ must comply with the resource limits policy.
+ </adm:description>
+ <adm:one-to-zero-or-one />
+ <adm:profile name="ldap">
+ <ldap:rdn-sequence>cn=ResourceLimits</ldap:rdn-sequence>
+ </adm:profile>
+ </adm:relation>
+
+ <adm:relation name="network-group-request-filtering-policy"
+ managed-object-name="network-group-request-filtering-policy">
+ <adm:synopsis>
+ Specifies the request filtering policy enforced by this
+ <adm:user-friendly-name />.
+ </adm:synopsis>
+ <adm:description>
+ All client connections belonging to a <adm:user-friendly-name />
+ must comply with the request filtering policy.
+ </adm:description>
+ <adm:one-to-zero-or-one />
+ <adm:profile name="ldap">
+ <ldap:rdn-sequence>cn=RequestFilteringPolicy</ldap:rdn-sequence>
+ </adm:profile>
+ </adm:relation>
+
<adm:property name="enabled" mandatory="true">
<adm:synopsis>
Indicates whether the
@@ -82,11 +131,32 @@
</ldap:attribute>
</adm:profile>
</adm:property>
- <adm:property name="workflow" mandatory="true" read-only="true"
- multi-valued="true">
+ <adm:property name="priority" mandatory="true">
+ <adm:synopsis>
+ Specifies the order in which the network groups are evaluated.
+ </adm:synopsis>
+ <adm:description>
+ A client connection is first compared against network group with
+ priority 1. If the client connection does not match the network group
+ criteria, the client connection is compared against network group
+ with priority 2 etc...
+ </adm:description>
+ <adm:syntax>
+ <adm:integer lower-limit="0"/>
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-priority</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
+ <adm:property name="workflow" multi-valued="true">
<adm:synopsis>
Identifies the workflows in the network group.
</adm:synopsis>
+ <adm:default-behavior>
+ <adm:undefined />
+ </adm:default-behavior>
<adm:syntax>
<adm:aggregation relation-name="workflow" parent-path="/">
<adm:constraint>
--
Gitblit v1.10.0