This repo contains all the work required by the DevOps team. We aim to apply the DevOps methodology standards which helps to
increase realibility, reduce development lifecycly time, and increase effeciency via automation.
As opposed to different software projects, DevOps can not be a stand-alone project so all files here represnt automation scripts for doing certain tasks to deployment. Some scripts will even need to be located inside the other repos (especially dockerization)
This folder contains all the work that is required for deploying and applying on a single instance on the cloud (Clinet-Server).
The folder contains scripts used for provisioning two instances. The first one is the master node that will monitor and apply pipelines for our server. And the second one is the actual server that runs the application images, accepts traffic, handle requests, and store data (this one will be provisioned from the master node as it is responsible for monitoring)
1 - Create a .env inside the terraform/slave directory file to store the needed credentials
2 - Go to your aws account and create an IAM user with root priviliges (maybe all these priviliges are not really needed but for future development)
3 - Store them in the following names
'''
AWS_ACCESS_KEY_ID="anaccesskey"
AWS_SECRET_ACCESS_KEY="asecretkey"
'''
4 - Create an EC2 key-value pair named (slave) on aws and download it inside the terraform directory under the name slave.pem (note that pem is required as we work with openssh)
5 - The downloaded file is required when you want to ssh into your server by running
'''
chmod 400 slave.pem
ssh -i "slave.pem" ubuntu@{YOUR_Public_IPv4_DNS}
'''
6 - Run the host.sh script to do all the required steps for you to provision all resources
'''
chmod u+x host.sh
./host.sh (may ask you for sudo password so, run it inside a sudo user)
'''
1 - For the Slave Configuration you need to login to your azure account first.
2 - log in the instance like mentioned in step 5 and type sudo reboot to add docker to the sudo users
3 - go to the IP:8080 to access jenkins
4 - go to the IP:9090 to access prometheus
5 - You will find the private key for the slave instance on azure in the directory Terraform/slave so you can ssh to it like step 5
6 - you will also need to login to each instance and type az login to login to your azure account (in case of using azure container registry you will need to login to it as well)