Re: Deploying CloudFoundry on AWS - bosh deploy returns timed out pinging


Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
 

Ok, some thoughts:

1) Aristoteles Neto, did you have to set this property even using c3.large?
I ask it because your manifest is using c3.large and I didn't have any kind
of problem using c3.large or m1.small. Only with t2.micro. So, If I
understood, did you have the same ping timeout using t2.micro and after
that changed the 'ephemeral_disk' property and it worked? Is it?

2) Gwenn Etourneau, my first thought was about that. But in my
minimal_aws.yml there is only one place to put stemcell name and version
and then I can't choose hvm because it only works with t2.micro. What I'm
saying is that I wanted, if possible, to do this:

resource_pools:
- name: small_z1
network: cf_private
stemcell:
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: 2986
cloud_properties:
availability_zone: sa-east-1a
instance_type: t2.micro

compilation:
workers: 6
network: cf_private
reuse_compilation_vms: true
stemcell:
name: bosh-aws-xen-ubuntu-trusty-go_agent
version: 2986
cloud_properties:
availability_zone: sa-east-1a
instance_type: m1.small

But It's not being possible, there is only stemcell property in the
resource pools.

The last question: As I've mentioned, when I change all to m1.small
(compilaitons VMs and CF jobs) everything works fine. Also, after it
succeeds for the first tiem, if I try to do a bosh deploy again using also
m1.small the compilation phase succees instantaneously. If I change to
other machine type, it tries to start the compilation phase again. So, is
compilation phase "per machine type"?

Thanks in advance, guys!


2015-06-16 19:21 GMT-03:00 Flávio Henrique Schuindt da Silva <
flavio.schuindt(a)gmail.com>:

Just to post the resolution...

I don't know why, but I delete all the stuff (deleted VPC) and restarted
tutorial from the beginning and now it suceeds.

In this same topic, I changed c3.large to m1.small in the minimal_aws.yml
manifest, because c3.large are very expensive!

Another test that I've done: After sucessfully deployed, I changed
m1.small to t2.micro and again I stucked in the compiling package phase and
receive ping timeout error after 600 seconds. Why it occurs? If I go back
to m1.small, it works fine again. Why can't I use t2.micro?

Thanks, guys!

2015-06-15 10:59 GMT-03:00 Flávio Henrique Schuindt da Silva <
flavio.schuindt(a)gmail.com>:

Hi, guys!

I'm trying to deploy CF on aws and I'm following strictly this tutorial:
http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html

I completed succesfully steps 1, 2 and 3, but I'm stuck on step 4. When I
run bosh deploy, I got it:

bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
------------------------------
Deployment name: `minimal-aws.yml'
Director name: `microbosh'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 33
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done
(00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

Started compiling packages
Started compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4
Started compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613
Started compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4
Started compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3
Failed compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4: Timed out
pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3: Timed out
pinging to 435b8765-8e9a-4615-8328-6f7b30bca3c0 after 600 seconds (00:11:04)
Failed compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613: Timed out pinging to
4c86e063-3c06-497d-829b-12b5455679e9 after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4: Timed out
pinging to 0a734427-f633-420e-94da-8d20ddc1d0be after 600 seconds (00:11:04)

Error 450002: Timed out pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc
after 600 seconds

I see on ec2 dashboard that the compilation vms workers start to run, but
in a couple of minutes they suddently got terminated (the terminated ation
is made by bosh, of course). The problem here, I think, is that the bosh
director aren't communicating properly with compilation vms and so they got
a timeout error. But I followed exactly the same steps from tutorial.

Also, I checked all the network config on aws console and nothing seems
to be wrong. How can i solve it? Thanks in advance, guys!

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.