This commit implements the ability for an admin to manage
existing RSD composed nodes with Valence. In the event that
an RSD pod manager contains composed nodes that were created
without Valence, it's possible to use this function to
add those nodes to the Valence database.
Change-Id: I13e8076fb718ebd356cb7b4839cfb4b83c798672
Implements-blueprint: manage-node
Current valence support two ways to specify required hardware
resource.
* Specify every details in "properties" attribution
* Specify node flavor via "flavor_id"
Added example to show how to compose through flavor.
Change-Id: Ieab02fe2f2a46fa8cd28285fb88bc5fba8e5b6ff
Closes-Bug: #1677080
This patch will allow a user to compose a node
based on requirements specified in a flavor by including
the flavor_id in the composition request. It also changes
the contents of the request requirements in the API to be
included in a "properties" key.
Change-Id: I3052e1d5877e63d4a217ecdcdaee32bdb21cb8ed
This patch allow user to set boot source of composed node. Two
parameters are needed in request body,
"Target" - the boot source to be used at next boot
"Enabled" - options "Once" and "Continuous" are supported, which
indicate whether this action is only one time change
Partially-Implements blueprint node-action
Change-Id: I46342c884e3cb8f00069e7e2c10c878582a2b185
Add a new entry point of pod_manager info and add how to Delete,
Create, Patch entry point of pod_manager, also show a mockup json
example of pod_manager resources for implementation reference.
Change-Id: I25c983bdcb379583587db7a8b2b6272ef1b05b95
Add pooled resources, compute system , composed node and flavor API.
Remove extra space with end of line and fix literal block warning.
Change-Id: Ib7f00617e48e7ecc6fe30091d79ef6b47ae4c5af
