You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/templates.rst
+10-23Lines changed: 10 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,11 +177,6 @@ as the prototype for other VMs.
177
177
5.4 to support a CentOS 6.2 image will in general not work.
178
178
In those cases you should choose Other.
179
179
180
-
.. note::
181
-
Since version 4.15, VMware templates do not allow users or administrators
182
-
selecting an OS Type when registering a template. The OS Type is
183
-
obtained from the template after it is registered.
184
-
185
180
186
181
- **Public**. Choose Yes to make this template accessible to all
187
182
users of this CloudStack installation. The template will appear in
@@ -198,13 +193,6 @@ The new template will be visible in the Templates section when the
198
193
template creation process has been completed. The template is then
199
194
available when creating a new VM.
200
195
201
-
.. note::
202
-
Since version 4.15, CloudStack obtains information from the VMware templates
203
-
automatically at registration time. If a template contains different deployment
204
-
options (or configurations) as in the case of virtual appliances, then CloudStack
205
-
display the information required by the template, allowing users or administrators
206
-
to configure their instances.
207
-
208
196
Creating a Template from a Snapshot
209
197
-----------------------------------
210
198
@@ -249,7 +237,12 @@ To upload a template:
249
237
available, or All Zones to make it available throughout
250
238
CloudStack.
251
239
252
-
- **OS Type**: (Except for VMware). This helps CloudStack and the hypervisor perform
240
+
- **Read VM settings from OVA**. (VMware only) If selected, the registered template will allow users to deploy VMs as clones of the template, including all their properties, configurations, end-user license agreements, disks, os type, etc. This option allows users to register virtual appliances. See `Support for Virtual Appliances <virtual_machines.html#about-virtual-appliances>`_.
241
+
242
+
.. note::
243
+
When this option is selected the following fields are hidden: Root disk controller, Keyboard type and OS Type.
244
+
245
+
- **OS Type**: This helps CloudStack and the hypervisor perform
253
246
certain operations and make assumptions that improve the
254
247
performance of the guest. Select one of the following:
255
248
@@ -264,8 +257,8 @@ To upload a template:
264
257
those cases you should choose Other.
265
258
266
259
.. note::
267
-
Since version 4.15, VMware templates do not allow users or administrators
268
-
selecting an OS Type when registering a template. The OS Type is
260
+
Since version 4.15.1, VMware templates do not allow users or administrators
261
+
selecting an OS Type when registering a template if the option 'Read VM settings from OVA' is selected. In this case, the OS Type is
269
262
obtained from the template after it is registered.
270
263
271
264
- **Hypervisor**: The supported hypervisors are listed. Select the
@@ -295,10 +288,9 @@ To upload a template:
295
288
Note that uploading multi-disk templates is also supported.
296
289
297
290
.. note::
298
-
VMware only: If the selected template contains OVF properties, different deployment options or configurations,
299
-
multiple NICs or end-user license agreements, then the wizard will display these properties.
291
+
VMware only: If the template is registered with the option 'Read VM settings from OVA' then the VM deployment wizard will display all the available OVF properties, different deployment options or configurations, multiple NICs or end-user license agreements.
300
292
301
-
See `“Support for Virtual Appliances”<virtual_machines.html#support-for-virtual-appliances>`_.
293
+
See `Support for Virtual Appliances <virtual_machines.html#about-virtual-appliances>`_.
302
294
303
295
304
296
@@ -314,11 +306,6 @@ The steps are similar as when Uploading a template/ISO from a remote HTTP server
314
306
For this feature to work, your SSVMs must be supporting HTTPS (for more info please visit `“Using a SSL Certificate for the Console Proxy”
Copy file name to clipboardExpand all lines: source/adminguide/virtual_machines/virtual_appliances.rst
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,18 @@
1
+
.. Licensed to the Apache Software Foundation (ASF) under one
2
+
or more contributor license agreements. See the NOTICE file
3
+
distributed with this work for additional information#
4
+
regarding copyright ownership. The ASF licenses this file
5
+
to you under the Apache License, Version 2.0 (the
6
+
"License"); you may not use this file except in compliance
7
+
with the License. You may obtain a copy of the License at
8
+
http://www.apache.org/licenses/LICENSE-2.0
9
+
Unless required by applicable law or agreed to in writing,
10
+
software distributed under the License is distributed on an
11
+
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
12
+
KIND, either express or implied. See the License for the
13
+
specific language governing permissions and limitations
14
+
under the License.
15
+
1
16
About Virtual Appliances
2
17
------------------------
3
18
@@ -8,9 +23,7 @@ An OVA file contain disc images, as well as the configuration data of the virtua
8
23
Virtual Appliances are supported only on VMware.
9
24
10
25
.. note::
11
-
Since version 4.15, all the new templates registered are treated as virtual appliance templates.
12
-
13
-
To keep the existing functionality, all the templates registered before version 4.15 are not affected by this changes.
26
+
Since version 4.15.1, administrators and users can register virtual appliance templates by selecting the option 'Read VM Settings from OVA' on the template registration.
0 commit comments