« Previous 1 2 3 4 5
NFS and CIFS shares for VMs with OpenStack Manila
Separate Silos
Conclusions
Manila already is almost an archetypal solution in OpenStack: The component design succeeded in the core, and Manila is in a position to provide OpenStack users with real added value, because sooner or later, many cloud users will be confronted with the need to set up a shared filesystem.
Manila is far from perfect from an admin's perspective, though. As is typical of OpenStack, the documentation is rather incomplete and difficult to understand. Various pitfalls include incomplete drivers for storage by large manufacturers, complex configuration work, and the missing UI module for Horizon.
On the positive side, NetApp should be highlighted. Many of Manila's developers are working on it, and with the driver for the separate ONTAP devices, a blueprint has almost been presented for a perfect back-end driver. Drivers for other solutions are more appearance than substance.
Nevertheless, users can hope for improvement – Manila is now following the official OpenStack release cycles. Furthermore, the solution is continuing to attract new developers, meaning that more development power is available. However, it might still take a while before Manila is level with the established standard components of OpenStack, such as Neutron, Nova, and Cinder.
Infos
- Manila: https://wiki.openstack.org/wiki/Manila
- Table of Manila drivers: http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html
« Previous 1 2 3 4 5
Buy this article as PDF
(incl. VAT)