Note: lists.cloudfoundry.org will be down for maintenance on Wednesday, October 5th, starting at 9AM Pacific Time (4PM Wednesday October 5, 2022 UTC), for approximately one hour.
On behalf of the Lattice team, I am pleased to welcome v0.3.0 of Lattice!
Lattice v0.3.0 introduces Buildpack support! The team has been working on
this for several months, and we're ready to share it with you. Check out
the release notes below!
- 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
- You can track our prioritized queue of work at: http://bit.ly/lattice
Pivotal Software, Inc.
---------- Forwarded message ----------
From: Marco Nicosia <notifications(a)github.com>
Date: Fri, Aug 7, 2015 at 5:54 PM
Subject: [lattice] v0.3.0
To: cloudfoundry-incubator/lattice <lattice(a)noreply.github.com>
Lattice v0.3.0 Generating Droplets using Buildpacks
Since launch, Lattice has been limited to deploying only Docker containers.
Starting with version 0.3.0, we've taught Lattice another trick for using
Diego: *Droplets*. This is made possible by leveraging another Cloud
Foundry technology, Buildpacks
In just a few commands, ltc uploads your code, runs a CF Buildpack on it,
saves the compiled artifact (the *Droplet*), and launches it alongside your
Docker containers. The apps are then managed like any other app on Lattice.
The droplets are only kept as long as the Lattice cluster runs, re-build
your Droplets when deploying a fresh Lattice cluster.
The provisioner now installs a droplet store alongside Diego. ltc us
automatically configured to use it when you target the Lattice cluster. You
will see, Blob store is targeted, when Buildpack functionality is enabled.
Buildpacks are available on both Vagrant [#95876346
<https://www.pivotaltracker.com/story/show/95876346>] and Terraform [
- ltc target discovers the droplet store and stores its configuration. [
- ltc does not complain if it cannot find a droplet store; droplet
functionality is left disabled.
- ltc will attempt to use same credentials as API endpoint for
- vagrant up provisioner defaults to no-auth configuration
- terraform apply provisioner uses lattice_username and
lattice_password values from lattice.tf to configure droplet store.
- *ltc build-droplet* uploads the contents of the working directory and
builds a droplet using the specified buildpack [#92186444
- writes logs to build-droplet-DROPLET-NAME [#98292720
- accepts a --path argument to allow user to specify a file or
directory to upload. [#92186456
- prints a failure message if staging fails, and returns a non-zero
exit code. [#92186450
- does not upload files that match entries in .cfignore. [#92186460
- *ltc launch-droplet* launches a container running the specified
droplet [#92186446 <https://www.pivotaltracker.com/story/show/92186446>]
[#98321746 <https://www.pivotaltracker.com/story/show/98321746>] [
- *ltc list-droplets* lists the droplets stored in droplet store [
#92186452 <https://www.pivotaltracker.com/story/show/92186452>] [
- *ltc remove-droplet* deletes a droplet from the droplet store [
#92186454 <https://www.pivotaltracker.com/story/show/92186454>] [
- *ltc export-droplet* downloads the droplet tarball and metadata [
- *ltc import-droplet* uploads a droplet and its metadata [#92186470
- Upgraded to Diego 0.1398.0 & a major upgrade of garden-linux with
btrfs [#100301008 <https://www.pivotaltracker.com/story/show/100301008>]
- ltc docs updated to reflect droplet syntax [#98824900
- Totally re-vamped development-readme and scripts to set up a dev
- Now includes CF_VERSION in addition to DIEGO_VERSION [#99906506
Interestings and Bugfixes
- AWS images cannot deploy in international regions #158
- ltc submit-lrp launches a container running the specified droplet [
Once you've run build-droplet, you can manually submit it as an LRP
using a JSON file that you write yourself. For those who want Total
Control, this is a low-level way to do the same thing that launch-droplet
does in a more user-friendly way.
ltc build-droplet in *v0.3.0* is limited to only 128MB of RAM. Larger
applications may struggle to build properly. Please download the latest
if you run into this issue. This will be configurable in the next Lattice
release. [#100701142 <https://www.pivotaltracker.com/story/show/100701142>]
Download Links ltc CLI
- OS X
- AWS: lattice.aws.tf
- DigitalOcean: lattice.digitalocean.tf
- Google Cloud: lattice.google.tf
- Openstack: lattice.openstack.tf
View it on GitHub