Closed
Bug 676129
Opened 14 years ago
Closed 14 years ago
Update refresh_nodes to the latest node-assignment schema
Categories
(Cloud Services :: Server: Other, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: telliott, Unassigned)
Details
(Whiteboard: [qa-])
Attachments
(1 file, 1 obsolete file)
|
4.56 KB,
patch
|
rmiller
:
review+
|
Details | Diff | Splinter Review |
refresh_nodes now needs to take a numerical value for the refresh and can now work on a product, cluster or node level as needed.
Attachment #550243 -
Flags: review?(rmiller)
Attachment #550243 -
Flags: feedback?(rsoderberg)
| Reporter | ||
Updated•14 years ago
|
Summary: Update refrest_nodes to the latest node-assignment schema → Update refresh_nodes to the latest node-assignment schema
Comment on attachment 550243 [details]
refreshes nodes
>storage.set_value('available', count, product, cluster, node)
Should only set_value if current available is less than the value to be set.
Attachment #550243 -
Flags: feedback?(rsoderberg) → feedback-
| Reporter | ||
Comment 2•14 years ago
|
||
Well, that actually complicated things a bit. Full patch to make this happen attached.
Attachment #550243 -
Attachment is obsolete: true
Attachment #550243 -
Flags: review?(rmiller)
Attachment #550742 -
Flags: review?(rmiller)
Comment 3•14 years ago
|
||
Comment on attachment 550742 [details] [diff] [review]
Script (and support) to update available nodes
Review of attachment 550742 [details] [diff] [review]:
-----------------------------------------------------------------
::: nodes/storage.py
@@ +95,5 @@
> +
> + if node is not None:
> + where.append(nodes.c.node == node)
> +
> + return where
This is definitely a use where SQLAlchemy's expression syntax is better than static SQL. :)
Attachment #550742 -
Flags: review?(rmiller) → review+
| Reporter | ||
Comment 4•14 years ago
|
||
| Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•