CLOUD COMPUTING AS A SERVICE FOR ENTERPRISE SOFTWARE AND DATA PROVISIONING

• US 20110276685A1
• Filed: 05/09/2011
• Published: 11/10/2011
• Est. Priority Date: 01/22/2010
• Status: Abandoned Application

• Current Assignee: Brutesoft, Inc.
• Original Assignee: Brutesoft, Inc.
• Inventors: de Waal, Abraham Benjamin, DeSwardt, Stephanus Jansen, Joubert, Niels, Joubert, Pieter Hendrik
• Application Number:
  US13/103,265
• Publication Number:
  US 20110276685A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system, including a central server, remotely install server agents, and administrative agents, is disclosed for provisioning software and updates, maintenance directives, and data to client machines within a central domain or a remote disjoint domain. By monitoring network traffic through various network nodes, a focal point of network traffic for all machines in the domain may be identified by the central server. A server agent is installed at the focal point network node for identifying all machines in the domain. Administrative agents are installed on all identified machines. The administrative agents facilitate the copying and distribution of files needed for software and data provisioning and maintenance.

Claims

1. A method of provisioning software and data from a central server, the method comprising:

identifying a network node operative as a focal point of network traffic associated with machines in a network domain;

monitoring network traffic propagating through the identified network node;

responsive to monitoring the network traffic, identifying each machine having initiated a corresponding portion of the network traffic through the network node to a network resource;

determining an administrable state of each identified machine; and

provisioning software and data on each identified machine according to the respective determined administrable state.

2. The method of claim 1, further comprising:

responsive to the monitoring of network traffic, populating a service registry with identifier information including the administrable state corresponding to each machine; and

installing an agent on each machine with identifier information having an administrable state indicating that the machine is remotely administrable.

3. The method of claim 1, further comprising:

for a further machine with an administrable state determined to not be remotely administrable, redirecting access of the further machine from a targeted webpage to an administrative webpage;

at the administrative webpage, providing an authenticating process regarding a set of administrative instructions; and

responsive to providing the authenticated set of administrative instructions, receiving permission to copy, install, and initialize an agent on the further machine.

4. The method of claim 1, further comprising:

responsive to identification of the focal point, installing a server agent on the identified network node;

receiving, from the server agent and for each machine having initiated network traffic, identifier information;

classifying, using a decision tree, each machine according to the received identifier information; and

storing the received identifier information for each machine in a service registry,

wherein monitoring network traffic includes receiving identifier information comprising at least one of an identifier, a configuration listing, a network address, a machine name, a user identifier, and the administrable state.

5. The method of claim 4, wherein the decision tree includes matching the network address to a topological location, determining a provisioning schedule and provisioning policies corresponding to characteristics of the identifier information, and assigning a management profile corresponding to the determined provisioning schedule and provisioning policies of each respective machine.

6. The method of claim 4, further comprising:

determining for each respective machine, whether i) any software versions or maintenance directives are missing from the configuration listing, ii) the machine is newly discovered, or iii) the machine is remotely administrable;

mapping each machine within the service registry to a service classification; and

as a result of the classifying, the mapping, and the determination of any missing software versions and maintenance directives, configuring a management profile for each respective machine in the service registry.

7. The method of claim 4, wherein the network address of each machine includes subnet fields and further comprising:

analyzing a topological location and the subnet fields in the network address of each machine;

responsive to analyzing the subnet fields, correlating an address segment in the subnet fields to a local network topology associated to each machine; and

configuring the service registry according to the locally associated network topology.

8. The method of claim 1, further comprising:

monitoring, with the central server, further network traffic propagating through a further focal point associated with a further network node situated within a disjoint network domain external to the network domain, the further network traffic associated with further machines within the disjoint network domain having initiated the further network traffic to a further network resource;

installing a server agent on the further network node during an initial period of connectivity;

receiving cached identifier information from the server agent during a subsequent period of connectivity, the identifier information corresponding to each further machine of the disjoint network domain having accessed the further network resource; and

storing the cached identifier information received for each further machine of the disjoint network domain in the service registry.

9. The method of claim 8, further comprising:

instructing the further network node to;

monitor network traffic propagating through the further network node;

populate a further service registry with identifier information including the administrable state corresponding to each further machine;

install an agent on each further machine with identifier information having an administrable state indicating that the machine is remotely administrable; and

cache identifier information and results generated by respective agents for each monitored further machine during a period extending from the initial period of connectivity through the subsequent period of connectivity.

10. The method of claim 8, further comprising:

instructing the further network node to;

monitor network traffic propagating through the further network node;

populate a further service registry with identifier information including the administrable state corresponding to each further machine;

for a further machine with an administrable state determined to not be remotely administrable;

redirecting access of the further machine from a targeted webpage to an administrative webpage,

at the administrative webpage, providing an authenticating process regarding a set of administrative instructions, and

responsive to providing the authenticated set of administrative instructions and receiving a user'"'"'s permission, copying, installing, and initializing an agent on the further machine; and

cache identifier information and results generated by respective agents for each monitored further machine during a period extending from the initial period of connectivity through the subsequent period of connectivity.

11. A computer-readable storage medium embodying a set of instructions, that when executed by at least one processor, cause the at least one processor to perform operations comprising:

identifying a network node operative as a focal point of network traffic associated with machines in a network domain;

monitoring network traffic propagating through the identified network node;

responsive to monitoring the network traffic, identifying each machine having initiated a corresponding portion of the network traffic through the network node to a network resource;

determining an administrable state of each identified machine; and

provisioning software and data on each identified machine according to the respective determined administrable state.

12. The computer-readable storage medium of claim 11, wherein the operations further comprise:

responsive to the monitoring of network traffic, populating a service registry with identifier information including the administrable state corresponding to each machine; and

installing an agent on each machine with identifier information having an administrable state indicating that the machine is remotely administrable.

13. The computer-readable storage medium of claim 11, wherein the operations further comprise:

for a further machine with an administrable state determined to not be remotely administrable, redirecting access of the further machine from a targeted webpage to an administrative webpage;

at the administrative webpage, providing an authenticating process regarding a set of administrative instructions; and

responsive to providing the authenticated set of administrative instructions, receiving permission to copy, install, and initialize an agent on the further machine.

14. The computer-readable storage medium of claim 11, wherein the operations further comprise:

responsive to identification of the focal point, installing a server agent on the identified network node;

receiving, from the server agent and for each machine having initiated network traffic, identifier information;

classifying, using a decision tree, each machine according to the received identifier information; and

storing the received identifier information for each machine in a service registry,

wherein monitoring network traffic includes receiving identifier information comprising at least one of an identifier, a configuration listing, a network address, a machine name, a user identifier, and the administrable state.

15. The computer-readable storage medium of claim 14, wherein the decision tree includes matching the network address to a topological location, determining a provisioning schedule and provisioning policies corresponding to characteristics of the identifier information, and assigning a management profile corresponding to the determined provisioning schedule and provisioning policies of each respective machine.

16. The computer-readable storage medium of claim 14, wherein the operations further comprise:

determining for each respective machine, whether i) any software versions or maintenance directives are missing from the configuration listing, ii) the machine is newly discovered, or iii) the machine is remotely administrable;

mapping each machine within the service registry to a service classification; and

as a result of the classifying, the mapping, and the determination of any missing software versions and maintenance directives, configuring a management profile for each respective machine in the service registry.

17. The computer-readable storage medium of claim 14, wherein the operations further comprise:

analyzing a topological location and the subnet fields in the network address of each machine;

responsive to analyzing the subnet fields, correlating an address segment in the subnet fields to a local network topology associated to each machine; and

configuring the service registry according to the locally associated network topology.

18. The computer-readable storage medium of claim 11, wherein the operations further comprise:

monitoring, with the central server, further network traffic propagating through a further focal point associated with a further network node situated within a disjoint network domain external to the network domain, the further network traffic associated with further machines within the disjoint network domain having initiated the further network traffic to a further network resource;

installing a server agent on the further network node during an initial period of connectivity;

receiving cached identifier information from the server agent during a subsequent period of connectivity, the identifier information corresponding to each further machine of the disjoint network domain having accessed the further network resource; and

storing the cached identifier information received for each further machine of the disjoint network domain in the service registry.

19. The computer-readable storage medium of claim 18, wherein the operations further comprise:

instructing the further network node to;

monitor network traffic propagating through the further network node;

populate a further service registry with identifier information including the administrable state corresponding to each further machine;

install an agent on each further machine with identifier information having an administrable state indicating that the machine is remotely administrable;

for an additional further machine with an administrable state determined to not be remotely administrable;

redirecting access of the additional further machine from a targeted webpage to an administrative webpage,

at the administrative webpage, providing an authenticating process regarding a set of administrative instructions, and

responsive to providing the authenticated set of administrative instructions and receiving a user'"'"'s permission, copying, installing, and initializing an agent on the further machine; and

cache identifier information and results generated by respective agents for each monitored further machine during a period extending from the initial period of connectivity through the subsequent period of connectivity.

20. A system comprising:

a central server communicatively coupled with a plurality of client machines and configured to provide an agent to each of the plurality of client machines;

a network traffic monitor configured to identify a focal point of network traffic through a network node in an associated network domain;

a classification module configured to determine a classification of each of the client machines according to a decision tree and a respective administrable state of each respective client machine;

a mapping module configured to analyze a plurality of address segments in subnet fields of network addresses corresponding to each respective client machines;

an authentication module configured to interactively authenticate administrative instructions with each respective client machine; and

a storage module configured to retain a service registry containing identifier information corresponding to each respective client machine.