CI/CD
We will conduct a Well-Architected Review of Customer’s Infrastructure in the beginning of engagement. The first phase of the project will focus on following.
1) Capture Customer’s Infrastructure as code using Terraform. They are currently using Ansible.
2) Build a CI/CD Pipeline with AWS CodePipeline (One Service) After the first phase is done, Customer has the option to define deliverables on a monthly or semi-monthly basis in consultation with the Project Manager. The timeline of deliverables will be determined by the number of Engineer Hours included in Customer’s Ongoing Service Package. Currently, Customer has informed that these are the high priority items in the backlog
1) Continue building a CI/CD Pipeline for other services
2) Adopt automation for applying product upgrades and creating new customer sites
3) Will need to migrate off their old ELBs onto the new ALBs, but due to the limitation of the current CIDR block allocations, they cannot do seamlessly. We will need to revisit how their subnets are assigned currently, and how to create new subnets for growth. Parts of this will be addressed in the first phase.
4) They also are currently not able to send notifications to their customers with their current notification system, is want to explore AWS managed services in regard to messaging and notifications.
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 5x
Client Team = 2x
1) CloudFormation code for VPC/Network/EKS Cluster
2) Kubernetes configuration files with options for service-autoscaling and cluster autoscaling.
3) Integration with AWS Parameter Store
4) Deployment through AWS CodePipeline CI/CD.
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
The Customer would like to migrate their app to AWS. Currently the staging and prod environments are already containerized using Docker swarm. The Customer is currently using Jenkins for deployments. We will migrate the existing environment to AWS, setup a proper CI/CD pipeline with Gitlab, enable monitoring, and monitor the environment 24×7 for any issues. The customer will also like to migrate to Aurora as part of the migration.
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
To migrate BKJ’s Application Stack that is currently running on SoftLayer to AWS.
1) Containerization of all Services
2) Finish/Review Core infrastructure buildout for EKS
3) Monitoring, Logging and Additional Services
4) CodePipeline CI/CD for EKS
5) Rolling out new AWS Environment in Stage
6) Developing Migration Strategy for Production Workload
7) Production Migration – UI Applications
8) Production Migration – Database and CMS Applications
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 2x
Client Team = 1x
The client is looking for an AWS partner, their AWS spend is about 10k. The first step, the customer wants us to build a scalable CI/CD pipeline. Currently, a build environment is manually created and very error-prone. The customer wants the build environment which is scalable, at the same it needs to be isolated. The isolation will allow Customer to have third-party developers spin up the containerized environment; the customer has been wanting on implement this kind of CI/CD pipeline for a while. After the CI/CD, the customer wants us to help them to containerize all of applications.
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 2x
Layer 1 Team = 2x
This project is for developing a new deployment platform for Client’s API Service based on Elastic Kubernetes Service (EKS). The project will also extend the current Jenkins CI/CD Pipeline to do automated deployments on the new platform. During the course of this project, we will be adopting Infrastructure as Code Practice (IaC) using Terraform. The new Deployment Platform will have a) A uniform way to deploy all microservices currently running in the Client’s API Service suite.
- Options to use Blue-Green or Rolling deployments with minimal service disruption
- A well-defined process to add new services. We will deliver a new environment for Dev/Staging environment and will work with the Client to come up with a migration plan to move the current Production Workload to the new Deployment Platform.
TEAMS & RESOURCES INVOLVED:
Sales Team = 1x
Project Management Team = 1x
DevOps Team = 3x
Client Team = 3x
Layer 1 Team = 4x
