Revision a17deeab doc/ovfconverter.rst

b/doc/ovfconverter.rst
44 44
ignore unused elements of this section, so their presence won't raise
45 45
any warnings.
46 46

  
47

  
48 47
Operating System
49 48
----------------
50 49
List of operating systems available on a cluster is viewable using
51 50
``gnt-os list`` command. When importing from external source, providing
52 51
OS type in a command line (``--os-type=...``) is **required**. This is
53
because rven if the type is given in OVF description, it is not detailed
52
because even if the type is given in OVF description, it is not detailed
54 53
enough for Ganeti to know which os-specific scripts to use.
54
Please note, that instance containing disks may only be imported using
55
OS script that supports raw disk images.
56

  
57
References
58
----------
59
Files listed in ``ovf:References`` section cannot be hyperlinks.
60

  
61

  
62
Limitations on export
63
=====================
64

  
65
Disk content
66
------------
67
Most Ganeti instances do not contain grub. This results in some
68
problems when importing to virtualization software that does expect it.
69
Examples of such software include VirtualBox and VMWare.
70

  
71
To avoid trouble, please install grub inside the instance before
72
exporting it.
73

  
74

  
75
Import to VirtualBox
76
--------------------
77
``format`` option should be set to ``vmdk`` in order for instance to be
78
importable by VirtualBox.
79

  
80
Tests using existing versions of VirtualBox (3.16) suggest, that
81
VirtualBox does not support disk compression or OVA packaging. In future
82
versions this might change.
83

  
84

  
85
Import to VMWare
86
----------------
87
Importing Ganeti instance to VMWare was tested using ``ovftool``.
88

  
89
``format`` option should be set to ``vmdk`` in order for instance to be
90
importable by VMWare.
91

  
92
Presence of Ganeti section does seem to cause some problems and
93
therefore it is recommended to use ``--external`` option on export.
94

  
95
Import of compressed disks generated by ovfconverter was impossible in
96
current version of ``ovftool`` (2.1.0). This seems to be related to old
97
``vmdk`` version. Since the conversion to ``vmdk`` format is done using
98
``qemu-img``, it is possible and in fact expected, that future versions
99
of the latter tool will resolve this problem.
55 100

  
56 101

  
57 102
Import examples
......
130 175
Known issues
131 176
============
132 177

  
133
Export
134
------
135
When exporting to **VirtualBox**, you may encounter errors regarding
136
network. If that is the case, simply change the network type in options
137
to ``NAT``.
178
Conversion errors
179
-----------------
180
If you are encountering trouble when converting the disk, please ensure
181
that you have newest ``qemu-img`` version.
182

  
183
OVA and compression
184
-------------------
185
The compressed disks and OVA packaging do not work correctly in either
186
VirtualBox (old version) or VMWare.
187

  
188
VirtualBox (3.16 OSE) does not seem to support those two, so there is
189
very little we can do about this.
190

  
191
As for VMWare, the reason behind it not accepting compressed or packed
192
instances created by ovfconverter seems to be related to the old vmdk
193
version.
194

  
195
Problems on newest VirtualBox
196
-----------------------------
197
In Oracle VM Virtualbox 4.0+ there seems to be a problem when importing
198
any OVF instance created by ovfconverter. Reasons are again unknown,
199
this will be investigated.
200

  
201
Disk space
202
----------
203
The disk space requirements for both import and export are at the moment
204
very large - we require free space up to about 3-4 times the size of
205
disks. This will most likely be changed in future versions.
138 206

  
139 207

  
140 208
.. vim: set textwidth=72 :

Also available in: Unified diff