Browse Prior Art Database

Metadata Driven Method for the Heterogeneous Tooling Framework of Platform as a Service in a Cloud Environment

IP.com Disclosure Number: IPCOM000239982D
Publication Date: 2014-Dec-19
Document File: 8 page(s) / 111K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a metadata driven method for systematically managing the heterogeneous tools for the Platform as a Service (PaaS) Tooling Framework.

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

Page 01 of 8

Metadata Driven Method for the Heterogeneous Tooling Framework of Platform as a Service in a Cloud Environment

In a cloud environment, Platform as a Service (PaaS) is the capability provided to the consumers (usually application developers) to deploy applications onto the virtualized infrastructure and utilize the supported computing platforms and solution stacks (called Services) from the service providers. These Services include operating system, middleware, application server, database, programming language runtime, development framework, and library. The service providers are responsible to manage the operations of these Services effectively in accordance with the underlining Service Level Agreement (SLA).

There are many activities in the PaaS Service operational life cycle, including service deployment and launch, service usage and health monitoring, service backup and restore, failure detection and recovery, etc. As the Services grow, the operational costs greatly increase. To reduce the cost, the service providers usually manage the operations through tooling and automation. Service providers write a set of tools to run within the tooling framework to automate the Service operations. Tools are usually

written in different programming languages and having different characteristics.

Managing the heterogeneous tools in the single tooling framework is challenging. The challenges include the following:

How to easily add new tools and remove existing tools from the framework

How to systematically manage tools written in different programming languages
How to systematically manage tools having different characteristics (e.g., some tools need to run periodically while others do

not, some tools require runtime parameters while others do not, etc.)

How to effectively control tool privileges so that restrictive tools can only be run by authorized people
How to properly handle execution conflicts amongst the tools; multiple tools can run concurrently without interfering each

other

The novel contribution is a metadata driven method for systematically managing the heterogeneous tools for the PaaS Tooling Framework. This method comprises the following steps:

1. Write a set of self-contained, single-purpose tools for managing the service operation. The tool can be written in any programming languages or script languages. The tool is self-contained with no dependency on other tools. The tool is single-purpose, managing one and only one task in the operational life cycle. Examples of the tools are: restart service instance, collect logs, and service upgrade.

2. Write a set of tool type modules (called handlers) in the framework to handle each type of tools. For example, a handler to run Shell scripts, a handler to run Python script, a handler to run Java executables, etc.

1


Page 02 of 8

3. Use metadata to register these tools into the framework. The metadata contains a set of tool properties and characteristics describing...