Table of Contents
Advertisement
Deploy Options
Review the options for the Deploy operation:
Specify whether to deploy the configuration in fenced mode.
Fencing is a technology that isolates or "fences" groups of machines on the same
network from other machines. For complete information on this feature and
consequences of deploying a fenced configuration after deploying it without
fencing and saving its state, see Appendix
Allow Traffic In and Out – Virtual machines can communicate with machines
outside the fence and machines outside the fence can communicate with
virtual machines in the fenced configuration.
Allow Traffic Out – Virtual machines in a fenced configuration can initiate
communication to machines outside the fence, and can receive messages back
on the same connection. Machines outside the fence cannot initiate
communication to virtual machines in the fenced configuration.
This option is useful when virtual machines need to obtain data or execute
code outside the fence (as seen with Web services or databases), but do not
want to receive messages that may disrupt testing.
Block Traffic In and Out – Network traffic does not travel across the fence.
Virtual machines in a fenced configuration cannot communicate with
machines outside of the fence, and machines outside the fence cannot
communicate with virtual machines in the fenced configuration.
This option is useful in these circumstances:
Deploying a configuration in fenced mode places all the virtual machines on a
single Managed Server system. You must have a Managed Server system
connected to the storage server where the templates that serve as the basis of this
configuration reside. The Managed Server system must have sufficient resources,
such as memory, slots, and fences.
VMware, Inc.
You are testing software viruses which need to remain isolated from the
network.
You are testing a client‐server application in isolation.
Chapter 5 Working with Configurations
C, "Network Fencing," on page 171.
87
Advertisement
Table of Contents
