Date
1 - 11 of 11
Deploying CloudFoundry on AWS - Too many machines are being created
|
Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
I succesfully deployed CF on aws using this tutorial:
http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html But this tutorial is kind of expensive...It creates 13 machines (one for each cf component) and each one is c3.large! I would like to create maybe, let's say, 4 ~ 5 machines to have all CF components. Is it possible? |
|
|
|
Gwenn Etourneau
Yes it is possible, you can colocate job.
On Thu, Jun 18, 2015 at 4:51 AM, Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com> wrote: I succesfully deployed CF on aws using this tutorial: |
|
|
|
Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
And how can I colocate the jobs? I mean, how could I change a little the
toggle quoted message
Show quoted text
tutorial to achieve it? Thanks! 2015-06-17 16:51 GMT-03:00 Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com>: I succesfully deployed CF on aws using this tutorial: |
|
|
|
Cornelia Davis <cdavis@...>
You will have to know quite a bit about the CF architecture to first know
which jobs can be collocated and then you'll have to change your manifest pretty significantly. Not a trivial thing. On Thu, Jun 18, 2015 at 6:21 AM, Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com> wrote: And how can I colocate the jobs? I mean, how could I change a little the |
|
|
|
Tom Sherrod <tom.sherrod@...>
I second the
toggle quoted message
Show quoted text
https://github.com/cloudfoundry-community/terraform-aws-cf-install project. Quite adjustable too. On Thu, Jun 18, 2015 at 11:15 AM, Cornelia Davis <cdavis(a)pivotal.io> wrote:
You will have to know quite a bit about the CF architecture to first know |
|
|
|
Gwenn Etourneau
Yes you can use
toggle quoted message
Show quoted text
https://github.com/cloudfoundry-community/terraform-aws-cf-install installation which will install one of this deployment https://github.com/cloudfoundry-community/cf-boshworkspace/tree/master/deployments Basically you can specify the size by changing cf_size in the terraform variable script. By default it will install the tiny one. Anyway you can still have a look at https://github.com/cloudfoundry-community/cf-boshworkspace/tree/master/deployments to see how the job (templates) are colocated. On Fri, Jun 19, 2015 at 4:23 AM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:
I second the |
|
|
|
Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
Nice tip, Gwenn Etourneau!
toggle quoted message
Show quoted text
In a simple way, I could deploy CF on aws using terraform. Really really good! But I still have one problem: terraform uses terraform-aws-cf-install ( https://github.com/cloudfoundry-community/terraform-aws-cf-install). It creates 11 instances (1x t2.small, 5x c3.large, 2x m3.medium and 3x m3.large) and it costs about ~ 1.08 dollars/hrs. It would be great if we could set the instance types in the terraform.tfvars file or something similar. But I couldn't find it the repo files. Any idea? Thanks! 2015-06-18 10:21 GMT-03:00 Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com>: And how can I colocate the jobs? I mean, how could I change a little the |
|
|
|
Tom Sherrod <tom.sherrod@...>
Look at variables.tf, a flavor choice is there, however, most other machine
choices are defaults or recommended sizes. To change others, log onto the bastion machine. workspace contains the microbosh and cf release/deployment directories containing all the manifests. The provision.sh drives the install and the manifests are created/updated when first ran. From within those directories, work can be done to update/reconfigure/delete/deploy with machine changes you wish. Terraform is ran once, everything else can be done from the bastion machine. On Sat, Jun 20, 2015 at 12:03 AM, Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com> wrote: Nice tip, Gwenn Etourneau! |
|
|
|
Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
Great, Tom!
toggle quoted message
Show quoted text
I saw the cf-boshworspace directory and there there is a lot of place to do a lot of config. I saw that by default, terraform use cf-aws-tiny.yml located in the cf-boshworkspace/deployments folder. This file has a lot of templates included and a lot of them has some resource_pools configured. I don't know exactly where I should change to do what I want. My question is simple: Where, in the cf-boshworskapce, should I change the instances sizes? After that, I only have to run provision.sh in my bastion server to update the jobs vms on aws? Is it? There is no instructions about it in the cf-boshworkspace docs, so it's kind of confusing... Thanks again! 2015-06-20 1:03 GMT-03:00 Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com>: Nice tip, Gwenn Etourneau! |
|
|
|
Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
Ok, more infos:
If you go in the cf-boshworkspace and try to do a find for 'm3.large' there is results from the resource_pools: https://github.com/cloudfoundry-community/cf-boshworkspace/search?utf8=%E2%9C%93&q=m3.large&type=Code Ok, it makes sense, because cf_aws_tiny.yml includes templates and onde of these set some resource_pools to m3.large. But if you do the same query for 'c3.large' it doesn't return anything, but it still createa a lot of c3.large machines. So, from where is coming these configurations!? It's really difficult, nothing is mentioned in the docs... Any help would be appreciated! Thanks, guys! |
|
|
|
Tom Sherrod <tom.sherrod@...>
Checkout
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-infrastructure-aws.yml Even provision isn't needed after the initial run. Go to the cf-boshworkspace...there will be .deployment .releases .stemcell directories containing information. I don't have an aws install in front of me, I'm assuming cf-boshworkspace combines/merges in the defaults. I would use bosh and edit the deployments directly, once the environment is up the first time. (I'm basing this off minor tweaks in Openstack(dns, domains, etc)...I have not adjusted instance sizes...yet) Tom On Sat, Jun 20, 2015 at 10:22 PM, Flávio Henrique Schuindt da Silva < flavio.schuindt(a)gmail.com> wrote: Ok, more infos: |
|
|