| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Key | Description |
|---|---|
6323 | OracleVM Plugin does not support VLAN-based management networks. See note on Oracle Ports and Bonds below |
6366 | Tasks are not accessible if the user that created them is deleted |
6375 | UNRECOGNIZED osType when importing OVF using many Windows flavors |
Notes on Oracle Ports and Bonds Abiquo recommends that you carefully read the Oracle VM Networking documentation and that you use separate ports/bonds for provisioning VM Networks within Oracle. The use of separate ports/bonds enables the Abiquo platform to fully automate the management of Network and VLAN creation within the Oracle VM environment. Therefore we recommend that OracleVM hypervisors have at least one port/bond for the management network, and at least one more port/bond for provisioning VMs. If an Oracle VM Hypervisor has only a single port/bond, then you will need to manually maintain all of the VLAN Segments for the bond. This is because the Oracle VM API does not currently permit Abiquo to create additional VLAN segments on the port/bond that is defined as the ‘management’ network. See Oracle VM Cloud Node Configuration in the Abiquo wiki for full updated information about configuring Oracle VM. |
Improvements
Key | Description |
|---|---|
4096 | IPV6 support v1 in Abiquo networking. See IPv6 Support v1 in v2.6.2 in the Abiquo wiki Abiquo has implemented version 1 of support for IPv6 in Abiquo 2.6.2. This is a preview version of the Abiquo 3.0 functionality. This functionality is fully supported in the Abiquo API and partially supported by the Abiquo 2.6 GUI. Users can create Abiquo private, public, external and unmanaged IPv6 networks via the API only. These networks will appear to end users in the GUI, and they will be able to use them in the same way as IPv4 networks are used. i.e. addresses will appear and be selected through the GUI. If you wish to use the DHCPv6 server to assign addresses, IPv6 will require one DHCPv6 server for each datacenter. i.e. Remote Services will require both an IPv4 and IPv6 DHCP server running. The DHCP and DHCPv6 servers may be running on the same machine. The implementation covers any IPv6 valid address format (short or long). It also covers the creation of IP addresses with most of the transitional IPv6 technologies: IPv4-mapped, IPv4-compatible, Teredo and ISATAP. The current proposal has limitations on the number of IPv6 NICs per virtual machine. |
6381 | vCenter - improved connection performance with lightweight connect |
...
Resolved issues
Key | Description |
|---|---|
7087 | API - Properly convert stateful (persistent) disk capacity from megabytes to bytes |
7122 | ESXi - React to ''Document: null'' during rescanHba task |
7126 | ESXi - Document:null retry during vCenter HostSystem lookup (and getConfig) |
| 7125 | Validate max anti-affinity rule name length (to prevent problems with vCenter maximum of 80 chars) |
Improvements
Key | Description |
|---|---|
7128 | ESXi - Task state polling interval set to 5 seconds to reduce load in large vCenter clusters |
...
2.6.7
Changes in properties in Abiquo 2.6.7
...