v0.6.0

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

• v0.6.0 does not work on DigitalOcean, Google Compute Engine, Openstack
  • Please continue to use the v0.5.0 bundle to deploy to these platforms
  • Lack of support for public user-created images (like AMIs) requires different deployment strategy
  • Additional discussions about this feature: DigitalOcean, Google Compute Engine
• vagrant up expects ltc target local.lattice.cf by default [#102582770]
• Removed Terraform module definition to simplify provisioning
  • Configured using terraform.tfvars instead of lattice.<platform>.tf [#104919576]
  • terraform get -update no longer necessary
• ltc launch-droplet no longer accepts --working-dir [#104935318]
• Define multple routes by passing the --http-route or --tcp-route flag multiple times [#105631892]
• Retire ltc update-routes [#104177142]
• Working with the Lattice development environment has changed (significantly) [#105305792]
  • Lattice has been split into separate cluster and CLI repositories
  • Moved cloudfoundry-incubator/lattice to cloudfoundry-incubator/lattice-release
  • Forked cloudfoundry-incubator/lattice/ltc to cloudfoundry-incubator/ltc

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

• Diego upgraded from 0.1424.1 to 0.1434.0
• Garden-Linux upgraded from 0.295.0 to 0.307.0
  • Fixes #187: Cells disk is full cloudfoundry-attic/garden-linux-release#7 [#102180368]
• CF upgraded from v213-93-g8a4f752 to v218 [#100518218]
• Works on Vagrant
  • VirtualBox [#104128040]
  • VMWare Fusion [#104921036]
  • AWS (all regions) [#104920976] [#105827024]
  • Replace shared folders with file provisioners for Vagrant VMs [#105732128]
  • vagrant up --provider=aws works to all AWS regions [#105376966]
• Works on Terraform (AWS only) (Δ)
  • AWS (all regions) [#104919576] [#105827024] [#105827024]
  • Removed Terraform module to simplify provisioning
    • Configured using terraform.tfvars instead of lattice.<platform>.tf (Δ)
    • terraform get -update no longer necessary

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

• Configure local.lattice.cf to replace 192.168.11.11.xip.io [#102582770] (Δ)
• Default timeout on ltc test increased to 5m [#105622190]
  • Longer timeout to adjust for AWS EBS volume no longer being pre-warmed
• vagrant up works on Windows host with AWS provider [#98709384]

CI / Packaging

• Create pipeline that does docker build docker push from cloudfoundry-incubator/lattice-ci
• Create pipeline that deploys from cloudfoundry-incubator/lattice-release [#104919732] [#105306942]
• CI builds and publishes vagrant boxes to Atlas
  • VirtualBox, VMWare Fusion [#105496810]
  • AWS [#105496796]
• Lattice has been split into separate cluster and CLI repositories
  • cloudfoundry-incubator/lattice moved to cloudfoundry-incubator/lattice-release
  • cloudfoundry-incubator/lattice/ltc forked to cloudfoundry-incubator/ltc
• Consolidate architecture-specific bundles into single bundle [#102485658]
  • Bundle no longer includes ltc; this is now served by the cluster [#102877664]

Documentation

• Update documentation for cluster changes [#105488088]
  • Vagrant Platforms [#105491060]
  • Terraform Platforms [#95925124]
• Document how to vagrant up using AWS provider [#105491060]
• Replace 192.168.11.11.xip.io with local.lattice.cf as default system domain [#102582848] (Δ)
• #220, #221: Upgrade Vagrant to support VirtualBox 5.x [#106054292] [#106052660]
• Document setting up the v0.6.0+ development environment on VirtualBox [#105305792] (Δ)
• Update ltc syntax for user context and routing functionality [#105069548] [#105635874]

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]