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

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

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

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 7m Proce

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 an will con

Hi Arpit, can you see the volume being created in OS? wrote:

Hi Arpit, thanks for your kind words. This should be the right place, where you can open a ticket: https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues wrote:

Hi Arpit, I would switch to a different hardware and in the meanwhile open a ticket to request configuration of this element as an option on the bosh_openstack_cpi. Best, Johannes wrote:

Hi Arpit, that means it works? wrote:

Then take a look here: https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues/39 wrote:

Hi Arpit, did you check: architecture='x86_64', auto_disk_config='true', hypervisor_type='kvm', os_distro='centos', os_type='linux', version='3421.11' Maybe no Hypervisor of type KVM? wrote:

Ok hmpf that's interesting. To unterstand it again Arpit, are you able to spawn an instance from Horizon or the CLI with the uploaded Stemcell? wrote:

Perhaps you have different AvailabilityZones for Nova and Cinder. Please go to the configuration file for OS V2 and add the following entry: ignore_server_availability_zone: true wrote:

Arpit, for debugging purpose: please try to download a stemcells and upload it by hand into OS. See if it is working, if not you might have the wrong stemcell. (there is a difference between the forma

Arpit, you did not specify a domain. Is your OS installation having v2 or v3 API endpoints? wrote:

No it is just a complete example. Remove the section if you don't need it.

Here you go: #!/bin/bash bosh create-env bosh.yml \ -o openstack/cpi.yml \ --state=/workspace/deployments/bosh-1/state.json \ --vars-store=/workspace/deployments/bosh-1/creds.yml \ -v director_name=bo

In the CLI command itself

As stated before changed security groups to default_security_groups=[default], then it should work. wrote:

If you deploy again (not bosh-init delete), all the data should remain on the detached disk, which is reattached after the deployment if I remember correctly. wrote: