On behalf of the Lattice AND the Routing teams, I am pleased to announce
v0.4.0 of Lattice!
We've taken some time off to convert our pipelines from GoCD to Concourse,
and the Routing team has integrated the TCP Router into Lattice. This is
something we've been looking forward to, please check it out and give us
The full release notes are included below.
I'm also happy to announce David Wadden as the new Product Manager for
Lattice. David's been the anchor of the project team for the last 6 months,
so he's well-equipped to step into the position. Please welcome in his new
role, and thank you David!
- If you think you've found a bug, please file a GitHub issue.
- If you have a contribution, we'd be happy to give you feedback via a
- You can track our prioritized queue of work at:
Marco Nicosia && David Wadden
---------- Forwarded message ----------
From: Marco Nicosia <notifications(a)github.com>
Date: Fri, Sep 4, 2015 at 11:12 AM
Subject: [lattice] v0.4.0
To: cloudfoundry-incubator/lattice <lattice(a)noreply.github.com>
Beginning with v0.4.1, direct access to Lattice cells will be restricted to
private addresses within the cluster.
Introducing TCP Router
TCP Router is a collection of components that balances traffic across one
or more instances of an application. Unlike gorouter, tcp-router balances
traffic other than HTTP, such as mysql, redis, or mongodb. Using ltc, a
user defines a route from an external port on the Lattice brain to an
exposed port on the application container. Under the hood, tcp-emitter
regularly updates HAProxy <http://www.haproxy.org/> with the TCP routes
defined on the Lattice cluster.
- #172 <https://github.com/cloudfoundry-incubator/lattice/pull/172> #182
<https://github.com/cloudfoundry-incubator/lattice/pull/191>: Merge TCP
Router functionality [#101089176
- [image: :+1:] Big thanks to the Routing team for their
contributions! @shalako <https://github.com/shalako> @fordaz
<https://github.com/fordaz> @atulkc <https://github.com/atulkc>
- --routes no longer works on ltc create and ltc launch-droplet.
- Use the --http-routes flag to define HTTP routes for an app. [
#100758692 <https://www.pivotaltracker.com/story/show/100758692>] [
- --http-routes takes a comma-delimited set of ROUTE:CONTAINER_PORT
- This is reversed from --routes (*breaking change*)
- New --tcp-routes flag takes comma-delimited set of
- Multiple TCP routes can route to same container port. [#101697408
- ltc update changes HTTP and/or TCP routes for a running application. [
- Replaces ltc update-routes (will be removed in a future release).
- ltc status and ltc list show TCP routes [#100258924
New Distribution Bundles
With the recent conversion to Concourse <http://concourse.ci/> as our CI
platform, we took the opportunity to change the way we distribute Lattice
-- no more git checkout; vagrant up. Starting with *v0.4.0*, we distribute
a *bundle* (links below) that contains ltc along with the vagrant/terraform
files needed to launch Lattice.
- Distribute Lattice via bundles [#101458202
- ltc target --s3 uses an S3 bucket as the droplet store [#100236758
- Allows multiple developers to share droplets
- Persists droplets across subsequent Lattice deployments
- ltc create --monitor-command uses a custom healthcheck command [
- ltc target times out when a connection to the blob store hangs [
- No longer downloads RootFS at provision-time on Vagrant and AWS [
#101844068 <https://www.pivotaltracker.com/story/show/101844068>] [
- Upgraded base Ubuntu image to 14.04.3 [#102162900
how to diagnose and resolve multiple vagrant instances running [
- ci.lattice.cf shows the current build status [#101284204
- As part of our migration to Concourse, we now track master. Moving
forward, please submit any PRs against the *master* branch. [#101834808
View it on GitHub