|
Re: Bosh Job and Package dependency problem.
Sabha
Probably add some extra scripting to check if task1 and task2 are started
before kicking off other tasks by doing a sleep-wakeup-check-sleep loop till task1 and task2 are really running as they are all running on the same vm? -- View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Bosh-Job-and-Package-dependency-problem-tp150p166.html Sent from the CF BOSH mailing list archive at Nabble.com. |
|
|
|
Re: Bosh Job and Package dependency problem.
Gwenn Etourneau
Oh nice trick, but that's not a bosh default behavior, just use for monit
toggle quoted message
Show quoted text
https://github.com/cf-platform-eng/docker-boshrelease/blob/654808a4808af12117ecb86838fdb9c55d1b8c49/jobs/containers/monit . On Wed, Jun 10, 2015 at 2:10 PM, James Bayer <jbayer(a)pivotal.io> wrote:
the docker bosh release supports "depends on" to start containers in a |
|
|
|
Re: Bosh Job and Package dependency problem.
James Bayer
the docker bosh release supports "depends on" to start containers in a
toggle quoted message
Show quoted text
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 --
Thank you, James Bayer |
|
|
|
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 |
|
|
|
Re: Specifying proxies on the bosh-init cpi job (bosh-vsphere-cpi-release)
Allan Espinosa
Argh sorry. Read the cpi job spec again
toggle quoted message
Show quoted text
Apparently I have the hash at the wrong level. s/cpi.env.http_proxy/env.http_proxy/ -----Original Message----- |
|
|
|
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: 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.
toggle quoted message
Show quoted text
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). |
|
|
|
Re: Deployment manifest not recognized by BOSH
Dmitriy Kalinin
With YAML it's very much different to have
toggle quoted message
Show quoted text
*--- !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 |
|
|
|
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
toggle quoted message
Show quoted text
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, |
|
|
|
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
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 |
|
|
|
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? -- Lev Berman Altoros - Cloud Foundry deployment, training and integration Github *: https://github.com/ldmberman <https://github.com/ldmberman>* |
|
|
|
Re: Bosh Job and Package dependency problem.
Xue Zhi Yong <zhiyxue@...>
But How to control these jobs run sequence?
toggle quoted message
Show quoted text
I tried these jobs will run concurrently. 在 2015年6月9日，21:38，Gwenn Etourneau <getourneau(a)pivotal.io> 写道： |
|
|
|
Re: Deployment manifest not recognized by BOSH
Gwenn Etourneau
Your manifest is wrong "*- !ruby/object:AWSDynamicNetworkBean *" are not a
toggle quoted message
Show quoted text
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, |
|
|
|
Re: Bosh Job and Package dependency problem.
Gwenn Etourneau
Right there is no dependency between job, but I think in the manifest you
toggle quoted message
Show quoted text
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: |
|
|
|
Re: Deployment manifest not recognized by BOSH
Kinjal Doshi
Hi,
toggle quoted message
Show quoted text
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, |
|
|
|
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: how to add openjdk 1.8 to my project
Gwenn Etourneau
Example :
toggle quoted message
Show quoted text
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 |
|
|
|
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
Up to you but nornally you just need to create a package to install openJdk,
toggle quoted message
Show quoted text
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 |
|
|
