Skip to content

Commit

Permalink
Work on README.md. Added images.
Browse files Browse the repository at this point in the history
  • Loading branch information
southsidedean committed Mar 18, 2024
1 parent eacb8e3 commit b7e5057
Show file tree
Hide file tree
Showing 13 changed files with 39 additions and 29 deletions.
68 changes: 39 additions & 29 deletions eliminate-cross-zone-traffic-hazl/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -708,6 +708,10 @@ Let's take a look at traffic flow _without **HAZL** enabled_ in **Buoyant Cloud*

![Buoyant Cloud: Topology](images/orders-no-hazl-bcloud.png)

![Grafana: HAZL Dashboard](images/orders-no-hazl-grafana.png)

![Deployments / HPA](images/orders-no-hazl-deployments-hpa.png)

We can see...

### Enable High Availability Zonal Load Balancing (HAZL)
Expand Down Expand Up @@ -736,6 +740,12 @@ Let's take a look at what traffic looks like with **HAZL** enabled, using **Buoy

![Buoyant Cloud: Topology](images/orders-hazl-bcloud.png)

![Grafana: HAZL Dashboard](images/orders-hazl-grafana.png)

![Deployments / HPA](images/orders-hazl-deployments-hpa.png)

We can see...

### Increase Orders Traffic in `zone-east`

A popular sitcom
Expand All @@ -756,13 +766,13 @@ watch -n 1 kubectl get deploy,hpa -n orders

Let's take a look at what the increased traffic looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-increased-east-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-increased-east-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-increased-east-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Increase Orders Traffic in `zone-central`

Expand All @@ -784,13 +794,13 @@ watch -n 1 kubectl get deploy,hpa -n orders

Let's take a look at what the increased traffic looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-increased-central-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-increased-central-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-increased-central-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Increase Orders Traffic in `zone-west`

Expand All @@ -812,13 +822,13 @@ watch -n 1 kubectl get deploy,hpa -n orders

Let's take a look at what the increased traffic looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-increased-west-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-increased-west-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-increased-west-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Increase Latency in `zone-central`

Expand Down Expand Up @@ -861,13 +871,13 @@ kubectl rollout restart -n orders deploy warehouse-chicago

Let's take a look at what the increased latency looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic in response to increased latency.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-increased-latency-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-increased-latency-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-increased-latency-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Take the `warehouse-chicago` Deployment Offline in `zone-central`

Expand All @@ -889,13 +899,13 @@ watch -n 1 kubectl get deploy,hpa -n orders

Let's take a look at what the increased traffic looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-chicago-offline-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-chicago-offline-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-chicago-offline-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Bring the `warehouse-chicago` Deployment Back Online and Remove Latency

Expand Down Expand Up @@ -929,13 +939,13 @@ watch -n 1 kubectl get deploy,hpa -n orders

Let's take a look at what the service restoration looks like in **Buoyant Cloud**. This will give us a more visual representation of the effect of **HAZL** on our traffic.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-chicago-restored-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-chicago-restored-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-chicago-restored-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

### Reset the Orders Application

Expand All @@ -955,14 +965,14 @@ watch -n 1 kubectl get deploy,hpa -n orders

If we give things a minute to settle back down, we should see all traffic back in zone and request rates back to 50.

![Buoyant Cloud: Topology](images/orders-hazl-increased-load-bcloud.png)
![Buoyant Cloud: Topology](images/orders-hazl-app-reset-bcloud.png)

![Grafana: Dashboard](images/orders-hazl-increased-load-grafana.png)
![Grafana: HAZL Dashboard](images/orders-hazl-app-reset-grafana.png)

We can see...
![Deployments / HPA](images/orders-hazl-app-reset-deployments-hpa.png)

<<Explain what we're seeing here>>
We can see...

## Summary: Deploying the Orders Application With High Availability Zonal Load Balancing (HAZL)

<<Summarize the entire thing here. Bullet points?>>
Summarize the entire thing here. Bullet points?
Binary file modified eliminate-cross-zone-traffic-hazl/images/orders-hazl-bcloud.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 comments on commit b7e5057

Please sign in to comment.