6 Responses

  1. thenexus6
    thenexus6 at |

    I use profiles to auto-deploy our 60-node cluster starting from release of 5.0. Well, sometimes I think I’d better use stateful install and do configuration updates via CLI scripting :)

    Most annoying host profiles problems for me are:

    1) You can’t save custom routes with profiles (so for example you get a problem with storage vmk when trying to reach the target in another subnet)

    2) After “update from reference host” action you lose all passwords in the profile (yep, it’s what they call “feature”) including iSCSI CHAP passwords so the least painful solution is to forget about updating from ref host right after main configuration is complete and use “edit profile” feature only.

    As a bonus I’ve got a frozen host after trying to boot 5.1 with 5.0 profile (yep, some kernel modules defaults had changed so had to skip this part).

    Anyway, it’s better than nothing and if you’re ready to adapt your infrastructure to fit host profiles restrictions – they allow you to mess hard once (in a free time) and then stay calm if any configuration problem appears.

    Reply
  2. Craig M
    Craig M at |

    I love host profiles and don’t mind spending the time to nut out these little issues (I’ve come across all of the above) for an initial setup.

    But the 1 thing that does my head in, is every time you update the reference host, you have to go through the same rigmarole again. For some reason the changes I make to the Profile Configuration do not stick after an update.

    That’s my facepalm moment.

    Reply
  3. Preetam
    Preetam at |

    Great Blog, Not sure how I missed it from my list. Thank you for sharing these valuable lessons

    Reply
  4. Alex
    Alex at |

    For the iSCSI Adapter IQN compliance failure message, the iSCSI Adapter IQN is something that’s saved in the Answer File, so it might work better to try doing the Update Answer File action before disabling the iSCSI stuff.

    Some of the other problems raised in this blog post and comments have been improved upon in vSphere 5.1. The enable/disable configuration options should be preserved across the “update from reference host” action, as are admin passwords, local users, and permissions (but maybe not iSCSI CHAP?).

    The set of resource pools managed by host profiles has been limited a lot, and some of the kinks have been worked out around firewall and service configuration.

    Static routes are supported in 5.1 as well.

    PSA and NMP configuration still isn’t going to work well unless the storage hardware is 100% identical, but it should deal with local SAS disks better in 5.1.

    Reply
  5. Some Tips for Host Profiles | VMware Support Insider - VMware Blogs

    [...] more interesting tidbit can be found on the topic over on this blog: Grappling With vSphere 5 Host Profiles [...]

Share your point of view!