Zero-based resource offset to start the response from
HPE Compute Ops Management API (latest)
HPE Compute Operations Management provides a Restful API to customers who want to manage their devices programmatically or through a command line. The API enables customers to invoke operations or tasks such as list devices, see device details, device health, and manage their device's firmware.
UPDATED API ENDPOINTS
Compute Ops Management now supports the HPE GreenLake API endpoints (<region>.api.greenlake.hpe.com
). The Guide contains more information about this change.
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/
https://us-west.api.greenlake.hpe.com/
https://eu-central.api.greenlake.hpe.com/
https://ap-northeast.api.greenlake.hpe.com/
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
OK
The path operation will be sunset and might become unresponsive anytime after this date and time.
Primary identifier for the job given by the system
The identifier of a job which triggered this job
URI to the job itself (i.e. a self link)
Automatically delete the job after it reaches the COMPLETE state.
URI to the job template this job is using
URI to the resource this job is operating against
Data needed for this job
The current state of a job, indicating whether a job is waiting, running, or terminal
{ "offset": 0, "count": 1, "total": 12, "items": [ { … } ] }
Request
Note: This path operation is going to be deprecated and sunset!
- Deprecated at:
Fri, 31 Jan 2025 23:59:59 GMT
- Sunset at :
Mon, 3 Mar 2025 23:59:59 GMT
- Successor version:
compute-ops-mgmt/v1/jobs
Create a job for a given resource. A job is a multi-step task performed by Compute Ops Manager.
This table summarizes the jobs and their template IDs. For more information about each job template, expand the Job Definitions section and click on Overview to get started.
Name | Description | Resource Type | Template ID |
---|---|---|---|
Server Power Off | Power off a server | compute-ops/server | d0c13b58-748c-461f-9a61-c0c5c71f1bb4 |
Server Power On | Power on a server | compute-ops/server | 0cbb2377-1834-488d-840c-d5bf788c34fb |
Server Restart | Restart a server | compute-ops/server | 30110551-cad6-4069-95b8-dbce9bbd8525 |
Server Cold Boot | Cold boot a server | compute-ops/server | aacfb3e0-6575-4d4f-a711-1ee1ae768407 |
Server Firmware Update | Update firmware on a server | compute-ops/server | fd54a96c-cabc-42e3-aee3-374a2d009dba |
Server iLO Firmware Update | Update iLO component firmware on a server | compute-ops/server | 94caa4ef-9ff8-4805-9e97-18a09e673b66 |
Server External Storage Details | Collect external storage details for a server | compute-ops/server | 139cc26b-ac93-4da0-826c-220d15e3a422 |
Appliance Software Update | Update OneView appliance | compute-ops/oneview-appliance | 1c4ac4be-8eeb-49f2-a86a-fd8c9182616c |
Group Firmware Update | Update firmware on servers in a group | compute-ops/group | 91159b5e-9eeb-11ec-a9da-00155dc0a0c0 |
Group Firmware Compliance | Calculate firmware compliance of servers in a group | compute-ops/group | 23b8ba2a-6c46-4223-b028-919382c7dcac |
Group Appliance Update | Update OneView appliances in a group | compute-ops/group | f69f553a-5004-4a08-9283-5b60abd9eb4a |
Group Internal Storage Configuration | Configures internal storage volume for servers in a group | compute-ops/group | c708eb57-235d-4ea8-9e21-8ceea2438773 |
Group Apply Server Setting | Apply server setting on a group | compute-ops/group | beff07ce-f36d-4699-9ac3-f872dcd63133 |
Group Apply External Storage Settings | Apply external storage settings on servers in a group | compute-ops/group | 1262f08e-79eb-4e9f-91d2-6984da9d31cd |
Group External Storage Compliance | Calculate external storage compliance of servers in a group | compute-ops/group | 977139e0-f9d9-4940-9418-e0c321b5a458 |
Carbon Footprint Report | Create carbon footprint report | compute-ops/filter | b0001d36-6490-48ac-93af-a87adfb997ed |
Collect Server Inventory | Collect complete or filtered server inventory | compute-ops/server | d6595f1b-84e6-4587-ade5-656e2a5ea20d |
Collect Server Network Connectivity | Collect server adapter port to switch port mappings | compute-ops/server | b21ca9e2-8a1b-11ee-b9d1-0242ac120002 |
Group Operating System Installation | Install operating system on servers in a group | compute-ops/group | e2952628-2629-4088-93db-91742304ef0c |
Group iLO Settings Compliance | Calculate ilo settings compliance of servers in a group | compute-ops/group | a55c8b26-3c57-4044-a4ee-1d0e3c108286 |
Content-Type header must designate 'application/json' in order for the request to be performed.
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
Job request
Identifier of the job template for this job. Supports ID(aacfb3e0-6575-4d4f-a711-1ee1ae768407) in addition to URI(/compute-ops-mgmt/v1beta3/job-templates/aacfb3e0-6575-4d4f-a711-1ee1ae768407)
Reference to the resource to run this job on
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X POST \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"jobTemplateUri": "/compute-ops-mgmt/v1beta3/job-templates/aacfb3e0-6575-4d4f-a711-1ee1ae768407",
"resourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686"
}'
Job data
The path operation will be sunset and might become unresponsive anytime after this date and time.
Primary identifier for the job given by the system
The identifier of a job which triggered this job
URI to the job itself (i.e. a self link)
Automatically delete the job after it reaches the COMPLETE state.
URI to the job template this job is using
URI to the resource this job is operating against
Data needed for this job
The current state of a job, indicating whether a job is waiting, running, or terminal
{ "id": "2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "parentJobId": "284f3b7a-7a17-4f0a-9b40-a51bc887c7d0", "type": "compute-ops-mgmt/job", "resourceUri": "/compute-ops-mgmt/v1beta3/jobs/2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "name": "FirmwareUpdate.New", "generation": 9, "deleteOnComplete": true, "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "jobTemplateUri": "/compute-ops-mgmt/v1beta2/job-templates/fd54a96c-cabc-42e3-aee3-374a2d009dba", "associatedResourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "resource": { "resourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "type": "servers" }, "data": { "state_reason_message": { … } }, "jobParams": { "property1": [], "property2": [] }, "results": { "property1": "string", "property2": "string" }, "state": "PENDING", "resultCode": {}, "status": "string", "statusDetails": {} }
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
Job data
The path operation will be sunset and might become unresponsive anytime after this date and time.
Primary identifier for the job given by the system
The identifier of a job which triggered this job
URI to the job itself (i.e. a self link)
Automatically delete the job after it reaches the COMPLETE state.
URI to the job template this job is using
URI to the resource this job is operating against
Data needed for this job
The current state of a job, indicating whether a job is waiting, running, or terminal
{ "id": "2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "parentJobId": "284f3b7a-7a17-4f0a-9b40-a51bc887c7d0", "type": "compute-ops-mgmt/job", "resourceUri": "/compute-ops-mgmt/v1beta3/jobs/2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "name": "FirmwareUpdate.New", "generation": 9, "deleteOnComplete": true, "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "jobTemplateUri": "/compute-ops-mgmt/v1beta2/job-templates/fd54a96c-cabc-42e3-aee3-374a2d009dba", "associatedResourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "resource": { "resourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "type": "servers" }, "data": { "state_reason_message": { … } }, "jobParams": { "property1": [], "property2": [] }, "results": { "property1": "string", "property2": "string" }, "state": "PENDING", "resultCode": {}, "status": "string", "statusDetails": {} }
Content-Type header must designate 'application/merge-patch+json' in order for the request to be performed.
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts
API to determine the application customer IDs for your tenant accounts.
Job update data
New state for the job (currently only Complete or Error is supported)
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for US West
https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta3/jobs/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta3/jobs/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{}'
Job data
The path operation will be sunset and might become unresponsive anytime after this date and time.
Primary identifier for the job given by the system
The identifier of a job which triggered this job
URI to the job itself (i.e. a self link)
Automatically delete the job after it reaches the COMPLETE state.
URI to the job template this job is using
URI to the resource this job is operating against
Data needed for this job
The current state of a job, indicating whether a job is waiting, running, or terminal
{ "id": "2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "parentJobId": "284f3b7a-7a17-4f0a-9b40-a51bc887c7d0", "type": "compute-ops-mgmt/job", "resourceUri": "/compute-ops-mgmt/v1beta3/jobs/2500759c-b7dd-4c68-ab7e-6b644bcf4b9c", "name": "FirmwareUpdate.New", "generation": 9, "deleteOnComplete": true, "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z", "jobTemplateUri": "/compute-ops-mgmt/v1beta2/job-templates/fd54a96c-cabc-42e3-aee3-374a2d009dba", "associatedResourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "resource": { "resourceUri": "/compute-ops-mgmt/v1beta2/servers/744674-N19+8899744674319686", "type": "servers" }, "data": { "state_reason_message": { … } }, "jobParams": { "property1": [], "property2": [] }, "results": { "property1": "string", "property2": "string" }, "state": "PENDING", "resultCode": {}, "status": "string", "statusDetails": {} }