IP Library Granted Patent US 12,450,099
Granted Patent B2
US 12,450,099 · App. 17/191,426 · Granted Oct 21, 2025

Release lifecycle management system for multi-node application

Inventors: Vadim Spivak (Emerald Hills, CA); Kent Skaar (Stow, MA); Oleg Shaldibin (Palo Alto, CA)
Assignee: Pivotal Software, Inc.
G06F9/5055G06F8/65G06F8/658G06F8/71G06F9/45558H04L41/0806H04L47/70H04L67/10H04L67/34G06F9/45533G06F2009/4557G06F2009/45595
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,450,099
App. No.
17/191,426
Granted
Oct 21, 2025
Kind
B2
Abstract

A deployment system provides the ability to deploy a multi-node distributed application, such as a cloud computing platform application that has a plurality of interconnected nodes performing specialized jobs. The deployment system may update a currently running cloud computing platform application according to a deployment manifest and a versioned release bundle that includes jobs and application packages. The deployment system determines changes to the currently running cloud computing platform application and distributes changes to each job to deployment agents executing on virtual machines (VMs). The deployment agents apply the updated jobs to their respective VMs (e.g., launching applications), thereby deploying an updated version of cloud computing platform application.

Claims (60)

1. A method comprising:

receiving, via a deployment system, a specification, wherein the specification specifies a plurality of functional components for a cloud computing platform application and a respective template for a respective ancillary virtual machine (VM) corresponding to each functional component, wherein the specification further specifies a number of instances of each respective functional component to be deployed on one or more of a plurality of main VMs to be instantiated for the cloud computing platform application;

requesting a virtual infrastructure platform to launch the respective ancillary VM, from the respective template, for each of the plurality of functional components, wherein the respective ancillary VM is configured to compile software to be executed by one or more instances of the functional component corresponding to the respective ancillary VM;

directing the respective ancillary VM to compile the software to be executed by each of the one or more instances of the functional component corresponding to the respective ancillary VM;

provisioning, via the deployment system, based at least in part on the specification, the plurality of main VMs to execute the plurality of functional components, wherein the specification maps each instance of a functional component of the plurality of functional components to a respective set of one or more main VMs;

deploying the each instance of the functional component of the plurality of functional components to the respective set of one or more main VMs by installing, on each main VM in the respective set of one or more main VMs, the software to be executed by the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs, wherein the software is compatible with hardware properties of each main VM in the respective set of one or more main VMs to execute the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs;

parsing, via the deployment system, a set of parameters from the specification, wherein a respective set of parameters is applied to the respective set of one or more main VMs for each respective instance of the functional component mapped to the respective set of one or more main VMs, wherein each respective set of one or more main VMs forms a respective node of a plurality of interconnected nodes, wherein the plurality of interconnected nodes constitutes the cloud computing platform application; and

modifying, via the deployment system, the specification to scale the cloud computing platform application, wherein scaling the cloud computing platform application includes provisioning one or more additional main VMs to deploy one or more additional instances of a functional component.

2. The method of claim 1 , wherein the installing the software compatible with the hardware properties of each main VM comprises:

directing an agent component of the main VM to install a package of computer-executable instructions specified by the specification, wherein the package of computer-executable instructions is configured to, when executed by the main VM, perform operations of at least one of the plurality of functional components.

3. The method of claim 1 , wherein each node of the plurality of interconnected nodes has a separate software application and separate library dependencies and is specially configured for the cloud computing platform application to function as a whole.

4. The method of claim 1 , wherein the specification specifies a plurality of configuration settings, and wherein the installing the software comprises:

retrieving a configuration file for an instance of a particular functional component of the plurality of functional components, wherein the configuration file specifies at least one configuration setting having a variable that references one of the plurality of configuration settings in the specification, and wherein the instance of the particular functional component is compatible with the hardware properties of the respective set of one or more main VMs mapped to the instance of the particular functional component;

modifying the configuration file to replace the variable with a value of the referenced configuration setting provided by the specification; and

providing the modified configuration file to respective agent component of each main VM in the respective set of one or more main VMs.

5. The method of claim 1 , wherein the specification for the cloud computing platform application to be deployed specifies network properties that would be required by any node executing any one of the plurality of functional components, and wherein each of the plurality of main VMs is configured according to the network properties required by at least one of the plurality of functional components.

6. The method of claim 1 , wherein the provisioning the plurality of main VMs comprises:

requesting, for each of the plurality of main VMs, provision of the main VM using a template that specifies a disk image comprising (i) a guest operating system and (ii) an agent component of the main VM.

7. The method of claim 1 , wherein the plurality of functional components for the cloud computing platform application are configured to coordinate to provide cloud computing services to host one or more web applications.

8. The method of claim 1 , further comprising:

monitoring, via a health monitor, communications from agents running on main VMs launched by a virtual infrastructure platform; or

re-starting, via the health monitory, a failed main VM if a lack of communication from the failed main VM is detected.

9. A system comprising:

processor; and

a non-transitory computer-readable medium in communication with the processor, the non-transitory computer-readable medium having encoded thereon a set of instructions executable by the processor to cause the processor to perform operations comprising:

receiving, via a deployment system, a specification, wherein the specification specifies a plurality of functional components for a cloud computing platform application and a respective template for a respective ancillary virtual machine (VM) corresponding to each functional component, wherein the specification further specifies a number of instances of each respective functional component to be deployed on one or more of a plurality of main VMs to be instantiated for the cloud computing platform application;

requesting a virtual infrastructure platform to launch the respective ancillary VM, from the respective template, for each of the plurality of functional components, wherein the respective ancillary VM is configured to compile software to be executed by one or more instances of the functional component corresponding to the respective ancillary VM;

directing the respective ancillary VM to compile the software to be executed by each of the one or more instances of the functional component corresponding to the respective ancillary VM;

provisioning, via the deployment system, based at least in part on the specification, the plurality of main VMs to execute the plurality of functional components, wherein the specification maps each instance of a functional component of the plurality of functional components to a respective set of one or more main VMs;

deploying the each instance of the functional component of the plurality of functional components to the respective set of one or more main VMs by installing, on each main VM in the respective set of one or more main VMs, the software to be executed by the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs, wherein the software is compatible with hardware properties of each main VM in the respective set of one or more main VMs to execute the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs;

parsing, via the deployment system, a set of parameters from the specification, wherein a respective set of parameters is applied to the respective set of one or more main VMs for each respective instance of the functional component mapped to the respective set of one or more main VMs, wherein each respective set of one or more main VMs forms a respective node of a plurality of interconnected nodes, wherein the plurality of interconnected nodes constitutes the cloud computing platform application; and

modifying, via the deployment system, the specification to scale the cloud computing platform application, wherein scaling the cloud computing platform application includes provisioning one or more additional main VMs to deploy one or more additional instances of a functional component.

10. The system of claim 9 , wherein the installing the software compatible with the hardware properties of each main VM comprises:

directing an agent component of the main VM to install a package of computer-executable instructions specified by the specification, wherein the package of computer-executable instructions is configured to, when executed by the main VM, perform operations of at least one of the plurality of functional components.

11. The system of claim 9 , wherein the specification for the cloud computing platform application to be deployed specifies network properties that would be required by any node executing any one of the plurality of functional components, and wherein each of the plurality of main VMs is configured according to the network properties required by at least one of the plurality of functional components.

12. The system of claim 9 , wherein the specification specifies a plurality of configuration settings, and wherein the installing the software comprises:

retrieving a configuration file for an instance of a particular functional component of the plurality of functional components, wherein the configuration file specifies at least one configuration setting having a variable that references one of the plurality of configuration settings in the specification, and wherein the instance of the particular functional component is compatible with the hardware properties of the respective set of one or more main VMs mapped to the instance of the particular functional component;

modifying the configuration file to replace the variable with a value of the referenced configuration setting provided by the specification; and

providing the modified configuration file to respective agent component of each main VM in the respective set of one or more main VMs.

13. The system of claim 9 , wherein each node of the plurality of interconnected nodes has a separate software application and separate library dependencies and is specially configured for the cloud computing platform application to function as a whole.

14. The system of claim 9 , wherein the provisioning the plurality of VMs comprises:

requesting, for each of the plurality of main VMs, provision of the main VM using a template that specifies a disk image comprising (i) a guest operating system and (ii) an agent component of the main VM.

15. The system of claim 9 , wherein the plurality of functional components for the cloud computing platform application are configured to coordinate to provide cloud computing services to host one or more web applications.

16. The system of claim 9 , the operations further comprising: monitoring via a health monitor of the deployment module, communications from agents running on main VMs launched by the virtual infrastructure platform; or

re-starting, via the health monitor, a failed main VM if a lack of communication from the failed main VM is detected.

17. A non-transitory computer-readable medium in communication with a processor, the non-transitory computer-readable medium having encoded thereon a set of instructions executable by the processor to cause the processor to perform operations comprising:

receiving, via a deployment system, a specification, wherein the specification specifies a plurality of functional components for a cloud computing platform application and a respective template for a respective ancillary virtual machine (VM) corresponding to each functional component, wherein the specification further specifies a number of instances of each respective functional component to be deployed on one or more of a plurality of main VMs to be instantiated for the cloud computing platform application;

requesting a virtual infrastructure platform to launch the respective ancillary VM, from the respective template, for each of the plurality of functional components, wherein the respective ancillary VM is configured to compile software to be executed by one or more instances of the functional component corresponding to the respective ancillary VM;

directing the respective ancillary VM to compile the software to be executed by each of the one or more instances of the functional component corresponding to the respective ancillary VM;

provisioning, via the deployment system, based at least in part on the specification, the plurality of main VMs to execute the plurality of functional components, wherein the specification maps each instance of a functional component of the plurality of functional components to a respective set of one or more main VMs;

deploying the each instance of the functional component of the plurality of functional components to the respective set of one or more main VMs by installing, on each main VM in the respective set of one or more main VMs, the software to be executed by the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs, wherein the software is compatible with hardware properties of each main VM in the respective set of one or more main VMs to execute the each instance of the functional component of the plurality of functional components mapped to the respective set of one or more main VMs;

parsing, via the deployment system, a set of parameters from the specification, wherein a respective set of parameters is applied to the respective set of one or more main VMs for each respective instance of the functional component mapped to the respective set of one or more main VMs, wherein each respective set of one or more main VMs forms a respective node of a plurality of interconnected nodes, wherein the plurality of interconnected nodes constitutes the cloud computing platform application; and

modifying, via the deployment system, the specification to scale the cloud computing platform application, wherein scaling the cloud computing platform application includes provisioning one or more additional main VMs to deploy one or more additional instances of a functional component.

18. The non-transitory computer-readable medium of claim 17 , wherein the installing the software comprises:

directing an agent component of the main VM to install a package of computer-executable instructions specified by the specification, wherein the package of computer-executable instructions is configured to, when executed by the main VM, perform operations of at least one of the plurality of functional components.

19. The non-transitory computer-readable medium of claim 17 , wherein the specification for the cloud computing platform application to be deployed specifies network properties that would be required by any node executing any one of the plurality of functional components, and wherein each of the plurality of main VMs is configured according to the network properties required by at least one of the plurality of functional components.

20. The non-transitory computer-readable medium of claim 17 , wherein the specification specifies a plurality of configuration settings, and wherein the installing the software comprises:

retrieving a configuration file for an instance of a particular functional component of the plurality of functional components, wherein the configuration file specifies at least one configuration setting having a variable that references one of the plurality of configuration settings in the specification, and wherein the instance of the particular functional component is compatible with the hardware properties of the respective set of one or more main VMs mapped to the instance of the particular functional component;

modifying the configuration file to replace the variable with a value of the referenced configuration setting provided by the specification; and

providing the modified configuration file to respective agent component of each main VM in the respective set of one or more main VMs.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2025
From: SPIVAK, VADIM; SKAAR, KENT; SHALDIBIN, OLEG
To: VMWARE, INC.
Reel/Frame 072381/0299 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2025
From: VMWARE, INC.
To: PIVOTAL SOFTWARE, INC.
Reel/Frame 072381/0438 →
Continuity (5)
Continuation 14965005 · Dec 10, 2015
Continuation 14642650 · Mar 9, 2015
Continuation 13428125 · Mar 23, 2012
Provisional Application 61474669 · Apr 12, 2011
Related Publication 20210349706A1 · Nov 11, 2021
References Cited (183)
US 6266809B1 · Craig et al. · 2001 [cited by applicant]
US 6367073B2 · Elledge · 2002 [cited by applicant]
US 6609128B1 · Underwood · 2003 [cited by applicant]
US 6976093B2 · Lara et al. · 2005 [cited by applicant]
US 7024668B2 · Shiomi et al. · 2006 [cited by applicant]
US 7275244B1 · Bell et al. · 2007 [cited by applicant]
US 7356679B1 · Le et al. · 2008 [cited by applicant]
US 7370322B1 · Matena et al. · 2008 [cited by applicant]
US 7533381B2 · Ando · 2009 [cited by applicant]
US 7577722B1 · Khandekar · 2009 [cited by applicant]
US 7634488B2 · Keys et al. · 2009 [cited by applicant]
US 7788662B2 · Haselden et al. · 2010 [cited by applicant]
US 7849460B1 · Martin · 2010 [cited by applicant]
US 7874008B2 · Chang et al. · 2011 [cited by applicant]
US 7900056B1 · Murphy · 2011 [cited by applicant]
US 7971059B2 · Calman et al. · 2011 [cited by applicant]
US 8091084B1 · Dobrovokskiy et al. · 2012 [cited by applicant]
US 8108855B2 · Dias · 2012 [cited by applicant]
US 8108912B2 · Ferris · 2012 [cited by applicant]
US 8176094B2 · Friedman · 2012 [cited by applicant]
US 8176559B2 · Mathur et al. · 2012 [cited by applicant]
US 8201237B1 · Doane et al. · 2012 [cited by applicant]
US 8225093B2 · Fok et al. · 2012 [cited by applicant]
US 8281307B2 · Arnold · 2012 [cited by applicant]
US 8327357B2 · Amsden · 2012 [cited by applicant]
US 8359594B1 · Davidson et al. · 2013 [cited by applicant]
US 8375360B2 · I'Anson · 2013 [cited by applicant]
US 8407689B2 · Dournov et al. · 2013 [cited by applicant]
US 8417798B2 · Chen · 2013 [cited by applicant]
US 8429630B2 · Nickolov et al. · 2013 [cited by applicant]
US 8490082B2 · Moore et al. · 2013 [cited by applicant]
US 8495611B2 · McCarthy · 2013 [cited by applicant]
US 8538921B2 · Hall · 2013 [cited by applicant]
US 8578375B2 · Pagan et al. · 2013 [cited by applicant]
US 8584119B2 · Ellington et al. · 2013 [cited by applicant]
US 8601226B1 · Lappas et al. · 2013 [cited by applicant]
US 8627310B2 · Ashok et al. · 2014 [cited by applicant]
US 8682957B2 · Elson et al. · 2014 [cited by applicant]
US 8793348B2 · Ott · 2014 [cited by applicant]
US 8799298B2 · Weissman · 2014 [cited by applicant]
US 8839221B2 · Sapuntzakis et al. · 2014 [cited by applicant]
US 8997078B2 · Spivak et al. · 2015 [cited by applicant]
US 9015710B2 · Spivak et al. · 2015 [cited by applicant]
US 9043767B2 · Spivak et al. · 2015 [cited by applicant]
US 9569198B2 · Spivak et al. · 2017 [cited by applicant]
US 10241774B2 · Spivak et al. · 2019 [cited by applicant]
US 10942724B2 · Spivak et al. · 2021 [cited by applicant]
US 20020174421A1 · Zhao et al. · 2002 [cited by applicant]
US 20020178254A1 · Brittenham et al. · 2002 [cited by applicant]
US 20030061247A1 · Renaud · 2003 [cited by applicant]
US 20040030710A1 · Shadle · 2004 [cited by applicant]
US 20040183831A1 · Ritchy et al. · 2004 [cited by applicant]
US 20050022198A1 · Olapurath et al. · 2005 [cited by applicant]
US 20050120332A1 · Martin · 2005 [cited by applicant]
US 20050120347A1 · Asare · 2005 [cited by applicant]
US 20050198303A1 · Knauerhase et al. · 2005 [cited by applicant]
US 20050257206A1 · Semerdzhiev · 2005 [cited by applicant]
US 20050278518A1 · Ko et al. · 2005 [cited by applicant]
US 20050289536A1 · Nayak et al. · 2005 [cited by applicant]
US 20060010176A1 · Armington · 2006 [cited by applicant]
US 20060026585A1 · Haselden et al. · 2006 [cited by applicant]
US 20060037071A1 · Rao et al. · 2006 [cited by applicant]
US 20060079356A1 · Kodama et al. · 2006 [cited by applicant]
US 20060136701A1 · Dickinson · 2006 [cited by applicant]
US 20060136897A1 · Laxminarayan et al. · 2006 [cited by applicant]
US 20060248522A1 · Lakshminarayanan et al. · 2006 [cited by applicant]
US 20070058548A1 · Babonneau et al. · 2007 [cited by applicant]
US 20070168956A1 · Moore et al. · 2007 [cited by applicant]
US 20070204262A1 · Ahluwalia et al. · 2007 [cited by applicant]
US 20070209035A1 · Sonderegger et al. · 2007 [cited by applicant]
US 20070250513A1 · Hall · 2007 [cited by applicant]
US 20080109788A1 · Prieto · 2008 [cited by applicant]
US 20080127175A1 · Naranjo · 2008 [cited by applicant]
US 20080163171A1 · Chess et al. · 2008 [cited by applicant]
US 20080163194A1 · Dias · 2008 [cited by applicant]
US 20080209016A1 · Karve et al. · 2008 [cited by applicant]
US 20080244577A1 · Le et al. · 2008 [cited by applicant]
US 20080307414A1 · Alpern et al. · 2008 [cited by applicant]
US 20090049102A1 · Weissman · 2009 [cited by applicant]
US 20090070752A1 · Alpern · 2009 [cited by applicant]
US 20090070853A1 · Chung et al. · 2009 [cited by applicant]
US 20090100420A1 · Sapuntzakis et al. · 2009 [cited by applicant]
US 20090112919A1 · De Spiegeleer · 2009 [cited by applicant]
US 20090172781A1 · Masuoka et al. · 2009 [cited by applicant]
US 20090187995A1 · Lopatic et al. · 2009 [cited by applicant]
US 20090216970A1 · Basler et al. · 2009 [cited by applicant]
US 20090276771A1 · Nickolov · 2009 [cited by applicant]
US 20090320012A1 · Lee et al. · 2009 [cited by applicant]
US 20090320019A1 · Ellington et al. · 2009 [cited by applicant]
US 20100103837A1 · Jungck et al. · 2010 [cited by applicant]
US 20100131590A1 · Coleman et al. · 2010 [cited by applicant]
US 20100142447A1 · Schlicht et al. · 2010 [cited by applicant]
US 20100146425A1 · Lance et al. · 2010 [cited by applicant]
US 20100251328A1 · Syed et al. · 2010 [cited by applicant]
US 20100257605A1 · McLaughlin et al. · 2010 [cited by applicant]
US 20100281166A1 · Buyya et al. · 2010 [cited by applicant]
US 20100318649A1 · Moore et al. · 2010 [cited by applicant]
US 20100325624A1 · Bartolo et al. · 2010 [cited by applicant]
US 20100333085A1 · Criddle et al. · 2010 [cited by applicant]
US 20110004916A1 · Schiffman et al. · 2011 [cited by applicant]
US 20110029947A1 · Markovic · 2011 [cited by applicant]
US 20110055707A1 · Kimmet · 2011 [cited by applicant]
US 20110055714A1 · Vemulapalli et al. · 2011 [cited by applicant]
US 20110055828A1 · Amsden · 2011 [cited by applicant]
US 20110061046A1 · Phillips et al. · 2011 [cited by applicant]
US 20110072505A1 · Ott · 2011 [cited by applicant]
US 20110107411A1 · McClain et al. · 2011 [cited by applicant]
US 20110126197A1 · Larsen et al. · 2011 [cited by applicant]
US 20110145790A1 · Rajaraman et al. · 2011 [cited by applicant]
US 20110145836A1 · Wheeler et al. · 2011 [cited by applicant]
US 20110153684A1 · Yung · 2011 [cited by applicant]
US 20110153727A1 · Li · 2011 [cited by applicant]
US 20110153824A1 · Chikando et al. · 2011 [cited by applicant]
US 20110167469A1 · Letca et al. · 2011 [cited by applicant]
US 20110214124A1 · Ferris et al. · 2011 [cited by applicant]
US 20110231552A1 · Carter et al. · 2011 [cited by applicant]
US 20110258333A1 · Pomerantz et al. · 2011 [cited by applicant]
US 20110258619A1 · Wookey et al. · 2011 [cited by applicant]
US 20110265076A1 · Thorat · 2011 [cited by applicant]
US 20110276713A1 · Brand · 2011 [cited by applicant]
US 20110283194A1 · Chen et al. · 2011 [cited by applicant]
US 20110302569A1 · Kunze et al. · 2011 [cited by applicant]
US 20110321031A1 · Dournov · 2011 [cited by applicant]
US 20120054731A1 · Aravamudan et al. · 2012 [cited by applicant]
US 20120066670A1 · Mccarthy et al. · 2012 [cited by applicant]
US 20120072480A1 · Hays · 2012 [cited by applicant]
US 20120084769A1 · Adi et al. · 2012 [cited by applicant]
US 20120102480A1 · Hopmann · 2012 [cited by applicant]
US 20120102481A1 · Mani et al. · 2012 [cited by applicant]
US 20120159469A1 · Laor · 2012 [cited by applicant]
US 20120185913A1 · Martinez et al. · 2012 [cited by applicant]
US 20120240110A1 · Breitgand · 2012 [cited by examiner]
US 20120240135A1 · Risbood et al. · 2012 [cited by applicant]
US 20120254850A1 · Hido et al. · 2012 [cited by applicant]
US 20120266156A1 · Spivak et al. · 2012 [cited by applicant]
US 20120266158A1 · Spivak et al. · 2012 [cited by applicant]
US 20120266159A1 · Risbood et al. · 2012 [cited by applicant]
US 20120266168A1 · Spivak et al. · 2012 [cited by applicant]
US 20120324116A1 · Dorai et al. · 2012 [cited by applicant]
US 20130006689A1 · Kinnear et al. · 2013 [cited by applicant]
US 20130041931A1 · Brand · 2013 [cited by applicant]
US 20130067461A1 · Taragin · 2013 [cited by examiner]
US 20130185715A1 · Dunning et al. · 2013 [cited by applicant]
US 20130227091A1 · Tompkins · 2013 [cited by applicant]
US 20130232480A1 · Winterfeldt et al. · 2013 [cited by applicant]
US 20130275975A1 · Masuda · 2013 [cited by examiner]
US 20130290771A1 · Kim · 2013 [cited by examiner]
US 20140040656A1 · Ho · 2014 [cited by applicant]
EP 2299360 · 2011 [cited by applicant]
EP 2381363 · 2011 [cited by applicant]
JP 2007507046 · 2007 [cited by applicant]
Suanhua Shi et al.; VNIX: Managing Virtual Machines on Clusters; IEEE; pp. 155-162; retrieved on Mar. 26, 2022 (Year: 2008). [cited by examiner]
Ian Gray; Exposing Non-Standard Architectures to Embedded Software Using Compile-Time Virtualisation; ACM; pp. 147-155; retrieved on May 30, 2025 (Year: 2009). [cited by examiner]
Armbrust et al., “A view of cloud computing,” 2010 ACM, pp. 50-58; <http://dl.acm.org/citation.cfm?id=1721672>. [cited by applicant]
Blomer et al., “Micro-CernVM: slashing the cost of building and deploying virtual machines,” Journal of Physics: Conference Series 513, 2014, 8 pages. [cited by applicant]
Borja Sotomayor, “Virtual Infrastructure Management in Private and Hybrid Clouds,” 2009 IEEE; pp. 14-22;http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=5233608. [cited by applicant]
Ching-Chi Lin, “Energy-Aware Virtual Machine Dynamic Provision and Scheduling for Cloud Computing,” 2011 IEEE; pp. 736-737; http://ieeexplore.ieee.org/stamp/stamp.jsp?arnu mber=6008778. [cited by applicant]
Daniel Nurmi, “The Eucalyptus Open-source Cloud-computing System,” 2009 IEEE; pp. 124-131;http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=5071863. [cited by applicant]
European Search Report in EP Application No. 11163533.0, dated Feb. 3, 2012, 10 pages. [cited by applicant]
Goodwill, “Deploying Web applications to Tomcat,” O'Reilly, Apr. 19, 2001, pp. 1-11, XP002646829, Retrieved from the Internet: URL: http://oreilly.com/lpt/a/780 [retrieved on Jun. 30, 2011]. [cited by applicant]
Goodwill, “Java Web Applications,” O'Reilly, Mar. 15, 2001, pp. 1-3, XP002646828, Retrieved from the Internet: URL: http://onjava.com/lpt/a/671 [retrieved on Jun. 30, 2011]. [cited by applicant]
Hansen et al., “Scalable Virtual machine storage using local disks”, Dec. 2010, 9 pages. [cited by applicant]
Hansen et al., “Lithium Virtual Machine Storage for the Cloud,” 2010 ACM; pp. 15-26 ;<http://dl.acm.org/citation.cfm?id=1807134>. [cited by applicant]
International Preliminary Report on Patentability in International Application No. PCT/US2012/033356, dated Oct. 15, 2013, 9 pages. [cited by applicant]
International Search Report dated Jun. 28, 2012 in counterpart PCT application PCT/US2012/033356, filed Apr. 12, 2012, with written opinion. [cited by applicant]
Keahey et al., “Virtual workspaces Achieving quality of service and quality of life in the Grid,” Scientific Programming, 2005, 13:265-275. [cited by applicant]
Kecshenneti et al., “An approach for virtual appliance distribution for service deployment,” Future Generation Computer Systems, Mar. 2011, pp. 280-289. [cited by applicant]
Konstantinou et al., “An Architecture for Virtual Solution Composition and Deployment in Infrastructure Clouds,” Jun. 2009; ACM; pp. 9-17. [cited by applicant]
Lagar-Cavilla et al., “SnowFlock Rapid Virtual Machine Cloning for Cloud Computing,” ACM, Apr. 2009, pp. 1-12; http://dl.acm.org/citation.cfm?id=1519067 retrieved on Oct. 10, 2018. [cited by applicant]
Leitner, “Application Level Performance Monitoring of Cloud services,” Dec. 2012, vol. 9, pp. 1-8. [cited by applicant]
Liu et al., “Saas Integration for Software Cloud,” 2010 IEEE; pp. 402-409 ;<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5557968>. [cited by applicant]
Matthews et al., “Virtual Machine Contracts for Datacenter and Cloud Computing Environments,” ACM, Jun. 2009, pp. 25-30. [cited by applicant]
Partial European Search Report for Application No. 11163533.0 dated Jul. 19, 2011, 6 pages. [cited by applicant]
Razavi et al., “Scalable Virtual Machine Deployment Using VM Image Caches,” ACM, Nov. 2013, 12 pages. [cited by applicant]
Rodrigo N. Calheiros, “Virtual Machine Provisioning Based on Analytical Performance and QoS in Cloud Computing Environments,” 2011 IEEE; pp. 295-304; http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=6047198. [cited by applicant]
Schmidt et al., “Efficient distribution of virtual machines for cloud computing,” 2010 IEEE; pp. 567-574 ;<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber =5452476>. [cited by applicant]
Sun et al., “Simplifying Service Deployment with Virtual Appliances,” 2008 IEEE International Conference on Services Computing, Jul. 7, 2008, pp. 265-272. [cited by applicant]
Sushil Bhardwaj, “Cloud Computing: a Study of Infrastructure as a Service (IAAS),” 2010 IJET; pp. 60-63;http://s3.amazonaws.com/academia.edu.documents/7299777/cloud%20computing%20a%20study%20of.pdf. [cited by applicant]
Tharam Dillon, “Cloud Computing Issues and Challenges,” 2010 IEEE; pp. 27-33;http://ieeexplore.ieee.org/stamp/stamp.jsp ?arnu mber=54 7 467 4. [cited by applicant]
Thomas, “Enabling Application Agility—Software as A Service, Cloud Computing and Dynamic Languages,” 2008 JOT; pp. 29-32; <http://www.jot.fm/issues/issue_2008_05/column3.pdf>. [cited by applicant]
Tonon, “Tomcat Architecture Diagram,” Apr. 26, 2011, p. 1, XP002fi4fi830, retrieved from internet: URL: http://marakana.com/forums/tomcat/general/106.html [retrieved on Jul. 1, 2011]. [cited by applicant]
Wei et al., “Managing security of virtual machine images in a cloud environment,” Nov. 13, 2009, 6 pages. [cited by applicant]
White page of BMC software, “Virtualization management with BMC and VMware,” © 2011 BMC software, 2 pages. [cited by applicant]