Comments on: vCloud Automation Center network selection during VM request

By: Manish

Manish — Wed, 09 Dec 2015 18:13:01 +0000

Hi Magnus – Can i use property dictionary to edit the default size of primary base disk eg: C drive. The point is – I can edit the base volume while requesting from catalog but ofcourse VM gets provisioned with the blueprint defined size and not the size i edit while requesting VM. Thanks !

By: Darren

Darren — Mon, 24 Aug 2015 05:54:06 +0000

In reply to magander3.

Thanks Magnus – that’s good news – I look forward to your blog post regarding the vRA VM renaming.

The same should apply to the renaming of a vCloud vApp deployment – as when the vCloud vApp blueprint gets deployed, with its multiple component blueprints, it too is forced to use a machine prefix, when I would prefer a naming convention that does not increments numbers.

Thanks
Darren

By: magander3

magander3 — Thu, 20 Aug 2015 19:00:53 +0000

In reply to Darren.

Hi Darren,
this is absolutely possible. you need to intercept the vRA provisioning and e.g. push the naming convention to vCO.
If you need assistance with this i’m sure we can work something out but i will most likely not write a blog post about it any time soon.

//Magnus

By: Darren

Darren — Thu, 20 Aug 2015 14:55:05 +0000

Hi magander3

Thank you for the article. Please could you elaborate on this further to include instructions how to rename a vRA 6.2 VM at time of provisioning to something that removes the compulsory machine prefix.

Or better yet, how can make machine prefix a non-compulsory requirement?

I am provisioning vApps from my vCloud Director endpoint using the vAppCloneWorkflow in the Blueprint, but I am forced to append a machine prefix onto the VM name, when this is not required, as vCloud automatically appends a GUID onto the name anyway, so do not need 001, 002, 003 appended to VM name.

Thanks in advance
Darren

By: magander3

magander3 — Fri, 09 Jan 2015 23:26:36 +0000

In reply to Ahmed Naguib.

Hi,
really don’t know what exactly you mean. You can only connect the VirtualMachine.NetworkN.Name to one vCAC Network Path. You can add several Network Paths to a VM by adding several VirtualMachine.NetworkN.Name (just change N to 0 for the first one, to 1 for the second one and so on).

vCAC Network Profiles can be used to determine from which internal vCAC Network Profile the VirtualMachine.NetworkN.Name will receive it’s IP address from.

You donate need to use both these anymore in vRA 6.2, it’s enough with VirtualMachine.NetworkN.NetworkProfileName.
See more here, http://magander.se/2014/12/09/vcloud-automation-center-virtualmachine-network-property-definition-changes/

//Magnus

By: Ahmed Naguib

Ahmed Naguib — Fri, 09 Jan 2015 15:23:18 +0000

What about the network paths, for example if I have three network profile, and each connected to a different path… Say I was able to click the check box – in reservation page – for the three network paths I have, and selected the correct network profile from the drop down list, beside each relevant network path.

Will vcac assign automatically the VMs to the correct path, or I have to also add a specific custom property for this ?

By: vCloud Automation Center 6.1 VirtualMachine.Network Property Definition changes | VCDX56

Tue, 09 Dec 2014 12:44:12 +0000

[…] A couple of moths back i wrote an article about how to select virtual machine (VM) network placement while deploying a VM via vCloud Automation Center (vCAC) soon to be renamed to vRealize Automation (vRA). You can find the blog post here. […]

By: magander3

magander3 — Fri, 21 Nov 2014 06:52:32 +0000

Gr8, give me an hour & and take a look //Magnus

By: Swaroop

Swaroop — Fri, 21 Nov 2014 05:52:12 +0000

In reply to magander3. I have mailed you the screenshots. Please have a look at it.

By: magander3

magander3 — Wed, 19 Nov 2014 09:41:49 +0000

Yeah, that’ll be fine.

//Magnus

By: Swaroop

Swaroop — Wed, 19 Nov 2014 07:14:36 +0000

In reply to magander3. Can I send you the screen shot? Can I mail to your Email-ID mentioned in your CV?

By: magander3

magander3 — Mon, 17 Nov 2014 07:22:08 +0000

In reply to Swaroop.

Hi,
can you send me the build profile, property dictionary, property attribute config via the author page and i can have a look?

//Magnus

By: Swaroop

Swaroop — Mon, 17 Nov 2014 06:24:12 +0000

Hi Magnus,
Thanks for this amazing piece of information. Just found out something strange while I was implementing this in the environment. I run on vCAC 6.1. I have got the Networks as drop down. If I provision VM by selecting the network in drop down, it takes IP from the particular network which is absolutely correct. When I view the VM details under Items tab in vCAC, in the Network tab I don’t see the IP of that VM. But in the vSphere, I see that VM has taken a correct IP. When I check the Network Profiles in the vCAC, I don’t see that status of that IP as “Allocated”.
If I provison a VM without dropdowns for selecting network (conventional method I meant), it works fine and I can see the IP in the Network Profiles and In the Machine Information as well.
Hope you can help me out on this!!

By: lexone27

lexone27 — Mon, 10 Nov 2014 14:48:42 +0000

OK email has been sent – awaiting your reply so I can provide screen shots. Thank you!

By: magander3

magander3 — Mon, 10 Nov 2014 07:44:23 +0000

In reply to Alex López  (@CoquiPR81).

Hi, ok sounds strange. Can you email me via the author page and i’ll reply requisition a few print screens from your environment?

thanks

//Magnus

By: Alex López  (@CoquiPR81)

Alex López  (@CoquiPR81) — Mon, 10 Nov 2014 05:53:49 +0000

Hi, yes you are correct. Using no custom network properties results in a DHCP address being assigned to the VM. Using custom network properties results in no DHCP address being assigned to the VM.