vCloud vApp Design considerations – Part 1

This is carrying on from my session at PEX that I presented with Hugo Phan. A few people have asked if I could provide some information of vApp Use Cases, and what design considerations are involved in this.  This is part 1 of a 4 part article.

So lets start off with some logical considerations

vApp Logical Design

The list below shows some of the basic design considerations that you need to consider when putting together your vApp.

• Use the latest version of VMware Tools
• Select 1 vCPU as a default UNLESS specifically required
• Use VMXNET3 network adapters where applicable
• Secure Virtual Machines as you would standard VMs or physical
• Use standard Virtual Machine naming conventions
• Virtual Hardware version – CPU intensive workloads require HW version 9

One thing that people also need to bear in mind (and has been mentioned many times previously) is that a vCloud vApp is different to a vSphere vApp. A vCloud vApp is a container for a distributed software solution

vApp Network Design Considerations

A vApp network consumes resources from a network pool.  The following rules apply

• Created Dynamically if vApp is fenced
• Created Manually for connection to an organization network (Internal or External)

Part 2 can be read by clicking here