[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [geclipse-user] using other EC2 api compatible Clouds - URI change
|
Hi Symon,
yes, testing with Eucalyptus is in my todo list but as you noticed the
service endpoints are still hardcoded... We will change that soon.
Cheers, Ariel
> I am a new g-eclipse user and wanted to test it with our local
> Eucalyptus installation (http://eucalyptus.cs.ucsb.edu/) which is API
> compatible with Amazon EC2 and S3. As the URI for EC2 and S3 in the VO
> dialog can not be changed (they are just shown there) i tried to
> modify them in the files:
>
> .metadata/.plugins/eu.geclipse.core/.vos/Eucalyptus/
> eu.geclipse.aws.ec2.service.ec2ServiceCreator/.ec2_service_properties
> .metadata/.plugins/eu.geclipse.core/.vos/Eucalyptus/
> eu.geclipse.aws.s3.service.s3AWSServiceCreator/.s3_service_properties
>
> To the local service addresses where eucalyptus is running. The VO
> dialog now shows the correct internal endpoints
> (http://192.168.64.187:8773/services/Walrus and
> http://192.168.64.187:8773/services/Eucalyptus) Still when i try to
> connect to EC2 or S3 trough the g-eclipse gui i notice outgoing
> connections to *.amazonaws.com and then an authentication error (as my
> keys are for eucalyptus and not amazon).
> i would like to know if there is an other way to change the service-
> URIs or if this is simply not supported by g-eclipse?
>
> greets
> Simon Ostermann
> Distributed and Parallel Systems Group
> Institute of Computer Science, University of Innsbruck
> Technikerstrasse 21a, A-6020 Innsbruck, Austria
