Búsqueda Imágenes Maps Play YouTube Noticias Gmail Drive Más »
Iniciar sesión
Usuarios de lectores de pantalla: deben hacer clic en este enlace para utilizar el modo de accesibilidad. Este modo tiene las mismas funciones esenciales pero funciona mejor con el lector.

Patentes

  1. Búsqueda avanzada de patentes
Número de publicaciónUS8549513 B2
Tipo de publicaciónConcesión
Número de solicitudUS 11/169,973
Fecha de publicación1 Oct 2013
Fecha de presentación29 Jun 2005
Fecha de prioridad29 Jun 2005
TarifaPagadas
También publicado comoUS9317270, US20070006218, US20140033197, US20160077862
Número de publicación11169973, 169973, US 8549513 B2, US 8549513B2, US-B2-8549513, US8549513 B2, US8549513B2
InventoresAnders B. Vinberg, Robert M. Fries, Kevin Grealish, Galen C. Hunt, Aamer Hydrie, Rob Mensching, Geoffrey Outhred, John M. Parchem, Bassam Tabbara, Rene Antonio Vega, Robert V. Welland, Eric J. Winner, Jeffrey A. Woolsey
Cesionario originalMicrosoft Corporation
Exportar citaBiBTeX, EndNote, RefMan
Enlaces externos: USPTO, Cesión de USPTO, Espacenet
Model-based virtual system provisioning
US 8549513 B2
Resumen
Model-based virtual system provisioning includes accessing a model of a workload to be installed on a virtual machine of a system as well as a model of the system. A workload refers to some computing that is to be performed, and includes an application to be executed to perform the computing, and optionally includes the operating system on which the application is to be installed. The workload model identifies a source of the application and operating system of the workload, as well as constraints of the workload, such as resources and/or other capabilities that the virtual machine(s) on which the workload is to be installed must have. An installation specification for the application is also generated, the installation specification being derived at least in part from the model of the workload and the model of the virtual system.
Imágenes(7)
Previous page
Next page
Reclamaciones(17)
The invention claimed is:
1. A method comprising:
accessing a model of a workload to be installed on a virtual machine of a system wherein the workload includes an application and an operating system to be installed on the virtual machine, the model of the workload comprising a component that identifies a source of the application and a component that identifies the source of the operating system of the workload and the model identifying the relationship between the operating system and the application by identifying a corresponding relationship between components in the workload model;
accessing a model of the system wherein the virtual machine is to be created on a computing device to provide virtualized components of the system, the virtual machine emulates a computing environment that is compatible with the operating system and has the characteristics required to allow the application to run, the model of the system comprising components corresponding to the virtualized components of the system, the model identifying relationships among the virtualized components by identifying a corresponding relationship among the components of the model; and
generating an installation specification for the workload, the installation specification being derived at least in part from the model of the workload and the model of the system, wherein the installation specification identifies an image file of the workload that is to be copied to a storage device of a computing device of the system on which the virtual machine is created in order to install the workload on the virtual machine.
2. A method as recited in claim 1, having a virtual machine created on a computing device of the system prior to installing an application and operating system on the virtual machine.
3. A method as recited in claim 1, wherein the installation specification includes an indication to migrate another virtual machine from one computing device to another computing device.
4. A method as recited in claim 1, further comprising:
generating a plurality of device class installation specifications for the workload, each of the plurality of device class installation specifications being for a different one of a plurality of classes of devices in the system on which the workload could be installed.
5. A method as recited in claim 4, further comprising:
generating a record associating each of the plurality of device class installation specifications with one of the plurality of classes of devices.
6. A method as recited in claim 1, further comprising:
performing, prior to generating the installation specification, a logical deployment evaluation to determine whether the workload could be installed in the system, the performing comprising comparing constraints associated with the workload to constraints associated with the system.
7. A method as recited in claim 6, wherein the constraints associated with the workload include software licensing requirements that must be satisfied by the system.
8. A method as recited in claim 1, further comprising:
identifying, prior to generating the installation specification, which one or more computing devices of a plurality of computing devices in the system is to have the workload installed thereon.
9. One or more computer readable storage media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:
access a model of a workload to be installed on one or more virtual machines of a system, the workload includes an application and an operating system to be installed on the virtual machine, the model of the workload comprising components corresponding to the application and the operating system to be installed and identifying the relationship between the operating system and the application by identifying a corresponding relationship between components in the workload model;
access a model of the system wherein the one or more virtual machines are to be created on a computing device to provide virtualized components of the system wherein the virtual machine emulates a computing environment that is compatible with the operating system and has the characteristics required to allow the application to run, the model of the system comprising components corresponding to the virtualized components of the system, the model identifying relationships among the virtualized components by identifying a corresponding relationship among the components of the model; and
generate a workload installation specification for the workload to be installed on one or more virtual machines of a system, the workload installation specification being based at least in part on the model of the workload and the model of the system.
10. One or more computer readable media as recited in claim 9, wherein the installation specification identifies an image file of the workload that is to be copied to a storage device of one or more computing devices of the system on which the one or more virtual machines are created in order to install the workload on the one or more virtual machines.
11. One or more computer readable media as recited in claim 9, wherein the plurality of instructions further cause the one or more processors to:
trigger deployment of the workload based on one or more constraints in the model of the workload.
12. One or more computer readable media as recited in claim 9, wherein the plurality of instructions further cause the one or more processors to:
generate a plurality of device class installation specifications for the workload, each of the plurality of device class installation specifications being for a different one of a plurality of classes of devices on which the workload could be installed; and
include the plurality of device class installation specifications in the workload installation specification.
13. One or more computer readable media as recited in claim 9, wherein to generate the workload installation specification is to:
access a constraint information page in the model of the workload;
obtain default values for settings from the constraint information page; and
include, in the workload installation specification, the default values to be stored as settings on the one or more computing devices during installation of the workload on the one or more computing devices.
14. A computing device comprising:
a processor; and
a memory, coupled to the processor, to store instructions that, when executed by the processor, cause the processor to:
access a model of a workload to be installed on a virtual machine of a system, the model of the workload comprising components corresponding to components to be installed on the virtual machine, including at least an operating system and an application, and identifying the relationship between the components to be installed on the virtual machine by identifying a corresponding relationship between components in the workload model;
access a model of the system wherein the model of the computing components of the system is different from the computing components of a computing device on which the virtual machine is installed wherein the virtual machine emulates a computing environment that is compatible with the operating system and has the characteristics required to allow the application to run, the model of the system comprising components corresponding to the virtualized components of the system, the model identifying relationships among the virtualized components by identifying a corresponding relationship among the components of the model; and
generate an installation specification for the workload, the installation specification being derived at least in part from the model of the workload and the model of the system.
15. A computing device as recited in claim 14, wherein the virtual machine is to be installed on a computing device of the system prior to installing an application and operating system of the workload on the virtual machine.
16. A computing device as recited in claim 14, further comprising:
generating a plurality of device class installation specifications for the workload, each of the plurality of device class installation specifications being for a different one of a plurality of classes of devices in the system on which the workload could be installed.
17. A computing device as recited in claim 14, wherein the generating comprises:
accessing a constraint information page in the model of the workload;
obtaining default values for settings from the constraint information page; and
including, in the installation specification, the default values to be stored as settings on a computing device of the system during installation of the workload on the computing device.
Descripción
BACKGROUND

Computers have become increasingly commonplace in our world and offer a variety of different functionality. Some computers are designed primarily for individual use, while others are designed primarily to be accessed by multiple users and/or multiple other computers concurrently. These different functionalities are realized by the use of different hardware components as well as different software applications that are installed on the computers.

Although the variety of available computer functionality and software applications is a tremendous benefit to the end users of the computers, such a wide variety can be problematic for the developers of the software applications as well as system administrators that are tasked with keeping computers running. Such problems can arise, for example, because of differences in configurations or settings that are required by different software applications that a user may try to install on the same computer. Situations can arise where the settings required by one software application cause another software application to malfunction. By way of another example, situations can arise where two software applications have conflicting requirements on how the operating system on the computer should be configured. Such situations can cause one or both of the software applications, and possibly additional applications, to operate incorrectly if both are installed concurrently.

Accordingly, there is a need for an improved way to install software applications on computers.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

Model-based virtual system provisioning is described herein.

In accordance with certain aspects, a model of a workload to be installed on a virtual machine of a system as well as a model of the system are accessed. A workload refers to some computing that is to be performed, and includes an application to be executed to perform the computing, and optionally includes the operating system on which the application is to be installed. The workload model identifies a source of the application and operating system of the workload, as well as constraints of the workload, such as resources and/or other capabilities that the virtual machine(s) on which the workload is to be installed must have. An installation specification for the application is also generated, the installation specification being derived at least in part from the model of the workload and the model of the virtual system.

BRIEF DESCRIPTION OF THE DRAWINGS

The same numbers are used throughout the drawings to reference like features.

FIG. 1 illustrates an example system definition model (SDM) that can be used with the model-based virtual system provisioning described herein.

FIG. 2 illustrates an example use of types, configurations, and instances.

FIG. 3 is a flowchart illustrating an example process for provisioning a virtual system.

FIG. 4 illustrates an example workload installation specification in additional detail.

FIG. 5 is a flowchart illustrating an example of the generation of a workload installation specification for physical deployment in additional detail.

FIG. 6 illustrates an example general computer environment, which can be used to implement the techniques described herein.

DETAILED DESCRIPTION

Model-based virtual system provisioning is described herein. An installation specification for provisioning a computing device(s) is generated and subsequently used to provision the computing device(s). The installation specification describes how to install a workload on the computing device(s), the workload referring to some computing that is to be performed. The workload is installed on a virtual machine of the computing device(s), which is typically created as part of the installation process. The installation specification is derived at least in part from a model of the workload to be installed on the computing device(s) and a model of the system in which the application is to be installed (the system including the computing device(s)).

As used herein, an application refers to a collection of instructions that can be executed by a processor, such as a central processing unit (CPU) of a computing device. An application can be any of a variety of different types of software or firmware, or portions thereof. Examples of applications include programs that run on an operating system, the operating system, operating system components, services, infrastructure, middleware, portions of any of these, and so forth.

A system definition model (SDM) describes a system that can be managed. Management of a system can include, for example, installing software on the system, monitoring the performance of the system, maintaining configuration information about the system, verifying that constraints within the system are satisfied, combinations thereof, and so forth. A system can be, for example, an application, a single computing device, multiple computing devices networked together (e.g., via a private or personal network such as a local area network (LAN) or via a larger network such as the Internet), and so forth.

The systems discussed herein can be virtual systems that include one or more virtual machines. A virtual machine can be thought of as a computing device implemented in software. A virtual machine typically emulates a computing device, including all of the hardware components of a computing device, although in some cases the physical devices may be assigned directly to a virtual machine without emulation. A virtual machine runs on a computing device in its own isolated and self-contained environment, having its own operating system and optionally other software installed on it. Multiple virtual machines can be run on the same computing device, each of the multiple virtual machines having its own isolated environment and its own operating system installed thereon. A virtual system includes one or more computing devices that run a virtual machine. A virtual system can include one or more computing devices that already run a virtual machine and/or one or more computing devices that are to have a virtual machine provisioned thereon. A virtual machine can be provisioned on a computing device as part of the virtual system provisioning described herein.

In addition to conventional virtual machines, other forms of containers for workloads are being contemplated or implemented in the industry, such as “sandboxes” that allow a workload to run within an operating system that is shared with other workloads but which nonetheless provide the workloads more isolation than if the workloads were running directly in the operating system. These different containers can be viewed as “lightweight” virtual machines, in the sense that they provide many of the same benefits as traditional virtual machines with less cost or operational overhead. The techniques described herein can be used for such containers as well as traditional virtual systems, and references to virtual machines herein include such other forms of containers.

FIG. 1 illustrates an example SDM 100 that can be used with the model-based virtual system provisioning described herein. SDM 100 includes a component corresponding to each of one or more software and/or hardware components being managed in a virtual system. These software and/or hardware components being managed refer to those software and/or hardware components that the author of SDM 100 and/or designers of the system desires to include in SDM 100. Examples of hardware and/or software components that could be in a system include an application (such as a database application, email application, file server application, game, productivity application, operating system, and so forth), particular hardware on a computer (such as a network card, a hard disk drive, one of multiple processors, and so forth), a virtual machine, a computer, a group of multiple computers, and so on. A system refers to a collection of one or more hardware and/or software components.

SDM 100 represents a system including component 102, component 104, component 106, component 108, component 110, component 112, and component 114. Although the example SDM 100 includes seven components, in practice a system, and thus the SDM, can include any number of components.

For example, component 106 could represent a particular computer, while component 104 represents an operating system running on that particular computer. By way of another example, component 106 could represent an operating system, while component 104 represents a database application running on the operating system. By way of yet another example, component 114 could represent a particular computer, while component 112 represents an operating system installed on that particular computer, component 110 represents a virtual machine running on the operating system, and component 108 represents an operating system running on the virtual machine. Note that the operating systems associated with component 112 and component 108 could be the same or alternatively two different operating systems.

The SDM is intended to be a comprehensive knowledge store, containing all information used in managing the system. This information includes information regarding the particular components in the system, as well as relationships among the various components in the system. Despite this intent, it is to be appreciated that the SDM may contain only some of the information used in managing the system rather than all of the information.

Relationships can exist between different components in a system, and these relationships are typically illustrated in SDM diagrams with lines connecting the related components. Examples of relationships that can exist between components include containment relationships, hosting relationships, and communication relationships. Containment relationships identify one component as being contained by another component—data and definitions of the component being contained are incorporated into the containing component. When a component is installed on a system, any components contained in that component are also typically installed on the system. In FIG. 1, containment relationships are illustrated by the diagonal lines connecting component 102 and component 104, and connecting component 102 and component 108.

Hosting relationships identify dependencies among components. In a hosting relationship, the hosting component typically must be present in order for the guest component to be included in the system. In FIG. 1, hosting relationships are illustrated by the vertical lines connecting component 104 and component 106, connecting component 108 and component 110, connecting component 110 and 112, and connecting component 112 and 114.

Communication relationships identify components that can communicate with one another. Communication relationships may or may not imply that a dependency exists between the components. In FIG. 1, communication relationships are illustrated by the horizontal line connecting component 104 and component 108.

Associated with each component in SDM 100 is one or more information (info) pages. Information pages 122 are associated with component 102, information pages 124 are associated with component 104, information pages 126 are associated with component 106, information pages 128 are associated with component 108, information pages 130 are associated with component 110, information pages 132 are associated with component 112, and information pages 134 are associated with component 114. Each information page contains information about the associated component. Different types of information can be maintained for different components. One or more information pages can be associated with each component in SDM 100, and the particular information that is included in a particular information page can vary in different implementations. All the information can be included on a single information page, or alternatively different pieces of information can be grouped together in any desired manner and included on different pages. In certain embodiments, different pages contain different types of information, such as one page containing installation information and another page containing constraint information. Alternatively, different types of information may be included on the same page, such as installation information and constraint information being included on the same page.

Examples of types of information pages include installation pages, constraint pages, monitoring pages, service level agreement pages, description pages, and so forth. Installation pages include information describing how to install the associated component onto another component (e.g., install an application onto a computer), such as what files to copy onto a hard drive, what system settings need to be added or changed (such as data to include in an operating system registry), what configuration programs to run after files are copied onto the hard drive, sequencing specifications that identify that a particular installation or configuration step of one component should be completed before an installation or configuration step of another component, and so forth.

Constraint pages include information describing constraints for the associated component, including constraints to be imposed on the associated component, as well as constraints to be imposed on the system in which the associated component is being used (or is to be used). Constraints imposed on the associated component are settings that the component should have (or alternatively should not have) when the component is installed into a system. Constraints imposed on the system are settings (or other configuration items, such as the existence of another application or a piece of hardware) that the system should have (or alternatively should not have) in order for the associated component to be used in that particular system.

It should also be noted that constraints can flow across relationships. For example, constraints can identify settings that any component that is contained by the component, or that any component that contains the component, should have (or alternatively should not have). By way of another example, constraints can identify settings that any component that is hosted by the component, or that any component that hosts the component, should have (or alternatively should not have). By way of yet another example, constraints can identify settings that any component that communicates with the component should have (or alternatively should not have).

In addition, constraint pages may also include a description of how particular settings (or components) are to be discovered. For example, if a constraint indicates that an application should not co-exist with Microsoft® SQL Server, then the constraint page could also include a description of how to discover whether Microsoft® SQL Server is installed in the system. By way of another example, if a constraint indicates that available physical memory should exceed a certain threshold, then the constraint page could also include a description of how to discover the amount of available physical memory in the system. By way of still another example, if a constraint indicates that a security setting for Microsoft® SQL Server should have a particular value, then the constraint page could also include a description of how to discover the value of that security setting for Microsoft® SQL Server.

Constraint pages may also include a description of how particular settings are to be modified if they are discovered to not be in compliance with the constraints. Alternatively, the constraint pages could include specifications of some other action(s) to take if particular settings are discovered to not be in compliance with the constraints, such as sending an event into the system's event log, alerting an operator, starting a software application to take some corrective action, and so forth. Alternatively, the constraint pages could include a policy that describes what action to take under various circumstances, such as depending on the time of day, depending on the location of the system.

Constraint pages may also optionally include default values for at least some of these settings, identifying a default value to use within a range of values that satisfy the constraint. These default values can be used to assist in installation of an application, as discussed in more detail below.

Monitoring pages include information related to monitoring the performance and/or health of the associated component. This information can include rules describing how the associated component is to be monitored (e.g., what events or other criteria to look for when monitoring the component), as well as what actions to take when a particular rule is satisfied (e.g., record certain settings or what events occurred, sound an alarm, etc.).

Service level agreement pages include information describing agreements between two or more parties regarding the associated component (e.g., between the purchaser of the associated component and the seller from which the associated component was purchased). These can be accessed during operation of the system to determine, for example, whether the agreement reached between the two or more parties is being met by the parties.

Description pages include information describing the associated component, such as various settings for the component, or other characteristics of the component. These settings or characteristics can include a name or other identifier of the component, the manufacturer of the component, when the component was installed or manufactured, performance characteristics of the component, and so forth. For example, a description page associated with a component that represents a computing device may include information about the amount of memory installed in the computing device, a description page associated with a component that represents a processor may include information about the speed of the processor, a description page associated with a component that represents a hard drive may include information about the storage capacity of the hard drive and the speed of the hard drive, and so forth.

As can be seen in FIG. 1, an SDM maintains various information (e.g., installation, constraints, monitoring, etc.) regarding each component in the system. Despite the varied nature of these information pages, they are maintained together in the SDM and thus can all be readily accessed by various utilities or other applications involved in the management of the system.

An SDM can be generated and stored in any of a variety of different ways and using any of a variety of different data structures. For example, the SDM may be stored in a database. By way of another example, the SDM may be stored in a file or set of multiple files, the files being encoded in XML (Extensible Markup Language) or alternatively some other form. By way of yet another example, the SDM may not be explicitly stored, but constructed each time it is needed. The SDM could be constructed as needed from information existing in other forms, such as installation specifications.

In certain embodiments, the SDM is based on a data structure format including types, instances, and optionally configurations. Each component in the SDM corresponds to or is associated with a type, an instance, and possibly one or more configurations. Additionally, each type, instance, and configuration corresponding to a particular component can have its own information page(s). A type refers to a general template having corresponding information pages that describe the component generally. Typically, each different version of a component will correspond to its own type (e.g., version 1.0 of a software component would correspond to one type, while version 1.1 of that software component would correspond to another type). A configuration refers to a more specific template that can include more specific information for a particular class of the type. An instance refers to a specific occurrence of a type or configuration, and corresponds to an actual physical component (software, hardware, firmware, etc.).

For types, configurations, and instances associated with a component, information contained in information pages associated with an instance can be more specific or restrictive than, but generally cannot contradict or be broader than, the information contained in information pages associated with the type or the configuration. Similarly, information contained in information pages associated with a configuration can be more specific or restrictive than, but cannot contradict or be broader than, the information contained in information pages associated with the type. For example, if a constraint page associated with a type defines a range of values for a buffer size, the constraint page associated with the configuration or the instance could define a smaller range of values within that range of values, but could not define a range that exceeds that range of values.

It should be noted, however, that in certain circumstances a model of an existing system as deployed (that is, a particular instance of a system) may violate the information contained in information pages associated with the type for that existing system. This situation can arise, for example, where the system was deployed prior to an SDM for the system being created, or where a user (such as a system administrator) may have intentionally deployed the system in noncompliance with the information contained in information pages associated with the type for that existing system.

The use of types, configurations, and instances is illustrated in FIG. 2. In FIG. 2, a type 202 corresponds to a particular component. Three different instances 204, 206, and 208 of that particular component exist and are based on type 202. Additionally, a configuration (config) 210 exists which includes additional information for a particular class of the particular component, and two instances 212 and 214 of that particular class of the particular component.

For example, assume that a particular component is a database application. A type 202 corresponding to the database application is created, having an associated constraint information page. The constraint information page includes various general constraints for the database application. For example, one of the constraints may be a range of values that a particular buffer size should be within for the database application. Type 202 corresponds to the database application in general.

Each of the instances 204, 206, and 208 corresponds to a different example of the database application. Each of the instances 204, 206, and 208 is an actual database application, and can have its own associated information pages. For example, each instance could have its own associated description information page that could include a unique identifier of the particular associated database application. By way of another example, the constraint information page associated with each instance could include a smaller range of values for the buffer size than is indicated in the constraint information page associated with type 202.

The information pages corresponding to the instances in FIG. 2 can be in addition to, or alternatively in place of, the information pages corresponding to the type. For example, two constraint information pages may be associated with each instance 204, 206, and 208, the first constraint information page being a copy of the constraint information page associated with type 202 and the second constraint information page being the constraint information page associated with the particular instance and including constraints for just that instance. Alternatively, a single constraint information page may be associated with each instance 204, 206, and 208, the single constraint information page including the information from the constraint information page associated with type 202 as well as information specific to the particular instance. For example, the range of values that the particular buffer size should be within for the database application would be copied from the constraint information page associated with type 202 to the constraint information page associated with each instance. However, if the constraint information page for the instance indicated a different range of values for that particular buffer size, then that different range of values would remain in the constraint information page associated with the instance rather than copying the range of values from the constraint information page associated with type 202.

Following this example of a database application, configuration 210 corresponds to a particular class of the database application. For example, different classes of the database application may be defined based on the type of hardware the application is to be installed on, such as different settings based on whether the computer on which the database application is to be installed is publicly accessible (e.g., accessible via the Internet), or based on whether an operating system is already installed on the server. These different settings are included in the constraint information page associated with configuration 210.

Each of the instances 212 and 214 corresponds to a different example of the database application. Similar to instances 204, 206, and 208, each of instances 212 and 214 is an actual database application, and can have its own information page(s). However, unlike instances 204, 206, and 208, the constraint information pages associated with instances 212 and 214 each include the constraints that are in the constraint information page associated with configuration 210 as well as the constraints in the constraint information page associated with type 202.

It should be noted that, although the information pages are discussed as being separate from the components in the SDM, the data structure(s) implementing the SDM could alternatively include the information discussed as being included in the various information pages. Thus, the component data structures themselves could include the information discussed as being included in the various information pages rather than having separate information pages.

The installation page associated with a component can be used as a basis for provisioning a virtual system. Provisioning a virtual system refers to installing a workload on the virtual system, as well as making any necessary changes to the virtual system in order for the workload to be installed. Such necessary changes typically include creating a new virtual machine, and can also include other actions, such as installing an operating system on the computing device on which the new virtual machine runs or installing an operating system on the newly created virtual machine, setting configuration values for the operating system, installing one or more other applications, configuring a storage system to be accessible to the virtual machine, configuring networks to be accessible to the virtual machine, and so forth. In certain implementations, the workload is installed by creating a new virtual machine on a computing device and copying an image file to the storage device of the computing device. This image file includes an application(s) to be run to perform the computing of the workload, and also typically includes the operating system on which the application(s) is to be run.

In the discussions herein, reference is made to different classes of computing devices. Each of these different classes of computing devices refers to computing devices having particular common characteristics, so they are grouped together and viewed as a class of devices. Examples of different classes of devices include IIS (Internet Information Services) servers that are accessible to the Internet, IIS servers that are accessible only on an internal intranet, database servers, email servers, order processing servers, desktop computers, and so forth. Typically, each different class of computing device corresponds to one of the configurations in the system model.

These different classes of computing devices can be different classes of physical devices, as well as different classes of virtual machines. The classes may distinguish between virtual machine classes and physical device classes. For example, one class may be database virtual machines, another class may be database physical servers (not running the database on a virtual machine), another class may be an order processing virtual machine, another class may be an order processing physical server (not running the order processing application(s) on a virtual machine), and so forth. Alternatively, the classes may not distinguish between virtual machine classes and physical device classes. For example, a single database server class may be used for database servers regardless of whether the database application(s) are run on a virtual machine or a computing device without a virtual machine(s).

Provisioning of virtual systems is based in part on workloads. Generally, a workload is some computing that is to be performed. A workload typically includes an application to be executed to perform the computing, and can also include the operating system on which the application is to be installed. Various configuration information describing how the application and/or operating system is to be configured, as well as data to be used by the application and/or operating system when executing, can also be included in the workload. A model of the workload includes the application, operating system, configuration information, and/or data, as well as constraints of the workload such as resources and/or other capabilities that the virtual machine(s) on which the workload is to be installed must have. Examples of these constraints are discussed below.

FIG. 3 is a flowchart illustrating an example process 300 for provisioning a virtual system. Portions of process 300 can be implemented in software, firmware, and/or hardware.

Initially, a model of a workload is built (act 302). As discussed above, the workload typically includes the application to be installed on a virtual system, and can also include the operating system, configuration information, and/or data. Alternatively, the workload may not include an application, but may include an operating system (or components of an operating system), configuration information, and/or data. The model of the workload can also include one or more constraints.

This building process in act 302 is typically performed by the developer of the workload, although could alternatively be performed by others. This model is an SDM model of the workload, analogous to model 100 of FIG. 1, and includes one or more components. The model of the workload includes types and optionally configurations. As part of the building process in act 302, zero or more information pages are associated with each component in the model. Typically, at least a constraint information page is associated with each component in the model.

As part of the building process in act 302, types and optionally configurations are defined, along with associated information page(s). The types and configurations can be standard types or configurations that are copied or modified in act 302, or alternatively can be newly created in act 302. As discussed above, different constraints can be included in the configuration information page associated with the type and the configuration information page associated with the configuration. The specific constraints included in the configuration information page for a particular workload can vary based on the particular computing to be performed and/or the desires of the designer of the workload.

The constraints included on a constraint information page can take a variety of forms, such as: hardware requirements regarding the computing device(s) or other hardware on which the application is to be installed (e.g., a minimum processor speed, a minimum amount of memory, a minimum amount of free hard drive space, a minimum amount of network bandwidth available, particular security mechanisms available, and so forth), software requirements regarding the computing device(s) or other hardware or software on which the workload is to be installed (e.g., a particular operating system that should already be installed on the computing device(s), one or more other applications that should already be installed on the computing device(s), specifications regarding how particular hardware and/or the operating system is to be configured such as particular settings for the operating system that should already be made, a particular type of security or encryption that should be in use, and so forth, requirements regarding a virtual machine that should be created on a computing device as well as requirements regarding an operating system that should be installed on the virtual machine before the application can be installed thereon, other requirements regarding the computing device(s) on which the workload is to be installed (e.g., particular security keys available, data center policies that should be enforced, authentication that is used, system topology, etc.), and so on.

Constraints can be positive requirements specifying that something should be present (e.g., the processor should have at least a minimum processor speed, or the Windows® XP operating system should already be installed on the computing device). Constraints can also be negative requirements specifying that something should not be present (e.g., one or more particular applications should not already be installed on the computing device, or particular operating system settings should not be present).

One example constraint of the workload is a number and/or size of CPUs that the system on which the workload is to be installed must have. This constraint can identify a specific number of CPUs that the system must have (e.g., 1 CPU, 2 CPUs, 4 CPUs, etc.), or a range of CPUs that the system must have (e.g., 2 to 4 CPUs). The constraint can also specify the size of the CPUs that are needed, referring to the fraction of a CPU that is needed (e.g., a workload may require 100% of 1 CPU, or 50% of each of 2 CPUs). Both requirements and recommendations can be specified (e.g., a minimum of 2 CPUs is required, but 4 or more CPUs should be used if possible).

Another example constraint of the workload is an amount of memory (e.g., RAM). This constraint typically identifies a minimum amount of memory that the system on which the workload is to be installed must have. Both requirements and recommendations can be specified (e.g., a minimum of 2 GB of memory is required, but 4 GB or more of memory should be used if possible).

Another example constraint of the workload is an amount of storage space (e.g., hard disk space, optical disk space, etc.). This constraint typically identifies a minimum amount of storage space that the system on which the workload is to be installed must have. Both requirements and recommendations can be specified (e.g., a minimum of 10 GB of storage space is required, but 15 GB or more of storage space should be used if possible).

Another example constraint of the workload is the hardware type or architecture. For example, particular types of CPUs, particular bus or memory speeds, particular co-processors, and so forth may be required and/or recommended.

Another example constraint of the workload is the type of storage available to the system. This constraint can specify performance and reliability characteristics of the storage (e.g., RAID 1 or RAID 5 is required). This constraint can also specify that access to particular systems or databases is required. Both requirements and recommendations can be specified (e.g., RAID 1 or RAID 5 is required, but RAID 5 should be used if possible).

Another example constraint of the workload is the schedule for the workload, referring to when the computing that is to be performed should be started and/or ended. Both requirements and recommendations can be specified (e.g., the computing must end by 6:00 am, but should end by 5:00 am if possible).

Another example constraint is the events that should trigger the deployment of the workload, referring to when the computing that is to be performed should be started and/or ended. For example, when the same workload is operating on several computing devices with tasks assigned to the individual devices and/or virtual machines by a load balancing device, a monitoring system may determine that the number of incoming requests is exceeding the aggregate capacity of the devices and/or virtual machines, and may send an event indicating that another instance of that workload should be deployed to help carry the load. By way of another example, when a running workload fails because of a software or hardware problem, a monitoring system may send an event that indicates that a replacement copy of that workload should be deployed.

The constraints may also include a combination of events and schedules. For example, a workload may be started by a schedule, and the constraints specify that the workload should be ended and removed from the computing device when processing is finished, as indicated by an event; however, if the processing is not completed when the “batch window closes” at 6:00 am, the workload should be paused and removed from the computing device, and restarted to continue processing when the next “batch window” opens at the following midnight.

These constraints of the workload can refer to constraints on the physical hardware of the virtual system and/or constraints on the virtual hardware of a virtual machine of the virtual system. The model of the workload identifies whether the constraints refer to physical hardware or virtual hardware. Typically, the constraints of the workload identify constraints of the virtual hardware, and these constraints can be compared to the constraints of the system to verify that a virtual machine having virtual hardware satisfying these constraints of the workload can be created. Alternatively, the constraints of the workload can be compared to the constraints of currently running virtual machines to verify that a virtual machine having virtual hardware satisfying these constraints of the workload exists. In another alternative, the constraints of the workload identify constraints of the physical hardware, and these constraints can be compared to the constraints of the system to verify that a computing device satisfying these constraints exists.

Additionally, the workload may have different constraints that apply for different types of deployment. For example, if the workload is deployed and started from a state where it is not previously running, a certain set of constraints apply, but if the workload is started after having been previously executing, paused and saved in a virtual machine image file, another set of constraints apply, and if the workload is to be moved from one computing device to another through a migration process, yet another set of constraints apply.

Additionally, a model of the system where the application is to be installed is built (act 304). This building process in act 304 is typically performed by an administrator of the system where the application is to be installed, although could alternatively be performed by others. This model is an SDM model of the system analogous to model 100 of FIG. 1, and includes one or more components. The model of the virtual system includes types and instances, and optionally configurations.

The system in act 304 can be referred to as a virtual system, although the virtual machine(s) onto which the application and the operating system of the workload are to be installed may not yet be created. As such, the system in act 304 describes the physical computing devices on which virtual machines may be created, and describes virtual machines that have already been created, but does not describe virtual machines that have not yet been created.

The system in act 304 could be a single computing device, or alternatively multiple computing devices. For example, if the application will be installed on a virtual machine of a computing device in a data center having a thousand computing devices, then the model of the system where the application is to be installed will include those thousand computing devices. By way of another example, if the application will be installed on a virtual machine of a home computer that is not coupled to any other computers, then the model of the system where the application is to be installed will include just that home computer.

It should also be noted that the exact nature of a computing device can vary, and that any of a wide variety of computing devices can be a system in act 304. For example, “hierarchical” computers can exist, such as a rack that can contain multiple chassis, each chassis can contain multiple blades, each blade can contain multiple motherboards, each motherboard can contain multiple processors, and each processor can contain multiple cores. Any of these components of such a hierarchical computer can be viewed as a computing device (e.g., the rack can be a computing device, each chassis can be a computing device, each blade can be a computing device, each motherboard can be a computing device, each processor can be a computing device, and/or each core can be a computing device).

The characteristics of each computing device in the hierarchy, and the characteristics of the containment, hosting and communications relationships among them, are typically significant for the placement of virtual machines on those computing devices. For example, the speed of the connection may determine how a workload can be deployed, and therefore a constraint in the workload model indicates that the workload cannot be deployed across several computing devices at a level in the hierarchy where the connection speed is too slow. By way of another example, while it may be possible to deploy a workload down to the level of a single core, it may not be desirable to do so because of unpredictable performance interactions between workloads on the cores within one processor, and in this case the workload model has constraints that the workload should not be deployed on a computing device below the level of a processor in the hierarchy, or below a level where certain performance guarantees can be met, which would be described in the model of the computing device. By way of yet another example, a particular constraint on the workload may specify the software licensing requirements for various types of deployment, where operating systems and applications would have different rules about the licenses required when deploying the workload on a processor, or on a blade with many processors, or across several blades. Under these types of constraints, a particular computing device may not have enough licenses to allow the workload to be deployed, even though it may have enough processing power, memory and storage.

Oftentimes, the model of the system built in act 304 will be generated by the system administrator prior to the workload being designed and the model of the workload being built in act 302. In such situations, the previously generated model can be accessed and need not be re-built in act 304.

Components in the model of the system built in act 304 will include constraint information pages. These constraint information pages include constraints for each component in the virtual system. Such constraint information pages can identify constraints for the corresponding component, and optionally constraints that should be satisfied by any application to be installed on the corresponding component. Both the constraints on the workload and the characteristics of the system may be time-series data, in addition to the possibly time-based nature of the deployment schedule. For example, if once started the workload requires only 1 CPU for half an hour, and then needs 4 CPUs for half an hour, this sequence of values can be represented in the constraints. Similarly, if a computing device has 8 CPUs, but 2 of them are assigned to a workload for 1 hour, and 4 of them are assigned to a workload for 3 hours, and after that no more work is assigned to the computing device, the number of available CPUs can be calculated as 2 CPUs for 1 hour, 4 CPUs for 2 hours after that, and 8 CPUs after that. This time series of available CPUs can be recorded in the characteristics page of the system model

Based on the models built in acts 302 and 304, a logical deployment evaluation is performed (act 306). The logical deployment evaluation involves comparing the model of the workload (from act 302) to the model of the system (from act 304) to determine whether the application could be installed in the system. Typically, the application designer or system administrator will identify a particular class (or classes) of computing device on which he or she desires to install the application. Alternatively, the application may be compared to all classes of computing devices in the system.

The constraints and/or description information for the workload are compared to the constraints for that class of computing device to determine whether the workload satisfies the constraints of the class of computing device, and the constraints and/or description information for the class of computing device are compared to the constraints for the workload to determine whether the class of computing device satisfies the constraints of the workload. The constraints and description information for all components of the class of computing device, including any applications that are hosted by the class of computing device (e.g., an operating system as well as possibly other applications) are also accessed as part of the logical deployment evaluation. These constraints used in the logical deployment evaluation can include constraints that are flowed across relationships, as discussed above. These constraints used in the logical deployment evaluation can also include time-series based constraints, as discussed above. Accessing the constraints for the operating system and other applications allows verification that, if installed on a device of the class of computing device, settings made on the computing device for the workload would not conflict with current settings for other applications installed on the computing device. The verification can use the scheduled start time of the workload, and the time-series of constraints and system characteristics, and can verify that the time profile of resources available on the system satisfies the time profile of requirements of the workload. In embodiments in which a virtual machine is being installed onto which the application will be installed, the evaluation in act 306 includes evaluating that any constraints of the virtual machine are satisfied by the class of computing device in order to verify that the virtual machine can be installed on the class of computing device.

By way of example, a particular constraint on the class of computing device may indicate that a software firewall should always be running on the class of computing device. A description page associated with the workload would be accessed to verify that the workload does not require a software firewall to be deactivated.

By way of another example, a particular constraint on the workload may indicate that the computing device should have a minimum processor speed. A description page associated with the class of computing device (or the processor of the class of computing device) would be accessed to verify that the speed of the processor is at least the minimum processor speed. As discussed above, this processor speed could refer to the speed of the virtual processor of the virtual machine on which the workload would be installed, or the speed of the physical processor of the class of computing device on which the virtual machine is installed. Furthermore, the fractional parts of the physical processor may be allocated to each virtual machine, and each such fractional part serves as the virtual processor for the virtual machine to which the part is allocated. As a fractional part of the physical processor could not be allocated as a virtual processor with a faster speed than the physical processor, a check would be made to ensure that the speed of the physical processor satisfies the constraint. Furthermore, a check would also be made that the fractional part of the physical processor can be allocated to the virtual machine to create a virtual processor that satisfies the constraint. This check can be performed by checking a description page associated with the system, or by communicating a request or query to a virtual system management component as to whether it would be able to create such a virtual machine having a virtual processor satisfying the constraint. It is to be appreciated that such speeds of virtual processors can vary depending on the number of other virtual machines that are already running on the computing device, as the presence of such other virtual machines will affect the fractional part of the physical processor that can be allocated to the virtual machine.

By way of yet another example, a particular constraint on the workload may indicate that the computing of the workload should be performed between midnight and 4:00 am. A description page associated with the class of computing device would be accessed to verify that the computing device has sufficient processing capacity (in light of other workloads already scheduled to be performed between midnight and 4:00 am) to have a new virtual machine (or alternatively an existing virtual machine) perform the computing of the workload.

It should be noted that, depending on the manner in which virtual machines are created and managed, it may be possible for a class of computing device to “overcommit” its resources. For example, three different virtual machines may each require 4 GB of memory, but a particular class of computing device may only have 8 GB of memory. In such situations, all three virtual machines could be run on that class of computing device by running only two of the three virtual machines concurrently, or all three virtual machines could be run simultaneously (on the assumption that the workloads will on the average share some memory pages that are used for read-only access). By way of another example, two different virtual machines may each require 100 GB of storage space, but a particular class of computing device may only have 160 GB of storage space. In such situations, both virtual machines could be run on that class of computing device by running the two virtual machines at separate times, or both virtual machines could be run simultaneously (on the assumption that they will not both make full demands on the storage space at the same time). The models of the workloads indicate whether such overcommitment is possible and whether it is desirable.

It should also be noted that whatever components are referenced by constraints in the SDM are evaluated in act 306, regardless of what those components are. Typically, constraints of the class of computing device are evaluated in act 306 down to the layer that is hosting the workload being installed, but may extend to other layers if referenced in the SDM. By way of example, assume that a virtual machine is being provisioned on a computing device, and a workload is being provisioned on the virtual machine. Typically, constraints of the virtual machine would be evaluated against the computing device and the operating system running on the computing device, while constraints of the workload would be evaluated against the virtual machine. However, if the workload had a constraint referencing the computing device itself (e.g., regarding physical protection of the computing device on which the workload is deployed), then that constraint of the workload would be evaluated against the computing device.

The results of the evaluation in act 306 can be returned to the workload designer and/or system administrator. An indication of success (if all of the constraints are satisfied) or failure (if all of the constraints are not satisfied) can be returned. In addition, if one or more of the constraints are not satisfied, then an indication of which constraint was not satisfied can be returned, as well as optionally an indication of which component caused the constraint to not be satisfied. Optionally, the evaluation can indicate whether the constraints that were not satisfied were mandatory or recommended constraints. Returning such information can assist the workload developer in modifying the workload so that it can be installed in the system, and in choosing which of the available systems would be most suited for the workload.

Process 300 then proceeds based on the results of the evaluation in act 306. If the evaluation indicates that the workload can be installed in the system, then process 300 can proceed to act 308. Act 306 may also optionally be repeated for a different class of computing device in the system. However, if the evaluation indicates that the workload cannot be installed in the system, then the evaluation of act 306 can be repeated for a different class of computing device in the virtual system, or alternatively the workload may be modified in order to overcome the problem(s) identified in the evaluation of act 306, and process 300 can return to act 302 to build a model of the modified workload. If time-series based constraints are not met by the system, and if the scheduled start time is specified as a recommended rather than required start time, the verification can evaluate whether the constraints can be met by a later or earlier start time and can return a list of possible classes of computing devices with the possible start time for each one.

In act 308, physical deployment of the workload is determined. Determining physical deployment of the workload refers to identifying which particular computing device(s) will perform the computing of the workload (and optionally have a new virtual machine created thereon to perform the computing of the workload). The particular computing device(s) which will perform the computing of the workload can be identified in different manners. One way in which the particular computing device(s) will perform the computing of the workload can be identified is manually, such as by a system administrator or other party manually selecting a particular computing device(s). This manually selected computing device(s) could be a computing device already(s) in the system, or alternatively a new computing device(s) that needs to be purchased or a computing device(s) that needs to be removed from storage and added to the system (e.g., coupled to the network that the other computing devices in the system are coupled to).

Alternatively, the particular computing device(s) which will perform the computing of the workload can be identified automatically. An application running in the system can identify various characteristics of the computing devices on which a virtual machine could be created and the workload installed thereon (e.g., the computing devices of the particular class of computing device on which the application is to be installed), such as load characteristics of each computing device. The load characteristics could identify, for example, the average or maximum amount of processor usage, the average amount of memory usage, the amount of available network bandwidth being used, the amount of hard disk drive space being used, and so forth. Based on these load characteristics, the computing device(s) most likely to be able to support the new virtual machine and the workload would be identified as the computing device(s) on which the computing of the workload is to be performed (e.g., the computing device having the lightest load, such as the lowest average processor usage, the smallest amount of available network bandwidth being used, the most hard disk drive space available, and so forth). If no computing device can meet the recommended schedule, but several can meet the required schedule, the computing device that comes closest to meeting the recommended schedule could be identified.

It should be noted that typically a new virtual machine is created as part of installing the workload. Thus, the characteristics of the computing devices are evaluated for purposes of determining which computing device(s) will have the new virtual machine created thereon and will perform the computing of the workload. Alternatively, a new virtual machine may not be created, and the workload may be installed on an already running virtual machine. In such situations, the characteristics of the currently running virtual machines are evaluated for purposes of determining which virtual machine(s) will perform the computing of the workload.

Alternatively, the particular computing device(s) which will perform the computing of the workload can be identified in a semi-automatic manner. An application running in the system can identify various characteristics of the computing devices on which the virtual machine could possibly be created and the computing of the workload could possibly be performed (or characteristics of the virtual machines on which the workload could possibly be performed) analogous to the automatic manner, and then present those results to a user (such as the system administrator) for manual selection of one or more of the computing devices (or virtual machines). One or more of the computing devices may optionally be recommended to the user as the best candidate(s) for selection, but the ultimate selection would remain at the user's discretion.

Additionally, priorities of different workloads may be used as part of the physical deployment determining of act 308. Workloads can optionally be assigned priorities, allowing the importance of the workloads relative to one another to be identified. These priorities are typically included in the model of the workload or the workload itself, but alternatively may be maintained elsewhere. Higher priority workloads can be given access to resources of the virtual system before lower priority workloads. This can result in situations where, for example, higher priority workloads can be performed by a computing device(s), but there are insufficient resources for lower priority workloads to be performed. This can also result in situations where, for example, higher priority workloads are given the resources recommended by the constraints of the workload, whereas lower priority workloads are given only the resources required by the constraints of the workload.

In addition, selection of different sources of data and/or other systems to which access is needed may be performed as part of the physical deployment determining of act 308. For example, multiple sources may exist from which data identified as being required in the model of the workload can be obtained, or multiple replicated file servers may exist that can be a file server identified as being required in the model of the workload. Particular sources of data and/or other systems to which access is needed may be selected in act 308 based on various factors, such as the load on the various sources and/or other systems, the bandwidth of the connection to those sources and/or systems, and so forth. Alternatively, rather than being performed as part of act 308, selection of such sources of data and/or other systems to which access is needed may be performed as part of the physical deployment in act 312 discussed below.

It should be noted that one additional factor that can be optionally taken into account when identifying the characteristics of the various computing devices is that virtual machines can be rearranged to run on different computing devices. For example, a virtual machine running on one computing device could be moved to another computing device, thereby freeing up capacity on the original computing device. Such a process of moving or rearranging virtual machines is also referred to as migration of the virtual machines. Virtual machines can be migrated in any of a variety of manners, such as with the assistance of the Virtual Server Migration Toolkit (VSMT) available from Microsoft Corporation of Redmond, Wash.

Accounting for the possibility of migrating virtual machines allows the load characteristics of the computing devices to be changed by migrating the virtual machines. For example, the situation may arise where none of the computing devices have the desired spare capacity to create a virtual machine on which the application could be installed, but that capacity of one of the computing devices could be released by moving a virtual machine from that one computing device to another of the computing devices. After the virtual machine is moved, however, the released capacity results in that one computing device having sufficient capacity so that the new virtual machine on which the application is to be installed can be created and the application installed on that new virtual machine.

This identification of which computing device should perform the computing of the workload, and optionally which virtual machines should be migrated to different computing devices, is performed as part of the physical deployment determining of act 308.

A workload installation specification for physical deployment of the workload is then generated (act 310). The workload installation specification can be saved as an installation page associated with the component representing the workload in the workload model. The workload installation specification includes an identification, for each class of device in the virtual system on which the workload may be installed, of how to install the workload. As each of these identifications indicates how to install the workload on a particular class of devices, these identifications can also be referred to as device class installation specifications. The device class installation specifications can also identify which particular computing device(s) of that class the workload is to be installed on (the computing device(s) determined in act 308).

This identification of how to install the workload includes, for example, all of the settings for the virtual machine to be created on the device, the operating system to install on the virtual machine (including all of the settings of the operating system and the identification of all of the files that need to be copied to the virtual machine to install the operating system), all of the settings of the computing device that should be made or changed, an identification of all of the files that need to be copied to the computing device and where those files should be copied, an order in which files should be copied and/or settings made or changed, any initialization programs that need to be run after the files have been copied and/or settings made or changed, and so forth. This identification may also include installing an operating system and/or one or more additional applications on the computing device prior to creating the virtual machine on the device. For example, one class of computing device may be a bare computing device with no operating system installed on it. In such situations, the installation specification for that class of computing device would include initially installing the appropriate operating system on the computing device, followed by creating the virtual machine on the computing device, then installing an operating system on the virtual machine, and then installing the application on that operating system of the virtual machine.

In certain implementations, this identification of how to install the workload identifies a particular image file that is the image to be run to perform the computing of the workload. The image file can be created as part of the process of building the model of the workload in act 302, or alternatively can be created at other times (e.g., after the logical deployment evaluation has been performed in act 306). The image file includes the application files and data, and optionally the files and data for the operating system on which the application will be executed, for the workload. The image file can be copied to a disk drive or other storage device and executed by a virtual machine to perform the computing of the workload—no additional installation or configuration of the operating system or the application of the workload is typically required. The image file can be generated in any of a variety of conventional manners, such as by installing the application and operating system onto a virtual machine and generating a file that includes all the folders and files installed onto that virtual machine, by a user (e.g., the designer of the workload) manually identifying the folders and files to be included in the image file, and so forth. The image file can then be simply copied to the computing device(s) as part of the physical deployment in act 312 discussed below.

Additionally, if any migration of virtual machines is to be performed for a particular class of device, as identified in act 308, then the device class installation specification for that class of device includes an indication of the migration that is to be performed and the constraints that must be met for that type of migration.

At least a portion of each device class installation specification can be generated automatically based on the information contained in the information pages associated with the workload to be installed. As discussed above, the constraint information page can include various default values. These default values can be used during act 310 to identify the settings or configuration values that should be set when installing the workload, and thus which should be included in the device class installation specification. For example, a particular default value may be included in the configuration information page for a buffer size. This default value would be included in the device class installation specification so that when the workload is installed on a particular computing device, the computing device settings (such as in an operating system registry) can be modified to include this default value for the buffer size (possibly replacing another value for the buffer size previously stored in the computing device settings).

In addition to default values, other constraint information included in the constraint information page can be used in act 310 to identify the settings or configuration values that should be set when installing the workload. If a range of values for a particular setting were included in the constraint information page, then a setting to be used when installing the application can be derived from that range. For example, the lowest value in the range could be selected, the highest value in the range could be selected, the average of the highest and lowest values in the range could be computed and selected, a value in the range could be selected randomly, and so forth.

Furthermore, in addition to information contained in the information pages associated with the workload, information contained in the information pages associated with the virtual system (such as the computing device on which the application is to be installed) can be used as a basis for automatically generating at least a portion of each device class installation specification. Default values and/or ranges of values can be used to automatically generate values for the device class installation specification in the same manner as discussed above.

It should also be noted that different components can have different constraints and different default values for the same settings or configuration values. In such situations, even though there is overlap of the constraints so that the different components can all be installed on a computing device, one or more of the default values may violate the constraints of another component. Thus, a suitable value that is compliant with the constraints of all of the components is determined. This suitable value can be determined in different manners, including manually, automatically, and semi-automatically. A suitable value can be determined manually by a user (such as the system administrator) inputting a suitable value for the setting or configuration value.

A suitable value can be determined automatically by evaluating the various constraints and selecting a value that satisfies all the constraints. This selected value is then used as the suitable value. For example, if each constraint lists a range of acceptable values, then a value that falls within each range of acceptable values can be automatically identified and used as the suitable value.

A suitable value can be determined semi-automatically by evaluating the various constraints and selecting a value that satisfies all the constraints analogous to the automatic manner. However, rather than automatically using the selected value as the suitable value, the selected value can be presented to a user (such as the system administrator) for approval. The user can accept this selected value, or alternatively input a different value. Alternatively, rather than presenting a single selected value to the user, the range of possible values (or portion of the range of possible values) that satisfies the constraints of the different components may be presented to the user.

It should further be noted that at least a portion of a device class installation specification may be generated manually rather than automatically. This manual generation refers to user inputs (such as by the application developer or system administrator) rather than automatic generation by some component or module (e.g., development module 400 discussed below). For example, the particular files to be identified in the device class installation specification may be identified manually rather than automatically.

Additionally, an assignment record is generated in act 310 that maintains a record of which device class installation specifications are to be used for which device classes. This record can be, for example, a mapping of device class to device class installation specification. Thus, given the workload installation specification including multiple device class installation specifications, a determination as to which particular device class installation specification to use can be made based on the class of the device on which the workload is to be installed. The assignment record generated can also be stored as part of the workload installation specification.

Alternatively, rather than having a separate assignment record, an identification of which device class installation specification is associated with which particular class of device may be maintained in other manners. For example, the indication may be inherent in the naming convention used for the device class installation specification (e.g., each device class installation specification may be a separate file having a file name that identifies the particular class of device), or each device class installation specification may include an indication of the associated class of device.

The workload installation specification is generated after the logical deployment evaluation in act 306. Thus, the application installation specification is generated only after it is verified that the workload can be installed in the system. Additionally, the constraint information (such as default values) associated with the workload can be used to determine settings to be included in the workload installation specification. Thus, it can be seen that the workload installation specification generated in act 310 is derived at least in part from the model of the workload as well as the model of the system.

After the workload installation specification is created, physical deployment of the workload is performed (act 312). The timing of the physical deployment can vary. Deployment may be triggered manually, such as by a user (such as the system administrator) specifying that deployment should begin “now” or at a particular time in the future. Deployment may also be triggered based on other events and/or schedules identified in the workload as discussed above.

In certain implementations, this physical deployment includes making the workload installation specification available to a deployment system and having the deployment system create a new virtual machine on the particular device identified in act 308, and also copy the image file identified by the workload on the particular device identified in act 308 for execution by the newly created virtual machine. In other implementations, this physical deployment includes making the workload installation specification available to a deployment system and having the deployment system create a new virtual machine on the particular device identified in act 308 and install the application on that new virtual machine following the installation instructions in the workload installation specification.

Once the deployment system is given the workload installation specification, the deployment system operates in a conventional manner to install the workload. If the application installation specification indicates that migration of any virtual machines is to be performed, then this migration can also be carried out by the deployment system (optionally with the assistance of another component, such as the Virtual Server Migration Toolkit discussed above). Any of a variety of deployment systems could be used in act 312, such as the Windows® Installer service or Microsoft® Systems Management Server, both available from Microsoft Corporation of Redmond, Wash.

Once the workload is installed on a computing device, the new virtual machine and the application installed thereon becomes part of the system and thus the workload model is incorporated into the system model and a component for the new virtual machine (as well as the operating system for the new virtual machine, and any other components running on the virtual machine) is added to the system model. Thus, after installation of the application, the SDM for the system includes the SDM of the workload. This includes modifying characteristics of the system such as available number of CPUs, which might be time-series based to reflect the allocation of CPUs to scheduled workloads and the time-series based requirements of CPUs of those workloads.

Alternatively, the evaluation in act 306 may be for a particular computing device or virtual machine rather than for a class of computing device. In this alternative, the evaluation in act 306 is the same as discussed above, except that constraint and description information for a particular instance of a computing device are used rather than constraint and description information for a class of computing device. In such situations, the identification of the particular computing device is made in, or prior to, act 306 rather than in act 308, and can be made in the same manner as discussed in act 308.

It should also be noted that a particular device class installation specification may indicate to install the whole workload or individual components of the workload on multiple different computing devices within the system. For example, the workload developer or system administrator may desire to install the workload on all of the computing devices of a particular class. By way of another example, the workload developer or system administrator may desire to install each part of the workload on a computing device of a specific class. In such a situation, an indication is included in the device class installation specification for that particular device class that the workload is to be installed on all of the computing devices of that particular class, or alternatively may identify the particular computing devices (e.g., by name or other unique identifier) on which the workload is to be installed. The installation instructions may also identify the sequence in which the parts of the workload are to be installed on each system, and how to coordinate the installation steps by waiting for the completion of one step before proceeding with the next, using conventional orchestration technologies. The deployment system used to install the workload receives this indication and installs the workload on the appropriate computing devices.

FIG. 4 illustrates an example workload installation specification in additional detail. An installation specification development module 400 generates a workload installation specification 402. Installation specification module 400 can be implemented in software, firmware, hardware, or combinations thereof, and can perform act 310 of FIG. 3, and optionally additional acts of FIG. 3 (such as act 306 and/or act 308). Workload installation specification 402 includes multiple (x) device class installation specifications 404(1), 404(2), . . . 404(x). Each of the device class installation specifications 404 identifies how the workload is to be installed on a particular class of computing device. Workload installation specification 402 also includes specification assignment record 406 to identify which specification 404 corresponds to which class of computing device.

Workload installation specification 402 is input to a deployment system 408 along with any necessary installation file(s) 410. Installation file(s) 410 include the file(s) that are to be installed on the computing device in order to install the application, such as one or more files of executable code, one or more files of data, an image file, and so forth. Alternatively, although illustrated separately, workload installation specification 402 and installation file(s) 410 may be stored together in a single package (e.g., a compressed file).

FIG. 5 is a flowchart illustrating the generation of a workload installation specification for physical deployment of act 310 of FIG. 3 in additional detail. FIG. 5 can be implemented in software, firmware, and/or hardware.

Initially, a device class on which the workload could be installed is selected (act 502). In certain embodiments the system administrator and/or workload developer (or alternatively some other party) may desire that the workload be installed only on certain classes of devices, in which case the devices on which the workload could be installed is less than all of the devices in the system. Alternatively, the workload may be able to be installed on any device in the system.

A device class installation specification for the selected device class is then generated, identifying how to install the workload and virtual machine on the selected device class (act 504). As discussed above, this generation can include using default values included in an information page associated with the workload in the workload model for setting values to include in the installation specification being generated.

In some situations, the device class installation specification is generated in a format that is expected and understood by a deployment system that will be installing the workload and the virtual machine. The device class installation specification may be generated in this format in act 504, or alternatively may be subsequently translated into this format (e.g., by a translation component of the distribution system).

It should be noted that different device installation specifications may be generated for computing devices that will have the same functionality but are currently configured differently, such as computing devices that do not yet have an operating system installed and computing devices that already have an operating system installed. Alternatively, such computing devices may be considered to be part of the same device class, but the device class installation specification would include a conditional portion to be used based on the configuration of the particular instance of the computing device on which the application is being installed (e.g., the conditional portion may be bypassed if the computing device already has an installed operating system, or used to install an operating system on the computing device if an operating system is not already installed on the computing device).

A check is then made as to whether there are any additional device class(es) in the virtual system for which no device class installation specification has been generated (act 506). If there are any such additional device class(es), then one such additional device class is selected (act 508) and the process returns to act 504 to generate a device class installation specification for the selected device class.

Returning to act 506, if device class installation specifications have been generated for all of the device class(es), then a specification assignment record is generated associating particular installation specifications with particular device classes (act 510). Alternatively, the specification assignment record may be generated in act 504 as the device class installation specifications are being generated, and an indication of which device class is associated with which device class installation specification added to the specification assignment record as the device class installation specification is generated.

The device class installation specifications generated in act 504 and the assignment record generated in act 510 are then combined into a workload installation specification for the application (act 512).

FIG. 6 illustrates an example general computer environment 600, which can be used to implement the techniques described herein. The computer environment 600 is only one example of a computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the computer and network architectures. Neither should the computer environment 600 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example computer environment 600.

Computer environment 600 includes a general-purpose computing device in the form of a computer 602. Computer 602 can be, for example, a computing device on which an application is installed or a computing device on which at least portions of process 300 of FIG. 3 are implemented. Computer 602 can be, for example, a desktop computer, a handheld computer, a notebook or laptop computer, a server computer, a game console, and so on. The components of computer 602 can include, but are not limited to, one or more processors or processing units 604, a system memory 606, and a system bus 608 that couples various system components including the processor 604 to the system memory 606.

The system bus 608 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus.

Computer 602 typically includes a variety of computer readable media. Such media can be any available media that is accessible by computer 602 and includes both volatile and non-volatile media, removable and non-removable media.

The system memory 606 includes computer readable media in the form of volatile memory, such as random access memory (RAM) 610, and/or non-volatile memory, such as read only memory (ROM) 612. A basic input/output system (BIOS) 614, containing the basic routines that help to transfer information between elements within computer 602, such as during start-up, is stored in ROM 612. RAM 610 typically contains data and/or program modules that are immediately accessible to and/or presently operated on by the processing unit 604.

Computer 602 may also include other removable/non-removable, volatile/non-volatile computer storage media. By way of example, FIG. 6 illustrates a hard disk drive 616 for reading from and writing to a non-removable, non-volatile magnetic media (not shown), a magnetic disk drive 618 for reading from and writing to a removable, non-volatile magnetic disk 620 (e.g., a “floppy disk”), and an optical disk drive 622 for reading from and/or writing to a removable, non-volatile optical disk 624 such as a CD-ROM, DVD-ROM, or other optical media. The hard disk drive 616, magnetic disk drive 618, and optical disk drive 622 are each connected to the system bus 608 by one or more data media interfaces 626. Alternatively, the hard disk drive 616, magnetic disk drive 618, and optical disk drive 622 can be connected to the system bus 608 by one or more interfaces (not shown).

The disk drives and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for computer 602. Although the example illustrates a hard disk 616, a removable magnetic disk 620, and a removable optical disk 624, it is to be appreciated that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like, can also be utilized to implement the exemplary computing system and environment.

Any number of program modules can be stored on the hard disk 616, magnetic disk 620, optical disk 624, ROM 612, and/or RAM 610, including by way of example, an operating system 626, one or more application programs 628, other program modules 630, and program data 632. Each of such operating system 626, one or more application programs 628, other program modules 630, and program data 632 (or some combination thereof) may implement all or part of the resident components that support the distributed file system.

A user can enter commands and information into computer 602 via input devices such as a keyboard 634 and a pointing device 636 (e.g., a “mouse”). Other input devices 638 (not shown specifically) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to the processing unit 604 via input/output interfaces 640 that are coupled to the system bus 608, but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus (USB).

A monitor 642 or other type of display device can also be connected to the system bus 608 via an interface, such as a video adapter 644. In addition to the monitor 642, other output peripheral devices can include components such as speakers (not shown) and a printer 646 which can be connected to computer 602 via the input/output interfaces 640.

Computer 602 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computing device 648. By way of example, the remote computing device 648 can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and the like. The remote computing device 648 is illustrated as a portable computer that can include many or all of the elements and features described herein relative to computer 602.

Logical connections between computer 602 and the remote computer 648 are depicted as a local area network (LAN) 650 and a general wide area network (WAN) 652. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

When implemented in a LAN networking environment, the computer 602 is connected to a local network 650 via a network interface or adapter 654. When implemented in a WAN networking environment, the computer 602 typically includes a modem 656 or other means for establishing communications over the wide network 652. The modem 656, which can be internal or external to computer 602, can be connected to the system bus 608 via the input/output interfaces 640 or other appropriate mechanisms. It is to be appreciated that the illustrated network connections are exemplary and that other means of establishing communication link(s) between the computers 602 and 648 can be employed.

In a networked environment, such as that illustrated with computing environment 600, program modules depicted relative to the computer 602, or portions thereof, may be stored in a remote memory storage device. By way of example, remote application programs 658 reside on a memory device of remote computer 648. For purposes of illustration, application programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device 602, and are executed by the data processor(s) of the computer.

Various modules and techniques may be described herein in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.

An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer storage media” and “communications media.”

“Computer storage media” includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

“Communication media” typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism. Communication media also includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.

Alternatively, portions of the framework may be implemented in hardware or a combination of hardware, software, and/or firmware. For example, one or more application specific integrated circuits (ASICs) or programmable logic devices (PLDs) could be designed or programmed to implement one or more portions of the framework.

CONCLUSION

Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.

Citas de patentes
Patente citada Fecha de presentación Fecha de publicación Solicitante Título
US42007706 Sep 197729 Abr 1980Stanford UniversityCryptographic apparatus and method
US42185826 Oct 197719 Ago 1980The Board Of Trustees Of The Leland Stanford Junior UniversityPublic key cryptographic apparatus and method
US440582914 Dic 197720 Sep 1983Massachusetts Institute Of TechnologyCryptographic communications system and method
US44244141 May 19783 Ene 1984Board Of Trustees Of The Leland Stanford Junior UniversityExponentiation cryptographic apparatus and method
US503108930 Dic 19889 Jul 1991United States Of America As Represented By The Administrator, National Aeronautics And Space AdministrationDynamic resource allocation scheme for distributed heterogeneous computer systems
US522062131 Jul 199115 Jun 1993International Business Machines CorporationCharacter recognition system using the generalized hough transformation and method
US543081018 Jun 19934 Jul 1995Imra America, Inc.Real time implementation of the hough transform
US54902761 Mar 19956 Feb 1996Echelon CorporationProgramming language structures for use in a network for communicating, sensing and controlling information
US549561013 Jul 199527 Feb 1996Seer Technologies, Inc.Software distribution system to build and distribute a software release
US549935719 Ago 199412 Mar 1996Xerox CorporationProcess for configuration management
US550492116 May 19942 Abr 1996Cabletron Systems, Inc.Network management system using model-based intelligence
US555777417 Mar 199417 Sep 1996Hitachi, Ltd.Method for making test environmental programs
US557948226 Jul 199526 Nov 1996Echelon CorporationMethod and apparatus for storing interface information in a computer system
US566899522 Abr 199416 Sep 1997Ncr CorporationMethod and apparatus for capacity planning for multiprocessor computer systems in client/server environments
US568694023 Dic 199411 Nov 1997Rohm Co., Ltd.Display apparatus
US57245089 Mar 19953 Mar 1998Insoft, Inc.Apparatus for collaborative computing
US574895830 Abr 19965 May 1998International Business Machines CorporationSystem for utilizing batch requests to present membership changes to process groups
US57583511 Mar 199526 May 1998Sterling Software, Inc.System and method for the creation and use of surrogate information system objects
US576827112 Abr 199616 Jun 1998Alcatel Data Networks Inc.Virtual private network
US577468922 Sep 199530 Jun 1998Bell Atlantic Network Services, Inc.Network configuration management system for digital communication networks
US57844634 Dic 199621 Jul 1998V-One CorporationToken distribution, registration, and dynamic configuration of user entitlement for an application level security system and method
US579089518 Oct 19964 Ago 1998Compaq Computer CorporationModem sharing
US581893712 Ago 19966 Oct 1998Ncr CorporationTelephone tone security device
US582253122 Jul 199613 Oct 1998International Business Machines CorporationMethod and system for dynamically reconfiguring a cluster of computer systems
US582601520 Feb 199720 Oct 1998Digital Equipment CorporationMethod and apparatus for secure remote programming of firmware and configurations of a computer over a network
US5835777 *20 Mar 199610 Nov 1998Hewlett-Packard CompanyMethod of automatically generating a software installation package
US58451241 May 19961 Dic 1998Ncr CorporationSystems and methods for generating and displaying a symbolic representation of a network model
US584527719 Dic 19961 Dic 1998Mci Communications CorporationProduction of statistically-based network maps
US586770619 Dic 19962 Feb 1999International Business Machines Corp.Method of load balancing across the processors of a server
US587292825 May 199516 Feb 1999Cabletron Systems, Inc.Method and apparatus for defining and enforcing policies for configuration management in communications networks
US58782204 Nov 19972 Mar 1999Oracle CorporationMethod and apparatus for storing and transferring data on a network
US58954993 Jul 199520 Abr 1999Sun Microsystems, Inc.Cross-domain data transfer using deferred page remapping
US590572810 Dic 199618 May 1999Electronics And Telecommunications Research InstituteMethod of assigning connection identifier in asynchronous transfer mode switching system
US591773016 Ago 199629 Jun 1999Gse Process Solutions, Inc.Computer implemented object oriented visualization system and method
US593079815 Ago 199627 Jul 1999Predicate Logic, Inc.Universal data measurement, analysis and control system
US595800927 Feb 199728 Sep 1999Hewlett-Packard CompanySystem and method for efficiently monitoring quality of service in a distributed processing environment
US59681262 Abr 199719 Oct 1999Switchsoft Systems, Inc.User-based binding of network stations to broadcast domains
US603540522 Dic 19977 Mar 2000Nortel Networks CorporationSecure virtual LANs
US604105424 Sep 199721 Mar 2000Telefonaktiebolaget Lm EricssonEfficient transport of internet protocol packets using asynchronous transfer mode adaptation layer two
US604732327 Jun 19964 Abr 2000Hewlett-Packard CompanyCreation and migration of distributed streams in clusters of networked computers
US604952830 Jun 199711 Abr 2000Sun Microsystems, Inc.Trunking ethernet-compatible networks
US605246914 Ago 199818 Abr 2000International Business Machines CorporationInteroperable cryptographic key recovery system with verification by comparison
US605984214 Abr 19989 May 2000International Business Machines Corp.System and method for optimizing computer software and hardware
US60650589 May 199716 May 2000International Business Machines Corp.Dynamic push filtering based on information exchanged among nodes in a proxy hierarchy
US60757766 Jun 199713 Jun 2000Nippon Telegraph And Telephone CorporationVLAN control system and method
US60761086 Mar 199813 Jun 2000I2 Technologies, Inc.System and method for maintaining a state for a user session using a web system having a global session server
US608182611 Mar 199727 Jun 2000Hitachi, Ltd.System using environment manager with resource table in each computer for managing distributed computing resources managed for each application
US608523822 Abr 19974 Jul 2000Matsushita Electric Works, Ltd.Virtual LAN system
US608661826 Ene 199811 Jul 2000Microsoft CorporationMethod and computer program product for estimating total resource usage requirements of a server application in a hypothetical user configuration
US61087022 Dic 199822 Ago 2000Micromuse, Inc.Method and apparatus for determining accurate topology features of a network
US611224330 Dic 199629 Ago 2000Intel CorporationMethod and apparatus for allocating tasks to remote networked processors
US611539321 Jul 19955 Sep 2000Concord Communications, Inc.Network monitoring
US61187857 Abr 199812 Sep 20003Com CorporationPoint-to-point protocol with a signaling channel
US612544212 Dic 199726 Sep 2000Maves International Software, Inc.Method, system and data structures for computer software application development and execution
US612544711 Dic 199726 Sep 2000Sun Microsystems, Inc.Protection domains to provide security in a computer system
US613459428 Oct 199717 Oct 2000Microsoft CorporationMulti-user, multiple tier distributed application architecture with single-user access control of middle tier objects
US614799531 Ago 199914 Nov 2000Cabletron Systems, Inc.Method for establishing restricted broadcast groups in a switched network
US615168814 Feb 199821 Nov 2000Novell, Inc.Resource management in a clustered computer system
US616705227 Abr 199826 Dic 2000Vpnx.Com, Inc.Establishing connectivity in networks
US616738322 Sep 199826 Dic 2000Dell Usa, LpMethod and apparatus for providing customer configured machines at an internet site
US61785293 Nov 199723 Ene 2001Microsoft CorporationMethod and system for resource monitoring of disparate resources in a server cluster
US618227526 Ene 199830 Ene 2001Dell Usa, L.P.Generation of a compatible order for a computer system
US618530826 Mar 19986 Feb 2001Fujitsu LimitedKey recovery system
US619240110 Mar 199920 Feb 2001Sun Microsystems, Inc.System and method for determining cluster membership in a heterogeneous distributed system
US619509110 Dic 199727 Feb 2001Netscape Communications CorporationApparatus for collaborative computing
US619535524 Sep 199827 Feb 2001Sony CorporationPacket-Transmission control method and packet-transmission control apparatus
US62083458 Jun 199827 Mar 2001Adc Telecommunications, Inc.Visual data integration system and method
US620864911 Mar 199827 Mar 2001Cisco Technology, Inc.Derived VLAN mapping technique
US620909914 Jul 199727 Mar 2001Ncr CorporationSecure data processing method and system
US621255928 Oct 19983 Abr 2001Trw Inc.Automated configuration of internet-like computer networks
US622678822 Jul 19981 May 2001Cisco Technology, Inc.Extensible network management system
US623031220 Nov 19988 May 2001Microsoft CorporationAutomatic detection of per-unit location constraints
US623361027 Ago 199715 May 2001Northern Telecom LimitedCommunications network having management system architecture supporting reuse
US62363658 Sep 199722 May 2001Tracbeam, LlcLocation of a mobile station using a plurality of commercial wireless infrastructures
US623690131 Mar 199822 May 2001Dell Usa, L.P.Manufacturing system and method for assembly of computer systems in a build-to-order environment
US623702030 Sep 199722 May 2001International Business Machines CorporationTask-oriented automatic distribution of software
US625323022 Sep 199826 Jun 2001International Business Machines CorporationDistributed scalable device for selecting a server from a server cluster and a switched path to the selected server
US625677331 Ago 19993 Jul 2001Accenture LlpSystem, method and article of manufacture for configuration management in a development architecture framework
US62594483 Jun 199810 Jul 2001International Business Machines CorporationResource model configuration and deployment in a distributed computer network
US62630891 Oct 199817 Jul 2001Nippon Telephone And Telegraph CorporationMethod and equipment for extracting image features from image sequence
US626670717 Ago 199824 Jul 2001International Business Machines CorporationSystem and method for IP network address translation and IP filtering with dynamic address resolution
US626907628 May 199831 Jul 20013Com CorporationMethod of resolving split virtual LANs utilizing a network management system
US626907923 Feb 200031 Jul 2001International Business Machines CorporationSystems, methods and computer program products for distributing connection information between ATM nodes
US63049723 Ene 200016 Oct 2001Massachusetts Institute Of TechnologySecure software system and related techniques
US63050151 Jul 199816 Oct 2001Bull S.A.Information processing system architecture
US631114431 Jul 199830 Oct 2001Nabil A. Abu El AtaMethod and apparatus for designing and analyzing information systems using multi-layer mathematical models
US631127014 Sep 199830 Oct 2001International Business Machines CorporationMethod and apparatus for securing communication utilizing a security processor
US633060519 Nov 199811 Dic 2001Volera, Inc.Proxy cache cluster
US633613825 Ago 19981 Ene 2002Hewlett-Packard CompanyTemplate-driven approach for generating models on network services
US633811218 May 20008 Ene 2002Novell, Inc.Resource management in a clustered computer system
US63516855 Nov 199926 Feb 2002International Business Machines CorporationWireless communication between multiple intelligent pickers and with a central job queue in an automated data storage library
US635386118 Jun 19965 Mar 2002Echelon CorporationMethod and apparatus for treating a logical programming expression as an event in an event-driven computer environment
US635389818 May 20005 Mar 2002Novell, Inc.Resource management in a clustered computer system
US63602658 Jul 199819 Mar 2002Lucent Technologies Inc.Arrangement of delivering internet protocol datagrams for multimedia services to the same server
US63670102 Jul 19992 Abr 2002Postx CorporationMethod for generating secure symmetric encryption and decryption
US637057331 Ago 19999 Abr 2002Accenture LlpSystem, method and article of manufacture for managing an environment of a development architecture framework
US63705841 Sep 19989 Abr 2002Trustees Of Boston UniversityDistributed routing
US637799618 Feb 199923 Abr 2002International Business Machines CorporationSystem for seamless streaming of data stored on a network of distributed primary and target servers using segmentation information exchanged among all servers during streaming
US638946427 Jun 199714 May 2002Cornet Technology, Inc.Device management system for managing standards-compliant and non-compliant network elements using standard management protocols and a universal site server which is configurable from remote locations via internet browser technology
US639338626 Mar 199821 May 2002Visual Networks Technologies, Inc.Dynamic modeling of complex networks and prediction of impacts of faults therein
US639345630 Nov 199821 May 2002Microsoft CorporationSystem, method, and computer program product for workflow processing using internet interoperable electronic messaging with mime multiple content type
US639347431 Dic 199821 May 20023Com CorporationDynamic policy management apparatus and method using active network devices
US639348527 Oct 199821 May 2002International Business Machines CorporationMethod and apparatus for managing clustered computer systems
US640839016 Ago 199918 Jun 2002Mitsubishi CorporationApparatus for data copyright management system
US641855421 Sep 19989 Jul 2002Microsoft CorporationSoftware implementation installer mechanism
US642471811 Jun 199723 Jul 2002International Business Machines CorporationData communications system using public key cryptography in a web environment
US64249928 Oct 199723 Jul 2002International Business Machines CorporationAffinity-based router and routing method
US642716310 Jul 199830 Jul 2002International Business Machines CorporationHighly scalable and highly available cluster system management scheme
US642717128 Feb 200030 Jul 2002Alacritech, Inc.Protocol processing stack for use with intelligent network interface device
US64381005 Ago 199920 Ago 2002Alcatel Canada Inc.Method and apparatus for routing server redundancy in a network having carrier scale internetworking
US644255727 Feb 199827 Ago 2002Prc Inc.Evaluation of enterprise architecture model including relational database
US644271330 Mar 199927 Ago 2002International Business Machines CorporationCluster node distress signal
US644965021 May 199910 Sep 2002Redback Networks Inc.Methods and apparatus for deploying quality of service policies on a data communication network
US64570487 Mar 200124 Sep 2002Sun Microsystems, Inc.System for representing device topology in a computer network operable independent of network management software
US64635365 Jun 20018 Oct 2002Mitsubishi CorporationData copyright management system
US64669859 Abr 199915 Oct 2002At&T Corp.Method and apparatus for providing quality of service using the internet protocol
US64700252 Feb 199922 Oct 20023Com TechnologiesSystem for providing fair access for VLANs to a shared transmission medium
US647046423 Feb 199922 Oct 2002International Business Machines CorporationSystem and method for predicting computer system performance and for making recommendations for improving its performance
US647379117 Ago 199829 Oct 2002Microsoft CorporationObject load balancing
US64809559 Jul 199912 Nov 2002Lsi Logic CorporationMethods and apparatus for committing configuration changes to managed devices prior to completion of the configuration change
US648426111 Dic 199819 Nov 2002Cisco Technology, Inc.Graphical network security policy management
US65021314 Dic 199831 Dic 2002Novell, Inc.Directory enabled policy management tool for intelligent traffic management
US650524429 Jun 19997 Ene 2003Cisco Technology Inc.Policy engine which supports application specific plug-ins for enforcing policies in a feedback-based, adaptive data network
US651961518 Oct 200011 Feb 2003Sun Microsystems, Inc.Method and system for leasing storage
US652995317 Dic 19994 Mar 2003Reliable Network SolutionsScalable computer network resource monitoring and location system
US653949417 Jun 199925 Mar 2003Art Technology Group, Inc.Internet server session backup apparatus
US654642322 Oct 19998 Abr 2003At&T Corp.System and method for network load balancing
US65465538 Jul 19998 Abr 2003Microsoft CorporationService installation on a base function and provision of a pass function with a service-free base function semantic
US65499341 Mar 199915 Abr 2003Microsoft CorporationMethod and system for remote access to computer devices via client managed server buffers exclusively allocated to the client
US65642619 May 200013 May 2003Telefonaktiebolaget Lm Ericsson (Publ)Distributed system to intelligently establish sessions between anonymous users over various networks
US657084718 Mar 199927 May 2003At&T Corp.Method and system for network traffic rate control based on fractional tokens
US657087513 Oct 199827 May 2003Intel CorporationAutomatic filtering and creation of virtual LANs among a plurality of switch ports
US657419519 Abr 20003 Jun 2003Caspian Networks, Inc.Micro-flow management
US65844999 Jul 199924 Jun 2003Lsi Logic CorporationMethods and apparatus for performing mass operations on a plurality of managed devices on a network
US658787624 Ago 19991 Jul 2003Hewlett-Packard Development CompanyGrouping targets of management policies
US65979562 Ago 200022 Jul 2003Terraspring, Inc.Method and apparatus for controlling an extensible computing system
US659803314 Jul 199722 Jul 2003Nortel Networks LimitedProblem model for alarm correlation
US65980775 Dic 200022 Jul 2003Warp Solutions, Inc.System and method for dynamic content routing
US659817311 Oct 200022 Jul 2003Micron Technology, Inc.Method of remote access and control of environmental conditions
US65982236 Oct 199922 Jul 2003Dell Usa, L.P.Method and system for installing and testing build-to-order components in a defined configuration computer system
US660110115 Mar 200029 Jul 20033Com CorporationTransparent access to network attached devices
US660123330 Jul 199929 Jul 2003Accenture LlpBusiness components framework
US660670824 Sep 199812 Ago 2003Worldcom, Inc.Secure server architecture for Web based data management
US660914810 Nov 199919 Ago 2003Randy SaloClients remote access to enterprise networks employing enterprise gateway servers in a centralized data center converting plurality of data requests for messaging and collaboration into a single request
US660921310 Ago 200019 Ago 2003Dell Products, L.P.Cluster-based system and method of recovery from server failures
US661152218 Jun 199926 Ago 2003Juniper Networks, Inc.Quality of service facility in a device for performing IP forwarding and ATM switching
US662867119 Ene 199930 Sep 2003Vtstarcom, Inc.Instant activation of point-to point protocol (PPP) connection using existing PPP state
US663114127 May 19997 Oct 2003Ibm CorporationMethods, systems and computer program products for selecting an aggregator interface
US664030322 Sep 200028 Oct 2003Ky Quy VuSystem and method for encryption using transparent keys
US66511019 Jul 200218 Nov 2003Cisco Technology, Inc.Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows
US665124028 Dic 199918 Nov 2003Fujitsu LimitedObject-oriented software development support apparatus and development support method
US665478220 Dic 199925 Nov 2003Networks Associates, Inc.Modular framework for dynamically processing network events using action sets in a distributed computing environment
US66547967 Oct 199925 Nov 2003Cisco Technology, Inc.System for managing cluster of network switches using IP address for commander switch and redirecting a managing request via forwarding an HTTP connection to an expansion switch
US666571430 Jun 199916 Dic 2003Emc CorporationMethod and apparatus for determining an identity of a network device
US667169920 May 200030 Dic 2003Equipe Communications CorporationShared database usage in network devices
US66753089 May 20006 Ene 20043Com CorporationMethods of determining whether a network interface card entry within the system registry pertains to physical hardware or to a virtual device
US667882123 Mar 200013 Ene 2004E-Witness Inc.Method and system for restricting access to the private key of a user in a public key infrastructure
US667883512 Jun 200013 Ene 2004AlcatelState transition protocol for high availability units
US668126228 Jun 200220 Ene 2004Infinicon SystemsNetwork data flow optimization
US669114824 Dic 199810 Feb 2004Verizon Corporate Services Group Inc.Framework for providing quality of service requirements in a distributed object-oriented computer system
US669116512 Abr 200010 Feb 2004Rainfinity, Inc.Distributed server cluster for controlling network traffic
US66911688 Feb 199910 Feb 2004Pmc-SierraMethod and apparatus for high-speed network rule processing
US669443619 May 199917 Feb 2004ActivcardTerminal and system for performing secure electronic transactions
US670136329 Feb 20002 Mar 2004International Business Machines CorporationMethod, computer program product, and system for deriving web transaction performance metrics
US671794931 Ago 19986 Abr 2004International Business Machines CorporationSystem and method for IP network address translation using selective masquerade
US67183617 Abr 20006 Abr 2004Network Appliance Inc.Method and apparatus for reliable and scalable distribution of data files in distributed networks
US67183799 Jun 20006 Abr 2004Advanced Micro Devices, Inc.System and method for network management of local area networks having non-blocking network switches configured for switching data packets between subnetworks based on management policies
US672525328 Jul 200020 Abr 2004Fujitsu LimitedLoad balancing system
US67288858 Oct 199927 Abr 2004Networks Associates Technology, Inc.System and method for network access control using adaptive proxies
US67355967 Jun 200111 May 2004Guy Charles CorynenComputer method and user interface for decision analysis and for global system optimization
US67387366 Oct 200018 May 2004Accenture LlpMethod and estimator for providing capacacity modeling and planning
US674126629 Ago 200025 May 2004Fujitsu LimitedGui display, and recording medium including a computerized method stored therein for realizing the gui display
US67420208 Jun 200025 May 2004Hewlett-Packard Development Company, L.P.System and method for managing data flow and measuring service in a storage network
US67484477 Abr 20008 Jun 2004Network Appliance, Inc.Method and apparatus for scalable distribution of information in a distributed network
US675471611 Feb 200022 Jun 2004Ensim CorporationRestricting communication between network devices on a common network
US675481626 Oct 200022 Jun 2004Dell Products L.P.Scalable environmental data calculation method customized by system configuration
US675774412 May 199929 Jun 2004Unisys CorporationDistributed transport communications manager with messaging subsystem for high-speed communications between heterogeneous computer systems
US676076520 Oct 20006 Jul 2004Matsushita Electric Industrial Co., Ltd.Cluster server apparatus
US67607756 Mar 20006 Jul 2004At&T Corp.System, method and apparatus for network service load and reliability management
US676900810 Ene 200027 Jul 2004Sun Microsystems, Inc.Method and apparatus for dynamically altering configurations of clustered computer systems
US676906025 Oct 200027 Jul 2004Ericsson Inc.Method of bilateral identity authentication
US677901611 Feb 200017 Ago 2004Terraspring, Inc.Extensible computing system
US678240830 Mar 199924 Ago 2004International Business Machines CorporationControlling a number of instances of an application running in a computing environment
US67890901 Jun 19997 Sep 2004Hitachi, Ltd.Virtual network displaying system
US68015283 Jul 20025 Oct 2004Ericsson Inc.System and method for dynamic simultaneous connection to multiple service providers
US680193731 May 20005 Oct 2004International Business Machines CorporationMethod, system and program products for defining nodes to a cluster
US68019498 May 20005 Oct 2004Rainfinity, Inc.Distributed server cluster with graphical user interface
US680478318 Abr 200012 Oct 2004Network Engineering SoftwareFirewall providing enhanced network security and user transparency
US681377817 Jul 20002 Nov 2004General Instruments CorporationMethod and system for downloading and managing the enablement of a list of code objects
US681689730 Abr 20019 Nov 2004Opsware, Inc.Console mapping tool for automated deployment and management of network devices
US682004224 Jul 200016 Nov 2004Opnet TechnologiesMixed mode network simulator
US682012124 Ago 200016 Nov 2004International Business Machines CorporationMethods systems and computer program products for processing an event based on policy rules using hashing
US68232999 Jul 199923 Nov 2004Autodesk, Inc.Modeling objects, systems, and simulations by establishing relationships in an event-driven graph in a computer implemented graphics system
US682337311 Ago 200023 Nov 2004Informatica CorporationSystem and method for coupling remote data stores and mobile devices via an internet based server
US682338220 Ago 200123 Nov 2004Altaworks CorporationMonitoring and control engine for multi-tiered service-level management of distributed web-application servers
US682963915 Nov 19997 Dic 2004Netvision, Inc.Method and system for intelligent global event notification and control within a distributed computing environment
US682977023 Feb 19997 Dic 2004Microsoft CorporationObject connectivity through loosely coupled publish and subscribe events
US683675023 Abr 200128 Dic 2004Hewlett-Packard Development Company, L.P.Systems and methods for providing an automated diagnostic audit for cluster computer systems
US683934830 Abr 19994 Ene 2005Cisco Technology, Inc.System and method for distributing multicasts in virtual local area networks
US684516014 Oct 199918 Ene 2005Fuji Xerox Co., Ltd.Apparatus and method for depositing encryption keys
US684797011 Sep 200225 Ene 2005International Business Machines CorporationMethods and apparatus for managing dependencies in distributed systems
US685384125 Oct 20008 Feb 2005Sun Microsystems, Inc.Protocol for a remote control device to enable control of network attached devices
US68540692 May 20018 Feb 2005Sun Microsystems Inc.Method and system for achieving high availability in a networked computer system
US685659115 Dic 200015 Feb 2005Cisco Technology, Inc.Method and system for high reliability cluster management
US686261310 Ene 20001 Mar 2005Sun Microsystems, Inc.Method and apparatus for managing operations of clustered computer systems
US686806228 Mar 200015 Mar 2005Intel CorporationManaging data traffic on multiple ports
US68684543 May 200015 Mar 2005Fujitsu LimitedDistributed-object development system and computer-readable recording medium recorded with program for making computer execute distributed-object development
US687992613 Nov 200112 Abr 2005National Instruments CorporationMeasurement system software architecture for easily creating high-performance measurement applications
US688000218 Mar 200212 Abr 2005Surgient, Inc.Virtualized logical server cloud providing non-deterministic allocation of logical attributes of logical servers to physical resources
US688603824 Oct 200026 Abr 2005Microsoft CorporationSystem and method for restricting data transfers and managing software components of distributed computers
US688880710 Jun 20023 May 2005Ipr Licensing, Inc.Applying session services based on packet flows
US689553426 Oct 200117 May 2005Hewlett-Packard Development Company, L.P.Systems and methods for providing automated diagnostic services for a cluster computer system
US689879121 Abr 199924 May 2005California Institute Of TechnologyInfospheres distributed object system
US690445826 Abr 20007 Jun 2005Microsoft CorporationSystem and method for remote management
US690739524 Oct 200014 Jun 2005Microsoft CorporationSystem and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US691256827 Jul 200028 Jun 2005Hitachi, Ltd.Service management system
US691265720 Feb 200128 Jun 2005Telefonaktiebolaget Lm EricssonMethod and arrangement in a communication network
US691533824 Oct 20005 Jul 2005Microsoft CorporationSystem and method providing automatic policy enforcement in a multi-computer service application
US69227919 Ago 200126 Jul 2005Dell Products L.P.Failover system and method for cluster environment
US692848229 Jun 20009 Ago 2005Cisco Technology, Inc.Method and apparatus for scalable process flow load balancing of a multiplicity of parallel packet processors in a digital communication network
US694418312 Jun 200013 Sep 2005AlcatelObject model for network policy management
US694467818 Jun 200113 Sep 2005Transtech Networks Usa, Inc.Content-aware application switch and methods thereof
US694475929 Sep 200013 Sep 2005Hewlett-Packard Development Company, L.P.Automatic system configuration management
US694798729 May 199820 Sep 2005Ncr CorporationMethod and apparatus for allocating network resources and changing the allocation based on dynamic workload changes
US695493019 Feb 200211 Oct 2005International Business Machines CorporationRemote validation of installation input data
US695718627 May 199918 Oct 2005Accenture LlpSystem method and article of manufacture for building, managing, and supporting various components of a system
US696398129 Ene 20028 Nov 2005Akamai Technologies, Inc.Method and apparatus for remote installation of an operating system over a network connection
US69682914 Nov 200322 Nov 2005Sun Microsystems, Inc.Using and generating finite state machines to monitor system status
US696853530 Abr 200222 Nov 2005Sun Microsystems, Inc.Service mapping method of enterprise application modeling and development for multi-tier service environments
US696855018 Ene 200222 Nov 2005International Business Machines CorporationApparatus and method for synchronizing software between computers
US696855117 Ago 200122 Nov 2005John HedigerSystem and user interface for generation and processing of software application installation instructions
US697106328 Jul 200029 Nov 2005Wireless Valley Communications Inc.System, method, and apparatus for portable design, deployment, test, and optimization of a communication network
US697107213 May 199929 Nov 2005International Business Machines CorporationReactive user interface control based on environmental sensing
US69736206 Sep 20016 Dic 2005International Business Machines CorporationMethod and apparatus for providing user support based on contextual information
US697362225 Sep 20006 Dic 2005Wireless Valley Communications, Inc.System and method for design, tracking, measurement, prediction and optimization of data communication networks
US697607929 Sep 200013 Dic 2005International Business Machines CorporationSystem and method for upgrading software in a distributed computer system
US697626929 Ago 200013 Dic 2005Equinix, Inc.Internet co-location facility security system
US697837926 May 200020 Dic 2005Hewlett-Packard Development Company, L.P.Configuring computer systems
US69833175 Jun 20003 Ene 2006Microsoft CorporationEnterprise management system
US69859562 Nov 200110 Ene 2006Sun Microsystems, Inc.Switching system
US69861356 Sep 200110 Ene 2006Cognos IncorporatedDeployment manager for organizing and deploying an application in a distributed computing environment
US698783816 Abr 200317 Ene 2006Entrisphere, Inc.System and method for deploying new equipment and services in conjunction with a legacy provisioning system
US699066625 Jul 200224 Ene 2006Surgient Inc.Near on-line server
US700356217 Sep 200121 Feb 2006Redseal Systems, Inc.Method and apparatus for network wide policy-based analysis of configurations of devices
US70035741 Nov 200021 Feb 2006Microsoft CorporationSession load balancing and use of VIP as source address for inter-cluster traffic through the use of a session identifier
US70129198 Dic 200014 Mar 2006Caspian Networks, Inc.Micro-flow label switching
US701346210 May 200114 Mar 2006Hewlett-Packard Development Company, L.P.Method to map an inventory management system to a configuration management system
US70169508 Dic 200421 Mar 2006Microsoft CorporationSystem and method for restricting data transfers and managing software components of distributed computers
US70244515 Nov 20014 Abr 2006Hewlett-Packard Development Company, L.P.System and method for maintaining consistent independent server-side state among collaborating servers
US702741218 May 200111 Abr 2006Veritas Operating CorporationSystem for dynamic provisioning of secure, scalable, and extensible networked computer environments
US702822828 Mar 200211 Abr 2006The Shoregroup, Inc.Method and apparatus for identifying problems in computer networks
US703203115 May 200118 Abr 2006Cloudshield Technologies, Inc.Edge adapter apparatus and method
US703578626 Oct 200125 Abr 2006Abu El Ata Nabil ASystem and method for multi-phase system development with predictive modeling
US703593026 Oct 200125 Abr 2006Hewlett-Packard Development Company, L.P.Method and framework for generating an optimized deployment of software applications in a distributed computing environment using layered model descriptions of services and servers
US70434077 Oct 19999 May 2006Trilogy Development Group, Inc.Method and apparatus for configuring systems
US70435458 Dic 20049 May 2006Microsoft CorporationSystem and method for restricting data transfers and managing software components of distributed computers
US704668028 Nov 200016 May 2006Mci, Inc.Network access system including a programmable access device having distributed service control
US70472795 May 200016 May 2006Accenture, LlpCreating collaborative application sharing
US705096121 Mar 200123 May 2006Unisys CorporationSolution generation method for thin client sizing tool
US705494328 Abr 200030 May 2006International Business Machines CorporationMethod and apparatus for dynamically adjusting resources assigned to plurality of customers, for meeting service level agreements (slas) with minimal resources, and allowing common pools of resources to be used across plural customers on a demand basis
US705514925 Jul 200130 May 2006Lenovo (Singapore) Pte Ltd.Method and apparatus for automating software upgrades
US705870430 Nov 19996 Jun 2006Network Appliance, Inc..Method and apparatus for implementing a service-level agreement
US70588264 Oct 20046 Jun 2006Amphus, Inc.System, architecture, and method for logical server and other network devices in a dynamically configurable multi-server network environment
US705885826 Oct 20016 Jun 2006Hewlett-Packard Development Company, L.P.Systems and methods for providing automated diagnostic services for a cluster computer system
US70627181 Abr 200213 Jun 2006National Instruments CorporationConfiguration diagram which graphically displays program relationship
US706920428 Sep 200027 Jun 2006Cadence Design System, Inc.Method and system for performance level modeling and simulation of electronic systems having both hardware and software elements
US706933712 Mar 200227 Jun 2006Mci, Inc.Policy-based synchronization of per-class resources between routers in a data network
US706948017 Ago 200427 Jun 2006The Shoregroup, Inc.Method and apparatus for identifying problems in computer networks
US70695533 Mar 200327 Jun 2006Computer Associates Think, Inc.Universal deployment tool
US707280726 Feb 20044 Jul 2006Microsoft CorporationArchitecture for distributed computing system and automated design, deployment, and management of distributed applications
US707282230 Sep 20024 Jul 2006Cognos IncorporatedDeploying multiple enterprise planning models across clusters of application servers
US707655223 May 200111 Jul 2006Sony International (Europe) GmbhUniversal QoS adaptation framework for mobile multimedia applications
US707663326 Oct 200111 Jul 2006Swsoft Holdings, Ltd.Hosting service providing platform system and method
US708014311 May 200418 Jul 2006Microsoft CorporationSystem and method providing automatic policy enforcement in a multi-computer service application
US70824646 Jul 200125 Jul 2006Juniper Networks, Inc.Network management system
US708928124 Ene 20028 Ago 2006Sun Microsystems, Inc.Load balancing in a dynamic session redirector
US70892932 Nov 20018 Ago 2006Sun Microsystems, Inc.Switching system method for discovering and accessing SCSI devices in response to query
US708953023 Nov 19998 Ago 2006Invensys Systems, Inc.Process control configuration system with connection validation and configuration
US709300522 May 200115 Ago 2006Terraspring, Inc.Graphical editor for defining and creating a computer system
US709328824 Oct 200015 Ago 2006Microsoft CorporationUsing packet filters and network virtualization to restrict network communications
US709625812 May 200422 Ago 2006Microsoft CorporationSystem and method providing automatic policy enforcement in a multi-computer service application
US709993629 Mar 200229 Ago 2006International Business Machines CorporationMulti-tier service level agreement method and system
US710318522 Dic 19995 Sep 2006Cisco Technology, Inc.Method and apparatus for distributing and updating private keys of multicast group managers using directory replication
US711390024 Oct 200026 Sep 2006Microsoft CorporationSystem and method for logical modeling of distributed computer systems
US711715825 Abr 20023 Oct 2006Bilcare, Inc.Systems, methods and computer program products for designing, deploying and managing interactive voice response (IVR) systems
US711726116 Ago 20023 Oct 2006Infrastructure Innovations, Llc.Auto control of network monitoring and simulation
US711726930 Abr 20023 Oct 2006Transtech Networks Usa, Inc.Packet switch with load surge-control and methods thereof
US71201542 Jul 200110 Oct 2006Marc BavantMethod for the routing of IP frames between the users of a variable graph network
US712079724 Abr 200210 Oct 2006Microsoft CorporationMethods for authenticating potential members invited to join a group
US712428931 Oct 200017 Oct 2006Opsware Inc.Automated provisioning framework for internet site servers
US71276254 Sep 200324 Oct 2006Hewlett-Packard Development Company, L.P.Application management based on power consumption
US713112330 Abr 200131 Oct 2006Opsware Inc.Automated provisioning of computing networks using a network database model
US713401118 May 20017 Nov 2006Huron Ip LlcApparatus, architecture, and method for integrated modular server system providing dynamically power-managed and work-load managed network devices
US713412231 May 20017 Nov 2006Oracle International CorporationOne click deployment
US713993025 Jul 200521 Nov 2006Dell Products L.P.Failover system and method for cluster environment
US713999931 Ago 199921 Nov 2006Accenture LlpDevelopment architecture framework
US714342029 Ago 200228 Nov 2006Sun Microsystems, Inc.Strategic technology architecture roadmap
US714635322 Jul 20035 Dic 2006Hewlett-Packard Development Company, L.P.Resource allocation for multiple applications
US71500154 Sep 200112 Dic 2006Pace Charles PMethod and system for deploying an asset over a multi-tiered network
US715210920 Abr 200119 Dic 2006Opsware, IncAutomated provisioning of computing networks according to customer accounts using a network database data model
US71521575 Mar 200319 Dic 2006Sun Microsystems, Inc.System and method for dynamic resource configuration using a dependency graph
US71553809 Dic 200426 Dic 2006Microsoft CorporationSystem and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US715549011 Oct 200026 Dic 2006Freewebs CorporationSystem and method for providing a web-based operating system
US716242720 Ago 19999 Ene 2007Electronic Data Systems CorporationStructure and method of modeling integrated business and information technology frameworks and architecture in support of a business
US716250930 Dic 20059 Ene 2007Microsoft CorporationArchitecture for distributed computing system and automated design, deployment, and management of distributed applications
US716263418 Abr 20019 Ene 2007Thomson LicensingMethod for providing security on a powerline-modem network
US71743793 Ago 20016 Feb 2007International Business Machines CorporationManaging server resources for hosted applications
US71817314 Sep 200120 Feb 2007Op40, Inc.Method, system, and structure for distributing and executing software and data on different network and computer devices, platforms, and environments
US718833515 Mar 20026 Mar 2007Trilogy Development Group, Inc.Product configuration using configuration patterns
US718836425 Ene 20026 Mar 2007Cranite Systems, Inc.Personal virtual bridged local area networks
US71913448 Ago 200213 Mar 2007Authenex, Inc.Method and system for controlling access to data stored on a data storage device
US719142927 Sep 200213 Mar 2007Manyeta Informatique Inc.System and method for managing architectural layers within a software model
US719443930 Abr 200120 Mar 2007International Business Machines CorporationMethod and system for correlating job accounting information with software license information
US719461625 Oct 200220 Mar 2007International Business Machines CorporationFlexible temporary capacity upgrade/downgrade in a computer system without involvement of the operating system
US71974189 Sep 200527 Mar 2007National Instruments CorporationOnline specification of a system which compares determined devices and installed devices
US720053029 Dic 20053 Abr 2007Microsoft CorporationArchitecture for distributed computing system and automated design, deployment, and management of distributed applications
US720066517 Oct 20013 Abr 2007Hewlett-Packard Development Company, L.P.Allowing requests of a session to be serviced by different servers in a multi-server data service system
US720391113 May 200210 Abr 2007Microsoft CorporationAltering a display on a viewing device based upon a user proximity to the viewing device
US72101434 Mar 200324 Abr 2007International Business Machines CorporationDeployment of applications in a multitier compute infrastructure
US721323111 Ene 20021 May 2007Cisco Technology, Inc.Cross-spectrum application model for dynamic computing environments in software lifecycle
US722214711 Ago 200022 May 2007Ciena CorporationProcessing network management data in accordance with metadata files
US722544127 Dic 200029 May 2007Intel CorporationMechanism for providing power management through virtualization
US723141010 Mar 200412 Jun 2007Qlogic, CorporationRevision control system for large-scale systems management
US72314304 Ene 200212 Jun 2007Egenera, Inc.Reconfigurable, virtual processing system, cluster, network and method
US723726716 Oct 200326 Jun 2007Cisco Technology, Inc.Policy-based network security management
US725463410 Mar 20037 Ago 2007Akamai Technologies, Inc.Managing web tier session state objects in a content delivery network (CDN)
US725758413 May 200414 Ago 2007Surgient, Inc.Server file management
US725781727 Nov 200114 Ago 2007Microsoft CorporationVirtual network with adaptive dispatcher
US727265326 Sep 200118 Sep 2007International Business Machines CorporationSystem and method for implementing a clustered load balancer
US72751565 Sep 200325 Sep 2007Xerox CorporationMethod and apparatus for establishing and using a secure credential infrastructure
US727827330 Dic 20039 Oct 2007Google Inc.Modular data center
US728115425 Jul 20059 Oct 2007Dell Products L.P.Failover system and method for cluster environment
US730260831 Mar 200427 Nov 2007Google Inc.Systems and methods for automatic repair and replacement of networked machines
US730554925 May 20044 Dic 2007Microsoft CorporationFilters to isolate untrusted ports of switches
US73055565 Dic 20014 Dic 2007Canon Kabushiki KaishaSecure printing with authenticated printer key
US730556125 May 20044 Dic 2007Microsoft CorporationEstablishing computing trust with a staging area
US73094989 Oct 200218 Dic 2007Belenkaya Bronislava GBiodegradable absorbents and methods of preparation
US731357317 Sep 200325 Dic 2007International Business Machines CorporationDiagnosis of equipment failures using an integrated approach of case based reasoning and reliability analysis
US73136142 Nov 200125 Dic 2007Sun Microsystems, Inc.Switching system
US731580114 Ene 20001 Ene 2008Secure Computing CorporationNetwork security modeling system and method
US731821617 Jun 20048 Ene 2008Tablecode Software CorporationSoftware application development environment facilitating development of a software application
US733300012 Nov 200419 Feb 2008Afco Systems Development, Inc.Tracking system and method for electrically powered equipment
US73436017 Feb 200511 Mar 2008International Business Machines CorporationEfficient application deployment on dynamic clusters
US734989111 Oct 200525 Mar 2008International Business Machines CorporationSite integration management system for operational support service in an internet data center
US735006822 Abr 200525 Mar 2008International Business Machines CorporationServer blade network boot method that minimizes required network bandwidth
US735018610 Mar 200325 Mar 2008International Business Machines CorporationMethods and apparatus for managing computing deployment in presence of variable workload
US7356679 *1 Oct 20048 Abr 2008Vmware, Inc.Computer image capture, customization and deployment
US736675528 Jul 200029 Abr 2008International Business Machines CorporationMethod and apparatus for affinity of users to application servers
US73670281 Abr 200229 Abr 2008National Instruments CorporationGraphically deploying programs on devices in a system
US737010312 Nov 20046 May 2008Hunt Galen CSystem and method for distributed management of shared computers
US73703235 Mar 20026 May 2008International Business Machines CorporationMethod and system for managing configuration changes in a data processing system
US73761254 Jun 200220 May 2008Fortinet, Inc.Service processing switch
US737998228 Mar 200327 May 2008Bassam TabbaraSystem and method for custom installation of an operating system on a remote client
US738332913 Feb 20013 Jun 2008Aventail, LlcDistributed cache for state transfer operations
US738672112 Mar 200310 Jun 2008Cisco Technology, Inc.Method and apparatus for integrated provisioning of a network device with configuration information and identity certification
US73953201 Jun 20051 Jul 2008Microsoft CorporationProviding automatic policy enforcement in a multi-computer service application
US740390113 Abr 200022 Jul 2008Accenture LlpError and load summary reporting in a health care solution environment
US740417511 Oct 200122 Jul 2008Bea Systems, Inc.Smart generator
US74065171 Nov 200429 Jul 2008Microsoft CorporationSystem and method for distributed management of shared computers
US740669224 Feb 200429 Jul 2008Bea Systems, Inc.System and method for server load balancing and server affinity
US740942031 Oct 20015 Ago 2008Bea Systems, Inc.Method and apparatus for session replication and failover
US741250218 Abr 200212 Ago 2008International Business Machines CorporationGraphics for end to end component mapping and problem-solving in a network environment
US741572918 Jun 200319 Ago 2008Hitachi, Ltd.Storage device
US74215051 Jun 20012 Sep 2008Noatak Software LlcMethod and system for executing protocol stack instructions to form a packet for causing a computing device to perform an operation
US743696519 Feb 200314 Oct 2008Microsoft CorporationOptical out-of-band key distribution
US74480793 Jul 20014 Nov 2008Ernst & Young, LlpMethod and apparatus for providing computer services
US746124911 Ago 20002 Dic 2008Hewlett-Packard Development Company, L.P.Computer platforms and their methods of operation
US746414710 Nov 20009 Dic 2008International Business Machines CorporationManaging a cluster of networked resources and resource groups using rule - base constraints in a scalable clustering environment
US747838115 Dic 200313 Ene 2009Microsoft CorporationManaging software updates and a software distribution service
US747838513 Jun 200313 Ene 2009National Instruments CorporationInstalling software using programmatic component dependency analysis
US74809079 Ene 200420 Ene 2009Hewlett-Packard Development Company, L.P.Mobile services network for update of firmware/software in mobile handsets
US749691124 Jun 200224 Feb 2009Invensys Systems, Inc.Installing supervisory process control and manufacturing software from a remote location and maintaining configuration data links in a run-time environment
US750006917 Sep 20013 Mar 2009Hewlett-Packard Development Company, L.P.System and method for providing secure access to network logical storage partitions
US750587211 Sep 200217 Mar 2009International Business Machines CorporationMethods and apparatus for impact analysis and problem determination
US750603429 Dic 200017 Mar 2009Intel CorporationMethods and apparatus for off loading content servers through direct file transfer from a storage center to an end-user
US751294224 Ago 200531 Mar 2009International Business Machines CorporationModel-driven software deployment in an application server
US754306630 Abr 20012 Jun 2009International Business Machines CorporationMethod and apparatus for maintaining session affinity across multiple server groups
US75675048 Sep 200328 Jul 2009Microsoft CorporationNetwork load balancing with traffic routing
US75743437 Mar 200611 Ago 2009Microsoft CorporationSystem and method for logical modeling of distributed computer systems
US759073630 Jun 200315 Sep 2009Microsoft CorporationFlexible network load balancing
US75942248 Oct 200422 Sep 2009Bea Systems, Inc.Distributed enterprise security system
US760344220 Jun 200313 Oct 2009Microsoft CorporationMethod and system for maintaining service dependency relationships in a computer system
US76069298 Sep 200320 Oct 2009Microsoft CorporationNetwork load balancing with connection manipulation
US761382230 Jun 20033 Nov 2009Microsoft CorporationNetwork load balancing with session information
US76240862 Mar 200624 Nov 2009Maxsp CorporationPre-install compliance system
US763087729 Dic 20058 Dic 2009Microsoft CorporationArchitecture for distributed computing system and automated design, deployment, and management of distributed applications
US763691730 Jun 200322 Dic 2009Microsoft CorporationNetwork load balancing with host status information
US765318720 Oct 200626 Ene 2010At&T Services, Inc.Method and system for presenting billing information according to a customer-defined hierarchal structure
US766923525 May 200423 Feb 2010Microsoft CorporationSecure domain join for computing devices
US768967612 Ene 200730 Mar 2010Microsoft CorporationModel-based policy application
US2001001415828 Mar 200116 Ago 2001Hush Communications CorporationPublic key cryptosystem with roaming user capability
US2001002022822 Mar 20016 Sep 2001International Business Machines CorporationUmethod, system and program for managing relationships among entities to exchange encryption keys for use in providing access and authorization to resources
US2002002295226 Mar 199821 Feb 2002David ZagerDynamic modeling of complex networks and prediction of impacts of faults therein
US2002004957328 Ago 200125 Abr 2002El Ata Nabil A. AbuAutomated system and method for designing model based architectures of information systems
US200200692671 Nov 20016 Jun 2002Karl ThieleData management framework for policy management
US2002007584410 Abr 200120 Jun 2002Hagen W. AlexanderIntegrating public and private network resources for optimized broadband wireless access and method
US2002008282023 Ene 200127 Jun 2002Glenn FergusonData model for automated server configuration
US200200872644 Ene 20014 Jul 2002Hills Alexander A.Position location system and method
US200200900895 Ene 200111 Jul 2002Steven BraniganMethods and apparatus for secure wireless networking
US2002013160119 Oct 200119 Sep 2002Toshihiko NinomiyaCryptographic key management method
US20020147862 *30 Jul 200110 Oct 2002Traut Eric P.Method for establishing a drive image in a computing environment
US2002015208615 Feb 200117 Oct 2002Smith Ned M.Method and apparatus for controlling a lifecycle of an electronic contract
US2002015690029 Mar 200224 Oct 2002Brian MarquetteProtocol independent control module
US2002017169015 May 200121 Nov 2002International Business Machines CorporationMethod and system for scaling a graphical user interface (GUI) widget based on selection pointer proximity
US2002018432711 May 20015 Dic 2002Major Robert DrewSystem and method for partitioning address space in a proxy cache server cluster
US2002018894112 Jun 200112 Dic 2002International Business Machines CorporationEfficient installation of software packages
US2002019899510 Abr 200126 Dic 2002International Business Machines CorporationApparatus and methods for maximizing service-level-agreement profits
US200300087124 Jun 20029 Ene 2003Playnet, Inc.System and method for distributing a multi-client game/application over a communications network
US200300095598 Jul 20029 Ene 2003Naoya IkedaNetwork system and method of distributing accesses to a plurality of server apparatus in the network system
US200300146442 May 200216 Ene 2003Burns James E.Method and system for security policy management
US2003004114227 Ago 200127 Feb 2003Nec Usa, Inc.Generic network monitoring tool
US2003004115917 Ago 200127 Feb 2003David TinsleySystems and method for presenting customizable multimedia presentations
US2003004661522 Dic 20006 Mar 2003Alan StoneSystem and method for adaptive reliability balancing in distributed programming networks
US2003005104913 Ago 200213 Mar 2003Ariel NoyNetwork provisioning in a distributed network management architecture
US2003006574328 Sep 20013 Abr 2003Jenny Patrick DuncanMethod and system for distributing requests for content
US200301264644 Dic 20013 Jul 2003Mcdaniel Patrick D.Method and system for determining and enforcing security policy in a communication session
US2003013810518 Ene 200224 Jul 2003International Business Machines CorporationStoring keys in a cryptology device
US2003021490817 Mar 200320 Nov 2003Anurag KumarMethods and apparatus for quality of service control for TCP aggregates at a bottleneck link in the internet
US2003021726321 Mar 200220 Nov 2003Tsutomu SakaiSystem and method for secure real-time digital transmission
US2003022556330 May 20024 Dic 2003Gonos Dan G.Capacity planning
US2004000287828 Jun 20021 Ene 2004International Business Machines CorporationMethod and system for user-determined authentication in a federated environment
US2004005981214 Dic 200125 Mar 2004Shmuel AssaTopology information system for a managed world
US2004007344310 Jun 200315 Abr 2004Gabrick John J.System for automating and managing an IP environment
US2004007379510 Oct 200215 Abr 2004Jablon David P.Systems and methods for password-based connection
US2004007878717 Jul 200322 Abr 2004Michael BorekSystem and method for troubleshooting, maintaining and repairing network devices
US2004011131516 Oct 200310 Jun 2004Xerox CorporationDevice model agent
US2004011747617 Dic 200217 Jun 2004Doug SteeleMethod and system for performing load balancing across control planes in a data center
US200401603861 Dic 200319 Ago 2004Georg MichelitschMethod for operating a display device
US200401933881 Mar 200430 Sep 2004Geoffrey OuthredDesign time validation of systems
US2004019957224 Oct 20037 Oct 2004Hunt Galen C.Architecture for distributed computing system and automated design, deployment, and management of distributed applications
US2004020517924 Oct 200314 Oct 2004Hunt Galen C.Integrating design, deployment, and management phases for systems
US2004022601017 Feb 200411 Nov 2004Loudcloud, Inc.Automated provisioning framework for internet site servers
US2005000800113 Feb 200413 Ene 2005John Leslie WilliamsSystem and method for interfacing with heterogeneous network data gathering tools
US2005002174231 Mar 200427 Ene 2005System Management Arts, Inc.Method and apparatus for multi-realm system modeling
US2005008081117 Ago 200414 Abr 2005Cendura CorporationConfiguration management architecture
US200500910782 Nov 200428 Abr 2005Microsoft CorporationSystem and method for distributed management of shared computers
US2005009122723 Oct 200328 Abr 2005Mccollum Raymond W.Model-based management of computer systems and distributed applications
US20050097082 *30 Oct 20035 May 2005International Business Machines CorporationSelection of optimal execution environment for software applications
US2005009709712 Nov 20045 May 2005Microsoft CorporationSystem and method for distributed management of shared computers
US2005009714623 Ago 20045 May 2005Konstantinou Alexander V.Methods and systems for autonomously managing a network
US2005010215412 Nov 200312 May 2005Dodd Ryan A.Method, computer useable medium, and system for enterprise resource management
US200501023888 Dic 200412 May 2005Microsoft CorporationSystem and method for restricting data transfers and managing software components of distributed computers
US2005010251310 Nov 200312 May 2005Nokia CorporationEnforcing authorized domains with domain membership vouchers
US200501025389 Dic 200412 May 2005Microsoft CorporationSystem and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US200501252129 Dic 20049 Jun 2005Microsoft CorporationSystem and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US2005013841619 Dic 200323 Jun 2005Microsoft CorporationObject model for managing firewall services
US2005015227012 Abr 200214 Jul 2005Gerardo Gomez ParedesPolicy-based qos management in multi-radio access networks
US2005019297122 Abr 20051 Sep 2005Microsoft CorporationSystem and method for restricting data transfers and managing software components of distributed computers
US200501931038 Oct 20031 Sep 2005John DrabikMethod and apparatus for automatic configuration and management of a virtual private network
US2005024652930 Abr 20043 Nov 2005Microsoft CorporationIsolated persistent identity storage for authentication of computing devies
US2005025178325 Mar 200410 Nov 2005Microsoft CorporationSettings and constraints validation to enable design for operations
US2005025724413 May 200417 Nov 2005Hewlett-Packard Development Company, L.P.Method and apparatus for role-based security policy management
US2005026832527 May 20041 Dic 2005Harumi KunoMethod and system for integrating policies across systems
US200600259842 Dic 20042 Feb 2006Microsoft CorporationAutomatic validation and calibration of transaction-based performance models
US2006002598529 Jun 20052 Feb 2006Microsoft CorporationModel-Based system management
US2006003124810 Mar 20059 Feb 2006Microsoft CorporationModel-based system provisioning
US200600342638 Sep 200516 Feb 2006Microsoft CorporationModel and system state synchronization
US20060037002 *29 Jun 200516 Feb 2006Microsoft CorporationModel-based provisioning of test environments
US2006004801730 Ago 20042 Mar 2006International Business Machines CorporationTechniques for health monitoring and control of application servers
US200601230403 Dic 20048 Jun 2006International Business Machines CorporationAlgorithm for automated enterprise deployments
US2006015570813 Ene 200513 Jul 2006Microsoft CorporationSystem and method for generating virtual networks
US2006016187918 Ene 200520 Jul 2006Microsoft CorporationMethods for managing standards
US2006016188418 Ene 200520 Jul 2006Microsoft CorporationMethods for managing capacity
US2006023292715 Abr 200519 Oct 2006Microsoft CorporationModel-based system monitoring
US2006023566415 Abr 200519 Oct 2006Microsoft CorporationModel-based capacity planning
US2006025960917 Jul 200616 Nov 2006Microsoft CorporationSystem and Method for Distributed Management of Shared Computers
US2006025961017 Jul 200616 Nov 2006Microsoft CorporationSystem and Method for Distributed Management of Shared Computers
US2007000617710 May 20054 Ene 2007International Business Machines CorporationAutomatic generation of hybrid performance models
US200701128472 Nov 200517 May 2007Microsoft CorporationModeling IT operations/policies
US2007019276918 Abr 200716 Ago 2007Fujitsu LimitedProgram, method, and apparatus for managing applications
US2008005921412 Ene 20076 Mar 2008Microsoft CorporationModel-Based Policy Application
CN1368694A1 Feb 200111 Sep 2002安德华科技股份有限公司Method and system for dynamically discriminating job entity
CN1375685A13 Mar 200223 Oct 2002松下电器产业株式会社信息终端装置及地图信息提供系统
EP0964546A325 May 19993 Sep 2003Hitachi, Ltd.Network management system
EP1180886B117 Ago 200011 Oct 2006Sun Microsystems, Inc.Load balancing method and system
EP1307018B124 Oct 200111 Oct 2006Sun Microsystems, Inc.Load balancing unit and method of its operation
EP1550969A311 Nov 200431 Ago 2005International Business Machines CorporationMethod and system for dynamically and automatically set-up offerings for IT-services
JP6250956A Título no disponible
JP8297567A Título no disponible
JP10124343A Título no disponible
JP10150470A Título no disponible
JP10240576A Título no disponible
JP10285216A Título no disponible
JP11007407A Título no disponible
JP11340980A Título no disponible
JP2000293497A Título no disponible
JP2001339437A Título no disponible
JP2001526814A Título no disponible
JP2002084302A Título no disponible
JP2002354006A Título no disponible
JP2003030424A Título no disponible
JP2003532784T5 Título no disponible
JP2005155729A Título no disponible
RU2111625C1 Título no disponible
RU2156546C2 Título no disponible
RU2189072C2 Título no disponible
Otras citas
Referencia
1"C.O.B.A.S. Centralized Out-Of-Band Authentication System," QT Wordtel Inc., Southeast Europe Cybersecurity Conference, Sophia, Bulgaria, Sep. 8-9, 2003.
2"Enhanced IP Services for Cisco Networks," retrieved on Jun. 19, 2007, at <<http://proquest.safaribooksonline.com/1578701066>>, Sep. 23, 1999, 11 pages.
3"Enhanced IP Services for Cisco Networks," retrieved on Jun. 19, 2007, at >, Sep. 23, 1999, 11 pages.
4"Integrated Security Management", OpenPMF (Policy Management Framework), retrieved as early as Apr. 23, 2007 from <<http://www.objectsecurity.com/doc/openpmf-A4.pdf>>, 2 pages.
5"Integrated Security Management", OpenPMF (Policy Management Framework), retrieved as early as Apr. 23, 2007 from >, 2 pages.
6"Pretty Good Privacy PGP for Personal Privacy, Version 5.0 for Windows 95 Windows NT", Pretty Good Privacy Inc., 1997, 137.
7"Remote Operating System Installation," retrieved on Feb. 13, 2009 at <<http://technet.microsoft.com/en-us/library/bb742501.aspx>>, Microsoft TechNet, Sep. 9, 1999, 1-28.
8"Remote Operating System Installation," retrieved on Feb. 13, 2009 at >, Microsoft TechNet, Sep. 9, 1999, 1-28.
9"The Age Changed by Information Network and System: The Internet Releasing Enterprises and Society A? The New Century created by an E Service and a Terabit Network Service: Disappearance of Enterprise Servers, Service Components Behind the Internet," Nikkei Internet Technology, Japan, Nikkei Business Publications, Inc., Dec. 22, 1999, No. 30, 76-81.
10Araki, "Linux Security Diary, Use VLAN in Linux," Linux Japan, Itsutsubashi Research Co., Ltd., Nov. 1, 2008, 3(11), 110-113, (CSDB: National Academy Paper 200300158009).
11Barrett et al., "Model driven distribution pattern design for dynamic web services compositions," ACM ICWE, 2006, 129-136.
12Cardelli, L., "Type Systems," CRC Handbook of Computer Science and Engineering, 2nd Edition, Ch. 97, Wednesday, Feb. 25, 2004, 8:00pm CRC Press, http://research.microsoft.com/Users.Iuca/Papers/TypeSystems.pdf.
13Chen, et al., "Performance Prediction of Component-based Application", Journal of Systems and Software, vol. 74, Issue 1, Jan. 2005, pp. 1-12.
14Chen, et al., "Performance Prediction of Component-based Applications", Journal of Systems and Software, vol. 74 , Issue 1, Jan. 2005, pp. 1-12.
15China Office Action from corresponding Chinese Patent Application No. 200410088250.0 dated Apr. 27, 2007, 3 pages.
16Chunxiao et al., "Configure and Move the e-Commerce Business Model by Utilizing XML," Applications of Computer Systems, Feb. 28, 2002, No. 2, 8-11.
17Chunxiao et al., "Using XML Schema to Configure Mobile E-Commerce Transaction Model," Applications of Computer Systems, Feb. 28, 2002, No. 2, 9 pages.
18Chunxiao, et al., Configure and move the e-Commerce Business Model by Utilizing XML, Applications of Computer Systems, No. 2, p. 8-11.
19Dekhil, et al., "Generalized Policy Model for Application and Service Management", Hewlett-Packard Laboratories, 1999, 3 pages.
20Dolstra et al., "Imposing a memory management discipline on software deployment," IEEE ICSE, 2004, 1-10.
21EPO Communication with Search Report dated Sep. 1, 2006, from counterpart EP Patent Application No. 04005431.4, 3 pages.
22Frolund et al., "Design-Time Simulation of a Large-Scale, Distributed Object System" ACM, Oct. 1998, 8(4), 374-400.
23Garschhammer, et al., "Towards Generic Service Management Concepts a Service Model Based Approach", IEEE/IFIP International Symposium, Integrated Network Management Proceedings, 2001,14 pages.
24Harbour, et al., "MAST: An Open Environment for Modeling, Analysis, and Design of Real-Time Systems", 2001, pp. 1-16.
25Hardwick, et al., "Modeling the Performance of E-Commerce Site", Journal of Computer Resource Management, 2002, 11 pages.
26Heilala et al., "Modeling and simulation for customer driven manufacturing system design and operation planning", IEEE, 2007, 1853-1862.
27Heinl et al., "A Comprehensive Approach to Flexibility in Workflow Management Systems," WACC '99, ACM, Feb. 1999, 79-88.
28Howard et al., "Designing Secure Web-Based Applications for Microsoft Windows 2000", 2000.
29 *IBM, "IBM Tivoli Workload Scheduler-Planning and Installation Guide", 2004, IBM, version 8.2, pp. i-xviii, 1-171.
30 *IBM, "IBM Tivoli Workload Scheduler—Planning and Installation Guide", 2004, IBM, version 8.2, pp. i-xviii, 1-171.
31Iwasaki, H., "IP Troubles Q&A-The Prevention of Network Troubles and the Risk Management," Computer & Network LAN, Japan Ohmsha, Ltd., Jul. 14, 2000, 18(8), 29-39.
32Iwasaki, H., "IP Troubles Q&A—The Prevention of Network Troubles and the Risk Management," Computer & Network LAN, Japan Ohmsha, Ltd., Jul. 14, 2000, 18(8), 29-39.
33Kitjongthawonkul, S. et al., "Modeling Information Systems Using Objects, Agents, and Task-Based Problem Solving Adapters," Proc. 10th Australasian Conference on Information Systems, 1999, http://www.vuw.ac.nz/acis99/Papers/PaperKitjongthawonkul-077.pdf.
34Kounev, "A Capacity Planning Methodology for Distributed E-Commerce Applications", Jan. 2, 2001, pp. 1-13.
35Lee et al., "Community Services: A Toolkit for Rapid Deployment of Network Services," Proceedings of the IEEE International Conference on Cluster Computing, IEEE, 2002, 4 pages.
36Levillain et al., "Switch-Based Server Load Balancing for Enterprises," Alcatel Telecommunications Review, 2002, No. 4, 298-302.
37 *Lin et al., "User-driven Scheduling of Interactive Virtual Machines", Oct. 2004, IEEE, 8 pages.
38Liu et al., "Visualization in Network Topology Optimization", ACM, 1992, 50-56.
39Mahon, "OpenView PolicyXpert: Heterogeneous Configuration and Control", OpenView Policy-Based Network Management, Feb. 1999, pp. 1-4.
40Meader, P., "Build Distributed Apps a New Way," VSLive!ShowDaily, San Francisco, Mar. 25, 2004, http://www.ftponline.com/reports/vslivesf/2004/whitehorse2/.
41Meader, P., "Model Apps More Effectively," VSLive!ShowDaily, San Francisco, Mar. 24, 2004, http://www.ftponline.com/reports/vslivesf/2004/whitehorse/.
42Meli, "Measuring Change Requests to Support Effective Project Management Practices," Proc. of the ESCOM 2001, London, Apr. 2001, 25-34.
43Menezes et al., "Handbook of Applied Cryptography," CRC Press, 1996, Chs. 8 & 12, 283-319 and 489-541.
44Microsoft.com, "System Definition Model," retrieved at <<http://web.archive.org/web/20040405230803/www.microsoft.com/windowsserversystem/dsi/sdm.mspx>>, Published Dec. 15, 2003 and updated Mar. 31, 2004, 4 pages.
45Microsoft.com, "System Definition Model," retrieved at >, Published Dec. 15, 2003 and updated Mar. 31, 2004, 4 pages.
46Miyamoto, et al., "VLAN Management System of Large-scale Network," Journal of Information Processing Society of Japan, Dec. 15, 2000, 41(12), 3234-3244 (CSDB: National Academy Paper 200200108005).
47Morimoto et al., "Compatability Testing for Windows Server 2003", Microsoft Windows Server 2003 Unleashed, Chapter 18, Section 1, Jun. 14, 2004, 2 pages.
48Nerurkar, "Security Analysis and Design", Dr. Dobb's Journal, Nov. 2000, 50-56.
49Nestor, "Security Modeling Using Hierarchical State Machines", IEEE, 1991, 110-119.
50Norton, "Simalytic Hybrid Modeling Planning the Capacity of Client/Server Applications", Colorado Technical University, Aug. 24-29, 1997, pp. 1-7.
51Office Action from the Patent Office of the State Intellectual Property Office of the People's Republic of China, Application No. 200410033027.7, mailed Feb. 2, 2007, 23 pages.
52PCT International Search Report and Written Opinion for PCT Application No. PCT/US2006/038856, mailed Feb. 20, 2007, 9 pages.
53 *Sapuntzakis et al., "Optimizing the Migration of Virtual Computers", 2002, USENIX Association, pp. 377-390.
54Selic, "A Generic Framework for Modeling Resources with UML", IEEE, vol. 33, Issue 6, Jun. 2000, pp. 64-69.
55Shi et al., "An Effective Model for Composition of Secure Systems", J. of Systems and Software, 1998, 233-244.
56Somers, "Hybrid: Unifying Centralised and Distributed Network Management using Intelligent Agents" IEEE Network Operations and Management Symposium, Kyoto, Apr. 15-19, 1996, 34-43.
57Sultan et al., "Migratory TCP: Connection Migration for Service Continuity in the Internet" Proceedings 22nd Intl. Conference on Distributed Computing Systems; Jul. 2002, 469-470.
58Tofts, C., "HOLOS-A Stimulation and Multi Mathematical Modelling Tool," Hewlett-Packard Company, 2001, http://www.hpf.hp.com/techreports/2001/HPL-2001-276.pdf.
59Tofts, C., "HOLOS—A Stimulation and Multi Mathematical Modelling Tool," Hewlett-Packard Company, 2001, http://www.hpf.hp.com/techreports/2001/HPL-2001-276.pdf.
60Translated the Japanese Office Action for Japanese Patent Application No. 2004-061396, mailed on Jun. 24, 2008, 27 pages.
61Translated the Japanese Office Action mailed Dec. 14, 2007 for the Japanese Patent Application No. 2001-326848, a counterpart foreign application of US Patent No. 6,886,038.
62Translated the Japanese Office Action mailed Jan. 26, 2007 for the Japanese Patent Application No. 2001-326848, a counterpart foreign application of US Patent No. 6,886,038.
63U.S. Appl. No. 11/427,041, filed Jun. 28, 2006, Vinberg et al.
64W3C: "Resource Description Framework (RDF), Concepts and Abstract Syntax", http://www.w3.org/TR2004/REC-rdf-concepts-20040210, Feb. 10, 2004, XP002570908.
65Wang, W-C, "How a SCVP client authenticates the SCVP server", Online! Sep. 12, 2003, Retrieved from the Internet: URL: http://www.imc.org/ietf-pkix/old-archive-03/msg01323.html].
66Yamasaki et al., "Model based resources selection for efficient virtual cluster deployment," ACM VTDC, 2007, 1-7.
67Yuhui, "e-Commerce Based on ERP for Enterprize by Utilizing DNA and XML," Computer Engineering, Jun. 2001, 27(6), 165, 166, 182.
68Yuhui, e-Commerce Based on ERP for Enterprize by Utilizing DNA and XML, Computer Engineering, vol. 27, No. 6, p. 165,166,182.
Citada por
Patente citante Fecha de presentación Fecha de publicación Solicitante Título
US8667482 *10 Ago 20074 Mar 2014Microsoft CorporationAutomated application modeling for application virtualization
US8863113 *6 Nov 201214 Oct 2014Parallels IP Holdings GmbHMethod and system for unattended installation of guest operating system
US8943203 *10 Jul 200927 Ene 2015Netapp, Inc.System and method for storage and deployment of virtual machines in a virtual server environment
US9070086 *12 May 200830 Jun 2015Microsoft Technology Licensing, LlcData driven component reputation
US9183121 *19 Jul 201310 Nov 2015Cisco Technology, Inc.Network development and testing as a cloud service
US92803361 May 20128 Mar 2016International Business Machines CorporationVirtual machine disk image installation
US931727030 Sep 201319 Abr 2016Microsoft Technology Licensing, LlcModel-based virtual system provisioning
US9535684 *25 Nov 20143 Ene 2017Vmware, Inc.Management of software updates in a virtualized environment of a datacenter using dependency relationships
US956346926 Ene 20157 Feb 2017Netapp, Inc.System and method for storage and deployment of virtual machines in a virtual server environment
US97059232 Sep 201411 Jul 2017Symantec CorporationMethod and apparatus for automating security provisioning of workloads
US20090044170 *10 Ago 200712 Feb 2009Microsoft CorporationAutomated Application Modeling for Application Virtualization
US20090281819 *12 May 200812 Nov 2009Microsoft CorporationData driven component reputation
US20130212282 *17 Dic 201215 Ago 2013Desktone, Inc.Virtual Computing Services Deployment Network
US20130290951 *1 Jul 201331 Oct 2013Matthew L. DomschVirtual Machine Manufacturing Methods and Media
US20140143011 *16 Nov 201222 May 2014Dell Products L.P.System and method for application-migration assessment
US20150026667 *19 Jul 201322 Ene 2015Cisco Technology, Inc.Network Development and Testing as a Cloud Service
US20160077862 *17 Sep 201517 Mar 2016Microsoft Technology Licensing, LlcModel-based virtual system provisioning
Clasificaciones
Clasificación de EE.UU.717/174, 717/104
Clasificación internacionalG06F9/445
Clasificación cooperativaG06F2009/4557, G06F8/61, G06F9/45558
Eventos legales
FechaCódigoEventoDescripción
20 Oct 2005ASAssignment
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VINBERG, ANDERS B.;FRIES, ROBERT M.;GREALISH, KEVIN;AND OTHERS;REEL/FRAME:016918/0548;SIGNING DATES FROM 20050805 TO 20051018
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VINBERG, ANDERS B.;FRIES, ROBERT M.;GREALISH, KEVIN;AND OTHERS;REEL/FRAME:016918/0573;SIGNING DATES FROM 20021012 TO 20051018
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VINBERG, ANDERS B.;FRIES, ROBERT M.;GREALISH, KEVIN;AND OTHERS;SIGNING DATES FROM 20021012 TO 20051018;REEL/FRAME:016918/0573
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VINBERG, ANDERS B.;FRIES, ROBERT M.;GREALISH, KEVIN;AND OTHERS;SIGNING DATES FROM 20050805 TO 20051018;REEL/FRAME:016918/0548
9 Dic 2014ASAssignment
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034543/0001
Effective date: 20141014
16 Mar 2017FPAYFee payment
Year of fee payment: 4