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 version: http://dev.opennebula.org/issues/618 Regards. On 4 May 2011 20:15, Lars Kellogg-Stedman <l...@seas.harvard.edu> wrote: >> 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 <l...@seas.harvard.edu> > Senior Technologist > Harvard University SEAS > Academic and Research Computing (ARC) > -- Daniel Molina, Cloud Technology Engineer/Researcher Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | dmol...@opennebula.org _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org