Date 1 - 3 of 3
Documentation Update AWS
Leandro David Cacciagioni
I have had a few issues over the last weeks deploying Cloud Foundry to AWS
and I think that maybe it will be nice to:
- Update the docs to be able to deploy without using the bosh aws gem
(It's broken at least with ruby 2.3.3/rbenv & Fedora Linux 25).
- Also is not nice that this GEM deletes everything when you try to
tear down all that was created, it not only delete what was create by it,
but everything else in the account if possible.
- Update the docs specifying the minimum AWS quotas required for minimal
- Update the stub sample to use m4 instances, since this has been in AWS
for quite some time and they are already in most of the AWS regions.
- Beyond AWS it would be nice a detailed step by step guide to deploy CF
with Diego enabled, since for those who have never touched CF is a little
difficult to understand all the moving parts of CF.
- In my case I was giving more than a week of training, at least one
hour per day until they catch up the concepts and understand the
how CF works (Forget about make them modify a bosh deployment to match a
Diego deployment if that's not in the docs)
Hope this help us all.
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 <
Leandro David Cacciagioni
Thanks a lot for the answer, and yes the pain points are those ones...toggle quoted message Show quoted text
Those are normally not pain points for someone who has already deployed CF
for a long time... But for new comers they are quite huge problems, that
many times lead to a more difficult adoption of CF among new comers... It
makes CF looks a little bit unprofessional. It is also a pain point to
explain to your coworkers why you do things that are not in the docs.
Once again thanks a lot for the new tools, I'll take a look to them this
2017-02-25 2:43 GMT+01:00 David Sabeti <dsabeti(a)pivotal.io>:
|1 - 3 of 3|