Browse Prior Art Database

Dynamic hierarchical provisioning mechanism

IP.com Disclosure Number: IPCOM000211768D
Publication Date: 2011-Oct-17
Document File: 5 page(s) / 60K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed are a system and method for dynamically and hierarchically provisioning a service. The method includes multiple hierarchical profiles including one or more services, and configuring information and programs for configuring an environment by specifying a computer to use for provisioning the one or more services in the profile or profiles.

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

Page 01 of 5

Dynamic hierarchical provisioning mechanism

The present invention generally relates to the configuration, distribution, and installation of software services in distributed computing environments. In particular, it expands upon patent application which describes a distribution mechanism using static profiles in a flat data structure using no hierarchical structure. [1] In particular, it expands upon another patent application which describes a system and method for dynamic server allocation and provisioning using static server images in a distributed but flat data structure. [2] Software to be downloaded may be either "pushed" from the server or "pulled" by the client.

One method dynamically generates a server image containing services via an "automated" process, never defined. [2] The static server image is stored in a repository and used to provision a server. While the "automated" process is dynamic at the time it is run, the resulting image is static and stored for later use. A server therefore can only be provisioned with a pre-existing server instance. What is needed is the ability to dynamically define the server instance at the time it is needed, as all possible conditions for the server cannot be predefined.

Software to be downloaded across a distributed computer network is predefined, typically in a profile that defines what software is to be downloaded, how the software is to be downloaded, and how the software is to be installed. The profile is static in nature, in that while it may be edited prior to use so that many different versions may coexist in slightly different forms, the profile, once specified for a particular download and the download started, cannot be modified.

Companies spend resources to create, test, install, and configure software. The final product may be spread across thousands of servers and client computers. An entire staff may be employed maintaining this structure, which includes hardware, software and configuration information. Collectively, the hardware, software and configuration information is known as the environment.

A company will need many environments. Some may be used for software creation, some for testing, some for installation and some for production. Different types of users interact with these environments at different stages. During creation, software engineers may write new applications in special development environments. During testing, product assurance teams may create and run test suites in development environments. During installation, production teams may develop production environments. During production, control teams may monitor the running of these environments and modify them as necessary.

Even "stable" production environments require changes. New versions of the operating system get released, as do new versions of the underlying software. Changes may need to be made to locally written or modified software. Data may change through internal or external factors.

1


Pag...