1. DevOps by examples Giulio Vian http://blog.casavian.eu/
@giulio_vian

2. 1990 ?
1992
2014
1995
freelance
1999
2015
TFS Aggregator
2010
2014
2016

3. Most recent project
© 2016 IMG Universe, LLC. All Rights Reserved

4. This Session
100/200-level
Grasp the essentials of the DevOps approach.
(well …, some essentials)
Leave open questions to the end

5. What we will talk about? DevOps intro Demos Wrap-up
Environment hosting the app
The Application itself
Deployment
Dynamic configuration
Wrap-up

6. Your turn
Azure Visual Studio Team Services (VSTS) ASP.NET Linux (Ubuntu)

7. «Appetizer»

8. DevOps is a job?
NO!

9. DevOps is a product?
NO!

10. DevOps is a culture, movement or practice
Wikipedia (2017)
DevOps is a term used to refer to a set of practices that emphasizes the collaboration and communication of both software developers and other information- technology (IT) professionals while automating the process of software delivery and infrastructure changes.
DevOps represents a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. DevOps emphasizes people (and culture), and seeks to improve collaboration between operations and development teams. DevOps implementations utilize technology — especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective.
DevOps is the union of people, process, and products to enable continuous delivery of value to our end users.
Gartner
DevOps is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment, where building, testing, and releasing software can happen rapidly, frequently, and more reliably.
Wikipedia (2017)
Microsoft (Donovan Brown)

11. Continuous Delivery evolution…
Source: Jez Humble © 2010

12. …rooted in Agile Principles
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan

13. «Main course» Where? Infrastructure-as-Code What? Build & Package
How? Deploy

14. Execution environment
Operating System
O.S. Modules
Local Services, Libraries
Application
Network & External Services
Data
The 1975 book _Algorithms + Data Structures = Programs_ of Turing Award winner Niklaus Wirth is still relevant.

15. Execution environment (alt)
Base container
Custom Container
Application (in container)
Network & External Services (e.g. Kubernetes)
Data
Out-of-scope

16. Execution environment – Comments
Setup times vs. launch times Capacity planning Running costs (Buy vs. Make)

17. Infrastructure-as-Code
Azure Resource Manager
Code
Automation

18. Infrastructure-as-Code – Comments
Declarative vs. Imperative Version Control Continuous Integration Dynamic vs. Static
Azure Resource Manager
Declarative Json-based
Extensible (script, DSC)
Entire infrastructure
AWS CloudFormation
Terraform
Docker
Not much declarative
Single container
Swarm, Kubernetes, Mesos, …
Ansible, Puppet, Chef, CFEngine, …

19. Application
Web page showing DB data
Environment
Configuration

20. Build & Packaging
Collect everything

21. Build & Packaging – Comments
Version Control Continuous Integration Semantic Versioning Artifacts Images (Docker, AMI, Azure VM images)

22. Deploy
VSTS Release Management
Controlled Automation

23. Secrets .gitignore Centralized Version Control Distinct repositories
Build time
Signing
Deploy time
Credentials
Run time
Tokens
Avoid exposures
git push hook
Static analysis
.gitignore
Centralized Version Control
Distinct repositories
Azure Key Vault,
AWS Key Management Service,
etc.

24. Deploy – Comments Category Integrated (dynamic) Release cadence
Dev / QA / Prod
Integrated (dynamic)
Release cadence
Feature toggles
Source: Pete Hodgson

25. Dynamic Configuration
Feature Toggle

26. Additional DevOps topics (out-of-scope)
Application Monitoring Troubleshooting Feedback loop …and more
Ops
Dev

27. «Dessert»

28. People
(Photo: DoD)

29. Automation
(Photo: Alexander Dummer)

30. Resources
(Photo: Elya)

31. Call to action
(Photo: Francesco Canu)

32. Bibliografy & References
team-services/

33. To know more
Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation — J.Humble, D.Farley (Addison-Wesley)
Delivery/dp/ /
The Phoenix Project — G.Kim, K.Behr, G.Spafford (IT Revolution Press)
DevOps-Helping-Business/dp/ /

34. To know more (cont’d)
The DevOps Handbook — G.Kim, P.Debois, J.Willis, J.Humble (IT Revolution Press)
Handbook-World-Class-Reliability- Organizations/dp/ /
Continuous Delivery with Visual Studio ALM 2015 — M.Olausson, J.Ehn (Apress)
Delivery-Visual-Studio-2015/dp/ /

35. Partial checklist
Where is configuration stored? How is configuration updated? Is production configuration isolated and secured? Where are the secrets and who can access them? How versions are tracked? Who authorizes changes and how? How data is preserved on updates? How data schema and module interfaces updates? Using environment images or scripts? How big is the deploy window? How are the tracked activities and errors? How are operational data is collected from production?

36. Fine delle trasmissioni

37. Demo Screenshots
Nota con VSTS cloud non significa pubblico!

38. Infrastructure-as-Code

39. Azure Portal

40. Resource Groups

41. Resulting Resource Group

42. Visual Studio Team Services – Project home

43. Visual Studio Team Services Release Management

44. Create/Update Resource Group

45. Install packages

46. Environment creation in progress

47. Resulting Environment

48. Application

49. Version Control

50. Home page

51. Query “C”

52. Build & Packaging

53. Continuous Integration

54. Semantic Versioning

55. App build script

56. Deploy

57. App deploy script – Database

58. App deploy script – Copy files to Target

59. App deploy script – Run final setup script

60. App deploy – configuration data

61. App deploy – source packages

62. Deploying the app

63. Deploying the app – pick a version

64. App deploy log

65. App deployed

66. Dynamic Configuration

67. Toggle feature script – generate new config files

68. Toggle feature deploy script – deploy config changes

69. New configuration data

70. Backup slides
Nota con VSTS cloud non significa pubblico!

71. DevOps is a culture, movement or practice
DevOps is a culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals while automating the process of software delivery and infrastructure changes.
DevOps is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment, where building, testing, and releasing software can happen rapidly, frequently, and more reliably.
Wikipedia (2017)
Wikipedia (2015)

72. Environments
Integration
Dev test
Laboratory QA
Staging
Production

73. Rollout dimensions Timeframe Size Patch Module Application System
Less then a week
One week
One month
A few month
Patch
Module
Application
System
Size

74. Rollout by steps Database tier Application tier Presentation tier
Cllient
Web
Application tier
Service tier
Database tier
Mainframe