Re: Documentation Update AWS
Thanks for this feedback. One of the things the CF team has been working on
is better tooling around deploying Cloud Foundry, including IaaS setup. A
lot of this work is still in flight, which is why the CF docs don't have
any information about it yet; when the work is complete, there will
definitely be an overhaul of the docs to explain how to use the new tools.
In your outline, I think I'm noticing the following concerns:
1. How do I set up an AWS account so that I can deploy a CF? What are the
requirements (for example, quotas) for my account?
2. Can we default to using the most up-to-date instances?
3. Once my account is set up, how do I deploy CF (with Diego)?
4. How do I understand what I'm deploying and how I can modify it on my own?
Let me know if I've understood your questions correctly: I'll make sure
that we take this feedback into account when we build the docs for the new
In the meantime, I'm happy to point people to the new tools, provided that
I emphasize that* these tools are not ready for production and still
undergoing active development. You should use these at your own risk.*
- To set up IaaS for CF: Take a look a "bbl" (short for bosh-bootloader
<https://github.com/cloudfoundry/bosh-bootloader>). This is tool that does
all the work to get you to a bosh director -- it create IaaS resources like
VPCs, NAT boxes, etc., and the creates a BOSH director that you can target.
- To deploy CF: Take a look at cf-deployment
<https://github.com/cloudfoundry/cf-deployment>. It contains a BOSH
manifest for deploying Cloud Foundry (with Diego!). It also uses new BOSH
features to make manifest generation a good deal simpler. This will be the
future for how to deploy CF when we deprecated cf-release.
Again, these aren't ready for prime time yet, but it should be good for
development, testing, and experimentation -- not to mention that we'd love
feedback on this from the community. Feel free to follow up if you have any
Product Manager, CF Release Integration Team
On Thu, Feb 23, 2017 at 12:04 AM Leandro David Cacciagioni <