You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Ioannis Canellos (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/05 15:52:51 UTC
[jira] [Resolved] (CAMEL-4622) Jclouds compute endpoints should
leverage predicates instead of requiring id.
[ https://issues.apache.org/jira/browse/CAMEL-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ioannis Canellos resolved CAMEL-4622.
-------------------------------------
Resolution: Fixed
> Jclouds compute endpoints should leverage predicates instead of requiring id.
> -----------------------------------------------------------------------------
>
> Key: CAMEL-4622
> URL: https://issues.apache.org/jira/browse/CAMEL-4622
> Project: Camel
> Issue Type: Improvement
> Components: camel-jclouds
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: 2.9.0
>
>
> Currently there is no way to define a node range for the available operations. Some examples:
> i) List nodes operation, will list all nodes regardless of state, group, image id etc.
> ii) Run script operation will require the id of a single node to run a script.
> iii) Destroy node will require the id of a single node to destroy.
> In would be really useful, if we could use predicates for filtering. Such fundtionality would allow us for example to list all nodes that are in RUNNING state and/or belong to group X.
> This will also allow to uses "multiple nodes" for operations that till now apply to a single node, which will have to be identified using its node id.
--
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