Taylor Shift's Ticket Shop

Projects Needs

Determine the services needed to match the following needs :

• Deploy Prestashop docker image from Docker Hub to AWS (-> Azure) and include a database (-> MySQL).
• Ensure the app is hosted and ready to handle a huge traffic. (Apache benchmark ?)
• Prioritize scalability and reliability.
• Provide README.md documentation.
• Estimate the base cost and variables from autoscale of the infrastructure.

Prerequisites

You must consider the ENVIRONMENT variable in the following configuration as your project environment. The following environment are accepted : dev, rec, prod. The terraform configuration will match the differents criteria of the infrastructure depending the chosen environment.

You must replace the environment value to match the environment you're deploying. This is made for automation using CI/CD and handle variables library.

Connect to AZ-CLI and select your subscription

# Login to Azure
az login

# Show the account 
az account show

# Set the right subscription key
az account set --subscription <my-subscription>

Add the subscription basic providers to Azure

az provider register --namespace Microsoft.Network
az provider register --namespace microsoft.support
az provider register --namespace Microsoft.SerialConsole
az provider register --namespace Microsoft.ResourceNotifications
az provider register --namespace Microsoft.ResourceGraph
az provider register --namespace Microsoft.Portal
az provider register --namespace Microsoft.MarketplaceOrdering
az provider register --namespace Microsoft.Features
az provider register --namespace Microsoft.CostManagement
az provider register --namespace Microsoft.Consumption
az provider register --namespace Microsoft.Commerce
az provider register --namespace Microsoft.ClassicSubscription
az provider register --namespace Microsoft.Billing
az provider register --namespace Microsoft.Authorization
az provider register --namespace Microsoft.ADHybridHealthService
az provider register --namespace Microsoft.Resources
az provider register --namespace Microsoft.Network
az provider register --namespace Microsoft.Compute
az provider register --namespace Microsoft.Advisor
az provider register --namespace Microsoft.ManagedIdentity
az provider register --namespace Microsoft.Kubernetes
az provider register --namespace Microsoft.ContainerService
az provider register --namespace Microsoft.ContainerInstance
az provider register --namespace Microsoft.ContainerRegistry
az provider register --namespace Microsoft.Storage
az provider register --namespace Microsoft.DBforMySQL
az provider register --namespace Microsoft.OperationalInsights
az provider register --namespace Microsoft.OperationsManagement

Create environment variables file inside the terraform folder : variables.tfvars (should not be pushed to repository, so add it to gitignore in real environment)

# For the terraform configuration
PROJECT_NAME="5hash"
ENVIRONMENT="dev"
LOCATION="northeurope"
RESOURCE_GROUPE_NAME="rg-5hash-dev-northeurope"
MYSQL_ADMIN_LOGIN    ="myloginsupinfo" # This is credentials and should not be push in real environment.
MYSQL_ADMIN_PASSWORD ="Mypassword100!" # This is credentials and should not be push in real environment.

Create the terraform file inside the terraform folder : backend.tfvars (should not be pushed to repository, so add it to gitignore in real environment)

resource_group_name  = "rg-5hash-dev-northeurope"
storage_account_name = "tfstate5hashdev"
container_name       = "tfstate"
key                  = "terraform.tfstate"

Deploy Terraform backend to Azure in storage account (default to westeurope because inavailable in northeurope)

Create the following environment variables matching your environment

# For the backend 
TF_CONTAINER_NAME=tfstate
TF_LOCATION=northeurope
TF_LOCATION_STORAGE=westeurope
ENVIRONMENT=dev
PROJECT_NAME=5hash
RESOURCE_GROUP_NAME=rg-$PROJECT_NAME-$ENVIRONMENT-$TF_LOCATION
TF_STORAGE_ACCOUNT_NAME=$TF_CONTAINER_NAME$PROJECT_NAME$(echo $ENVIRONMENT)nathan # We added a firstname to avoid an Azure subscription bug with student account

Those commands create the resource group in Azure and prepare a storage account to hold the shared tfstate of our environment.

# Create resource group
az group create --name $RESOURCE_GROUP_NAME --location $TF_LOCATION --tags project=$PROJECT_NAME environment=$ENVIRONMENT

# Create storage account (can be taken if another student subscript use it... bug azure)
az storage account create --resource-group $RESOURCE_GROUP_NAME --name $TF_STORAGE_ACCOUNT_NAME --location $TF_LOCATION_STORAGE --min-tls-version TLS1_2 --kind StorageV2 --sku Standard_LRS --encryption-services blob --allow-blob-public-access false --https-only true --tags project=$PROJECT_NAME environment=$ENVIRONMENT

# Create blob container 
az storage container create --name $TF_CONTAINER_NAME --account-name $TF_STORAGE_ACCOUNT_NAME

# Cleaning up the resource group and storage account
# az group delete --name $RESOURCE_GROUP_NAME --yes --no-wait
# az storage account delete --name $TF_STORAGE_ACCOUNT_NAME --yes

Start deploying

Terraform commands

# Enter the terraform folder
cd terraform

# Provision the infrastructure
terraform init -backend-config="backend.tfvars"
terraform plan -var-file="variables.tfvars" -out="plan.tfplan"
terraform apply "plan.tfplan"

# This command destroy the Terraform configuration
terraform destroy -var-file="variables.tfvars" -var-file="backend.tfvars"

Add images to Azure Container Registry

You must have Docker running for this part.

# Set the ACR_NAME as environment variable
ACR_NAME=acr5hashdevnortheurope

# Login to the registry
az acr login -n $ACR_NAME

# Build and Push the images from Docker Hub to the Azure Registry
az acr import --name $ACR_NAME --source docker.io/prestashop/prestashop:latest --image prestashop:latest

Create the configMap to add secrets and environment variables

You should create your files like this documentation precise it : https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/ We need a configMap inside each overlays folders (dev, rec, prod) in kubernetes configuration.

# Example
cat <<EOF >./kustomization.yaml
# this configMap should be added by the CI/CD pipeline
apiVersion: v1
kind: ConfigMap
metadata:
  name: prestashop-config
  namespace: app
data:
  port: "8080"
  db_user: "taylorShift@sqlserver-5hash-dev-northeurope"
  db_passwd: "Mypassword100!"
  db_name: "prestashopdbdev"
  db_server: "sqlserver-5hash-dev-northeurope.mysql.database.azure.com"
  admin_mail: "[email protected]"
  admin_passwd: "Mypassword100!"
  ps_install_auto: "1"
  ps_handle_dynamic_domain: "1"

EOF

Deploy the Kubernetes configuration with Kustomize

# Move to Kubernetes folder
cd kubernetes
# Set your environment variables if not already done
ENVIRONMENT=dev
RESOURCE_GROUP_NAME=rg-5hash-dev-northeurope
AKS_NAME=aks-5hash-dev-northeurope

# Get cluster credentials
az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $AKS_NAME --overwrite-existing

# Attach Cluster To ACR
az aks update -n $AKS_NAME -g $RESOURCE_GROUP_NAME --attach-acr $ACR_NAME

# Download the ingress-nginx chart

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update

# Deploy the ingress controller
helm install ingress-nginx ingress-nginx/ingress-nginx \
  --create-namespace --namespace app \
  --set controller.replicaCount=3  \
  --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz \
  --set controller.service.externalTrafficPolicy=Local
# OR
helm install ingress-nginx ingress-nginx/ingress-nginx --create-namespace --namespace app --set controller.replicaCount=3 --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz --set controller.service.externalTrafficPolicy=Local

# To uninstall ingress-nginx use this command :
helm uninstall ingress-nginx -n app

# Apply Kubernetes configuration with Kustomization
kubectl apply -k ./overlays/$ENVIRONMENT

# Delete configuration
kubectl delete -k  ./overlays/$ENVIRONMENT

Access the Cluster Public IP

# Get ingress controller public IP
kubectl --namespace app get services ingress-nginx-controller | awk '{print $4}' | tail -n 1

Azure Cost Estimation / Month

Each deployed resource, except for Azure Role Assignment, incurs charges. It's crucial to estimate the cost of a month of service as accurately as possible for our different environments. The estimates are based on the maximum capacities of the machines; actual costs will likely be slightly lower as the server doesn't always need to be at its maximum power.

Azure Container Registry

The Azure Container Registry remains the same across our various environments. With a basic level, it will cost us €4.72 per environment per month.

Azure Kubernetes Cluster

The Azure Kubernetes Cluster is significantly more expensive. Our production and staging infrastructure plans for the deployment of several virtual machines to handle increased traffic, while development will only need one. We can use up to 5 VMs in production (and 3 in staging) costing €31 each.
At their minimum usage, the production and staging machines use only 2 VMs, lowering the price by €90 per month (the final price will be less impacted, as billing is based on usage, we might spend 50% of the time with 2 VMs and 50% with 5, which would cost us the average of the two prices). Deploying these VMs requires 1 Kubernetes cluster at €69. An additional 32GB storage disk for €1.45 should be added to this price.

Azure Database for MySQL

We use different machines depending on the environment. In development and staging, we have chosen a single Gen5 2vcore server at €0.182 per hour. For more performance in production, we use a Gen5 4vcore machine at €0.364 per hour. These machines cost €132.90 and €265.81 respectively. Additionally, €0.60 per month should be added for 5GB of storage and €1.04 for 10GB of storage backups.

Cost Summary

Environment	Role Assignment	Container Registry	Kubernetes Cluster	MySQL Database	Total
Development	€0	€4.72	€225.72	€267	€497.44
Staging	€0	€4.72	€225.72	€134.54	€364.98
Production	€0	€4.72	€101.51	€134.54	€240.77
Total	€0	€14.16	€552.95	€536.08	€1103.19

Our three environments will cost an estimated maximum of €1103 per month, with €0 in initial fees.