Thanks for the reply Carlos and Javier. I didn't know it would be used by the scheduler. I had assumed that only client side commands would use it. I have responded to the ticket:1257<http://dev.opennebula.org/issues/1257> as well.
-- Shantanu On Apr 26, 2012, at 5:56 AM, Javier Fontan wrote: ONE_AUTH or standard auth file is used in all the executions so the scheduler knows the credentials to connect to oned. On Tue, Apr 24, 2012 at 11:19 PM, Shantanu Pavgi <pa...@uab.edu<mailto:pa...@uab.edu>> wrote: Does OpenNebula need ONE_AUTH file accessible while starting the 'one' daemon for the first time after fresh installation or every time? It seems like it doesn't need ONE_AUTH 'environment variable' for subsequent start commands however it does require that authentication file is present for every 'one start' command. I understand that it uses ONE_AUTH file contents to create administrator account when OpenNebula process is launched for the first time after a fresh install. However I am not following why does it need accessible for subsequent start commands. It doesn't seem to complain if it's contents are changed between two start commands. So does it actually use authentication file for subsequent start commands? Any explanation on how it works will be helpful. -- Thanks, Shantanu _______________________________________________ Users mailing list Users@lists.opennebula.org<mailto:Users@lists.opennebula.org> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org<http://www.OpenNebula.org> | jfon...@opennebula.org<mailto:jfon...@opennebula.org> | @OpenNebula
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
