topic Re: REST API assign server profile from a template in HPE OneView

REST API assign server profile from a template

BradV — Tue, 30 Jul 2019 16:46:29 GMT

Can someone point me to the correct API? I have a server profile template defined. I want to use that to assign/create a server profile for a given server. Not finding the correct reference.

Re: REST API assign server profile from a template

DaveArko — Tue, 30 Jul 2019 19:57:16 GMT

The API you are looking for is documented in the server-profile-templates section of the API docs:

GET /rest/server-profile-templates/{id}/new-profile

"A profile object will be returned with the configuration based on this template. Specify the profile name and server hardware to assign. If template has any fibre channel connection which is configured to boot from user defined targets but boot target is not specified in template, then boot target must be specified for that connection during creation of profile. This profile object can subsequently be used for the POST https://{appl}/rest/server-profiles/ API."

So basically you will do a GET using this path (with {id} of that of your template), and then modify it as needed (with the server-hardware URI, etc), then POST it back to /rest/server-profiles to create and assign the profile.

Re: REST API assign server profile from a template

BradV — Wed, 31 Jul 2019 09:12:01 GMT

Thanks, but how does one identify the UUID? It says: "Retrieves a server profile template managed by the appliance based on its UUID." However, when I execute: GET ${OneView}/rest/server-profile-templates, I don't see anything labeled as UUID. Would the UUID be the last part of the URI? OK, I just tested that and it works. I think HPE needs to point that out in the API reference and/or modify the API to return the UUID as a seperate value. Thanks again!

Re: REST API assign server profile from a template

DaveArko — Wed, 31 Jul 2019 16:31:03 GMT

I see your point - docs are using UUID and {Id} interchangeably. I submitted a request to have this improved. Thanks for your feedback!

Re: REST API assign server profile from a template

BradV — Wed, 07 Aug 2019 12:49:14 GMT

When I try this, what am I supposed to get back? The name is null. Uri is null. state says creating. taskuri is null. I look in the gui and there is no new server profile created. I do get back a json that looks like a server profile, but no "handle" that I can see to use to apply this new profile to a host.

Re: REST API assign server profile from a template

DaveArko — Wed, 07 Aug 2019 16:49:27 GMT

When you do a GET on https://<ov-appliance//rest/server-profile-templates/<templante-id>/new-profile you get back a profile object that needs some modifications. You need to fill in the missing info such as the "serverHardwareUri" (which you get from the server-hardare list). And "name". I just tried a simple template, and those were the two required things to fill in.

Then do a POST with that object to https://<ov-appliance>/rest/server-profiles and it should apply it to the server-hardware that you set via the serverHardwareUri attribute in the object.

You can ignore the state/taskuri, etc.

Re: REST API assign server profile from a template

BradV — Thu, 08 Aug 2019 11:11:29 GMT

Oh! That was not at all clear! Thanks! Most of the other functions return a task uri that you then reference. I was expecting something like that or an object reference, not the actual object. I'll work on that and see if I can implement properly.

Thanks!

Re: REST API assign server profile from a template

BradV — Wed, 08 Apr 2020 14:15:04 GMT

Finally got back to this. Did the following:

NEWPROF=$(curl --insecure \ --header "X-API-Version" ${currentVersion}" \ --header "auth: ${sessionID}" \ --request GET ${OneView}/rest/server-profile-templates/<id>/new-profile) # The variable HARDW points to a file where I have extracted all of the hardware from OneView DATA2=$(jq -r '.members[] | select(.serverName=="myservername")' ${HARDW} HRDWURI=$(echo ${DATA2} | jq -r '.uri') NAM=$(echo ${DATA2} | jq -r '.name') NEWPROF=$(echo ${NEWPROF} | sed -e "s|\name\":\)null|\1\"${NAM}\"|") NEWPROF=$(echo ${NEWPROF} | sed -e "s|\serverHardwareUri\":\)null|\1\"${HRDWURI}\"|") curl --insecure --header "X-API-Version" ${currentVersion}" \ --header "auth: ${sessionID}" \ --header "content-type: application/json" \ --include \ --data "${NEWPROF}" \ --request POST ${OneView}/rest/server-profiles

and I get back

parse error: Invalid numeric literal at line 1, column 9

I echoed ${NEWPROF} | jq -r '.' and it parses just fine. Any idea what might be wrong?