Answer found - AWS CFN has no notion of stack suspend/resume, thus actual AWS resources have it neither. As it it an OpenStack feature, and I know how Nova + Cinder behave currently, it looks safe to remove the mentioned logic.
Best regards, Pavlo Shchelokovskyy Software Engineer Mirantis Inc www.mirantis.com On Fri, Mar 13, 2015 at 4:22 PM, Pavlo Shchelokovskyy < [email protected]> wrote: > Hi all, > > as I am removing scheduler tasks from server resources, I have the > following question: > > in OS Server resource on suspend/resume/delete we do not care about > attached volumes. In fact Nova keeps them attached to the suspended > instance (volumes are in 'in-use' state) and after server resume they are > still attached to the server without any additional steps. On server delete > Nova again detaches all the volumes automatically. > > On the other hand, in AWS Instance resource we manually detach volumes on > delete/suspend and reattach them on resume. What's the point of that? Is it > for some compatibility with instance+volumes behavior in real AWS or some > leftover from earlier Nova days? > > An advice from anyone with AWS experience would be appreciated, as if it > is not for compatibility sake, I would gladly remove that seemingly > unnecessary logic. > > Best regards, > > Pavlo Shchelokovskyy > Software Engineer > Mirantis Inc > www.mirantis.com >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
