1. Cf-Bosh
  2. Topics

vCloud/vSphere microBOSH deployments - SSH Tunnel

Moiz Khan
 

Hi all,

I was just wondering if it's possible to deploy microBOSH using bosh-init from outside the vDC network i.e. deploying microBOSH externally similar to AWS where the Elastic IP address is used by bosh-init to SSH onto the VM to perform actions. There is a block in the AWS manifest https://bosh.io/docs/init-aws.html called ssh_tunnel which is used to implement this. Does anyone know if there is similar functionality for vCloud/vSphere deployments as well? Or does the machine running bosh-init have to be on the same network where microBOSH has to be deployed.

Regards,
Moiz Khan
Moiz Khan
 

Hi,

Answered my own query here by trial and error and it works properly with some minor changes to the vCD manifest. The ssh_tunnel field works well even on vCloud.

Only changes needed are in the cloud_provider field of the manifest:

You just need to specify the unencrypted (don't know if encrypted will work) password instead of the private key file unlike AWS. And you just need to replace the IP in the mbus field with the external IP of the vDC.

And obviously, you need to set up proper DNATs so that the required ports (22,6868) are forwarded to the IP of the microBOSH VM.

The bosh-init docs for vCloud Director can be updated to reflect this if needed since currently there's no mention of the ssh_tunnel there.

Regards,
Moiz Khan
Dmitriy Kalinin
 

there is no need to use ssh_tunnel for vcloud, you just have to make sure firewall settings are ok.

Sent from my iPhone

On Nov 18, 2015, at 11:56 PM, Moiz Khan <moiz.khan(a)atos.net> wrote:

Hi,

Answered my own query here by trial and error and it works properly with some minor changes to the vCD manifest. The ssh_tunnel field works well even on vCloud.

Only changes needed are in the cloud_provider field of the manifest:

You just need to specify the unencrypted (don't know if encrypted will work) password instead of the private key file unlike AWS. And you just need to replace the IP in the mbus field with the external IP of the vDC.

And obviously, you need to set up proper DNATs so that the required ports (22,6868) are forwarded to the IP of the microBOSH VM.

The bosh-init docs for vCloud Director can be updated to reflect this if needed since currently there's no mention of the ssh_tunnel there.

Regards,
Moiz Khan
Moiz Khan
 

Hi Dmitriy,

I made a few attempts with and without the ssh_tunnel field. It always failed at the 'Waiting for agent' state saying it didn't get a response in time (10 minutes) when ssh_tunnel wasn't specified correctly. Does bosh-init not need to ssh onto the VM to perform some actions?

Regards,
Moiz Khan

there is no need to use ssh_tunnel for vcloud, you just have to make sure firewall
settings are ok.

Sent from my iPhone

On Nov 18, 2015, at 11:56 PM, Moiz Khan <moiz.khan(a)atos.net&gt; wrote:

Hi,

Answered my own query here by trial and error and it works properly with some minor
changes to the vCD manifest. The ssh_tunnel field works well even on vCloud.

Only changes needed are in the cloud_provider field of the manifest:

You just need to specify the unencrypted (don't know if encrypted will work)
password instead of the private key file unlike AWS. And you just need to replace the IP
in the mbus field with the external IP of the vDC.

And obviously, you need to set up proper DNATs so that the required ports (22,6868)
are forwarded to the IP of the microBOSH VM.

The bosh-init docs for vCloud Director can be updated to reflect this if needed since
currently there's no mention of the ssh_tunnel there.

Regards,
Moiz Khan

1 - 4 of 4