On Wed, Apr 12, 2017 at 2:54 PM, Matt Riedemann <[email protected]> wrote: > > Correct, I thought about this yesterday too. And this should be a detail in > the Cinder spec for sure, but Cinder should probably have a specific policy > check for attempting to extend an attached volume. Having said this, I see > that Cinder has a "volume:extend" policy rule but I don't see it actually > checked in the code, is that a bug? > > But the idea is, you, as a deployer, could allow extending volumes that are > not attached (using the existing volume:extend policy) but disable the > ability to extend attached volumes (maybe new rule volume:extend_attached?). > Then if you're running older computes, or not running libvirt/hyperv > computes, etc, then you just disable the API entrypoint for the entire > operation on the Cinder side. > > ^ should all be captured in the Cinder spec. >
It has been added to Cinder spec: https://review.openstack.org/#/c/453286/ -- Mathieu __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
