Abstract:
A deployment system enables a developer to define a logical, multi-tier application blueprint that can be used to create and manage (e.g., redeploy, upgrade, backup, patch) multiple applications in a cloud infrastructure. In the application blueprint, the developer models an overall application architecture, or topology, that includes individual and clustered nodes (e.g., VMs), logical templates, cloud providers, deployment environments, software services, application-specific code, properties, and dependencies between top-tier and second-tier components. The application can be deployed according to the application blueprint, which means any needed VMs are provisioned from the cloud infrastructure, and application components and software services are installed.
Abstract:
A deployment system orchestrates execution of deployment plan in coordination with nodes participating in deployment of a multi-tier application in a cloud infrastructure. The deployment system distributes local deployment plans to each node and maintains a centralized state of deployment time dependencies between tasks in different local deployment plans. Prior to execution of each task, deployment agents executing on each node communicates with the centralized deployment system to check whether any deployment time dependencies need to be resolved. Additionally, the deployment system utilizes a node task timer that triggers a heartbeat mechanism for monitoring failure of deployment agents.
Abstract:
A deployment system enables a developer to customize a deployment plan generated according to a logical, multi-tier application blueprint for deploying multiple applications in a cloud infrastructure. Using the deployment system, the developer inserts a custom script or task in a sequence of tasks to be performed to deploy an application component in different phases (e.g., installation, configuration, start-up) on a virtual machine. The deployment system anchors the custom script to the different phases of the application component's deployment such that the customizations to the deployment plan are maintained through changes to the underlying application blueprint.
Abstract:
A deployment system enables a developer to generate a deployment plan according to a logical, multi-tier application blueprint defined by application architects. The deployment plan includes tasks to be executed for deploying application components on virtual computing resource provided in a cloud infrastructure. The deployment plan includes time dependencies that determine an execution order of the tasks according to dependencies between application components specified in the application blueprint. The deployment plan enables system administrators to view the application blueprint as an ordered workflow view that facilitates collaboration between system administrators and application architects.
Abstract:
A deployment system orchestrates execution of deployment plan in coordination with nodes participating in deployment of a multi-tier application in a cloud infrastructure. The deployment system distributes local deployment plans to each node and maintains a centralized state of deployment time dependencies between tasks in different local deployment plans. Prior to execution of each task, deployment agents executing on each node communicates with the centralized deployment system to check whether any deployment time dependencies need to be resolved. Additionally, the deployment system utilizes a node task timer that triggers a heartbeat mechanism for monitoring failure of deployment agents.
Abstract:
Modeling a data path of a network environment is disclosed. Components are identified at a source location of a data path, at a target location of the data path, and connections there between. The network environment includes a plurality of domains, and the data path traverses the plurality of domains. Components and the connections there between are assigned to one of: an input-output path pattern, a virtualizer pattern, and a meta pattern. The patterns represent common elements of components of the network environment. The patterns and relationships between patterns are defined to repeat within and across domains in the network environment. A model of the data path is created from the assigned patterns and the defined relationships between patterns. The created model of the data path is then presented.
Abstract:
A system provides a user map service that receives component data associated with a resource in a storage area network and matches the component data to entries in a user-created component matching database to determine a specific identity of the resource in the storage area network to which the component data is associated. The system provides the specific identity of the resource in the storage area network to which the component data is associated. The system maintains the user-created component matching database by allowing a user to create matches between individual resources for which component data is received to specific identities of those resources as determined by the user. The database can be queried and updated to make matching more efficient.
Abstract:
A deployment system enables a developer to customize a deployment plan generated according to a logical, multi-tier application blueprint for deploying multiple applications in a cloud infrastructure. Using the deployment system, the developer inserts a custom script or task in a sequence of tasks to be performed to deploy an application component in different phases (e.g., installation, configuration, start-up) on a virtual machine. The deployment system anchors the custom script to the different phases of the application component's deployment such that the customizations to the deployment plan are maintained through changes to the underlying application blueprint.
Abstract:
A deployment system enables a developer to define a logical, multi-tier application blueprint that can be used to create and manage (e.g., redeploy, upgrade, backup, patch) multiple applications in a cloud infrastructure. In the application blueprint, the developer models an overall application architecture, or topology, that includes individual and clustered nodes (e.g., VMs), logical templates, cloud providers, deployment environments, software services, application-specific code, properties, and dependencies between top-tier and second-tier components. The application can be deployed according to the application blueprint, which means any needed VMs are provisioned from the cloud infrastructure, and application components and software services are installed.
Abstract:
A SAN connectivity advisor analyzes the physical connections of a physical fabric, identifies logical connections based on the physical connections and connectivity information, and applies a set of connectivity rules indicative of good or mandatory SAN connection practices. The connectivity advisor generates a report indicative of connections that may need or benefit from modification, typically an error message for each suspect connection found. The connectivity advisor applies the rules to each physical and logical connection to qualify the connection according to the rules, thus reflecting the actual configuration at the port-to-port connection level, rather than the conventional device-to-device level. Further, the connectivity advisor does not require an interoperability matrix or other database query of device interoperability. The generated results indicate suggested (warning) or mandatory (inoperative) actions for remedying particular connection anomalies, and in this manner, apply a consistent set of aggregated rules to each physical and logical SAN connection.