Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule you
suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I run
BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for
the first time.

when i execute bosh micro deploy it got stuck at below point. I see a
Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh