On Wed, Oct 12, 2016 at 12:34 PM, James Penick wrote:
> Are you backing both glance and nova-compute with NFS? If you're only
> putting the glance store on NFS you don't need any special changes. It'll
> Just Work.
I've got both glance and nova backed by NFS. Haven't put up cinder
yet, but that w
Are you backing both glance and nova-compute with NFS? If you're only
putting the glance store on NFS you don't need any special changes. It'll
Just Work.
On Wed, Oct 12, 2016 at 11:18 AM, Curtis wrote:
> On Wed, Oct 12, 2016 at 11:58 AM, Kris G. Lindgren
> wrote:
> > We don’t use shared storag
On Wed, Oct 12, 2016 at 11:58 AM, Kris G. Lindgren
wrote:
> 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
Tobias does bring up something that we have ran into before.
With NFSv3 user mapping is done by ID, so you need to ensure that all of your
servers use the same UID for nova/glance. If you are using packages/automation
that do useradd’s without the same userid its *VERY* easy to have mismatched
Hi,
We have an environment with glance and cinder using NFS.
It's important that they have the correct rights. The shares should be owned by
nova on compute if mounted up on /var/lib/nova/instances
And the same for nova and glance on the controller..
It's important that you map the glance and no
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 s
