Date   

Re: cf-stub.yml example with minimum or required info

Ali
 

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

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

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


Re: cf-stub.yml example with minimum or required info

Gwenn Etourneau
 

Try to make bosh cck before bosh deploy.

On Tue, Jun 9, 2015 at 3:43 AM, Ahmed Ali (ahmeali) <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>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
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>
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

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

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>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
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>
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>
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) 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

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

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>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Wednesday, June 3, 2015 at 5:40 PM
To: "cf-bosh(a)lists.cloudfoundry.org" <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
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


Re: how to add openjdk 1.8 to my project

Gwenn Etourneau
 

Up to you but nornally you just need to create a package to install openJdk,
for example
https://github.com/cloudfoundry-community/jenkins-boshrelease/tree/master/packages
we install the jre, should be mostly the same script to install the jdk you
want.

But before that maybe you should understand how to create a bosh release.

On Mon, Jun 8, 2015 at 11:17 PM, James Bayer <jbayer(a)pivotal.io> wrote:

the uaa needs java

the java buildpack builds and hosts the openjdk jre's on a repository:
https://github.com/cloudfoundry/java-buildpack/blob/master/config/repository.yml

you'll just need some help to find out where exactly. hopefully someone
can point out how to do it.

On Mon, Jun 8, 2015 at 6:28 AM, ramonskie <ramon.makkelie(a)klm.com> wrote:

i'm trying to create a bosh release that needs openjdk 1.8
but i have no clue on how to do this

i know that you can do it with bosh-gen --apt option
and then it downloads a massive amount of dependencies

but when i check other projects they all depend on openjdk-*.*.tar.gz
and i searched that net but i can't find them so i assume that you need to
create the package yourself
so i'm wondering if we have some global packages?
or maby point me in to the right directions of how you should do it



--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/how-to-add-openjdk-1-8-to-my-project-tp142.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


--
Thank you,

James Bayer

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: how to add openjdk 1.8 to my project

ramonskie
 

i understand somehow bosh works not of al of it
i created this a 2 months ago
https://github.com/cloudfoundry-community/bosh-scaler-boshrelease

and i understand how to extract it and use the packages script
but what i was wondering where/how did you get the sources of the jre/jdk
and packaged it



--
View this message in context: http://cf-bosh.70367.x6.nabble.com/how-to-add-openjdk-1-8-to-my-project-tp142p148.html
Sent from the CF BOSH mailing list archive at Nabble.com.


Re: how to add openjdk 1.8 to my project

Gwenn Etourneau
 

Example :
Get the file here for example ,
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

You need to add to the blobstore to be able to use it, for dev local is
enough.
Or add it into the src directory which is not a good pratice as you will
push it to your source control system.
Once your final release is ready you can package all in one tarball.

Please read https://bosh.io/docs/create-release.html

On Tue, Jun 9, 2015 at 4:51 PM, ramonskie <ramon.makkelie(a)klm.com> wrote:

i understand somehow bosh works not of al of it
i created this a 2 months ago
https://github.com/cloudfoundry-community/bosh-scaler-boshrelease

and i understand how to extract it and use the packages script
but what i was wondering where/how did you get the sources of the jre/jdk
and packaged it



--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/how-to-add-openjdk-1-8-to-my-project-tp142p148.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Bosh Job and Package dependency problem.

Xue Zhi Yong <zhiyxue@...>
 

I have five Docker image which have following runtime dependency:
The Docker image 1 and Docker image 2 must be run before Docker image 3, 4 ,5
I create five bosh Jobs for them, but bosh document said can't set dependency between jobs. So when the Docker image 4 job will failed when it's run before image 3.
I'm not sure if it works when I create package for Docker image 1, 2, 3, and job for Docker image 4,5. In these two jobs to start all direct depend and indirectly depend image.


Anyone can give correct package and job skeleton and dependcy?


Re: Deployment manifest not recognized by BOSH

Kinjal Doshi
 

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it has
comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using '!'
sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal




Re: Bosh Job and Package dependency problem.

Gwenn Etourneau
 

Right there is no dependency between job, but I think in the manifest you
can put an order

job:

-name: docker1
...

-name:docker2
....


etc...

But dependency don't really exist in bosh.

On Tue, Jun 9, 2015 at 6:04 PM, Xue Zhi Yong <zhiyxue(a)126.com> wrote:

I have five Docker image which have following runtime dependency:
The Docker image 1 and Docker image 2 must be run before Docker image 3, 4
,5
I create five bosh Jobs for them, but bosh document said can't set
dependency between jobs. So when the Docker image 4 job will failed when
it's run before image 3.
I'm not sure if it works when I create package for Docker image 1, 2, 3,
and job for Docker image 4,5. In these two jobs to start all direct depend
and indirectly depend image.

Anyone can give correct package and job skeleton and dependcy?




_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: Deployment manifest not recognized by BOSH

Gwenn Etourneau
 

Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are not a
yaml field.
You script using to_yaml is just wrong, nothing related to bosh.

On Tue, Jun 9, 2015 at 7:08 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it
has comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using
'!' sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal



_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: Bosh Job and Package dependency problem.

Xue Zhi Yong <zhiyxue@...>
 

But How to control these jobs run sequence?
I tried these jobs will run concurrently.

在 2015年6月9日,21:38,Gwenn Etourneau <getourneau(a)pivotal.io> 写道:

Right there is no dependency between job, but I think in the manifest you can put an order

job:

-name: docker1
...

-name:docker2
....


etc...

But dependency don't really exist in bosh.





On Tue, Jun 9, 2015 at 6:04 PM, Xue Zhi Yong <zhiyxue(a)126.com> wrote:
I have five Docker image which have following runtime dependency:

The Docker image 1 and Docker image 2 must be run before Docker image 3, 4 ,5
I create five bosh Jobs for them, but bosh document said can't set dependency between jobs. So when the Docker image 4 job will failed when it's run before image 3.
I'm not sure if it works when I create package for Docker image 1, 2, 3, and job for Docker image 4,5. In these two jobs to start all direct depend and indirectly depend image.

Anyone can give correct package and job skeleton and dependcy?




_______________________________________________
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


Re: Bosh Job and Package dependency problem.

Lev Berman
 

You can not control the sequence when there are several compilation workers
but you can set the workers number to 1. In the manifest:

compilation:
workers: 1

Also, you can run all of the containers in one job.

On Tue, Jun 9, 2015 at 5:44 PM, 126 Mail Same Pass With Sins <
zhiyxue(a)126.com> wrote:

But How to control these jobs run sequence?
I tried these jobs will run concurrently.



在 2015年6月9日,21:38,Gwenn Etourneau <getourneau(a)pivotal.io> 写道:

Right there is no dependency between job, but I think in the manifest
you can put an order

job:

-name: docker1
...

-name:docker2
....


etc...

But dependency don't really exist in bosh.





On Tue, Jun 9, 2015 at 6:04 PM, Xue Zhi Yong <zhiyxue(a)126.com> wrote:

I have five Docker image which have following runtime dependency:
The Docker image 1 and Docker image 2 must be run before Docker image
3, 4 ,5
I create five bosh Jobs for them, but bosh document said can't set
dependency between jobs. So when the Docker image 4 job will failed when
it's run before image 3.
I'm not sure if it works when I create package for Docker image 1, 2, 3,
and job for Docker image 4,5. In these two jobs to start all direct depend
and indirectly depend image.

Anyone can give correct package and job skeleton and dependcy?




_______________________________________________
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


--
Lev Berman

Altoros - Cloud Foundry deployment, training and integration

Github
*: https://github.com/ldmberman <https://github.com/ldmberman>*


Re: Deployment manifest not recognized by BOSH

Kinjal Doshi
 

Hi,

I am aware that this does not have anything to do with BOSH but when a ruby
object is converted to yaml, this format is appended automatically.

Couple of months ago, I was able to deploy with a manifest of this format
but now on a new BOSH deployment, I am not able to.

I am using the default yaml gem in ruby to transform from object to yaml
which appends this type of info for each objects that it transforms.

Any ideas would be great on this, or are you saying that the manifest is
invalid with this '!' info?

Thanks,
Kinjal


On Tue, Jun 9, 2015 at 7:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are not
a yaml field.
You script using to_yaml is just wrong, nothing related to bosh.


On Tue, Jun 9, 2015 at 7:08 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it
has comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using
'!' sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal



_______________________________________________
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


Re: Bosh Job and Package dependency problem.

Sabha
 

IIRC, Bosh would kick off the jobs in the order you have declared (serial).
So, you can have jobs 1 and 2 go first, then the others... If there are
multiple job templates all bundled to run within the same vm or job
definition, those they are concurrent.

-Sabha



--
View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Bosh-Job-and-Package-dependency-problem-tp150p157.html
Sent from the CF BOSH mailing list archive at Nabble.com.


Re: Deployment manifest not recognized by BOSH

John Wong
 

I am not sure why it fails now, but my two cents are why not just
serialized the object?

In the case of python, i would see that if I try to save an object like in
your case: http://pyyaml.org/wiki/PyYAMLDocumentation#Objects
But I would write a method to convert my object to basic dictionary (in
Python), which I can easily convert into YAML using pyyaml library.

John

On Tue, Jun 9, 2015 at 11:47 AM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am aware that this does not have anything to do with BOSH but when a
ruby object is converted to yaml, this format is appended automatically.

Couple of months ago, I was able to deploy with a manifest of this format
but now on a new BOSH deployment, I am not able to.

I am using the default yaml gem in ruby to transform from object to yaml
which appends this type of info for each objects that it transforms.

Any ideas would be great on this, or are you saying that the manifest is
invalid with this '!' info?

Thanks,
Kinjal


On Tue, Jun 9, 2015 at 7:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are not
a yaml field.
You script using to_yaml is just wrong, nothing related to bosh.


On Tue, Jun 9, 2015 at 7:08 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it
has comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using
'!' sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this
error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal



_______________________________________________
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

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: Deployment manifest not recognized by BOSH

Dmitriy Kalinin
 

With YAML it's very much different to have

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*

vs

*---*
*networks: *
*- **type: dynamic*

First represents real classes being serialized, but the second shows
regular hashes (maps). There is no way bosh can deserialize the first
example since it does not have these objects.

On Tue, Jun 9, 2015 at 11:26 AM, John Wong <gokoproject(a)gmail.com> wrote:

I am not sure why it fails now, but my two cents are why not just
serialized the object?

In the case of python, i would see that if I try to save an object like in
your case: http://pyyaml.org/wiki/PyYAMLDocumentation#Objects
But I would write a method to convert my object to basic dictionary (in
Python), which I can easily convert into YAML using pyyaml library.

John

On Tue, Jun 9, 2015 at 11:47 AM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I am aware that this does not have anything to do with BOSH but when a
ruby object is converted to yaml, this format is appended automatically.

Couple of months ago, I was able to deploy with a manifest of this format
but now on a new BOSH deployment, I am not able to.

I am using the default yaml gem in ruby to transform from object to yaml
which appends this type of info for each objects that it transforms.

Any ideas would be great on this, or are you saying that the manifest is
invalid with this '!' info?

Thanks,
Kinjal


On Tue, Jun 9, 2015 at 7:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are
not a yaml field.
You script using to_yaml is just wrong, nothing related to bosh.


On Tue, Jun 9, 2015 at 7:08 PM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

would be great if someone could please help me with this matter.

Regards,
Kinjal

On Mon, Jun 8, 2015 at 6:25 PM, Kinjal Doshi <kindoshi(a)gmail.com>
wrote:

Hi,

I am trying to use manifest that is generated using the to_yaml
transformation technique in Ruby.

However, this deployment manifest is not recognized by bosh because it
has comments that detail the class names like:

*--- !ruby/object:DeploymentManifest *
*networks: *
*- !ruby/object:AWSDynamicNetworkBean *
* type: dynamic*
* cloud_properties: !ruby/object:AWSNetworkCPBean *
* security_groups: *
* - docker*
* - bosh*
* subnet: *
* name: default*
*- !ruby/object:AWSDynamicNetworkBean *
* type: vip*
* cloud_properties: {}*

As can be seen in above snippet, to_yaml adds object description using
'!' sign.

On using the command:

bosh deployment <manifest_file_path>

The following error is observed:

Usage: deployment [<filename>]

Removing the object details starting at '!' seems to resolve this
error.

However, this was not happening with previous version of bosh_cli. I
don't remember the previous version that I was using. Current version being
used by me is: bosh cli-1.2978.0

Would be great if some one can please help me with this matter.


Regards,
Kinjal



_______________________________________________
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

_______________________________________________
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


Re: Bosh Job and Package dependency problem.

Xue Zhi Yong <zhiyxue@...>
 

In my case, I create job for each container and all are run within same vm. So the result is out of control.


Except run all containers in one job. Is it possible that change some job to package, then add them as dependency for other jobs?

At 2015-06-10 01:15:54, "Sabha" <sabhap(a)pivotal.io> wrote:
IIRC, Bosh would kick off the jobs in the order you have declared (serial).
So, you can have jobs 1 and 2 go first, then the others... If there are
multiple job templates all bundled to run within the same vm or job
definition, those they are concurrent.

-Sabha



--
View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Bosh-Job-and-Package-dependency-problem-tp150p157.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Specifying proxies on the bosh-init cpi job (bosh-vsphere-cpi-release)

Allan Espinosa
 

Hi,

We need specify https_proxy to connected to our avcenters. We're able to do this when we deploy Bosh directors using bosh micro and multi-bosh setups. But I cannot get it running under bosh init.

I built a dev release from the latest master of bosh-vsphere-cpi-release that incorporates the proxy environment variables for the cpi job. However, as far as I understand from the logs below, bosh-init doesn't actually execute the job but the cpi binary directly:

manifest:

cloud_provider:
mbus: ...
properties:
agent: ...
blobstore: ...
cpi: &cpi
env:
http_proxy: http://myproxy.server:3182
https_proxy: myproxy.server:3182
no_proxy: 127.0.0.1
ntp: ...
vcenter: ...
template:
name: cpi
release: bosh-vsphere-cpi

properties:
...
cpi: *cpi
director:
...
env:
http_proxy: http://myproxy.server:9501
https_proxy: http://myproxy.server:9501
no_proxy: 127.0.0.1



BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

[cloud] 2015/06/10 00:50:03 DEBUG - Creating stemcell
[Cmd Runner] 2015/06/10 00:50:03 DEBUG - Running command: /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/jobs/cpi/bin/cpi
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stdout:
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stderr: /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:805:in `initialize': execution expired (HTTPClient::ConnectTimeoutError)
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:805:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:805:in `create_socket'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:752:in `block in connect'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:751:in `connect'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:609:in `query'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient/session.rb:164:in `query'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient.rb:1087:in `do_get_block'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient.rb:891:in `block in do_request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9
.1/gems/httpclient-2.4.0/lib/httpclient.rb:985:in `protect_keep_alive_disconnected'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient.rb:890:in `do_request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient.rb:778:in `request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclient-2.4.0/lib/httpclient.rb:684:in `post'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:29:in `invoke_method'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:13:in `invoke_method'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:45:in `block (3 levels) in finalize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:57:in `invoke_property'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:17:in `invoke_property'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:30:in `block (3 levels) in finalize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere/client.rb:16:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `client'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere/cloud.rb:18:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_vsphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `<top (required)>'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `load'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `<main>
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Successful: true (0)


--end snippet---

Am I setting the right environment variable in the right place? I get the same problem when I tried specifying the proxy environment variables for bosh-init itself:

https_proxy=http://myproxy:3182 http_proxy=http://myproxy:3182 BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

Thanks
Allan


Re: Specifying proxies on the bosh-init cpi job (bosh-vsphere-cpi-release)

Allan Espinosa
 

Argh sorry. Read the cpi job spec again

Apparently I have the hash at the wrong level.

s/cpi.env.http_proxy/env.http_proxy/

-----Original Message-----
From: cf-bosh-bounces(a)lists.cloudfoundry.org [mailto:cf-bosh-
bounces(a)lists.cloudfoundry.org] On Behalf Of Espinosa, Allan | Allan | OPS
Sent: Mierkoles, Hunyo 10, 2015 10:00 AM
To: cf-bosh(a)lists.cloudfoundry.org
Subject: [cf-bosh] Specifying proxies on the bosh-init cpi job (bosh-vsphere-
cpi-release)

Hi,

We need specify https_proxy to connected to our avcenters. We're able to
do this when we deploy Bosh directors using bosh micro and multi-bosh
setups. But I cannot get it running under bosh init.

I built a dev release from the latest master of bosh-vsphere-cpi-release that
incorporates the proxy environment variables for the cpi job. However, as far
as I understand from the logs below, bosh-init doesn't actually execute the
job but the cpi binary directly:

manifest:

cloud_provider:
mbus: ...
properties:
agent: ...
blobstore: ...
cpi: &cpi
env:
http_proxy: http://myproxy.server:3182
https_proxy: myproxy.server:3182
no_proxy: 127.0.0.1
ntp: ...
vcenter: ...
template:
name: cpi
release: bosh-vsphere-cpi

properties:
...
cpi: *cpi
director:
...
env:
http_proxy: http://myproxy.server:9501
https_proxy: http://myproxy.server:9501
no_proxy: 127.0.0.1



BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

[cloud] 2015/06/10 00:50:03 DEBUG - Creating stemcell [Cmd Runner]
2015/06/10 00:50:03 DEBUG - Running command:
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/jobs/cpi/bin/cpi
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stdout:
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stderr:
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `initialize': execution expired
(HTTPClient::ConnectTimeoutError)
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `create_socket'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:752:in `block in connect'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:751:in `connect'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:609:in `query'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:164:in `query'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:1087:in `do_get_block'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:891:in `block in do_request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9
.1/gems/httpclient-2.4.0/lib/httpclient.rb:985:in
`protect_keep_alive_disconnected'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:890:in `do_request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:778:in `request'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:684:in `post'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:29:in
`invoke_method'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:13:in
`invoke_method'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:45:in
`block (3 levels) in finalize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:57:in
`invoke_property'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:17:in
`invoke_property'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:30:in
`block (3 levels) in finalize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/client.rb:16:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `client'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/cloud.rb:18:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `initialize'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `new'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `<top (required)>'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `load'
from /home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `<main> [Cmd
Runner] 2015/06/10 00:50:35 DEBUG - Successful: true (0)


--end snippet---

Am I setting the right environment variable in the right place? I get the same
problem when I tried specifying the proxy environment variables for bosh-
init itself:

https_proxy=http://myproxy:3182 http_proxy=http://myproxy:3182
BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

Thanks
Allan
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: Specifying proxies on the bosh-init cpi job (bosh-vsphere-cpi-release)

Gwenn Etourneau
 

Indeed :)

On Wed, Jun 10, 2015 at 10:10 AM, Espinosa, Allan | Allan | OPS <
allan.espinosa(a)rakuten.com> wrote:

Argh sorry. Read the cpi job spec again

Apparently I have the hash at the wrong level.

s/cpi.env.http_proxy/env.http_proxy/

-----Original Message-----
From: cf-bosh-bounces(a)lists.cloudfoundry.org [mailto:cf-bosh-
bounces(a)lists.cloudfoundry.org] On Behalf Of Espinosa, Allan | Allan |
OPS
Sent: Mierkoles, Hunyo 10, 2015 10:00 AM
To: cf-bosh(a)lists.cloudfoundry.org
Subject: [cf-bosh] Specifying proxies on the bosh-init cpi job
(bosh-vsphere-
cpi-release)

Hi,

We need specify https_proxy to connected to our avcenters. We're able to
do this when we deploy Bosh directors using bosh micro and multi-bosh
setups. But I cannot get it running under bosh init.

I built a dev release from the latest master of bosh-vsphere-cpi-release
that
incorporates the proxy environment variables for the cpi job. However,
as far
as I understand from the logs below, bosh-init doesn't actually execute
the
job but the cpi binary directly:

manifest:

cloud_provider:
mbus: ...
properties:
agent: ...
blobstore: ...
cpi: &cpi
env:
http_proxy: http://myproxy.server:3182
https_proxy: myproxy.server:3182
no_proxy: 127.0.0.1
ntp: ...
vcenter: ...
template:
name: cpi
release: bosh-vsphere-cpi

properties:
...
cpi: *cpi
director:
...
env:
http_proxy: http://myproxy.server:9501
https_proxy: http://myproxy.server:9501
no_proxy: 127.0.0.1



BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

[cloud] 2015/06/10 00:50:03 DEBUG - Creating stemcell [Cmd Runner]
2015/06/10 00:50:03 DEBUG - Running command:
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/jobs/cpi/bin/cpi
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stdout:
[Cmd Runner] 2015/06/10 00:50:35 DEBUG - Stderr:
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `initialize': execution expired
(HTTPClient::ConnectTimeoutError)
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `new'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:805:in `create_socket'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:752:in `block in connect'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:751:in `connect'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:609:in `query'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient/session.rb:164:in `query'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:1087:in `do_get_block'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:891:in `block in do_request'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9
.1/gems/httpclient-2.4.0/lib/httpclient.rb:985:in
`protect_keep_alive_disconnected'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:890:in `do_request'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:778:in `request'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/httpclie
nt-2.4.0/lib/httpclient.rb:684:in `post'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:29:in
`invoke_method'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:13:in
`invoke_method'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:45:in
`block (3 levels) in finalize'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/soap/stub_adapter.rb:57:in
`invoke_property'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:17:in
`invoke_property'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/ruby_vim_sdk/vmodl/managed_object.rb:30:in
`block (3 levels) in finalize'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/client.rb:16:in `initialize'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `new'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/config.rb:43:in `client'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere/cloud.rb:18:in `initialize'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `new'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/lib/cloud/vsphere.rb:49:in `initialize'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `new'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/gem_home/ruby/1.9.1/gems/bosh_v
sphere_cpi-1.2922.0/bin/vsphere_cpi:23:in `<top (required)>'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `load'
from
/home/myuser/.bosh_init/installations/3a44e2b2-9fed-40a4-457c-
8e0696b5cba8/packages/vsphere_cpi/bin/vsphere_cpi:16:in `<main> [Cmd
Runner] 2015/06/10 00:50:35 DEBUG - Successful: true (0)


--end snippet---

Am I setting the right environment variable in the right place? I get
the same
problem when I tried specifying the proxy environment variables for bosh-
init itself:

https_proxy=http://myproxy:3182 http_proxy=http://myproxy:3182
BOSH_INIT_LOG_LEVEL=debug bosh-init deploy meta.yml

Thanks
Allan
_______________________________________________
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


Re: Bosh Job and Package dependency problem.

James Bayer
 

the docker bosh release supports "depends on" to start containers in a
particular order:
https://github.com/cf-platform-eng/docker-boshrelease/blob/master/examples/docker-aws.yml#L88-L89

On Tue, Jun 9, 2015 at 5:51 PM, Xue Zhi Yong <zhiyxue(a)126.com> wrote:

In my case, I create job for each container and all are run within same
vm. So the result is out of control.

Except run all containers in one job. Is it possible that change some job
to package, then add them as dependency for other jobs?



At 2015-06-10 01:15:54, "Sabha" <sabhap(a)pivotal.io> wrote:
IIRC, Bosh would kick off the jobs in the order you have declared (serial).
So, you can have jobs 1 and 2 go first, then the others... If there are
multiple job templates all bundled to run within the same vm or job
definition, those they are concurrent.

-Sabha



--
View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Bosh-Job-and-Package-dependency-problem-tp150p157.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
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

--
Thank you,

James Bayer

201 - 220 of 2761