Container Technologien sind neben Linux nun auch im Windows Umfeld angekommen. Applikationen als Container auszuliefern bringen viele Vorteile. Dieser Prozess soll, ganz in DevOps-Manier, voll automatisiert mittels dem Build und Release System von VSTS / TFS durchgeführt werden. Die Session zeigt Ihnen die Integration der Docker Tools in VSTS und TFS für Build und Release Management.

1. #td17ch
Asp.NET Core Anwendungen
automatisiert als Container
ausliefern
Marc Müller
PrincipalConsultant
4tecture GmbH

2. Marc Müller
Principal Consultant
@muellermarc

3. Agenda
Agenda
 Intro Docker und Asp.NET Core
 Docker Support in Visual Studio
 Docker CI / CD
 Enterprise Hosting / ACS

4. Microsoft

5. I like
…but I‘m a Microsoft Fan-Boy

6. Docker?
https://twitter.com/dberkholz/status/689211852157407233

7. 100 Deployments
pro Tag!

9. Monolithische Architektur
Orders
Products
DAL
Order
Data
Product
Data
BL
Order
Logic
Product
Search
Product
Logic
UI
Admin UI

10. API
Gateway /
Proxy
Order Service
Orders
Order
Data
Order
Logic
Customer
UI
Admin UI
Product Search Service
Products
Product
Data
Product
Search
Product Service
Products
Product
Data
Product
Search
MessageQueue
Micro-Service Architektur

11. Bleeding edge technology is a category of technologies so new that
they could have a high risk of being unreliable and lead adopters to incur greater expense in
order to make use of them.[1][2] The term bleeding edge was formed as an allusion to the similar
terms "leading edge" and "cutting edge". It tends to imply even greater advancement, albeit at an
increased risk because of the unreliability of the software or hardware.[3] The first documented
example of this term being used dates to early 1983, when an unnamed banking executive was
quoted to have used it in reference to Storage Technology Corporation.[4]
Source: https://en.wikipedia.org/wiki/Bleeding_edge_technology
Cutting Edge Technology

12. Intro Docker und Asp.NET Core

13. Server
Host OS
Hypervisor
Server
Host OS
Docker Engine
Guest
OS
Guest
OS
Guest
OS
Bins/Libs Bins/Libs Bins/Libs
App A App A’ App B
Bins/Libs Bins/Libs
AppA
AppA’
AppB
AppB’
AppB
AppB’
AppB
AppB’
Containers are isolated, but
share OS and, where
appropriate, bins/librariesBins/Libs
Image Source: https://sec.ch9.ms/sessions/build/2016/B822.pptx

14. Docker Layers
simpledockerdemo.Web
microsoft/aspnet
microsoft/dotnet
buildpack-deps:jessie-scm
buildpack-deps:jessie-curl
debian:jessie

15. Developer PC / Laptop
Environments - Development
Docker Engine
Container Container Container

16. Environments – Hosting / Cloud

17. Cloud Management
App1
App2

18. Vorteile von Containern
 Schnelles Deployment
 Schneller Start
 Einfaches Scaling und Partitioning
 Isolierter, versionierter, wiederverwendbarer Code (Artefakt /
Konfigurationselement)
Klare Abgrenzung zwischen Entwicklung und Betrieb
 Entwicklung kümmert sich um den Inhalt des Containers
 Betrieb kümmert sich darum, wie der Container verwendet wird

19. Docker Support in VS

20. Docker for Windows
https://docs.docker.com/docker-for-windows/

21. Visual Studio Tools for Docker
http://aka.ms/DockerToolsforVS

22. Demo
Docker for Windows
Manuelles Erstellen von Containern
VS Docker Support

23. Docker CI Build

24. Docker CI / CD
VSTS Build
VSTS Release
Management
Docker Registry
Build App
Test
Build Container
Repo
Container Info
Publish to Target
Host
Container Info
Push
Host
Pull
Config
Artifact

25. VSTS / TFS Build Agent
VSTS Build Agent
Build Pool
Build Pool
Build Pool
Build
Definition
Build
Definition
Build
Queue
Docker Engine
Build
Agent

26. Custom Docker Build Agent

27. Custom Docker Build Agent - DockerFile

28. Demo
VSTS Build Agent in Container

29. Setup in Azure Portal

30. Docker Registry API
Image Source: https://docs.docker.com/registry/spec/api/

31. Docker Registry API - Samples
List Repositories: /v2/_catalog
List Tags: /v2/<repository>/tags/list

32. Docker Registry – UI Sample
https://acrwebmanagerdemo.azurewebsites.net/

33. Azure Container Registry und Docker
 Login to your private registry docker login <registry> -u username -p password
 Pull the desired image docker pull <registry>/<repository>:<tag>
 Run the container docker run…

34. Demo
Docker Registry
Azure Web App Pull

35. Enterprise Hosting und
Continuous Deployment

36. Build/CI,
Integrate,
Test
3.
1.
Containerized Workflow
Monitor and Diagnose
Outer-Loop
Push
Code
Production
environments
Run, Manage
5.
6.
Container Service
Service Fabric
Batch
App Services
Coming soon
…
…
Code
Run
Validate
Debug
Inner-Loop
CD, Deploy
4.
Visual Studio Team Services
Source Code
Control
(SCC)
2.
Azure
Container
Registry
Image Source: https://sec.ch9.ms/sessions/69613110-c334-4f25-bb36-08e5a93456b5/206BuildDebugDeployASPNETCorewithDocker.pptx

37. Azure Container Service
ACS = ARM Templates
3 Varianten
 DC/OS with Marathon
 Docker Swarm
 Kubernetes
Image Source: https://docs.microsoft.com/en-us/azure/container-service/container-service-intro

38. Simplified ACS DCOS Setup
VSTS
Azure Resource Group
DCOS Master
DCOS Master
DCOS Master
DCOS Master
DCOS Master
Public Agent
DCOS Master
DCOS Master
Private Agent
Marathon-LB
VSTS Agent
App1
App1
App1
App1
App1
App2
Git
Build
Release
Internet
AzureLoadBalancer

39. CI / CD aus Visual Studio erstellen

40. Demo
ACS Build und Release

41. Azure Resource Group

42. Load Balancer Settings for Services

43. Load Balancer Settings for Services

44. Use Environment Variables

45. Zusammenfassung

46. Zusammenfassung
 Micro-Service Architektur
 Reduktion der Komplexität, einfacher und schnellere Deployments
 Automatisierung der Build- und Release-Prozesse
 Isolation der Services als Container
 Isolation der Build Umgebung (Agent)
 Load Balancing mittels Service Discovery

47. Besten Dank für Ihre Aufmerksamkeit
Für allfällige Fragen stehen wir Ihnen jederzeit
gerne zur Verfügung:
4tecture GmbH Marc Müller
Aathalstrasse 84 Principal Consultant
CH-8610 Uster
+41 44 508 37 00 marc.mueller@4tecture.ch
info@4tecture.ch @muellermarc
www.4tecture.ch