Upgrade Plan
Upgrades the node to a larger plan (more vCPU / RAM / disk). The node must be powered off before issuing this request. The upgrade is destructive to the underlying VM but preserves the persistent root disk; transient state in RAM is lost.
/api/v1/nodes/upgrade/{node_id}Path parameters
node_idPathstringrequiredPath parameter
node_id.
Query parameters
project_idQuerystringoptionalIdentifier of the project to scope the request to. Optional; if omitted, the account's default project is used.
- optional
- if omitted, the request is applied to the default project
example{{project_id}}apikeyQuerystringoptionalAPI key used to authenticate the request
- required
- non-empty string
example{{api_key}}locationQuerystringoptionalRegion of the node being upgraded.
- must be a non-empty string
- should be a valid region identifier
example{{location}}
Request body
application/json
Plan SKU to upgrade to. The new plan must be larger than the current plan in at least one dimension (vCPU / RAM / disk). Use the plans API to discover valid SKUs.
C3-2vCPU-2RAM-15DISK-C3.4GB_CHENNAI-Chennai- required
- non-empty string
- must follow the plan naming convention (alphanumeric, hyphens, periods)
- must reference an existing plan in the node's region
OS image identifier to use after the upgrade. Usually the same as the node's current image - supplied explicitly so the new VM is reprovisioned from a known template.
CentOS-7.5-Distro- required
- non-empty string
- allowed characters are letters, digits, hyphens, and periods
Responses
200Successful response
HTTP status code indicating the result of the upgrade request.
200- integer between 100 and 599
Human-readable status message for the upgrade.
Node successfully upgraded- non-empty string
- maximum length 255 characters