- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Ujian Tengah Semester - Ujian Tengah Semester - ADRIAN EVAN NURZATNA
Lab = GSP007 - Set Up Network and HTTP Load Balancers
Tugas : Cloud Computing
Topik : Ujian Tengah Semester
Lab : Ujian Tengah Semester
Dosen Pengampu : apt. Anrie Suryaningrat S.Si, M.T.I.
I'm using AI summarization for testing
Executive Summary
Business Objective:
In modern cloud environments, relying on a single server to handle application traffic creates a single point of failure and limits scalability. The goal of this lab is to demonstrate how to achieve high availability, fault tolerance, and improved application performance by distributing incoming network traffic across multiple servers.
High-Level Outcome:
By the end of the lab, you deploy a Network Load Balancer that routes external user traffic efficiently across a pool of web servers. This ensures that if one server goes down or becomes overwhelmed, the load balancer automatically redirects users to healthy servers, keeping the application online and responsive without any manual intervention.
Technical Summary
Architecture Overview:
The lab focuses on deploying a regional, external, passthrough Layer 4 (TCP/UDP) Network Load Balancer. It routes incoming traffic based on IP address, port, and protocol to a target pool of backend Compute Engine virtual machines (VMs) running Apache web servers.
Key GCP Resources Used:
- Compute Engine: For provisioning the backend virtual machines (VMs).
- Cloud Load Balancing: Specifically configuring a Target Pool and a Forwarding Rule for L4 load balancing.
- VPC Firewalls: To allow external HTTP traffic to reach the backend instances.
- Cloud Shell / Cloud SDK (gcloud): Used as the primary CLI tool to provision and configure the infrastructure.
Step-by-Step Breakdown:
1. Set Region and Zone: Configure the default compute region and zone using gcloud config to ensure all subsequent resources are spun up in the correct location.
2. Provision Backend VMs: Create three separate e2-small Compute Engine instances (www1, www2, www3). A bash startup script is injected via metadata to automatically install Apache, restart the service, and write a custom index page identifying the specific server name.
3. Configure Firewall Rules: Create a VPC firewall rule (network-lb-tag) allowing incoming TCP traffic on port 80 (HTTP) so the web servers can receive requests.
4. Set Up the Health Check: Deploy a legacy HTTP health check (basic-check) so the load balancer can continuously monitor the health of the backend VMs and stop sending traffic to unresponsive ones.
5. Create the Target Pool: Group the three web server instances into a Target Pool and attach the HTTP health check to it.
6. Create the Forwarding Rule: Deploy a forwarding rule that serves as the frontend IP address of the load balancer. This rule listens for external traffic and forwards it to the Target Pool.
7. Verify Traffic Distribution: Use curl to send continuous requests to the forwarding rule's external IP address to verify that traffic is being evenly distributed across www1, www2, and www3.
#undira #cloudcomputing #skillboost #cloudcomputing #googlecloud
Видео Ujian Tengah Semester - Ujian Tengah Semester - ADRIAN EVAN NURZATNA канала VILATERIAS
Tugas : Cloud Computing
Topik : Ujian Tengah Semester
Lab : Ujian Tengah Semester
Dosen Pengampu : apt. Anrie Suryaningrat S.Si, M.T.I.
I'm using AI summarization for testing
Executive Summary
Business Objective:
In modern cloud environments, relying on a single server to handle application traffic creates a single point of failure and limits scalability. The goal of this lab is to demonstrate how to achieve high availability, fault tolerance, and improved application performance by distributing incoming network traffic across multiple servers.
High-Level Outcome:
By the end of the lab, you deploy a Network Load Balancer that routes external user traffic efficiently across a pool of web servers. This ensures that if one server goes down or becomes overwhelmed, the load balancer automatically redirects users to healthy servers, keeping the application online and responsive without any manual intervention.
Technical Summary
Architecture Overview:
The lab focuses on deploying a regional, external, passthrough Layer 4 (TCP/UDP) Network Load Balancer. It routes incoming traffic based on IP address, port, and protocol to a target pool of backend Compute Engine virtual machines (VMs) running Apache web servers.
Key GCP Resources Used:
- Compute Engine: For provisioning the backend virtual machines (VMs).
- Cloud Load Balancing: Specifically configuring a Target Pool and a Forwarding Rule for L4 load balancing.
- VPC Firewalls: To allow external HTTP traffic to reach the backend instances.
- Cloud Shell / Cloud SDK (gcloud): Used as the primary CLI tool to provision and configure the infrastructure.
Step-by-Step Breakdown:
1. Set Region and Zone: Configure the default compute region and zone using gcloud config to ensure all subsequent resources are spun up in the correct location.
2. Provision Backend VMs: Create three separate e2-small Compute Engine instances (www1, www2, www3). A bash startup script is injected via metadata to automatically install Apache, restart the service, and write a custom index page identifying the specific server name.
3. Configure Firewall Rules: Create a VPC firewall rule (network-lb-tag) allowing incoming TCP traffic on port 80 (HTTP) so the web servers can receive requests.
4. Set Up the Health Check: Deploy a legacy HTTP health check (basic-check) so the load balancer can continuously monitor the health of the backend VMs and stop sending traffic to unresponsive ones.
5. Create the Target Pool: Group the three web server instances into a Target Pool and attach the HTTP health check to it.
6. Create the Forwarding Rule: Deploy a forwarding rule that serves as the frontend IP address of the load balancer. This rule listens for external traffic and forwards it to the Target Pool.
7. Verify Traffic Distribution: Use curl to send continuous requests to the forwarding rule's external IP address to verify that traffic is being evenly distributed across www1, www2, and www3.
#undira #cloudcomputing #skillboost #cloudcomputing #googlecloud
Видео Ujian Tengah Semester - Ujian Tengah Semester - ADRIAN EVAN NURZATNA канала VILATERIAS
Комментарии отсутствуют
Информация о видео
7 ч. 30 мин. назад
00:09:42
Другие видео канала




















