[Rdo-list] Manila configuration Kilo

[Charles Short]

Hi,

Thank you for the quick reply.

That sounds useful for testing general Manila functionality.

In an ideal world I would like the backend I use to support a 
multi-tenacy segmented network, this one does not -

"The driver does not support network segmented multi-tenancy model, but 
instead works over a flat network, where the tenants share a network"

I am using vxlan in the tenant network, and so would like to create a 
Manila share network with a vxlan segmentation id.

Is there another backend that would support this, or am I bound to 
NetApp for this sort of support?

Thanks


On 06/07/2015 14:57, Haïkel wrote:
> 2015-07-06 15:41 GMT+02:00 Charles Short <cems at ebi.ac.uk>:
>> Hi,
>>
>> I have installed the latest RDO Kilo release with two compute nodes and one
>> controller.  This all works.
>>
>> I have an external NFS Linux server that currently provides NFS for Cinder.
>>
>> I want to provide another NFS export from the same server directly to an
>> instance with Manila. I can't seem to find any guidance on how to configure
>> a backend in the manila.conf file for this purpose. I need to know how I
>> configure the export server ip, path etc. The only example I can find online
>> is how to configure a backend for NetApp.
>>
>> http://netapp.github.io/openstack-deploy-ops-guide/kilo/content/manila.examples.manila_conf.single_svm.html
>>
>> I need a backend for a generic Linux NFS server
>>
> You may use the glusterfs backend
> http://docs.openstack.org/developer/manila/devref/glusterfs_driver.html
>
> Packstack doesn't configure it yet (though puppet-manila has already
> glusterfs support)
>
> H.
>
>> Thanks
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe at redhat.com