We're pleased to announce Lattice v0.5.0! We've finished adding SSH
functionality and Lattice runs behind most proxies. Also, `terraform
apply` is no longer quite so bandwidth-hungry, it runs faster now and works
from low-bandwidth network links.

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.
dwadden(a)pivotal.io

---------- Forwarded message ---------
From: davidwadden <notifications(a)github.com>
Date: Fri, Oct 2, 2015 at 3:08 PM
Subject: [lattice] v0.5.0
To: cloudfoundry-incubator/lattice <lattice(a)noreply.github.com>


New Features

- #205 <https://github.com/cloudfoundry-incubator/lattice/issues/205>:
Terraform cells download lattice.tgz directly at provision-time [
#104137996 <https://www.pivotaltracker.com/story/show/104137996>]
- terraform apply can now be run from low-bandwidth network
connections
- Diego upgraded from 0.1398.0
<https://github.com/cloudfoundry-incubator/diego-release/releases/tag/0.1398.0>
to 0.1424.1
<https://github.com/cloudfoundry-incubator/diego-release/releases/tag/0.1424.1>
[#100656516 <https://www.pivotaltracker.com/story/show/100656516>] [
#103211906 <https://www.pivotaltracker.com/story/show/103211906>]
- Improve proxy support <http://lattice.cf/docs/proxy/> for Lattice [
##2088022 <https://www.pivotaltracker.com/epic/show/2088022>] [#103746258
<https://www.pivotaltracker.com/story/show/103746258>]
- Droplets created following vagrant up with proxy enabled use
cluster proxy configuration [#103533536
<https://www.pivotaltracker.com/story/show/103533536>]
- ltc works behind a "not strict" proxy (not Squid
<http://www.squid-cache.org/>) to connect to an external Lattice
cluster [#103737106
<https://www.pivotaltracker.com/story/show/103737106>]
- Validated CF buildpacks <https://docs.cloudfoundry.org/buildpacks/>
respect proxy configuration [#100512640
<https://www.pivotaltracker.com/story/show/100512640>]
- ltc ssh <http://lattice.cf/docs/ltc/#ltc-ssh> has reached feature
parity with Diego SSH <https://www.pivotaltracker.com/epic/show/1869002>
[##2051878 <https://www.pivotaltracker.com/epic/show/2051878>]
- Supports port forwarding with or without interactive shell [
#101709060 <https://www.pivotaltracker.com/story/show/101709060>] [
#102907420 <https://www.pivotaltracker.com/story/show/102907420>]
- Detects whether to allocate a PTY, -T disables PTY allocation [
#101710922 <https://www.pivotaltracker.com/story/show/101710922>] [
#101710892 <https://www.pivotaltracker.com/story/show/101710892>]
- Restores PTY from "raw" to "sane" mode following error or TERM
signal [#104210274
<https://www.pivotaltracker.com/story/show/104210274>]

Bug Fixes

- Changes to ltc visualize --graphical
- #209 <https://github.com/cloudfoundry-incubator/lattice/pull/209>:
Cell labels are populated from CellID value in Diego instead of
sequencer [#104439866
<https://www.pivotaltracker.com/story/show/104439866>]
- Cells are sorted properly (i.e., cell-2 before cell-11) [#93577238
<https://www.pivotaltracker.com/story/show/93577238>]
- Cell names are not prefixed with namespace on Google Compute Engine
<https://cloud.google.com/compute/> [#104658746
<https://www.pivotaltracker.com/story/show/104658746>]
- #204 <https://github.com/cloudfoundry-incubator/lattice/issues/204>:
Update out-of-date manual install instructions
<http://lattice.cf/docs/manual-install/> [#104094016
<https://www.pivotaltracker.com/story/show/104094016>]

Interestings

- Changes to ltc status <http://lattice.cf/docs/ltc/#ltc-status>
- Prints instance summary by default, --detailed gives details [
#104235428 <https://www.pivotaltracker.com/story/show/104235428>]
- Displays the RootFS and Monitor configuration [#104058110
<https://www.pivotaltracker.com/story/show/104058110>] [#104058110
<https://www.pivotaltracker.com/story/show/104058110>]
- ltc update-routes <http://lattice.cf/docs/ltc/#ltc-update-routes> will
be deprecated in a future release.

Known Issues

- Subsequent definitions of the same TCP route may not function properly
#208 <https://github.com/cloudfoundry-incubator/lattice/issues/208>
- Verify connectivity directly to app container (See ltc status
--detailed <http://lattice.cf/docs/ltc/#ltc-status-detailed>)
- Two apps with same TCP route defined will round-robin between two
separate apps

—
View it on GitHub
<https://github.com/cloudfoundry-incubator/lattice/releases/tag/v0.5.0>.