Date   

Re: Any information Docker image on CF / Pivotal CF

Gwenn Etourneau
 

Cloudfoundry support docker image, I mean the open source version does no
with diego, for me diego is a part of CF ..
But yet is not official right now.



On Mon, Jul 13, 2015 at 3:16 PM, Prysmakou Aliaksandr <
aliaksandr.prysmakou(a)altoros.com> wrote:

Hi,

Currently CF doesn't run docker images. But there is project to add
support of Docker to CF called Diego.
More details are here -
https://github.com/cloudfoundry-incubator/diego-release

Alex Prysmakou / Altoros
Tel: (617) 841-2121 ext. 5161 | Toll free: 855-ALTOROS
Skype: aliaksandr.prysmakou
www.altoros.com | blog.altoros.com | twitter.com/altoros

On Jul 13, 2015, at 8:52 AM, Balaramaraju JLSP <balaramaraju(a)gmail.com>
wrote:

HI All,

can i use my docker image on cloud foundry ?
if any one succeed please share the information

--
J L S P Balaramaraju
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev



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


Re: Python buildpack failed to work on CF 210

Gwenn Etourneau
 

:)

On Mon, Jul 13, 2015 at 2:33 PM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Thanks a lot, Gwenn

I specify python version in runtime.txt, after modifying it to 2.7.9, it
works.

2015-07-10 11:47 GMT+08:00 Gwenn Etourneau <getourneau(a)pivotal.io>:

I am wondering about "Installing runtime (python-2.7.6)" I think only
2.7.9 and 2.7.10 are supported on the cf2linux stack.

Do you specify the python version on your application ? Can you try the
one I give you ?


On Fri, Jul 10, 2015 at 12:30 PM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Hi, there

I upgraded CloudFoundry to verion 210 from 205 last week, today when I
push a "hello world" python project (works before) to CF using command
below:

cf push python11 -p python-sample.zip -b
https://github.com/cloudfoundry/python-buildpack

it failed with followoing error, seems pre-comipled package does not
work on latest stack cflinuxfs2, any ideas?

BTW, when I push python project using cached python buildpack 1.3.1 with
old stack lucid64, it worked.

2015-07-10T03:27:05.72+0000 [DEA] OUT Got staging request for app
with id 04900427-41c0-48c4-9cae-e904b9b6caa4
2015-07-10T03:27:06.69+0000 [STG] OUT -----> Downloaded app package
(4.0K)
2015-07-10T03:27:06.76+0000 [STG] ERR Cloning into
'/tmp/buildpacks/python-buildpack'...
2015-07-10T03:27:13.58+0000 [STG] OUT Submodule 'compile-extensions'
(https://github.com/cloudfoundry-incubator/compile-extensions.git)
registered for path 'compile-extensions'
2015-07-10T03:27:13.62+0000 [STG] ERR Cloning into
'compile-extensions'...
2015-07-10T03:27:16.67+0000 [STG] OUT Submodule path
'compile-extensions': checked out 'f752ecf4b27d2f31bb082dfe7a47c76fefc769d7'
2015-07-10T03:27:16.79+0000 [STG] OUT -------> Buildpack version
1.4.0
2015-07-10T03:27:16.83+0000 [STG] OUT -----> Installing runtime
(python-2.7.6)
2015-07-10T03:27:31.22+0000 [STG] OUT -----> Installing dependencies
with pip
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash md5
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type md5
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha1
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha1
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash
sha224 was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha224
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash
sha256 was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha256
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash
sha384 was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha384
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash
sha512 was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha512
2015-07-10T03:27:31.37+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/bin/pip", line 9, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR
load_entry_point('pip==7.0.1', 'console_scripts', 'pip')()
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 552, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2672, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2345, in load
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2351, in
resolve
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/__init__.py",
line 15, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.vcs import git,
mercurial, subversion, bazaar # noqa
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/vcs/mercurial.py",
line 10, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.download import
path_to_url
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/download.py",
line 38, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip._vendor import
requests, six
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/_vendor/__init__.py",
line 92, in load_module
2015-07-10T03:27:31.37+0000 [STG] ERR raise ImportError("No
module named '%s'" % (name,))
2015-07-10T03:27:31.37+0000 [STG] ERR ImportError: No module named
'pip._vendor.requests'
2015-07-10T03:27:31.38+0000 [STG] OUT Staging failed: Buildpack
compilation step failed


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

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

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


Re: Removing FUSE support from CF

Lerenc, Vedran <vedran.lerenc@...>
 

Hi Onsi,


Ø Thoughts? Concerns?

Well, that’s bad news.

We, and I assume many others as well (like the folks from Stackato who do it in the public), have used SSHFS + FUSE to implement a persistent file system for old-fashioned apps/apps that are not Cloud-native. I don’t want to fight an ideological battle here, it’s just that these apps do still exist (in majority) and a file system service is an important service/feature for them.

So if you remove FUSE (which we thought is not going away/was added to stay), it’s pretty bad for us/many apps.

Best regards, Vedran



From: Onsi Fakhouri
Reply-To: "Discussions about Cloud Foundry projects and the system overall."
Date: Saturday 11 July 2015 01:10
To: cf-dev
Subject: [cf-dev] Removing FUSE support from CF

Hey CF-Dev,

The Garden team has been hard at work substantially improving Garden-Linux's security features. Garden-Linux now employs user namespaces and drops capabilities when creating unprivileged containers - we're excited to bring both of these features to the platform!

Diego currently runs applications in privileged containers. These lack the security features outlined above and we are planning on switching to launch all CF applications in unprivileged containers.

Unfortunately, it has proved difficult to support mounting FUSE filesystems from within unprivileged containers. We believe the security benefits outweigh the features that FUSE give us and are planning on removing support for FUSE in favor of better securing our containers. If/when FUSE support in unprivileged containers becomes possible we may add it back to the platform.

Thoughts? Concerns?

Thanks!

Onsi


Re: Any information Docker image on CF / Pivotal CF

Prysmakou Aliaksandr <aliaksandr.prysmakou@...>
 

Hi,

Currently CF doesn't run docker images. But there is project to add support of Docker to CF called Diego.
More details are here - https://github.com/cloudfoundry-incubator/diego-release

Alex Prysmakou / Altoros
Tel: (617) 841-2121 ext. 5161 | Toll free: 855-ALTOROS
Skype: aliaksandr.prysmakou
www.altoros.com<http://www.altoros.com/> | blog.altoros.com<http://blog.altoros.com/> | twitter.com/altoros<http://twitter.com/altoros>

On Jul 13, 2015, at 8:52 AM, Balaramaraju JLSP <balaramaraju(a)gmail.com<mailto:balaramaraju(a)gmail.com>> wrote:

HI All,

can i use my docker image on cloud foundry ?
if any one succeed please share the information

--
J L S P Balaramaraju
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Any information Docker image on CF / Pivotal CF

Balaramaraju JLSP <balaramaraju@...>
 

HI All,

can i use my docker image on cloud foundry ?
if any one succeed please share the information

--
J L S P Balaramaraju


Re: Python buildpack failed to work on CF 210

王小锋 <zzuwxf at gmail.com...>
 

Thanks a lot, Gwenn

I specify python version in runtime.txt, after modifying it to 2.7.9, it
works.

2015-07-10 11:47 GMT+08:00 Gwenn Etourneau <getourneau(a)pivotal.io>:

I am wondering about "Installing runtime (python-2.7.6)" I think only
2.7.9 and 2.7.10 are supported on the cf2linux stack.

Do you specify the python version on your application ? Can you try the
one I give you ?


On Fri, Jul 10, 2015 at 12:30 PM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Hi, there

I upgraded CloudFoundry to verion 210 from 205 last week, today when I
push a "hello world" python project (works before) to CF using command
below:

cf push python11 -p python-sample.zip -b
https://github.com/cloudfoundry/python-buildpack

it failed with followoing error, seems pre-comipled package does not work
on latest stack cflinuxfs2, any ideas?

BTW, when I push python project using cached python buildpack 1.3.1 with
old stack lucid64, it worked.

2015-07-10T03:27:05.72+0000 [DEA] OUT Got staging request for app
with id 04900427-41c0-48c4-9cae-e904b9b6caa4
2015-07-10T03:27:06.69+0000 [STG] OUT -----> Downloaded app package
(4.0K)
2015-07-10T03:27:06.76+0000 [STG] ERR Cloning into
'/tmp/buildpacks/python-buildpack'...
2015-07-10T03:27:13.58+0000 [STG] OUT Submodule 'compile-extensions' (
https://github.com/cloudfoundry-incubator/compile-extensions.git)
registered for path 'compile-extensions'
2015-07-10T03:27:13.62+0000 [STG] ERR Cloning into
'compile-extensions'...
2015-07-10T03:27:16.67+0000 [STG] OUT Submodule path
'compile-extensions': checked out 'f752ecf4b27d2f31bb082dfe7a47c76fefc769d7'
2015-07-10T03:27:16.79+0000 [STG] OUT -------> Buildpack version 1.4.0
2015-07-10T03:27:16.83+0000 [STG] OUT -----> Installing runtime
(python-2.7.6)
2015-07-10T03:27:31.22+0000 [STG] OUT -----> Installing dependencies
with pip
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash md5
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type md5
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha1
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha1
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha224
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha224
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha256
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha256
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha384
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha384
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha512
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha512
2015-07-10T03:27:31.37+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/bin/pip", line 9, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR
load_entry_point('pip==7.0.1', 'console_scripts', 'pip')()
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 552, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2672, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2345, in load
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2351, in
resolve
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/__init__.py",
line 15, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.vcs import git,
mercurial, subversion, bazaar # noqa
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/vcs/mercurial.py",
line 10, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.download import
path_to_url
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/download.py",
line 38, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip._vendor import
requests, six
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/_vendor/__init__.py",
line 92, in load_module
2015-07-10T03:27:31.37+0000 [STG] ERR raise ImportError("No
module named '%s'" % (name,))
2015-07-10T03:27:31.37+0000 [STG] ERR ImportError: No module named
'pip._vendor.requests'
2015-07-10T03:27:31.38+0000 [STG] OUT Staging failed: Buildpack
compilation step failed


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

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


Re: Composite Application Deployer

James Bayer
 

david,

it sounds like you have a fair amount of applications. any numbers you
would be willing to share that talks about the jenkins jobs, or at least
the ratio of:
app : spaces : jenkins jobs

to develop cloud foundry, we use concourse [1] for most of the ci.
previously we had relied on jenkins and gocd from thoughtworks [2].
however, concourse was designed with container images in-mind and it has
great support for pipelines like you're describing that involve multiple
environments with tests gating the automated promotion.

one of the features of concourse is that it works with the cf cli plugin
named autopilot [3] which does zero-downtime deploys and relies on a cf app
manifest which can be checked into SCM. the concourse files should also be
checked into SCM. this way your SCM drives your CI and your deployments.

the runtime team has been working on the so-called v3 cloud controller api
for awhile when enables having multiple versions of the same cf application
to exist and be running at the same time. when that work finishes, you
won't need 2 separate apps that share the same route as the current
blue/green processes require. then the platform can support a standard
zero-downtime application update, but you still may want to have some sort
of mechanism to health-check the new version of the app before cutting over
traffic to the new version completely.

[1] http://concourse.ci/
[2] http://www.thoughtworks.com/products/go-continuous-delivery
[3] https://github.com/concourse/autopilot

On Sat, Jul 11, 2015 at 12:57 PM, David Vydra <david(a)vydra.net> wrote:

We are new to CF. After some hacking, we found ourselves with hundreds of
jobs in Jenkins and a variety of shell scripts to promote our apps from
space to space with a blue/green strategy. We also run smoke tests before
we switch the routes and sometimes need to retry a deploy due to network
issues, etc. We would like to specify what needs to be deployed in Github,
not Jenkins.

Has anyone heard of a tool that does this well?

Thanks,
David

--
http://www.linkedin.com/in/dvydra
http://www.testdriven.com
http://twitter.com/vydra



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

--
Thank you,

James Bayer


Re: R: Re: Deploy CF on OpenStack, api and uaa failing

Yitao Jiang
 

What are your network security group rules ? Can you mount the nfs shared
directory manually?

On Thu, Jul 9, 2015 at 7:56 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello,

I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they
looks the same as the ones I can see by manually ssh into the VM.
What is the difference?


I'd point you to this logs from api, about the nfs mounter:

mount.nfs: mount(2): No such file or directory
[2015-07-09 09:24:31+0000] mount.nfs: trying 10.0.0.103 prog 100003 vers 3
prot TCP port 2049
[2015-07-09 09:24:34+0000] mount.nfs: portmap query retrying: RPC: Timed
out
[2015-07-09 09:24:34+0000] mount.nfs: trying 10.0.0.103 prog 100005 vers 3
prot TCP port 52652
[2015-07-09 09:24:36+0000] touch: cannot touch
'/var/vcap/nfs/shared/.nfs_test': Read-only file system
[2015-07-09 09:25:34+0000] stop: Unknown instance:
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted
[2015-07-09 09:25:38+0000] umount.nfs: remote share not in 'host:dir'
format
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted

and:

idmapd stop/waiting
[2015-07-09 09:24:28+0000] idmapd start/running, process 4862
[2015-07-09 09:24:28+0000] NFS unmounted
[2015-07-09 09:24:28+0000] Mounting NFS...
[2015-07-09 09:24:36+0000] mount.nfs: timeout set for Thu Jul 9 09:26:29
2015
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,vers=4,addr=10.0.0.103,clientaddr=10.0.0.58'
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,addr=10.0.0.103'
[2015-07-09 09:24:36+0000] mount.nfs: prog 100003, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=17
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] Failed to start: cannot write to NFS
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:34+0000] idmapd start/pre-start, process 5826
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:38+0000] NFS unmounted
[2015-07-09 09:25:38+0000] Failed to unmount NFS, exiting...
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] idmapd start/pre-start, process 6755
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] Mounting NFS...

the manifest is on the prevuous email, I used the default manifest with
the openstack stub, after that I did some edits to solve varous errors,
like changing the default passwords for uaa and api, because they did not
match using spiff to generate the final manifest. I also added 10.0.0.0/24
instead of null on the allowed networks for nfs connections.

If I try to write in /var/vcap/nfs as root I get permission denied. If I
manually unmount and mount it back I still have no write permissions,
(strange because with null instead of 10.0.0.0/24 on allowed range, I had
permissions)

Thanks,
Michael


Il 09/07/15 12:56, *Gwenn Etourneau * <getourneau(a)pivotal.io> ha scritto:

Hi,

This log are not so usefull, can you login into the VM using bosh ssh and
go to /var/vcap/sys/log/ and you will see some folder and you will have
some log here.

thanks

On Thu, Jul 9, 2015 at 7:23 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'm trying to deploy CF on top of a little OpenStack cluster but I get
api and uaa VMs constantly on starting/failing status.



After each 'bosh deploy' with some changes on the configuration, I always
get:

Failed: `api_z1/0' is not running after update (00:11:07)
Error 400007: `api_z1/0' is not running after update


from api VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 7m*

*Process 'cloud_controller_ng' running*
*Process 'cloud_controller_worker_local_1' running*
*Process 'cloud_controller_worker_local_2' running*
*Process 'nginx_cc' running*
*Process 'cloud_controller_migration' running*
*Process 'routing-api' not monitored*
*Process 'metron_agent' running*
*Process 'statsd-injector' running*
*Process 'consul_agent' running*
*File 'nfs_mounter' accessible*
*System 'system_1572093d-c49a-4a38-9336-6d1a288b8bd7' running*

from uaa VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 11m*

*Process 'uaa' Connection failed*
*Process 'uaa_cf-registrar' initializing*
*Process 'metron_agent' running*
*Process 'consul_agent' running*
*System 'system_24698313-5f71-4b4f-94fc-8e09a8da0866' running*



I attach some useful info like: manifest (most probably where the error
is), and logs from uaa, nfs and api
Ps. I am using a domain that is not registered on the internet, but i
have a custom dns that resolve *.domain.co with the floating IP of the
ha_proxy (assigned manually)

Thank you!

Michael

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

------------------------------

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


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


--

Regards,
Yitao(依涛 姜)
jiangyt.github.io


Re: Composite Application Deployer

Azad Bolour
 

Nicely put. Let’s see what we get.

Azad

From: David Vydra <david(a)vydra.net<mailto:david(a)vydra.net>>
Reply-To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Date: Saturday, July 11, 2015 at 12:57 PM
To: "cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>" <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: [cf-dev] Composite Application Deployer

We are new to CF. After some hacking, we found ourselves with hundreds of jobs in Jenkins and a variety of shell scripts to promote our apps from space to space with a blue/green strategy. We also run smoke tests before we switch the routes and sometimes need to retry a deploy due to network issues, etc. We would like to specify what needs to be deployed in Github, not Jenkins.

Has anyone heard of a tool that does this well?

Thanks,
David

--
http://www.linkedin.com/in/dvydra<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_dvydra&d=AwMFAw&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=mKQyOqxpP3Pxe4bGZxxgMJpUdWb5sjU245GYtlUzGHQ&m=WtunChoVNxq-qxs8N37bT3qZXiLppWHyL7j0xp59u30&s=R9tcTiMZ9qFlKxgcInGRgfK4Q31ySJu7TUaHY6g_wbU&e=>
http://www.testdriven.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.testdriven.com&d=AwMFAw&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=mKQyOqxpP3Pxe4bGZxxgMJpUdWb5sjU245GYtlUzGHQ&m=WtunChoVNxq-qxs8N37bT3qZXiLppWHyL7j0xp59u30&s=BiSKIAR3Zs5D5k3_UNX6xzs4WEUKHp3cRrD-iTs_rzs&e=>
http://twitter.com/vydra<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_vydra&d=AwMFAw&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=mKQyOqxpP3Pxe4bGZxxgMJpUdWb5sjU245GYtlUzGHQ&m=WtunChoVNxq-qxs8N37bT3qZXiLppWHyL7j0xp59u30&s=uJH9TrCsdV8Asywf0NLIIDwYhmAp44Myn7yEv8Qpmxw&e=>


Composite Application Deployer

David Vydra <david@...>
 

We are new to CF. After some hacking, we found ourselves with hundreds of
jobs in Jenkins and a variety of shell scripts to promote our apps from
space to space with a blue/green strategy. We also run smoke tests before
we switch the routes and sometimes need to retry a deploy due to network
issues, etc. We would like to specify what needs to be deployed in Github,
not Jenkins.

Has anyone heard of a tool that does this well?

Thanks,
David

--
http://www.linkedin.com/in/dvydra
http://www.testdriven.com
http://twitter.com/vydra


OpenSAF comparison

Sashan Govender <sashang@...>
 

Hi

I had a look at the 2014 presentation here:
http://cloudfoundry.org/learn/index.html

In it they compared 6 platforms however OpenSAF was not one of them. I am
wondering where people creating these PaaS systems see OpenSAF fitting in
and what the regions of overlap. There seems to be a significant amount of
overlap in terms of functionality, for example, the ability to install,
upgrade and remove an application on set of nodes, a distributed
configuration database and monitoring of applications. Is there any reason
why OpenSAF is not considered for comparison when it provides some of the
features required for a PaaS system? Is it missing something fundametal to
PaaS? Is it too awkward to admin or use? Is it not very well known?

http://www.opensaf.org/
http://sourceforge.net/projects/opensaf/


Removing FUSE support from CF

Onsi Fakhouri <ofakhouri@...>
 

Hey CF-Dev,

The Garden team has been hard at work substantially improving
Garden-Linux's security features. Garden-Linux now employs user namespaces
and drops capabilities when creating unprivileged containers - we're
excited to bring both of these features to the platform!

Diego currently runs applications in *privileged* containers. These lack
the security features outlined above and we are planning on switching to
launch all CF applications in *unprivileged* containers.

Unfortunately, it has proved difficult to support mounting FUSE filesystems
from within unprivileged containers. We believe the security benefits
outweigh the features that FUSE give us and* are planning on removing
support for FUSE in favor of better securing our containers.*
If/when FUSE support in unprivileged containers becomes possible we may add
it back to the platform.

Thoughts? Concerns?

Thanks!

Onsi


Re: Did anybody deploy a wiki as app to CF?

Johannes Tuchscherer
 

Hi Stephan,

I managed to get an instiki(instiki.org) instance up and running on PWS. I
had to change a few things to get it to work and even with those changes, it
isn't great yet. For example, uploaded files are stored locally in the
Warden container. Therefore, they get lost when the app is restarted. But it
wouldn't be to hard to change the code to use an S3 bucket as a storage
solution, I just didn't bother yet.

I will clean up my local changes and document them, then I'll push them up
to github.

P.S.: I also looked for some other open source wiki engines. I didn't find a
single one that could be deployed to CF (or any other PaaS) without major
changes.



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Did-anybody-deploy-a-wiki-as-app-to-CF-tp643p680.html
Sent from the CF Dev mailing list archive at Nabble.com.


R: Re: R: Re: R: Re: Deploy CF on OpenStack, api and uaa failing

Michael Grifalconi <michael.grifalconi@...>
 

Il 10/07/15 11:49, Alexander Lomov <alexander.lomov(a)altoros.com> ha scritto:


Sorry, but I don't see any logs attached.






------------------------
Alex Lomov
Altoros — Cloud Foundry deployment, training and integration
Twitter: @code1n(https://twitter.com/code1n) GitHub: @allomov(https://gist.github.com/allomov)



On Fri, Jul 10, 2015 at 12:46 PM, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello, the log is into the api_* folder in my previous email, 

I attach it here too!


Thank you!
Michael

Il 10/07/15 03:10, Gwenn Etourneau <getourneau(a)pivotal.io> ha scritto:




What log do you have into the dir /var/vcap/sys/log/cloudcontroller_ng/ thanks?



On Thu, Jul 9, 2015 at 8:56 PM, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello, 

I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they looks the same as the ones I can see by manually ssh into the VM.
What is the difference?


I'd point you to this logs from api, about the nfs mounter:


mount.nfs: mount(2): No such file or directory
[2015-07-09 09:24:31+0000] mount.nfs: trying 10.0.0.103 prog 100003 vers 3 prot TCP port 2049
[2015-07-09 09:24:34+0000] mount.nfs: portmap query retrying: RPC: Timed out
[2015-07-09 09:24:34+0000] mount.nfs: trying 10.0.0.103 prog 100005 vers 3 prot TCP port 52652
[2015-07-09 09:24:36+0000] touch: cannot touch '/var/vcap/nfs/shared/.nfs_test': Read-only file system
[2015-07-09 09:25:34+0000] stop: Unknown instance:
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted
[2015-07-09 09:25:38+0000] umount.nfs: remote share not in 'host:dir' format
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted


and:


idmapd stop/waiting
[2015-07-09 09:24:28+0000] idmapd start/running, process 4862
[2015-07-09 09:24:28+0000] NFS unmounted
[2015-07-09 09:24:28+0000] Mounting NFS...
[2015-07-09 09:24:36+0000] mount.nfs: timeout set for Thu Jul 9 09:26:29 2015
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options 'timeo=10,intr,lookupcache=positive,vers=4,addr=10.0.0.103,clientaddr=10.0.0.58'
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options 'timeo=10,intr,lookupcache=positive,addr=10.0.0.103'
[2015-07-09 09:24:36+0000] mount.nfs: prog 100003, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=17
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] Failed to start: cannot write to NFS
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:34+0000] idmapd start/pre-start, process 5826
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:38+0000] NFS unmounted
[2015-07-09 09:25:38+0000] Failed to unmount NFS, exiting...
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] idmapd start/pre-start, process 6755
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] Mounting NFS...


the manifest is on the prevuous email, I used the default manifest with the openstack stub, after that I did some edits to solve varous errors, like changing the default passwords for uaa and api, because they did not match using spiff to generate the final manifest. I also added 10.0.0.0/24(http://10.0.0.0/24) instead of null on the allowed networks for nfs connections.

If I try to write in /var/vcap/nfs as root I get permission denied. If I manually unmount and mount it back I still have no write permissions, (strange because with null instead of 10.0.0.0/24(http://10.0.0.0/24) on allowed range, I had permissions)

Thanks,
Michael



Il 09/07/15 12:56, Gwenn Etourneau <getourneau(a)pivotal.io> ha scritto:



Hi,

This log are not so usefull, can you login into the VM using bosh ssh and go to /var/vcap/sys/log/ and you will see some folder and you will have some log here.

thanks



On Thu, Jul 9, 2015 at 7:23 PM, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'm trying to deploy CF on top of a little OpenStack cluster but I get api and uaa VMs constantly on starting/failing status.




After each 'bosh deploy' with some changes on the configuration, I always get:


Failed: `api_z1/0' is not running after update (00:11:07)
Error 400007: `api_z1/0' is not running after update



from api VM:

monit summary
The Monit daemon 5.2.4 uptime: 7m


Process 'cloud_controller_ng' running
Process 'cloud_controller_worker_local_1' running
Process 'cloud_controller_worker_local_2' running
Process 'nginx_cc' running
Process 'cloud_controller_migration' running
Process 'routing-api' not monitored
Process 'metron_agent' running
Process 'statsd-injector' running
Process 'consul_agent' running
File 'nfs_mounter' accessible
System 'system_1572093d-c49a-4a38-9336-6d1a288b8bd7' running


from uaa VM:

monit summary
The Monit daemon 5.2.4 uptime: 11m


Process 'uaa' Connection failed
Process 'uaa_cf-registrar' initializing
Process 'metron_agent' running
Process 'consul_agent' running
System 'system_24698313-5f71-4b4f-94fc-8e09a8da0866' running




I attach some useful info like: manifest (most probably where the error is), and logs from uaa, nfs and api
Ps. I am using a domain that is not registered on the internet, but i have a custom dns that resolve *.domain.co(http://domain.co) with the floating IP of the ha_proxy (assigned manually)

Thank you!


Michael

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





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


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




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



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




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


Re: R: Re: R: Re: Deploy CF on OpenStack, api and uaa failing

Alexander Lomov <alexander.lomov@...>
 

Sorry, but I don't see any logs attached.

------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Fri, Jul 10, 2015 at 12:46 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello, the log is into the api_* folder in my previous email,

I attach it here too!


Thank you!
Michael

Il 10/07/15 03:10, *Gwenn Etourneau * <getourneau(a)pivotal.io> ha scritto:

What log do you have into the dir /var/vcap/sys/log/cloudcontroller_ng/
thanks?

On Thu, Jul 9, 2015 at 8:56 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello,

I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they
looks the same as the ones I can see by manually ssh into the VM.
What is the difference?


I'd point you to this logs from api, about the nfs mounter:

mount.nfs: mount(2): No such file or directory
[2015-07-09 09:24:31+0000] mount.nfs: trying 10.0.0.103 prog 100003 vers
3 prot TCP port 2049
[2015-07-09 09:24:34+0000] mount.nfs: portmap query retrying: RPC: Timed
out
[2015-07-09 09:24:34+0000] mount.nfs: trying 10.0.0.103 prog 100005 vers
3 prot TCP port 52652
[2015-07-09 09:24:36+0000] touch: cannot touch
'/var/vcap/nfs/shared/.nfs_test': Read-only file system
[2015-07-09 09:25:34+0000] stop: Unknown instance:
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted
[2015-07-09 09:25:38+0000] umount.nfs: remote share not in 'host:dir'
format
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted

and:

idmapd stop/waiting
[2015-07-09 09:24:28+0000] idmapd start/running, process 4862
[2015-07-09 09:24:28+0000] NFS unmounted
[2015-07-09 09:24:28+0000] Mounting NFS...
[2015-07-09 09:24:36+0000] mount.nfs: timeout set for Thu Jul 9 09:26:29
2015
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,vers=4,addr=10.0.0.103,clientaddr=10.0.0.58'
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,addr=10.0.0.103'
[2015-07-09 09:24:36+0000] mount.nfs: prog 100003, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=17
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] Failed to start: cannot write to NFS
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:34+0000] idmapd start/pre-start, process 5826
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:38+0000] NFS unmounted
[2015-07-09 09:25:38+0000] Failed to unmount NFS, exiting...
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] idmapd start/pre-start, process 6755
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] Mounting NFS...

the manifest is on the prevuous email, I used the default manifest with
the openstack stub, after that I did some edits to solve varous errors,
like changing the default passwords for uaa and api, because they did not
match using spiff to generate the final manifest. I also added
10.0.0.0/24 instead of null on the allowed networks for nfs connections.

If I try to write in /var/vcap/nfs as root I get permission denied. If I
manually unmount and mount it back I still have no write permissions,
(strange because with null instead of 10.0.0.0/24 on allowed range, I
had permissions)

Thanks,
Michael


Il 09/07/15 12:56, *Gwenn Etourneau * <getourneau(a)pivotal.io> ha scritto:

Hi,

This log are not so usefull, can you login into the VM using bosh ssh and
go to /var/vcap/sys/log/ and you will see some folder and you will have
some log here.

thanks

On Thu, Jul 9, 2015 at 7:23 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'm trying to deploy CF on top of a little OpenStack cluster but I get
api and uaa VMs constantly on starting/failing status.



After each 'bosh deploy' with some changes on the configuration, I
always get:

Failed: `api_z1/0' is not running after update (00:11:07)
Error 400007: `api_z1/0' is not running after update


from api VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 7m*

*Process 'cloud_controller_ng' running*
*Process 'cloud_controller_worker_local_1' running*
*Process 'cloud_controller_worker_local_2' running*
*Process 'nginx_cc' running*
*Process 'cloud_controller_migration' running*
*Process 'routing-api' not monitored*
*Process 'metron_agent' running*
*Process 'statsd-injector' running*
*Process 'consul_agent' running*
*File 'nfs_mounter' accessible*
*System 'system_1572093d-c49a-4a38-9336-6d1a288b8bd7' running*

from uaa VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 11m*

*Process 'uaa' Connection failed*
*Process 'uaa_cf-registrar' initializing*
*Process 'metron_agent' running*
*Process 'consul_agent' running*
*System 'system_24698313-5f71-4b4f-94fc-8e09a8da0866' running*



I attach some useful info like: manifest (most probably where the error
is), and logs from uaa, nfs and api
Ps. I am using a domain that is not registered on the internet, but i
have a custom dns that resolve *.domain.co with the floating IP of the
ha_proxy (assigned manually)

Thank you!

Michael

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

------------------------------

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


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

------------------------------

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


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


R: Re: R: Re: Deploy CF on OpenStack, api and uaa failing

Michael Grifalconi <michael.grifalconi@...>
 

Hello, the log is into the api_* folder in my previous email, 

I attach it here too!


Thank you!
Michael

Il 10/07/15 03:10, Gwenn Etourneau <getourneau(a)pivotal.io> ha scritto:


What log do you have into the dir /var/vcap/sys/log/cloudcontroller_ng/ thanks?



On Thu, Jul 9, 2015 at 8:56 PM, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello, 

I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they looks the same as the ones I can see by manually ssh into the VM.
What is the difference?


I'd point you to this logs from api, about the nfs mounter:


mount.nfs: mount(2): No such file or directory
[2015-07-09 09:24:31+0000] mount.nfs: trying 10.0.0.103 prog 100003 vers 3 prot TCP port 2049
[2015-07-09 09:24:34+0000] mount.nfs: portmap query retrying: RPC: Timed out
[2015-07-09 09:24:34+0000] mount.nfs: trying 10.0.0.103 prog 100005 vers 3 prot TCP port 52652
[2015-07-09 09:24:36+0000] touch: cannot touch '/var/vcap/nfs/shared/.nfs_test': Read-only file system
[2015-07-09 09:25:34+0000] stop: Unknown instance:
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted
[2015-07-09 09:25:38+0000] umount.nfs: remote share not in 'host:dir' format
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted


and:


idmapd stop/waiting
[2015-07-09 09:24:28+0000] idmapd start/running, process 4862
[2015-07-09 09:24:28+0000] NFS unmounted
[2015-07-09 09:24:28+0000] Mounting NFS...
[2015-07-09 09:24:36+0000] mount.nfs: timeout set for Thu Jul 9 09:26:29 2015
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options 'timeo=10,intr,lookupcache=positive,vers=4,addr=10.0.0.103,clientaddr=10.0.0.58'
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options 'timeo=10,intr,lookupcache=positive,addr=10.0.0.103'
[2015-07-09 09:24:36+0000] mount.nfs: prog 100003, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=17
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] Failed to start: cannot write to NFS
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:34+0000] idmapd start/pre-start, process 5826
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:38+0000] NFS unmounted
[2015-07-09 09:25:38+0000] Failed to unmount NFS, exiting...
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] idmapd start/pre-start, process 6755
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] Mounting NFS...


the manifest is on the prevuous email, I used the default manifest with the openstack stub, after that I did some edits to solve varous errors, like changing the default passwords for uaa and api, because they did not match using spiff to generate the final manifest. I also added 10.0.0.0/24(http://10.0.0.0/24) instead of null on the allowed networks for nfs connections.

If I try to write in /var/vcap/nfs as root I get permission denied. If I manually unmount and mount it back I still have no write permissions, (strange because with null instead of 10.0.0.0/24(http://10.0.0.0/24) on allowed range, I had permissions)

Thanks,
Michael



Il 09/07/15 12:56, Gwenn Etourneau <getourneau(a)pivotal.io> ha scritto:



Hi,

This log are not so usefull, can you login into the VM using bosh ssh and go to /var/vcap/sys/log/ and you will see some folder and you will have some log here.

thanks



On Thu, Jul 9, 2015 at 7:23 PM, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'm trying to deploy CF on top of a little OpenStack cluster but I get api and uaa VMs constantly on starting/failing status.




After each 'bosh deploy' with some changes on the configuration, I always get:


Failed: `api_z1/0' is not running after update (00:11:07)
Error 400007: `api_z1/0' is not running after update



from api VM:

monit summary
The Monit daemon 5.2.4 uptime: 7m


Process 'cloud_controller_ng' running
Process 'cloud_controller_worker_local_1' running
Process 'cloud_controller_worker_local_2' running
Process 'nginx_cc' running
Process 'cloud_controller_migration' running
Process 'routing-api' not monitored
Process 'metron_agent' running
Process 'statsd-injector' running
Process 'consul_agent' running
File 'nfs_mounter' accessible
System 'system_1572093d-c49a-4a38-9336-6d1a288b8bd7' running


from uaa VM:

monit summary
The Monit daemon 5.2.4 uptime: 11m


Process 'uaa' Connection failed
Process 'uaa_cf-registrar' initializing
Process 'metron_agent' running
Process 'consul_agent' running
System 'system_24698313-5f71-4b4f-94fc-8e09a8da0866' running




I attach some useful info like: manifest (most probably where the error is), and logs from uaa, nfs and api
Ps. I am using a domain that is not registered on the internet, but i have a custom dns that resolve *.domain.co(http://domain.co) with the floating IP of the ha_proxy (assigned manually)

Thank you!


Michael

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





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


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




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


Re: Python buildpack failed to work on CF 210

Gwenn Etourneau
 

I am wondering about "Installing runtime (python-2.7.6)" I think only 2.7.9
and 2.7.10 are supported on the cf2linux stack.

Do you specify the python version on your application ? Can you try the one
I give you ?

On Fri, Jul 10, 2015 at 12:30 PM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Hi, there

I upgraded CloudFoundry to verion 210 from 205 last week, today when I
push a "hello world" python project (works before) to CF using command
below:

cf push python11 -p python-sample.zip -b
https://github.com/cloudfoundry/python-buildpack

it failed with followoing error, seems pre-comipled package does not work
on latest stack cflinuxfs2, any ideas?

BTW, when I push python project using cached python buildpack 1.3.1 with
old stack lucid64, it worked.

2015-07-10T03:27:05.72+0000 [DEA] OUT Got staging request for app with
id 04900427-41c0-48c4-9cae-e904b9b6caa4
2015-07-10T03:27:06.69+0000 [STG] OUT -----> Downloaded app package
(4.0K)
2015-07-10T03:27:06.76+0000 [STG] ERR Cloning into
'/tmp/buildpacks/python-buildpack'...
2015-07-10T03:27:13.58+0000 [STG] OUT Submodule 'compile-extensions' (
https://github.com/cloudfoundry-incubator/compile-extensions.git)
registered for path 'compile-extensions'
2015-07-10T03:27:13.62+0000 [STG] ERR Cloning into
'compile-extensions'...
2015-07-10T03:27:16.67+0000 [STG] OUT Submodule path
'compile-extensions': checked out 'f752ecf4b27d2f31bb082dfe7a47c76fefc769d7'
2015-07-10T03:27:16.79+0000 [STG] OUT -------> Buildpack version 1.4.0
2015-07-10T03:27:16.83+0000 [STG] OUT -----> Installing runtime
(python-2.7.6)
2015-07-10T03:27:31.22+0000 [STG] OUT -----> Installing dependencies
with pip
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash md5 was
not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type md5
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha1
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha1
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha224
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha224
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha256
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha256
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha384
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha384
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha512
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise
ValueError('unsupported hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash
type sha512
2015-07-10T03:27:31.37+0000 [STG] ERR Traceback (most recent call
last):
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/bin/pip", line 9, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR
load_entry_point('pip==7.0.1', 'console_scripts', 'pip')()
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 552, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2672, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2345, in load
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2351, in
resolve
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/__init__.py",
line 15, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.vcs import git,
mercurial, subversion, bazaar # noqa
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/vcs/mercurial.py",
line 10, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.download import
path_to_url
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/download.py",
line 38, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip._vendor import
requests, six
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/_vendor/__init__.py",
line 92, in load_module
2015-07-10T03:27:31.37+0000 [STG] ERR raise ImportError("No module
named '%s'" % (name,))
2015-07-10T03:27:31.37+0000 [STG] ERR ImportError: No module named
'pip._vendor.requests'
2015-07-10T03:27:31.38+0000 [STG] OUT Staging failed: Buildpack
compilation step failed


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


Python buildpack failed to work on CF 210

王小锋 <zzuwxf at gmail.com...>
 

Hi, there

I upgraded CloudFoundry to verion 210 from 205 last week, today when I push
a "hello world" python project (works before) to CF using command below:

cf push python11 -p python-sample.zip -b
https://github.com/cloudfoundry/python-buildpack

it failed with followoing error, seems pre-comipled package does not work
on latest stack cflinuxfs2, any ideas?

BTW, when I push python project using cached python buildpack 1.3.1 with
old stack lucid64, it worked.

2015-07-10T03:27:05.72+0000 [DEA] OUT Got staging request for app with
id 04900427-41c0-48c4-9cae-e904b9b6caa4
2015-07-10T03:27:06.69+0000 [STG] OUT -----> Downloaded app package
(4.0K)
2015-07-10T03:27:06.76+0000 [STG] ERR Cloning into
'/tmp/buildpacks/python-buildpack'...
2015-07-10T03:27:13.58+0000 [STG] OUT Submodule 'compile-extensions' (
https://github.com/cloudfoundry-incubator/compile-extensions.git)
registered for path 'compile-extensions'
2015-07-10T03:27:13.62+0000 [STG] ERR Cloning into
'compile-extensions'...
2015-07-10T03:27:16.67+0000 [STG] OUT Submodule path
'compile-extensions': checked out 'f752ecf4b27d2f31bb082dfe7a47c76fefc769d7'
2015-07-10T03:27:16.79+0000 [STG] OUT -------> Buildpack version 1.4.0
2015-07-10T03:27:16.83+0000 [STG] OUT -----> Installing runtime
(python-2.7.6)
2015-07-10T03:27:31.22+0000 [STG] OUT -----> Installing dependencies
with pip
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash md5 was
not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
md5
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha1 was
not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
sha1
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha224
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
sha224
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha256
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
sha256
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha384
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
sha384
2015-07-10T03:27:31.27+0000 [STG] ERR ERROR:root:code for hash sha512
was not found.
2015-07-10T03:27:31.27+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 139, in <module>
2015-07-10T03:27:31.27+0000 [STG] ERR globals()[__func_name] =
__get_hash(__func_name)
2015-07-10T03:27:31.27+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/hashlib.py", line 91, in
__get_builtin_constructor
2015-07-10T03:27:31.27+0000 [STG] ERR raise ValueError('unsupported
hash type ' + name)
2015-07-10T03:27:31.27+0000 [STG] ERR ValueError: unsupported hash type
sha512
2015-07-10T03:27:31.37+0000 [STG] ERR Traceback (most recent call last):
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/bin/pip", line 9, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR
load_entry_point('pip==7.0.1', 'console_scripts', 'pip')()
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 552, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2672, in
load_entry_point
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2345, in load
2015-07-10T03:27:31.37+0000 [STG] ERR File
"build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line 2351, in
resolve
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/__init__.py",
line 15, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.vcs import git,
mercurial, subversion, bazaar # noqa
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/vcs/mercurial.py",
line 10, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip.download import
path_to_url
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/download.py",
line 38, in <module>
2015-07-10T03:27:31.37+0000 [STG] ERR from pip._vendor import
requests, six
2015-07-10T03:27:31.37+0000 [STG] ERR File
"/app/.heroku/python/lib/python2.7/site-packages/pip-7.0.1-py2.7.egg/pip/_vendor/__init__.py",
line 92, in load_module
2015-07-10T03:27:31.37+0000 [STG] ERR raise ImportError("No module
named '%s'" % (name,))
2015-07-10T03:27:31.37+0000 [STG] ERR ImportError: No module named
'pip._vendor.requests'
2015-07-10T03:27:31.38+0000 [STG] OUT Staging failed: Buildpack
compilation step failed


Re: Issues on Diego Deployment on Openstack

Eric Malm <emalm@...>
 

Hi, Mohamed,

Thanks for reporting the problems you've encountered. As Gwenn pointed out,
this has already been reported on GitHub in
https://github.com/cloudfoundry-incubator/diego-release/issues/60, and is
likely a version mismatch between cf-release and the consul service
properties generated in the diego-release deployment manifest. We track the
compatible versions of cf-release and diego-release that pass through our
testing pipelines in the
https://github.com/cloudfoundry-incubator/diego-cf-compatibility repo.
There's unfortunately not a lot of explanation in the README there at the
moment, but the Diego team has a story coming up soon (
https://www.pivotaltracker.com/story/show/93811624) to provide more
documentation about how to interpret those records.

For now, I recommend the following process to deploy compatible releases:

- If you are deploying a recent final release of CF, the release notes (
https://github.com/cloudfoundry/cf-release/releases) for that version will
contain a link to a compatible final version (0.N.0 for some number N) of
diego-release. You can then check out the git tag 0.N.0, upload the release
YAML file to your BOSH director, and generate your diego deployment
manifest. Make sure to have both the new CF and Diego releases uploaded
before deploying Diego, as the Diego deployment co-locates some jobs from
cf-release (consul-agent, metron-agent) on its VMs.

- If you are deploying a recent development version of CF, search for the
first 8 characters of its commit SHA in the CF_RELEASE_COMMIT_SHA column of
https://github.com/cloudfoundry-incubator/diego-cf-compatibility/blob/master/compatibility-v1.csv.
(GitHub conveniently lets you filter for those records via the search bar
at the top of the displayed CSV.) If there is a 'release_candidate' record,
check out and deploy the final version of diego-release listed in the
DIEGO_RELEASE_VERSION column as described above. If there is only a
'development' record for that cf-release SHA, you can check out the
diego-release SHA from the DIEGO_RELEASE_COMMIT_SHA column, generate a dev
release from that, and upload and deploy that to your BOSH. Please note
that those release combinations may not be as stable, though.

- If you are deploying from the tip of diego-release's develop branch,
which you should typically be doing only when doing development on Diego,
you likely want to deploy either the runtime-passed or develop branches of
cf-release, although there are no guarantees about the stability or
compatibility of the releases on those 'edge' branches.

It's important to note that in general the master branch of cf-release and
the master branch of diego-release are not guaranteed to be compatible, as
the Diego team creates minor final versions on a much faster cadence than
cf-release creates its major versions.

We're not currently publishing example manifests for specific
infrastructures, although we would like to as we expand the Diego testing
pipelines to more infrastructures and as we publish more about the
AWS-based environments we currently use in our pipeline.

Thanks,
Eric, CF Runtime Diego PM


On Thu, Jul 9, 2015 at 7:09 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Missing of documentation really ?

There is a lot of documentation about Diego

https://github.com/cloudfoundry-incubator/diego-release
https://github.com/cloudfoundry-incubator/diego-design-notes



Btw if you look at the issue, your problem is already there and fix
https://github.com/cloudfoundry-incubator/diego-release/issues/60

On Fri, Jul 10, 2015 at 6:39 AM, Mohamed Mohamed <
mohamed.mohamed(a)telecom-sudparis.eu> wrote:

Hi,

We are trying to deploy Diego on Openstack (using microbosh), since there
is no clear documentation on doing that we are having several problems.
The manifest that we are using is attached.

The error message that we are seeing for bosh deploy is:

```
...

Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 34: undefined method `tr' for ["bbs", {}]:Array) (00:00:00)


Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 34: undefined method `tr' for ["bbs", {}]:Array)
```

When we commented the bbs properties for database_z1

We had this error message:

```
...

Started preparing configuration > Binding configuration. Failed: Error filling in template `rep_ctl.erb' for `cell_z1/0' (line 70: Can't find property `["diego.rep.bbs.api_url"]') (00:00:01)


Error 100: Error filling in template `rep_ctl.erb' for `cell_z1/0' (line 70: Can't find property `["diego.rep.bbs.api_url"]')
```


Did anybody succeed to deploy diego on openstack? If yes, is it possible
to share the used manifest with the group because many people are having
same issues?

Any suggestion is welcome!

Thanks and regards,
Mohamed


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

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


Re: R: Re: Deploy CF on OpenStack, api and uaa failing

Gwenn Etourneau
 

What log do you have into the dir /var/vcap/sys/log/cloudcontroller_ng/
thanks?

On Thu, Jul 9, 2015 at 8:56 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello,

I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they
looks the same as the ones I can see by manually ssh into the VM.
What is the difference?


I'd point you to this logs from api, about the nfs mounter:

mount.nfs: mount(2): No such file or directory
[2015-07-09 09:24:31+0000] mount.nfs: trying 10.0.0.103 prog 100003 vers 3
prot TCP port 2049
[2015-07-09 09:24:34+0000] mount.nfs: portmap query retrying: RPC: Timed
out
[2015-07-09 09:24:34+0000] mount.nfs: trying 10.0.0.103 prog 100005 vers 3
prot TCP port 52652
[2015-07-09 09:24:36+0000] touch: cannot touch
'/var/vcap/nfs/shared/.nfs_test': Read-only file system
[2015-07-09 09:25:34+0000] stop: Unknown instance:
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted
[2015-07-09 09:25:38+0000] umount.nfs: remote share not in 'host:dir'
format
[2015-07-09 09:25:38+0000] umount.nfs: /var/vcap/nfs: not mounted

and:

idmapd stop/waiting
[2015-07-09 09:24:28+0000] idmapd start/running, process 4862
[2015-07-09 09:24:28+0000] NFS unmounted
[2015-07-09 09:24:28+0000] Mounting NFS...
[2015-07-09 09:24:36+0000] mount.nfs: timeout set for Thu Jul 9 09:26:29
2015
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,vers=4,addr=10.0.0.103,clientaddr=10.0.0.58'
[2015-07-09 09:24:36+0000] mount.nfs: trying text-based options
'timeo=10,intr,lookupcache=positive,addr=10.0.0.103'
[2015-07-09 09:24:36+0000] mount.nfs: prog 100003, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=17
[2015-07-09 09:24:36+0000] mount.nfs: prog 100005, trying vers=3, prot=6
[2015-07-09 09:24:36+0000] Failed to start: cannot write to NFS
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:34+0000] idmapd start/pre-start, process 5826
[2015-07-09 09:25:34+0000] Found NFS mount, unmounting...
[2015-07-09 09:25:38+0000] NFS unmounted
[2015-07-09 09:25:38+0000] Failed to unmount NFS, exiting...
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] idmapd start/pre-start, process 6755
[2015-07-09 09:27:18+0000] NFS unmounted
[2015-07-09 09:27:18+0000] Mounting NFS...

the manifest is on the prevuous email, I used the default manifest with
the openstack stub, after that I did some edits to solve varous errors,
like changing the default passwords for uaa and api, because they did not
match using spiff to generate the final manifest. I also added 10.0.0.0/24
instead of null on the allowed networks for nfs connections.

If I try to write in /var/vcap/nfs as root I get permission denied. If I
manually unmount and mount it back I still have no write permissions,
(strange because with null instead of 10.0.0.0/24 on allowed range, I had
permissions)

Thanks,
Michael


Il 09/07/15 12:56, *Gwenn Etourneau * <getourneau(a)pivotal.io> ha scritto:

Hi,

This log are not so usefull, can you login into the VM using bosh ssh and
go to /var/vcap/sys/log/ and you will see some folder and you will have
some log here.

thanks

On Thu, Jul 9, 2015 at 7:23 PM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'm trying to deploy CF on top of a little OpenStack cluster but I get
api and uaa VMs constantly on starting/failing status.



After each 'bosh deploy' with some changes on the configuration, I always
get:

Failed: `api_z1/0' is not running after update (00:11:07)
Error 400007: `api_z1/0' is not running after update


from api VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 7m*

*Process 'cloud_controller_ng' running*
*Process 'cloud_controller_worker_local_1' running*
*Process 'cloud_controller_worker_local_2' running*
*Process 'nginx_cc' running*
*Process 'cloud_controller_migration' running*
*Process 'routing-api' not monitored*
*Process 'metron_agent' running*
*Process 'statsd-injector' running*
*Process 'consul_agent' running*
*File 'nfs_mounter' accessible*
*System 'system_1572093d-c49a-4a38-9336-6d1a288b8bd7' running*

from uaa VM:
* monit summary*
*The Monit daemon 5.2.4 uptime: 11m*

*Process 'uaa' Connection failed*
*Process 'uaa_cf-registrar' initializing*
*Process 'metron_agent' running*
*Process 'consul_agent' running*
*System 'system_24698313-5f71-4b4f-94fc-8e09a8da0866' running*



I attach some useful info like: manifest (most probably where the error
is), and logs from uaa, nfs and api
Ps. I am using a domain that is not registered on the internet, but i
have a custom dns that resolve *.domain.co with the floating IP of the
ha_proxy (assigned manually)

Thank you!

Michael

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

------------------------------

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


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

8701 - 8720 of 9425