Revision a17deeab doc/design-ovf-support.rst
| b/doc/design-ovf-support.rst | ||
|---|---|---|
| 85 | 85 |
|
| 86 | 86 |
In our implementation of the OVF we allow a choice between raw, cow and |
| 87 | 87 |
vmdk disk formats for both import and export. Other formats covertable |
| 88 |
using ``qemu-img`` are allowed, but not tested. |
|
| 88 |
using ``qemu-img`` are allowed in import mode, but not tested.
|
|
| 89 | 89 |
The justification is the following: |
| 90 | 90 |
|
| 91 | 91 |
- Raw format is supported as it is the main format of disk images used |
| ... | ... | |
| 250 | 250 |
|
| 251 | 251 |
As mentioned, Ganeti will allow export in ``raw``, ``cow`` and ``vmdk`` |
| 252 | 252 |
formats. This means i.e. that the appropriate ``ovf:format`` |
| 253 |
will be provided. It does not mean that other formats cannot be used, |
|
| 254 |
rather that we did not test them. |
|
| 253 |
will be provided. |
|
| 255 | 254 |
As for import, we will support all formats that ``qemu-img`` can convert |
| 256 | 255 |
to ``raw``. At this point this means ``raw``, ``cow``, ``qcow``, |
| 257 | 256 |
``qcow2``, ``vmdk`` and ``cloop``. We do not plan for now to support |
| ... | ... | |
| 268 | 267 |
purposes and is better standardized. |
| 269 | 268 |
|
| 270 | 269 |
Please note, that due to security reasons we require the disk image to |
| 271 |
be in the same directory as the ``.ovf`` description file. |
|
| 270 |
be in the same directory as the ``.ovf`` description file for both |
|
| 271 |
import and export. |
|
| 272 | 272 |
|
| 273 | 273 |
In order to completely ignore disk-related information in resulting |
| 274 | 274 |
config file, please use ``--disk-template=diskless`` option. |
| ... | ... | |
| 302 | 302 |
accessibility for Ganeti instances. List of installed OSes can be |
| 303 | 303 |
checked using ``gnt-os list`` command. |
| 304 | 304 |
|
| 305 |
References |
|
| 306 |
---------- |
|
| 307 |
|
|
| 308 |
Files listed in ``ovf:References`` section cannot be hyperlinks. |
|
| 309 |
|
|
| 305 | 310 |
Other |
| 306 | 311 |
----- |
| 307 | 312 |
|
| ... | ... | |
| 425 | 430 |
--------------- |
| 426 | 431 |
|
| 427 | 432 |
Disk conversion for both import and export is done using external tool |
| 428 |
called qemu-tools. The same tool is used to determine the type of disk,
|
|
| 429 |
as well as its virtual size. |
|
| 433 |
called ``qemu-img``. The same tool is used to determine the type of
|
|
| 434 |
disk, as well as its virtual size.
|
|
| 430 | 435 |
|
| 431 | 436 |
|
| 432 | 437 |
Import |
| ... | ... | |
| 492 | 497 |
- if ``--ova`` option was chosen, pack the results into ``.ova`` tarfile |
| 493 | 498 |
|
| 494 | 499 |
|
| 500 |
Work in progress |
|
| 501 |
---------------- |
|
| 502 |
|
|
| 503 |
- conversion to/from raw disk should be quicker |
|
| 504 |
- add graphic card memory to export information (12 MB of memory) |
|
| 505 |
- space requirements for conversion + compression + ova are currently |
|
| 506 |
enormous |
|
| 507 |
- add support for disks in chunks |
|
| 508 |
- add support for certificates |
|
| 509 |
- investigate why VMWare's ovftool does not work with ovfconverter's |
|
| 510 |
compression and ova packaging -- maybe noteworty: if OVA archive does |
|
| 511 |
not have a disk (i.e. in OVA package there is only .ovf ad .mf file), |
|
| 512 |
then the ovftool works |
|
| 513 |
- investigate why new versions of VirtualBox have problems with OVF |
|
| 514 |
created by ovfconverter (everything works fine with 3.16 version, but |
|
| 515 |
not with 4.0) |
|
| 516 |
|
|
| 517 |
|
|
| 495 | 518 |
.. vim: set textwidth=72 : |
| 496 | 519 |
.. Local Variables: |
| 497 | 520 |
.. mode: rst |
Also available in: Unified diff