Browse Prior Art Database

Collaborative Adaptive Agent Configuration in dynamically changing Cloud environment

IP.com Disclosure Number: IPCOM000226931D
Publication Date: 2013-Apr-24
Document File: 4 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for providing a collaborative adaptive agent configuration in a dynamically changing cloud environment is disclosed.

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

Page 01 of 4

Collaborative Adaptive Agent Configuration in dynamically changing Cloud environment

Disclosed is a method for providing a collaborative adaptive agent configuration in a dynamically changing cloud environment.

Autonomous agents running in Cloud environment (virtual/physical machines) collaboratively utilize inter-agent communication to identify active management servers and existing agents. The autonomous agents intelligently deduce their own configuration parameters via self-awareness of the information technology (IT) environment. Key aspects of this invention are self-awareness, self-adapt and inhabit functions to discover, monitor and understand how agents and servers interact with each other on their environment, and then drive to the conclusion of intelligent self-configuration to plug into the environment to execute proper functions. For example, an agent can discover the IT environment where the agent itself is installed, figures out the same environment's other agents and servers configurations. The configuration information may include which management server to connect to, using which credentials, at what frequency, what protocol is being used, what port number, what user is running other agents, which agent functions to perform, and etc. Agent functions can vary. Examples include monitor system availability, monitor resource utilization, measure application performance, provision software patches, monitor security, event reporting, and etc.

Monitoring of IT infrastructure (or Cloud infrastructure) requires deployment of monitoring agents to systems and applications. Similarly, other management functions such as provisioning of software, monitoring security, etc also require agents to be deployed on endpoints.

The following agent systems are considered:

Centralized Management system is used to figure out where to deploy the agents,


A.

provide credentials for the end points and given the right permissions, centralized system is able to push the agent code to the endpoint, install the agents and configure them to talk to the appropriate management server upon installation. The main drawbacks of this method are:


At the configuration time, connectivity is required between central management system and endpoints. Administrator is required to obtain appropriate credentials and permissions to deploy software agents on the endpoints.

Administrator goes to each endpoint and configures the agents manually to talk to


B.

desired management system. The main drawbacks of this method are:


High cost of deployment and configuration of agents to obtain value from the monitoring infrastructure. Manual labor of performing installation of agents at each endpoint, which would not scale when there are thousands or millions of endpoints. This method is available for customers to use in pretty much any agent based system.

Configuration via agent broadcasting. This method is utilized when an agent comes


C.

1


Page 02 of 4

up and advertises itse...