VMware
In this post we will be explaining how we have created a chatops workflow that enables us to upload VMWare ESXi log bundles directly to a VMWare support case from our chat client of choice. The code that makes all of this work is at the bottom of this article.
Chatops Introduction For the those who have never heard of chatops before; To me, it means the ability to call automation workflows from your favorite chat client.
In this blog post we will be explaining how we are changing the iSCSI LoginTimeout and the reasons why we are doing it in this method.
Background Recently we were going through a code upgrade on our storage arrays and one of the recommendations from Pure support is to increase the iSCSI LoginTimeout prior to upgrading the code. For the uninitiated, VMware defines the LoginTimeout as “Time in seconds the initiator will wait for the login response to finish.
Background VMware Affinity rules can solve many issues in a virtualized environment with out the need to create different clusters or datacenters to separate Virtual Machines. The specific need that we at Encore had for this was that when a vm is being cloned, if the VM was migrated to a different Host due to a vMotion, the custom spec with Kickstart files or Autounattended Syspreps would fail.
This was a random error that would only happened when vCenter or a host was overloaded.
