În această sesiune Mihai Tătăran vorbește despre cum puteți îmbunătăți procesul de dezvoltare, permițând echipei de dezvoltare software / QA să își creeze propriile medii de dezvoltare, testare, staging, înloc să le aștepte să le creeze departamentul IT. De asemenea, veți vedea cum puteți măriți viteza de deployment și să reduceți totodată costurile IT pentru mediile Dev / Test.

1. 23 NOIEMBRIE 2017 | BUCUREȘTI
DevTest cu Microsoft Azure
MIHAI TĂTĂRAN
General Manager, Avaelgo

2. 23 NOIEMBRIE 2017 | BUCUREȘTI
Mulțumiri sponsorilor și partenerilor
SPONSORI
ORGANIZATOR
PARTENER MEDIA
PARTENER DE IMAGINE

3. PEACE OF MIND
AS-A-SERVICE
CLOUD STRATEGY | MANAGED SERVICES | IT SECURITY | TRAINING

4. 23 NOIEMBRIE 2017 | BUCUREȘTI
Mihai Tătăran
• General Manager @ Avaelgo
–Microsoft Gold Cloud Platform Partner
–Training and consulting, Software development,
Infrastructure
• Microsoft Azure Most Valuable Professional
• Co-founder @ ITCamp & ITCamp Community

5. 23 NOIEMBRIE 2017 | BUCUREȘTI
Objectives
• Understand the challenges of DevTest
• See a solution with Microsoft Azure

6. 23 NOIEMBRIE 2017 | BUCUREȘTI
• Major disconnection between Development and Infrastructure teams
• Who is in charge of the temporary infrastructure?
• Sounds familiar?
– Dev team asks for a few VMs for their Dev / Staging environment, for proper
functional and integration testing
– Infrastructure team gets the ticket / request, sends it through the proper channels
to relevant person in charge
– VMs are created and Dev team is notified
– VMs are not exactly how the dev team has requested. Redo previous steps
– Tests are done
– Dev team forgets to notify infrastructure team to release the VMs
Dev/Test challenges: Disconnection Dev / Infrastructure

7. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev/Test challenges: cost
• Having tens or hundreds of VMs in an on premises
infrastructure is a major cost issue
• Especially if they are not needed all the time:
–Day and night?
–The whole development lifecycle? E.g.: is it good enough
to have them every 2 weeks on Wednesday to Friday?

8. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev/Test challenges: skills
• Development process
• Developer tools: TFS, VSTS, Release Management,
etc.
• Infrastructure team process
• Infrastructure tools: PowerShell, etc.

9. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev/Test challenges: business constraints
• Software as a Service
• Deliver faster / shorter time to market

10. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev/Test challenges: hard to configure
• Staging infrastructure needs to be identical to the
Production infrastructure
• How do you guarantee that, repeatedly, with
minimum work?

11. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev & test today
Provision VMs
Use VMs

12. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev & test in the cloud
Manageenvironment
Use VMs
Provision VMs

13. 23 NOIEMBRIE 2017 | BUCUREȘTI
Dev/Test with Azure
• Self service: Dev team can create temporary infrastructures
– Infrastructure team can create / contribute to rules, workflows, etc.
• Elasticity: shut down the VMs over nights, weekends; be able
to scale easily
• Fast: provisioning takes minutes to complete
• Less waste using: quotas, access policies, automatic
shutdowns
• Create once, use as a template
• Integrates with existing toolchain: Visual Studio, git, Puppet,
Chef, Eclipse

14. 23 NOIEMBRIE 2017 | BUCUREȘTI
Continuous Integration tools from Microsoft
TFS
Team Foundation Server
THE CI / CD tool from MS
AZURE INTEGRATION
TFS with Release Management
VSTS with Build, Release tabs
VSTS
Visual Studio Team Services,
former VSO
Lightweight, SaaS version of TFS

15. 23 NOIEMBRIE 2017 | BUCUREȘTI

16. 23 NOIEMBRIE 2017 | BUCUREȘTI
VSTS features
• Seems too simple for
complex scenarios
• But, there are interesting
things you can do:
– Copy files
– Run PowerShell scripts
on target VMs
– Run tests
– Approve

17. 23 NOIEMBRIE 2017 | BUCUREȘTI
Deployment process
Source Code
editing in Visual
Studio
Visual Studio Team
Services BUILD
Visual Studio Team
Services RELEASE
Environment
Creation as
specified by ARM
template
Email
confirmation.
Testing can begin
Solution
deployment
With VMs
prerequisites

18. 23 NOIEMBRIE 2017 | BUCUREȘTI
Environment creation
• Environment(s) creation in Azure
–Dev, Test, Staging, etc.
• No matter how complex they are
–Load balancers, virtual networks, storage accounts, IPs,
VMs, etc.
• In an automated fashion
• Repeatedly
• Identically

19. 23 NOIEMBRIE 2017 | BUCUREȘTI
Azure Resource Groups
Tightly coupled containers of multiple resources
of similar or different types
Which have common lifecycle and management
Every resource must exist in one and only one
resource group
Resource groups can span regions
Can be created using ARM templates

20. 23 NOIEMBRIE 2017 | BUCUREȘTI
Declarative v.s. Imperative
Declarative (What) Imperative (How)
Define WHAT it should be (Desired State)
without specifying how it is being done in
details
Define HOW things should be done
explicitly in details steps in order to
achieve the desired result
"resources": [
{
"type": "<resource-type-name>",
"name": "<name-of-the-resource>",
"location": "<location-of-resource>",
"dependsOn": [
"<array-of-related-resource-names>"
],
"properties": "<settings-for-the-resource>",
"resources": [
"<array-of-child-resources>"
]
}
]
Write-Host "Selecting subscription '$subscriptionId'";
Set-AzureRmContext -SubscriptionID $subscriptionId;
$resourceGroup = Get-AzureRmResourceGroup -Name
$resourceGroupName -ErrorAction SilentlyContinue
if(!$resourceGroup) {
Write-Host "Resource group '$resourceGroupName' does not exist.
New-AzureRmResourceGroup -Name $resourceGroupName -Location
$resourceGroupLocation }
else{ Write-Host "Using existing resource group
'$resourceGroupName'"; }

21. 23 NOIEMBRIE 2017 | BUCUREȘTI
Solution deployment
• Prerequisites on Virtual Machines
–Windows features
–Setup
–Configuration
• Actual solution deployment
• Challenges:
–Make sure the prerequisites are installed every time
–Even more: promote from Staging to Production

22. 23 NOIEMBRIE 2017 | BUCUREȘTI
PowerShell Desired State Configuration
• Specify the desired state of each VM in your
environment
• Push the specification
• Or let the VM pull it and refresh its state
• Reusing the configurations
–Throughout deployments (v1, v2, v3,…)
–Throughout mediums (Dev, Test, Staging, Production)

23. 23 NOIEMBRIE 2017 | BUCUREȘTI
Traditional Scripts vs DSC
DSC Configurations
Intent
DSC Resources
Technology Specific
DSC Engine
Dependency Resolution
Logging & Error Handling
Reboot Resiliency
Repeatable Automation
Traditional Scripts

24. 23 NOIEMBRIE 2017 | BUCUREȘTI
Easy to write and easy to deploy
Intent Environment
Configuration
(Dev -> Test -> Production)
$WebConfigEnv = @{
ComputerName = $VMServerNames
Name = “FourthCoffee”
}
…
Structural
Configuration
WindowsFeature IIS {
Name = "Web-Server"
Ensure = "Present"
}
…
Make It So Idempotent
Automation
foreach -parallel ($featureName in $Name)
{
$feature = Get-WindowsFeature -Name $featureName
if(($Ensure -eq "Present") -and (!$feature.Installed))
{
Install-WindowsFeature -Name $featureName
}
….
}
…
Source: Channel 9

25. 23 NOIEMBRIE 2017 | BUCUREȘTI
• Push
– Manual Process. DSC Resources have to be copied to the nodes
– Use Start-DscConfiguration to copy the MOF to the nodes and tell
them to make it so.
• Pull
– Use Push to enroll nodes, configuring them to query a Pull Server.
The nodes then check the pull server every 30 minutes for
configuration changes.
– DSC Resources must be zipped and placed on the Pull Server
– Every generated MOF file has to be accompanied by a checksum file
and both need to be placed on the Pull server.
Two Deployment Modes

26. 23 NOIEMBRIE 2017 | BUCUREȘTI
PowerShell DSC Scenarios
• You can deploy “bare” VMs and have DSC configure them
based on a role (Web Server, SQL Server, AD Domain
Controller, Cluster etc.)
– No more gold images
• You can keep production servers in check
– You can be sure that everything that you configured via DSC will
stay that way even if somebody tampers with the configuration
• Create multiple identical environments with ease.
– Dev, QA, Staging, Production
• You can use DSC with your release management tools.
– VSTS, TFS, TeamCity etc.

27. 23 NOIEMBRIE 2017 | BUCUREȘTI
Sample BUILD

28. 23 NOIEMBRIE 2017 | BUCUREȘTI
Sample RELEASE

29. 23 NOIEMBRIE 2017 | BUCUREȘTI
Sample email confirmation

30. 23 NOIEMBRIE 2017 | BUCUREȘTI
DEMO
Visual Studio Team Services
Azure Dev/Test environments and process

31. 23 NOIEMBRIE 2017 | BUCUREȘTI
New version CI/CD process
8 am: start environment creation
and deployment to DEV
Work, test, etc.
8 pm: automatic DEV
environment deleted
8 am: deploy to QA
(environment exists)
Testing is done in QA. QA approved for promotion
Build from QA used for a new
Release in STAGING
Testing / integration testing is
done in STAGING
STAGING approved for Prod
delivery
DEV
QA
STAGING
PRODUCTION environment

32. 23 NOIEMBRIE 2017 | BUCUREȘTI
DevTest Labs
• A service in Azure
• Quickly create environments
– Using templates (ARM)
• Formulas (reusable bases):
– Agents, tools, programs (such as Visual Studio, Fiddler, etc.)
you need on your VMs
– Actions
– Applications to test
• Minimize waste using Caps. E.g.: number of VMs / user
• Control costs with Policies. E.g.: shut down VMs on a
schedule

33. 23 NOIEMBRIE 2017 | BUCUREȘTI

34. 23 NOIEMBRIE 2017 | BUCUREȘTI
DEMO
DevTest Labs

35. 23 NOIEMBRIE 2017 | BUCUREȘTI
Next steps
• Raffle
• Avaelgo events: https://avaelgo.ro/blog/