Cloud-Based Automation of Resources

• US 20100153482A1
• Filed: 12/09/2009
• Published: 06/17/2010
• Est. Priority Date: 12/10/2008
• Status: Abandoned Application

• Current Assignee: Full Armor Corporation
• Original Assignee: Full Armor Corporation
• Inventors: Thompson, Paul R., Chung, Hakjae Robert, Kim, Danny
• Application Number:
  US12/634,050
• Publication Number:
  US 20100153482A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

In an example embodiment, workflow based procedures are authored, tested and converted to a collection of resource automation scripts with orchestration rules. The scripts and rules are uploaded to a cloud-based provisioning service. The cloud-based provisioning service follows the orchestration rules to coordinate with a provisioning agent installed on a VM host, storage area network (SAN) or other network device to execute a sequence of scripts to provision or tear down resources.

Claims

1. A computer implemented method comprising:

converting a workflow to plural resource automation scripts;

generating orchestration rules that define flow logic for executing the plural scripts in a defined sequence; and

sending the plural scripts and orchestration rules to a cloud-based service.

2. The method of claim 1 wherein the workflow includes plural activities and converting includes:

converting each activity to a corresponding script.

3. A computer implemented method comprising:

receiving a resource automation script from a cloud-based service;

executing the script;

generating status information associated with execution of the script; and

sending the script status information to the cloud-based service.

4. The method of claim 3 further comprising:

receiving a second script from the cloud-based service in response to the sent status information;

executing the second script;

generating status information associated with execution of the second script; and

sending the second script status information to the cloud-based service.

5. The method of claim 3 further comprising:

receiving event trigger information indicating occurrence of a particular monitored event;

sending the event trigger information to the cloud-based service; and

receiving the script in response to the sent event trigger information.

6. A computer implemented method of providing a cloud-based service, the method comprising:

receiving plural resource automation scripts and orchestration rules from an administration workstation, the orchestration rules defining flow logic for executing the plural scripts in a defined sequence;

selecting one of the plural scripts;

sending the selected script to an endpoint agent for execution by the endpoint agent; and

receiving status information associated with execution of the script from the endpoint agent.

7. The method of claim 6 further comprising:

selecting a second script of the plural scripts based on the received script status information;

sending the second script to the endpoint agent for execution by the endpoint agent; and

receiving status information associated with execution of the second script from the endpoint agent.

8. The method of claim 7 wherein selecting is based on the orchestration rules.

9. The method of claim 6 further comprising:

storing the plural scripts and orchestration rules to a storage resource of the cloud-based service.

10. The method of claim 6 wherein sending is responsive to receiving event trigger information from the endpoint agent.

11. A non-transitory computer-readable medium with an executable program stored thereon, wherein the program instructs a microprocessor to perform the following steps:

converting a workflow to plural resource automation scripts;

generating orchestration rules that define flow logic for executing the plural scripts in a defined sequence; and

sending the plural scripts and orchestration rules to a cloud-based service.

12. A non-transitory computer-readable medium with an executable program stored thereon, wherein the program instructs a microprocessor to perform the following steps:

receiving a resource automation script from a cloud-based service;

executing the script;

generating status information associated with execution of the script; and

sending the script status information to the cloud-based service.

13. A non-transitory computer-readable medium with an executable program stored thereon, wherein the program instructs a microprocessor to perform the following steps:

receiving plural resource automation scripts and orchestration rules from an administration workstation, the orchestration rules defining flow logic for executing the plural scripts in a defined sequence;

selecting one of the plural scripts;

sending the selected script to an endpoint agent for execution by the endpoint agent; and

receiving status information associated with execution of the script from the endpoint agent.

14. Apparatus comprising:

means for converting a workflow to plural resource automation scripts;

means for generating orchestration rules that define flow logic for executing the plural scripts in a defined sequence; and

means for sending the plural scripts and orchestration rules to a cloud-based service.

15. Apparatus comprising:

means for receiving a resource automation script from a cloud-based service;

means for executing the script;

means for generating status information associated with execution of the script; and

means for sending the script status information to the cloud-based service.

16. Apparatus comprising:

means for receiving plural resource automation scripts and orchestration rules from an administration workstation, the orchestration rules defining flow logic for executing the plural scripts in a defined sequence;

means for selecting one of the plural scripts;

means for sending the selected script to an endpoint agent for execution by the endpoint agent; and

means for receiving status information associated with execution of the script from the endpoint agent.