VMware VLM3-ENG-CP User Guide - Page 87

Deploy Options, Deploy, Allow Traffic In and Out

Page 87 highlights

Chapter 5 Working with Configurations 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 C, "Network Fencing," on page 171. „ 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: „ You are testing software viruses which need to remain isolated from the network. „ You are testing a client‐server application in isolation. 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. 87

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

VMware, Inc.
87
Chapter 5
Working with Configurations
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 C, “Network Fencing,”
on page 171.
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:
You are testing software viruses which need to remain isolated from the
network.
You are testing a client
server application in isolation.
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.