XenAPINFS is a Block Storage (Cinder) driver that uses an NFS share through the XenAPI Storage Manager to store virtual disk images and expose those virtual disks as volumes. This driver does not access the NFS share directly. It accesses the share only through XenAPI Storage Manager. Consider this driver as a reference implementation for use of the XenAPI Storage Manager in OpenStack (present in XenServer and XCP). A XenServer/XCP installation that acts as Storage Controller. This hypervisor is known as the storage controller. Use XenServer/XCP as your hypervisor for Compute nodes. An NFS share that is configured for XenServer/XCP. For specific requirements and export options, see the administration guide for your specific XenServer version. The NFS share must be accessible by all XenServers components within your cloud. To create volumes from XenServer type images (vhd tgz files), XenServer Nova plug-ins are also required on the storage controller. You can use a XenServer as a storage controller and compute node at the same time. This minimal configuration consists of a XenServer/XCP box and an NFS share. Local configuration (Recommended): The driver runs in a virtual machine on top of the storage controller. With this configuration, you can create volumes from qemu-img-supported formats.

Remote configuration: The driver is not a guest VM of the storage controller. With this configuration, you can only use XenServer vhd-type images to create volumes.

Assuming the following setup: XenServer box at 10.2.2.1 XenServer password is r00tme NFS server is nfs.example.com NFS export is at /volumes To use XenAPINFS as your cinder driver, set these configuration options in the cinder.conf file: volume_driver = cinder.volume.drivers.xenapi.sm.XenAPINFSDriver xenapi_connection_url = http://10.2.2.1 xenapi_connection_username = root xenapi_connection_password = r00tme xenapi_nfs_server = nfs.example.com xenapi_nfs_serverpath = /volumes The following table shows the configuration options that the XenAPINFS driver supports: