From 6db288dc7676c6a5ce8e2656d9f9d07776d3fff9 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Mon, 16 Oct 2017 14:14:54 -0700 Subject: [PATCH 1/4] Update readme.md --- deploy/az/servicefabric/WindowsContainers/readme.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/deploy/az/servicefabric/WindowsContainers/readme.md b/deploy/az/servicefabric/WindowsContainers/readme.md index 4b6920e42..016279e0a 100644 --- a/deploy/az/servicefabric/WindowsContainers/readme.md +++ b/deploy/az/servicefabric/WindowsContainers/readme.md @@ -1,8 +1,13 @@ -# Deploying Azure Service Fabric (No Secured) +# Deploying a Service Fabric cluster based on Windows nodes (No Secured) +You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster -The ARM template `servicefabricdeploy.json` and its parameter file (`servicefabricdeploy.parameters.json`) are used to create a service fabric cluster environment for windows containers. +However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster. -## Editing servicefabricdeploy.parameters.json file +Because of those reasons, we have created a set of ARM templates and scripts so you can create, re-create and configure the SF clusters much faster, as explained below: + +Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\WindowsContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/WindowsContainers), you can find the ARM template `servicefabricdeploy.json` and its parameters file (`servicefabricdeploy.parameters.json`) to create a Service Fabric cluster environment for Windows Containers. + +## Edit the servicefabricdeploy.parameters.json file Edit the following params in `servicefabricdeploy.parameters.json` file to set your values: From d79e7e2dac3bff124d05c2f1bad473cb356997cc Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Mon, 16 Oct 2017 14:14:59 -0700 Subject: [PATCH 2/4] Update readme.md --- deploy/az/servicefabric/LinuxContainers/readme.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/deploy/az/servicefabric/LinuxContainers/readme.md b/deploy/az/servicefabric/LinuxContainers/readme.md index 5bdd86737..bfaf9c81a 100644 --- a/deploy/az/servicefabric/LinuxContainers/readme.md +++ b/deploy/az/servicefabric/LinuxContainers/readme.md @@ -1,6 +1,11 @@ -# Deploying Azure Service Fabric (No Secured) +# Deploying a Service Fabric cluster based on Linux nodes (No Secured) +You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster -The ARM template `servicefabricdeploy.json` and its parameter file (`servicefabricdeploy.parameters.json`) are used to create a service fabric cluster environment for linux containers. +However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster. + +Because of those reasons, we have created a set of ARM templates and scripts so you can create, re-create and configure the SF clusters much faster, as explained below: + +Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\LinuxContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/LinuxContainers), you can find the ARM template `servicefabricdeploy.json` and its parameters file (`servicefabricdeploy.parameters.json`) to create a Service Fabric cluster environment for Linux Containers. ## Editing servicefabricdeploy.parameters.json file From c16b1120a09185bdb98099464b33ac95da0be748 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Mon, 16 Oct 2017 14:38:54 -0700 Subject: [PATCH 3/4] Update readme.md --- .../servicefabric/WindowsContainers/readme.md | 27 ++++++++++++------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/deploy/az/servicefabric/WindowsContainers/readme.md b/deploy/az/servicefabric/WindowsContainers/readme.md index 016279e0a..c995883dc 100644 --- a/deploy/az/servicefabric/WindowsContainers/readme.md +++ b/deploy/az/servicefabric/WindowsContainers/readme.md @@ -12,26 +12,33 @@ Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\ Edit the following params in `servicefabricdeploy.parameters.json` file to set your values: - clusterName: Name of your SF cluster +- clusterLocation: Datacenter location, like westus or westeurope +- computeLocation: Datacenter location, like westus or westeurope +- adminUserName: user-name for VMs administration +- adminPassword: user-password for VMs administration - dnsName: Name assigned to your SF dns -- adminUserName: user name for administration -- adminPassword: user password for administration -Optionally, you can modify which ports are opened in the LoadBalancer for accessing externally to the apps: - -- webMvcHttpPort: port externally exposed for the WebMVC app -- webSpaHttpPort: port externally exposed for the WebSPA app -- webStatusHttpPort: port externally exposed for the WebStatus app -- IdSrvHttpRule: port externally exposed for the Identity app +Optionally, you could modify which ports are opened in the LoadBalancer for the multiple eShopOnContainer apps and API services. +By default, they are setup as: +- webMvcHttpPort: 5100 +- webSpaHttpPort: 5104 +- webStatusHttpPort: 5107 +- IdSrvHttpRule: 5105 +- BasketApiHttpRule: 5103 +- CatalogApiHttpRule: 5101 +- OrderingApiHttpRule: 5102 +- MarketingApiHttpRule: 5110 +- LocationsApiHttpRule: 5109 ## Deploy the template Once parameter file is edited you can deploy it using [create-resources script](../readme.md). -i. e. if you are in windows, to deploy sql databases in a new resourcegroup located in westus, go to `deploy\az` folder and type: - +For example, to deploy the cluster to a new resourcegroup located in westus, go to `deploy\az` folder and type: ``` create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy newResourceGroup -c westus ``` + ## Deploy eShopOnServiceFabric with Visual Studio. Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool. From 94a64fd3825d3898eba4be947d42566812db4b73 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Mon, 16 Oct 2017 14:38:58 -0700 Subject: [PATCH 4/4] Update readme.md --- .../servicefabric/LinuxContainers/readme.md | 28 ++++++++++++------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/deploy/az/servicefabric/LinuxContainers/readme.md b/deploy/az/servicefabric/LinuxContainers/readme.md index bfaf9c81a..0c29b50cc 100644 --- a/deploy/az/servicefabric/LinuxContainers/readme.md +++ b/deploy/az/servicefabric/LinuxContainers/readme.md @@ -7,31 +7,39 @@ Because of those reasons, we have created a set of ARM templates and scripts so Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\LinuxContainers](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/LinuxContainers), you can find the ARM template `servicefabricdeploy.json` and its parameters file (`servicefabricdeploy.parameters.json`) to create a Service Fabric cluster environment for Linux Containers. -## Editing servicefabricdeploy.parameters.json file +## Edit the servicefabricdeploy.parameters.json file Edit the following params in `servicefabricdeploy.parameters.json` file to set your values: - clusterName: Name of your SF cluster +- clusterLocation: Datacenter location, like westus or westeurope +- computeLocation: Datacenter location, like westus or westeurope +- adminUserName: user-name for VMs administration +- adminPassword: user-password for VMs administration - dnsName: Name assigned to your SF dns -- adminUserName: user name for administration -- adminPassword: user password for administration -Optionally, you can modify which ports are opened in the LoadBalancer for accessing externally to the apps: - -- webMvcHttpPort: port externally exposed for the WebMVC app -- webSpaHttpPort: port externally exposed for the WebSPA app -- webStatusHttpPort: port externally exposed for the WebStatus app -- IdSrvHttpRule: port externally exposed for the Identity app +Optionally, you could modify which ports are opened in the LoadBalancer for the multiple eShopOnContainer apps and API services. +By default, they are setup as: +- webMvcHttpPort: 5100 +- webSpaHttpPort: 5104 +- webStatusHttpPort: 5107 +- IdSrvHttpRule: 5105 +- BasketApiHttpRule: 5103 +- CatalogApiHttpRule: 5101 +- OrderingApiHttpRule: 5102 +- MarketingApiHttpRule: 5110 +- LocationsApiHttpRule: 5109 ## Deploy the template Once parameter file is edited you can deploy it using [create-resources script](../readme.md). -i. e. if you are in windows, to deploy sql databases in a new resourcegroup located in westus, go to `deploy\az` folder and type: +For example, to deploy the cluster to a new resourcegroup located in westus, go to `deploy\az` folder and type: ``` create-resources.cmd servicefabric\LinuxContainers\servicefabricdeploy newResourceGroup -c westus ``` + ## Deploy eShopOnServiceFabric with Visual Studio. Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool.