On Mon, Feb 26, 2018 at 2:13 PM, Matt Riedemann <mriedemos at gmail.com> wrote: > On 2/26/2018 8:09 PM, John Griffith wrote: > >> I'm interested in looking at creating a mechanism to "refresh" all of the >> existing/current attachments as part of the Cinder Failover process. >> > > What would be involved on the nova side for the refresh? I'm guessing > disconnect/connect the volume via os-brick (or whatever for non-libvirt > drivers), resulting in a new host connector from os-brick that nova would > use to update the existing volume attachment for the volume/server instance > combo? Yep, that's pretty much exactly what I'm thinking about / looking at. I'm also wondering how much of the extend actions we can leverage here, but I haven't looked through all of that yet. > > > -- > > Thanks, > > Matt > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180226/d1026b9d/attachment.html>