Novell, Inc.

International Business Machines Corporation

Apple Inc.

Emc Corporation

Micro Focus Software Inc.

Zack Traube Grossbart

Lee Edward Lowry

Brent W Thurgood

Volker Gunnar Scheuber-Heinz

William Street

Rajesh Vasudevan

Stephen R Carter

Ryan Cox

Karin Stella Lundberg

Steven Garrett Raden

Jennifer Erin Lanier

Lauren Marie Rice

Astha Jain

Joseph Henry Adamski

Megan Baxter Pollard

A method, system, and computer program product for implementing computer resource provisioning is provided. The method includes receiving a first request for identification credentials associated with a user. In response, resource identification credentials for the user are generated and a second request for generating a first computer resource is received in response to analyzing the resource identification credentials. The resource identification credentials are validated with respect to a local ID cache structure and it is determined if the resource identification credentials are available for usage by the user. In response, a resource implementation process is executed.

Computer resource provisioning

A method, system and computer program product for automatic IP range selection is provided. The GUI accepts user input for a parent IP range and IP range size, from which is calculated an address space prefix that corresponds to the address space that has the available IP range size. If the user does not provide input, the GUI fields are dynamically populated with default values for IP range, address prefix, address space, IP range, and number of addresses, wherein the default values are retrieved from a system IP network configuration.

Automatic IP range selection

Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Mechanisms to persist hierarchical object relations

Techniques managing complex dependencies in a file-based team environment are provided. A software module is represented as an object. The object is defined via a file. The file includes relationships, and some of the relationships define dependencies to other objects. In some cases, attributes for the object are also included in the file and are defined via references to still other objects. The relationships and the attributes are carried with the object via the file.

Managing complex dependencies in a file-based team environment

Mechanisms to build dynamic locations to reduce brittleness in a team environment are provided. A project includes resources, each resource is assigned a key. Each key is mapped to a current location for its corresponding resource. The keys and locations are maintained in an index. Locations for the resources can change as desired throughout the lifecycle of the project and as changes occur the index is updated. When references are made within the project to the resources, the references are translated to the keys, if necessary. The keys are then used for accessing the index and dynamically acquiring the current locations for the resources at the time the references are made.

Mechanism to build dynamic locations to reduce brittleness in a team environment

Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Mechanisms to support object-oriented version control operations

Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.

Growing community of inventors

Cambridge, MA, United States of America

Zack Traube Grossbart