> 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 the econe-* tools prefer ONE_AUTH over the EC2 variables? This way EC2_SECRET_KEY could be set for eucatools or Elastic Fox, while the econe-* tools could pull their config from wherever ONE_AUTH points. -- Lars Kellogg-Stedman <[email protected]> Senior Technologist Harvard University SEAS Academic and Research Computing (ARC) _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
