Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: Provided are techniques for grouping resources based upon ownership in a cloud environment into a collection representing a composite application corresponding to a particular user; automatically monitoring the resources across two or more virtual machines and two or more physical computing devices; and displaying the monitored resources in a graphical user interface (GUI) in a context associated with the composite application for managing the composite application and the resources, wherein the resources are provided as one or more of a platform as service (PaaS) environment and an infrastructure as Service (IaaS) environment.

Abstract: Provided are techniques for grouping resources based upon ownership in a cloud environment into a collection representing a composite application corresponding to a particular user; automatically monitoring the resources across two or more virtual machines and two or more physical computing devices; and displaying the monitored resources in a graphical user interface (GUI) in a context associated with the composite application for managing the composite application and the resources, wherein the resources are provided as one or more of a platform as service (PaaS) environment and an infrastructure as Service (IaaS) environment.

Abstract: Components are dynamically associated in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. This includes defining, in a memory of a host computing system, a pattern that has an inventory of components of a multi-tier application. Each of the components are associated with a corresponding tier label for an n-tier architecture and the pattern is loaded into a pattern engine. The pattern engine deploys each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: A method, system and computer program product for deploying a pattern. A placement engine of a hierarchical tier selects the region(s) of a next lower tier based on placement policies and constraints at the next lower tier and availability of the artifacts required by the virtual machine instance(s) in the next lower tier utilizing the summarization of resource usage and availability at the next lower tier. The placement engine at the lowest tier selects the compute node(s) in the selected region(s) of the lowest tier to place the virtual machine instances of the pattern based on placement policies and constraints at the compute node level and availability of the artifacts required by the virtual machine instance(s) of the pattern in the compute node level. In this manner, the virtual machine instances of the pattern can be effectively deployed when the resources of the cloud environment are large and geographically dispersed.

Abstract: A cloud deployment appliance (or other platform-as-a-service (IPAS) infrastructure software) includes a mechanism to deploy a product as a “shared service” to the cloud, as well as to enable the product to establish a trust relationship between itself and the appliance or IPAS. The mechanism further enables multiple products deployed to the cloud to form trust relationships with each other (despite the fact that each deployment and each product typically, by the nature of the cloud deployment, are intended to be isolated from one another). In addition, once deployed and provisioned into the cloud, a shared service can become part of a single sign-on (SSO) domain automatically. SSO is facilitated using a token-based exchange. Once a product registers with a token service, it can participate in SSO. This approach enables enforcement of consistent access control policy across product boundaries, and without requiring a user to perform any configuration.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: Embodiments of the present invention provide a method, system and computer program product for the dynamic association of components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure. In an embodiment of the invention, a method for dynamically associating components in a multi-tier application to different layers of a corresponding multi-tier application infrastructure includes defining in memory of a host computing system a pattern that has an inventory of components of a multi-tier application. The method also includes associating each of the components with a corresponding tier label for an n-tier architecture. The method yet further includes loading the pattern into a pattern engine. Finally, the method includes deploying by the pattern engine each component of the pattern to a layer of the n-tier architecture corresponding to a tier label associated with the component.

Abstract: A method, system and computer program product for deploying a pattern. A placement engine of a hierarchical tier selects the region(s) of a next lower tier based on placement policies and constraints at the next lower tier and availability of the artifacts required by the virtual machine instance(s) in the next lower tier utilizing the summarization of resource usage and availability at the next lower tier. The placement engine at the lowest tier selects the compute node(s) in the selected region(s) of the lowest tier to place the virtual machine instances of the pattern based on placement policies and constraints at the compute node level and availability of the artifacts required by the virtual machine instance(s) of the pattern in the compute node level. In this manner, the virtual machine instances of the pattern can be effectively deployed when the resources of the cloud environment are large and geographically dispersed.

Abstract: A method, system and computer program product for sharing resources among remote repositories. In a shared file system, a resource identifier and metadata are created for a resource, where the resource identifier is stored in a lock file in a shared volume accessible by the remote repositories. The lock file is then released in response to distributing the associated resource to the remote repositories. Alternatively, in a peer-to-peer system, a request is received to create, read, update or delete a resource stored in a content repository. A resource name, a resource version and/or a resource fingerprint are received in connection with the request to create, read, update or delete the resource in the content repository. A determination is then made as to whether the received resource name, resource version and/or resource fingerprint matches the respective resource name, resource version and/or resource fingerprint stored in a node graph for the resource.