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: https://services.enterprisecloud.terremark.com/cloudapi/explorer/ApiExplorer/ValidateCredentials Request Method: POST Status Code: HTTP/1.1 200 OK Request Headers 22:47:58.000 X-Requested-With:XMLHttpRequestUser-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Firefox/21.0Referer: https://services.enterprisecloud.terremark.com/cloudapi/explorerPragma:no-cacheHost:services.enterprisecloud.terremark.comContent-Type:application/json; charset=UTF-8Content-Length:183Connection:keep-aliveCache-Control:no-cacheAccept-Language:en-US,en;q=0.5Accept-Encoding:gzip, deflateAccept:*/* Request Body {"AuthenticationType":"basic","Username":"myusername","Password":"password","PublicKey":"","PrivateKey":"","HashAlgorithm":"SHA1","Version":"2013-02-01","IsSpec":false} Response Headers Pragma:no-cacheExpires:-1Date:Sat, 03 Aug 2013 05:47:59 GMTContent-Type:application/json; charset=utf-8Content-Length:167Cache-Control:no-cache, must-revalidate,proxy-revalidate Response Body {"IsValid":true,"UserName":"myusername","LastName":"lName","FirstName":"fName","OrganizationName":"org","IsSpec":false,"Version":"2013-02-01"} Rgds Jai On Thu, Aug 1, 2013 at 11:55 AM, Jai M <jaiganes...@gmail.com> wrote: > Thanks Andrew for the input. I will try to run the compute-basics example > and let you know. I will also work on trying to get a test account for this > purpose. > > Thanks > Jai > > > On Thu, Aug 1, 2013 at 11:37 AM, Andrew Phillips <andr...@apache.org>wrote: > >> 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 to be. It >> could be as simple as changing the endpoint in the context. >> >> In order to help us figure out what's going on, could you run the >> compute-basics example [1] against eCloud? I suspect the result will be the >> same, but then we can use that as a shared test case. >> >> As regards priority, once we establish this as a bug we'll first need to >> create a JIRA issue for this and see if someone from the community picks it >> up. Obviously, any contribution your organization can make - ideally a pull >> request, but a test account would be useful, too, will help. >> >> ap >> >> [1] https://github.com/jclouds/**jclouds-examples/tree/master/** >> compute-basics<https://github.com/jclouds/jclouds-examples/tree/master/compute-basics> >> > >
