Re: cf-stub.yml example with minimum or required info
Ali
Sorry I did not see this reply from Gwenn Etourneau.
toggle quoted message
Show quoted text
After “bosh cck”, it found 6 problems and then I tried option 2 to reboot and also tried option 3 to recreate VM, none of them fixed the issue, but I noticed the problematic VMs are using duplicate IPs, my network section in the manifest has 2 networks (cf1 and cf2) and there is no overlab, see network section below. For example the VM router_z1/0 (vm-c36efd49-7ac7-4b90-9779-b5192408e4a6) got the ip 10.195.166.110, and another VM from same deployment (vm-2b532db0-36df-433d-8132-89c76a9c81c3) got the same ip 10.195.166.110 I tried also removing the section “jobs" and go with defaults which is generated by spiff and run into same issue, do I have to statically assign IP address to each job? M-20JW:cf-release ahmeali$ bosh cck Performing cloud check... Processing deployment manifest ------------------------------ Director task 141 Started scanning 26 vms Started scanning 26 vms > Checking VM states. Done (00:00:10) Started scanning 26 vms > 20 OK, 6 unresponsive, 0 missing, 0 unbound, 0 out of sync. Done (00:00:00) Done scanning 26 vms (00:00:10) Started scanning 0 persistent disks Started scanning 0 persistent disks > Looking for inactive disks. Done (00:00:00) Started scanning 0 persistent disks > 0 OK, 0 missing, 0 inactive, 0 mount-info mismatch. Done (00:00:00) Done scanning 0 persistent disks (00:00:00) Task 141 done Started 2015-06-12 20:03:17 UTC Finished 2015-06-12 20:03:27 UTC Duration 00:00:10 Scan is complete, checking if any problems found... Found 6 problems Problem 1 of 6: Unknown VM (vm-e4da0933-52ba-473f-903d-a9ee09d1671f) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Problem 2 of 6: hm9000_z1/0 (vm-5ea4c90d-247e-43ad-a189-ff4d2d781854) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Problem 3 of 6: router_z1/0 (vm-c36efd49-7ac7-4b90-9779-b5192408e4a6) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Problem 4 of 6: nfs_z1/0 (vm-868e2bb9-ac61-49f0-86fb-38d5c338201b) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Problem 5 of 6: router_z2/0 (vm-773e83ee-c97f-4aa4-b163-d09a703a4678) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Problem 6 of 6: ha_proxy_z1/0 (vm-643f3c80-93cb-4ccf-9239-1f85a407a317) is not responding. 1. Ignore problem 2. Reboot VM 3. Recreate VM using last known apply spec 4. Delete VM reference (DANGEROUS!) Please choose a resolution [1 - 4]: 2 Below is the list of resolutions you've provided Please make sure everything is fine and confirm your changes 1. Unknown VM (vm-e4da0933-52ba-473f-903d-a9ee09d1671f) is not responding Reboot VM 2. hm9000_z1/0 (vm-5ea4c90d-247e-43ad-a189-ff4d2d781854) is not responding Reboot VM 3. router_z1/0 (vm-c36efd49-7ac7-4b90-9779-b5192408e4a6) is not responding Reboot VM 4. nfs_z1/0 (vm-868e2bb9-ac61-49f0-86fb-38d5c338201b) is not responding Reboot VM 5. router_z2/0 (vm-773e83ee-c97f-4aa4-b163-d09a703a4678) is not responding Reboot VM 6. ha_proxy_z1/0 (vm-643f3c80-93cb-4ccf-9239-1f85a407a317) is not responding Reboot VM Apply resolutions? (type 'yes' to continue): yes Applying resolutions... Director task 142 Started applying problem resolutions Started applying problem resolutions > unresponsive_agent 154: Reboot VM. Failed: Agent is responding now, skipping resolution (00:00:00) Started applying problem resolutions > unresponsive_agent 184: Reboot VM. Failed: Agent is responding now, skipping resolution (00:00:00) Started applying problem resolutions > unresponsive_agent 177: Reboot VM. Done (00:00:30) Started applying problem resolutions > unresponsive_agent 179: Reboot VM. Failed: Agent is responding now, skipping resolution (00:00:00) Started applying problem resolutions > unresponsive_agent 185: Reboot VM. Done (00:00:11) Started applying problem resolutions > unresponsive_agent 180: Reboot VM. Done (00:00:29) Failed applying problem resolutions (00:01:10) Task 142 done Started 2015-06-12 20:04:01 UTC Finished 2015-06-12 20:05:11 UTC Duration 00:01:10 Cloudcheck is finished Network section in cf-stub.yml --- name: cf director_uuid: b9a1bf7b-952f-48e1-a496-f6543d7a782c releases: - {name: cf, version: latest} networks: - name: cf1 subnets: - range: 10.195.166.0/23 gateway: 10.195.166.1 static: - 10.195.166.105 - 10.195.166.135 reserved: # .1 is special - 10.195.166.2 - 10.195.166.104 - 10.195.166.188 - 10.194.177.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.195.166.x' - name: cf2 subnets: - range: 10.195.166.0/23 gateway: 10.195.166.1 static: - 10.195.166.136 - 10.195.166.166 reserved: # .1 is special - 10.195.166.2 - 10.195.166.104 - 10.195.166.188 - 10.194.177.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.195.166.x' Thank you From: Gwenn Etourneau <getourneau(a)pivotal.io<mailto:getourneau(a)pivotal.io>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Monday, June 8, 2015 at 6:16 PM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info Try to make bosh cck before bosh deploy. On Tue, Jun 9, 2015 at 3:43 AM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com<mailto:ahmeali(a)cisco.com>> wrote:
I was able to fix this by copying from the generated cf-deployment.yml and use it in cf-stub.yml after changing cf release and jobs section. Now "bosh deploy" works but not complete, running into an issue I think has to do with jobs/nodes misconfigured, not sure what are the list of jobs/nodes I need to include and the properties of each one, any idea where I can find information about the list of jobs/nodes and properties for each such as templates/network ..etc? "Bosh vms” shows some Vms in “unresponsive agent” and unknown job. +------------------------------------+--------------------+---------------+----------------+ | Job/index | State | Resource Pool | IPs | +------------------------------------+--------------------+---------------+----------------+ | unknown/unknown | unresponsive agent | | | | unknown/unknown | unresponsive agent | | | | unknown/unknown | unresponsive agent | | | | unknown/unknown | unresponsive agent | | | | unknown/unknown | unresponsive agent | | | | unknown/unknown | unresponsive agent | | | | unknown/unknown | running | medium_z1 | 10.195.166.106 | | unknown/unknown | running | router_z1 | 10.195.166.108 | | unknown/unknown | running | small_z1 | 10.195.166.141 | | api_z1/0 | running | large_z1 | 10.195.166.139 | | api_z2/0 | running | large_z2 | 10.195.166.107 | | clock_global/0 | running | medium_z1 | 10.195.166.140 | | consul_z1/0 | running | medium_z1 | 10.195.166.122 | | consul_z2/0 | running | medium_z2 | 10.195.166.153 | | etcd_z1/0 | running | medium_z1 | 10.195.166.119 | | etcd_z1/1 | running | medium_z1 | 10.195.166.120 | | etcd_z2/0 | running | medium_z2 | 10.195.166.149 | | hm9000_z1/0 | running | medium_z1 | 10.195.166.142 | | hm9000_z2/0 | running | medium_z2 | 10.195.166.109 | | loggregator_trafficcontroller_z1/0 | running | small_z1 | 10.195.166.145 | | loggregator_trafficcontroller_z2/0 | running | small_z2 | 10.195.166.112 | | loggregator_z1/0 | running | medium_z1 | 10.195.166.144 | | loggregator_z2/0 | running | medium_z2 | 10.195.166.111 | | login_z1/0 | running | medium_z1 | 10.195.166.138 | | postgres_z1/0 | running | medium_z1 | 10.195.166.117 | | routing_api_z1/0 | running | medium_z1 | 10.195.166.121 | | routing_api_z2/0 | running | medium_z2 | 10.195.166.152 | | runner_z1/0 | running | runner_z1 | 10.195.166.143 | | runner_z2/0 | running | runner_z2 | 10.195.166.110 | | stats_z1/0 | running | small_z1 | 10.195.166.136 | | uaa_z1/0 | running | medium_z1 | 10.195.166.137 | | uaa_z2/0 | running | medium_z2 | 10.195.166.105 | +------------------------------------+--------------------+---------------+----------------+ VMs total: 32 Started preparing deployment > Binding existing deployment. Failed: Timed out sending `get_state' to eabc55f7-b402-42f7-85b5-e3732306b813 after 45 seconds (00:02:15) Error 450002: Timed out sending `get_state' to eabc55f7-b402-42f7-85b5-e3732306b813 after 45 seconds Thanks Ali From: AHMED ALI <ahmeali(a)cisco.com<mailto:ahmeali(a)cisco.com>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Friday, June 5, 2015 at 10:45 AM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info That fixed the error, thank you! And run into another error :) M-20JW:cf-release ali00$ bosh deployment cf-deployment.yml Deployment set to `/Users/ali00/deployments/cf-release/cf-deployment.yml' M-20JW:cf-release ali00$ ./generate_deployment_manifest vsphere cf-stub.yml > cf-deployment.yml M-20JW:cf-release ali00$ bosh deploy Processing deployment manifest ------------------------------ Getting deployment properties from director... Compiling deployment manifest... Please review all changes carefully Deploying --------- Deployment name: `cf-deployment.yml' Director name: `bosh2' Are you sure you want to deploy? (type 'yes' to continue): yes Director task 38 Started unknown Started unknown > Binding deployment. Done (00:00:00) Error 140002: Template `consul_agent' (job `consul_z1') references an unknown release `cf' Task 38 error For a more detailed error report, run: bosh task 38 --debug M-20JW:cf-release ali00$ How can construct the section in cf-stub to provide correct cf release which I think should be cf-210 in my case (not sure)? Modified networks part in my cf-stub.yml ------------------------------------------------------- releases: - name: cf-210 version: latest networks: - name: cf1 subnets: - range: 10.195.166.0/23<http://10.195.166.0/23> gateway: 10.195.166.1 static: - 10.195.166.104 - 10.195.166.125 reserved: # .1 is special - 10.195.166.2 - 10.195.166.101 - 10.195.166.147 - 10.194.177.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.195.166.x' - name: cf2 subnets: - range: 10.195.166.0/23<http://10.195.166.0/23> gateway: 10.195.166.1 static: - 10.195.166.126 - 10.195.166.146 reserved: # .1 is special - 10.195.166.2 - 10.195.166.101 - 10.195.166.147 - 10.194.177.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.195.166.x' ------------------------------------------------ Thanks Ali From: CF Runtime <cfruntime(a)gmail.com<mailto:cfruntime(a)gmail.com>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Friday, June 5, 2015 at 10:11 AM To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info Hi Ahmed, It looks like you haven't allocated enough IPs in your network. The line for reserved IPs "10.166.166.104 - 10.166.166.115" should be increased to have at least 19 IPs. You'll need to decrease the number of reserved addresses as well in order to increase the number of available IPs in your network. We recommend "10.166.166.104 - 10.166.166.123" for available IPs and "10.166.166.124 - 10.194.167.254" for your reserved range. If you're tracking our current develop branch and not the final releases you should look in cf-release/spec/fixtures/vsphere/cf-stub.yml for the stub that we use to do our vsphere acceptance tests. Best, Zachary Auerbach + Dan Lavine CF Runtime Team On Thu, Jun 4, 2015 at 2:18 PM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com<mailto:ahmeali(a)cisco.com>> wrote: Thanks Joseph for your help, please see the error below: 20JXXW:cf-release ali00$ ./generate_deployment_manifest vsphere cf-stub.yml > cf-deployment.yml 2015/06/04 13:34:50 error generating manifest: unresolved nodes: (( static_ips(12) )) in ./templates/cf-infrastructure-vsphere.yml jobs.[5].networks.[0].static_ips (( static_ips(16) )) in ./templates/cf-infrastructure-vsphere.yml jobs.[8].networks.[0].static_ips (( static_ips(14, 15) )) in ./templates/cf-infrastructure-vsphere.yml jobs.[15].networks.[0].static_ips (( static_ips(17, 18, 19) )) in ./templates/cf-infrastructure-vsphere.yml jobs.[17].networks.[0].static_ips (( jobs.postgres_z1.networks.cf1.static_ips.[0] )) in dynaml properties.databases.address (( properties.databases.address )) in dynaml properties.ccdb.address (( properties.databases.address )) in dynaml properties.uaadb.address M-2XX0JW:cf-release ali00$ I do not want to bug cf-bosh alias with every error I run into so my ask is to find a sample of cf-stub.yml with all minimum required values, Im sure Im missing a lot :), the sample online here http://docs.cloudfoundry.org/deploying/cf-stub-vsphere.html, when I first run it I got an error regarding “Error 40001: Required property `range' was not specified in object”, then after I added “range” property I got the error above. Im looking for building a POC CF with minimum effort, do have one network (10.166.166.0/23<http://10.166.166.0/23>) and vSphere 5.x, I want to use it for both CF networks (cf1 and cf2), not sure how many Ips I need on each network, and if I have to specify nodes spec and vsphere info in cf-stub since I do not see section for it? I also tried bosh-lite and it worked fine on Ubuntu 14. Here is my cf-stub.yml in case you want to have a look # The following line helps maintain current documentation at http://docs.cloudfoundry.org. # code_snippet cf-stub-vsphere start --- name: cloudfoundry director_uuid: b9a1bf7b-952f-48e1-a496-f6543d7a782c releases: - name: cf-210 version: latest networks: - name: cf1 subnets: - range: 10.166.166.0/23<http://10.166.166.0/23> gateway: 10.195.76.1 static: - 10.166.166.104 - 10.166.166.115 reserved: # .1 is special - 10.166.166.2 - 10.166.166.101 - 10.166.166.120 - 10.194.167.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.166.166.x' - name: cf2 subnets: - range: 10.166.166.0/23<http://10.166.166.0/23> gateway: 10.166.166.1 static: - 10.166.166.120 - 10.166.166.140 reserved: # .1 is special - 10.166.166.2 - 10.166.166.101 - 10.166.166.120 - 10.195.167.254 # .255 is special dns: [10.166.168.183] cloud_properties: name: '10.166.166.x' jobs: ha_proxy_z1: properties: ha_proxy: disable_http: true properties: cc: droplets: droplet_directory_key: the_key buildpacks: buildpack_directory_key: bd_key staging_upload_user: username staging_upload_password: password bulk_api_password: password db_encryption_key: the_key dea_next: disk_mb: 2048 memory_mb: 1024 loggregator_endpoint: shared_secret: loggregator_endpoint_secret nats: user: nats_user password: nats_password router: enable_ssl: true ssl_cert: | -----BEGIN CERTIFICATE----- MIIDBjCCAe4CCQCz3nn1SWrDdTANBgkqhkiG9w0BAQUFADBFMQswCQYDVQQGEwJB VTETMBEGA1UECBMKU29tZS1TdGF0ZTEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0 cyBQdHkgTHRkMB4XDTE1MDMwMzE4NTMyNloXDTE2MDMwMjE4NTMyNlowRTELMAkG A1UEBhMCQVUxEzARBgNVBAgTClNvbWUtU3RhdGUxITAfBgNVBAoTGEludGVybmV0 IFdpZGdpdHMgUHR5IEx0ZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AKtTK9xq/ycRO3fWbk1abunYf9CY6sl0Wlqm9UPMkI4j0itY2OyGyn1YuCCiEdM3 b8guGSWB0XSL5PBq33e7ioiaH98UEe+Ai+TBxnJsro5WQ/TMywzRDhZ4E7gxDBav 88ZY+y7ts0HznfxqEIn0Gu/UK+s6ajYcIy7d9L988+hA3K1FSdes8MavXhrI4xA1 fY21gESfFkD4SsqvrkISC012pa7oVw1f94slIVcAG+l9MMAkatBGxgWAQO6kxk5o oH1Z5q2m0afeQBfFqzu5lCITLfgTWCUZUmbF6UpRhmD850/LqNtryAPrLLqXxdig OHiWqvFpCusOu/4z1uGC5xECAwEAATANBgkqhkiG9w0BAQUFAAOCAQEAV5RAFVQy 8Krs5c9ebYRseXO6czL9/Rfrt/weiC1XLcDkE2i2yYsBXazMYr58o4hACJwe2hoC bihBZ9XnVpASEYHDLwDj3zxFP/bTuKs7tLhP7wz0lo8i6k5VSPAGBq2kjc/cO9a3 TMmLPks/Xm42MCSWGDnCEX1854B3+JK3CNEGqSY7FYXU4W9pZtHPZ3gBoy0ymSpg mpleiY1Tbn5I2X7vviMW7jeviB5ivkZaXtObjyM3vtPLB+ILpa15ZhDSE5o71sjA jXqrE1n5o/GXHX+1M8v3aJc30Az7QAqWohW/tw5SoiSmVQZWd7gFht9vSzaH2WgO LwcpBC7+cUJEww== -----END CERTIFICATE----- ssl_key: | -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAq1Mr3Gr/JxE7d9ZuTVpu6dh/0JjqyXRaWqb1Q8yQjiPSK1jY 7IbKfVi4IKIR0zdvyC4ZJYHRdIvk8Grfd7uKiJof3xQR74CL5MHGcmyujlZD9MzL DNEOFngTuDEMFq/zxlj7Lu2zQfOd/GoQifQa79Qr6zpqNhwjLt30v3zz6EDcrUVJ 16zwxq9eGsjjEDV9jbWARJ8WQPhKyq+uQhILTXalruhXDV/3iyUhVwAb6X0wwCRq 0EbGBYBA7qTGTmigfVnmrabRp95AF8WrO7mUIhMt+BNYJRlSZsXpSlGGYPznT8uo 22vIA+ssupfF2KA4eJaq8WkK6w67/jPW4YLnEQIDAQABAoIBAQCDVqpcOoZKK9K8 Bt3eXQKEMJ2ji2cKczFFJ5MEm9EBtoJLCryZbqfSue3Fzpj9pBUEkBpk/4VT5F7o 0/Vmc5Y7LHRcbqVlRtV30/lPBPQ4V/eWtly/AZDcNsdfP/J1fgPSvaoqCr2ORLWL qL/vEfyIeM4GcWy0+JMcPbmABslw9O6Ptc5RGiP98vCLHQh/++sOtj6PH1pt+2X/ Uecv3b1Hk/3Oe+M8ySorJD3KA94QTRnKX+zubkxRg/zCAki+as8rQc/d+BfVG698 ylUT5LVLNuwbWnffY2Zt5x5CDqH01mJnHmxzQEfn68rb3bGFaYPEn9EP+maQijv6 SsUM9A3lAoGBAODRDRn4gEIxjPICp6aawRrMDlRc+k6IWDF7wudjxJlaxFr2t7FF rFYm+jrcG6qMTyq+teR8uHpcKm9X8ax0L6N6gw5rVzIeIOGma/ZuYIYXX2XJx5SW SOas1xW6qEIbOMv+Xu9w2SWbhTgyRmtlxxjr2e7gQLz9z/vuTReJpInnAoGBAMMW sq5lqUfAQzqxlhTobQ7tnB48rUQvkGPE92SlDj2TUt9phek2/TgRJT6mdcozvimt JPhxKg3ioxG8NPmN0EytjpSiKqlxS1R2po0fb75vputfpw16Z8/2Vik+xYqNMTLo SpeVkHu7fbtNYEK2qcU44OyOZ/V+5Oo9TuBIFRhHAoGACkqHhwDRHjaWdR2Z/w5m eIuOvF3lN2MWZm175ouynDKDeoaAsiS2VttB6R/aRFxX42UHfoYXC8LcTmyAK5zF 8X3SMf7H5wtqBepQVt+Gm5zGSSqLcEnQ3H5c+impOh105CGoxt0rk4Ui/AeRIalv C70AJOcvD3eu5aFq9gDe/1ECgYBAhkVbASzYGnMh+pKVH7rScSxto8v6/XBYT1Ez 7JOlMhD667/qvtFJtgIHkq7qzepbhnTv5x3tscQVnZY34/u9ILpD1s8dc+dibEvx 6S/gYLVorB5ois/DLMqaobRcew6Gs+XX9RPwmLahOJpZ9mh4XrOmCgPAYtP71YM9 ExpHCQKBgQCMMDDWGMRdFMJgXbx1uMere7OoniBdZaOexjbglRh1rMVSXqzBoU8+ yhEuHGAsHGWQdSBHnqRe9O0Bj/Vlw2VVEaJeL1ewRHb+jXSnuKclZOJgMsJAvgGm SOWIahDrATA4g1T6yLBWQPhj3ZXD3eCMxT1Q3DvpG1DjgvXwmXQJAA== -----END RSA PRIVATE KEY----- cipher_suites: TLS_RSA_WITH_RC4_128_SHA:TLS_RSA_WITH_AES_128_CBC_SHA status: user: router_user password: router_password login: logout: redirect: parameter: disable: false uaa: admin: client_secret: admin_secret batch: username: batch_username password: batch_password cc: client_secret: cc_client_secret clients: app-direct: secret: app-direct_secret developer_console: secret: developer_console_secret login: secret: login_client_secret notifications: secret: notification_secret doppler: secret: doppler_secret cloud_controller_username_lookup: secret: cloud_controller_username_lookup_secret gorouter: secret: gorouter_secret jwt: verification_key: vk signing_key: sk scim: users: - admin|fakepassword|scim.write,scim.read,openid,cloud_controller.admin,doppler.firehose # code_snippet cf-stub-vsphere end # The previous line helps maintain current documentation at http://docs.cloudfoundry.org. Thank you Ahmed From: CF Runtime <cfruntime(a)gmail.com<mailto:cfruntime(a)gmail.com>> Reply-To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Date: Wednesday, June 3, 2015 at 5:40 PM To: "cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>" <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info Hi Ali, We try to keep those docs up to date, but it is possible they are missing some pieces. Can you tell me what errors you are getting? Joseph Palermo CF Runtime Team _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|