As promised in our latest release update we would do more frequent releases. Et voilà , today we release a new alpha version of the upcoming GA release. If possible, we will provide new versions from now on as an update so that you don’t have to reinstall your Open vStorage environment. As this new version is the first one with the update/upgrade functionality, there is no update possible between alpha 1 and alpha 2.
What is new in Open vStorage 2.2 alpha 2:
- Upgrade functionality: Under the Administration section you can check for updates of the Framework, the Volumedriver and the Open vStorage Backend and apply them. For the moment an update might require all VM’s to be shutdown.
- Support for non-identical hardware layouts: You can now mix hardware which doesn’t have the same amount of SSDs or PCI-e flash cards. When extending a vPool to a new Storage Router you can select which devices to use as cache.
- The Backend policy which defines how SCOs are stored on the Backend can now be changed. The wizard is straightforward in case you want to set for example 3-way replication.
- Rebalancing of the Open vStorage Backend, moving data from disks which are almost full to new disks to make sure all disks are evenly used, is now a service which can be enabled and disabled.
- Audit trails are no longer stored in the model but in a log.
- ASD raises time out or stops under heavy load.
- Extening a vPool to a new Storage Router doesn’t require the existing vMachines on the vPool to be stopped.
- FailOverCache does not exit but hangs in accept in some cases.
- Remove vpool raises cluster not reachable exception.
- Add logrotate entry for /var/log/arakoon/*/*.log
- Error in vMachine detail (refreshVDisks is not found).
- Arakoon 1.8.4 rpm doesn’t work on CentOS7.
- Arakoon catchup is quite slow.
- The combination Openstack with multiple vPools and live migration does not properly work in some cases.