Terraform : Infrastructure as Code : Quick Example

 Here we will see.

• Install Terraform on Windows Machine - Manual

• 
  

• Install Terraform on AWS EC2 - Manal

• Install Docker on AWS EC2 using Terraform Script

• Install Jenkins on AWS EC2 using Terraform Script

• Install AWS Components and provisioning using Terraform Script

• Upload the Terraform Script (Code into GitHub)

• terraform.tfstate - Track, Security, Access Provisioning 

• Terraform Registry and Providers

• Change Infrastructure using Script

• Destroy Infrastructure using Script - terraform destroy 

• Terraform Cloud 

allows teams to easily version, audit, and collaborate on infrastructure changes. It also securely stores variables, including API tokens and access keys, and provides a safe, stable environment for long-running Terraform processes.

For more hands-on experience with the Terraform configuration language, resource provisioning, or importing existing infrastructure, review the tutorials below.

• Configuration Language - Get more familiar with variables, outputs, dependencies, meta-arguments, and other language features to write more sophisticated Terraform configurations.

• Modules - Organize and re-use Terraform configuration with modules.

• Provision - Use Packer or Cloud-init to automatically provision SSH keys and a web server onto a Linux VM created by Terraform in AWS.

• Import - Import existing infrastructure into Terraform.

• 
  

DevOps and DevSecOps

 Do we need Repository for artifacts? 

Do we need repository only for dependencies and not for applications?

What is Infra as Code and how terraform helps?

DevOps :

Culture : 

     Development, Infra, IT, Business and Testing team - will work as single unit

Best Practices 

    Developers involve in IT Operations

    IT Operations involve in Development

    Version Control for Code, Infra, Repo

     Adapt new changes quickly to Code, IT, Process, Infra

    Everything Automated - Code, CI, CD, Testing, Reports

    Containerized Tools and Environment - DEV-PROD parity

Tools

    Source control - Code Repo, DockerHub, Access provisioning

    CI/CD - Jenkins Docker Images, Security, Access provisioning

    Testing 

    Code Coverage Tools 

    Configuration Management and Tools

    Binary Management/ Artifactory

    Monitoring 

    Security

    Collaboration

    

Spring Boot, Jenkins, Docker, Kubernetes on AWS EKS

Here we will

1. Simple Spring Webflux based API
2. Containerize the application using Docker
3. Create CI Jenkins Pipeline 
1. Build
2. Run Unit Tests
3. Run Jacoco Reports
4. Create Docker Image and Push to DockerHub
4. Create CD Pipeline
1. Login to AWS
2. Pull Docker Image from Docker Hub and create container
3. Deploy in AWS EKS
5. Configure CI pipeline to be triggered only when code checked-in to any feature/* branches
6. Configure CI pipeline to be triggered only when PR raised
7. Configure CD pipeline to be triggered only when PR merged
8. 
   

1. Simple Spring Webflux based API

For Sample API, please checkout the code from 

https://github.com/balajimathu/beer-order-service

1. Please check the README.md for how to build locally
2. Beer-Service.postman_collection.json for testing the application using postman. 

2. Containerize the application using Docker

    Add a file name "Dockerfile" into the application folder location. 

    Add below configuration 

FROM adoptopenjdk/openjdk11 COPY build/libs/*SNAPSHOT.jar beerOrderService.jar EXPOSE 8080 CMD ["java", "-jar", "beerOrderService.jar" ]       Here in above file we use the image adoptopenjdk/openjdk11 We copy the built jar file as beerOrderService.jar We expose the post it need to be executed.  The execution command to run application once container started

3. Create CI Jenkins Pipeline 

1. Build
2. Run Unit Tests
3. Run Jacoco Reports
4. Create Docker Image and Push to DockerHub

Create Jenkins 

Create CD Pipeline

1. Login to AWS
2. Pull Docker Image from Docker Hub and create container
3. Deploy in AWS EKS

Configure CI pipeline to be triggered only when code checked-in to any feature/* branches
Configure CI pipeline to be triggered only when PR raised
Configure CD pipeline to be triggered only when PR merged

    

Azure DevOps vs Jenkins

 

Azure DevOps vs Jenkins

• Group Tasks – Azure allows you to perform a sequence of tasks, already defined in a pipeline, into a single task, whereas Jenkins is generally done by a single user which leads to tracking and accountability problems.
• YAML Interface – With YAML in Azure Pipelines, you can configure CI/CD pipeline as code, whereas Jenkins doesn’t have a YAML interface.
• Platform, language, and cloud – In Azure Pipelines, you can deploy various applications including Node.js, android, iOS, java, python, and many more and then deploy to either on-premise, AWS, Azure, or GCP. With regards to Jenkins, you get scripted pipelines that must be programmed in Groovy.
• Analytics in Azure Pipelines is provided at the end with two parameters – rate and duration of the run. Jenkins doesn’t provide any analytics.
• Plugins and Tasks – The built-in plugins and extensions can be downloaded from Azure DevOps marketplace. Jenkins has a wide range of plugins to choose from.
• Integration of Azure Pipelines with Microsoft is easy, but requires configuration changes to integrate with non-Microsoft products. Jenkins, on the other hand, can easily be modified and extended.
• Easy Support – Since Jenkins is open source, there is a huge support from the agile teams.

Who wins the battle?

The battle boils down to the team or the project you work on. While Jenkins is more flexible to create and deploy complex workflows, Azure DevOps is faster to adapt. In most cases, organizations use both the tools and in such cases, Azure Pipelines supports integration with Jenkins.

Concerns with Jenkins: 

12

Workarounds needed for basic requirements

9

Groovy with cumbersome syntax

7

Plugins compatibility issues

6

Lack of support

6

Limited abilities with declarative pipelines

4

No YAML syntax

3

Too tied to plugins versions

Sample Jenkins File 

pipeline {

    agent none

    stages {

        stage('Build') {

            steps {

                sh 'npm install'

                sh 'npm run build'

            }

        }

        stage('Test') {

            steps {

                sh 'npm test'

            }

        }

    }

}

Azure-pipeline.yaml

jobs:

- job: Build

  steps:

  - script: npm install

  - script: npm run build

- job: Test

  steps:

  - script: npm test

If we containerized our applications.

Jenkinsfile

pipeline {

    agent none

    stages {

        stage('Build') {

            agent {

                docker {

                    image 'ubuntu:trusty'

                    args '-v $HOME:/build -w /build'

                }

            }

            steps {

                sh 'make'

            }

        }

        stage('Test') {

            agent {

                docker {

                    image 'ubuntu:xenial'

                    args '-v $HOME:/build -w /build'

                }

            }

            steps {

                sh 'make test'

            }

        }

    }

}

Azure-pipeline.yaml

resources:

  containers:

  - container: trusty

    image: ubuntu:trusty

  - container: xenial

    image: ubuntu:xenial

jobs:

- job: build

  container: trusty

  steps:

  - script: make

- job: test

  dependsOn: build

  container: xenial

  steps:

  - script: make test

After completion Jenkinsfile

post {

    always {

        echo "The build has finished"

    }

    success {

        echo "The build succeeded"

    }

    failure {

        echo "The build failed"

    }

}

Azure-pipeline.yaml

jobs: - job: always steps: - script: echo "The build has finished" condition: always() - job: success steps: - script: echo "The build succeeded" condition: succeeded() - job: failed steps: - script: echo "The build failed" condition: failed()

https://blog.opstree.com/2021/04/13/jenkins-vs-azure-devops/

Jenkins CI Pipeline for SpringBoot Application : Pipeline Script VS Pipeline Script from SCM

 Here we will create CI and CD Pipelines to build and deploy application using Jenkins pipelines.

We can create in two was 

1. Pipeline Script 

2. Pipeline Script from SCM

Docker : Docker, DockerCompose and DockerRun and params

Docker : Plugins comparison : palantir VS bmuschko

 https://plugins.gradle.org/search?term=com.palantir.docker

https://palantir.github.io/

https://tomgregory.com/bmuschko-docker-gradle-plugin-review/

https://tomgregory.com/automating-docker-builds-with-gradle/