openstack
/
murano-deployment
Code Issues Proposed changes
murano-deployment/ExecutionPlan
History
Dmitry Teselkin 3614cb1bdc PowerShell functions updated. 
* More traps
* Assign undesirable output to $null
* Reorganize some execution plans

Change-Id: Ifb877ba3facc526baa2855432ad2d408cf23cb98
 		2013-08-09 00:43:07 +04:00
..
1.CreatePrimaryDC Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
2.JoinDomain Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
3.CreateSecondaryDC Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
4.JoinAndPromote Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
DeployWebApp Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
FailoverCluster AOAG execution plans updated. 2013-08-01 18:47:34 +04:00
GetDnsIpAddressesOnDc Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
InstallIIS Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
InstallSQL Execution plans for Failover Cluster added. 2013-07-30 15:30:53 +04:00
SqlServerAlwaysOnAvailabilityGroup PowerShell functions updated. 2013-08-09 00:43:07 +04:00
ExecutionPlanGenerator.exe Removed all projects except Glazier Deployment 2013-04-09 15:29:23 +04:00
ExecutionPlanGenerator.py Execution plan validation added. 2013-07-16 15:21:03 +04:00
Newtonsoft.Json.dll Removed all projects except Glazier Deployment 2013-04-09 15:29:23 +04:00
README.rst 'keero' and 'glazier' replaced by 'murano' 2013-04-25 16:27:00 +04:00

README.rst

Execution Plan

Execution Plan is a sequence of actions that should be run on an instance in order to configure it.

Execution Plan contains at least one step, and may reboot the instance.

An Exectution Plan definition file may contain following sections: * PowerShell functions that are passed to the instance as part of Execution Plan * At least one execution step * Conditional reboot statement

In order to simplify the process of Execution Plan creation, a simple SDL was introduced.

SDL's statements: * include <file with PowerShell functions> * call <PowerShell function name> [<argument name>=<argument value> [...]] * reboot <condition> * out <output file name>

SEE ALSO