Page Comparison

16825

NSX-T

VPN support in the Abiquo NSX-T integration

• For a description and configuration steps to add VPNs to your existing configuration, see Abiquo and NSX-T VPNs

• For details of how Abiquo supports VPNs in NSX-T, see Manage VPNs

• For full configuration details, see Configure the Abiquo NSX-T integration

16903

User interface

Add a new UI client property to exclude bill providers from display on billing dashboard.
This is a temporary property until the new private billing functionality is introduced.
See Configure provider list in dashboard billing widgets

16901

Private cloud

Refactor process to retrieve/import VMs:

• Add new VMs to the database

• For existing VMs, request VM definition sync to update VM configuration in Abiquo (using the same process as the periodic check)

16888

Azure

CSP billing should use pre-tax values.
Added a property to identify and exclude the Azure plans consumption items from billing line items.
Azure plans consumption will then be obtained from usage items only.

16872

Private cloud

When editing a VM, add an autoselected external IP from the available external IPs

7729

16774

Private cloud

On VM import, delegate synchronization of existing VMs to Virtual machine definition sync process

16934

Public cloud billing

Manual billing ignores enterprises with billing only credential

16930

User interface

Allow Edit and Sync VPNs if operation is supported.
NSX-T does not support VPN edit or sync, so do not display these buttons

16919

LDAP

2FA does not work when LDAP is enabled in multi mode

16918

User interface

400-BAD-REQUEST: Metadata cannot be null error when creating VM from template with bootstrap script and monitoring enabled by default

7774

16912

NSX-T

Distributed firewall rules for DNAT/SNAT could be more restrictive with the destinations.
See Configure the Abiquo NSX-T integration
To summarise the changes to firewalls related to this issue and the other NSX-T NAT firewall issues.

• The abiquo.nsxt.infra.tier0-allowed-gateways property was removed.

• It was replaced by the following properties for entry points:

  • abiquo.nsxt.infra.allow-dnat-sources

  • abiquo.nsxt.infra.allow-snat-destinations

• And the following properties to allow internet access

  • abiquo.nsxt.infra.allow-dnat-sources-public

  • abiquo.nsxt.infra.allow-snat-destinations-public

• The above properties are context properties, so you can configure them on the Abiquo server, or as enterprise properties, or for a VDC.

• You can specify and IP address, network address or an existing NSX-T group

16911

NSX-T

SNAT distributed firewall rule prevents connecting to another NAT IP

16910

NSX-T

Bad firewall ports

16904

LDAP

Invalid login shows 2fa confirmation instead of Bad credentials

7764

16902

NSX-T

Cannot capture VM when using NSXT (and Group 'Exclude' was modified)

7761

16009

NSX-T

Editing load balancer does not work depending on which button is used.
API was not persisting Health Check provider ID after creating the health check in the provider