Specifications

Organizing Your Inventory 6
Plan how you will set up your virtual infrastructure. A large vSphere implementation might contain several
virtual datacenters with a complex arrangement of hosts, clusters, resource pools, and networks. It might
involve multiple vSphere Servers operating in Linked Mode. Smaller implementations might require a single
virtual datacenter with a much less complex topology. Regardless of the scale of your virtual infrastructure,
consider how the virtual machines it will support are going to be used and administered.
Here are questions you should answer as you create and organize an inventory of virtual objects:
n
Will some virtual machines require dedicated resources?
n
Will some virtual machines experience periodic spikes in workload?
n
Will some virtual machines need to be administered as a group?
n
Do you want to use multiple Distributed Switches?
n
Do you want to use vMotion and Distributed Resource Management with certain virtual machines but
not others?
n
Will some virtual objects require one set of system permissions, while other objects will require a different
set of permissions?
The left pane of the vSphere Client displays your vSphere inventory. You can add and arrange objects in any
way with the following restrictions:
n
The name of an inventory object must be unique with its parent.
n
vApp names must be unique within the Virtual Machines and Templates view.
n
System permissions are inherited and cascade.
Populating and organizing your inventory involves the following activities:
This chapter includes the following topics:
n
“Create Datacenters,” on page 58
n
“Add Hosts,” on page 58
n
“Create Clusters,” on page 59
n
“Create Resource Pools,” on page 60
n
“Create a Resource Pool in the vSphere Web Client,” on page 60
n
“Create a Folder in the vSphere Web Client,” on page 61
n
“Create Datastores,” on page 61
n
“Create Host-Wide Networks,” on page 62
VMware, Inc.
57