Tuesday, April 24, 2012

new-deployrule can't find trusted source

turns out, when New_DeployRule is run and can't find a trusted source(error msg) then add the variable:

$DeployNoSignatureCheck=$true.

That'll get you past it!

Thursday, April 19, 2012

AutoDeploy, statesless computing, and Cisco UCS

It's been a while since I blogged anything, which should mean it's been a while since I've learned anything new. Not true, I've just been avoiding writing anything down. Bad techie, no Doritos for me.

I work in the SAVTG now, so I get to be the resident expert on VMware vSphere and other things VMware-ish. One interesting area I'm exploring is AutoDeploy.

The fact that VMware even productized AutoDeploy means they really are interested in stateless computing, meaning not having your software inextricably coupled to your hardware. Cisco endorses and supports this point of view, and embraces the AutoDeploy concept. UCS hardware even puts special OEM strings into it's AutoDeploy response, so the AutoDeploy server can have rules associating the Service Profile with the ESXi image. Read more about that here: http://infrastructureadventures.com/2011/12/11/scaling-vmware-deployments-with-cisco-ucs-and-vmware-auto-deploy/

The basic PowerCLI commands used to set up the AutoDeploy server are:

   Add-EsxSoftwareDepot “<path to your depot>\<your-depot.zip>”

Or you can use the VMware depot, if you have internet access:
  
   Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

Use the Get-EsxSoftwareDepot command to find the name of the image you want

Then, create a Deploy rule

  New-DeployRule -name "<a name>" -Item "<the image you want>" -AllHosts (or -Pattern, if you want to restrict this image to certain physical servers)

More infor can be found at the VMware website, or here: http://www.gabesvirtualworld.com/vsphere-5-how-to-run-esxi-stateless-with-vsphere-auto-deploy/