|
Re: OpenSSL v0.9.8 in CF Ruby Buildpack 1.4
OK, that makes sense.
It sounds like you're installing the web app on the bare VM, and not in a
container rootfs. This isn't really a supported use case for the Buildpack,
which is going to make assumptions that you're running in either the
`lucid64` or `cflinuxfs` rootfs.
Can you explain a bit more about what you're trying to do, and why you're
using the ruby buildpack?
toggle quoted messageShow quoted text
On Tue, May 12, 2015 at 1:03 PM, Daya Sharma <dsharma(a)cloudbees.com> wrote: Hi Mike,
the line
```gem 'jruby-openssl', :platforms => :jruby ```
means jruby-openssl gem will be downloaded by bundler if and only if JRuby
platform is detected, I am using MRI not JRuby.
The OpenSSL error happens even before any dependency is downloaded or
resolved, it happens because Gemfile has this line
```source 'https://rubygems.org'``` to fulfill https needs system tries
to load OpenSSL 0.9.8 library which is not found on the virtual machine.
To further clarify the problem if I install OpenSSL 0.9.8 on the virtual
machine the problem disappears even though a higher version of OpenSSL
1.0.1f is already installed as shown in the log output.
-daya
On Tue, May 12, 2015 at 2:45 PM, Mike Dalessio <mdalessio(a)pivotal.io>
wrote:
Hi Daya,
I'm a bit confused, as it looks from your Gemfile like you're trying to
load a JRuby openssl gem while running MRI ruby.
What happens if you remove your dependency on the `jruby-openssl` gem?
On Tue, May 12, 2015 at 12:24 PM, Daya Sharma <dsharma(a)cloudbees.com>
wrote:
testing_openssl.rb mentioned previously is here
https://gist.github.com/daya/71a589f9b83f9ff57608
CloudFoundry Ruby Build Pack 1.4
https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.4.0
On Tue, May 12, 2015 at 1:32 AM, Daya Sharma <dsharma(a)cloudbees.com>
wrote:
Hi
There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack
and Stemcells are concerned
Our bosh-lite environment is
*StemCell*:
Name: bosh-warden-boshlite-ubuntu-trusty-go_agent
Version: 2776
CID: 3241e75c-e0ae-4c81-4c3e-69ef5545dcfe
OpenSSL: 1.0.1f
*CF Ruby BuildPack*:
Version
:
1.4
OpenSSL: 0.9.8
*Gemfile*: here
<https://github.com/daya/active_merchant/blob/master/Gemfile> refers
to Ruby 2.2.2
*Problem*: When sourcing cf_buildpack followed by bundle install with
https://rubygems.orginvokes Ruby version 2.2.2 which is built against
OpenSSL version 0.9.8 but vm based on above mentioned StemCell has OpenSSL
version 1.0.0 causing *ruby app failures*.
Following are the relevant outputs from a jenkins CI job
-------> Buildpack version 1.4.0
-----> Compiling Ruby
-----> Using Ruby version: ruby-2.2.2
-----> Installing dependencies using 1.7.12
Running: bundle install --without none --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Bundler Output:
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Steps to Reproduce:
Using file testing_openssl.rb
On VM
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -W2 /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:9: warning: assigned but unused variable - response
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.0.9.8: cannot open shared object file: No such file or directory - /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/net/http.rb:574:in `start'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:5:in `<main>'
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# apt-cache showpkg openssl
Package: openssl
Versions:
1.0.1f-1ubuntu2.7
Any ideas on how to best solve this problem.
Thanks,
-daya
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
Re: OpenSSL v0.9.8 in CF Ruby Buildpack 1.4
Daya Sharma <dsharma@...>
Hi Mike, the line ```gem 'jruby-openssl', :platforms => :jruby ``` means jruby-openssl gem will be downloaded by bundler if and only if JRuby platform is detected, I am using MRI not JRuby. The OpenSSL error happens even before any dependency is downloaded or resolved, it happens because Gemfile has this line ```source ' https://rubygems.org'``` to fulfill https needs system tries to load OpenSSL 0.9.8 library which is not found on the virtual machine. To further clarify the problem if I install OpenSSL 0.9.8 on the virtual machine the problem disappears even though a higher version of OpenSSL 1.0.1f is already installed as shown in the log output. -daya
On Tue, May 12, 2015 at 2:45 PM, Mike Dalessio <mdalessio(a)pivotal.io> wrote: Hi Daya,
I'm a bit confused, as it looks from your Gemfile like you're trying to
load a JRuby openssl gem while running MRI ruby.
What happens if you remove your dependency on the `jruby-openssl` gem?
On Tue, May 12, 2015 at 12:24 PM, Daya Sharma <dsharma(a)cloudbees.com>
wrote:
testing_openssl.rb mentioned previously is here
https://gist.github.com/daya/71a589f9b83f9ff57608
CloudFoundry Ruby Build Pack 1.4
https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.4.0
On Tue, May 12, 2015 at 1:32 AM, Daya Sharma <dsharma(a)cloudbees.com>
wrote:
Hi
There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack
and Stemcells are concerned
Our bosh-lite environment is
*StemCell*:
Name: bosh-warden-boshlite-ubuntu-trusty-go_agent
Version: 2776
CID: 3241e75c-e0ae-4c81-4c3e-69ef5545dcfe
OpenSSL: 1.0.1f
*CF Ruby BuildPack*:
Version
:
1.4
OpenSSL: 0.9.8
*Gemfile*: here
<https://github.com/daya/active_merchant/blob/master/Gemfile> refers to
Ruby 2.2.2
*Problem*: When sourcing cf_buildpack followed by bundle install with
https://rubygems.orginvokes Ruby version 2.2.2 which is built against
OpenSSL version 0.9.8 but vm based on above mentioned StemCell has OpenSSL
version 1.0.0 causing *ruby app failures*.
Following are the relevant outputs from a jenkins CI job
-------> Buildpack version 1.4.0
-----> Compiling Ruby
-----> Using Ruby version: ruby-2.2.2
-----> Installing dependencies using 1.7.12
Running: bundle install --without none --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Bundler Output:
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Steps to Reproduce:
Using file testing_openssl.rb
On VM
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -W2 /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:9: warning: assigned but unused variable - response
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.0.9.8: cannot open shared object file: No such file or directory - /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/net/http.rb:574:in `start'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:5:in `<main>'
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# apt-cache showpkg openssl
Package: openssl
Versions:
1.0.1f-1ubuntu2.7
Any ideas on how to best solve this problem.
Thanks,
-daya
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
Re: OpenSSL v0.9.8 in CF Ruby Buildpack 1.4
Hi Daya,
I'm a bit confused, as it looks from your Gemfile like you're trying to
load a JRuby openssl gem while running MRI ruby.
What happens if you remove your dependency on the `jruby-openssl` gem?
toggle quoted messageShow quoted text
On Tue, May 12, 2015 at 12:24 PM, Daya Sharma <dsharma(a)cloudbees.com> wrote: testing_openssl.rb mentioned previously is here
https://gist.github.com/daya/71a589f9b83f9ff57608
CloudFoundry Ruby Build Pack 1.4
https://github.com/cloudfoundry/ruby-buildpack/releases/tag/v1.4.0
On Tue, May 12, 2015 at 1:32 AM, Daya Sharma <dsharma(a)cloudbees.com>
wrote:
Hi
There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack
and Stemcells are concerned
Our bosh-lite environment is
*StemCell*:
Name: bosh-warden-boshlite-ubuntu-trusty-go_agent
Version: 2776
CID: 3241e75c-e0ae-4c81-4c3e-69ef5545dcfe
OpenSSL: 1.0.1f
*CF Ruby BuildPack*:
Version
:
1.4
OpenSSL: 0.9.8
*Gemfile*: here
<https://github.com/daya/active_merchant/blob/master/Gemfile> refers to
Ruby 2.2.2
*Problem*: When sourcing cf_buildpack followed by bundle install with
https://rubygems.orginvokes Ruby version 2.2.2 which is built against
OpenSSL version 0.9.8 but vm based on above mentioned StemCell has OpenSSL
version 1.0.0 causing *ruby app failures*.
Following are the relevant outputs from a jenkins CI job
-------> Buildpack version 1.4.0
-----> Compiling Ruby
-----> Using Ruby version: ruby-2.2.2
-----> Installing dependencies using 1.7.12
Running: bundle install --without none --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Bundler Output:
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Steps to Reproduce:
Using file testing_openssl.rb
On VM
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -W2 /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:9: warning: assigned but unused variable - response
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.0.9.8: cannot open shared object file: No such file or directory - /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/net/http.rb:574:in `start'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:5:in `<main>'
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# apt-cache showpkg openssl
Package: openssl
Versions:
1.0.1f-1ubuntu2.7
Any ideas on how to best solve this problem.
Thanks,
-daya
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
Re: OpenSSL v0.9.8 in CF Ruby Buildpack 1.4
Daya Sharma <dsharma@...>
toggle quoted messageShow quoted text
On Tue, May 12, 2015 at 1:32 AM, Daya Sharma <dsharma(a)cloudbees.com> wrote: Hi
There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack
and Stemcells are concerned
Our bosh-lite environment is
*StemCell*:
Name: bosh-warden-boshlite-ubuntu-trusty-go_agent
Version: 2776
CID: 3241e75c-e0ae-4c81-4c3e-69ef5545dcfe
OpenSSL: 1.0.1f
*CF Ruby BuildPack*:
Version
:
1.4
OpenSSL: 0.9.8
*Gemfile*: here
<https://github.com/daya/active_merchant/blob/master/Gemfile> refers to
Ruby 2.2.2
*Problem*: When sourcing cf_buildpack followed by bundle install with
https://rubygems.orginvokes Ruby version 2.2.2 which is built against
OpenSSL version 0.9.8 but vm based on above mentioned StemCell has OpenSSL
version 1.0.0 causing *ruby app failures*.
Following are the relevant outputs from a jenkins CI job
-------> Buildpack version 1.4.0
-----> Compiling Ruby
-----> Using Ruby version: ruby-2.2.2
-----> Installing dependencies using 1.7.12
Running: bundle install --without none --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Bundler Output:
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at http://rvm.io/packages/openssl.
Steps to Reproduce:
Using file testing_openssl.rb
On VM
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -W2 /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:9: warning: assigned but unused variable - response
/var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.0.9.8: cannot open shared object file: No such file or directory - /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/net/http.rb:574:in `start'
from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:5:in `<main>'
root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# apt-cache showpkg openssl
Package: openssl
Versions:
1.0.1f-1ubuntu2.7
Any ideas on how to best solve this problem.
Thanks,
-daya
|
|
|
OpenSSL v0.9.8 in CF Ruby Buildpack 1.4
Daya Sharma <dsharma@...>
Hi There is a OpenSSL version/dependency mismatch as far as Ruby BuildPack and Stemcells are concerned Our bosh-lite environment is *StemCell*: Name: bosh-warden-boshlite-ubuntu-trusty-go_agent Version: 2776 CID: 3241e75c-e0ae-4c81-4c3e-69ef5545dcfe OpenSSL: 1.0.1f *CF Ruby BuildPack*: Version : 1.4 OpenSSL: 0.9.8 *Gemfile*: here < https://github.com/daya/active_merchant/blob/master/Gemfile> refers to Ruby 2.2.2 *Problem*: When sourcing cf_buildpack followed by bundle install with https://rubygems.orginvokes Ruby version 2.2.2 which is built against OpenSSL version 0.9.8 but vm based on above mentioned StemCell has OpenSSL version 1.0.0 causing *ruby app failures*. Following are the relevant outputs from a jenkins CI job -------> Buildpack version 1.4.0 -----> Compiling Ruby -----> Using Ruby version: ruby-2.2.2 -----> Installing dependencies using 1.7.12 Running: bundle install --without none --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment Could not load OpenSSL. You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using RVM are available at http://rvm.io/packages/openssl. Bundler Output: Could not load OpenSSL. You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using RVM are available at http://rvm.io/packages/openssl. Steps to Reproduce: Using file testing_openssl.rb On VM root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -v ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux] root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/bin/ruby -W2 /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:9: warning: assigned but unused variable - response /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.0.9.8: cannot open shared object file: No such file or directory - /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError) from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>' from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/vendor/ruby-2.2.2/lib/ruby/2.2.0/net/http.rb:574:in `start' from /var/vcap/store/jenkins_slave/workspace/ruby-buildpack-test/testing_openssl.rb:5:in `<main>' root(a)21d7bdc5-cbd5-4cdb-80cc-25c654549d3e:~# apt-cache showpkg openssl Package: openssl Versions: 1.0.1f-1ubuntu2.7 Any ideas on how to best solve this problem. Thanks, -daya
|
|
|
Re: [cf-lattice] [cf-dev] Links to Nabble archives of the CF lists
aaron, i added a page on the cf community wiki with your links: https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Mailing-ListsOn Wed, May 6, 2015 at 1:55 PM, Christopher B Ferris <chrisfer(a)us.ibm.com> wrote: +! nice job!
Cheers,
Christopher Ferris
IBM Distinguished Engineer, CTO Open Cloud
IBM Software Group, Open Technologies
email: chrisfer(a)us.ibm.com
twitter: @christo4ferris
blog: http://thoughtsoncloud.com/index.php/author/cferris/
phone: +1 508 667 0402
[image: Inactive hide details for Chip Childers ---05/06/2015 01:51:38
PM---Thanks Aaron! Chip Childers | Technology Chief of Staff | C]Chip
Childers ---05/06/2015 01:51:38 PM---Thanks Aaron! Chip Childers |
Technology Chief of Staff | Cloud Foundry Foundation
From: Chip Childers <cchilders(a)cloudfoundry.org>
To: "Huber, Aaron M" <aaron.m.huber(a)intel.com>
Cc: "cf-dev(a)lists.cloudfoundry.org" <cf-dev(a)lists.cloudfoundry.org>, "
cf-lattice(a)lists.cloudfoundry.org" <cf-lattice(a)lists.cloudfoundry.org>, "
cf-bosh(a)lists.cloudfoundry.org" <cf-bosh(a)lists.cloudfoundry.org>
Date: 05/06/2015 01:51 PM
Subject: Re: [cf-dev] [cf-bosh] Links to Nabble archives of the CF lists
Sent by: cf-dev-bounces(a)lists.cloudfoundry.org
------------------------------
Thanks Aaron!
Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation
On Wed, May 6, 2015 at 4:28 PM, Huber, Aaron M <*aaron.m.huber(a)intel.com*
<aaron.m.huber(a)intel.com>> wrote:
I’ve created Nabble archives of the CF lists here:
*http://cf-bosh.70367.x6.nabble.com/*
<http://cf-bosh.70367.x6.nabble.com/>
*http://cf-dev.70369.x6.nabble.com/*
<http://cf-dev.70369.x6.nabble.com/>
*http://cf-lattice.70370.x6.nabble.com/*
<http://cf-lattice.70370.x6.nabble.com/>
The archives are searchable and allow web viewing of the mailing list
without subscribing via email. There is also an RSS feed for each list.
Aaron
_______________________________________________
cf-bosh mailing list
*cf-bosh(a)lists.cloudfoundry.org* <cf-bosh(a)lists.cloudfoundry.org>
*https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh*
<https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh>
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
_______________________________________________
cf-lattice mailing list
cf-lattice(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
-- Thank you, James Bayer
|
|
|
Re: Issue on re-deploy to AWS - static IP already reserved/in use
We had the similar issue with AWS. In AWS pannel we couldn't find any instance that used some IP address, still there was no ability to create an instance with such IP. We got this bug after we redeployed cluster several times. I think it could be AWS problem, so the solution here will be to put this IP addresses to the list of reserved IPs. ------------------------ Alex Lomov *Altoros* — Cloud Foundry deployment, training and integration *Twitter:* @code1n < https://twitter.com/code1n> *GitHub:* @allomov < https://gist.github.com/allomov>
On Thu, May 7, 2015 at 8:10 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Was that IP previously assigned to a different VM (check via `bosh vms`)?
Currently BOSH does not allow to pick a static IP if it's already in use
by another VM. You could try putting it as a reserved IP, then doing bosh
deploy, and then assigning it as a static IP for the haproxy VM.
On Thu, May 7, 2015 at 3:32 AM, Lev Berman <lev.berman(a)altoros.com> wrote:
Have you terminated the previous Amazon HA Proxy instance? If not, this
might be the reason of the reserved IP error.
On Thu, May 7, 2015 at 1:11 PM, teddyking <ed(a)cloudcredo.com> wrote:
Hi BOSH users!
We're running into an error when attempting to re-deploy a failing BOSH
deployment of CF to AWS:
`ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already
reserved/in use
We're essentially doing the following:
* Allocate new EIP in AWS
* Generate manifest for CF with the EIP assigned to HA Proxy
* Run `bosh deploy` - this fails because we're hitting AWS API limits
* Run `bosh deploy` again - this now fails due to the above 'already
reserved' error
Is this the expected behaviour?
We've tried manually releasing the EIP in AWS and retrying the
deployment,
but we still experience the 'already reserved' failure.
We're running BOSH version 1.2922.0 and have attached the relevant
backtrace
from the debug log.
Any help appreciated.
Thanks,
Ed and Gareth
aws-static-ip-already-reserved-debug.txt
<
http://cf-bosh.70367.x6.nabble.com/file/n10/aws-static-ip-already-reserved-debug.txt
--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/Issue-on-re-deploy-to-AWS-static-IP-already-reserved-in-use-tp10.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
--
Lev Berman
Altoros - Cloud Foundry deployment, training and integration
Github
*: https://github.com/ldmberman <https://github.com/ldmberman>*
_______________________________________________
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: Deploy CF Diego Release on OpenStack
王天青 <wang.tianqing.cn at gmail.com...>
Thanks.
toggle quoted messageShow quoted text
On Fri, May 8, 2015 at 1:13 AM Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Might want to cross-post this to cf-dev.
On Wed, May 6, 2015 at 7:17 PM, 王天青 <wang.tianqing.cn(a)gmail.com> wrote:
Hi all,
When deploying Cloud Foundry on OpenStack using BOSH, there is a good
reference doc:
http://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html
.
For Diego release, is there any similar docs? If more specifically, is
there any sample deployment manifest file? Like cf-stub.yml, thanks.
Best Regards!
$ ./generate_deployment_manifest openstack cf-stub.yml > cf-deployment.yml
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
Re: Deploy CF Diego Release on OpenStack
Might want to cross-post this to cf-dev.
toggle quoted messageShow quoted text
|
|
|
Re: Issue on re-deploy to AWS - static IP already reserved/in use
Was that IP previously assigned to a different VM (check via `bosh vms`)?
Currently BOSH does not allow to pick a static IP if it's already in use by
another VM. You could try putting it as a reserved IP, then doing bosh
deploy, and then assigning it as a static IP for the haproxy VM.
toggle quoted messageShow quoted text
On Thu, May 7, 2015 at 3:32 AM, Lev Berman <lev.berman(a)altoros.com> wrote: Have you terminated the previous Amazon HA Proxy instance? If not, this
might be the reason of the reserved IP error.
On Thu, May 7, 2015 at 1:11 PM, teddyking <ed(a)cloudcredo.com> wrote:
Hi BOSH users!
We're running into an error when attempting to re-deploy a failing BOSH
deployment of CF to AWS:
`ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already
reserved/in use
We're essentially doing the following:
* Allocate new EIP in AWS
* Generate manifest for CF with the EIP assigned to HA Proxy
* Run `bosh deploy` - this fails because we're hitting AWS API limits
* Run `bosh deploy` again - this now fails due to the above 'already
reserved' error
Is this the expected behaviour?
We've tried manually releasing the EIP in AWS and retrying the deployment,
but we still experience the 'already reserved' failure.
We're running BOSH version 1.2922.0 and have attached the relevant
backtrace
from the debug log.
Any help appreciated.
Thanks,
Ed and Gareth
aws-static-ip-already-reserved-debug.txt
<
http://cf-bosh.70367.x6.nabble.com/file/n10/aws-static-ip-already-reserved-debug.txt
--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/Issue-on-re-deploy-to-AWS-static-IP-already-reserved-in-use-tp10.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
--
Lev Berman
Altoros - Cloud Foundry deployment, training and integration
Github
*: https://github.com/ldmberman <https://github.com/ldmberman>*
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
Re: Issue on re-deploy to AWS - static IP already reserved/in use
Have you terminated the previous Amazon HA Proxy instance? If not, this
might be the reason of the reserved IP error.
toggle quoted messageShow quoted text
On Thu, May 7, 2015 at 1:11 PM, teddyking <ed(a)cloudcredo.com> wrote: Hi BOSH users!
We're running into an error when attempting to re-deploy a failing BOSH
deployment of CF to AWS:
`ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already
reserved/in use
We're essentially doing the following:
* Allocate new EIP in AWS
* Generate manifest for CF with the EIP assigned to HA Proxy
* Run `bosh deploy` - this fails because we're hitting AWS API limits
* Run `bosh deploy` again - this now fails due to the above 'already
reserved' error
Is this the expected behaviour?
We've tried manually releasing the EIP in AWS and retrying the deployment,
but we still experience the 'already reserved' failure.
We're running BOSH version 1.2922.0 and have attached the relevant
backtrace
from the debug log.
Any help appreciated.
Thanks,
Ed and Gareth
aws-static-ip-already-reserved-debug.txt
<
http://cf-bosh.70367.x6.nabble.com/file/n10/aws-static-ip-already-reserved-debug.txt
--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/Issue-on-re-deploy-to-AWS-static-IP-already-reserved-in-use-tp10.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
|
|
|
Issue on re-deploy to AWS - static IP already reserved/in use
Hi BOSH users! We're running into an error when attempting to re-deploy a failing BOSH deployment of CF to AWS: `ha_proxy_z1/0' asked for a static IP 52.28.90.12 but it's already reserved/in use We're essentially doing the following: * Allocate new EIP in AWS * Generate manifest for CF with the EIP assigned to HA Proxy * Run `bosh deploy` - this fails because we're hitting AWS API limits * Run `bosh deploy` again - this now fails due to the above 'already reserved' error Is this the expected behaviour? We've tried manually releasing the EIP in AWS and retrying the deployment, but we still experience the 'already reserved' failure. We're running BOSH version 1.2922.0 and have attached the relevant backtrace from the debug log. Any help appreciated. Thanks, Ed and Gareth aws-static-ip-already-reserved-debug.txt < http://cf-bosh.70367.x6.nabble.com/file/n10/aws-static-ip-already-reserved-debug.txt> -- View this message in context: http://cf-bosh.70367.x6.nabble.com/Issue-on-re-deploy-to-AWS-static-IP-already-reserved-in-use-tp10.htmlSent from the CF BOSH mailing list archive at Nabble.com.
|
|
|
Deploy CF Diego Release on OpenStack
王天青 <wang.tianqing.cn at gmail.com...>
Hi all, When deploying Cloud Foundry on OpenStack using BOSH, there is a good reference doc: http://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html. For Diego release, is there any similar docs? If more specifically, is there any sample deployment manifest file? Like cf-stub.yml, thanks. Best Regards! $ ./generate_deployment_manifest openstack cf-stub.yml > cf-deployment.yml
|
|
|
Re: [cf-dev] Links to Nabble archives of the CF lists
Christopher B Ferris <chrisfer@...>
+! nice job! Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Cloud IBM Software Group, Open Technologies email: chrisfer(a)us.ibm.com twitter: @christo4ferris blog: http://thoughtsoncloud.com/index.php/author/cferris/phone: +1 508 667 0402 From: Chip Childers <cchilders(a)cloudfoundry.org> To: "Huber, Aaron M" <aaron.m.huber(a)intel.com> Cc: "cf-dev(a)lists.cloudfoundry.org" <cf-dev(a)lists.cloudfoundry.org>, "cf-lattice(a)lists.cloudfoundry.org" <cf-lattice(a)lists.cloudfoundry.org>, "cf-bosh(a)lists.cloudfoundry.org" <cf-bosh(a)lists.cloudfoundry.org> Date: 05/06/2015 01:51 PM Subject: Re: [cf-dev] [cf-bosh] Links to Nabble archives of the CF lists Sent by: cf-dev-bounces(a)lists.cloudfoundry.org Thanks Aaron! Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation
|
|
|
Re: Links to Nabble archives of the CF lists
|
|
|
Re: Links to Nabble archives of the CF lists
|
|
|
Links to Nabble archives of the CF lists
|
|
|
Re: Best practices around porting CF to RHEL/SLES?
Rishi Misra <misra.rishi@...>
Thanks Dmitriy - I guess with DEA not working there won't be any
functioning CF on CentOS/RHEL.
I wonder if SLES has better CF story at this point (in terms of porting)?
toggle quoted messageShow quoted text
On Wed, May 6, 2015 at 3:18 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Cloud Foundry Elastic Runtime can only be deployed at this point on Ubuntu
Trusty stemcell. All components work of ER work on CentOS stemcell except
the DEA (component that runs applications) due to certain incompatibilities
with how containers are managed. Once CentOS 7.2+ is released that includes
user namespacing, I believe there will be some effort to certify that full
ER runs on CentOS/RHEL.
RHEL stemcells can be built. See
https://github.com/cloudfoundry/bosh/tree/master/bosh-stemcell for more
details.
On Wed, May 6, 2015 at 11:13 AM, Rishi Misra <misra.rishi(a)gmail.com>
wrote:
This is great .. thanks Wayne.
Does this mean CF already supports CentOS7? For some reason I thought
it was Ubuntu trusty all the way. Is my understanding correct that when
creating Stemcells for CF, I must also ensure that all CF components must
first work on VMs with that Stemcell as its base? By "work" I mean it at
least compiles and successfully runs associated testcases?
Thanks again.
On Wed, May 6, 2015 at 2:02 PM, Wayne E. Seguin <
wayneeseguin(a)starkandwayne.com> wrote:
Building RHEL 7 is very similar to building CentOS 7 and is supported by
BOSH.
There are also official released CentOS 7 Stemcells:
http://bosh.io/stemcells/bosh-aws-xen-centos-7-go_agent
In order to use these you update what stemcell is being used in the CF
Deployment Manifest.
I would recommend you get your deployment working with CentOS 7 while
working on building your custom RHEL 7 stemcells. The BOSH repository has
instructions within it for how to build custom stemcells:
https://github.com/cloudfoundry/bosh
~Wayne
Wayne E. Seguin <wayneeseguin(a)starkandwayne.com>
CTO ; Stark & Wayne, LLC
On May 6, 2015, at 13:17 , Rishi Misra <misra.rishi(a)gmail.com> wrote:
Folks,
I am looking for some guidance around getting CF to work on RHEL/SLES.
From my limited knowledge of CF I have gathered the following:
- CF only supports Ubuntu trusty
- CF consists of CCNG/GoRouter/DEA/Health
Manager/CLI/UAA/Loggregator/BOSH repositories
- CF is deployed using BOSH on IaaS
- CF can be deployed on a local system using BOSH lite
- BOSH/BOSH lite deployment of CF consists of pushing components
listed above in a virtual machines (based on stemcells)
- BOSH uses trusty stemcells to deploy CF components (?)
My guess would be if I have to make this work in RHEL envt I would need
to do the following:
- Investigate if BOSH RHEL stemcell can be created
- For each CF repositories try to see if it compiles and runs
(associated test suites) on RHEL
- Create release/deployment manifest based on existing CF manifest
- Use BOSH/BOSH lite to deploy
- Debug failures
- ...
Any tips greatly appreciated.
Thanks in advance for your help.
_______________________________________________
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: Best practices around porting CF to RHEL/SLES?
Cloud Foundry Elastic Runtime can only be deployed at this point on Ubuntu Trusty stemcell. All components work of ER work on CentOS stemcell except the DEA (component that runs applications) due to certain incompatibilities with how containers are managed. Once CentOS 7.2+ is released that includes user namespacing, I believe there will be some effort to certify that full ER runs on CentOS/RHEL. RHEL stemcells can be built. See https://github.com/cloudfoundry/bosh/tree/master/bosh-stemcell for more details.
On Wed, May 6, 2015 at 11:13 AM, Rishi Misra <misra.rishi(a)gmail.com> wrote: This is great .. thanks Wayne.
Does this mean CF already supports CentOS7? For some reason I thought
it was Ubuntu trusty all the way. Is my understanding correct that when
creating Stemcells for CF, I must also ensure that all CF components must
first work on VMs with that Stemcell as its base? By "work" I mean it at
least compiles and successfully runs associated testcases?
Thanks again.
On Wed, May 6, 2015 at 2:02 PM, Wayne E. Seguin <
wayneeseguin(a)starkandwayne.com> wrote:
Building RHEL 7 is very similar to building CentOS 7 and is supported by
BOSH.
There are also official released CentOS 7 Stemcells:
http://bosh.io/stemcells/bosh-aws-xen-centos-7-go_agent
In order to use these you update what stemcell is being used in the CF
Deployment Manifest.
I would recommend you get your deployment working with CentOS 7 while
working on building your custom RHEL 7 stemcells. The BOSH repository has
instructions within it for how to build custom stemcells:
https://github.com/cloudfoundry/bosh
~Wayne
Wayne E. Seguin <wayneeseguin(a)starkandwayne.com>
CTO ; Stark & Wayne, LLC
On May 6, 2015, at 13:17 , Rishi Misra <misra.rishi(a)gmail.com> wrote:
Folks,
I am looking for some guidance around getting CF to work on RHEL/SLES.
From my limited knowledge of CF I have gathered the following:
- CF only supports Ubuntu trusty
- CF consists of CCNG/GoRouter/DEA/Health
Manager/CLI/UAA/Loggregator/BOSH repositories
- CF is deployed using BOSH on IaaS
- CF can be deployed on a local system using BOSH lite
- BOSH/BOSH lite deployment of CF consists of pushing components
listed above in a virtual machines (based on stemcells)
- BOSH uses trusty stemcells to deploy CF components (?)
My guess would be if I have to make this work in RHEL envt I would need
to do the following:
- Investigate if BOSH RHEL stemcell can be created
- For each CF repositories try to see if it compiles and runs
(associated test suites) on RHEL
- Create release/deployment manifest based on existing CF manifest
- Use BOSH/BOSH lite to deploy
- Debug failures
- ...
Any tips greatly appreciated.
Thanks in advance for your help.
_______________________________________________
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: Full text search for the mailing list?
I put in a request with markmail.org. Dan On Wed, May 6, 2015 at 2:38 PM, Chip Childers <cchilders(a)cloudfoundry.org> wrote: It would be great if someone from the community took the initiative to
register the lists with markmail and nabble!
The reason that we changed the list platform was that we were too large
for Google Groups (really!), and people were experiencing errors due to
hard limits that google has set for the service.
Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation
On Wed, May 6, 2015 at 2:08 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
Another list I monitor uses markmail.org. Perhaps someone could submit a
request to have them index our lists [1]? Looks like Nabble has a similar
form [2].
Dan
[1] - http://markmail.org/docs/feedback.xqy
[2] - http://n6.nabble.com/archive-your-mailing-list.html
On Wed, May 6, 2015 at 1:57 PM, Huber, Aaron M <aaron.m.huber(a)intel.com>
wrote:
I used to just view the posts in the Google Groups web interface as
opposed to subscribing via email, so I’m missing the friendly web view and
search abilities as well. I was looking around for something that might
replace it and found http://www.nabble.com. It looks like they are
archiving a large number of OSS mailing lists and it provides most of what
is now missing including search and an RSS feed for the posts. I’m
guessing it works by just subscribing to the list itself so there would be
no impact to mailman.
Does anyone have any experience using it?
Aaron
*From:* cf-bosh-bounces(a)lists.cloudfoundry.org [mailto:
cf-bosh-bounces(a)lists.cloudfoundry.org] *On Behalf Of *Cyrille Le Clerc
*Sent:* Wednesday, May 6, 2015 8:20 AM
*To:* cf-bosh(a)lists.cloudfoundry.org
*Subject:* [cf-bosh] Full text search for the mailing list?
Dear all,
I imagine that there are reasons to move the mailing list from Google
Groups to the OSS Mailman (1) that are related to the guidelines of the
Cloud Foundry Foundation.
Will it be possible to have full text search on the archive of the
mailing-list?
It will be much more difficult to search for questions that has already
been answered.
Cyrille
(1) http://lists.cloudfoundry.org/pipermail/cf-bosh/
--
Cyrille Le Clerc
email & gtalk : cleclerc(a)cloudbees.com / mob: +33-6.61.33.69.86 /
skype: cyrille.leclerc
CloudBees, Inc
www.cloudbees.com
<https://www.cloudbees.com/jenkins/juc-2015>
<https://www.cloudbees.com/cdsummit-2015>
_______________________________________________
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
|
|
|
