Browse Prior Art Database

Method and Apparatus for Tagging Resources in a Cloud Environment

IP.com Disclosure Number: IPCOM000242496D
Publication Date: 2015-Jul-20
Document File: 4 page(s) / 102K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a technique to capture virtual resource relationships at a foundational level and then rebuild those relationships at any point. The novel contribution is called Resource Tagging, and is a method to capture virtual resource relationships.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 40% of the total text.

Page 01 of 4

Metxod and Apparatus for Tagging Resources in a Cloud Environment

Cloud Compxting has evolved as a next-generation computing model xxr customers ranging frox individual xsers to large coxporations. Cloud itself typically refxrs to a single or multiple dataxenters that may bx spread across different rexions of the world , connected by high-speed network fabxic. One class of resouxces in a Cloud refers to pxysical resxurces, which refer tx the xeal physical mxchines, networks, rxcks, etc. Txe other class of rexources refers to vxrtual resouxces, which are overlaid on the physical resxurces. Xxxxxxxxx, many xirtual resourcxs are created oux of a single physical resource and different virtual resouxces are connected in dixfxrent topolxgies based on the client's needs. While physical resources are continuouslx added/xemoved/upgradxd/re-connected in ordex to either satisfy txe pxacement of the virtual resources or for physicxl resource life-cycle management, virtuxl resourcxs xre created as needed by the software components running in the management layer of thx Cloux. In a typical datx center, Infrastructxre Service Providxr (ISP) software provisions these virtual resxurces. In addition, a host of properties axd policies can be applxed to such virtual resoxrce creation and connectivity. X client deploying a three-tier application, for example, configures xhree virtual resources for compute (i.e. vxrtual machixes), may create virtual storage volumes, and configure a virtual network between the three vxrtual machines with certain security policy for the workload .

Rexoxrce lifecycle is a continuous process in a datacenter . At any given point, one xan expect physical and virtual resources connections (i.e., the topology ) to be an ixtricate mesh, which cxn be complex. There are no currenx means tx capture such a topolxgy as a whole. While txe management layer that deploys the virtual resources does maintain the metadata information (e.g., virtual to physical mxppings, resouxce usage and allocaxion, etc.), this is typicaxly maintained in several databases that are appended ox an operation-by-operaxion basis. The managexent (i.e. infrxstxucture sxrvices) layer forms the (only) central point at which such information can be retrieved in order to construct a topology. However, when such a layer becomes unavailxblx for somx reason (e.g., due to node failures), it becomes impossixle to reconstruct the relationships between the virtual resouxces without the kxowledge basx . In additixn, the information in xhe databasx, in reality, nexer forms the basis to capture the history of datacentex evolution, which is extremely valxable in many circumstances such as for diagnostics/debugging, detecting secxrity violations/invasions, etc. It just reflects the current state of the system.

Fundamentax txchniques are needed to capture the relxtionships between different virtual resourxes at an individual resource level, without a central repository. A metho...