Šibenik, 4 April 2019 http://windays.hr/ In this talk, you will hear about the DevOps journey in our company, from the initial brown-field all-manual state, to our current situation where we migrated (almost) everything to the cloud using automation in a few months. Not a migration but rebuilding the environment using Infrastructure-as-Code tools: Terraform, Powershell, Ansible, TFS/Azure DevOps. In equilibrium between an high-level view and useful practical tips, we will touch on what informed our decisions, in terms of priorities and technologies, some lessons learned, and how the legacy constraints helped or hindered.

1. How we moved
our environments
to the cloud

2. Session framing

3. Agenda
Azure Pipelines

6. Green-field

7. Initial State
Hosting
DB
LanguagesOS
Tools

8. Issues Problems
Rare and troublesome releases
Incongruent environments
Resistance to change
‘Don’t touch it’ mindset
Lack of Scalability

9. Technical debt

10. © Lara Paulussen

11. Change

12. © Fr. Lawrence Lew,

13. Infrastructure Application stack Pipelines
Azure Pipelines

15. Unique naming

16. Seclude

17. Regions gotchas

18. Central US
Environments
East US 2 West EU
Central US East US 2 West EU
C E
Sandbox LegacySandbox
U
Q
D
I

19. Central US
Environments
East US 2 West EU
Central US East US 2 West EU
C E U
Q
D
I

20. Control costs

21. Tips

22. Summary Cloud works
Plan
Design
Control

24. Terraform DSL
resource azurerm_virtual_machine vm_demo
demovm
northeurope
tf-demo
azurerm_network_interface.vm_demo.id
Standard_B2s
MicrosoftWindowsServer
WindowsServerSemiAnnual
Datacenter-Core-1803-smalldisk
latest
demovm-osdisk
ReadWrite
FromImage
demovm-datadisk
Empty
100
DEMOVM
var.vm_admin_username
var.vm_admin_password
true
false

25. How it works

26. Language Limits (HCL <0.12)

27. Critical choices

28. Summary
Terraform is easy
Don’t push too hard
Treat as usual code

31. Desired State Configuration (DSC)
Configuration MyBox
{
# Install the IIS role
WindowsFeature IIS
{
Ensure = "Present"
Name = "Web-Server"
}
# Install the ASP .NET 4.5 role
WindowsFeature AspNet45
{
Ensure = "Present"
Name = "Web-Asp-Net45"
}
#...
}


32. Ansible
---
- hosts: webservers
vars:
http_port: 80
max_clients: 200
remote_user: root
tasks:
- name: get latest version
yum:
name: httpd
state: latest
- name: write the config file
template:
src: /srv/httpd.j2
dest: /etc/httpd.conf
notify:
- restart apache
- name: ensure running
service:
name: httpd
state: started
handlers:
- name: restart apache
service:
name: httpd
state: restarted

33. Working together

Alternatives

34. Summary This worked for us
There are other ways
Biggest effort
Ready to host apps
Gray area: pipeline deploy

35. Formerly
known as
Azure Pipelines

36. Deployment Groups Azure Pipelines

37. Configuration Values Azure Pipelines

38. Summary Source control
Source control
Source control
Deployment groups
Key Vault

43. Money Project approved on cost reduction
Estimate an X% saving on operational expenses

44. Side effects

45. Version control migration Azure Repos

46. and the
road goes
on…

47. Bio in pictures
giulio.dev@casavian.eu
@giulio_vian
https://www.slideshare.net/giuliov
http://blog.casavian.eu/
https://tfsaggregator.github.io
Hardware spec:
1KB RAM (upg. 16KB)
4KB ROM
First computer Companies Communities

48. To know more
https://www.amazon.com/Continuous-
Delivery/dp/0321601912/
https://www.amazon.com/DevOps-Handbook-World-
Class-Reliability-Organizations/dp/1942788002/

49. To know more (cont’d)
https://www.amazon.co.uk/gp/product/1491977086/
https://leanpub.com/the-dsc-book
1491977086/

50. Links
https://continuousdelivery.com/
https://www.terraform.io/
https://github.com/giuliov
https://azure.microsoft.com/en-us/services/key-vault/
https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions
https://martinfowler.com/articles/evodb.html
http://www.powershellgallery.com/
https://docs.microsoft.com/en-us/powershell/dsc/overview
https://itrevolution.com/devops-handbook-debunking-devops-myths/
https://docs.ansible.com/

51. The End