We don’t use shared storage at all.  But I do remember what you are talking 
about.  The issue is that compute nodes weren’t aware they were on shared 
storage, and would nuke the backing mage from shared storage, after all vm’s on 
*that* compute node had stopped using it. Not after all vm’s had stopped using 
it.

https://bugs.launchpad.net/nova/+bug/1620341 - Looks like some code to address 
that concern has landed  but only in trunk maybe mitaka.  Any stable releases 
don’t appear to be shared backing image safe.

You might be able to get around this by setting the compute image manager task 
to not run.  But the issue with that will be one missed compute node, and 
everyone will have a bad day.

___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

On 10/12/16, 11:21 AM, "Curtis" <serverasc...@gmail.com> wrote:

    Hi All,
    
    I've never used NFS with OpenStack before. But I am now with a small
    lab deployment with a few compute nodes.
    
    Is there anything special I should do with NFS and glance and nova? I
    remember there was an issue way back when of images being deleted b/c
    certain components weren't aware they are on NFS. I'm guessing that
    has changed but just wanted to check if there is anything specific I
    should be doing configuration-wise.
    
    I can't seem to find many examples of NFS usage...so feel free to
    point me to any documentation, blog posts, etc. I may have just missed
    it.
    
    Thanks,
    Curtis.
    
    _______________________________________________
    OpenStack-operators mailing list
    OpenStack-operators@lists.openstack.org
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
    

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to