This project is now included in the Lattice project
This project contains several Terraform templates to help you deploy Lattice on your choice of IaaS.
- Terraform installed on your machine
- Credentials for your choice of IaaS
Create a lattice.tf file downloading the AWS example file:
wget --quiet https://raw.githubusercontent.com/cf-platform-eng/lattice-terraform/master/aws/lattice.tf.example -O lattice.tfUpdate the downloaded file filling the variables according to the AWS README file.
Create a lattice.tf file downloading the DigitalOcean example file:
wget --quiet https://raw.githubusercontent.com/cf-platform-eng/lattice-terraform/master/digitalocean/lattice.tf.example -O lattice.tfUpdate the downloaded file filling the variables according to the DigitalOcean README file.
Create a lattice.tf file downloading the Google Cloud example file:
wget --quiet https://raw.githubusercontent.com/cf-platform-eng/lattice-terraform/master/google/lattice.tf.example -O lattice.tfUpdate the downloaded file filling the variables according to the Google Cloud README file.
Get the templates and deploy the cluster:
terraform get -update
terraform apply
After the cluster has been successfully, terraform will print the Lattice domain:
Outputs:
lattice_target = x.x.x.x.xip.io
lattice_username = xxxxxxxx
lattice_password = xxxxxxxx
Refer to the Lattice CLI documentation.
Destroy the cluster:
terraform destroy
In the spirit of free software, everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using alpha, beta, and prerelease versions
- by reporting bugs
- by suggesting new features
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
- by refactoring code
- by closing issues
- by reviewing patches
We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Commit and push your changes.
- Submit a pull request.
See LICENSE for details. Copyright (c) 2015 Pivotal Software, Inc.