Thanks, I'll do that. I opened an issue on github to request the feature: https://github.com/cloudfoundry/bosh-cli/issues/266 And I'll try out that workaround to run the bosh call in the background,

Hi Tushar, Thanks for your response. I have tried with this option also. Still same issue.

The new expected behavior is to only allow you to become root if you use the bosh CLI to perform your ssh since it creates a better audit trails and prevents unauthorized

Hi Johannes, Today I have tried with other stemcell(bosh-openstack-kvm-ubuntu-trusty-go_agent-raw). Also created different security group.I have also mentiond security group rules below. But still

Thanks, Alex. The current design doesn't require any BOSH changes in order for it to work. Keeping it separate from BOSH in the meantime has the advantages that we can make experimental changes and

identifier. if variables section contains a variable name, the director will try to ask credhub to generate value if one doesnt exist. sounds about right. manifest file for the identifier then no

Wanted to verify the steps that Bosh Director and CredHub perform to generate a password during a deployment. Here are the assumed steps: 1) Director does a CredHub REST API GET call to obtain the

Yes Johannes, I am using c1oudc0w. But still same issue. I am also surprised here.

Hi Arpit, the password is c1oudc0w and 0 ist zero not O. That's the one you used? wrote:

Hey Johannes, Still same issue. I am able to login in instance via ssh. it is not taking password. [root(a)openstack ~]# ssh -i /root/.ssh/id_rsa_demokey vcap(a)10.100.10.23 The authenticity of

Hi Chris, Very cool! What is the thinking of having this as an additional release and not part core BOSH as an experimental feature? Do you see this being moved into core BOSH at some point?

yes...I loged in director via OS cli with private key using ssh. Maybe I have done wrong password attemp more then 3. let me create director once again.

But you could login with ssh -i key vcap(a)ip?

I am doing with same password c1oudc0w. But unable to login. bosh/0:~$ sudo su [sudo] password for vcap: Sorry, try again. [sudo] password for vcap: Sorry, try again. [sudo] password for

As I wrote: c1oudc0w Mit freundlichen Grüßen Johannes Hiemer

I am unable to login with this password.

Hi Johannes, Unable to understand you. When I will do sudo for root from vcap user. It is asking for vcap user password. Where I can get this password?

Do a sudo su with c1oudc0w and then the following: sudo su [sudo] password for vcap: root(a)dc1a850b-184b-4189-47e8-68db05d91bdd:/home/vcap# monit summary The Monit daemon 5.2.5 uptime: 9d 2h

Hi Johannes, I am agree with you. I knew that after director deployment, I need to deploy more then 12 VM's. This will definitely require better hardware. Our team will take some time to arrange this

Hi Arpit, two important things: - I would not proceed with an installation, if you already run into disk capacity issues now. A minimal useful installation consists of at least 10 - 12 VMs