Introduction and practice of Microsoft cloud computing (19 practices)

The practices in the following sections focus on how to improve efficiency through automation, self-service and authorization control, and provide unified management for infrastructure, important components used in these practices are Service Manager, orchestrator, app controller, and virtual machine manager.

I. Automated self-service in Microsoft's private cloud

I will not talk much about Microsoft's private cloud automatic self-service, background knowledge and product features. I will post a few pictures and you can understand them.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/40/C2/wKioL1PPW2ySgfa0AAI0qjKmsHs405.jpg "style =" float: none; "Title =" 20140723143718.jpg" alt = "wkiol1ppw2ysgfa0aai0qjkmshs405.jpg"/>

(It requirements and system center functions)

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C2/wKioL1PPW2yz9fe0AAHavFkYUkM668.jpg "style =" float: none; "Title =" 20140723144217.jpg" alt = "wkiol1ppw2yz9fe0aahavfkyukm668.jpg"/>

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/40/C2/wKiom1PPWlLg4eizAAIdpwWpyj0129.jpg "style =" float: none; "Title =" 20140723144237.jpg" alt = "wkiom1ppwllg4eizaaidpwwpyj0129.jpg"/>

(Scenario of tenant and application owner)

2. orchestrator automation engine and integration package

Our administrator, John, knows that Orchestrator is a powerful and easy-to-use Automation engine, and it comes with a complete set of out-of-the-box automation functions. Orchestrator can also be easily expanded by using integration packages. An integration package is a combination of automatic functions. It virtually extends orchestrator functions to provide more automation functions and integrate them into other third-party applications. Therefore, in this practice, James will first deploy the integration package for system center 2012 SP1.

Download the integration package:

Http://www.microsoft.com/en-us/download/details.aspx? Id = 34611

Register the integration package:

When we use an integration package in orchestrator, We need to register it. John is the integration package for registering Microsoft Virtual Machine manager.

1. Connect to the Orchestrator Server as contoso \ administrator and open the local user and group

2. Open orchestratorusersgroup and add the contoso \ domain administrator.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C4/wKiom1PPW_-wOsSOAAEcETtrWJ8104.jpg "Title =" image1.jpg "alt =" wKiom1PPW_-wOsSOAAEcETtrWJ8104.jpg "/>

3. Open the orchestrator Deployment Manager in system center 2012 SP1

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C4/wKiom1PPXlayCeoZAAJw8KbbeSU246.jpg "Title =" image2.jpg "alt =" wkiom1ppxlayceozaa1_8kbbesu246.jpg "/>

4. Right-click the integration package and select the management server of the registered IP address and orchestrator.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C4/wKioL1PPX7HyGzTAAACoBcufJMQ955.jpg "Title =" image3.jpg "alt =" wkiol1ppx7hygztaaacobcufjmq955.jpg "/>

5. Select next in the welcome integration package Registration Wizard

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C5/wKioL1PPYI2C6JqcAAHXsQfQBqI917.jpg "Title =" image4.jpg "alt =" wkiol1ppyi2c6jqcaahxsqfqbqi917.jpg "/>

6. Select the Add button and browse to the location where your integrated package is stored.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C5/wKiom1PPX8DC1kCzAAET4ay_E3U825.jpg "Title =" image5.jpg "alt =" wkiom1ppx8dc1kczaaet4ay_e3u825.jpg "/>

7. Select system center 2012 SP1 Virtual Machine manager integration package and select Open

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C5/wKiom1PPX92ARvL5AALD_jV8lS4761.jpg "Title =" image6.jpg "alt =" wkiom1ppx92arvl5aald_jv8ls4761.jpg "/>

8. Select next. When you have added a management component

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C6/wKiom1PPYAfBOYKJAAEwvB9c8KI458.jpg "Title =" image7.jpg "alt =" wkiom1ppyafboykjaaewvb9c8ki458.jpg "/>

9. On the complete integration package page, select finish)

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C6/wKiom1PPYCGwwEIgAAGKSP5L2-I835.jpg "Title =" image8.jpg "alt =" wKiom1PPYCGwwEIgAAGKSP5L2-I835.jpg "/>

10. Accept the End User License Agreement by choosing. We usually have to do this multiple times (1 EULA is integrated per package)

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C5/wKioL1PPYVOgwjffAAGFvICJUF0276.jpg "Title =" image9.jpg "alt =" wkiol1ppyvogwjffaagfvicjuf0276.jpg "/>

3. Deploy the integration package

For the integration package that Mr. Zhang has registered, he also needs to deploy them to each runbook server and each server/workstation. The runbook designer will use this integration package. In our practice, John will deploy it on these orchestrator servers.

1. Open the Deployment Manager of the system center orchestrator on April 9, 2012.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C6/wKiom1PPYHixAF79AAE1b0ywU-w261.jpg "Title =" image10.jpg "alt =" wKiom1PPYHixAF79AAE1b0ywU-w261.jpg "/>

2. Right-click the integration package and select the server or runbook designer who deploys the IP address to runbook.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/40/C5/wKioL1PPYanQYJyiAADD7bQts1E488.jpg "Title =" image11.jpg "alt =" wkiol1ppyanqyjyiaadd7bqts1e488.jpg "/>

3. Select next in the welcome to the Integration deployment wizard.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/40/C5/wKioL1PPYb_yaEoYAAFLet4w7Ls865.jpg "Title =" image12.jpg "alt =" wkiol1ppyb_yaeoyaaflet4w7ls865.jpg "/>

4. On the deploy the integration package or patch page, Mr. Zhang selects the self-registered integration suite and then selects the next step.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C6/wKiom1PPYL2i2XuVAAEQKnjnzTk943.jpg "Title =" image13.jpg "alt =" wkiom1ppyl2i2xuvaaeqknjnztk943.jpg "/>

5. On the "Computer details" Page, select the name Type of the runbook server (in our case, this is in orchestrator), and then select the "add" button. Then select next

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C6/wKiom1PPYObCPNi8AAD2gsNurAw905.jpg "Title =" image14.jpg "alt =" wkiom1ppyobcpni8aad2gsnuraw905.jpg "/>

6. On the installation and configuration page, Mr. Zhang selects the currently deployed integration package. This will stop running manuals on all servers. If this is a problem, he can also choose to install or install the integration package without stopping the run manual or restarting the server later.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/40/C6/wKiom1PPYPrCAMzVAAGLrLhshi8410.jpg "Title =" image15.jpg "alt =" wkiom1ppyprcamzvaaglrlhshi8410.jpg "/>

7. On the complete integration package deployment page, select finish)

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/40/C6/wKioL1PPYmLTdWXpAAGyOFUCRKM795.jpg "Title =" image16.jpg "alt =" wkiol1ppymltdwxpaagyofucrkm795.jpg "/>

8. Verify deployment. You can view the integration package in the designer folder of runbook In the Deployment Manager of orchestrator. You can check the runbook server and select orchestrator to see if all the integration packages are displayed.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/40/C6/wKioL1PPYnbjUJeZAACej0LxMKM813.jpg "Title =" image17.jpg "alt =" wkiol1ppynbjujezaacej0lxmkm813.jpg "/>

Well, this job is boring, but it is all necessary for the subsequent major events. Let's go back to it!

This article from the "stars on my head" blog, please be sure to keep this source http://staronmytop.blog.51cto.com/6366057/1446991