You're right. Each context configures the connection to a provider, using its endpoint and your credentials. If you need to work with more than one provider at the same time you'll need one context for each.
I. El 17/01/2014 09:00, "Jose" <[email protected]> escribió: > Hi, > First, thanks a lot for your replies, these are very usefull for me. > > A more (last questions, I hope). I think the template is matched a > provider only, e.g. EC2. For example you have a Context for EC2 and a > template, if you want to match a template with another provider (such as > HP) you will need another ComputeServiceContext, is true? > > Thanks again. > Jose > > > El 16/01/2014 15:21, Andrew Phillips escribió: > >> When do you define a template Jclouds searchs and builds a node (fox >>> example a AMI in Amazon) which matchs with the template specification? >>> >> >> From my understanding, it doesn't *build* a "custom" node, it simply >> searches for an existing AMI that matches the requirements that you set in >> the template. >> >> For things like memory size which are based (in EC2) on the instance that >> is instantiated, jclouds will choose an instance type (micro, medium etc.) >> that meets the requirements, if that is possible. >> >> Hope that helps. jclouds EC2 experts will hopefully be able to expand >> on/correct my comments! >> >> ap >> > >
