Hi Michael, You are very right. What I tend to do is set the oneadmin home folder to /vmfs/volumes. Let me know if this works for you and I'll add the suggestion to the documentation.
Regards, -Tino -- Constantino Vázquez Blanco, MSc Project Engineer OpenNebula - The Open-Source Solution for Data Center Virtualization www.OpenNebula.org | @tinova79 | @OpenNebula On Tue, May 15, 2012 at 10:23 AM, Michael Rebstock <[email protected]> wrote: > Hello ONE-Community, > > > > these days I’m trying out Open Nebula 2.4 within our Organization. We’re > using ESXi 5.0.0 on our host systems. > > > > There is major problem in using Open Nebula along with ESXi host systems: > > In the installation guide for VMware driver > (http://opennebula.org/documentation:rel3.4:evmwareg) is written: > > “Add oneadmin's front-end account public key (FE → > $HOME/.ssh/id_{rsa,dsa}.pub) to the ESX oneadmin account authorized_keys > (ESX → $HOME/.ssh/authorized_keys).” > > > > I did it as described and it worked fine until I rebooted the host system. > After that, the ssh connection from the front end to the host required a > password again. The problem is, that the ESXi host deletes all “not > original” files that were created since the last reboot. > > There exists a workaround to make files consistent on ESXi but this leads to > loosing of guarantee and support from VMware which is no option for our > organization. > > > > Is this problem already known? And does there exist any (other) solution on > this issue? > > > > Best Regards > > Michael > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
