topic Re: vCenter REST API - deploy from ovf template in VMware vCenter™ Discussions

vCenter REST API - deploy from ovf template

Larch — Tue, 26 Feb 2019 14:29:11 GMT

Hello everyone

I am trying to deploy from an ovf template. The following body with the "/com/vmware/vcenter/ovf/library-item/id:{ovf_library_item_id}?~action=deploy" function is already working.

{

"deployment_spec": {

"accept_all_EULA": true,

"default_datastore_id": "datastore-30598",

"network_mappings": [

{

"key": "4000",

"value": "network-154"

}

"name": "AATest08"

"target": {

"folder_id": "group-v5920",

"host_id": "host-1934",

"resource_pool_id": "resgroup-43"

}

My problem is, that the network parameters (marked in red) are getting completly ignored. How can i fix that? What am i doing wrong?

Sadly, i cant find any examples on the web. I hope you guys can help me out.

Michael

Re: vCenter REST API - deploy from ovf template

vmrale — Thu, 28 Feb 2019 13:44:14 GMT

Hi,

did You check if this Port Group related with MOiD "network-154" exists on a host?

Re: vCenter REST API - deploy from ovf template

Larch — Tue, 12 Mar 2019 08:35:38 GMT

Hi vmrale

Thank you for the response.

Yes the Network-154 is in the Port-Group of the Host i used to depoy the template.

I will contact the vmWare support and post the solution here.

Re: vCenter REST API - deploy from ovf template

avseelam — Mon, 18 Mar 2019 13:16:51 GMT

Do you have any response from VMware. I am having similar issue while deploying library item from API

Re: vCenter REST API - deploy from ovf template

Larch — Tue, 19 Mar 2019 07:07:34 GMT

I dont have any response. But my workaround is to change the network after the deployment.

Helpf for changing the network of an existing VM: REST API - update_spec

Re: vCenter REST API - deploy from ovf template

avseelam — Tue, 19 Mar 2019 07:24:01 GMT

update the key to original portgroup name of library item instead of 4000. That did the trick however I cannot use the same code in vRO as it is throwing Java map errors