Introduction to Cloud Automation, Azure DevOps, Infrastructure As Code (IaC), PowerShell, Azure Resource Manager (ARM), Unit-Testing with Pester, CI/CD Pipeline with Azure DevOps and more!
You can find detailed description of the topic in the Article and Demonstrations in the Code. Also you can find a detailed example to guide you through a Infrastructure as Code example in Workshop
My Definition of Infrastructure as Code:
Infrastructure as Code (IaC) is the management of infrastructure in a descriptive model, using the same versioning as DevOps team uses for source code. Like the principle that the same source code generates the same binary, an IaC model generates the same environment every time it is applied
My Definition of DevOps:
DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The contraction of “Dev” and “Ops” refers to replacing siloed Development and Operations to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications.
So DevOps is about the union of people, process, and technology to enable continuous delivery of value to your end users.
- Consistency: Standardised provisioning
- Accelerating: Rapid deployment and provisioning
- Reusability: JSON code and pipeline
- Extensibility: Extensible JSON
Characteristics of Infrastructure as Code:
- Declarative
- Single source of truth
- Increase repeatability and testability
- Decrease provisioning time
- Rely less on availability of persons to perform tasks
- Use proven software development practices for deploying infrastructure
- Repeatable and testable
- Faster to provision
- Idempotent provisioning and configuration (calls can be executed repeatedly while producing the same result)
A practice in Infrastructure as Code is to write your definitions in a declarative way versus an imperative way.
You define the state of the infrastructure you want to have and let the system do the work on getting there. In the following sections we will have a look at tools to implement the practice.
- Help you to create a robust and reliable infrastructure
- Each time you deploy, the infrastructure will be exactly the same
- Easily change the resources you are using by changing code and not by changing infrastructure
- Everything should be automated to:
- save time
- make fewer manual configuration
- only allow tested changes
- ultimatly you will encounter fewer errors
- All changes in the infrastructure are accessible in source control.
- Source control gives great insight in why and what is changed and by whom.
- culture, movement or practice
- emphasizes collaboration and communication
- automating process of software delivery and infrastructure changes
- build, testing and releasing software
- softwaretestingfundamentals
- docs.microsoft
- What is Infrastructure as Code
- What is DevOps?
- derrickcawthon
- openedx.microsoft
- blogs.msdn.microsoft.com/azuredev
- blogs.msdn.microsoft.com/mvpawardprogram
- blogs.msdn.microsoft.com/mvpawardprogram
- Blog: Stop using ARM, use CLI instead
Contact me!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent