v0.5.0

New Features

• #205: Terraform cells download lattice.tgz directly at provision-time [#104137996]
  • terraform apply can now be run from low-bandwidth network connections
• Diego upgraded from 0.1398.0 to 0.1424.1 [#100656516] [#103211906]
  • #66: Garden v0.290.0 creates non-existent working directory on Docker RootFS [#91438788] [#91550852] cloudfoundry-attic/garden-linux#29
• Improve proxy support for Lattice [##2088022] [#103746258]
  • Droplets created following vagrant up with proxy enabled use cluster proxy configuration [#103533536] [#103796516]
  • ltc works behind a "not strict" proxy (not Squid) to connect to an external Lattice cluster [#103737106]
  • Validated CF buildpacks respect proxy configuration [#100512640]
• ltc ssh has reached feature parity with Diego SSH [##2051878]
  • Supports port forwarding with or without interactive shell [#101709060] [#102907420]
  • Detects whether to allocate a PTY, -T disables PTY allocation [#101710922] [#101710892]
  • Restores PTY from "raw" to "sane" mode following error or TERM signal [#104210274]

Bug Fixes

• Changes to ltc visualize --graphical
  • #209: Cell labels are populated from CellID value in Diego instead of sequencer [#104439866]
  • Cells are sorted properly (i.e., cell-2 before cell-11) [#93577238]
• Cell names are not prefixed with namespace on Google Compute Engine [#104658746]
• #204: Update out-of-date manual install instructions [#104094016]

Interestings

• Changes to ltc status
  • Prints instance summary by default, --detailed gives details [#104235428]
  • Displays the RootFS and Monitor configuration [#104058110] [#104058110]
• ltc update-routes will be deprecated in a future release.

Known Issues

• Subsequent definitions of the same TCP route may not function properly #208
  • Verify connectivity directly to app container (See ltc status --detailed)
• Two apps with same TCP route defined will round-robin between two separate apps