Hi Gary,
Prior to the reboot, the VCL site should go into maintenance mode to
prevent a user from creating a reservation while this reboot procedure
happens. You'll want to write a script that enumerates the VMs running on
the VM host prior to shutdown, then bring those VMs back up after reboot.
Once the VM host is back online, bring VCL out of maintenance mode.
I know this would be pretty straightforward with ESXi, but I'm not sure
about VMWare Server 2. I just did a quick Google search and found this:
http://www.cyberciti.biz/tips/start-stop-vmware-virtualization-vms-command.html
Regards,
Mike
--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com
On Thu, Jun 14, 2012 at 6:22 PM, Gary Trail tra...@rpi.edu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Mike.
you are correct - rebooting during pulling image would be avoided if
at all possible.
To elaborate a bit. Our objective is to run an unattended regular
(weekly/monthly) vmware server restart/reboot without impacting the
integrity of VCL. Of course, users would be disconnected when their
guest vm shuts down but, upon restart vmware server (version 2) would
restart any previously running vm's and users could just re-connect
using the same IP address, user name etc and the VCL infrastructure
would resume in its pre-reboot state and reservations would time out s
if nothing happened.
In our pilot project, the VCL management node and vmware server2
services are running on the same physical hardware while the VCL
database and VCL front-end components are on two different hardware
hosts. VM images currently reside on DAS disks on the
management/vmware node hardware.
Is this all possible/reasonable?
How are others accomplishing this?
Thanks
Gary
Mike Haudenschild wrote the following on 6/14/2012 5:02 PM:
Hi Gary,
I'm assuming you do NOT mean shutting down the VM host while VCL
is actively pulling an image... That would surely be bad.
I think that the reservation should still remain active in the
database. Shut down the client image cleanly, then bring down the
management node and front end cleanly, and reboot the VM host.
Bring up the management node and front end. You'll have to
manually power on your image VM on via the vSphere Client, but as
long as the reservation hasn't expired it should be okay. Should be
the same credentials to login to the image VM, too.
Regards, Mike
On Thursday, June 14, 2012, Gary Trail wrote:
Quick question -
We're in the middle of a pilot VCL installation (3 machines -
front-end, database and management node (VCL management and vmware
server on one management node).
What will happen to any in process image updates if the vmware
server reboots? Will the image updates survive the reboot?
Thanks Gary
Gary Trail Rensselaer Hartford Graduate Center 860-548-7869
tra...@rpi.edu javascript:;
- --
Gary Trail
Director of Network Services
Rensselaer Hartford Graduate Center
860-548-7869
tra...@rpi.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJP2mQyAAoJENG9onuHOfZFsEMIAKbQV0w9qxLraoiFkl6gIc0F
sGmZ5a0QaZIXEUyryrlXgxuvJkp+/4XEHDNi8UVXAFam0gNo8jlbEKcTh84Ix6uk
9p+Llmw2RTiQtqGXGF/cufkIDnw8lZB4KaU8zjjfdNnAcW6x1YmLOlfzMBVbxxzH
gC9uU5UR0fZvwTxDM2HKwNsmg3Zugu7VhbxqXgDyFBNwS2AR2175pZT0PFP+wEAw
1bNM77/8TCM/fsmHfAqejgEFWxqmwlxK3M+nf/vRCPc2KhWL9/mkTF4zKMy06iY8
MHXylps30IGXHdH7nwsX/pZoc3NGxXN2vHcmhDsKXYASnYG2ofaPBxL9t4SSh30=
=+CP6
-END PGP SIGNATURE-
