You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2010/05/22 19:47:19 UTC
[jira] Created: (DIRSERVER-1508) Add an extended operation to
perform operations on config schema dynamically
Add an extended operation to perform operations on config schema dynamically
----------------------------------------------------------------------------
Key: DIRSERVER-1508
URL: https://issues.apache.org/jira/browse/DIRSERVER-1508
Project: Directory ApacheDS
Issue Type: New Feature
Components: ldap
Reporter: Kiran Ayyagari
Assignee: Kiran Ayyagari
Fix For: 2.0.0-RC1
>From version 2.0.0 onwards the configuration of ApacheDS will be stored in DIT under ou=config partition (no more server.xml !)
Currently any changes made to the config partition require a restart to take affect, it would be cool to have an extended operation to activate
most of the configuration options on the fly.
A few examples of such kind of operations
1. Add/Remove partitions, indexes
2. Start/Stop replication with peers
The exteded operation's inputs are
a. The DN of the entry
b. Enum constant representing the operation type e.x START, STOP etc..
The operation's response should contain a meaningful message describing the result of the performed operation in addition to any relevant result code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1508) Add an extended operation to
perform operations on config schema dynamically
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari updated DIRSERVER-1508:
--------------------------------------
Description:
>From version 2.0.0 onwards the configuration of ApacheDS will be stored in DIT under ou=config partition (no more server.xml !)
Currently any changes made to the config partition require a restart to take affect, it would be cool to have an extended operation to activate
most of the configuration options on the fly.
A few examples of such kind of operations
1. Add/Remove partitions, indexes
2. Start/Stop replication with peers
The exteded operation's inputs are
a. The DN of the entry
b. Enum constant representing the operation type e.x START, STOP etc..
The operation's response should contain a meaningful message describing the result of the performed operation in addition to any relevant result code
was:
>From version 2.0.0 onwards the configuration of ApacheDS will be stored in DIT under ou=config partition (no more server.xml !)
Currently any changes made to the config partition require a restart to take affect, it would be cool to have an extended operation to activate
most of the configuration options on the fly.
A few examples of such kind of operations
1. Add/Remove partitions, indexes
2. Start/Stop replication with peers
The exteded operation's inputs are
a. The DN of the entry
b. Enum constant representing the operation type e.x START, STOP etc..
The operation's response should contain a meaningful message describing the result of the performed operation in addition to any relevant result code
Fix Version/s: (was: 2.0.0-RC1)
2.1.1
No time to do it now, postponing.
> Add an extended operation to perform operations on config schema dynamically
> ----------------------------------------------------------------------------
>
> Key: DIRSERVER-1508
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1508
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: ldap
> Reporter: Kiran Ayyagari
> Assignee: Kiran Ayyagari
> Fix For: 2.1.1
>
>
> From version 2.0.0 onwards the configuration of ApacheDS will be stored in DIT under ou=config partition (no more server.xml !)
> Currently any changes made to the config partition require a restart to take affect, it would be cool to have an extended operation to activate
> most of the configuration options on the fly.
> A few examples of such kind of operations
> 1. Add/Remove partitions, indexes
> 2. Start/Stop replication with peers
> The exteded operation's inputs are
> a. The DN of the entry
> b. Enum constant representing the operation type e.x START, STOP etc..
>
> The operation's response should contain a meaningful message describing the result of the performed operation in addition to any relevant result code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.