You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Toni Menzel (JIRA)" <ji...@apache.org> on 2009/10/12 10:28:31 UTC
[jira] Created: (ACE-53) Ability to send configuration data to
gateways
Ability to send configuration data to gateways
----------------------------------------------
Key: ACE-53
URL: https://issues.apache.org/jira/browse/ACE-53
Project: Ace
Issue Type: New Feature
Reporter: Toni Menzel
In terms of the "passive gateway" scenario, it would be good if the server could serve configuration data (in standard format at best, ConfigAdmin Spec) to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-53) Ability to send configuration data to
gateways
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764600#action_12764600 ]
Toni Menzel commented on ACE-53:
--------------------------------
So basically there is a new rest endpoint on the server that publishes configuration data upon request.
in the client side, there should be a new Configurator that issues such a request and applies the result to the local Config Admin service.
> Ability to send configuration data to gateways
> ----------------------------------------------
>
> Key: ACE-53
> URL: https://issues.apache.org/jira/browse/ACE-53
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
>
> In terms of the "passive gateway" scenario, it would be good if the server could serve configuration data (in standard format at best, ConfigAdmin Spec) to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-53) Ability to send configuration data to
gateways
Posted by "Toni Menzel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764607#action_12764607 ]
Toni Menzel commented on ACE-53:
--------------------------------
Looks like Auto Config from the compendium spec is the name of the game.
> Ability to send configuration data to gateways
> ----------------------------------------------
>
> Key: ACE-53
> URL: https://issues.apache.org/jira/browse/ACE-53
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
>
> In terms of the "passive gateway" scenario, it would be good if the server could serve configuration data (in standard format at best, ConfigAdmin Spec) to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-53) Ability to send configuration data to
gateways
Posted by "Angelo van der Sijpt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765198#action_12765198 ]
Angelo van der Sijpt commented on ACE-53:
-----------------------------------------
Auto Config is indeed a mechanism for pushing configurations, and most of the components are actually ready for this:
- The RepositoryAdmin has a mechanism for handling artifacts that should be handled by resource processors, which includes AutoConf configuration files; see ConfigurationHelper
- There is an implementation of a resource processor for AutoConf data, see AutoConfResourceProcessor
In fact (I'd have to check that), I'm pretty sure that we can put our resource processor and some AutoConf data in the OBR, put the ConfligurationHelper bundle on the server, and start deploying configuration data!
> Ability to send configuration data to gateways
> ----------------------------------------------
>
> Key: ACE-53
> URL: https://issues.apache.org/jira/browse/ACE-53
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
>
> In terms of the "passive gateway" scenario, it would be good if the server could serve configuration data (in standard format at best, ConfigAdmin Spec) to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ACE-53) Ability to send configuration data to
gateways
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766912#action_12766912 ]
Marcel Offermans commented on ACE-53:
-------------------------------------
Like Angelo says, this should already work.
Just to explain a bit further, the Deployment Admin specification that we use allows you to add support for new file types to deploy. Auto Config is such a new file type and this one is actually part of the OSGi spec already. Such new file types can be supported by resource processors, which get installed alongside these new resources. The resource processors allow local handling of these files, and at te same time are part of the "transaction" within Deployment Admin, so if anything goes wrong, the whole transaction gets rolled back.
> Ability to send configuration data to gateways
> ----------------------------------------------
>
> Key: ACE-53
> URL: https://issues.apache.org/jira/browse/ACE-53
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
>
> In terms of the "passive gateway" scenario, it would be good if the server could serve configuration data (in standard format at best, ConfigAdmin Spec) to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.