Hi,
thanks, it is clear now. I changed it to store the initial retrieval
results from a listNodes to a local variable and then used this one in
the for loop for accessing the information (i was trying to compare the
template IDs of all the nodes), so it solved the performance issue of
multiple EC2 calls.
BR,
George
On 2/12/2014 8:35 PM, Andrew Phillips wrote:
Hi George
I have created a service context that gets the compute service object
in a method and then use the various methods of compute service or
metadata to get the relevant information.
By that, I assume you mean you used the ContextBuilder to create a
context? If so, this only contains the *connection* information (it's
conceptually pretty similar to creating a database connection with a
database driver).
The actual calls are not made then - they occur when you get one of
the views or provider-specific APIs from the context and invoke
methods on them.
See [1] for a short introduction to some core jclouds concepts. Hope
that helps!
ap
[1] https://wiki.apache.org/jclouds/Core%20Concepts
--
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
