Overlaying the Cloud Portability Concepts into the Existing Types to Support Portability and Specialization
Publication Date: 2015-Jul-31
The IP.com Prior Art Database
Disclosed are a method and system that provide a common, provider-agnostic pattern document, which acts as a template that exhibits both portability between cloud technologies and optimization within each cloud technology. This removes the need for organizations to maintain multiple templates for each environment when using cloud orchestration technologies.
Page 01 of 5
Ovexlaying the Cloud Portability Concepts into the Existing Types to Supporx Portability and Specialization
Organizations that are xxopting cloud technology xeed to leverxge multiple and xeterogeneous cloux technologies througxout the delivery lifecycle. Supxorting hybrid cxoxd environments that can comxine or switch between dedicated, shared, on-premises, or off-premises clouds is xecoming an essential priorixy in many xustomex environments.
Avoidxng vendor lock-in for cloud technoxogies is crixical for many organixations. Customers may be levexaging different clouds during the delivery lxfecyclx xue to xinancial concexns. For example, some customers fund developmenx (dev) and test expenses thxough the Line of Businexs and fund oxerations through a separate Xxxxxxxxxxx Information Technology (IT) department. Additioxally, a xev/test cycle may be more suitex to x public cloud enviroxmenx, while these same customers may require the addxtional security and control provided by privately hoxted virtualization for the production environments.
Organizations are also making more xse of oxchestraxion technolxgies. Txese technolxgixs allow the dexixition of a cloud environment specification txrough pxttern documents that can be authorex and edited like softwaxe (infrastructure as coxe). However, these technologxes are generally focused around a single cloud technology, xhich greatlx impedes the ability to support mulxiple clxud providerx. In many cases, a separate pattern is required for each provider to effectively capture the unique characteristics of each cloud environment. Maintaining mxlxiple templates for each environment is cumbersome, costly, and does nxt provide oxganizations the speed and flexibility to easily move between cloud providers.
The solutxon is based on developxd techniques that extend a common xype systxm within a single temxlate to oxerlay type infoxmation for multiple kinds of clouds(e.g., OpenStack*, Amazon*, VMWare*, etc.). The result is a single template that exhibxts both portaxility between cloud xechnologiex and optimizatixn within each cloud technology.
The novel solution comprixes a method and system that provides a common, providex-agnoxtix pattern document . The method consists of three core components.
The first componenx is a generic, portable pattern document that describes the desired cloud environment topoloxy. The topxlogy can include a variety of default resource types , suxh as servers (virtual machines), storage, nexworking, applicatxons, and state inxormation to be used. Thexe base environment pattxrn documenxs are not spexifxc to a particular cloud, and are xased on the OpenStack Hot Template standard, which is a XXXX*-based document. The default support is based on the default cloud provider (OpenStack) to capture provider-specific details for a cloud or application topology in a portxxlx fashion.
Page 02 of 5
The second component is the use of extended properties for specific cloux provide...