System and method for creating or reconfiguring a virtual server image for cloud deployment

• US 9,239,814 B2
• Filed: 01/27/2014
• Issued: 01/19/2016
• Est. Priority Date: 06/01/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lagergren, Marcus, Vidstedt, Mikael
• Primary Examiner(s): HOANG, HIEU T
• Application Number:
  US14/164,503
• Publication Number:
  US 20140143389A1
• Time in Patent Office: 722 Days
• Field of Search: 709/211, 709/222, 709/228
• US Class Current: 1/1
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45545 Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

A system and method to convert a software application, such as a Java application into a virtual server image that is suitable for cloud deployment. In accordance with an embodiment, the system and method allows for building a hypervisor appliance containing a virtual machine running an application. In particular, the hypervisor appliance can be compatible with any hypervisor for server virtualization and the application virtual machine can be a Java Virtual Machine (JVM).

Claims

1. A system for converting a software application into a virtual server image, comprising:

a computer including a processor, and an operating system;

a memory space in the computer for creating a virtual server image;

a Java virtual machine on the computer configured to execute a software application; and

a builder application that operates to

receive instructions that specify a particular type of hypervisor to be used with the virtual server image,

determine, based on the specified particular type of hypervisor, whether to initialize the memory space with bootloader code,

write a bootable component of the Java virtual machine into the memory space,

write a non-bootable component of the Java virtual machine, together with the software application, into the memory space,

configure the bootable component of the Java virtual machine in the memory space to execute the non-bootable component therein, and

write the memory space to the virtual server image for deployment to the specified particular type of hypervisor.

2. The system of claim 1, wherein the builder application further operates to configure the bootloader code to execute the bootable component of the Java virtual machine in the memory space.

3. The system of claim 1, wherein the memory space is allocated in RAM in the computer.

4. The system of claim 1, wherein the builder application is further configured to read a configuration file that specifies a location of code and data of the software application.

5. The system of claim 1, further comprising an updater that operates to update the software application and the Java virtual machine without disturbing application data of the software application.

6. The system of claim 1, wherein the specified particular type of hypervisor uses the virtual server image as a snapshot of sectors of a virtual hard disk, and the bootloader code is written into the memory space.

7. The system of claim 1, wherein configuring the bootable component to execute the non-bootable component includes updating the bootable component with a location of the non-bootable component.

8. A method for converting a software application into a virtual server image, comprising:

executing a builder application on a computer including a processor, and a memory space for creating a virtual server image from a Java virtual machine configured to execute a software application;

receiving instructions that specify a particular type of hypervisor to be used with the virtual server image;

determining, based on the specified particular type of hypervisor, whether to initialize the memory space with bootloader code;

writing a bootable component of the Java virtual machine into the memory space;

writing a non-bootable component of the Java virtual machine, together with the software application, into the memory space;

configuring the bootable component of the Java virtual machine in the memory space to execute the non-bootable component therein; and

writing the memory space to the virtual server image for deployment to the specified particular type of hypervisor.

9. The method of claim 8, further comprising

configuring the bootloader code to execute the bootable component of the Java virtual machine in the memory space.

10. The method of claim 8, wherein the memory space is allocated in RAM in the computer.

11. The method of claim 8, further comprising

reading, via the builder application, a configuration file that specifies a location of code and data of the software application.

12. The method of claim 8, further comprising

using an updater to update the software application and the Java virtual machine without disturbing application data of the software application.

13. The method of claim 8, wherein the specified particular type of hypervisor uses the virtual server image as a snapshot of sectors of a virtual hard disk, and the bootloader code is written into the memory space.

14. The method of claim 8, wherein configuring the bootable component to execute the non-bootable component includes updating the bootable component with a location of the non-bootable component.

15. A non-transitory computer-readable storage medium, including instructions stored thereon, which when read and executed by a computer cause the computer to perform the steps comprising:

executing a builder application on a computer including a processor, and a memory space for creating a virtual server image from a Java virtual machine configured to execute a software application;

receiving instructions that specify a particular type of hypervisor to be used with the virtual server image;

determining, based on the specified particular type of hypervisor, whether to initialize the memory space with bootloader code;

writing a bootable component of the Java virtual machine into the memory space;

writing a non-bootable component of the Java virtual machine, together with the software application, into the memory space;

configuring the bootable component of the Java virtual machine in the memory space to execute the non-bootable component therein; and

writing the memory space to the virtual server image for deployment to the specified particular type of hypervisor.

16. The non-transitory computer-readable storage medium of claim 15, further comprising

configuring the bootloader code to execute the bootable component of the Java virtual machine in the memory space.

17. The non-transitory computer-readable storage medium of claim 15, wherein the memory space is allocated in RAM in the computer.

18. The non-transitory computer-readable storage medium of claim 15, further comprising

reading, via the builder application, a configuration file that specifies a location of code and data of the software application.

19. The non-transitory computer-readable storage medium of claim 15, further comprising

using an updater to update the software application and the Java virtual machine without disturbing application data of the software application.

20. The non-transitory computer-readable storage medium of claim 15, wherein the specified particular type of hypervisor uses the virtual server image as a snapshot of sectors of a virtual hard disk, and the bootloader code is written into the memory space.

21. The non-transitory computer-readable storage medium of claim 15, wherein configuring the bootable component to execute the non-bootable component includes updating the bootable component with a location of the non-bootable component.