Thanks Andrew

On 3 December 2013 09:55, Andrew Phillips <[email protected]> wrote:

> Hi Simon
>
>  It seems that the common API is a good starting point (and does sensible
>> things around location and image), but I'd like to pull in a few fields
>> from the vendor specific API. However, I don't really want to call the API
>> twice. In an ideal world I'd like to call the common API and then unwrap
>> the results to get the specific API result data. Is this possible or does
>> the common API simply not contain the data?
>>
>
> From what I know, the data returned by calls to the portable APIs has, for
> most providers, genuinely been transformed/extracted from the data returned
> by the underlying provider (see e.g. [1])
>
> In other words, we're not looking at some kind of "transparent view"
> through which you could trapdoor your way to the underlying data - the
> underlying response has been lost at that point. Hope that explanation
> makes some kind of sense ;-)
>

I suspected, even assumed, that to be the case - but it's worth asking. I'm
afraid I currently find the jClouds code base pretty much impenetrable (I
haven't had a lot of experience with dependency injection) so I couldn't be
sure from what I've ascertained so far. The RunningInstanceToNodeMetadata
code is really useful to help me understand what's going on.

With regard specifically to public/private DNS, if this is an attribute
> offered by a fair number of providers, the best bet might be to open a JIRA
> issue to add that to the standard metadata, or otherwise expose it via the
> portable API. Obviously, that's only one of many potential data points you
> might be after.


I'm currently only spiking the use of jClouds, but will bear that in mind
for the future.


>
>   - First: Is there any way to get the ARN for an instance?
>>
>
> You *can* get the ARN for the IAM instance profile [2], but I'm not aware
> of something to get the ARN of the instance itself. Seems like a good
> candidate for a feature request (or, better still, *pull* request [3] ;-))
> to something like AWSRunningInstance [4].


Fair enough - again, I'm currently at a stage of spiking jClouds to
understand it better, but would happily do some work to get some features
into the code :)


>   - Secondly: I'm doing buildApi(classOf[AWSEC2Client]) on the
>> ContextBuilder to get the vendor specific API - however AWSEC2Client is
>> deprecated. If I use AWSEC2Api as suggested in the JavaDoc then I get a
>> guice exception (No implementation for org.jclouds.aws.ec2.AWSEC2Api was
>> bound) - any thoughts on what I should be doing?
>>
>
> Which version of jclouds are you using? If you're on 1.7.0-SNAPSHOT and
> are still getting the Guice exception trying to use buildApi, please put
> the full error in a Gist or Pastie and respond to this thread.
>

I'm currently using 1.6.3 and will have a look at 1.7.0-SNAPSHOT.


> Hope that helps!
>

Definitely - thanks for taking the time to reply and explain what's going
on.

Simon

Please consider the environment before printing this email.
------------------------------------------------------------------
Visit theguardian.com   

On your mobile, download the Guardian iPhone app theguardian.com/iphone and our 
iPad edition theguardian.com/iPad   
Save up to 33% by subscribing to the Guardian and Observer - choose the papers 
you want and get full digital access.
Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also
be privileged. If you are not the named recipient, please notify
the sender and delete the e-mail and all attachments immediately.
Do not disclose the contents to another person. You may not use
the information for any purpose, or store, or copy, it in any way.
 
Guardian News & Media Limited is not liable for any computer
viruses or other material transmitted with or as part of this
e-mail. You should employ virus checking software.
 
Guardian News & Media Limited
 
A member of Guardian Media Group plc
Registered Office
PO Box 68164
Kings Place
90 York Way
London
N1P 2AP
 
Registered in England Number 908396

--------------------------------------------------------------------------

Reply via email to