wrote:

Hi Ferran,
Earlier I tried using bosh-init. This time I deleted the instance and
tried again with bosh using the following manifest:

name: cf-bosh

network:
type: manual
vip: <FLOATING_IP> # Replace with a floating IP address
ip: <SUBNET_IP> # Replace with an address from the subnet IP address
allocation pool of your OpenStack internal network
cloud_properties:
net_id: <NET_UUID> # Replace with your OpenStack internal network UUID

resources:
persistent_disk: 20000
cloud_properties:
instance_type: CO2-Large

cloud:
plugin: openstack
properties:
openstack:
auth_url: <OPENSTACK_URL> # Replace with your OpenStack Identity API
endpoint
tenant: <PROJECT_NAME>
username: <USER_NAME># Replace with OpenStack username
api_key: # Replace with your OpenStack password
default_key_name: bosh-keypair # OpenStack Keypair name
private_key: bosh-keypair.pem # Path to OpenStack Keypair private key
default_security_groups: [default,ssh]
ignore_server_availability_zone: true

apply_spec:
properties:
director: {max_threads: 3}
hm: {resurrector_enabled: true}
ntp: [0.north-america.pool.ntp.org, 1.north-america.pool.ntp.org]


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

Now I see different error as so:

/usr/local/lib/ruby/gems/2.1.0/gems/bosh_openstack_cpi-1.2982.0/lib/cloud/openstack/cloud.rb:431:in
`block in create_disk': undefined method `availability_zone' for
nil:NilClass (NoMethodError)
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_common-1.2982.0/lib/common/thread_formatter.rb:49:in
`with_thread_name'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_openstack_cpi-1.2982.0/lib/cloud/openstack/cloud.rb:409:in
`create_disk'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:282:in
`block in create_disk'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:85:in
`step'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:280:in
`create_disk'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:352:in
`update_persistent_disk'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:137:in
`block in create'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:85:in
`step'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:136:in
`create'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:98:in
`block in create_deployment'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:92:in
`with_lifecycle'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/deployer/instance_manager.rb:98:in
`create_deployment'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli_plugin_micro-1.2982.0/lib/bosh/cli/commands/micro.rb:179:in
`perform'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli-1.2982.0/lib/cli/command_handler.rb:57:in
`run'
from
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli-1.2982.0/lib/cli/runner.rb:56:in
`run'
from /usr/local/lib/ruby/gems/2.1.0/gems/bosh_cli-1.2982.0/bin/bosh:16:in
`<top (required)>'
from /usr/local/bin/bosh:23:in `load'
from /usr/local/bin/bosh:23:in `<main>'

Thanks.




From: Ferran Rodenas <frodenas(a)gmail.com>
Date: Friday, June 12, 2015 12:05 AM
To: Surekha Bejgam <sbejgam(a)cisco.com>
Cc: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>, Srikanth Bhamidipati <bsri(a)cisco.com>,
"osc-team-harmony(mailer list)" <osc-team-harmony(a)cisco.com>

Subject: Re: [cf-bosh] deploying cloud foundry fails with openstack
Icehouse

What blockstorage backend are you using? Ceph or pure Cinder (lvm)?

Is weird that the create volume api call passes the mel-2-csx
availability zone, when ignore_server_availability_zone is set, it should
not pass it. Can you please paste a sanitiez version of your deployment
manifest?

- Ferdy

On Jun 12, 2015, at 8:50 AM, Surekha Bejgam (sbejgam) <sbejgam(a)cisco.com>
wrote:

Thanks Ferran for your suggestion. I tried adding this property, still
fails with the same error message.
Not sure what else I could try.

Regards,
Surekha

From: Ferran Rodenas <frodenas(a)gmail.com>
Date: Thursday, June 11, 2015 11:31 PM
To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Cc: Surekha Bejgam <sbejgam(a)cisco.com>, Srikanth Bhamidipati <
bsri(a)cisco.com>, "osc-team-harmony(mailer list)" <
osc-team-harmony(a)cisco.com>
Subject: Re: [cf-bosh] deploying cloud foundry fails with openstack
Icehouse

Have you tried setting the "ignore_server_availability_zone" property?

properties:
openstack:
ignore_server_availability_zone: true

- Ferdy

2015-06-12 7:55 GMT+02:00 Lakshman Mukkamalla (lmukkama) <
lmukkama(a)cisco.com>:

Just FYI.
We are even tried with *bosh-init* to install CF in openstack. Below is
what we see, with the same issue as bosh micro deploy

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid
'4a91752f-7427-4f2a-8351-6c02de9d41cd':
CPI 'create_vm' method responded with error:
CmdError{"type":"Bosh::Clouds::CloudError","message":"*OpenStack API Bad
Request (The requested availability zone is not available). Check task
debug log for details.*","ok_to_retry":false}

Detailed debug logs:
[2015-06-11T19:15:40.821299 #8208] DEBUG -- : excon.error
{:error=>#<Excon::Errors::BadRequest: Expected([200, 202]) <=> Actual(400
Bad Request)
excon.error.response
:body => "{\"badRequest\": {\"message\": \"Invalid input
received: Availability zone 'mel-2-csx' is invalid\", \"code\": 400}}"
:headers => {
"Content-Length" => "108"
"Content-Type" => "application/json; charset=UTF-8"
"Date" => "Thu, 11 Jun 2015 23:15:41 GMT"
"X-Compute-Request-Id" => "req-55e756f5-4cfc-4929-a74e-5f2f5fbbc090"
"X-Openstack-Request-Id" => "req-55e756f5-4cfc-4929-a74e-5f2f5fbbc090"
}

Thanks.

From: "Surekha Bejgam (sbejgam)" <sbejgam(a)cisco.com>
Date: Thursday, June 11, 2015 7:15 PM
To: "cf-bosh(a)lists.cloudfoundry.org" <cf-bosh(a)lists.cloudfoundry.org>
Cc: "osc-team-harmony(mailer list)" <osc-team-harmony(a)cisco.com>,
Srikanth Bhamidipati <bsri(a)cisco.com>
Subject: deploying cloud foundry fails with openstack Icehouse

Hello,

We are trying to deploy cloud foundry using bosh.

Stemcell info
-------------
Name: bosh-openstack-kvm-ubuntu-trusty-go_agent-raw
Version: 2915

BOSH Version: BOSH 1.2982.0

Below is the error we are seeing during: "bosh micro deployment
manifest.yml"


***************************************************************************************************

Started deploy micro bosh
Started deploy micro bosh > Unpacking stemcell. Done (00:00:04)
Started deploy micro bosh > Uploading stemcell. Done (00:01:39)
Started deploy micro bosh > Creating VM from
d3ef9ac6-5a51-438e-a0e0-50d7df6e0c70. Done (00:00:13)
Started deploy micro bosh > Waiting for the agent. Done (00:01:35)
Started deploy micro bosh > Updating persistent disk
Started deploy micro bosh > Create disklog writing failed. can't be
called from trap context
/usr/local/lib/ruby/gems/2.1.0/gems/bosh_openstack_cpi-1.2982.0/lib/cloud/openstack/helpers.rb:20:in
`cloud_error': OpenStack API Bad Request (Invalid input received:
Availability zone 'mel-2-csx' is invalid). Check task debug log for
details. (Bosh::Clouds::CloudError)


Any idea what we are missing here ?

Thanks,
Surekha


_______________________________________________
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