Thanks a lot Dieu, that answers my question. I have another question about creating a deployment manifest using the following as guidelines: http://do <http://docs.cloudfoundry.org/deploying/aws/cf-st

Sorry, for the typo I meant 6868 Thanks, Kinjal

Hi Amit, This does not seem to be a port issue on 6968. I tried the same deployment by modifying the security groups (both bosh and cf ) to allow All Protocol All Ports. even wit this change the deplo

Hi, I have a question regarding the configuration of cloud controller. It is described at http://docs.cloudfoundry.org/deploying/aws/cf-stub.html#editing that DROPLET_DIRECTORY_KEY should be replaced

Hi Amit, I checked the ports on all the security groups and found that 6868 is enabled on the inbound for 0.0.0.0/0 in all the groups. Am sending you the the bosh logs on your personal email address.

Hi Amit, Really appreciate all the help I receive on this forum. Hats off to you all. Here is the deployment log output: https://gist.github.com/kinjaldoshi/0925fdf6022b079ca2b5 Thanks, Kinjal

Hi Amit, Thanks a lot for the quick response. I am currently sanitizing the output, will send it soon. In the mean while, I wanted to confirm if I have created microbosh using the correct process. I h

Hi I have resolved the errors in generating deployment manifest. on executing bosh deploy, the below error is encountered while compiling packages: Started compiling packages Started compiling package

Hi Amit, Please ignore the unresolved nodes error in the above email. I have been able to correct it, running into some more problems, checking it right now. Please do let me know about my question on

Hi Amit, Thanks a lot for your response on this. I was trying to use the manifest generation scripts to redeploy cf but I ran into errors during spiff merge as below: ubuntu(a)ip-172-31-45-52:~/cf-dep

Hi Eric, Thanks a lot for the detailed response to my query. I used the minimal-aws.yml configuration ( https://github.com/cloudfoundry/cf-release/tree/v226/example_manifests) to create my deployment

Hi, After deploying CF version 226 on AWS using microbosh, I am trying to understand how to deploy Diego now to work with this version of CF but have not been able to figure out much yet. I was able t

Thanks Amit, that worked like a charm :) Regards, Kinjal

Hi, I was able to deploy CF successfully after removing '@' symbol from password as suggested by Amit. As a last step I am trying to bosh ssh into vms but this is failing. Below is my command: *bosh s

Hi Amit, Thanks a lot for your response. I too agree with what Gwenn and you have said. In my own hurry to meet a dead line, I did not think through well before putting in 'Urgent' on the email subjec

Hi Gwenn, Thanks a lot for the quick response. Apologies, will refrain from putting Urgent going forward. Please find below the manifest file: # The following line helps maintain current documentation

Hi, I am trying to deploy cloud foundry with the stemcell light-bosh-stemcell-3147-aws-xen-hvm-ubuntu-trusty-go_agent.tgz and cloud foundry release manifest cf-226yml I am also using the minimal-aws.y

Thanks a lot for directing me towards this project. When I am trying to deploy CF using this project, there are some issues as below: 1. 'bosh prepare deployment' fails because of checksum failure on

Hi, I am looking at miminal-aws.yml in the release https://github.com/cloudfoundry/cf-release and realized that this deployment will consume 13 instances on AWS. Is it possible to reduce the number of

Hi, From the architecture point of view I understand that there are no service explicitly associated with CF. However, the following doc is very confusing: http://docs.cloudfoundry.org/devguide/servic