Hi,

I am trying to deploy cf into Openstack with multiple computing nodes.

Computer node 1: has all openstack services running, including cinder
service (az1)
Computer node 2: has computing service only. (az2)

when I deployed the cf, the job VMs has been provisioned into the two
availability zones evenly. When BOSH started to update the job VM (etcd was
provisioned in az2) to create a disk, I got an error "Availability zone
'az2' is invalid".

My question is how to specify the availability zone for VMs and their
persistent disk?

Thanks.

Try telling BOSH to ignore what AZ the server is in when provisioning disks:

https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/spec#L395

It will default to cinders default AZ for storage that you have configured.

John

From: cf-dev-bounces(a)lists.cloudfoundry.org [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Guangcai Wang
Sent: 27 May 2015 08:23
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Multiple Availability Zone

Hi,
I am trying to deploy cf into Openstack with multiple computing nodes.
Computer node 1: has all openstack services running, including cinder service (az1)
Computer node 2: has computing service only. (az2)
when I deployed the cf, the job VMs has been provisioned into the two availability zones evenly. When BOSH started to update the job VM (etcd was provisioned in az2) to create a disk, I got an error "Availability zone 'az2' is invalid".
My question is how to specify the availability zone for VMs and their persistent disk?
Thanks.

This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email

I updated my bosh (using bosh-init) with enabling
ignore_server_availability_zone. but it still failed when I deployed my cf.
Anything suggestion?

openstack: &openstack
auth_url: http://137.172.74.78:5000/v2.0 # <--- Replace with OpenStack
Identity API endpoint
tenant: cf # <--- Replace with OpenStack tenant name
username: cf-admin # <--- Replace with OpenStack username
api_key: passw0rd # <--- Replace with OpenStack password
default_key_name: cf-keypair
default_security_groups: [default,bosh]
ignore_server_availability_zone: true


Error message from the deployment of cf:
Started updating job etcd_z1 > etcd_z1/0 (canary). Failed: OpenStack API
Bad Request (Invalid input received: Availability zone 'cloud-cf-az2' is
invalid). Check task debug log for details. (00:00:19)

Error 100: OpenStack API Bad Request (Invalid input received: Availability
zone 'cloud-cf-az2' is invalid). Check task debug log for details.


I checked the api request on first computing node. (/var/log/cinder/api.log)
2015-05-27 16:28:40.652 32174 DEBUG cinder.api.v1.volumes
[req-4df6ac85-e986-438a-a953-5a2190ec5f62 8b0d5a75bd9c4539ba7fa64e5669c6c8
48a0898a9c4944f1b321da699ca4c37a - - -] Create volume request body:
{u'volume': {'scheduler_hints': {}, u'availability_zone': u'cloud-cf-az2',
u'display_name': u'volume-36f9a2eb-8bc9-4f27-9530-34c9d24fa881',
u'display_description': u'', u'size': 10}} create
/usr/lib/python2.6/site-packages/cinder/api/v1/volumes.py:316


Attached my cf deployment file for reference.
cf-deployment-single-az.yml
<http://cf-dev.70369.x6.nabble.com/file/n206/cf-deployment-single-az.yml>





--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Multiple-Availability-Zone-tp192p206.html
Sent from the CF Dev mailing list archive at Nabble.com.