This document discusses DevOps concepts and examples. It describes DevOps as a culture and practice that emphasizes collaboration between software developers and IT operations. The document provides examples of infrastructure as code, building and packaging applications, and deployment. It discusses using tools like Azure Resource Manager, Docker, and VSTS Release Management to automate processes like continuous delivery.

2. Esempi di Pipeline e DevOps
Giulio Vian
http://blog.casavian.eu/
giulio.dev@casavian.eu
@giulio_vian
http://www.getlatestversion.it/

3. DevOps by Examples
Giulio Vian
http://blog.casavian.eu/
giulio.dev@casavian.eu
@giulio_vian
http://www.getlatestversion.it/

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

5. L’ultimo progetto cui ho partecipato
Miss Universe 2016
Iris Mittenaere
© 2016 IMG Universe, LLC.
All Rights Reserved

6. Di che si chiacchiera?
DevOps?
Esempi
Un ambiente per il codice
Una applicazione
Il suo rilascio
Riconfigurazione
Riassunto e riferimenti
Livello semplice
o avanzato?

7. È una figura professionale?

8. È un prodotto?

9. DevOps is a culture, movement or practice
DevOps is a term used to referto 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.
Wikipedia (2017)
Gartner
Microsoft
(Donovan Brown)

10. Evoluzione di Continuous Delivery
Source: Jez Humble © 2010

11. La ciccia
Dove?
Infrastructure-as-Code
Cosa?
Build & Package
Come?
Deploy

12. Ambiente di esecuzione
Sistema Operativo
Moduli S.O.
Servizi locali, Librerie
Applicazione
Rete e Servizi esterni
Dati

13. Ambiente di esecuzione (alt)
Base container
Custom Container
Applicazione
(in container)
Rete e Servizi esterni
(e.g. Kubernetes)
Dati

14. Considerazioni sull’ambiente di esecuzione
Tempi di allestimento
Costi di esercizio

15. Infrastructure-as-Code
Azure Resource Manager
• Codice
• Automazione

16. Infrastructure-as-Code – Considerazioni
Declarativo o Imperativo
Version Control
Continuous Integration
Dinamico o Statico
Azure Resource Manager
Declarative Json-based
Extensible (script, DSC)
Entire infrastructure
AWS CloudFormation
Declarative Json-based
Docker
Not much declarative
Single container
Ansible, Puppet, Chef, CFEngine, …

17. Applicazione
Pagina web con dati da DB
• Ambiente
• Configurazione

18. Build & Package – Considerazioni
Version Control
Continuous Integration
Semantic Versioning
Artifacts
Immagini (Docker, AMI, Azure VM images)

19. Deploy
VSTS Release Management
• Automazione controllata

20. Segreti
Build time
Sign
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

21. Deploy – Considerazioni
Categoria
Dev / QA / Prod
Integrato (dinamico)
Frequenza di Rilascio
Feature toggles
Source: Pete Hodgson

22. Configurazione dinamica
Feature toggle

23. Non abbiamo il tempo di parlare di
Application Monitoring
Troubleshooting
Feedback loop

24. Persone
(Photo: DoD)

25. Automazione
(Photo: Alexander Dummer)

26. Call to action

27. Question time

28. Thanks to our Sponsors

29. Bibliografia & Riferimenti
http://martinfowler.com/articles/feature-toggles.html
https://leanpub.com/build
https://launchdarkly.com/
http://www.slideshare.net/giuliov/presentations
http://agilemanifesto.org/
https://azure.microsoft.com/en-us/services/application-insights/
https://github.com/tfsaggregator/tfsaggregator
https://github.com/aspnet
https://azure.microsoft.com/en-us/services/key-vault/
https://aws.amazon.com/kms/
https://blogs.msdn.microsoft.com/buckh/2016/09/30/controlling-exposure-through-
feature-flags-in-vs-team-services/

30. To know more
Continuous Delivery: Reliable Software Releases
through Build, Test, and Deployment Automation —
J.Humble, D.Farley (Addison-Wesley)
https://www.amazon.it/Continuous-Delivery/dp/0321601912/
Continuous Delivery with Visual Studio ALM 2015 —
M.Olausson, J.Ehn (Apress)
http://www.amazon.it/Continuous-Delivery-Visual-Studio-
2015/dp/1484212738/

31. Fine delle trasmissioni