Hi Lars,
I think the best solution would be to change the econe client
implementation to use the sha1 password, therefore the EC2_SECRET_KEY
can be used in the same way for the three clients. The priority is CLI
ENV ONE_AUTH
I have opened a ticket regarding this issue to include it in the next
I think the best solution would be to change the econe client
implementation to use the sha1 password, therefore the EC2_SECRET_KEY
can be used in the same way for the three clients. The priority is CLI
ENV ONE_AUTH
Sounds good to me!
--
Lars Kellogg-Stedman l...@seas.harvard.edu
Senior
The econe tools use the ruby URI gem that will take the host part of
the string and will ignore the path.
It is probably a misnomer to call this a URL, then. Perhaps the
documentation should be clear that is really just a hostname.
running the OCCI server and the EC2 server in different
Maybe the problem is related to the previous point. The Signature that
will authenticate the user is generated using the EC2_URL, maybe the
server is ignoring the path section. Would you mind to try starting
the server without path?.
I've been able to get the EC2 service to work using
Would you mind to try specifying:
SSL_SERVER=arc-vm-opennebula.int.seas.harvard.edu:80
instead of
SSL_SERVER=arc-vm-opennebula.int.seas.harvard.edu
Kind regards.
On 4 May 2011 19:14, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
Maybe the problem is related to the previous point. The
Would you mind to try specifying:
SSL_SERVER=arc-vm-opennebula.int.seas.harvard.edu:80
instead of
SSL_SERVER=arc-vm-opennebula.int.seas.harvard.edu
Both euca-describe-images and econe-describe-images fail with this change.
--
Lars Kellogg-Stedman l...@seas.harvard.edu
Senior Technologist
Ok, I think the problem was that the EC2_SECRET_KEY for euca tools is
the sha1 password and in the econe client is the plain password.
On 4 May 2011 19:41, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
Would you mind to try specifying:
SSL_SERVER=arc-vm-opennebula.int.seas.harvard.edu:80
Ok, I think the problem was that the EC2_SECRET_KEY for euca tools is
the sha1 password and in the econe client is the plain password.
Ah, that did it.
The fact the econe-* expects different values from both EcuaTools and
Elastic Fox is somewhat confusing. Do you think it would make sense
for
After successfully getting the OCCI clients working with OpenNebula,
I've tried getting the EC2 interface to work and I've run into a
variety of problems.
(1) The OpenNebula tools don't respect the path in EC2_URL.
If EC2_URL is set to something like http://myserver/ec2/;, the
OpenNebula EC2
