Open virtual appliance

• US 20070294676A1
• Filed: 06/19/2007
• Published: 12/20/2007
• Est. Priority Date: 06/19/2006
• Status: Abandoned Application

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: XenSource, Inc. (Cloud Software Group)
• Inventors: Warfield, Andrew Kent, Mellor, Ewan Ellis
• Application Number:
  US11/820,252
• Publication Number:
  US 20070294676A1
• Time in Patent Office: Days
• US Class Current: 717/139
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

An open virtual appliance is a transport mechanism allowing virtual appliances to be performed upon various virtual environments, even where the formatting of the virtual appliance and virtual environment are not similar. The open virtual appliance provides a common, flexible packaging format for virtual machines that guide their management throughout all stages of a virtual machines life cycle.

Claims

1. A packaging format for a virtual machine, comprising:

an executable instruction set, including virtual machine specific information, for guiding the management of the virtual machine throughout the virtual machine'"'"'s life cycle.

2. The packaging format of claim 1, further comprising a security feature.

3. The packaging format of claim 2, wherein the security feature is a security verification file including a list of each component of the packaging format and the component'"'"'s security information.

4. The packaging format of claim 2, wherein the security feature comprises at least one of a manifest.txt, signature.asc, or mf-signature.asc.

5. The packaging format of claim 1, further comprising at least one virtual machine.

6. The packaging format of claim 1, wherein the packaging format is included in at least one of a tar or a zip.

7. The packaging format of claim 1, wherein the executable instruction set is in an xml format.

8. The packaging format of claim 7, wherein the executable instruction set includes instructions for obtaining virtual machine components from specified locations.

9. The packaging format of claim 8, wherein the specified locations are selected from the group consisting of a network location, a file location, an http:

location, and an https;

location.

10. The packaging format of claim 1, wherein the executable instruction set further comprises directions for at least one of updating or customizing at least one of the packaging format or the virtual machine.

11. The packaging format of claim 1, wherein the executable instruction set is executable by a digital information handling system.

12. The packaging format of claim 1, wherein the life cycle includes four broad stages development, deployment, maintenance, and removal.

13. A method of formatting a virtual machine, comprising:

providing a virtual machine; and

associating the virtual machine with a packaging format, including virtual machine specific information, for guiding the management of the virtual machine throughout the virtual machine'"'"'s life cycle.

14. The method of claim 13, further comprising creating a security feature and including the security feature within the packaging format.

15. The method of claim 14, wherein the security feature further comprises a security verification file including a list of each component of the packaging format and the component'"'"'s security information.

16. The method of claim 15, wherein the security verification file further comprises at least one of a manifest.txt, signature.asc, or mf-signature.asc.

17. The method of claim 13, further comprising storing the packaging format in at least one of a tar or a zip.

18. The method of claim 13, wherein the packaging format includes an executable instruction set.

19. The method of claim 18, wherein the executable instruction set is written in xml language.

20. The method of claim 18, wherein the executable instruction set includes instructions for obtaining virtual machine components from specified locations.

21. The method of claim 20, wherein the specified locations are selected from the group consisting of a network location, a file location, an http:

location, and an https;

location.

22. The method of claim 18, wherein the executable instruction set further comprises directions for at least one of updating or customizing at least one of the packaging format or the virtual machine.

23. An executable instruction set for a packaging format of a virtual machine, comprising:

a first instruction providing a memory for the virtual machine; and

a second instruction providing a location of a source file for the virtual machine.

24. The executable instruction set of claim 23, wherein the memory may be provided as at least one of an integer of a memory size factor, a minimum memory size, a maximum memory size, or a range between a minimum and maximum memory size.

25. The executable instruction set of claim 23, wherein the location may be provided including a virtual block device <

vbd>

designation, a virtual disk image <

vdi>

or filesystem <

fs>

designation, and a mode designation.

26. The executable instruction set of claim 25, wherein the <

vbd>

specifies the particular <

vdi>

or <

fs>

exported to the virtual machine and the mode under which this occurs.

27. The executable instruction set of claim 26, wherein the <

vdi>

or <

fs>

specify the location of the source file.

28. The executable instruction set of claim 27, wherein the location of the source file is selected from the group consisting of a network location, a file location, an http:

location, and an https;

location.

29. The executable instruction set of claim 26, wherein a single <

vdi>

or <

fs>

is referenced by multiple <

vbd>

'"'"'s.

30. The executable instructions set of claim 23, wherein the source file is selected from the group consisting of directions for at least one of updating or customizing at least one of the packaging format or the virtual machine, and a security verification file including at least one of a list of each component of the packaging format and the component'"'"'s security information, a manifest.txt, signature.asc, or mf-signature.asc.