API Description | API Path |
---|---|
Get upgrade task statusGet upgrade task status for the given task of the given bundle. Both bundle_name and task_id must be provided, otherwise you will receive a 404 NOT FOUND response. |
GET /api/v1/node/upgrade
GET /api/v1/transport-nodes/<transport-node-id>/node/upgrade GET /api/v1/cluster/<cluster-node-id>/node/upgrade |
Execute upgrade taskExecute upgrade task. |
POST /api/v1/node/upgrade/performtask
POST /api/v1/transport-nodes/<transport-node-id>/node/upgrade/performtask POST /api/v1/cluster/<cluster-node-id>/node/upgrade/performtask |
Get upgrade progress statusGet progress status of last upgrade step, if upgrade bundle is present. |
GET /api/v1/node/upgrade/progress-status
GET /api/v1/transport-nodes/<transport-node-id>/node/upgrade/progress-status GET /api/v1/cluster/<cluster-node-id>/node/upgrade/progress-status |
Get upgrade status summaryGet status summary of node upgrade, if upgrade bundle is present. |
GET /api/v1/node/upgrade/status-summary
GET /api/v1/transport-nodes/<transport-node-id>/node/upgrade/status-summary GET /api/v1/cluster/<cluster-node-id>/node/upgrade/status-summary |
Upgrade the upgrade coordinator.Upgrade the upgrade coordinator module itself. This call is invoked after user uploads an upgrade bundle. Once this call is invoked, upgrade coordinator stops and gets restarted and target version upgrade coordinator module comes up after restart. |
POST /api/v1/upgrade?action=upgrade_uc
|
Abort pre-upgrade checksAborts execution of pre-upgrade checks if already in progress. Halts the execution of checks awaiting execution at this point and makes best-effort attempts to stop checks already in execution. Returns without action if execution of pre-upgrade checks is not in progress. |
POST /api/v1/upgrade?action=abort_pre_upgrade_checks
|
Execute pre-upgrade checksRun pre-defined checks to identify potential issues which can be encountered during an upgrade or can cause an upgrade to fail. The results of the checks are added to the respective upgrade units aggregate-info. The progress and status of operation is part of upgrade status summary of individual components. Returns HTTP status 500 with error code 30953 if execution of pre-upgrade checks is already in progress. |
POST /api/v1/upgrade?action=execute_pre_upgrade_checks
|
Execute post-upgrade checksRun pre-defined checks to identify issues after upgrade of a component. The results of the checks are added to the respective upgrade units aggregate-info. The progress and status of post-upgrade checks is part of aggregate-info of individual upgrade unit groups. Returns HTTP status 500 with error code 30953 if execution of post-upgrade checks is already in progress. |
POST /api/v1/upgrade/<component-type>?action=execute_post_upgrade_checks
|
Upload upgrade bundleUpload the upgrade bundle. The call returns after upload is initiated. User needs to check upload status periodically by retrieving upgrade bundle upload status to find out if the upload is completed. This API is deprecated, please use /upgrade/bundles?action=upload API to upload the upgrade bundle. |
POST /api/v1/upgrade/bundle?action=upload
(Deprecated)
|
Upload upgrade bundleUpload the upgrade bundle. This call returns after upload is completed. You can check bundle processing status periodically by retrieving upgrade bundle upload status to find out if the upload and processing is completed. |
POST /api/v1/upgrade/bundles?action=upload
|
Fetch upgrade bundle from given urlFetches the upgrade bundle from url. The call returns after fetch is initiated. Check status by periodically retrieving upgrade bundle upload status using GET /upgrade/bundles/ The upload is complete when the status is SUCCESS. |
POST /api/v1/upgrade/bundles
|
Get uploaded upgrade bundle informationGet uploaded upgrade bundle information |
GET /api/v1/upgrade/bundles/<bundle-id>
|
Cancel upgrade bundle uploadCancel upload of upgrade bundle. This API works only when bundle upload is in-progress and will not work during post-processing of upgrade bundle. If bundle upload is in-progress, then the API call returns http OK response after cancelling the upload and deleting partially uploaded bundle. |
POST /api/v1/upgrade/bundles/<bundle-id>?action=cancel_upload
|
Get uploaded upgrade bundle upload statusGet uploaded upgrade bundle upload status |
GET /api/v1/upgrade/bundles/<bundle-id>/upload-status
|
Accept end user license agreementAccept end user license agreement |
POST /api/v1/upgrade/eula/accept
|
Return the acceptance status of end user license agreementReturn the acceptance status of end user license agreement |
GET /api/v1/upgrade/eula/acceptance
|
Return the content of end user license agreementReturn the content of end user license agreement in the specified format. By default, it's pure string without line break |
GET /api/v1/upgrade/eula/content
|
Get functional state of the upgrade coordinatorGet the functional state of the upgrade coordinator. |
GET /api/v1/upgrade/functional-state
|
Get upgrade historyGet upgrade history |
GET /api/v1/upgrade/history
|
Get list of nodes across all typesGet list of nodes. If request parameter component type is specified, then all nodes for that component will be returned. If request parameter component version is specified, then all nodes at that version will be returned. |
GET /api/v1/upgrade/nodes
|
Get summary of nodesGet summary of nodes, which includes node count for each type and component version. |
GET /api/v1/upgrade/nodes-summary
|
Upgrade selected unitsUpgrades, Resumes the upgrade of a selected set of units. |
POST /api/v1/upgrade/plan?action=upgrade_selected_units
|
Stage the upgrade bitsThis will stage the upgrade bits so that upgrade can be driven from outside NSX upgrade-coordinator. If component type is not provided as a request parameter then upgrade staging will be performed on all the components. |
POST /api/v1/upgrade/plan?action=stage-upgrade
|
Start upgradeStart the upgrade. Upgrade will start as per the upgrade plan. |
POST /api/v1/upgrade/plan?action=start
|
Pause upgradePause the upgrade. Upgrade will be paused after upgrade of all the nodes currently in progress is completed either successfully or with failure. User can make changes in the upgrade plan when the upgrade is paused. |
POST /api/v1/upgrade/plan?action=pause
|
Reset upgrade plan to default planReset the upgrade plan to default plan. User has an option to change the default plan. But if after making changes, user wants to go back to the default plan, this is the way to do so. |
POST /api/v1/upgrade/plan?action=reset
|
Continue upgradeContinue the upgrade. Resumes the upgrade from the point where it was paused. |
POST /api/v1/upgrade/plan?action=continue
|
Get upgrade plan settings for the componentGet the upgrade plan settings for the component. |
GET /api/v1/upgrade/plan/<component_type>/settings
|
Update upgrade plan settings for the componentUpdate the upgrade plan settings for the component. |
PUT /api/v1/upgrade/plan/<component_type>/settings
|
Returns pre-upgrade checks in csv formatReturns pre-upgrade checks in csv format |
GET /api/v1/upgrade/pre-upgrade-checks?format=csv
|
Get Pre-upgrade Check FailuresGet failures resulting from the last execution of pre-upgrade checks. If the execution of checks is in progress, the response has the list of failures observed so far. |
GET /api/v1/upgrade/pre-upgrade-checks/failures
|
Get upgrade status summaryGet upgrade status summary |
GET /api/v1/upgrade/status-summary
|
Get upgrade summaryGet upgrade summary |
GET /api/v1/upgrade/summary
|
Get upgrade-coordinator upgrade statusGet upgrade-coordinator upgrade status |
GET /api/v1/upgrade/uc-upgrade-status
|
Returns information about upgrade checksReturns information of pre-upgrade and post-upgrade checks. If request parameter component type is specified, then returns information about all pre-upgrade and post-upgrade for the component. Otherwise returns information of checks across all component types. |
GET /api/v1/upgrade/upgrade-checks-info
|
Return information of all upgrade unit groupsReturn information of all upgrade unit groups in the upgrade plan. If request parameter summary is set to true, then only count of upgrade units will be returned, upgrade units list will be empty. If request parameter component type is specified, then all upgrade unit groups for that component will be returned. |
GET /api/v1/upgrade/upgrade-unit-groups
|
Create a groupCreate a group of upgrade units. |
POST /api/v1/upgrade/upgrade-unit-groups
|
Get upgrade status for upgrade unit groupsGet upgrade status for upgrade unit groups |
GET /api/v1/upgrade/upgrade-unit-groups-status
|
Delete the upgrade unit groupDelete the specified group. NOTE - A group can be deleted only if it is empty. If user tries to delete a group containing one or more upgrade units, the operation will fail and an error will be returned. |
DELETE /api/v1/upgrade/upgrade-unit-groups/<group-id>
|
Return upgrade unit group informationReturns information about a specific upgrade unit group in the upgrade plan. If request parameter summary is set to true, then only count of upgrade units will be returned, upgrade units list will be empty. |
GET /api/v1/upgrade/upgrade-unit-groups/<group-id>
|
Add upgrade units to specified upgrade unit groupAdd upgrade units to specified upgrade unit group. The upgrade units will be added at the end of the upgrade unit list. |
POST /api/v1/upgrade/upgrade-unit-groups/<group-id>?action=add_upgrade_units
|
Reorder upgrade unit groupReorder an upgrade unit group by placing it before/after the specified upgrade unit group. |
POST /api/v1/upgrade/upgrade-unit-groups/<group-id>?action=reorder
|
Update the upgrade unit groupUpdate the specified upgrade unit group. Removal of upgrade units from the group using this is not allowed. An error will be returned in that case. Following extended_configuration is supported: Key: upgrade_mode Supported values: maintenance_mode,in_place Default: maintenance_mode Key: maintenance_mode_config_vsan_mode Supported values: evacuate_all_data, ensure_object_accessibility, no_action Default: ensure_object_accessibility Key: maintenance_mode_config_evacuate_powered_off_vms Supported values: true, false Default: false Key: rebootless_upgrade Supported values: true, false Default: true |
PUT /api/v1/upgrade/upgrade-unit-groups/<group-id>
|
Get upgrade status for groupGet upgrade status for upgrade units in the specified group. User can specify whether to show only the upgrade units with errors. |
GET /api/v1/upgrade/upgrade-unit-groups/<group-id>/status
|
Reorder an upgrade unit within the upgrade unit groupReorder an upgrade unit within the upgrade unit group by placing it before/after the specified upgrade unit |
POST /api/v1/upgrade/upgrade-unit-groups/<group-id>/upgrade-unit/<upgrade-unit-id>?action=reorder
|
Return aggregate information of all upgrade unit groupsReturn information of all upgrade unit groups in the upgrade plan. If request parameter summary is set to true, then only count of upgrade units will be returned, upgrade units list will be empty. If request parameter component type is specified, then all upgrade unit groups for that component will be returned. |
GET /api/v1/upgrade/upgrade-unit-groups/aggregate-info
|
Get upgrade unitsGet upgrade units |
GET /api/v1/upgrade/upgrade-units
|
Get upgrade units statsGet upgrade units stats |
GET /api/v1/upgrade/upgrade-units-stats
|
Get a specific upgrade unitGet a specific upgrade unit |
GET /api/v1/upgrade/upgrade-units/<upgrade-unit-id>
|
Get upgrade units aggregate-infoGet upgrade units aggregate-info |
GET /api/v1/upgrade/upgrade-units/aggregate-info
|
Get the version whitelistGet whitelist of versions for different components |
GET /api/v1/upgrade/version-whitelist
|
Get the version whitelist for the specified componentGet whitelist of versions for a component. Component can include HOST, EDGE, CCP, MP |
GET /api/v1/upgrade/version-whitelist/<component_type>
|
Update the version whitelist for the specified component typeUpdate the version whitelist for the specified component type (HOST, EDGE, CCP, MP). |
PUT /api/v1/upgrade/version-whitelist/<component_type>
|