[cf-lattice] Fwd: [lattice] v0.4.0

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Fwd: [lattice] v0.4.0

Marco Nicosia
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 feedback!

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!

As always:
  - 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 Pull Request.
  - You can track our prioritized queue of work at: http://bit.ly/lattice-tracker

--
  Marco Nicosia && David Wadden


---------- Forwarded message ----------
From: Marco Nicosia <[hidden email]>
Date: Fri, Sep 4, 2015 at 11:12 AM
Subject: [lattice] v0.4.0
To: cloudfoundry-incubator/lattice <[hidden email]>


v0.4.0

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 with the TCP routes defined on the Lattice cluster.

  • #172 #182 #191: Merge TCP Router functionality [#101089176] [#101699282] [#102296358]
  • --routes no longer works on ltc create and ltc launch-droplet.
  • Use the --http-routes flag to define HTTP routes for an app. [#100758692] [#100436212]
    • --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 EXTERNAL_PORT:CONTAINER_PORT
  • Multiple TCP routes can route to same container port. [#101697408]
  • ltc update changes HTTP and/or TCP routes for a running application. [#98240702]
    • Replaces ltc update-routes (will be removed in a future release).
  • ltc status and ltc list show TCP routes [#100258924] [#100258722]

New Distribution Bundles

With the recent conversion to Concourse 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.

New Features

  • ltc target --s3 uses an S3 bucket as the droplet store [#100236758] [#100237448]
    • Allows multiple developers to share droplets
    • Persists droplets across subsequent Lattice deployments
  • ltc create --monitor-command uses a custom healthcheck command [#91461922]

Usability Fixes

  • ltc target times out when a connection to the blob store hangs [#101164182]
  • No longer downloads RootFS at provision-time on Vagrant and AWS [#101844068] [#101844098]
  • Upgraded base Ubuntu image to 14.04.3 [#102162900]
  • Document how to diagnose and resolve multiple vagrant instances running [#101992188]

For Developers

  • 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.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] Re: [cf-dev] Fwd: [lattice] v0.4.0

James Bayer
great release team!

i love the new tcp router functionality. this will unlock many workloads in the platform and i love that lattice gives us a way to use it early before the full cloud foundry feature is ready.

although confusing at first why i was getting the error message on the main repo when i did the standard workflow to update, i now understand the release bundles. i would encourage you to put something in the Vagrantfile provision script in the root of the repo that says "Please use the new release bundle approach as of v0.4.0 and higher as documented here: [link]".

On Fri, Sep 4, 2015 at 12:30 PM, Marco Nicosia <[hidden email]> wrote:
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 feedback!

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!

As always:
  - 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 Pull Request.
  - You can track our prioritized queue of work at: http://bit.ly/lattice-tracker

--
  Marco Nicosia && David Wadden


---------- Forwarded message ----------
From: Marco Nicosia <[hidden email]>
Date: Fri, Sep 4, 2015 at 11:12 AM
Subject: [lattice] v0.4.0
To: cloudfoundry-incubator/lattice <[hidden email]>


v0.4.0

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 with the TCP routes defined on the Lattice cluster.

  • #172 #182 #191: Merge TCP Router functionality [#101089176] [#101699282] [#102296358]
  • --routes no longer works on ltc create and ltc launch-droplet.
  • Use the --http-routes flag to define HTTP routes for an app. [#100758692] [#100436212]
    • --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 EXTERNAL_PORT:CONTAINER_PORT
  • Multiple TCP routes can route to same container port. [#101697408]
  • ltc update changes HTTP and/or TCP routes for a running application. [#98240702]
    • Replaces ltc update-routes (will be removed in a future release).
  • ltc status and ltc list show TCP routes [#100258924] [#100258722]

New Distribution Bundles

With the recent conversion to Concourse 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.

New Features

  • ltc target --s3 uses an S3 bucket as the droplet store [#100236758] [#100237448]
    • Allows multiple developers to share droplets
    • Persists droplets across subsequent Lattice deployments
  • ltc create --monitor-command uses a custom healthcheck command [#91461922]

Usability Fixes

  • ltc target times out when a connection to the blob store hangs [#101164182]
  • No longer downloads RootFS at provision-time on Vagrant and AWS [#101844068] [#101844098]
  • Upgraded base Ubuntu image to 14.04.3 [#102162900]
  • Document how to diagnose and resolve multiple vagrant instances running [#101992188]

For Developers

  • 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.





--
Thank you,

James Bayer
Loading...