UNIVERSITY OF WEST ATTICA
SCHOOL OF ENGINEERING
DEPARTMENT OF COMPUTER ENGINEERING AND INFORMATICS
Cloud Computing and Services
Vasileios Evangelos Athanasiou
Student ID: 19390005
Georgios Theocharis
Student ID: 19390283
Supervisor: Apostolos Anagnostopoulos, Special Technical Laboratory Staff
Athens, June 2024
This project was created for the cloud computing lab and provides a virtual lab environment using Docker. Its purpose is to facilitate the development and management of various applications by providing many features and services. This README file briefly describes the project, its features, and the services used.
| Section | Title | Description |
|---|---|---|
| assign | Assignment | Contains assignments and tasks |
| src | Source Code | All source code files and implementations |
The Docker project has the following features:
- Individual Networks: Each virtual lab creates its own network, allowing secure communication between containers.
- Data Preservation: Provides storage for persistent data management, ensuring that data is preserved even if containers are restarted or stopped.
- Automatic Service Startup and Shutdown: Use shell scripts to automatically run and shutdown services without manual intervention.
- Service Isolation: Each service runs in a separate container. WordPress is the main application, while MySQL manages the database. phpMyAdmin provides a graphical interface to manage the MySQL database.
- Resource Management: Configure resources for optimal allocation and prevent memory problems. Docker Compose files define resource limits for all containers.
The Docker project uses the following services:
- WordPress: A popular content management system for creating and managing websites.
- MySQL: A popular open-source relational database management system.
- phpMyAdmin: A graphical interface for MySQL database management, simplifying database administration.
The WordPress container is the main page for the project, allowing the creation and management of web pages.
Configuration
To implement the WordPress container, we use two Docker Compose files: docker-compose.yaml and docker-compose.override.yaml.
docker-compose.override.yaml
version: '3.8'
services:
wordpress:
container_name: wordpress
ports:
- '8080:80'
restart: always
volumes:
- /wp_data:/var/www/html
environment:
WORDPRESS_DB_HOST: database
WORDPRESS_DB_USER: wordpress
WORDPRESS_DB_PASSWORD: apostolos
WORDPRESS_DB_NAME: wordpress
deploy:
resources:
limits:
cpus: '0.10'
memory: 500M
reservations:
cpus: '0.05'
memory: 50M
networks:
- vlab_network
volumes:
data:
driver: local- container_name: Specify the name of the WordPress container as "wordpress".
- ports: We map port 8080 on the host to port 80 on the container, allowing access to WordPress via http://localhost:8080.
- restart: We ensure that the container restarts automatically if it stops or encounters an error.
- volumes: We create a volume named "/wp_data" and mount it in the container's "/var/www/html" directory. This allows WordPress files to be stored outside the container, preserving the data even if the container is stopped or removed.
- environment: The environment variables are used to specify the connection between WordPress and the MySQL container.
- deploy: We set the resource limits for the container, including CPU and memory limitations.
- network: We connect the WordPress container to the "wordpressNetwork" network.
docker-compose.yaml
version: '3.8'
services:
wordpress:
image: wordpress:latest
networks:
vlab_network:
name: vlab_network
driver: bridge- We run the WordPress service using the WordPress Docker Image, which is pulled from Docker Hub with the latest tag if the image does not already exist on the machine.
- With "networks" we connect the WordPress container to the "vlab_network" network. We name the network separately in the networks section, specifying its name as "vlab_network" and the driver as "bridge"
Together, these Docker Compose files configure and deploy the WordPress container, ensuring that it is connected to the specified network and has access to the necessary resources and volumes.
The MySQL container hosts the database used by WordPress.
Configuration
To implement the MySQL container, we use two Docker Compose files: docker-compose.yaml and docker-compose.override.yaml.
docker-compose.override.yaml
version: '3.8'
services:
database:
container_name: mysql_database
ports:
- '3306:3306'
restart: always
volumes:
- /db_data:/var/lib/mysql
environment:
MYSQL_ROOT_PASSWORD: apostolos
MYSQL_DATABASE: wordpress
MYSQL_USER: wordpress
MYSQL_PASSWORD: apostolos
deploy:
resources:
limits:
cpus: '0.10'
memory: 500M
reservations:
cpus: '0.05'
memory: 50M
networks:
- vlab_network
volumes:
data:
driver: local- container_name: Specify the name of the MySQL container as "mysql".
- ports: We map the host port 3306 to the container port 3306, allowing access to the database through the MySQL client.
- restart: We ensure that the container restarts automatically if it stops or encounters an error.
- volumes: We create a volume named "/db_data" and mount it in the container's "/var/lib/mysql" directory. This allows the database data to be stored outside the container, preserving the data even if the container is stopped or removed.
- environment: The environment variables are used to specify the database parameters.
- deploy: We set the resource limits for the container, including CPU and memory constraints.
- network: We connect the MySQL container to the "vlab_network" network.
docker-compose.yaml
version: '3.8'
services:
database:
image: mysql:5.7
networks:
vlab_network:
driver: bridge
external: true- We run the MySQL service using the MySQL Docker Image, which is pulled from Docker Hub with the latest tag if the image does not already exist on the machine.
- With "networks" we connect the MySQL container to the "vlab_network" network. We define the network name separately in the networks section, specifying its name as "vlab_network" and the driver as "bridge"
Together, these Docker Compose files configure and deploy the MySQL container, ensuring that it is connected to the specified network and has access to the necessary resources and volumes.
The phpMyAdmin container provides a graphical interface for managing the MySQL database.
Configuration
To implement the phpMyAdmin container, we use two Docker Compose files: docker-compose.yaml and docker-compose.override.yaml.
docker-compose.override.yaml
version: '3.8'
services:
phpmyadmin:
container_name: phpMyAdmin_CLI
ports:
- '8081:80'
restart: always
environment:
PMA_HOST: database
PMA_USER: wordpress
PMA_PASSWORD: apostolos
deploy:
resources:
limits:
cpus: '0.10'
memory: 200M
reservations:
cpus: '0.05'
memory: 50M
networks:
- vlab_network
volumes:
data:
driver: local- container_name: Specify the name of the phpMyAdmin container as "phpmyadmin".
- ports: We map port 8081 on the host to port 80 on the container, allowing access to phpMyAdmin via http://localhost:8081.
- restart: We ensure that the container restarts automatically if it stops or encounters an error.
- environment: With the environment variables we specify the connection parameters to the MySQL container.
- deploy: We set the resource limits for the container, including CPU and memory constraints.
- network: We connect the phpMyAdmin container to the "vlab_network" network.
docker-compose.yaml
version: '3.8'
services:
phpmyadmin:
image: phpmyadmin/phpmyadmin
networks:
vlab_network:
driver: bridge
external: true- We run the phpMyAdmin service using the phpMyAdmin Docker Image, which is pulled from Docker Hub with the latest tag if the image does not already exist on the machine.
- With "networks" we connect the phpMyAdmin container to the "vlab_network" network. We define the network name separately in the networks section, specifying its name as "vlab_network" and the driver as "bridge"
Together, these Docker Compose files configure and deploy the phpMyAdmin container, ensuring that it is connected to the specified network and has access to the necessary resources and volumes.