deploying cf on openstack - <Bosh::Director::NetworkReservationNotEnoughCapacity: Resource pool `m

168 views
Skip to first unread message

Ramesh Sambandan

unread,
Apr 15, 2015, 8:58:41 PM4/15/15
to bosh...@cloudfoundry.org
I am trying to deploy cf release 206 to microbosh director that I deployed.

I am using nova network.

I believe my problems are with cf-stub.yml for openstack. I had to add cf2 and floating networks (among other things) to spiff merge the yml-s (unresolved dependencies). If anybody can share complete working stub file for openstack, that will be of great help.

Following is my stub yml contents. I have also attached my merged cf-deployment.yml that I am trying to deploy.
name: demo-cf-release
director_uuid
: 45dbc684-fe0f-4917-b67d-0fe95747aced # from bosh config
meta
:
  openstack
:
    net_id
: 9a6eed65-4711-46f7-a3c4-6a1814762592 # net_id from nova network-list
    auth_url
: http://172.16.9.1:5000/v2.0
    tenant
: bosh-tenant
    username
: bosh
    api_key
: boshPwd
    security_groups
: ["bosh","cf", "cf-private", "cf-public", "ssh"]
  floating_static_ips
:
 
- 192.168.0.137
networks
:
- name: cf1
  subnets
:
   
- cloud_properties: {}
      range
: 172.16.9.254/25
     
static:
     
- 172.16.9.140 - 172.16.9.254
- name: cf2
  subnets
:
   
- cloud_properties: {}
      range
: 172.16.10.254/25
     
static:
     
- 172.16.10.140 - 172.16.10.254
- name: floating
  type
: vip
  cloud_properties
: {}
properties
:
  cc
:
    droplets
:
      droplet_directory_key
: dropletKey
    buildpacks
:
      buildpack_directory_key
: buildpackKey
    staging_upload_user
: stgUploadUser
    staging_upload_password
: stgUploadPwd
    bulk_api_password
: bulkApiPwd
    db_encryption_key
: dbEncryptionKey
  ccdb
:
    roles
:
   
- name: ccadmin
      password
: ccadminPwd
      tag
: admin
  databases
:
    roles
:
   
- name: ccadmin
      password
: ccadminPwd
   
- name: uaaadmin
      password
: uaaadminPwd
  dea_next
:
    disk_mb
: 2048
    memory_mb
: 1024
  domain
: yesVin.com
  loggregator_endpoint
:
    shared_secret
: loggregatorEndpointSecret
                                                                                                                                                                                           
1,1           Top





I am getting following error. (bosh task --debug)

I, [2015-04-16 00:28:40 #2006] [task:21]  INFO -- DirectorJobRunner: sending update deployment error event
D
, [2015-04-16 00:28:40 #2006] [task:21] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"551543a5-3515-4bf7-bbb0-71b9e86a6564","severity":3,"title":"director - error during update deployment","summary":"Error during update deployment for demo-cf-release against Director 45dbc684-fe0f-4917-b67d-0fe95747aced: #<Bosh::Director::NetworkReservationNotEnoughCapacity: Resource pool `medium_z1' asked for a dynamic IP but there were no more available>","created_at":1429144120}
E
, [2015-04-16 00:28:40 #2006] [task:21] ERROR -- DirectorJobRunner: Resource pool `medium_z1' asked for a dynamic IP but there were no more available
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/network_reservation.rb:109:in `handle_error'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/network.rb:40:in `
reserve!'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/resource_pool.rb:118:in `reserve_dynamic_network'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/resource_pool.rb:96:in `block in process_idle_vms'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/resource_pool.rb:94:in `
each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/resource_pool.rb:94:in `process_idle_vms'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/assembler.rb:268:in `block in bind_resource_pools'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/assembler.rb:267:in `
each'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/assembler.rb:267:in `bind_resource_pools'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/preparer.rb:25:in `block in prepare'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/base_job.rb:48:in `
block in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/event_log.rb:97:in `call'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/event_log.rb:50:in `
track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/base_job.rb:46:in `track_and_log'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/deployment_plan/preparer.rb:24:in `prepare'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/update_deployment.rb:52:in `
prepare'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/update_deployment.rb:85:in `block in perform'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/lock_helper.rb:21:in `block in with_deployment_lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/lock.rb:56:in `
lock'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/lock_helper.rb:21:in `with_deployment_lock'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/update_deployment.rb:82:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/job_runner.rb:108:in `
perform_job'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/job_runner.rb:31:in `block in run'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.2915.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/job_runner.rb:31:in `
run'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/lib/bosh/director/jobs/base_job.rb:10:in `perform'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/job.rb:227:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:250:in `
perform'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:189:in `block in work'

/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/resque-1.25.2/lib/resque/worker.rb:166:in `
work'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.2915.0/bin/bosh-director-worker:75:in `<top (required)>'

/var/vcap/packages/director/bin/bosh-director-worker:16:in `load'
/var/vcap/packages/director/bin/bosh-director-worker:16:in `<main>'


Can somebody please help. Is there a reference working stub file for openstack using nova network,

Thank you in advance for your help.

regards
-Ramesh
cf-deployment.yml

ronak

unread,
Apr 16, 2015, 4:29:14 AM4/16/15
to bosh...@cloudfoundry.org
Openstack is not able to assign IP to a vm. check your network pool . 
...

lavi...@gmail.com

unread,
Apr 20, 2015, 1:18:57 PM4/20/15
to bosh...@cloudfoundry.org
We have an example stub for OpenStack here. This should include the bare minimum required fields to get your deployment up and running.  Looking at your stub and the error reported by bosh, it could be that your OpenStack deployment has a different IP range allocated.

Hope that helps,
Dan && Utako, The CF Runtime Team 
Reply all
Reply to author
Forward
0 new messages