Bonus Assignment for Midterm Exam of Spring 2025 DevOps Class

1. Tech Stack Used : Git Action, npm[Semantic Release], maven, react, springboot, docker, AWS[EC2, RDS, Route53, ECR]


2. Repository :

         -Source repo : contains FrontEnd and BackEnd Code. Added release.yml so it could do tagging with Semantic Release. 

        -Infra repo : contains Git Action Workflow scripts. I added “Promotion.yml” script so triggered script could pull latest docker image and deploy it on RC server. 


3. Work Flow :

        -source repo has a workflow that releases tag in commits by semantic release

        -once the release tag is created, it will kick off a promotion workflow in the infra repo

        -workflow in infra repo(promotion.yml) will pull docker image and run it on pre-installed EC2

        -pre-installed EC2 will contain SSL and it has domain name "myapp-rc.domain.com"



4. Implementation Details :

        4.1 Write release.yml(Git Action workflow file) in source code. : 


Only commits that abide certain rules will trigger semantic release. Also we need to set up Node.js to install semantic release here. BackEnd is made with Java and Maven. Also added “.releaserc.json” and “prepare-release.sh” file to support it. 







        4.2 Write workflow in infra repo : release.yml file will trigger another workflow script in infra repo. Newly tagged commit will trigger this workflow to pull latest docker image and deploy it on pre-installed EC2. 


                  


This script will pull latest docker image and tag it and then deploy it. 



        4.3 Pre-installed EC2 will contain SSL and it has domain name "myapp-rc.domain.com" : Pre-installed ec2 will contain SSL. I added related codes in nginx.conf in front-end code so it could find keys. 


Also through Route53, I linked the domain myapp-rc.domain.com to the ec2. Therefore after the build was finished I could access it by “https://myapp-rc.jakekwon.hair/” 



5. Challenges and lessons learned : Installing semantic release was tricky and I could find a github repo(link) that explained how to implement it to Java/Maven project. Other than that, giving proper permissions(e.g. Docker Socket) and Credentials(AWS credentials, Github Credentials) was important to run scripts. Plus, Java Version and node version caused error so I upgraded them. 


6. Assumptions made (Scenario) : 

        -Source Repo has the souce code of the project

        -Through Nightly-build(in infra-repo) the project is built and the image is stored in repository(ECR).

        -ECR image is deployed to QA Server so it can be tested.

        -Another Semantic Tag script in source code triggers deployment of RC Server. It is made from image in ECR which means it has passed smoke test. 


-video demo (link)

Comments

Post a Comment

Popular posts from this blog

CICD Pipeline - Midterm Exam of Spring 2025 DevOps Class

Image
  Introduction  This project was making CICD pipeline with Git Action, Docker, EC2, RDS, ECR, and Route53. I used my side project Jake (Social Media platform for international students) as source code. The flow of CI/CD pipeline goes like below. Source Repo contains Dockerfile and Docker-Compose.yml. It needs to run locally without any error. Infra Repo contains GitAction workflow codes. This triggers launching a temporary EC2 and fetch codes from source repo. It builds docker files and conducts smoke test. If smoke test succeeds, it pushes docker image to ECR, and it is deployed in EC2 as a QA Server. Route 53 directs IP address to domain name. The Issue  There were many issues and errors while building the CI/CD pipeline.  Source Repo Local test CORS Error : Connecting FrontEnd and BackEnd caused CORS error, which is not letting other origin use same address. To fix it, I used Reverse Proxy by Nginx, and added annotation in SpringBoot controller(@CrossOrigin)....
Read more

Open Source Project - Open Energy Dashboard

Image
  Open Source Project - Open Energy Dashboard Introduction  During last 4 weeks our CTI team (Hyunoh, Abas, Ezequiel, and Mon) worked on Open Energy Dashboard open-source project. Open Energy Dashboard(OED) is a project where it is used as an energy dashboard so that all the users can manage the energy usage of their worksite. ( link ) The Issue  We as a team coded a line group reading test case(c11) in JavaScript and TypeScript using Docker and Visual Studio Code, ensuring values are read correctly to reflect 14 days giving hourly point and middle readings. ( Link )   Test cases are important to enhance accuracy of a software. By writing and updating test case, we estimate we improved test coverage by 30% and enhanced data accuracy by 25% in a Dockerized environment, ensuring seamless integration and reliable energy value processing.  To resolve the issue, our team 1. looked up for development document,  2.starting Docker and activate web and database...
Read more

2025 Spring CS686 DevOps - Final Project

 Final Project Overview -make MSA service -use EKS -Automate -deploy blue-green strategy  -deployment flow : Nightly Build -> QA -> UAT -> Prod  Steps 1. Make MSA codes  Dismantled existing code into three services - backend1, backend2, and frontend 2. By Git Action test and deploy Made GitAction Workflow('Nightly-Build') to start temporary EC2 and test(smoke-test) the code. Used dockers to run three different services and tested if it works. 3. Deploy to QA Server Using GitAction, deployed it on QA server(single EC2 server). Now we can see it at IP address of EC2 instance.  4. Make EKS Cluster and Deploy Blue Service of UAT  Make VPC and EKS Cluster.  Make Node Group. Need to use good enough instance.  Using Git Action and yaml file from Infra repo, apply configuration to running pods on EKS.  Now your microservice is deployed on EKS and you can access it through url.  5. Switch it to Green Service of UAT  Deployment of Gr...
Read more