As mentioned in review [1] this will be driven by jichenjc with a blueprint. No need for this bug report anymore.
References: [1] https://review.openstack.org/#/c/177217/ ** Changed in: nova Status: Confirmed => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1446741 Title: global value for shutdown_timeout Status in OpenStack Compute (nova): Opinion Bug description: Ther's shutdown_timeout defined in nova.conf, which implies, that all virtual machines in cloud should get in time to turn off, no matter what OS they have installed. Not logical from my point of view. You have `image_os_shutdown_timeout` property, which used instead of shutdown_timeout, but it stored in system_metadata and cannot be overwritten. In result user only has ACPI shutdown and no access to libvirt's destroy method. This is what pisses off the most in AWS: you are unable to forcefully turn off VPS, when it hangs ! I use Juno and I think this is a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1446741/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
