| Step | 61 |Action | 62 |Result | 63 |
|---|---|---|
| 1 | 68 |Create an instance of the container and run it, by running the following command in PowerShell: 69 |docker run -p 80:80 -d --name eshoptest eshopweb:1.0 |
70 | This creates and starts a container, exposing port 80 on the local host. | 71 |
| 2 | 74 |Once the command return, open Edge and browse to http://localhost. | 75 |You should now see the application being served from the container. | 76 |
| 3 | 79 |Stop the container by running the command docker stop eshoptest in PowerShell | 80 |This stops the container and persists the state and configuration. You can then restart the container at a later point. | 81 |
| 4 | 84 |Remove the container by running the command docker rm eshoptest in PowerShell | 85 |This command will remove the container state and configuration. We will do this as in the next step we create a new instance of the container with a different configuration. | 86 |
| 5 | 89 |The application has a feature to add an environment variable to the front-page title. 90 |Create a new configuration of the container image, by running the following command in PowerShell: 91 |docker run -p 80:80 -d --name eshoptest -e eShopTitle=MyTitle eshopweb:1.0 92 |Note: 93 |This feature is implemented in the Site.Master.cs file. |
94 | Environment variables is a common way of passing configurations to containers. The -e parameter is used with docker to pass environment variables to containers. | 95 |
| 6 | 98 |Once the command returns, open Edge and browse to http://localhost. | 99 |You should now see the application title using your environment variable. | 100 |
| 7 | 103 |You can run commands inside a running container’. Output the environment variables from the container by running the following commands in PowerShell: 104 |docker exec eshoptest cmd.exe /C SET |
105 | You will see all the environment variables in the container being output. | 106 |
| 8 | 109 |Let’s stop and remove the container: 110 |
|
114 | 115 | |
| Step | 15 |Procedure | 16 |
|---|---|
| Create a container registry | 21 |Create a private container registry using the Azure Container Registry service. 22 |Note: This requires an Azure account |
23 |
| Build, tag and push the container image | 26 |Create a production ready container image and push it to the registry. | 27 |
| Pull the container image and run it locally | 30 |Pull the production ready image from the container registry and run it. | 31 |
| Step | 44 |Action | 45 |Result | 46 |
|---|---|---|
| 1 | 51 |Browse to https://shell.azure.com/ and sign-in to your Azure subscription. | 52 |If you do not have one, you can get a trial subscription here: https://azure.microsoft.com/en-us/free/ | 53 |
| 2 | 56 |Create a new resource group: 57 |az group create --name [insert rg name] --location eastus 58 |Note: Substitute the [insert rg name] with the name for your Resource Group |
59 | az will output information about the resource group. | 60 |
| 3 | 63 |Create a container registry in that resource group: 64 |az acr create --resource-group [insert rg name] --name [insert acr name] --sku Basic --admin-enabled 65 |Note: Substitute the [insert acr name] with the name for your registry name |
66 | az will output the information about the newly created acr. | 67 |
| 4 | 70 |Retrieve the credentials to sign-in to the container registry, and note these to be used later: 71 |az acr credential show --name [insert acr name] 72 |Note: Substitute the [insert acr name] with the name for your registry name |
73 | az will output the passwords and login names for the registry, which we will use later in the lab. | 74 |
| Step | 94 |Action | 95 |Result | 96 |
|---|---|---|
| 1 | 101 |Open PowerShell and run the following command to tag the image: 102 |docker tag eshopweb:1.0 [insert acr name].azurecr.io/eshopweb:1.0 103 |Note: 104 |The registry part of the container image tag should match the name of your container registry. |
105 | This command creates a container image tag with the container registry name and version of the container image. | 106 |
| 2 | 109 |Run the following command to login to your container registry: 110 |docker login [insert acr name].azurecr.io 111 |Note: 112 |To retrieve the login server, username and password, see above section |
113 | 114 | |
| 3 | 117 |Push the container image to your registry: 118 |docker push [insert acr name].azurecr.io/eshopweb:1.0 |
119 | This will start uploading the container image layers to you Azure Container Registry. | 120 |
MyEnvVar value: @Environment.GetEnvironmentVariable("MyEnvVar")
70 | ``` 71 | 72 | 1. Press **F5** to debug the application, once the web site comes up, go to the **About** page and you should see the value from the environment variable show up. 73 | 74 | 1. Without stopping the debugger, you can make changes to the About.cshtml file and reload the browser to see you changes. There is no need to redeploy the container and app to quickly see changes that do not require recompiling the code. 75 | 76 | 1. Stop the debug session by pressing **Shift+F5** 77 | 78 | ## Deploy the new version to Azure Service Fabric Mesh 79 | 80 | 1. To publish the updated application to Service Fabric Mesh in Azure, **Right-click** the Service Fabric Mesh application project and choose **Publish** 81 | 82 | 1. The publish dialog should have stored the information and you can click **Publish** 83 | 84 | This will kick-off a rebuild and deployment of the containers. Once finished go to the web site. You can also browse the Azure portal to see the environment variable that the container is running with. 85 | 86 | ### Completion 87 | 88 | In this section of the lab, we’ve build a new asp.net core service and deployed it to Azure Service Fabric Mesh -------------------------------------------------------------------------------- /Instructions/ServiceFabricMesh/5addservice.md: -------------------------------------------------------------------------------- 1 | # Create an second service to your application 2 | 3 | ## Goal 4 | 5 | The goal of this section is to add a second service to your .net core application and run it in Mesh. 6 | 7 | ## Process 8 | 9 | | **Step** | **Procedure** | 10 | | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | 11 | | Create a second service for our Service Fabric Mesh Application using Visual Studio | We will use Visual Studio to create a Service Fabric application hosting the container | 12 | | Setup communication between the services | Using HTTPClient to communicate | 13 | | Debug and deploy the services | We will see it running in Mesh | 14 | 15 | ## Add a second to the Service Fabric Application 16 | 17 | 1. In Visual Studio **right-click** the Service Fabric Mesh Application project and choose **Add --> New Service Fabric Service** 18 | 19 | 1. Choose **ASP.NET Core** and click **Next** 20 | 21 | 1. Choose the **API** template 22 | 23 | 1. Open the **ValuesController.cs** file in the **Controllers** folder 24 | 25 | 1. Substitute the **Get()** method with this method: 26 | 27 | ```c# 28 | public String Get() 29 | { 30 | return "Hello from the other side"; 31 | } 32 | ``` 33 | 34 | 1. Save the file 35 | 36 | ## Setup communication between the services 37 | 38 | 1. Open the **About.cshtml.cs** file in the first project you created 39 | 40 | 1. Add the following code snippet to replace the OnGet method 41 | 42 | ```c# 43 | public async Task OnGet() 44 | { 45 | HttpClient client = new HttpClient(); 46 | string response = await client.GetStringAsync("http://web1:2008/api/values); 47 | 48 | Message = response; 49 | } 50 | ``` 51 | 52 | **Note** Make sure to make the URL match the name of the new WebAPI service you created, as well as the port it's listening on. The port, can be found in the service.yaml file in the WebAPI project. 53 | 54 | ## Deploy the new version to Azure Service Fabric Mesh 55 | 56 | 1. To publish the updated application to Service Fabric Mesh in Azure, **Right-click** the Service Fabric Mesh application project and choose **Publish** 57 | 58 | 1. The publish dialog should have stored the information and you can click **Publish** 59 | 60 | This will kick-off a rebuild and deployment of the containers. Once finished go to the web site. You can also browse the Azure portal to see the environment variable that the container is running with. -------------------------------------------------------------------------------- /Instructions/ServiceFabricMesh/README.md: -------------------------------------------------------------------------------- 1 | # ContainersSFLab - Service Fabric Mesh application 2 | 3 | The instructions below walk you through working with ASP.NET for Azure Service Fabric Mesh. 4 | 5 | For more info about Service Fabric Mesh look here: https://docs.microsoft.com/en-us/azure/service-fabric-mesh 6 | 7 | Requirements for running the lab are documented here: https://docs.microsoft.com/en-us/azure/service-fabric-mesh/service-fabric-mesh-howto-setup-developer-environment-sdk 8 | 9 | You'll also need an Azure subscription. If you do not have one, you can get a trial subscription here: https://azure.microsoft.com/en-us/free/ 10 | 11 | ## Lab content 12 | 13 | 1. Build a Docker container and upload it to Azure Container Registry 14 | 1. [Build a Docker container for an existing asp.net application](./1buildacontainer.md) 15 | 1. [Create an Azure Container Registry and push the container](./2createacr.md) 16 | 1. Azure Service Fabric Mesh 101 17 | 1. [Deploy a container to Azure Service Fabric Mesh](./3meshhelloworld.md) 18 | 1. Build an application for Azure Service Fabric Mesh 19 | 1. [Use Visual Studio to create and ASP.NET Core application for Mesh](./4createappvs.md) 20 | 1. [Add more services to your application](./5addservice.md) 21 | 22 | If you are already familiar with building Docker containers and using ACR, you can skip the first part of the lab. -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2018 Mikkel Mork Hegnhoj 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # ContainersSFLab 2 | 3 | This repository containers instructions for two Service Fabric container labs: 4 | 5 | 1. [Containerize an existing ASP.NET application using Visual Studio and Service Fabric clusters](./Instructions/ServiceFabricNative.md) 6 | 7 | 1. [Hands-on with Azure Service Fabric Mesh](./Instructions/ServiceFabricMesh/README.md) 8 | -------------------------------------------------------------------------------- /eShopLegacyWebFormsSolution/eShopLegacyWebForms.sln: -------------------------------------------------------------------------------- 1 | 2 | Microsoft Visual Studio Solution File, Format Version 12.00 3 | # Visual Studio 15 4 | VisualStudioVersion = 15.0.27130.2020 5 | MinimumVisualStudioVersion = 10.0.40219.1 6 | Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "eShopLegacyWebForms", "src\eShopLegacyWebForms\eShopLegacyWebForms.csproj", "{4416714A-9BB8-480B-95B3-C2599598E3EC}" 7 | EndProject 8 | Global 9 | GlobalSection(SolutionConfigurationPlatforms) = preSolution 10 | Debug|Any CPU = Debug|Any CPU 11 | Debug|x64 = Debug|x64 12 | Release|Any CPU = Release|Any CPU 13 | Release|x64 = Release|x64 14 | EndGlobalSection 15 | GlobalSection(ProjectConfigurationPlatforms) = postSolution 16 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Debug|Any CPU.ActiveCfg = Debug|Any CPU 17 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Debug|Any CPU.Build.0 = Debug|Any CPU 18 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Debug|x64.ActiveCfg = Debug|Any CPU 19 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Debug|x64.Build.0 = Debug|Any CPU 20 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Release|Any CPU.ActiveCfg = Release|Any CPU 21 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Release|Any CPU.Build.0 = Release|Any CPU 22 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Release|x64.ActiveCfg = Release|Any CPU 23 | {4416714A-9BB8-480B-95B3-C2599598E3EC}.Release|x64.Build.0 = Release|Any CPU 24 | EndGlobalSection 25 | GlobalSection(SolutionProperties) = preSolution 26 | HideSolutionNode = FALSE 27 | EndGlobalSection 28 | GlobalSection(ExtensibilityGlobals) = postSolution 29 | SolutionGuid = {7BB9F6BE-2470-4251-80B7-0825E02EEA6F} 30 | EndGlobalSection 31 | EndGlobal 32 | -------------------------------------------------------------------------------- /eShopLegacyWebFormsSolution/src/eShopLegacyWebForms/About.aspx: -------------------------------------------------------------------------------- 1 | <%@ Page Title="About" Language="C#" MasterPageFile="~/Site.Master" AutoEventWireup="true" CodeBehind="About.aspx.cs" Inherits="eShopLegacyWebForms.About" %> 2 | 3 |Use this area to provide additional information.
7 |7 | 8 | Create New 9 | 10 |
11 | 12 || No data was returned. | 17 |
| 25 | | Name 26 | | 27 |Description 28 | | 29 |Brand 30 | | 31 |Type 32 | | 33 |Price 34 | | 35 |Picture name 36 | | 37 |Stock 38 | | 39 |Restock 40 | | 41 |Max stock 42 | | 43 |
|---|
58 | <%#:Item.Name%> 59 |
60 |63 | <%#:Item.Description%> 64 |
65 |68 | <%#:Item.CatalogBrand.Brand%> 69 |
70 |73 | <%#:Item.CatalogType.Type%> 74 |
75 |78 | <%#:Item.Price%> 79 |
80 |83 | <%#:Item.PictureFileName%> 84 |
85 |88 | <%#:Item.AvailableStock%> 89 |
90 |93 | <%#:Item.RestockThreshold%> 94 |
95 |98 | <%#:Item.MaxStockThreshold%> 99 |
100 |