Presentatie-Tech-talk.pptx
- 2. “Enable the reconstruction of the business from nothing but a source code repository, an application data backup, and bare metal resources” Jesse Robins
- 3. Why Infrastructure as code Business Development teams Operations/ IT
- 4. Consistently repeat the configurations. Tested and verified. Shared and promoted across the entire environment. Provide building blocks for the continuous delivery pipeline. Why Infrastructure as code
- 5. How infrastructure evolves Define topology Create tech. design Setup infrastructure Availability set Availability set Availability set Virtual Network Index Site 1 Site 2 Site N Search Word Automation Excel services BCS MMS Reporting Manual Deployments Release notes Deployment cycles Errors Solution? D T A P App servers Reporting DB server Replication Domain controller Domain controller Web server Web server Index Site 1 Site 2 Site N
- 6. Items of complexity What’s so complex? .NET framework Web Server Application pools Service accounts Permissions Server log files Web content Registry settings Users Index locations Updates Antivirus PowerShell modules Utilities Groups Configuration changes Firewall rules Ports Trusted computers Network configurations Files
- 7. How infrastructure evolves Define topology Create tech. design Setup infrastructure Availability set Availability set Availability set Virtual Network Index Site 1 Site 2 Site N Search Word Automation Excel services BCS MMS Reporting Manual Deployments Release notes Deployment cycles Errors Solution? D T A P App servers Reporting DB server Replication Domain controller Domain controller Web server Web server Index Site 1 Site 2 Site N
- 8. Current state Infrastructure automation Stable DTAP Changes to infrastructure in small iterations Test against lower environments Automated releases Release often Continuous monitoring Integrated into pipeline
- 9. Allow you to define the desired state of the system The how part is taken care by the software that converts the system to the desired state. Desired state?
- 10. Infrastructure management Configuration Node Node Role Resource Resource Resource Resource Resource
- 11. Components of Infrastructure as code Node Node Node Node Node Node Workstation Version control Configuration management server Users Continuous integration
- 12. Components of Infrastructure as code Workstation Server Node Create and authorize configurations Manage nodes, roles, data etc. Manage cloud resources Push configurations Monitor Manage History and reporting Contact server and pulls configurations Compile and run
- 13. Ansible Demo – Open source track
- 14. PowerShell DSC Visual Studio Team Services Azure Git Chocolatey Pester/ FluentShell unit Chef Reports Release pipeline Demo – Microsoft track
- 15. Prajeesh Prathap CONTACT Technical Agile consultant Thank you Maarten Kossen CONTACT Technical Agile consultant
Editor's Notes
- #4: With constantly evolving and changing market, business agility is one of the capabilities to be adopted by firms to be able to respond to new changes and ideas faster. Software development practices has changed a lot recently making the development teams capable of adopting to these changes But IT still uses the old way of manual configurations, custom scripts, golden images or outdated tools to manage infrastructure, leading to slower deployments and too many errors.
- #11: Configuration -> Declarative syntax, defining a configuration Resource -> Items of complexity Role -> DB server, Web front end Node -> Servers that the configuration is to be applied Agent vs. agentless operations