Re: ESXi host, local disk
SSH is disabled by default on the ESXi host and is 'unsupported' by Vmware. I've noticed this behavior as well, where the command succeeds but it is not reflected in the return code. You can enable SSH by going to the ESXi console. If you go the NFS route make sure to use the address of the NFS on the exporting computer rather than address of the mount of the ESXi host or you will run into the same problems if SSH is not enabled. The idea that the VCL developers have expressed is that using an NFS setup distributes the workload among multiple drives which improves performance. On Sat, May 29, 2010 at 2:21 PM, My LinuxHAList wrote: > Replying to my own thread: > > >> (2) Any updates from an old issue: > >> > http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html > >> The target is ESXi 3.5 host. > > To get familiarity of the software, I've been using ESXi 3.5 local > disk storage; so I specify the datastore to be ESXi's IP:/PATH. > > Hence, during image capture phase, the ssh commands seem to be going > off to the ESXi host. > The command seems to succeed all the time; however the return code is > mostly 255 and sometimes 0. > It's weird because I'm certain that commands being sent were > successful; I reproduced it manually the weird behavior > ( similar to > http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html > ) > > I take that this is an sshd oddity on ESXi host. > > I saw entries of "localdisk" or "networkdisk" on vmprofile. Not sure > how they are used. > > Is the setup of ESXi with local disk considered to be a supported option ? > If so, how would I get around the sshd oddity for the ESXi's > IP:/DATASTOREPATH issues during image capture ? Or I should do things > differently for localdisk. > > I'll switch to NFS so that I can move forward. > > I wish to get some understanding on potentially what I did wrong or > what I did was simply an "unsupported" setup. > > Thanks again. >
Re: VCL 2.2 with VMware Server 2.x or ESXi 4.x
xCAT 2.5 which vcl can be based off automatically configures ESXi 4 with ssh enabled. This is for running diskless installs. On May 29, 2010, at 10:14 AM, Andy Kurth wrote: It would be pretty easy to implement but requiring SSH poses some legal/licensing questions, along with some technical problems. There's a thread that discusses whether or not it violates the VMware EULA to enable and use SSH, with no definitive answer: http://communities.vmware.com/message/1418182 Even if the EULA would not be violated by VCL managing "free" ESXi via SSH, I'd be wary to devote much development time or make this the recommended configuration because (a) the EULA may be changed in the future to disallow it and (b) there is nothing preventing VMware from taking away the SSH "Tech Support Mode" in the future, and (c) there is no way to automate the enabling of SSH so every host will have to be manually configured. That said, I have enabled SSH on my ESXi test hosts and have found it very useful. Instructions on how to enable SSH: http://kb.vmware.com/kb/1003677 Once enabled, the VCL code could do everything it needs by running vim-cmd and other commands. This would be easy to implement. The new code is very modular and contains 2 utility modules, VIX_API.pm and vSphere_SDK.pm. These implement the functions to control the VMs such as register, power_on, etc. We would need to implement another utility module to perform the same functions via ESXi/SSH. There will be some technical problems that will need to be addressed. For example, you can create an authorized_keys file on the ESXi host to login using an identity key but this file gets deleted for some reason every time you reboot the ESXi host. -Andy Ryan Johnson wrote: I was going through some of the posts on the vmware forums. Apparently one could ssh into the ESXi host itself and use the vimsh wrapper to administer virtual machines. Not sure how hard this would be to implement. http://communities.vmware.com/thread/203414
ESXi host, local disk
Replying to my own thread: >> (2) Any updates from an old issue: >>http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html >> The target is ESXi 3.5 host. To get familiarity of the software, I've been using ESXi 3.5 local disk storage; so I specify the datastore to be ESXi's IP:/PATH. Hence, during image capture phase, the ssh commands seem to be going off to the ESXi host. The command seems to succeed all the time; however the return code is mostly 255 and sometimes 0. It's weird because I'm certain that commands being sent were successful; I reproduced it manually the weird behavior ( similar to http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html ) I take that this is an sshd oddity on ESXi host. I saw entries of "localdisk" or "networkdisk" on vmprofile. Not sure how they are used. Is the setup of ESXi with local disk considered to be a supported option ? If so, how would I get around the sshd oddity for the ESXi's IP:/DATASTOREPATH issues during image capture ? Or I should do things differently for localdisk. I'll switch to NFS so that I can move forward. I wish to get some understanding on potentially what I did wrong or what I did was simply an "unsupported" setup. Thanks again.
Re: New Reservation Query
Thank you all, the issue was the image groups and computer groups weren't mapped together and I have fixed it now. I am able to make a reservation now but the issue which I am now facing is that when I try to connect to the remote machine through the credentials got from the web front end, the login fails because of user authentication issues. however using the same user id and password I am able to login through the VM console. . Both the ssh daemons are running and node is accessible.I suspect some configuration issues with the ssh. any help or suggestions?? Thanks and Regards Vinay Venkatesh. On Thu, May 27, 2010 at 4:41 PM, Andy Kurth wrote: > Also, there may be some other things to check in these previous posts: > http://markmail.org/search/set:arkurth/vcl+%22not+currently+available%22 > > -Andy > > > Vinay Venkatesh wrote: > >> Hello, >> >> I am facing few issues when trying to make a new reservation. even though >> I >> have computers available loaded with the desired image, I still get "There >> are currently no computers available that can run the application you >> selected". Is there any selection /setting which I am missing. >> >> Thanks and Regards >> Vinay Venkatesh. >> >>
Re: VCL 2.2 with VMware Server 2.x or ESXi 4.x
It would be pretty easy to implement but requiring SSH poses some legal/licensing questions, along with some technical problems. There's a thread that discusses whether or not it violates the VMware EULA to enable and use SSH, with no definitive answer: http://communities.vmware.com/message/1418182 Even if the EULA would not be violated by VCL managing "free" ESXi via SSH, I'd be wary to devote much development time or make this the recommended configuration because (a) the EULA may be changed in the future to disallow it and (b) there is nothing preventing VMware from taking away the SSH "Tech Support Mode" in the future, and (c) there is no way to automate the enabling of SSH so every host will have to be manually configured. That said, I have enabled SSH on my ESXi test hosts and have found it very useful. Instructions on how to enable SSH: http://kb.vmware.com/kb/1003677 Once enabled, the VCL code could do everything it needs by running vim-cmd and other commands. This would be easy to implement. The new code is very modular and contains 2 utility modules, VIX_API.pm and vSphere_SDK.pm. These implement the functions to control the VMs such as register, power_on, etc. We would need to implement another utility module to perform the same functions via ESXi/SSH. There will be some technical problems that will need to be addressed. For example, you can create an authorized_keys file on the ESXi host to login using an identity key but this file gets deleted for some reason every time you reboot the ESXi host. -Andy Ryan Johnson wrote: I was going through some of the posts on the vmware forums. Apparently one could ssh into the ESXi host itself and use the vimsh wrapper to administer virtual machines. Not sure how hard this would be to implement. http://communities.vmware.com/thread/203414
