One of the most stunning features of abiCloud is how it can manage different hypervisors with different technologies seamlessly to the user. AbiCloud can deploy virtual images of different types on each hypervisor, but what most people don't know is that it can deploy a virtual image in different hypervisors following a list of simple rules. This is what is called Virtual to Virtual (V2V), but take it one step further.
This chapter will detail the following topics:
- Virtual Images Introduction
- What is OVF
- How abiCloud uses OVF
- Which parts of the OVF are used by abiCloud
- How to Create a Virtual Image compatible with multiple Hypervisors
- How to Use Virtualbox to Create a compatible Virtual Image
- Publish the OVF Bundle in an abiCloud Repository Space
- Use Apache HTTPD to Publish a Repository Space
- Use Amazon S3 to Publish a Repository Space
- Annex. Compatible VMDK Formats
- Annex. Default User & Password for provided Virtual Appliances
Labels
Virtual Images Introduction
What is OVF
How abiCloud uses OVF
Which parts of the OVF are used by abiCloud
How to Create a Virtual Image compatible with multiple Hypervisors
How to Use Virtualbox to Create a compatible Virtual Image
Publish the OVF Bundle in an abiCloud Repository Space
Use Apache HTTPD to Publish a Repository Space
Use Amazon S3 to Publish a Repository Space
Annex. Compatible VMDK Formats
Annex. Default User & Password for provided Virtual Appliances
