1 year, 9 months
On the main docs page (http://lattice.cf/docs/) I read:
"If you need to set up a productionized deployment of Lattice you will need
to be sure to make all the components redundant"
Are there any docs about how to do this?
Announcing Lattice v0.2.5
1 year, 9 months
On behalf of the Lattice team, I am pleased to announce v0.2.5 of Lattice!
Originally an optimization release, we delayed a few weeks to sneak in some
exciting features. Here's the mundane stuff first: We've updated the base
OS images to Ubuntu-trusty-64 14.04.2 and simplified Vagrant and AWS
provisioning. We've also updated to support Terraform 0.5 and up.
The release includes two new interesting features: First, You can now
specify a URL to monitor when creating an app, rather than relying on the
standard port health check. You can also set a timeout to make sure your
app isn't judged unhealthy when it's really just a little slow. We love all
our apps just the same.
Second, we've updated the `ltc` command line tool to expose Diego's Task
We haven't built any fancy UI around this, you'll have to feed the CLI a
JSON file to make it work. Tasks enable a whole different world of use
cases - they are one-off work that are guaranteed to run at most once.
Also, in Lattice v0.2.5, we're introducing a *community-contributed* OpenStack
module for Terraform. We're super thankful to the contributors, and are
very interested to hear your experiences. One caveat: Because OpenStack is
kind of "supermorphic," we haven't set up a continuous integration pipeline
to make sure that module changes don't break functionality. So we're
marking this feature as *community supported*, and hope that OpenStack
support can grow more sophisticated over time. We're looking forward to
Finally, we've unified the lattice website <http://lattice.cf/> documentation
with the GitHub documentation
you can open issues (and hopefully PRs) against our documentation, and the
website will reflect those changes, too.
We're humbled and pleased by the amount of community activity, and have
been doing our best to make sure you all feel the love. One quick reminder:
Please make sure to fork Develop, not Master, or we'll have to ask you to
rebase. The Master branch is the result of a successful continuous
integration run. Develop is where we introduce new code and the concomitant
A lot more went into this release, for full release notes, please check out:
*Nota Bene:* It's really great that all of this has been the work of just a
single pair. Part of the Pivotal Way is that team members frequently rotate
projects in order to cross-pollinate domain knowledge as well as expand
their breadth of skills. This week, the team says goodbye to KL, who has
been a pleasure to work with. Thanks for everything, we're sad to see you
- 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:
Pivotal Software, Inc.