Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page describes how to configure datastore discovery options on VMware.

For details of how Abiquo discovers datastores and how to manage datastores, see VMware

Allow datastores mounted on at least one host

You can configure Abiquo to retrieve a datastore if it is mounted, not in maintenance mode, and accessible on at least one host in the cluster.

To allow datastores if they are mounted on at least one host:

  1. On the Remote Services server, edit the abiquo.properties file and add the following property

    com.abiquo.esxi.clusterdatastore.atleastone=true
  2. To activate the properties, restart the tomcat service of the Remote Services


Ignore datastores by name

You can configure Abiquo to ignore datastores by name when you add a host or on an existing host, so that Abiquo will not check or use the datastores. You can still use these datastores outside of the platform. 

To ignore datastores by name:

  1. On the Remote Services server, in the abiquo.properties file, set the following property to a Java regular expression string to match the name of the datastores to ignore. 
    For example, to add an ESXi host or cluster with multiple datastores and ignore two datastores called Backup_1 and Backup_2, set the property as follows.

    com.abiquo.esxi.discovery.datastore.ignorebyname=Backup_.*
  2. To activate the properties, restart the tomcat service of the Remote Services


Ignore datastores that are not writeable

To configure Abiquo to ignore datastores that are not writeable:

  1. On the Remote Services server, in the abiquo.properties file, set the following property.

    com.abiquo.esxi.experimental.unsafe.ignorebaddatastore=true
  2. To activate the properties, restart the tomcat service of the Remote Services

If you activate this property, the platform may remove inaccessible datastores during an infrastructure check


  • No labels