VMware Cloud Community
shay009
Contributor
Contributor

adding vdc network to vm in vco 5.1 ( migration issue )

i am not able to add / update vdc org network to vm in vco 5.1

following code was working in vco 4.2.3

task = System.getModule("com.vmware.library.vCloud.vApp.VM").wireVM(
vm,nicNumber,vAppNetworkName,ipAddressingMode,ipAddress,isConnected,macAddress,needsCustomization) ;

but now it is giving exception "network not found".

do i need now to create vApp network first seperate to vdc network?

or is there any other way arround to do it?

thanks in advance for your help

Reply
0 Kudos
6 Replies
cdecanini_
VMware Employee
VMware Employee

You must have upgraded vCloud / the vCloud plug-in to 5.1, right ?

With vCD 5.1 it is necessary to create a vApp network first (there is a library workflow for that) and bind it to the organization VDC network.

There is no other way around it.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
shay009
Contributor
Contributor

yes we have installed a plugin vCloud plug-in to 5.1

I too think we are now forced to create a vApp network first I don't know why Smiley Sad

Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

There were some changes in the API at the network level. For example before you had Organization Networks and not Organization VDC networks.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Burke-
VMware Employee
VMware Employee

Start by using the "Add a vApp Network" workflow - this will allow you to get something into your vApp to connect your VMs to. When you add it, set the fenceMode to Bridged. Once you have done that, then you can take that new vAppNetwork and connect the VM(s) to it using the "Wire a virtual machine network" workflow. These are the steps required when working through the api as the plug-in does. WIthin the vCD UI, this is what is done behind the scenes when you tell a VM to connect to an Org vDC Network.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
atauber
VMware Employee
VMware Employee

I've run into a similar issue after we upgraded to vCD 5.1 - the "WireVM" section of our orchestrator workflow no longer works.  What troubles me is that we did not upgrade the Orchestrator vCD plug-in.  We are still using the vCD 1.5 plug-in which I assume should allow our workflows to work.  Is this a bug?

Reply
0 Kudos
Burke-
VMware Employee
VMware Employee

I advise against using the 1.5 plug-in with vCloud Director 5.x due to the numerous changes in the api and object changes.. in particular, the older workflows try connecting to vCloud Organization Networks and the newer one connects to Org VDC Networks - different objects from vCO (and API) point of view.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
Reply
0 Kudos