Hi, so for this moment we have 2 options: - somehow check every time that nodes are on shared storage(now it's done over ssh) - define that shared storage explicitly() The possible workaround for the first option is to use RPC for checking that temporarily created test file exists(more RPC calls). For the second option(I think the most preferable) there is a bp [1] that introduce abstraction that allows set up such shared storages. Timofey [1] - https://blueprints.launchpad.net/nova/+spec/generic-resource-pools On Thu, Jul 28, 2016 at 11:34 AM, Marcus Furlong <furlongm at gmail.com> wrote: > Hi, > > I've been trying to find some information about using nova resize on > shared storage, without giving each compute node ssh access to every > other compute node. As the VM is on shared storage, the compute node > shouldn't need ssh access to another compute node? > > Is this something that anyone has succeeded in doing? > > I've found the following documentation: > > http://docs.openstack.org/mitaka/config-reference/compute/resize.html > http://docs.openstack.org/user-guide/cli_change_the_size_ > of_your_server.html > > but it does not say what to do in the case of shared storage. > > Cheers, > Marcus. > -- > Marcus Furlong > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160808/c6f0824d/attachment.html>