You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/09/21 21:15:14 UTC
[jira] [Created] (KARAF-888) Add a service layer for ConfigAdmin
Add a service layer for ConfigAdmin
-----------------------------------
Key: KARAF-888
URL: https://issues.apache.org/jira/browse/KARAF-888
Project: Karaf
Issue Type: Improvement
Components: karaf-config
Reporter: Jean-Baptiste Onofré
Fix For: 3.0.0
Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
I propose two improvements around ConfigAdmin:
- we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
- the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-888) Add a Karaf Config Service
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112404#comment-13112404 ]
Jean-Baptiste Onofré commented on KARAF-888:
--------------------------------------------
I think I wasn't clear in my previous comment.
The Karaf Config Service is only responsible of the ConfigAdmin storage, and it implements the PersistenceManager ConfigAdmin interface.
> Add a Karaf Config Service
> --------------------------
>
> Key: KARAF-888
> URL: https://issues.apache.org/jira/browse/KARAF-888
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-888) Add a Karaf Config Service
Posted by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated KARAF-888:
--------------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
I think we can delay this to 3.1
> Add a Karaf Config Service
> --------------------------
>
> Key: KARAF-888
> URL: https://issues.apache.org/jira/browse/KARAF-888
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-888) Add a Karaf Config Service
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved KARAF-888.
---------------------------------------
Resolution: Fixed
I think this is resolved with the new config admin and file install versions that do the persistence themselves.
> Add a Karaf Config Service
> --------------------------
>
> Key: KARAF-888
> URL: https://issues.apache.org/jira/browse/KARAF-888
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-888) Add a Karaf Config Service
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-888:
---------------------------------------
Summary: Add a Karaf Config Service (was: Add a service layer for ConfigAdmin)
> Add a Karaf Config Service
> --------------------------
>
> Key: KARAF-888
> URL: https://issues.apache.org/jira/browse/KARAF-888
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-888) Add a Karaf Config Service
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber updated KARAF-888:
---------------------------------
Fix Version/s: (was: 3.1.0)
3.0.0
> Add a Karaf Config Service
> --------------------------
>
> Key: KARAF-888
> URL: https://issues.apache.org/jira/browse/KARAF-888
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira