POST /profiles/<id>

Use the POST method to activate a profile on a target system by assigning an inactive server profile to a target server or redeploying a server profile that is active, pending, or failed activation.


Authentication with user name and password is required.

Request URL

POST https://<management_server_IP>/profiles/<id>

where <id> is the unique ID of the server profile that was assigned when the server pattern was deployed. To obtain the server profile ID, use the GET /profiles method.

Query parameters


Request body

Attributes Required / Optional Type Description
restart Required String Indicates when to restart the server to activate the profile. This can be one of the following values.
  • immediate. Restart the server and completes the activation immediately.
  • defer. Does not restart the server. Activate is completed after the server is manually restarted.
uuid Required if the server profile is inactive (not assigned); otherwise, optional String For a rack or tower server, this is the UUID of the target server.

For a Flex System server, this is the location ID of the target server.

Important: An assigned server profile (in the active, pending, or failed activation state) can be redeployed only to the server to which the profile is currently assigned. If you do not specify the uuid attribute for an assigned server profile, the target-server UUID is retrieved from the server profile. If you specified the uuid attribute for an assigned server profile, the specified UUID must match the UUID of the current target server.

Request example

   "restart": "defer",
   "uuid": "1B54B9AEFCE04D5E820C0B6310D03590_bay3"

Response codes

Code Description
200 OK The profile was deployed successfully.
400 Bad request. The request body was not formatted correctly.
404 Not found. The profile <id> does not exist.
500 Internal server error

Response body