[![Build Status](](

# gorouter

This repository contains the source code for a Go implementation of the Cloud
Foundry router.

This router is now used on, replacing the old implementation.

## Summary

The original router can be found at cloudfoundry/router. The original router is
backed by nginx, that uses Lua code to connect to a Ruby server that -- based
on the headers of a client's request -- will tell nginx whick backend it should
use. The main limitations in this architecture are that nginx does not support
non-HTTP (e.g. traffic to services) and non-request/response type traffic (e.g.
to support WebSockets), and that it requires a round trip to a Ruby server for
every request.

The Go implementation of the Cloud Foundry router is an attempt in solving
these limitations. First, with full control over every connection to the
router, it can more easily support WebSockets, and other types of traffic (e.g.
via HTTP CONNECT). Second, all logic is contained in a single process,
removing unnecessary latency.

## Getting started

The following instructions may help you get started with gorouter in a
standalone environment.

### Setup

export GOPATH=~/go # or wherever
export PATH=$GOPATH/bin:$PATH


mkdir -p src/
  cd src/
  git clone

go get -v ./src/

go get

### Running Tests

We are using Gocheck, to run tests

go env
go get -v ./...
go build -v ./...
go test -v ./...

# just run tests whose names match Registry
go test -v ./... -gocheck.f=Registry

# run the tests for only the registry package
go test -v ./registry

If tests are failing with ` .../gorouter/router_test.go: too many open files`
you should increase your max file descriptor ulimit

ulimit -n 1024

### Start

# Start NATS server in daemon mode
gnatsd &

# Start gorouter

### Usage

When gorouter starts, it sends `router.start`. This message contains an
interval that other components should then send `router.register` on. If they
do not send a `router.register` for an amount of time considered "stale" by the
router, the routes are pruned. The default "staleness" is 2 minutes.

The format of this message is as follows:

  "id": "some-router-id",
  "hosts": [""],
  "minimumRegisterIntervalInSeconds": 5

If a component comes online after the router, it must make a NATS request
called `router.greet` in order to determine the interval. The response to this
message will be the same format as `router.start`.

The format of route updates are as follows:

  "host": "",
  "port": 4567,
  "uris": [
  "tags": {
    "another_key": "another_value",
    "some_key": "some_value"

Such a message can be sent to both the `router.register` subject to register
URIs, and to the `router.unregister` subject to unregister URIs, respectively.

$ nohup ruby -rsinatra -e 'get("/") { "Hello!" }' &
$ nats-pub 'router.register' '{"host":"","port":4567,"uris":["",""],"tags":{"another_key":"another_value","some_key":"some_value"}}'
Published [router.register] : '{"host":"","port":4567,"uris":["",""],"tags":{"another_key":"another_value","some_key":"some_value"}}'
$ curl

### Instrumentation

Gorouter provides `/varz` and `/healthz` http endpoints for monitoring.

The `/routes` endpoint returns the entire routing table as JSON. Each route has an associated array of host:port entries.

All of the endpoints require http basic authentication, credentials for which
can be acquired through NATS. The `port`, `user` and password (`pass` is the config attribute) can be explicitly set in the gorouter.yml config
file's `status` section.

  port: 8080
  user: some_user
  pass: some_password

Example interaction with curl:

curl -vvv "http://someuser:somepass@"
* About to connect() to port 8080 (#0)
*   Trying
* connected
* Connected to ( port 8080 (#0)
* Server auth using Basic with user 'someuser'
> GET /routes HTTP/1.1
> Authorization: Basic c29tZXVzZXI6c29tZXBhc3M=
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
> Host:
> Accept: */*
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Mon, 25 Mar 2013 20:31:27 GMT
< Transfer-Encoding: chunked

## Logs

The router's logging is specified in its YAML configuration file, in a [steno configuration format](
The meanings of the router's log levels are as follows:

* `fatal` - An error has occurred that makes the current request unservicable.
Examples: the router can't bind to its TCP port, a CF component has published invalid data to the router.
* `warn` - An unexpected state has occurred. Examples: the router tried to publish data that could not be encoded as JSON
* `info`, `debug` - An expected event has occurred. Examples: a new CF component was registered with the router, the router has begun
to prune routes for stale droplets.

## Contributing

Please read the [contributors' guide](

Imports 9 package(s)


Test imports 4 package(s)