3.8.x
3.10.x
4.0.x
4.2.0
Added
Property | Description | ||||
---|---|---|---|---|---|
abiquo.capturedhcp | Update DHCP during virtual machine capture | ||||
abiquo.monitoring.max.statistic.period.days | Maximium period in days for statistical metrics queries through the API | ||||
abiquo.nsx.edge.datastore-policy | Allocation policy for selection of datastores to deploy Edge appliances. | ||||
abiquo.rabbitmq.tls | Set to true if RabbitMQ server is SSL enabled | ||||
abiquo.rabbitmq.tls.trustallcertificates | The platform will not enforce any server certificate authentication if set to true | ||||
abiquo.vm.statsupdate.interval | Interval between executions of the virtual machine standardized stats updater in milliseconds | ||||
abiquo.vm.statsupdate.range.days | Number of days to consider in the statistic query executed by the virtual machine standardized stats updater | ||||
abiquo.watchtower.password | Watchtower password | ||||
abiquo.watchtower.tls | Set to true if Watchtower server is SSL enabled | ||||
abiquo.watchtower.tls.trustallcertificates | The platform will not enforce any server certificate authentication if true | ||||
abiquo.watchtower.username | Watchtower username |
Changed
Property_______________________________ | Description | ||||
---|---|---|---|---|---|
abiquo.backup.check.delay | Delay between executions of the backup results check (milliseconds). Default is 10 minutes | ||||
abiquo.nsx.edge.datastore-id | List of vCenter datastores where the Edge appliances will be deployed in CSV format with allocation according to abiquo.nsx.edge.datastore-policy |
Deprecated
Property_______________________________ | Description | ||||
---|---|---|---|---|---|
com.abiquo.esxi.experimental.eagerzero.copy | If true, force eager zero thick provisioning on copied disks. Deprecated and replaced by Allocation attribute for VM templates and VM disks | ||||
com.abiquo.esxi.experimental.eagerzero.new | If true, force eager zero thick provisioning on new empty disks. Deprecated and replaced by Allocation attribute for VM templates and VM disks |
Deleted
4.2.1
New obligatory properties for Abiquo NSX integration in 4.2.1
For the Abiquo NSX integration
- The abiquo.nsx.edge.description property is obligatory in Abiquo 4.2.1+. You can add this property for the entire platform, or for each enterprise as nsx.edge.description.
The abiquo.nsx.edge.dhcp.size and the abiquo.nsx.edge.esg.size properties are obligatory in Abiquo 4.2.1+. You can add these properties for the entire platform, or for each enterprise as nsx.edge.description.
See Configure the NSX integration
Added
Cloudoorsphere properties are also documented on the provider page: CloudoorSphere
Property | Description | ||||
---|---|---|---|---|---|
abiquo.cpp.cloudoorsphere.defaults.healthcheck.attempts | The load balancer health check attempts to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.bodyregex | The load balancer health check body regex to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.interval | The load balancer health check interval to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.path | The load balancer health check path to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.port | The load balancer health check port to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.protocol | The load balancer health check protocol to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.statusregex | The load balancer health check status regex to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.healthcheck.timeout | The load balancer health check timeout to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.loadbalancer.algorithm | The load balancer algorithm to return while syncing a load balancer | ||||
abiquo.cpp.cloudoorsphere.defaults.loadbalancer.instancetype | The instance type (hardware profile) to use when creating a load balancer | ||||
abiquo.cpp.cloudoorsphere.loadbalancer.allowed.algorithms | The list of algorithms supported by the load balancers (comma-separated values) | ||||
abiquo.cpp.cloudoorsphere.loadbalancer.creation.timeout | Timeout to use while creating a load balancer and waiting for a finished status | ||||
abiquo.cpp.cloudoorsphere.loadbalancer.deletion.timeout | Timeout to use while deleting a load balancer and waiting for a finished status because the API does not return this status | ||||
abiquo.nsx.edge.description | Edge description. | ||||
abiquo.nsx.edge.dhcp.size | Specify the size of the DHCP Edge appliance (ecmp plugin). | ||||
abiquo.nsx.edge.esg.size | Specify the size of the ESG Edge appliance (gateway and ecmp plugin). | ||||
abiquo.nsx.edge.plr-esg-id | ID of the Edge that acts as the PLR (nsx-nat only) | ||||
abiquo.nsx.edge.plr-transit-cidr | CIDR of the transit network to be used between the PLR and the Edges of each Abiquo VDC (nsx-nat only) | ||||
abiquo.nsx.edge.plr-transit-ip | Configure the IP to be used to connect the PLR to the plr-transit vSwitch (nsx-nat only). Optional, if not set, use the lowest address in "abiquo.nsx.edge.plr-transit-cidr" | ||||
abiquo.virtualfactory.cloudoorsphere.vmstate.retry.timeoutInMilliseconds | The timeout to get the state of a VM after a power action | ||||
cloudoorsphere.non-retryable | A list of API calls that must not be retried after an error code in the response (comma-separated values) Default: server:create | ||||
abiquo.vcd.connectionTimeoutMs | Time to wait to establish the connection to vCloud Director (milliseconds) | ||||
abiquo.vcd.login.TimeoutMs | Maximum time to wait for login to vCloud Director (milliseconds) | ||||
abiquo.vcd.readTimeoutMs | Maximum time to wait to read from the connection to vCloud Director (milliseconds) |
4.2.2
New
Property_______________________________ | Description | ||||
---|---|---|---|---|---|
abiquo.nsx.nat.protocols | Allowed NAT rule protocols (nsx-nat only) Default: TCP,UDP,ANY,ICMP#ANY,ICMP#Parameter-Problem,ICMP#Echo-Request,ICMP#Destination-Unreachable,ICMP#Redirect,ICMP#Router-Solicitation,ICMP#Time-Exceeded,ICMP#Address-Mask-Request,ICMP#Timestamp-Reply,ICMP#Router-Advertisement,ICMP#Timestamp-Request,ICMP#Address-Mask-Reply,ICMP#Echo-Reply,ICMP#Source-Quench |
Changed
Property_______________________________ | Description | ||||
---|---|---|---|---|---|
abiquo.nsx.edge.public-network-cidr | Network range where the "public" load balancer IPs will be taken from. It must be a range dedicated to Abiquo. Deleted from NAT plugin, still used in gateway plugin |
4.2.3
New
Property_______________________________ | Description | ||||
---|---|---|---|---|---|
abiquo.guest.password.length | Template to configure guest initial passwords that enables you to define the length and the character set. The following tokens are allowed in the template:
For each token, the value must be in one of the following formats:
Examples:
Default: lower=2-6,upper=2-6,numbers=2-6,symbols=2-6 |
| |||
abiquo.guest.password.exclude | Characters to avoid when generating guest passwords, for example: ,;$ | ||||
abiquo.vcd.metric.live.force | Do not try to retrieve historical metrics data for vCloud Director, only use live metrics | ||||
abiquo.vcd.metric.live.fallback | If it is not possible to retrieve historical metrics data for vCloud Director, attempt to use live metrics | ||||
abiquo.vcd.parentnetwork | Private network connection to allow outgoing traffic in vCloud Director. Value can be "none" for isolated networks or any existing organization network name. The default value of "edge-uplink" will use the external network connected to the edge gateway of the organization virtual datacenter. | ||||
abiquo.virtualfactory.hyperv.automaticShutdownAction | Action to take for the VM when the host is shut down. Sets Msvm_VirtualSystemSettingData.AutomaticShutdownActionhttps://msdn.microsoft.com/en-us/Library/hh850257(v=vs.85).aspxwhen creating a VM. When it is set to "3", the state will be saved and swap files will be written; set their location with the swapFileDataRoot property. | ||||
abiquo.virtualfactory.hyperv.refreshMonitorJob.intervalms | Refresh interval in milliseconds for checking progress on operations that require monitoring of a job, such as disk copies. | ||||
abiquo.virtualfactory.hyperv.sambaHosts | List of Samba hosts where the platform can discover shares to use as Hyper-V datastores. The list is in CSV format. Leave empty to not try discovery | ||||
abiquo.virtualfactory.hyperv.swapFileDataRoot | The path of a directory where swap files for the VM will be stored. When the automaticShutdownAction property is set to save the VM state, swap files will be written to this location. |
4.4.0
Property | Description | |||||
---|---|---|---|---|---|---|
abiquo.amazon.waitforstatus.timeout | Default AWS wait for status timeout | |||||
abiquo.dnsmasq.serviceiface | Network interface onto which bridged VLAN interfaces will be attached | |||||
abiquo.dnsmasq.basedir | Folder in which to store lease information | |||||
abiquo.dnsmasq.startscript | Script to start a new instance of dnsmasq on a bridged VLAN interface | |||||
abiquo.dnsmasq.stopscript | Script to stop and clean up an instance of dnsmasq running on a bridged VLAN interface | |||||
abiquo.dnsmasq.reloadscript | Script to reload a running instance of dnsmasq | |||||
abiquo.oraclease.read-timeout-ms | Timeout to complete connections to the Oracle ASE manager (milliseconds). A value of 0 means no timeout | |||||
abiquo.oraclease.connection-timeout-ms | Timeout to establish connections to the ORACLE ASE manager in milliseconds. A value of 0 means no timeout. | |||||
abiquo.oraclease.timeout | Timeout to get the state of a virtual machine | |||||
abiquo.oraclease.defaultLoginUser | ORACLE ASE default user for connecting to Linux VMs over SSH. For Windows VMs, edit the template and enter the Administrator username and password | |||||
abiquo.virtualfactory.azurecompute-arm.operationtimeout | The timeout to consider an operation failed in Azure ARM | |||||
abiquo.vsm.vmsyncforcedpublishcount.{PLUGIN}
| Number of virtual machine synchronizer executions before force the publish of virtual machine definitions. The default value of 0 means never Default: 0 |
Deleted
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.virtualfactory.azure.defaultLoginPassword | Default password for virtual machines in Azure if not found in the template | |||||
abiquo.virtualfactory.azure.defaultLoginUser | Default login for virtual machines in Azure if not found in the template. | |||||
abiquo.virtualfactory.azure.retry.timeBetweenTriesInSeconds | Time to wait between polls during a retry | |||||
abiquo.virtualfactory.azure.retry.timeoutInSeconds | Timeout retrying an operation | |||||
abiquo.virtualfactory.azure.storageAccountPrefix | Prefix of the name of the Azure Storage account created for deployments (one account per region). | |||||
abiquo.virtualfactory.azure.wait.timeBetweenTriesInSeconds | Time to wait between polls during an operation wait. | |||||
abiquo.virtualfactory.azure.wait.timeoutInSeconds | Timeout waiting for an operation to complete, e.g deploy / undeploy. |
Changed
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.vsm.actor.creation.delay.{PLUGIN}
| The delay in milliseconds added between the creation of actors on VSM startup for each hypervisor or public cloud plugin (PLUGIN). | |||||
abiquo.vsm.hostsyncfrequency.{HV}
| Time between executions of infrastructure check in milliseconds | |||||
abiquo.vsm.pollingfrequency.{PC}
| The delay between VSM polling of virtual machines in milliseconds for each public cloud plugin (PC). | |||||
abiquo.vsm.vmsyncfrequency.{PLUGIN}
| The delay between virtual machine synchronizer operations in milliseconds. for each hypervisor or public cloud plugin (PLUGIN) |
4.5.0
Added
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.openid.client.acr-validation | Validate acr values from jwt token when authenticating with an OpenID Connect Server, if true | |||||
abiquo.openid.client.acr-values | Space separated values to send as acr values to an OpenID Connect Server when authenticating and to validate from jwt token if 'acr-validation' property is true | |||||
abiquo.openid.cookie.maxage | After OpenID authentication flow, the API redirect adds a cookie with the access_token and the id_token. The expiry of the OpenID authentication cookie in seconds. A negative value means that the cookie is not stored persistently and will be deleted when the web browser exits. A zero value causes the cookie to be deleted | |||||
abiquo.openid.cookie.refreshtoken.include | If true, the OpenID authentication cookie will also contain the refresh token. Default: false | |||||
abiquo.pluginmetadata.{HP}.ethernetDrivers | Override default plugin metadata to update the compatible ethernet driver | |||||
abiquo.server.mail.from | The sender of platform email notifications | |||||
abiquo.virtualfactory.azurecompute-arm.defaultloginname | The default login name if not specified by the imported ARM template or by editing the template in the platform |
| ||||
abiquo.virtualfactory.azurecompute-arm.defaultloginpassword | The default login password if not specified by editing the template in the platform |
| ||||
abiquo.virtualfactory.{HP}.openSession
| The maximum number of simultaneous operations on a single hypervisor or provider region. |
| ||||
abiquo.virtualfactory.{DEV}.device.openSession
| The maximum number of simultaneous operations on a single device |
| ||||
abiquo.virtualfactory.{BM}.backup.openSession
| The maximum number of simultaneous operations on a single backup manager, by type |
| ||||
abiquo.virtualfactory.openSession.byvdc | If true, the maximum number of simultaneous operations applies to a single virtual datacenter (instead of single hypervisor) |
| ||||
abiquo.virtualfactory.{HP}.openSession.byvdc
| If true, the max number of simultaneous operations applies to a single virtualdatacenter (instead of single hypervisor), by type. | |||||
abiquo.virtualfactory.device.openSession.byvdc | If true, the default maximum number of simultaneous operations applies to a single virtualdatacenter (instead of a single device) |
| ||||
abiquo.virtualfactory.{DEV}.device.openSession.byvdc
| If true, the default maximum number of simultaneous operations applies to a single virtualdatacenter (instead of a single device), by type |
| ||||
abiquo.virtualfactory.backup.openSession.byvdc | If true, the default maximum number of simultaneous operations applies to a single virtualdatacenter (instead of a single backup manager) |
| ||||
abiquo.virtualfactory.{BM}.backup.openSession.byvdc
| If true, the default maximum number of simultaneous operations applies to a single virtualdatacenter (instead of a single backup manager), by type |
| ||||
abiquo.inactivitysession.maxinhours | Maximum hours without activity in a pool before release. The minimum value is 6 and if a lower value is specified, the platform will use 6 | |||||
abiquo.virtualfactory.openSession.faststatechanges | If true, VM state changes (powerOn, powerOff, shutdown, reset, pause, resume) are executed outside the pool (not waiting for any operation) |
| ||||
abiquo.virtualfactory.{HP}.openSession.faststatechanges
| If true, VM state changes (powerOn, powerOff, shutdown, reset, pause, resume) are executed outside the pool (not waiting for any operation), by type. | |||||
com.abiquo.esxi.experimental.vmgroup.gueststartswith.{OSprefix} | Add newly deployed VMs to an existing VM group (naming convention is Lic_{clustername}_{osname}_VMs) using DRS rules when the template osType matches the OSprefix of a property. For example, to add Windows VMs to Lic_vcloudcluster_Windows_VMs, you could use "win" as the value of OSprefix, |
Deleted
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.heartbeat.autostart | Automatically start Abiquo heartbeat |
Changed
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.virtualfactory.openSession | The default maximum number of simultaneous operations on a single hypervisor Description changed from "maximum" to "The default maximum" due to the introduction of more specific properties |
| ||||
abiquo.virtualfactory.backup.openSession | The default maximum number of simultaneous operations on a single backup manager Description changed from "maximum" to "The default maximum" due to the introduction of more specific properties |
| ||||
abiquo.virtualfactory.device.openSession | The default maximum number of simultaneous operations on a single device Description changed from "maximum" to "The default maximum" due to the introduction of more specific properties |
|
4.6.0
Added
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.enterprise.property.discount.suffix | Pricing discount is defined in the enterprise properties. The property key is built using the hypervisor type in lowercase and adding a suffix, which is defined by this property |
| ||||
abiquo.enterprise.property.pricefactor.suffix | Pricing pricefactor is defined in the enterprise properties. The property key is built using the hypervisor type in lowercase and adding a suffix, which is defined by this property |
| ||||
abiquo.nars.async.amqp.backoff.minseconds | AMQP consumer reconnection. First attempt to restart in seconds | |||||
abiquo.nars.async.amqp.backoff.maxseconds | AMQP consumer reconnection. Maximum number of seconds without restart attempt | |||||
abiquo.nars.async.pool.max | Default maximum number of simultaneous operations on a single hypervisor or region connection. | |||||
abiquo.nars.async.pool.byvdc | If true, the max number of simultaneous operations apply to a single virtualdatacenter (instead of single hypervisor or region connection) | |||||
abiquo.nars.async.pool.inactivity.maxhours | Maximum hours without activity in a pool before release. Minimum value is 6, if a lower value is specified, will use 6 | |||||
abiquo.nars.async.pool.{plugin}.max
| Maximum number of simultaneous operations on a single hypervisor or region connection, by type. | |||||
abiquo.nars.async.pool.{plugin}.byvdc
| If true, the max number of simultaneous operations apply on a single virtual datacenter (instead of single hypervisor or region connection), by type. Default: abiquo.nars.async.pool.byvdc | |||||
abiquo.nars.async.prefetch | Limit of parallelism of async request execution. Number of unacknowledged messages from the requests queue. | |||||
abiquo.plugin-client.connectionrequesttimeout | API to NARS http client configuration: timeout in milliseconds used when requesting a connection. A value of 0 is interpreted as an infinite timeout. A negative value is interpreted as undefined | |||||
abiquo.plugin-client.connectiontimeout | API to NARS client configuration: timeout in milliseconds when a connection is established. A value of 0 is interpreted as an infinite timeout. A negative value is interpreted as undefined | |||||
abiquo.plugin-client.pool.checkconnections | API to NARS http client pool configuration: When reusing a connection checks if the elapsed time since the last use exceeds this timeout. | |||||
abiquo.plugin-client.pool.maxclients | API to NARS http client pool configuration: Max active HTTP connections to any NARS. | |||||
abiquo.plugin-client.pool.maxclientsperendpoint | API to NARS http client pool configuration: Max active HTTP connections to the same NARS instance. | |||||
abiquo.plugin-client.pool.maxkeepalivesms | API to NARS http client pool configuration: Max time to keep a persistent connection. | |||||
abiquo.plugin-client.timeout | API to NARS http client configuration: milliseconds to wait for a sync execution in the plugin. | |||||
abiquo.plugin-client.timeout.{plugintype} | API to NARS http client configuration: milliseconds to wait for a sync execution in the plugin by type | |||||
abiquo.plugin-client.timeout.{plugintype}.{operationname} | API to NARS http client configuration: milliseconds to wait for a sync execution in the plugin by type and operation | |||||
abiquo.pricing.import.check.delayInHrs | Delay between executions of the pricing import check in hours |
Deleted
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.nodecollector.timeout | Timeout for Server/API connections to Nodecollector (Discovery manager) in milliseconds. |
Changed
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.cloudoorspherecloudoorspherecpp | For all CloudoorSphere properties, see CloudoorSphere Property name changed from abiquo.cpp.cloudoorspherecpp |
4.6.1
Added
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
com.abiquo.esxi.discovery.networkinterface.networks | Only use physical network interfaces connected to the specified networks when adding vCenter hosts or clusters. If ''onlymanagementip'' is true, then first check for IPs (management or not) in the specified networks and if none are found, use onlymanagementip filter. The filter is a comma separated list of network in CIDR format, and the order specifies the priority |
| ||||
com.abiquo.esxi.discovery.networkinterface.onlymanagementip | Only use virtual NICs of the host configured for management traffic<br/> Default: false |
|
4.6.3
Added
Property_______________________________ | Description | |||||
---|---|---|---|---|---|---|
abiquo.costusage.task.frequencyinhours | Frequency for executing the consolidation of usage accounted |
| ||||
abiquo.nars.async.pendingpublish.minutes | Check for pending responses which failed to publish due to AMQP failure in nars | |||||
abiquo.nars.async.pendingpublish.path | Path to file that stores pending responses which failed to publish due to AMQP failure in nars | |||||
abiquo.virtualfactory.pendingpublish.minutes | Check for pending responses which failed to publish due to AMQP failure in virtualfactory | |||||
abiquo.virtualfactory.pendingpublish.path | Path to file that stores pending responses which failed to publish due to AMQP failure in virtualfactory |