Open Stack

Hi Eddie,

One way to do this is to “shelve” the instance which will allow to use your PCI device for other instance.
But you won’t be able to “unshelve” the previous instance until you delete or unshelve the newly created instance.

NOTE:
Shelving will release all the resources associated to that instance if the config option shelved_offload_time is not -1.

Thanks and Regards,
Dinesh Bhor | App. Software Dev. Cnslt.
dinesh.bhor at nttdata.com<mailto:dinesh.bhor at nttdata.com> | VOIP. 8833.8395I | nttdata.com/americas<http://nttdata.com/americas>
NTT DATA, Inc.
Consulting | Digital | Managed Services | Industry Solutions
Learn more:
[Description: Description: cid:image005.jpg at 01D193F0.F70B44C0]<http://americas.nttdata.com/>

[Description: Description: cid:image009.jpg at 01D193F0.F70B44C0]<http://www.linkedin.com/company/ntt-data-americas>

[Description: Description: cid:image010.jpg at 01D193F0.F70B44C0]<https://twitter.com/NTTDATAAmericas>

[Description: Description: cid:image011.jpg at 01D193F0.F70B44C0]<https://www.facebook.com/NTTDATAAmericas>



From: Eddie Yen [mailto:missile0407 at gmail.com]
Sent: Wednesday, July 05, 2017 1:49 PM
To: openstack at lists.openstack.org
Subject: [Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

Hi everyone,

I'm using OpenStack Mitaka (which deployed from Fuel 9.2) and doing GPU things.

I got a problem is I need to delete current instance which contains GPU to release device if I want assign GPU to another new instance temperately.

I'll got "No valid host was found" if I creating new instance contains GPU flavor without delete present instance, even the instance is shutdown.

Is there any way that I just shutdown the instance rather than delete it to release GPU device?


Many thanks,
Eddie.

______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170705/67c05c3e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 940 bytes
Desc: image001.jpg
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170705/67c05c3e/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 840 bytes
Desc: image002.jpg
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170705/67c05c3e/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 828 bytes
Desc: image003.jpg
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170705/67c05c3e/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 779 bytes
Desc: image004.jpg
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170705/67c05c3e/attachment-0003.jpg>