AUTONOMOUS SERVER AGENTS

• US 20150350006A1
• Filed: 06/02/2015
• Published: 12/03/2015
• Est. Priority Date: 06/03/2014
• Status: Active Grant

• Current Assignee: JumpCloud, Inc.
• Original Assignee: JumpCloud, Inc.
• Inventors: Bhargava, Rajat, Brown, James, Marie, Christopher
• Granted Patent: US 10,257,017 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/166 at the transport layer

Abstract

Methods, systems, and devices are described for orchestrating server management in an information technology network. The described techniques may be implemented to manage any number of networked severs, whether local, remote, or both. Server orchestration may leverage a central, cloud-based management system and one or more autonomous agents installed on servers within the network. The autonomous agents may each be registered with the supervisory server and may operate with awareness of one another.

Claims

1. A method of server management, comprising:

installing an autonomous agent on a subservient server;

registering a unique identifier of the autonomous agent with a supervisory server; and

establishing a secure communication mechanism between the autonomous agent and the supervisory server.

2. The method of claim 1, further comprising:

registering an initial server management task at the autonomous agent.

3. The method of claim 2, further comprising:

executing the initial server management task on the subservient server with the autonomous agent, irrespective of connectivity between the autonomous agent and the supervisory server.

4. The method of claim 2, further comprising:

determining an additional task to execute based at least in part on the initial server management task execution; and

deciding to execute the additional task on the subservient server, irrespective of connectivity between the autonomous agent and the supervisory server.

5. The method of claim 2, wherein registering the initial server management task comprises executing a server script comprising a command associated with the initial server management task.

6. The method of claim 2, further comprising:

identifying a server management task execution by another agent installed on another server; and

executing the initial server management task on the subservient server with the autonomous agent based at least in part on the identifying and irrespective of connectivity between the autonomous agent and the supervisory server.

7. The method of claim 2, further comprising:

registering a new server management task at the autonomous agent.

8. The method of claim 1, further comprising:

registering a plurality of server management tasks at the autonomous agent; and

executing the plurality of server management tasks on the subservient server with the autonomous agent according to a schedule or on an ad hoc basis, irrespective of connectivity between the autonomous agent and the supervisory server.

9. The method of claim 1, wherein the secure connection mechanism comprises a transport layer security (TLS) protocol.

10. The method of claim 1, wherein the supervisory server comprises a cloud-hosted server.

11. A system to manage servers, comprising:

a supervisory server that manages tasks on a set subservient servers, each subservient server of the set having a network connection to the supervisory server;

a first autonomous agent on a first subservient server of the set of subservient servers; and

a console that provides access by a user to the supervisory server for management of the first subservient server via the first autonomous agent, the console in communication to the supervisory server.

12. The system of claim 11, further comprising:

a second autonomous agent on a second subservient server of set of subservient servers, wherein the console provides access by the user to the supervisory server for management of the second subservient server via the second autonomous agent.

13. The system of claim 11, wherein the first autonomous agent comprises:

a task cache module that registers one or more tasks in response to a script or command executed at the supervisory server;

a processing module that executes the tasks registered with the task cache module, wherein the processing module is in communication with the task cache module.

14. The system of claim 13, wherein the first autonomous agent comprises:

a timing module that directs the processing module to execute the tasks registered with the task cache module within a time period defined by the user or upon expiration of a timer, or both.

15. The system of claim 11, wherein the supervisory server comprises:

a server orchestration module that manages, schedules, or execute tasks on the first subservient server utilizing the first autonomous agent.

16. The system of claim 11, wherein the supervisory server comprises:

a command execution module that executes commands utilizing the first autonomous agent, wherein the command execution module is in communication with a server orchestration module.

17. The system of claim 11, wherein the supervisory server comprises:

a user management module that stores user credentials, user preferences, locations of subservient servers of the set, or a combination thereof, wherein the user management module is in communication with a data store.

18. The system of claim 16, wherein the supervisory server comprises:

a scheduler module that executes tasks according to a schedule provided by the scheduler module, wherein the scheduler module is in communication with the command execution module.

19. The system of claim 11, further comprising:

a data store in communication with the supervisory server, wherein the data store comprises content, scripts, tasks, event logs, or user data, or a combination thereof.

20. A system to manage a set of subservient servers, comprising:

a first autonomous agent on a first subservient server of the set of subservient servers, the first autonomous agent comprising;

a first task cache module that registers one or more tasks for execution on the first subservient server in response to a command executed at a supervisory server;

a first processing module that executes the tasks registered with the first task cache module, wherein the first processing module is in communication with the first task cache module;

a first timing module that directs the first processing module to execute the tasks registered with the first task cache module within a time period defined by a user or upon expiration of a first timer, or both.

a second autonomous agent on a second subservient server of the set of subservient servers, the second autonomous agent comprising;

a second task cache module that registers one or more tasks for execution on the second subservient server in response to the command executed at the supervisory server;

a second processing module that executes the tasks registered with the second task cache module and based at least in part on tasks executed by the first processing module, wherein the first processing module is in communication with the second task cache module;

a second timing module that directs the first processing module to execute the tasks registered with the second task cache module within the time period defined by the user or upon expiration of a second timer, or both;

a console that provides access by the user to the supervisory server for management of the first subservient server via the first autonomous agent and the second subservient server via the second autonomous agent, wherein the console is in communication with the supervisory server; and

wherein the supervisory server has a network connection with each subservient server of the set of subservient servers and comprises;

a server orchestration module that manages registration of the one or more tasks with the first task cache module and the second task cache module based at least in part on direction from the user; and

a command execution module that executes the command to register the one or more tasks with the first and second task cache modules.