From 38d38de1d0a26daf3eb032ba62fcb4a3175c8761 Mon Sep 17 00:00:00 2001 From: RamonTC Date: Tue, 10 Oct 2017 19:46:54 +0200 Subject: [PATCH] Updated 11. Setting the solution up in Service Fabric (markdown) --- ...tting-the-solution-up-in-Service-Fabric.md | 46 ++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-) diff --git a/11.-Setting-the-solution-up-in-Service-Fabric.md b/11.-Setting-the-solution-up-in-Service-Fabric.md index 6271281..5e138d1 100644 --- a/11.-Setting-the-solution-up-in-Service-Fabric.md +++ b/11.-Setting-the-solution-up-in-Service-Fabric.md @@ -44,4 +44,48 @@ Open the SF explorer page to check out the deployment and healthcheck status. -### - Deploying eShopOncontainers as Linux Containers to Azure Service Fabric (TBD) \ No newline at end of file +### - Deploying eShopOncontainers as Linux Containers to Azure Service Fabric + +In order to deploy eShopOnContainers as Linux Containers an Azure SF environment must be first set. There is available an ARM template to do that job in the following link [SF Linux ARM deployment](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/az/servicefabric/LinuxContainers). Follow the steps in [create SF](https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/deploy/az/servicefabric/LinuxContainers/readme.md). +The ARM script will generate all the necessary Azure resources to publish eShopOnContainers as Linux containers. + +Once the SF resources have been successfully created, the next step is to publish the SF projects. These projects are under the directory [SF Directory](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/ServiceFabric/Linux) and contains all the xml config files needed to configure and publish eShopOnContainers. It is composed by the following SF projects: + + + +- eShopOnServiceFabric: contains all the api services consumed by eShop. +- eShopOnServiceFabricIdSrv: contains the Identity server for authentication. +- eShopOnServiceFabricWebMVC: contains the MVC web app. +- eShopOnServiceFabricWebSPA: containes the SPA web app. +- eShopOnServiceFabricWebStatus: contains the web app for service health checking. +- eShopOnServiceFabricBus: contains a bus service (Rabbitmq). +- eShopOnServiceFabricNoSql: contains a no sql service (MongoDB). +- eShopOnServiceFabricRedis: contains a cache service (Redis). +- eShopOnServiceFabricSql: contains a sql service (Mssql). + +Before deploying, replace **ALL** the external urls in the cloud.xml config file of each SF app which reference the SF dns name with the dns name of your SF. Example: + + + + + + + + + +To deploy the SF apps: +- Open the eShopOnContainers-ServicesAndWebApps.sln with vs2017 (Service Fabric SDK installation must be installed). +- Add the existing SF projects in the solution in order to be published. +- Right-click on each SF project selecting the publish button. Firstly, publish the infrastructure services [SF infrastructure services](https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/ServiceFabric/Linux/Infrastructure) and once deployed, do the same process for the rest of apps. + + + +A new window will be prompted allowing you to select the SF cluster you have previously created. + +![image](https://user-images.githubusercontent.com/1712635/30892260-9769397a-a305-11e7-9f41-2b86e398c366.png) + +Open the SF explorer page to check out the deployment and healthcheck status. + + + + \ No newline at end of file