In my previous blog post, I discuss details of the workflow and gentlemen App Orchestration. In this blog, I'll cover more details on the specific workflow that creates the App Orchestration Technology.
The changes in the desired state trigger the creation of workflows. A stream consists of one or more steps. The same type of step could be included in different workflows. For example, a step can deal with moving machinery to an organizational unit. This step could be part of the flow of agricultural labor allocation or it could be part of the flow of decommissioning work machine. In both cases, the machines must be moved to a certain organizational unit, but the step is really the same thing with different parameters (names of different machine, different target OU).
Some workflows contain a single step. In this case, referring to the workflow name or stage name indicates the same operation, but the implementation is always the same. In future versions, several steps can be added to an existing workflow
The full list of workflows that can be triggered by the App Orchestration engine :.
1. OU structure
2. capacity of the machine
3. Workload machine metadata
4. The workload validation of the machine
5. Get Information agricultural
6. agricultural allocation
7. workload allocation machine
8. Updating the working group
9. subscription
10. de-allocation machine workload
11. Remove Application
12. sites Update Web interface
13. Remove a farm from a web interface site
Web site interface 14. Delete
15. Remove infrastructure machine
16. Remove control machine
17. Remove the machine workload
18. Remove the workload
the following is a list of the types of steps that a workflow can contain:
1. update-OR
2. Remove OR
3. Get-Capability
4. Get-metadata
5. Compare Metadata
6. Get-FarmInformation
7. Machine Movement
8. update-WebInterfaceSite
9. Remove-WebInterfaceSite
10. Remove-WebInterfaceSiteFarm
11. Add -WorkloadMachine
12. update to apply
13. Remove-enforcement
14. Start-drain
15. update-WorkerGroup
16. Remove-WorkerGroup
17 . Remove-FarmMachine
notice that the names of steps follow a similar naming convention PowerShell cmdlets. The App Orchestration Agent maps each step to a cmdlet name which is loaded within its PowerShell module. Having closely match the name of the step with the cmdlet name makes it easier to change a default implementation, as described in my previous blog. Note that the agent module adds a prefix to the part of the verb to follow PowerShell guidelines when building the cmdlet names. For example, the Get-capacity step is implemented by the cmdlet Get-CamCapability.
The first workflow, you will encounter is the "OU structure" workflow. He usually step update-OR which is intended to verify that the specified OU exist. In this case, the UO that need to be created are imported UO, which is where the machines have to be abandoned in order to be imported into the system.
When the agent detects App Orchestration machines in one of these OUs, workflow "machine capacity" are created for each machine. This workflow has the Get-Capability step that manages an image analysis tool to identify the capabilities of the machine. These capabilities are built according to software which is installed in the machine. For example, there are capabilities that identify and XenApp Web Interface machines. The actual content of capacity is only used internally for validation purposes.
After a machine is imported and validated its capabilities, depending on the type of machine, a different workflow is created. For workload of machines, the "workload Machine metadata" workflow is created next. This workflow is only assigned to the first machine of its catalog. It contains the Get-step Metadata works similar to the Get-Capability step. the image analysis tool is run to extract even more details on the machine. in this case, an inventory of all the applications available in the menu start is built, including data type icon association and file. When this workflow is completed, the returned data is stored in the corresponding workload catalog and will be used to validate other machines are added. this is done with the "validation workload of the workflow engine", which contains step-Compare Metadata. This step contains part of the data returned by the Get-step metadata that ran on the first machine of the catalog. Step confirms that all the data of the new machine match the expected values.
In the case of import of XenApp controller machines, workflow "Get agricultural information" is created. This workflow contains step-Get FarmInformation. This step retrieves the name of the farm, the controllers of the battery and the database information. Each controller will be affected this step. When the App Orchestration engine receives data for all controllers in a farm and agricultural object is created. At this point, one of the agents controller is assigned as principal. Only this agent will be used workflows that need to configure the battery. The other controller agents act as backups and will be used if the primary agent is down.
In the case of machines in the web interface, no other workflows are created at this stage. Assuming all workflows successfully completed all machines are now ready to be assigned workloads.
Up to this point, all work flows have been assigned to the App Orchestration agent running in the same box as the App Orchestration Engine. However, the Get-FarmInformation step is for the running agent in the machine controller of XenApp. In general, the workflows that are specific to a product are assigned to specific agents.
In the next blog I will continue to describe workflows that manage the allocation of machines.
This post is part of a series on the application orchestration. For the remaining articles in this series please refer to these articles:
• Concepts
• The architecture
• The Provisioning machines. Part 1 and 2
• Management of tenants (to come)
• Classified Management
• Manage Subscriptions (forthcoming)
• Patching workload Machinery (coming soon)
• Understanding Workflows. Part 1, 2 and 3
• Troubleshooting (forthcoming)
• Integration with CloudPortal Services Manager (forthcoming)
0 Komentar