yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #66240
[Bug 1707252] [NEW] Claims in the scheduler does not account for doubling allocations on resize to same host
Public bug reported:
This code in the scheduler report client is used by the scheduler when
making allocation requests against a certain instance during a move
operation:
https://github.com/openstack/nova/blob/09f0795fe0f5d043593f5ae55a6ec5f6298ba5ba/nova/scheduler/client/report.py#L200
The idea is to retain the source node allocations in Placement when also
adding allocations for the destination node.
However, with the set difference code in there, it does not account for
resizing an instance to the same host, where the compute node for the
source and destination are the same.
We need to double the allocations for resize to same host for a case
like resizing the instance and the VCPU/MEMORY_MB goes down but the
DISK_GB goes up.
** Affects: nova
Importance: Medium
Status: Confirmed
** Tags: pike-rc-potential placement scheduler
** Tags added: pike-rc-potential
--
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/1707252
Title:
Claims in the scheduler does not account for doubling allocations on
resize to same host
Status in OpenStack Compute (nova):
Confirmed
Bug description:
This code in the scheduler report client is used by the scheduler when
making allocation requests against a certain instance during a move
operation:
https://github.com/openstack/nova/blob/09f0795fe0f5d043593f5ae55a6ec5f6298ba5ba/nova/scheduler/client/report.py#L200
The idea is to retain the source node allocations in Placement when
also adding allocations for the destination node.
However, with the set difference code in there, it does not account
for resizing an instance to the same host, where the compute node for
the source and destination are the same.
We need to double the allocations for resize to same host for a case
like resizing the instance and the VCPU/MEMORY_MB goes down but the
DISK_GB goes up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1707252/+subscriptions
Follow ups