Here is some information about vSphere that I thought would be good to share with the world. As with everything else this is just a drop in the bucket. I’m currently working on putting together some upgrade videos and screenshots so take a look back and hopefully I will have them done by the end of the week.
Here is some interesting information about vSpehere and what it supports keep in mind these are just some notes I jotted down:
Read more…
Share on Facebook
Categories: ESX 4, VI4, VMware, vSphere Tags: ESX, ESX4, green technology, installtion, vCenter, vCenter_Upgrade, VI4, Virtual Center, virtualization, VMware, vsphere
Some are speculating that next Tuesday VMware is going to announce the release of VMware vSphere which is what essentially is Virtual Infrastructure 4.0 which would include ESX 4.0. I can’t say what VMware is going to do but over the next few weeks I will be publishing information on vSphere as well as some instructional videos. For now I have some teasers for you.
Here is a screen shot of the alarms available in vSphere. A you can see they have expanded the alarm feature from what was available in VI3.
Read more…
Share on Facebook
Categories: VMware Tags: Automated Deployment, ESX, ESXi, green technology, HA, installtion, vCenter, Virtual Center, virtualization, VMware, vsphere
I have been asked this question a few times so I thought it would be wise to post an article on it. When deploying an automated build script with the kickstart and/or installation files located on http, ftp, or nfs there are network configuration dependencies that you need to be aware of.
The ESX installer is a modified version of anaconda which is the same installer used for RedHat and a few or Linux variants. Anaconda is what allows for the kickstart portion of the automated build script. Anaconda itself has some limitations as far as what it supports.
Read more…
Share on Facebook
I had a conversation with some colleagues of mine about ESX local disk partitioning and some interesting questions were raised.
How many are creating local vmfs storage on their ESX servers?
How many actually use that local vmfs storage?
Typically it is frowned upon to store vm’s on local vmfs because you loose the advances features of ESX such as vMotion, DRS, and HA. So if you don’t run vm’s from the local vmfs, then why create it? Creating this local datastore promotes it’s use just by being there. If you’re short on SAN space and need to deploy a vm and can’t wait for the SAN admins to present you more storage, what do you do? I’m sure more frequently than not you deploy to the local storage to fill the need for the vm. I’m also sure that those at least 20% of the time those vm’s continue to live there.
Read more…
Share on Facebook
