Distributed Configuration Orchestration for Network Client Management

• US 20090327465A1
• Filed: 06/27/2008
• Published: 12/31/2009
• Est. Priority Date: 06/27/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cannella, Sean Andrew, Healy, Michael J., Khan, Shafqat Ullah, Flegg, Brett D. A.
• Application Number:
  US12/147,483
• Publication Number:
  US 20090327465A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities

Abstract

Described is a network configuration management technology in which an orchestration point coordinates client machines and/or other machines to each run an activity with respect to the client machines to perform management tasks. The orchestration point controls the start of the activity. A management point and server may report progress. The orchestration point coordinates running the activities, e.g., serially or in parallel among the clients, and/or based on percentage of total machines allowed to simultaneously run an activity and/or current workload. Activities may include a task sequencing activity, a desired configuration management activity, a command set-related activity and/or a custom activity generated from a script, e.g., a PowerShell™ script. Also described is a replicator activity, which may be limited (e.g., based on a percentage of the total machines) and/or throttled (e.g., based on current load).

Claims

1. In a computing environment, a system comprising:

an orchestration point; and

a plurality of client machines coupled to the orchestration point, the orchestration point coordinating at least one management task with respect to managing the client machines.

2. The system of claim 1 wherein each client includes a client agent coupled to the orchestration point to run a management task via an activity on each client machine, the orchestration point controlling the start of the activity run by each client agent.

3. The system of claim 1 wherein the orchestration point coordinates at least one management task by controlling the start of an activity run on a machine that is a remote machine relative to at least one client being managed.

4. The system of claim 1 wherein the orchestration point comprises a workflow host that hosts a workflow runtime corresponding to the task and an execution engine that exposes operation to the workflow activity.

5. The system of claim 1 wherein the orchestration point coordinates running the management task, including running tasks serially by starting the management task on one client machine after completion of the management task on another client machine.

6. The system of claim 1 wherein the orchestration point coordinates running the management task, including running tasks at least partially in parallel by starting the management task on one client machine before completion of the management task on another client machine.

7. The system of claim 1 wherein the orchestration point coordinates running the management task on each client machine, including by determining when to start a management task on a machine based on a parameter that corresponds to how many machines may run the management task in parallel.

8. The system of claim 1 wherein the orchestration point coordinates running the management task on each client machine, including by determining when to start a management task on a machine based on a throttling parameter that corresponds to a current system load.

9. The system of claim 1 wherein the activity comprises a task sequencing activity, a desired configuration management activity, an activity corresponding to a command set, or an activity generated from a script.

10. The system of claim 1 wherein the management task corresponds to a replicator activity.

11. The system of claim 1 wherein the orchestration point is coupled to the client machines via an arbitrator or a database to assign workloads to servers, monitor performance, or forward commands or messages or both commands and messages to suspended workflows, or any combination of assigning workloads, monitoring performance, or forwarding commands or messages or both commands and messages.

12. The system of claim 1 further comprising a management server coupled to one or more of the client machines to output progress information based on received status information.

13. The system of claim 12 further comprising a management point, wherein the management server is coupled to the one or more client machines via the management point.

14. The system of claim 13 wherein the management point receives heartbeat messages from each client coupled thereto.

15. In a computing environment, a method comprising, coordinating activity instances of an activity across each of a plurality of client machines, including, for each activity instance, controlling a start of the activity, subscribing for status updates corresponding to the activity, receiving status updates, updating progress information based on a status updated that provides progress information, and completing the activity based upon a status update that indicates completion.

16. The method of claim 15 wherein the activity corresponds to a task sequence activity, and wherein receiving the status updates comprises receiving notifications from the task sequence activity based on status messages obtained by the task sequence activity from the client.

17. The method of claim 15 wherein coordinating the activity instances comprises, controlling how many client machines are running the activity at the same time based on an input parameter, or controlling how many client machines are running the activity at the same time based on a load parameter versus current load data, or both controlling how many client machines are running the activity at the same time based on an input parameter and based on a load parameter versus current load data.

18. In a computing environment, a system comprising:

an orchestration point;

a plurality of client machines coupled to the orchestration point, the orchestration controlling the start of an activity run with respect to each client machine; and

a management point coupled to receive status messages corresponding to progress in executing the activity with respect to at least one client.

19. The system of claim 18 wherein the activity is run on a client agent of the client machine or on a remote machine relative to the client machine, and wherein the orchestration point coordinates running the activity, including controlling how many client machines the activity applies to at a same time based on an input parameter, or controlling how many client machines the activity applies to at the same time based on a load parameter versus current load data, or both controlling how many client machines are running the activity at the same time based on an input parameter and based on a load parameter versus current load data.

20. The system of claim 18 wherein the activity is run on a client agent of the client machine or on a remote machine relative to the client machine, the activity comprising a task sequencing activity, a desired configuration management activity, an activity corresponding to running a command set, or a custom activity generated from a script, or any combination of a task sequencing activity, a desired configuration management activity, an activity corresponding to running a command set, or a custom activity generated from a script.