This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
/
configuring_vmware.dita
359 lines (354 loc) · 12.1 KB
/
configuring_vmware.dita
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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
<?xml version="1.0" encoding="UTF-8"?>
<!--This work by Eucalyptus Systems is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. See the accompanying LICENSE file for more information.-->
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
<task id="configuring_vmware" otherprops="subscription">
<title>Configure VMware</title>
<shortdesc/>
<prolog>
<metadata>
<keywords>
<indexterm>VMware <indexterm>configuring</indexterm>
</indexterm>
</keywords>
</metadata>
</prolog>
<!--Test -->
<taskbody>
<context>
<note type="tip">VMware support is available by subscription only.
If you are not using VMware, skip this section.</note>
<p>The easiest way to configure vSphere for Eucalyptus is to give
Eucalyptus unrestricted access to all vSphere endpoint(s). This
way does not require complex modifications to local access
permission settings. You can grant this access to Eucalyptus by
using an existing administrative account and password or by
creating a new account for Eucalyptus and associating it with
vSphere’s standard Administrator role at the top level of the
vSphere hierarchy as seen in the vSphere client.</p>
<image href="images/vmware_assign_permissions.png" scale="90"
alt="Assing Persmissions windows"/>
<p>To give a more limited amount of control to Eucalyptus over your
vSphere infrastructure managed by a vCenter server, create one
new user and two new roles as described next.</p>
</context>
</taskbody>
<task id="vmware_create_user">
<title>Create New User</title>
<shortdesc/>
<taskbody>
<context>
<p>To give the minimal required amount of control to Eucalyptus
over your vSphere infrastructure managed on vCenter, create
one new user and two new roles. The new user and its
password will be used for granting Eucalyptus access to the
infrastructure.</p>
</context>
<steps>
<step>
<cmd>Create a user (e.g., named
<userinput>eucalyptus</userinput>) on the system
where vCenter server is running.</cmd>
</step>
<step>
<cmd>Create a role (e.g., named <userinput>Eucalyptus
vSphere</userinput>), for use at the top level of
the vSphere hierarchy, with the following
privileges:</cmd>
<info><ul>
<li>Global<ul>
<li>Licenses</li>
</ul></li>
</ul></info>
</step>
<step>
<cmd>Create a role (e.g., named
<userinput>Eucalyptus</userinput>), for use with
vSphere resources to be used by Eucalyptus, with the
following privileges:</cmd>
<info><ul>
<li>Datastore<ul>
<li>Allocate Space</li>
<li>Browser Datastore</li>
<li>Low level file operations</li>
</ul></li>
<li>Folder<ul>
<li>Create folder</li>
</ul></li>
<li>Host<ul>
<li>Configuration <ul>
<li>Network Configuration</li>
<li>Storage partition configuration</li>
</ul></li>
</ul></li>
<li>Network<ul>
<li>Assign network</li>
<li>Remove</li>
</ul></li>
<li>Resource<ul>
<li>Assign Virtual Machine to Resource
Pool</li>
</ul></li>
<li>Virtual Machine<ul>
<li>(all Virtual Machine permissions)</li>
</ul></li>
</ul></info>
</step>
<step>
<cmd>Associate the user with the top-level role</cmd>
<substeps>
<substep>
<cmd>Right-click on the top-level resource, named
after vCenter, and select <uicontrol>Add
Permission...</uicontrol></cmd>
</substep>
<substep>
<cmd>In <uicontrol>Users and groups</uicontrol>
section click
<uicontrol>Add...</uicontrol></cmd>
</substep>
<substep>
<cmd>Add user <userinput>eucalyptus</userinput> with
assigned role <userinput>Eucalyptus
vSphere</userinput> and <uicontrol>Propagate
to Child Objects</uicontrol> set to
<uicontrol>No</uicontrol></cmd>
</substep>
</substeps>
</step>
<step>
<cmd>Associate the user with the resource-level role</cmd>
<info>For each resource or collection of resources that you
want Eucalyptus to use, the
<userinput>eucalyptus</userinput> user must be given
sufficient privileges by using the
<userinput>Eucalyptus</userinput> role. For example,
you can create a new virtual datacenter for Eucalyptus
to use, add to it the relevant hosts or clusters, and
assign the <userinput>eucalyptus</userinput> user
<userinput>Eucalyptus</userinput> role just for that
datacenter.</info>
<substeps>
<substep>
<cmd>Right-click on each of the resources to be used
by Eucalyptus and select <uicontrol>Add
Permission...</uicontrol></cmd>
</substep>
<substep>
<cmd>In <uicontrol>Users and groups</uicontrol>
section click
<uicontrol>Add...</uicontrol></cmd>
</substep>
<substep>
<cmd>Add user <userinput>eucalyptus</userinput> with
assigned role <userinput>Eucalyptus</userinput>
and <uicontrol>Propagate to Child
Objects</uicontrol> set to
<uicontrol>Yes</uicontrol></cmd>
</substep>
</substeps>
</step>
</steps>
<postreq>You're now ready to set up a datastore.</postreq>
</taskbody>
</task>
<task id="configuring_vmware_datastore">
<title>Set Up a Datastore</title>
<shortdesc/>
<taskbody>
<context>
<p>Each node requires at least one datastore (either local or
one shared by multiple nodes). If more than one datastore is
available to a node, Eucalyptus will choose the datastore
arbitrarily. If Eucalyptus is to be restricted in its use of
available datastores, specify a datastore in Eucalyptus’s
configuration for VMware.</p>
<p>To determine the datastores that are available on a host,
perform the following steps with vSphere client referencing
either at vCenter Server or at a specific ESX/ESXi node:</p>
</context>
<steps>
<step>
<cmd>Choose a host in left-hand-side panel.</cmd>
</step>
<step>
<cmd>Click the <uicontrol>Configuration</uicontrol>
tab.</cmd>
</step>
<step>
<cmd>Click <uicontrol>Storage</uicontrol> in the secondary
left-hand side panel.</cmd>
</step>
<step>
<cmd>Click <uicontrol>View: Datastores</uicontrol> at the
top of the panel.</cmd>
</step>
</steps>
<postreq>You're now ready to create a network.</postreq>
</taskbody>
</task>
<task id="configuring_vmware_network">
<title>Create a Network</title>
<shortdesc/>
<taskbody>
<context>
<p>Each node must have a network reachable by the node running
the Eucalyptus VMware Broker.</p>
<note type="tip">If more than one network is available, specify
the network name in Eucalyptus configuration explicitly.
Eucalyptus assumes that this network resides on the switch
named "vSwitch0".</note>
<p>To check the network settings and create a network (if
necessary) perform the following steps with vSphere client
pointed either at vCenter Server or at a particular ESX/ESXi
node:</p>
</context>
<steps>
<step>
<cmd>Click a host in left-hand side panel.</cmd>
</step>
<step>
<cmd>Click the <uicontrol>Configuration</uicontrol>
tab.</cmd>
</step>
<step>
<cmd>Click <uicontrol>Networking</uicontrol> in the
secondary left-hand-side panel.</cmd>
</step>
<step>
<cmd>If there is no VM Network in the list, add it by
performing these steps:</cmd>
<substeps>
<substep>
<cmd>Click <uicontrol>Add Networking...</uicontrol>
in the upper-right corner.</cmd>
</substep>
<substep>
<cmd>Click <uicontrol>Virtual Machine</uicontrol>
and click <uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Click a switch (e.g., <uicontrol>Use
vSwitch0</uicontrol>) and click
<uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Enter <uicontrol>VM Network for Network
Label</uicontrol>, leave <uicontrol>VLAN
ID</uicontrol> blank, and click
<uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Check the summary and click
<uicontrol>Finish</uicontrol>.</cmd>
</substep>
</substeps>
</step>
</steps>
</taskbody>
</task>
<task id="configuring_vmware_ebs">
<title>Enable EBS Support</title>
<shortdesc/>
<taskbody>
<context>
<p>To enable VMware support for dynamic block volume support
(like Amazon’s Elastic Block Store) in Eucalyptus, configure
each of the ESX/ESXi nodes in your infrastructure to support
iSCSI. Given a node that is licensed for iSCSI support, this
amounts to enabling and configuring the gateway for the
VMkernel network. To accomplish that, perform the following
steps with vSphere client pointed either at vCenter or at a
particular ESX/ESXi node:</p>
</context>
<steps>
<step>
<cmd>Click a host in left-hand-side panel.</cmd>
</step>
<step>
<cmd>Click the <uicontrol>Configuration</uicontrol>
tab.</cmd>
</step>
<step>
<cmd>Select <uicontrol>Networking</uicontrol> in the
secondary left-hand-side panel.</cmd>
</step>
<step>
<cmd>If there is no <uicontrol>VMkernel</uicontrol> network
listed, add it by performing the following tasks:</cmd>
<substeps>
<substep>
<cmd>Click <uicontrol>Add Networking...</uicontrol>
in the upper-right corner.</cmd>
</substep>
<substep>
<cmd>Click <uicontrol>VMkernel</uicontrol> and click
<uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Click a switch (e.g., <uicontrol>Use
vSwitch0</uicontrol>) and click
<uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Click the label <uicontrol>VLAN ID</uicontrol>
and make sure that
<uicontrol>None(0)</uicontrol> is selected,
then click <uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Choose either dynamic network config or static
IP assignment, depending on your environment.
When your are done, click
<uicontrol>Next</uicontrol>.</cmd>
</substep>
<substep>
<cmd>Click <uicontrol>Finish</uicontrol>.</cmd>
</substep>
</substeps>
</step>
<step>
<cmd>Click <uicontrol>DNS and Routing</uicontrol> in the
secondary left-hand-side panel.</cmd>
</step>
<step>
<cmd>If VMkernel does not have a gateway, add it by
performing these steps:</cmd>
<substeps>
<substep>
<cmd>Click <uicontrol>Properties...</uicontrol> in
upper-right corner.</cmd>
</substep>
<substep>
<cmd>Click the <uicontrol>Routing</uicontrol> tab,
enter the gateway's IP, and click
<uicontrol>OK</uicontrol>.</cmd>
</substep>
</substeps>
</step>
</steps>
<postreq>For more information about configuring vSphere, go to the
VMware website at <xref format="html"
href="http://www.vmware.com/support/pubs/vs_pubs.html"
>http://www.vmware.com/support/pubs/vs_pubs.html</xref>.</postreq>
</taskbody>
</task>
<task id="configuring_vmware_tools">
<title>Install VMware Tools</title>
<shortdesc/>
<taskbody>
<context>
<p>Ensure that VMware Tools are installed in the images that
will be installed and run within the Eucalyptus cloud. These
tools allow Eucalyptus to discover an instance’s IP address
in System networking mode. They also are required for using
the <cmdname>euca-bundle-instance</cmdname> command when
running Windows VMs in Eucalyptus, since VMware Tools enable
clean shutdown of VMs from outside the instance. For
information about installing VMware Tools, go to the VMware
documentation at <xref format="html"
href="http://www.vmware.com"
>http://www.vmware.com</xref>.</p>
</context>
</taskbody>
</task>
</task>