Author: Unlicensed user
Every time a VDC is deployed, Abiquo Abiquo will create a NSX edge and connect it the uplink network to provide gateway, router, firewall, load balancing and SNAT services to the VMs inside the VDC.
Expand | ||
---|---|---|
| ||
Limitations
Maximum 9 private networks per VDC as per NSX limitation
Load
balancingbalancers do not support firewalls.
Abiquo properties
The following properties are global to the platform and must be configured in the DC Server and Remote Services applianceappliances:
Name | Description |
---|---|
abiquo.nsx.transport-zone | The transport zone where the networks created by Abiquo will be attached. |
abiquo.nsx.edge.cluster-id | Identifier (in VCenter) of the cluster where Abiquo will deploy the ESG. |
abiquo.nsx.edge.datastore-id |
CSV list of identifiers (in VCenter) of the |
datastores where Abiquo |
can deploy the ESG appliances according to the datastore-policy | |
abiquo.nsx.edge.datastore-policy | Allocation policy for selection of datastores to deploy ESG appliances. |
abiquo.nsx.edge.dvportgroup-id | Id of the port group where Abiquo will attach the ESG uplink. |
abiquo.nsx.edge.public-network-cidr | Network range where the ESG uplink IP and the "public" load balancer IPs will be taken from. It must be a range dedicated to Abiquo. |
abiquo.nsx.load-balancer-reserved-ips | Number of IP addresses that are reserved for NSX in each private network to allocate to load balancers. Default: 20 |
The following properties can be configured globally or per tenant. See Manage enterprise credentials and properties to configure them as tenant properties.
To configure properties globally in the API properties, add an abiquo.
prefix to their names, such as abiquo.nsx.esg.size
:
Excerpt | |||
---|---|---|---|
|
...
|
...
|
...
|