VMware vSphere 5 Memory Management and Monitoring diagram
Concepts and best practices in Resource Pools
If like me you use iSCSI then you will likely spend a bit of time setting up your Path Selection Polices to suit your specific needs, so it was interesting to note the following.
When you do uninstall and remove PernixData from your hosts your Path Selection Polices do not revert back to your original configuration rather they revert back to the default vSphere setting of MRU (Most recently used).
This is worth noting as this is not mentioned in the documentation PernixData provide.
UPDATE - After being contacted by the guys at PernixData I can confirm they will be updating their documentation shortly to reflect this outcome.
Extending a vCenter Orchestrator (vCO) Workflow with ForEach – Backing up all ESXi hosts in a Cluster
In my previous post Backing up ESXi 5.5 host configurations with vCenter Orchestrator (vCO) – Workflow design walkthrough I showed how to create a workflow to back up host configurations, but it was limited to one host at a time. For this post I’m going to show how to create a new workflow that calls the previous one on multiple hosts using a ForEach loop to run it against each one. This was actually easier than I had anticipated (having read posts on previous versions of vCO that involved created the loops manually).
Ready? Here we go…
Create a new workflow – I’ve called mine “DefinIT-Backup-ESXi-Config-Cluster” and open the Schema view. Drag a “ForEach” element onto the workflow and the Chooser window pops up. This is a bit deceptive at first because it’s blank! However, if you enter some search text it will bring up existing workflows, so I searched for my “DefinIT-Backup-ESXi-Config” workflow that was created in that previous post.
Backing up ESXi 5.5 host configurations with vCenter Orchestrator (vCO) – Workflow design walkthrough
As a little learning project, I thought I’d take on Simon’s previous post about backing up ESXi configurations and extend it to vCenter Orchestrator (vCO), and document how I go about building up a workflow. I'm learning more and more about vCO all the time, but I found it has a really steep entry point, and finding use cases is hard if you haven't explored capabilities.
The steps I want to create in this post are:
- Right click host to trigger
- Sync and then back up the configuration to file
- Copy the file to a datastore, creating a folder based on date and the host
Ideas for future extensions of this workflow include - trigger from cluster/datastore/host folder, email notifications, emailing the backup files and backup config before triggering a VMware Update Manager remediation. Hopefully all this will come in future posts - for now, lets get stuck into the creation of this workflow.
Unless you have been sleeping under a rock you will be aware that VSAN was launched last week and has gone GA today and from what I have seen so far I do think VSAN is a great product and I think VMware have done a superb job with it.
Aside from the -many- discussions on twitter and other channels regarding the then lack of licensing information and pricing I was eager to see if VMware would offer a "foundation" VSAN option for SMB/SME
Well with the Announcements I have seen today this would seem not to be the case.
VSAN requires a minimum of 3 hosts, so lets assume for arguments sake they will have 2 CPUs each, this will mean a VSAN install will set you back around a cool £9000 (happy to be corrected if this figure is now inaccurate) before you even go ahead and procure any disks etc. That is not exactly compelling me to rush out and buy it especially given a SAN in this area of the marketplace is not far above that price including disks.
So where is the SME/SMB love VMware? I am sure they are keenly aware that 50-60% of their business is SME/SMB (in the UK at least) so I am very disappointed to see little or no offerings for this marketplace.
Perhaps this comes down to their interpretation of an SME/SMB everyone I have so far spoken to has differing opinions so perhaps this should not be a surprise?
Perhaps they had no intention to pitch it at that marketplace?
Either way I will hold out hope that a "Foundation" option appears and SME/SMB businesses alike can share in the VSAN goodness.
If you work in an SME/SMB please let me know what you think. I am personally very keen for more opinions on the subject.