demo/

directory
v0.9.2-rc.1 Latest Latest
Warning

This package is not in the latest version of its module.

 Go to latest Published: Aug 17, 2021 License: Apache-2.0

README

How to Run the OSM Automated Demo

System Requirements

  • MacOS, Linux or WSL2 on Windows
  • GCC
  • Go version 1.15.7 or higher
  • Kubectl version 1.15 or higher
  • Docker CLI
    • on a Debian based GNU/Linux system: sudo apt-get install docker
    • on a macOS use brew install docker or alternatively visit Docker for Mac
    • on Windows visit Docker for Windows
  • Watch
    • brew install watch on macOS

Prerequisites

  1. Clone this repo on your workstation

  2. Setup .env environment variable file

    • From the root of the repository run make .env
    • It is already listed in .gitignore so that anything you put in it would not accidentally leak into a public git repo. Refer to .env.example in the root of this repo for the mandatory and optional environment variables.

  3. Provision access to a Kubernetes cluster. Any certified conformant Kubernetes cluster (version 1.15 or higher) can be used. Here are a couple of options:

    • Option 1: Local kind cluster
      • Install kind
        • brew install kind on macOS
      • Provision a local cluster and registry in Docker: make kind-up
    • Option 2: A Kubernetes cluster - use an already provisioned cluster config, either in the default location ($HOME/.kube/config) or referenced by the $KUBECONFIG environment variable.
      • Set CTR_REGISTRY in your .env file to a container registry you have permission to push and pull from.
      • Ensure you are logged into the container registry using: docker login <registry url>

    We will use images from Docker Hub. Ensure you can pull these containers using: docker pull openservicemesh/osm-controller

OpenShift

If you are running the demo on an OpenShift cluster, there are additional prerequisites.

  1. Install the oc CLI.
  2. Set DEPLOY_ON_OPENSHIFT=true in your .env file.
    • This enables privileged init containers and links the image pull secrets to the service accounts. Privileged init containers are needed to program iptables on OpenShift.

Run the Demo

From the root of this repository execute:

./demo/run-osm-demo.sh
Observability and tracing

By default:

  • Prometheus is not deployed by the demo script. To enable prometheus deployment, set the variable DEPLOY_PROMETHEUS in your .env file to true.
  • Grafana is not deployed by the demo script. To enable Grafana deployment, set the variable DEPLOY_GRAFANA in your .env file to true.
  • Jaeger is not deployed by the demo script. To enable Jaeger deployment, set the variable DEPLOY_JAEGER in your .env file to true. The section on Jaeger below describes tracing with Jaeger.
This script will:

  • compile OSM's control plane (cmd/osm-controller), create a separate container image and push it to the workstation's default container registry (See ~/.docker/config.json)

  • build and push demo application images described below

  • create the following topology in Kubernetes:

    Graph

    • bookbuyer and bookthief continuously issue HTTP GET requests against bookstore to buy books and github.com to verify egress traffic.
    • bookstore is a service backed by two servers: bookstore-v1 and bookstore-v2. Whenever either sells a book, it issues an HTTP POST request to the bookwarehouse to restock.

  • applies SMI traffic policies allowing bookbuyer to access bookstore-v1 and bookstore-v2, while preventing bookthief from accessing the bookstore services

  • finally, a command indefinitely watches the relevant pods within the Kubernetes cluster

To see the results of deploying the services and the service mesh - run the tailing scripts:

  • the scripts will connect to the respective Kubernetes Pod and stream its logs
  • the output will be the output of the curl command to the bookstore service and the count of books sold, and the output of the curl command to github.com to demonstrate access to an external service
  • a properly working service mesh will result in HTTP 200 OK response code for the bookstore service with ./demo/tail-bookbuyer.sh along with a monotonically increasing counter appearing in the response headers, while ./demo/tail-bookthief.sh will result in HTTP 404 Not Found response code for the bookstore service. When egress is enabled, HTTP requests to an out-of-mesh host will result in a HTTP 200 OK response code for both the bookbuyer and bookthief services. This can be automatically checked with go run ./ci/cmd/maestro.go

View Mesh Topology with Jaeger

When the demo is run with DEPLOY_JAEGER set to true in your .env file, OSM will install a Jaeger pod. To configure all participating Envoys to send spans to this Jaeger instance, you must additionally enable tracing using:

kubectl patch meshconfig osm-mesh-config -n osm-system -p '{"spec":{"observability":{"tracing":{"enable":true,"address": "jaeger.osm-system.svc.cluster.local","port":9411,"endpoint":"/api/v2/spans"}}}}'  --type=merge

Jaeger's UI is running on port 16686 and can be viewed by forwarding port 16686 from the Jaeger pod to the local workstation. In the ./scripts directory we have included a helper script to find the Jaeger pod and forward the port: ./scripts/port-forward-jaeger.sh. After running this script, navigate to http://localhost:16686/ to examine traces from the various applications.

Demo Web UI

The Bookstore, Bookbuyer, and Bookthief apps have simple web UI visualizing the number of requests made between the services.

To expose web UI ports of all components of the service mesh the local workstation use the following helper script: /scripts/port-forward-all.sh

Deleting the kind cluster

When you are done with the demo and want to clean up your local kind cluster, just run the following.

make kind-reset

Directories

Path Synopsis
cmd
bookbuyer
bookstore
bookthief
bookwarehouse
common
tcp-client
package main implements a TCP client that sends TCP data to a TCP echo server and prints the response.
 package main implements a TCP client that sends TCP data to a TCP echo server and prints the response.
tcp-echo-server
package main implements a TCP echo server that echoes back the TCP client's request as a part of its response.
 package main implements a TCP echo server that echoes back the TCP client's request as a part of its response.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL
go.dev uses cookies from Google to deliver and enhance the quality of its services and to analyze traffic. Learn more.