Andrew - not sure if this would help, I attached a file with sample REST
calls to Terremark API current version. It includes URLs and required
headers. I replaced all identifiers, tokens, keys with hidden. Let me
know if I can help with any other info.
Thanks for that. I've attached the
I actually met with Victor from Terremark recently - he was expressing an
interest in working on getting ecloud back working again, but I haven't
heard anything from him since I met him on Thursday...
A.
On Wed, Sep 4, 2013 at 3:53 PM, Andrew Phillips andr...@apache.org wrote:
Andrew - not
The following is the request/response wire trace retrieved from the cloud
explorer. This might give some info on the URL and structure of req/resp
being used.
Thanks for that. It does indeed, though, look very much like an
explorer-specific URL, rather than the regular login URL for the API.
Just to follow up: according to the vCloud Express (of which jclouds
assumes eCloud is a flavour) documentation [1], the structure of the
login request is as follows:
POST https://{Terremark URI}/login
As per the output of your Gist (thanks for that!), on of the available
Terremark URIs
Hi Andrew ,
I wanted to quickly try the three options you provided. However the url's
https://services.enterprisecloud.terremark.com/api/v0.8b-ext2.8;
https://services.enterprisecloud.terremark.com/api/version; are returning
a 404 error.
I talked to the terremark support regarding login
Ah, interesting. Thanks for digging this up. Without having read the
documentation in any great detail, I would guess that eCloud now has
its own API that differs from the vCloud Express API - certainly, the
response to the /versions call is quite different now.
If this turns out to be
Andrew, I might have difficulty getting the account access because of
privacy concerns.
The following is the request/response wire trace retrieved from the cloud
explorer. This might give some info on the URL and structure of req/resp
being used.
Request URL:
Thanks Andrew. Does this mean there will have to be some rework to the
current terremark eCloud support in jclouds ? The reason I am asking is
because If the login url has changed, there is a lot of chance for other
calls to fail too ?
It's hard to say - it depends on what the problem turns out
Has the api specification on Terremark deprecated the one used on jclouds ?
Also the stack trace shows that the code path for this login is through
vCloudExpress implementation. Is this intentional ?
Yes, this is intentional: the ECloud compute service is just a slight
adapter layer on top of
Yes Andrew, I get the same error.
However, there is a cloud explorer link where I can try out the api's
directly
https://services.enterprisecloud.terremark.com/cloudapi/explorer
On this page, on the top right hand side, there is a settings link. This
launches a authentication dialog. On this
10 matches
Mail list logo
