NetApp's Manila drivers for clustered Data ONTAP (with or without the management of share servers) are offered in a single, unified driver.
NetApp’s contribution strategy involves adding all new capabilities directly into the upstream OpenStack Shared File System service repositories, so all the features are available regardless of which distribution you choose when deploying OpenStack. Bug fixes are delivered into the appropriate branches that represent the different releases of OpenStack (e.g. trunk, stable/juno, stable/icehouse, etc).
On occasion, it may be necessary for NetApp to deliver capability to a previous release of OpenStack that can not be accepted in the upstream OpenStack repositories. In that case, we post the capability at the NetApp Github repository - accessible at https://github.com/NetApp/manila. Be sure to choose the branch from this repository that matches the release version of OpenStack you are deploying with. There will be a README file in the root of the repository that describes the specific changes that are merged into that repository beyond what is available in the upstream repository.
A variety of OpenStack file share storage deployment options for NetApp clustered Data ONTAP based systems are available in the Kilo OpenStack release and involve making deployment choices between the presence or absence of management of share servers (SVM or Vservers) by the driver.
The following lists all of the individual options and subsequent sections are intended to offer guidance on which configuration options ought to be employed given varying use cases:
