Hi,
Just an update. As nobody here seems to know the answer to this I have
asked NetApp the same question as they clearly are an early adopter of
Manila and will understand how it works.
I will post back with any answers I get.
On 07/07/2015 16:41, Charles Short wrote:
Hi,
I have managed to get our storage team here to give me access to a
NetApp.
So I started reading this in detail -
http://netapp.github.io/openstack-deploy-ops-guide/kilo/content/section_m...
and it became quickly apparent that there appears to be no mention of
a particular functionality we may need....
To elaborate -
We have existing NFS exports containing files that we would like to
make available to instances directly with Manila.
All the documentation I have read both from NetApp and Openstack
concentrates on creating new Manila shares, in NetApp speak this means
the NetApp Manila backend acting on an API call to create a new
FlexVol (Manila share) on the NetApp NFS filer.
So how do you import existing FlexVols (NFS exports) into Manila?
I looks briefly at the code and only came up with this Class that
looked promising (but equally may be a red herring)-
>>
grep -ir -B 1 -A5 "existing"
/usr/lib/python2.7/site-packages/manila/api/contrib/share_manage.py
class Share_manage(extensions.ExtensionDescriptor):
"""Allows existing share to be 'managed' by
Manila."""
name = 'ShareManage'
alias = 'os-share-manage'
updated = '2015-02-17T00:00:00+00:00'
>>
Am I missing something here (which is entirely possible) or does the
API not yet expose this functionality?
Thanks
On 06/07/2015 15:13, Charles Short wrote:
> 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(a)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.ex...
>>>
>>>
>>> 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(a)redhat.com
>>>
https://www.redhat.com/mailman/listinfo/rdo-list
>>>
>>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com