Lattice
Lattice was a Cloud Foundry project focused on delivering the Diego application scheduler into the hands of users as quickly as possible before Diego was fully integrated to Cloud Foundry. Lattice served that purpose well, but now Diego is available as the application scheduler for Cloud Foundry, and Cloud Foundry is the best way to use Diego. Therefore, Lattice is no longer actively maintained.
Lattice is an open source project for running containerized workloads on a cluster. Lattice bundles up http load-balancing, a cluster scheduler, log aggregation/streaming and health management into an easy-to-deploy and easy-to-use package.[ Website | Latest Release | Nightly Builds ]
A colocated deployment of Lattice can be launched locally with Vagrant. You will need:
NOTE: Ubuntu 14.04 LTS does not install a compatible version of Vagrant by default. You can upgrade the version that you get out of the box by downloading the
.debfile from Vagrant.
Unzip the Lattice bundle, and switch to the vagrant directory
unzip lattice-bundle-VERSION.zip
cd lattice-bundle-VERSION/vagrant
vagrant up --provider virtualboxThis spins up a virtual environment that is accessible at local.lattice.cf
ltc (the Lattice CLI)If you're running Linux: curl -O http://receptor.local.lattice.cf/v1/sync/linux/ltc
If you're running OS X: curl -O http://receptor.local.lattice.cf/v1/sync/osx/ltc
Finally: chmod +x ltc
./ltc target local.lattice.cfA scalable cluster deployment of Lattice can be launched on Amazon Web Services with Terraform. You will need:
Unzip the Lattice bundle, and switch to the terraform/aws directory
unzip lattice-bundle-VERSION.zip
cd lattice-bundle-VERSION/terraform/awsUpdate the terraform.tfvars file with your AWS credentials and desired cluster configuration.
terraform applyTerraform will generate a terraform.tfstate file. This file describes the cluster that was built - keep it around in order to modify/tear down the cluster.
ltc (the Lattice CLI)After a successful deployment Terraform will print the Lattice target and Lattice user information. Refer to the target = output line to find the address of your cluster.
If you're running Linux: curl -O http://receptor./v1/sync/linux/ltc
If you're running OS X: curl -O http://receptor./v1/sync/osx/ltc
Finally: chmod +x ltc
./ltc target NOTE: These instructions are for people contributing code to Lattice. If you only want to deploy Lattice, see above. These instructions cover Vagrant/Virtualbox development. A similar process can be followed for Vagrant/VMWare, Vagrant/AWS, and Terraform/AWS development. More documentation is forthcoming.
To develop Lattice you will need to have the following tools installed:
git clone --recursive https://github.com/cloudfoundry-incubator/lattice-release.gitSetup your shell for building Lattice:
cd lattice-release
direnv allow # or: source .envrcIf you change any Diego components, you'll need to build a local Vagrant box with your changes.
If you don't plan to change any Diego components, you can update the box_version property
in vagrant/Vagrantfile to point to a pre-built Lattice box on Atlas
and skip this step.
bundle
cd vagrant
./build -only=virtualbox-iso
vagrant box add --force lattice-virtualbox-v0.box --name lattice/colocated# in lattice-release/vagrant
../release/build lattice.tgzOnce you have a Lattice tarball, use vagrant to deploy Lattice:
# in lattice-release/vagrant
vagrant up --provider=virtualboxCompiling ltc is as simple as using go install:
go install github.com/cloudfoundry-incubator/ltcltc target local.lattice.cf
ltc test -vIf you are interested in contributing to Lattice, please refer to CONTRIBUTING.
See LICENSE for details. Copyright (c) 2015 Pivotal Software, Inc.
No open issues yet, or sync has not completed.