/examples

Amalgam8 Microservice Fabric - Samples and Demos

Primary LanguageShellApache License 2.0Apache-2.0

Amalgam8 Examples

Sample microservice-based applications and local sandbox environment for Amalgam8.

An overview of Amalgam8 can be found at www.amalgam8.io.

[//]: # (Note: This is an unstable branch. If you are experimenting with Amalgam8 for the first time, please use the stable branch (git checkout -b 0.1.0 origin/0.1.0) and use this README from the stable branch.)

Overview

This project includes a number of Amalgam8 sample programs, scripts and a preconfigured environment to allow you to easily run, build, and experiment with the provided samples, in several environments. In addition, the scripts are generic enough that you can easily deploy the samples to other environments as well.

The following samples are available for Amalgam8:

  • Helloworld is a single microservice app that demonstrates how to route traffic to different versions of the same microservice
  • Bookinfo is a multiple microservice app used to demonstrate and experiment with several Amalgam8 features

Setup

Before running the samples, you need to setup the requisite environment.

  • Vagrant sandbox: The repository's root directory includes a Vagrant file that provides an environment with everything needed to run, and build, the samples (Go, Docker, Kubernetes, Amalgam8 CLI w/ Gremlin SDK already installed. Depending on the runtime environement you want to try, using it may be the easiest way to get Amalgam8 up and running.

  • Custom setup: If you are not using the vagrant environment, then install the following pre-requisites:

    • Amalgam8 python CLI
    sudo pip install git+https://github.com/amalgam8/a8ctl

  • Development Mode: If you'd like to also be able to change and compile the code, or build the images, refer the Developer Instructions.

Deployment Options

Amalgam8 platform can be deployed on the following container runtimes and PaaS environments. Pick an option below and follow the instructions in the respective section.

Amalgam8 with Docker - local environment

The installation steps below have been tested with the Vagrant sandbox environment (based on Ubuntu 14.04) as well as with Docker for Mac Beta (v1.11.2-beta15 or later). These steps have not been tested on Docker for Windows Beta.

The following instructions assume that you are using the Vagrant environment. Where appropriate, environment specific instructions are provided.

  1. Clone the Amalgam8 examples repo and then start the Vagrant environment (or install and setup the equivalent dependencies manually)

    git clone https://github.com/amalgam8/examples

cd examples
vagrant up
vagrant ssh

cd $GOPATH/src/github.com/amalgam8/examples

  2. Start the multi-tenant control plane and a tenant

    Start the control plane services (registry and controller) by running the following command:

    docker/run-controlplane-docker.sh start

    The above command also creates a tenant named "local" in the control plane.

  3. Before we start using the a8ctl command line utility, we need to set the A8_CONTROLLER_URL and the A8_REGISTRY_URL environment variables to point to the addresses of the controller and the registry respectively.

    • If you are running the Docker setup using the Vagrant file in the examples folder or if you are running Docker locally (on Linux or Docker for Mac Beta)
    export A8_CONTROLLER_URL=http://localhost:31200
export A8_REGISTRY_URL=http://localhost:31300
    • If you are running Docker using the Docker Toolbox with Docker Machine, then set the environment variables to the IP address of the VM created by Docker Machine. For example, assuming you have only one Docker Machine running on your system, the following commands will setup the appropriate environment variables:
    export A8_CONTROLLER_URL=`docker-machine ip`
export A8_REGISTRY_URL=`docker-machine ip`

  4. Confirm everything is working with the following command:

    a8ctl service-list

    The command shouldn't return any services, since we haven't started any yet, but if it returns the following empty table, the control plane services (and CLI) are working as expected:

    +---------+-----------+
| Service | Instances |
+---------+-----------+
+---------+-----------+

  5. Instead of using the a8ctl CLI commands, you can optionally use the Amalgam8 prototype console UI to view and/or manage services. To start the console server, run the following command:

    docker-compose -f docker/console.yaml up -d

    To access the UI, point your browser to http://localhost:31000/. Same as a8ctl service-list in the previous step, you should currently see an empty list of services.

  6. Deploy the API gateway

    Every tenant application should have an API Gateway that provides a single user-facing entry point for a microservices-based application. You can control the Amalgam8 gateway for different purposes, such as version routing, red/black deployments, canary testing, resiliency testing, and so on. The Amalgam8 gateway is a simple lightweight Nginx server that is controlled by the control plane.

    To start the API gateway, run the following command:

    docker-compose -f docker/gateway.yaml up -d

    Usually, the API gateway is mapped to a DNS route. However, in our local standalone environment, you can access it at port 32000 on localhost. If you are using Docker directly, then the gateway should be accessible at http://localhost:32000 or http://dockermachineip:32000.

  7. Confirm that the API gateway is running by accessing http://localhost:32000 from your browser. If all is well, you should see a simple Welcome to nginx! page in your browser.

    Note: You only need one gateway per tenant. A single gateway can front more than one application under the tenant at the same time, so long as they don't implement any conflicting microservices.

  8. Follow the instructions for the sample that you want to run.

    (a) helloworld sample

    • Start the helloworld application:
    docker-compose -f docker/helloworld.yaml up -d
docker-compose -f docker/helloworld.yaml scale helloworld-v1=2
docker-compose -f docker/helloworld.yaml scale helloworld-v2=2
    docker-compose -f docker/helloworld.yaml kill
docker-compose -f docker/helloworld.yaml rm -f

    (b) bookinfo sample

    • Start the bookinfo application:
    docker-compose -f docker/bookinfo.yaml up -d
    docker-compose -f docker/bookinfo.yaml kill
docker-compose -f docker/bookinfo.yaml rm -f

    When you are finished, shut down the gateway and control plane servers by running the following commands:

    docker/cleanup.sh

Amalgam8 with Kubernetes - local environment

The following setup has been tested with Kubernetes v1.2.3.

  1. Clone the Amalgam8 examples repo and then start the Vagrant environment (or install and setup the equivalent dependencies manually)

    git clone git@github.com:amalgam8/examples.git

cd examples
vagrant up
vagrant ssh

cd $GOPATH/src/github.com/amalgam8/examples
export A8_CONTROLLER_URL=http://localhost:31200
export A8_REGISTRY_URL=http://localhost:31300

    Start Kubernetes, by running the following command:

    sudo kubernetes/install-kubernetes.sh

    Note: If you stopped a previous Vagrant VM and restarted it, Kubernetes might be started already, but in a bad state. If you have problems, first start by removing previously deployed services and uninstalling Kubernetes with the following commands:

    kubernetes/cleanup.sh
sudo kubernetes/uninstall-kubernetes.sh

  2. Start the local control plane services (registry and controller) by running the following commands:

    kubernetes/run-controlplane-local-k8s.sh start

  3. Run the following command to confirm the control plane is working:

    a8ctl service-list

    The command shouldn't return any services, since we haven't started any yet, but if it returns the following empty table, the control plane servers (and CLI) are working as expected:

    +---------+-----------+
| Service | Instances |
+---------+-----------+
+---------+-----------+

    Note: If this did not work, it's probabaly because the image download and/or service initialization took too long. This is usually fixed by waiting a minute or two, and then running kubernetes/run-controlplane-local-k8s.sh stop and then repeating the previous step.

    You can also access the registry at http://localhost:31300 from the host machine (outside the Vagrant box), and the controller at http://localhost:31200 . To access the control plane details of tenant local, access http://localhost:31200/v1/tenants/local from your browser.

  4. Instead of using the a8ctl CLI commands, you can optionally use the Amalgam8 prototype console UI to view and/or manage services. To start the console server, run the following command:

    kubectl create -f kubernetes/console.yaml

    To access the UI, point your browser to http://localhost:31000/. Same as a8ctl service-list in the previous step, you should currently see an empty list of services.

  5. Run the API Gateway with the following commands:

    kubectl create -f kubernetes/gateway.yaml

    Usually, the API gateway is mapped to a DNS route. However, in our local standalone environment, you can access it at port 32000 on localhost.

  6. Confirm that the API gateway is running by accessing http://localhost:32000 from your browser. If all is well, you should see a simple Welcome to nginx! page in your browser.

    Note: You only need one gateway per tenant. A single gateway can front more than one application under the tenant at the same time, so long as they don't implement any conflicting microservices.

  7. Visualize your deployment using Weave Scope by accessing http://localhost:30040 . Click on Pods tab. You should see a graph of pods depicting the connectivity between them. As you create more apps and manipulate routing across microservices, the graph changes in real-time.

  8. Deploying sample apps: follow the instructions for the sample that you want to run.

    (a) helloworld sample

    (b) bookinfo sample

  9. When you are finished, shut down the gateway and control plane servers by running the following commands:

    kubernetes/cleanup.sh

Amalgam8 with Marathon/Mesos - local environment

The following setup has been tested with Marathon 0.15.2 and Mesos 0.26.0.

  1. Clone the Amalgam8 examples repo

    git clone git@github.com:amalgam8/examples.git

cd examples

  2. Edit the Vagrant file in the examples folder. Uncomment the line starting with config.vm.network "private_network", ip: "192.168.33.33/24".

  3. Start the Vagrant environment

    vagrant up
vagrant ssh

cd $GOPATH/src/github.com/amalgam8/examples
export A8_CONTROLLER_URL=http://192.168.33.33:31200
export A8_REGISTRY_URL=http://192.168.33.33:31300

  4. The run-controlplane-marathon.sh script in the marathon folder sets up a single host (local) marathon/mesos cluster (based on Holiday Check's mesos-in-the-box) and launches the controller and the registry as apps in the marathon framework.

    marathon/run-controlplane-marathon.sh start

    From your browser, confirm that the Marathon dashboard is accessible at http://192.168.33.33:8080 and the Mesos dashboard at http://192.168.33.33:5050

    Verify that the controller and registry are running via the Marathon dashboard.

  5. Launch the API Gateway

    marathon/run-component.sh gateway start

  6. Confirm that the API gateway is running by accessing the http://localhost:32000 from your browser. If all is well, you should see a simple Welcome to nginx! page in your browser.

    Note: You only need one gateway per tenant. A single gateway can front more than one application under the tenant at the same time, so long as they don't implement any conflicting microservices.

  7. Follow the instructions for the sample that you want to run.

    (a) helloworld sample

    • Start the helloworld application:
    marathon/run-component.sh helloworld start
    marathon/run-component.sh helloworld stop

    (b) bookinfo sample

    • Start the bookinfo application:
    marathon/run-component.sh bookinfo start
    marathon/run-component.sh bookinfo stop

    When you are finished, shut down the gateway and control plane servers by running the following commands:

    marathon/cleanup.sh

Amalgam8 on IBM Bluemix

To run the Bookinfo sample app on Bluemix, follow the instructions below. If you are not a Bluemix user, you can register at bluemix.net.

  1. Download Docker 1.10 or later, CF CLI 6.12.0 or later, Bluemix CLI 0.3.3 or later, jq 1.5 or later, and the Amalgam8 python CLI 0.1.8

  2. Login to Bluemix and initialize the containers environment using bluemix login and bluemix ic init

  3. Create Bluemix routes to be mapped to the controller/bookinfo gateway, e.g.:
    cf create-route myspace mybluemix.net -n myamalgam8-controller
    cf create-route myspace mybluemix.net -n myamalgam8-bookinfo

  4. Configure the examples/bluemix/.bluemixrc file to your environment variable values

    • BLUEMIX_REGISTRY_NAMESPACE should be your Bluemix registry namespace, e.g. bluemix ic namespace-get
    • BLUEMIX_REGISTRY_HOST should be the Bluemix registry hostname. This needs to be set only if you're targeting a Bluemix region other than US-South.
    • CONTROLLER_HOSTNAME should be the (globally unique) Bluemix route to be mapped to the controller
    • BOOKINFO_ROUTE should be the (globally unique) Bluemix route to be mapped to the bookinfo gateway
    • ROUTES_DOMAIN should be the domain used for the Bluemix routes (e.g., mybluemix.net)
    • ENABLE_SERVICEDISCOVERY determines whether to use the Bluemix-provided Service Discovery instead of the A8 registry. When set to false, you can deploy your own customized A8 registry (not yet implemented).
    • ENABLE_MESSAGEHUB determines whether to use the Bluemix-provided Message Hub. When set to false, the A8 proxies will use a slower polling algorithm to get changes from the A8 Controller.
      Note that the Message Hub Bluemix service is not a free service, and using it might incur costs.

  5. Deploy the A8 controlplane by running bluemix/deploy-controlplane.sh. Verify that the controller is running by bluemix ic groups and checking if the amalgam8_controller group is running.

  6. Configure the Amalgam8 CLI according to the routes defined in .bluemixrc. For example

    export A8_CONTROLLER_URL=https://mya8controller.mybluemix.net

  7. Run the following command to confirm the control plane is working:

    a8ctl service-list

    The command shouldn't return any services, since we haven't started any yet, but if it returns the following empty table, the control plane servers (and CLI) are working as expected:

    +---------+-----------+
| Service | Instances |
+---------+-----------+
+---------+-----------+

  8. Deploy the API Gateway and the Bookinfo app by running bluemix/deploy-bookinfo.sh

  9. Confirm the microservices are running

    a8ctl service-list

    Should produce the following output:

    +-------------+---------------------+
| Service     | Instances           |
+-------------+---------------------+
| productpage | v1(1)               |
| ratings     | v1(1)               |
| details     | v1(1)               |
| reviews     | v1(1), v2(1), v3(1) |
+-------------+---------------------+

  10. Follow the Bookinfo sample app instructions for the rest of the demo. When you reach the part where it instructs you to open, in your browser, the bookinfo application at http://localhost:32000/productpage/productpage, make sure to change "http://localhost:32000" to the value of the BOOKINFO_URL environment variable that you defined in your .bluemixrc file.

    Note: The Bluemix version of the bookinfo sample app does not yet support running the Gremlin recipe. We are working on integrating the app with the Bluemix Logmet services, to enable support for running Gremlin recipes.

  11. When you are finished, shut down the gateway and control plane servers by running the following commands:

    ./kill-bookinfo.sh
./kill-controlplane.sh

Amalgam8 on Google Cloud Platform

  1. Setup Google Cloud SDK on your machine

  2. Setup a cluster of 3 nodes

  3. Launch the control plane services

    kubernetes/run-controlplane-gcp.sh start

  4. Locate the node where the controller is running and assign an external IP to the node if needed

  5. Initialize the first tenant. The run-controlplane-gcp.sh script stores the JSON payload to initialize the tenant in /tmp/tenant_details.json.

    cat /tmp/tenant_details.json|curl -H "Content-Type: application/json" -d @- http://ControllerExternalIP:31200/v1/tenants

  6. Deploy the API gateway

    kubectl create -f kubernetes/gateway.yaml

    Obtain the public IP of the node where the gateway is running. This will be the be IP at which the sample app will be accessible.

  7. Visualizing your deployment with Weave Scope

    kubectl create -f 'https://scope.weave.works/launch/k8s/weavescope.yaml' --validate=false

    Once weavescope is up and running, you can view the weavescope dashboard on your local host using the following commands

    kubectl port-forward $(kubectl get pod --selector=weavescope-component=weavescope-app -o jsonpath={.items..metadata.name}) 4040

    Open http://localhost:4040 on your browser to access the Scope UI. Click on Pods tab. You should see a graph of pods depicting the connectivity between them. As you create more apps and manipulate routing across microservices, the graph changes in real-time.

  8. You can now deploy the sample apps as described in Deploying sample apps section under the local Kubernetes installation instructions. Remember to replace the IP address localhost with the public IP address of the node where the gateway service is running on the Google Cloud Platform.

Contributing

Contributions and feedback are welcome! Proposals and pull requests will be considered. Please see the CONTRIBUTING.md file for more information.