Comment 4 for bug 1301279
Revision history for this message
| aeva black (tenbrae) wrote Re: Changing nodes properties after it's deployed will count as available resources in Nova | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
It is conceivable that an operator may perform physical maintenance on a node, while an instance is deployed, that do in fact change its properties -- and I think we should continue to allow that to be reflected in Ironic's API.
If I understand correctly, the real problem here isn't whether nova sees additional resources -- it's whether nova will attempt to schedule a second instance on that node.
I think the solution is to adjust the scheduler filters to prevent that situation, rather than add constraints in Ironic's API that do not reflect reality. We could also change the calculation of available resources to be based on the flavor, rather than the node, which would avoid this problem.