Setup of domain in Cloudfoundry Manifest

animesh nandanwar

unread,

Sep 19, 2012, 3:24:01 PM9/19/12

to bosh-...@cloudfoundry.org

Hi all,

I am able to deploy cloudfoundry on Openstack and now I can not do vmc target: domain which is specified in cloudfoundry manisfest file.

Can someone help me to set it up and make it working ?

Following information will help you

I have a private openstack installation which is done using devstack. So all the VMs have ip addresses in network 10.0.0.0/24. I also have floating IPs associated to VMs which have network 172.24.4.224/28. So everything is private. Please find below my cloudfoundry manifest details.

Manifest:

---

version: 104.1-dev

director_uuid: e3fd8add-8cea-40a0-bc4c-5e6b233c49d7

release:

version: 104.1-dev

compilation:

workers: 2

network: private

cloud_properties:

instance_type: m1.small

key_name: inception

update:

canaries: 1

canary_watch_time: 3000-90000

update_watch_time: 3000-90000

max_in_flight: 1

max_errors: 1

networks:

- name: private

type: dynamic

cloud_properties:

security_groups:

- default

- name: public

type: vip

cloud_properties:

security_groups:

- default

resource_pools:

- name: dea

network: private

size: 4

stemcell:

version: 0.6.6

cloud_properties:

instance_type: m1.small

key_name: inception

env:

bosh:

password: $6$JQgtik9/5uI2$FCHCAW3q0NPmlYm4MolQOEDOI4c9Kga4qFvWYdxwPpNSywTXYHKFE/WNR6L4jbPR2ZPn69Q1GZ5vpYH.47VwO/

- name: infrastructure

network: private

size: 10

stemcell:

version: 0.6.6

cloud_properties:

instance_type: m1.small

key_name: inception

env:

bosh:

password: $6$JQgtik9/5uI2$FCHCAW3q0NPmlYm4MolQOEDOI4c9Kga4qFvWYdxwPpNSywTXYHKFE/WNR6L4jbPR2ZPn69Q1GZ5vpYH.47VwO/

jobs:

- name: debian_nfs_server

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: public

static_ips:

- 172.24.4.226

- name: cloud_controller

instances: 2

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: dea

instances: 4

resource_pool: dea

networks:

- name: private

default:

- dns

- gateway

- name: router

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: public

static_ips:

- 172.24.4.227

- name: stager

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: ccdb_postgres

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: public

static_ips:

- 172.24.4.228

- name: vcap_redis

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: public

static_ips:

- 172.24.4.229

- name: health_manager

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

- name: nats

instances: 1

resource_pool: infrastructure

networks:

- name: private

default:

- dns

- gateway

properties:

domain: cloudfoundry.test

env: {}

networks:

apps: private

management: private

nats:

user: nats

password: nats

address: 172.24.4.225

port: 4222

cc:

srv_api_uri: http://api.cloudfoundry.test

external_uri: cloudfoundry.test

password: aaauuLaap44jadlas2l312lk

token: aaaf4eaa8c1758f66d5cb7adcb24adb9d7

use_nginx: true

new_stager_percent: 25

new_stager_email_regexp: '.*@test.com'

staging_upload_user: stager

staging_upload_password: definitelychangeme

allow_registration: true

uaa:

enabled: false

resource_id: cloud_controller

client_secret: aaaNxRJcx6cpv

admins:

- ani...@test.com

stager:

max_staging_duration: 120

max_active_tasks: 20

queues:

- staging

ccdb:

user: ccadmin

password: changemechangeme

address: 172.24.4.230

port: 5524

pool_size: 10

dbname: appcloud

roles:

- tag: admin

password: changemechangeme

databases:

- tag: cc

vcap_redis:

address: 172.24.4.231

port: 5454

password: changemechangemechangeme

maxmemory: 1000000000 # 1GB

dea:

max_memory: 1024

nfs_server:

address: 172.24.4.232

network: 172.24.4.224/28

router:

status:

port: 8080

user: router

password: changemechangemechangeme

uaa:

cc:

token_secret: aaabxaiC371JM

client_secret: $2a$08$dahioBqSkqa1AbLvaqkLoe5W0aOPN3Ia9W0xkeB926G.AZJhq1SsK

batch:

username: do0H2AKay2jAc

password: FSCTiplI5Q83n

skaar

unread,

Sep 19, 2012, 3:40:40 PM9/19/12

to bosh-...@cloudfoundry.org

Is "cloudfoundry.test" a wild carded DNS record in your environment? You will need it pointing to your router IP (or a load balancer fronting the router ip) - if you just want to test the vmc client - and you don't have DNS set up yet - you can locally add api.cloudfoundry.test to point to the router IP (which from your manifest looks like it is: 172.24.4.227)

/skaar

animesh nandanwar

unread,

Sep 19, 2012, 4:22:06 PM9/19/12

to bosh-...@cloudfoundry.org

Thanks Skaar,

I do not have DNS setup and hence added " 172.24.4.227 api.cloudfoundry.test" to /etc/hosts file.

But still is does not work.

stack@esg-dell-c4-s07:~$ vmc target api.cloudfoundry.test

Host is not available or is not valid: 'http://api.cloudfoundry.test'

Would you like see the response? [yN]: y

Error (JSON 404): <html>

<head><title>404 Not Fo...

Thanks,

Animesh

skaar

unread,

Sep 19, 2012, 9:28:24 PM9/19/12

to bosh-...@cloudfoundry.org

what is the output of:

bosh vms cloudfoundry

/skaar

animesh nandanwar

unread,

Sep 19, 2012, 9:45:58 PM9/19/12

to bosh-...@cloudfoundry.org

Here is the output

root@inception-vm:/var/vcap/deployments# bosh vms cloudfoundry

Deployment cloudfoundry

Director task 21

Task 21 done

+---------------------+---------+----------------+-------------------------+

+---------------------+---------+----------------+-------------------------+

| dea/0 | running | dea | 10.0.0.6 |

| dea/1 | running | dea | 10.0.0.9 |

| dea/2 | running | dea | 10.0.0.11 |

| dea/3 | running | dea | 10.0.0.16 |

+---------------------+---------+----------------+-------------------------+

VMs total: 14

root@inception-vm:/var/vcap/deployments#

Thanks,

Animesh

Reply all

Reply to author

Forward