[cf-lattice] Fwd: [lattice-release] v0.6.0

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

[cf-lattice] Fwd: [lattice-release] v0.6.0

David Wadden
Phew! We spent the last few weeks reworking our cluster internals and build process to bring you the best Lattice yet.  Functionally, this is not a big release, but the changes give us a noticeably more stable cluster (less random errors around startup), and open up a lot of possibilities for future functionality.

There are a number of breaking changes, most notably the lack of support on DigitalOcean, Google Compute Engine or Openstack.  These platforms don't have the same ability to publish public base images like Vagrant boxes on Atlas (Vagrant Cloud) or AMIs on AWS.  We're currently prioritizing whether/how soon we can bring back support for those platforms, and what it might look like (packer null builder or maybe bake-your-own images since those platforms support private base images).

If you use Lattice (and especially if you use one of the "temporarily discontinued" platforms), please take the time and fill out our survey at http://goo.gl/forms/z33xBoLaeQ.  We'd love your feedback on what Lattice does for you and what platform(s) you're using (or would like to).

Quick rundown:
  • Cluster
  • CLI
    • Provided by cluster, then ltc sync updates itself from cluster
    • Supports setting user context by USER directive for docker images
    • Define HTTP routes to fully-qualified domains or context paths
We updated a lot of our documentation to go with the cluster changes, but there are still some broken links and outdated contents.  We're working towards open-sourcing the website contents themselves, but for now if you want to fix something on on lattice.cf, we encourage you to open a Github issue.

Full release notes are included below.

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

--
David Wadden
Product Manager
Pivotal Software, Inc.

---------- Forwarded message ---------
From: davidwadden <[hidden email]>
Date: Thu, Oct 22, 2015 at 3:33 PM
Subject: [lattice-release] v0.6.0
To: cloudfoundry-incubator/lattice-release <[hidden email]>


Help us help you, we'd love to hear your thoughts and suggestions on our survey!
Your answers will help us understand how you use Lattice and inform upcoming feature work.

Breaking Changes

Complete retooling of Lattice build and cluster deployment [##2124074]

The Lattice build process has been completely retooled to create images that are fully configured with all Lattice + Diego microservices at build time. We use packer-bosh to bake the Diego, Loggregator, and Routing BOSH releases into the Lattice base image. This ensures the configurations never get out of sync with the mainline CF versions. Thus, we greatly improve cluster stability. Users do not and will not need to understand or use BOSH to deploy Lattice.

New Features

Δ indicates a breaking change.

Cluster

CLI

  • ltc should be downloadable from the Lattice cluster [#102877664]
  • ltc sync updates itself from the cluster [#102877664] [#105668046] [#102482290]
  • Vendor ltc dependencies with submodules instead of Godeps [#101770536]
  • ltc launch-droplet no longer accepts --working-dir [#104935318] (Δ)
  • ltc build-droplet and ltc launch-droplet no longer use privileged containers [#104921458]
  • ltc create --privileged starts a docker image with a privileged container [#105355654]
  • ltc supports improved user namespacing [#105324808] [#105328688]
    • ltc create --user specifies the user context of a docker app [#104917574]
    • Next, uses the USER directive from docker metadata [#104917678]
    • Lastly, defaults to "root" [#104918540]
  • Routing enhancements for ltc
    • The below changes apply to ltc create, ltc launch-droplet, and ltc update
    • Define multple routes by passing the --http-route or --tcp-route flag multiple times [#105631892] (Δ)
    • HTTP/TCP routes determine default container port for single port apps [#105635660]
    • #104, #137: Custom domains in routes [#93628052] [#96562554]
    • #217: Use of context path routes with Lattice [#105301140]
    • Retire ltc update-routes [#104177142] (Δ)

Bug Fixes

  • Modify docker image examples to app(s) start properly [#105069548] [#105881880]
  • Postgres docker image requires ltc create --privileged to start [#105071050]

Interestings

CI / Packaging

Documentation

Known Issues

  • TCP routes are not deleted when route is removed / app(s) are stopped #208 [##1940024]
  • Two apps with same TCP route defined will round-robin between two separate apps [#105929084]


View it on GitHub.

Loading...