Scaling Kubernetes Microservices on OpenStack With TOSCA Orchestration Pt II of II

OpenStack Austin Summit | OpenStack Orchestration | TOSCA Cloud Orchestration | Kubernetes Docker | Kubernetes Orchestration | Cloud Automation | Kubernetes Cluster
In my previous post, I described orchestrating a hybrid architecture that included Kubernetes, Kubernetes hosted microservices, and a cloud hosted database, all running on Openstack. That post described how everything was deployed, but left the implementation of post deployment dynamism to the imagination. This post finishes the story.

Try the Kubernetes Orchestration as a Service Tool today!  Go


We resume our story with the deployment in the following configuration:

  • Openstack cloud platform.
  • A Kubernetes master and node server on separate VMs.
  • Nodejs running behind a Kubernetes service endpoint in Kubernetes in a pod with a Diamond collector.
  • A MongoDb instance (single node) on a separate VM.

The very simple Diamond metric collector is feeding TCP connection metrics to a RabbitMQ queue which is consumed by both InfluxDb and Riemann on the Cloudify server. Influxdb is storing the metrics for querying. Riemann is responsible for triggering actions based on the metrics stream.
The objective is to scale Kubernetes microservices based on metrics from containers emanating from those microservices (as provided by the previously mentioned Diamond collector).

High Level Overview of Solution

Since the goal is to scale Cloudify deployed Kubernetes microservices, the rest of this post will focus on the essentials for that goal:

  • Gathering metrics from containers that don’t contain Cloudify agents.
  • Creating a workflow to scale microservices on Kubernetes.
  • Defining a Riemann policy to execute the Kubernetes scaling workflow.
  • Configuring the blueprint properly to facilitate the preceding.

container metrics

Summary: Gathering Metrics From Containers

Kubernetes defines scaling in units called “pods” (which are groups of containers on a single host), and a “replication controller” which scales and maintains pods. Pods share the same network namespace, so on a given pod, the experience for a container is similar to conventional processes on a host (i.e. two containers can “see” each other). Our microservice of interest is a Nodejs server and webapp. In order to monitor it, a separate container was created just hosting the Diamond collector that will monitor it. Together these are assembled into a pod and deployed into Kubernetes. When the pod starts, the collector only sees it’s companion in the pod and send the metrics to the Cloudify server (and ultimately Riemann).
kubernetes scale

Summary: The Workflow to Scale Microservices

The Kubernetes CLI has a simple scale command for scaling up replication controllers. The Kubernetes scale workflow simply logs into to the Kubernetes master node and executes the CLI to scale the replication controller as required. The Kubernetes CLI simply allows a user to set the number of replicas, which isn’t really enough for what we need, so the workflow has the ability to specify a scaling increment (e.g. +1 +2 etc…).

Summary: Defining the Riemann Policy

The Riemann policy observes the arriving metrics from the various Diamond containers and maintains an adjustable sliding window of values. It also keeps track internally of the number of containers reporting metrics. It takes the sum of the sliding window and divides by the host count, and triggers the scale workflow on the Cloudify server when the threshold parameter is breached. It’s also parameterized to define scale down behavior as well as scale up, and permits a “cooldown” period to avoid thrashing.

Summary: Configuring the Blueprint

In the blueprint, as described in the Cloudify docs, a policy type is defined that points to the actual Riemann policy code, references the Kubernetes scaling workflow, and has a list of the blueprint nodes that will be affected (just the Kubernetes node in this case).

Some Detailed Discussion of the Solution

Sending Metrics from Kubernetes Pods

As mentioned in the overview, the approach for metrics gathering is to define a container that gathers and transmits the metrics and forwards them to the Cloudify server. In practice, this means essentially putting a portion of what would normally be considered the Cloudify agent in a container in a pod. Running Diamond collectors is really quite simple and not the subject of this post. However, some of the mechanics of submitting metrics to Cloudify outside the “normal” path may be of interest.
Submitting metrics to Cloudify means “writing a message to a RabbitMQ topic on the Cloudify server”. Among other things, that means the container (and ultimately the Diamond configuration) have to be informed of the IP address of the Cloudify server. Kubernetes native descriptors allow the definition of environment variables that get passed to containers at deploy time (as described in my previous post). Overriding those environment variables with runtime information was one of the duties of the Kubernetes plugin, and the reason for this:

Note the %{management_ip%} token. It grabs the IP address of the manager and sets it in the Kubernetes descriptor for the Diamond container. Once that is done Diamond can connect and start sending.

More Metric Sending Details

The Diamond service sends metrics to Cloudify in a JSON map/dictionary. A Diamond service consists of one of more “collectors” and one or more “handlers”. The collectors measure the metrics, and the handler push them to particular receiving systems. The handler is what assembles the JSON that gets pushed to the RabbitMQ broker on the server. In order to do so successfully, it must use the proper keys in the map and send to the appropriate routing key. In the case of Cloudify the topic is ‘cloudify-monitoring’, and the routing key is the deployment id. The topic is fixed in the container configuration, but the deployment id is passed in a similar manner as the manager ip was:

The Kubernetes Scaling Workflow

To scale our microservice/replication controller inside of Kubernetes, we need a custom workflow. The default scaling workflow will increase the number of instances of a given node in a blueprint. Of course, we don’t want to launch an entire new Kubernetes cluster when our Nodejs server runs out of connections, we simply want to command Kubernetes to scale the number of instances of the pod we deployed. As mentioned earlier,
Kubernetes supplies an easy means of doing so through its CLI. Something like:
kubectl scale --replicas=<count> rc <replication-controller-name>
So ultimately, we just need our workflow ssh to the Kubernetes master node and run kubectl. Except, when we get notified to “scale”, we won’t be given the number of nodes to scale to, we’ll just be informed that scaling is needed. The workflow can be parameterized for the scale increment:

Note the “amount” property. The workflow interprets this as either an absolute number (unlikely to need that), or an increment (signed integer). Note also the ssh information is required for the Kubernetes node, and the node name of the Kubernetes master (or proxy), along with the actual microservice node name (in case more than one microservice were running). To hande increments, a simple algorithm that reads the current replica count, increments it and then sets it, is used.

Defining the Policy

The scaling policy, executed by Riemann, is Clojure code that tracks the number of hosts reporting, maintains a sliding window of metrics, and invokes the Cloudify supplied function process-policy-triggers, which has the effect of commanding
the manager to invoke the Kubernetes scale workflow. Policies in Cloudify (and TOSCA of course) are defined first by defining a policy type. The policy type used here is:

Note that we’re pointing to some code (scale.clj), and defining a bunch of parameters. When Cloudify creates a deployment, one of the things it does is start up a Riemann core dedicated to processing events from the deployment. This Riemann core is given a configuration file (also Clojure code) that includes the defined policies, along with code to connect to RabbitMQ properly and define various utility functions (like process-policy-triggers, among other things. Before it copies
the policy code into the Riemann config file, it runs it through the Jinja2 template processor, substituting the properties for configured values (and doing whatever Jinja stuff you might like). So an excerpt of the policy looks like the following (note the property references:

Note the call to process-policy-triggers. It is guarded by a list of conditions, including that the cooldown period is not in effect, that the scaling limit has not been reached, and that the scaling threshold has indeed been breached. Also note the riemann.index/update call after a scale has been commanded. It simply writes a synthetic event into Riemann’s index (by default a hash map), and sets the time to live to be the cooldown period as specified in the blueprint. Riemann evicts events from the index when they expire, so we can use that to implement the cooldown. Also note the token. The value of this property in the blueprint is actual Clojure code, either < for scale up behavior, or > for scale down behavior.


Thus ends the journey to a Cloudify managed hybrid cloud deployment including Kubernetes, Kubernetes deployed microservices, and external services outside of Kubernetes. Note also that the standard scale workflow in Cloudify works for Kubernetes itself, so in reality the suite of blueprints included can scale not only Kubernetes microservices, but Kubernetes itself. Watch this video to see the autoscaling in action. The code is on github. As always, comments are welcome.
Stay tuned to this channel for more OpenStack, containers, security, and NFV posts throughout the month as we prepare for OpenStack Austin!


    Leave a Reply

    Your email address will not be published. Required fields are marked *

    Back to top