Automatically select the least-utilized vCenter datastore

Problem

  • I have multiple datastores named DS1, DS2, & DS3 available to my vCenter instance.
  • When provisioning new servers, I want CloudBolt to automatically use the data store with the most available capacity.
  • The user should not have to select or interact with the available datastores.

Solution

  1. For a given vCenter-backed environment, go to the VMware tab and click "import parameters from <resource handler name>".  This will import all available datastore and resource pools from the associated vCenter instance.
  2. Note the datastores from which you want CloudBolt to choose.
  3. Click the "Edit" pencil and click "remove all" to remove all datastores from the list.
  4. Click "Add Another" and enter each datastore as a comma delimited list, e.g. DS1, DS2, DS3. There should only be ONE value consisting of a comma-delimited string of datastore names in the list of datastores.
    • Since there's only one option, the datastore parameter will be hidden from the user and the single option will be automatically selected.
  5. Click Save.
    • For servers in this environment, CloudBolt will now select the datastore with the most free space from the list DS1, DS2, and DS3
Have more questions? Submit a request

4 Comments

  • 0
    Avatar
    Rick Kilcoyne

    Hey CloudBolt fans, this is no longer a valid solution since adding storage tiers.

  • 0
    Avatar
    Erin Getschmann

    Hi Rick, I just came across this solution - this would have been super helpful for us!  But I see your comment that it does not work with storage tiers.  Does Cloudbolt have an alternate solution for intelligently selecting a datastore, if vmware storage tiers are in use?  

    Thanks,

    Erin

  • 0
    Avatar
    Tor Peck

    Very interested in the answer to Erin's question.

    Where in the same boat.

    Thanks

    Tor

  • 0
    Avatar
    David Adamec

    Hey folks, we've brought back the comma-separated datastores in CloudBolt 7.1. This solution should work once again if you've updated CloudBolt to the latest GA release.

    Thanks,
    David

     

Please sign in to leave a comment.