To be clear - the changes that Yunhong describes below are not part of the
extensible-resource-tracking blueprint. Extensible-resource-tracking has the
more modest aim to provide plugins to track additional resource data.
Paul.
-Original Message-
From: Jiang, Yunhong
Paul, thanks for clarification.
--jyh
-Original Message-
From: Murray, Paul (HP Cloud Services) [mailto:pmur...@hp.com]
Sent: Friday, January 17, 2014 7:02 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] how is resource
Hi,
I'm trying to figure out how resource tracking is intended to work for
live migration and evacuation.
For a while I thought that maybe we were relying on the call to
ComputeManager._instance_update() in
ComputeManager.post_live_migration_at_destination(). However, in
On Jan 16, 2014, at 1:12 PM, Chris Friesen chris.frie...@windriver.com wrote:
Hi,
I'm trying to figure out how resource tracking is intended to work for live
migration and evacuation.
For a while I thought that maybe we were relying on the call to
ComputeManager._instance_update() in
There are some related discussion on this before.
There is a BP at
https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking which
try to support more resources.
And I have a documentation at
https://docs.google.com/document/d/1gI_GE0-H637lTRIyn2UPfQVebfk5QjDi6ohObt6MIc0
.
