devops-automation-deployement-project

THIS A PROJECT FOR DEVOPS DEPLOYEMENT AND AUTOMATION

MICROSERVICES USED

LOGIN MICROSERVICE (nodejs ---> to assure auth with jwt)
SONG API MICROSERVICE (nodejs ---> will send the music info like the image and song title)
MUSIC FRONTEND (frontend exposed to the internet as ui for all users)

ARCHITECTURE

THE DATABASE IS EXTERNAL (MONGO DB ATLAS)

ALL THE MICROSERVICES ARE DOCKERIZED

There is images for tests environments
There is images for dev environments
There is images for prod environments

INFRASTRUCTURE

WORKED ON AZURE AS WELL AS ON KIND (locally)

LOCALLY THERE IS THE CONFIGURATION FOR THE CLUSTER USING KIND

.main/infrastructure/cluster-config

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  kubeadmConfigPatches:
  - |
    kind: InitConfiguration
    nodeRegistration:
      kubeletExtraArgs:
        node-labels: "ingress-ready=true"
  extraPortMappings:
  - containerPort: 80
    hostPort: 80
    protocol: TCP
  - containerPort: 443
    hostPort: 443
    protocol: TCP

DEVOPS TOOLS (METRICS - TRACES - LOGS)

METRICS ( HOST METRICS : SEMATEXT AGENT )

METRICS ( APP METRICS : PROMETHEUS + GRAFANA (PULL BASED) COUNTERS )

WE CAN PORTFORAWRD TO THE PROMETHEUS BY CREATING A TUNNEL (IF WE FOLLOW THE GOOD PRACTICIES WE MUST ENABLE RBAC OR SET PERMISSION KEY )

GRAFANA VISUALISATION FOR PROMETHEUS

LOGS ( AGENT DATADOG ) + (WINSTON FROM THE APPLICATION CLIENT)

STRUCTURE OF LOGS

TRACES ( DATADOG and OPENTELEMETRY ) auto instrumented

HELM SHARDS

WE USED 3 HELM SHARDS :

MUSIC APP
PROMETHEUS ( to SET OUR VALUES WHEN INSTALLING PROMETHEUS HELM + SAVED THE OUTPUT )
DATADOGS ( to SET OUR VALUES WHEN INSTALLING DATA DOG )

WE USE ALSO HELM SHARDS TO CHANGE BETWEEN DIFFERENT ENVIRONMENTS:

DEV
TEST
PROD

WE ALSO USE SHARDS VALUE TO PICK BETWEEN BETWEEN BLUE AND GREEN AS LABELS

BECAUSE USED BLUE GREEN ROLL OUT ALL AT ONCE (TRIED argoproj.io/v1alpha1)

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  name: rollout-bluegreen
spec:
[...] # this part of the template is identical to a regular Deployment
  strategy:
    blueGreen: 
      activeService: rollout-bluegreen-active
      previewService: rollout-bluegreen-preview
      autoPromotionEnabled: false ```

THE BLUE GREEN DEPLOYEMENT DIDN'T WORK OUT

AUTOMATIC PROVISIONING

TERRAFORM MICRO STACKS (2 stacks to create cluster and to install helm sharts in the clusters itself)

WE ALSO AUTOMATED THE PROVISION OF A STAND ALONE VIRTUAL MACHINE THAT'S SUPPOSED TO RUN A PYTHON SCRIPT TO SCRAPE ALL SONGS DATA (NAME ARTIST IMAGE)

WE ALSO AUTOMATED THE CONFIGURATION OF THAT MACHIBE USING ANSIBLE PLAYBOOK TO INSTALL ALL DEPENDANCIES FOR PYTHON AND RUNNING THE SCRIPT

- name: WebserverPlaybook
  hosts: webserver
  become: true
  tasks:
    - name: Install BeautifulSoup python package
      ansible.builtin.pip:
        name: beautifulsoup4
    - name: Install pandas python package
      ansible.builtin.pip:
        name: pandas
    - name: Install request python package
      ansible.builtin.pip:
        name: requests
    - name: Copy the script
      template:
        src: ./server/scrape-script.py
        dest: /home/{{ ansible_user }}/scrape-script.py
    - name: launch script  
      ansible.builtin.command: python3 /home/{{ ansible_user }}/scrape-script.py
    - name: log script  
      ansible.builtin.command: echo "this script has finished"
      ```

aminfelah / devops-automation-deployement-project