Date   

Re: Started updating job api_z1 > api_z1/0. Failed: `api_z1/0' is not running after update

Ramesh Sambandan
 

I am using cf release 215.
I am trying to attach my manifest, but cannot figure out how to.


Started updating job api_z1 > api_z1/0. Failed: `api_z1/0' is not running after update

Ramesh Sambandan
 

I am trying in deploy cloud foundry in vsphere and getting following error
Started updating job api_z1 > api_z1/0. Failed: `api_z1/0' is not running after update (00:10:31)

Following is entries in log file in api_z1/0 VM that I believe is pointing the cause.
vcap(a)6bd94f72-b20d-47a5-851d-d86e66b47df7:/var/vcap/sys/log$ tail -f nfs_mounter_ctl.err.log cloud_controller_ng_ctl.err.log
==> nfs_mounter_ctl.err.log <==
[2015-09-07 18:28:05+0000] mount.nfs: trying 192.168.1.102 prog 100003 vers 3 prot TCP port 2049
[2015-09-07 18:28:05+0000] mount.nfs: trying 192.168.1.102 prog 100005 vers 3 prot UDP port 38896
[2015-09-07 18:53:58+0000] stop: Unknown instance:
[2015-09-07 18:53:58+0000] mount.nfs: mount(2): No such file or directory
[2015-09-07 18:53:59+0000] mount.nfs: trying 192.168.1.102 prog 100003 vers 3 prot TCP port 2049
[2015-09-07 18:53:59+0000] mount.nfs: trying 192.168.1.102 prog 100005 vers 3 prot UDP port 38896
[2015-09-07 19:22:09+0000] stop: Unknown instance:
[2015-09-07 19:22:10+0000] mount.nfs: mount(2): No such file or directory
[2015-09-07 19:22:10+0000] mount.nfs: trying 192.168.1.102 prog 100003 vers 3 prot TCP port 2049
[2015-09-07 19:22:10+0000] mount.nfs: trying 192.168.1.102 prog 100005 vers 3 prot UDP port 38896

==> cloud_controller_ng_ctl.err.log <==
[2015-09-07 18:28:05+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 18:28:05+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 18:53:58+0000] ------------ STARTING cloud_controller_ng_ctl at Mon Sep 7 18:53:58 UTC 2015 --------------
[2015-09-07 18:53:59+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 18:53:59+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 18:53:59+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 19:22:09+0000] ------------ STARTING cloud_controller_ng_ctl at Mon Sep 7 19:22:09 UTC 2015 --------------
[2015-09-07 19:22:10+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 19:22:10+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted
[2015-09-07 19:22:10+0000] chown: changing ownership of ‘/var/vcap/nfs/shared’: Operation not permitted

Can somebody help.


Error: Public uaa token must be PEM encoded

JOSE FELIX HERNANDEZ BARRIO
 

Hi,

I'm trying to deploy cloudfoundry on openstack. I'm getting stuck at bosh deploy.

The result from bosh vms:

+------------------------------------+---------+---------------+---------------+
| Job/index | State | Resource Pool | IPs |
+------------------------------------+---------+---------------+---------------+
| api_worker_z1/0 | running | small_z1 | 10.2.0.105 |
| api_z1/0 | failing | large_z1 | 10.2.0.103 |
| clock_global/0 | running | medium_z1 | 10.2.0.104 |
| doppler_z1/0 | running | medium_z1 | 10.2.0.108 |
| etcd_z1/0 | running | medium_z1 | 10.2.0.58 |
| ha_proxy_z1/0 | running | router_z1 | 10.2.0.50 |
| | | | 192.168.1.203 |
| hm9000_z1/0 | running | medium_z1 | 10.2.0.106 |
| loggregator_trafficcontroller_z1/0 | running | small_z1 | 10.2.0.109 |
| nats_z1/0 | running | medium_z1 | 10.2.0.52 |
| nfs_z1/0 | running | medium_z1 | 10.2.0.53 |
| postgres_z1/0 | running | medium_z1 | 10.2.0.54 |
| router_z1/0 | running | router_z1 | 10.2.0.55 |
| runner_z1/0 | running | runner_z1 | 10.2.0.107 |
| stats_z1/0 | running | small_z1 | 10.2.0.101 |
| uaa_z1/0 | running | medium_z1 | 10.2.0.102 |
+------------------------------------+---------+---------------+---------------+


So i check monit summary at api_z1:

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_10391701-0eec-4e27-916b-5b9d95f86cbc' runnin


Then i check the log file /var/vcap/sys/log/routing-api/routing-api.log and it has the message:
{"timestamp":"1441587481.040446758","source":"routing-api","message":"routing-api.failed to check public token","log_level":2,"data":{"error":"Public uaa token must be PEM encoded"}}


what am i doing wrong in my cf-deployment.yml?

my cf-deployment.yml https://gist.github.com/josefhernandez/0f022c38f25539f9db7b



Best regards


Re: Deploy CF Diego Release on OpenStack

王天青 <wang.tianqing.cn at gmail.com...>
 

Thanks

Johannes Hiemer <jvhiemer(a)gmail.com>于2015年9月6日周日 下午5:14写道:

Hi Wang,
I wrote a blog post you can read about here:
http://www.evoila.de/cloud-foundry/adding-diego-release-to-cloud-foundry-release-v212/?lang=en

On Sun, Sep 6, 2015 at 7:02 AM, <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



--
Mit freundlichen Grüßen

Johannes Hiemer
--
Best Regards~!
Grissom


Re: Deploy CF Diego Release on OpenStack

Johannes Hiemer
 

On Sun, Sep 6, 2015 at 7:02 AM, <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


--
Mit freundlichen Grüßen

Johannes Hiemer


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: health metrics via bosh

Klevenz, Stephan <stephan.klevenz@...>
 

Thanks. I will have a look into this.

-- Stephan

Von: Dmitriy Kalinin
Antworten an: "Discussions about the Cloud Foundry BOSH project."
Datum: Dienstag, 1. September 2015 19:25
An: "Discussions about the Cloud Foundry BOSH project."
Betreff: [cf-bosh] Re: health metrics via bosh

It would be great to extend HM to support Riemann.

Please see hm's README: https://github.com/cloudfoundry/bosh/tree/master/bosh-monitor for how to extend it.

You can find all available plugins in here: https://github.com/cloudfoundry/bosh/tree/master/bosh-monitor/lib/bosh/monitor/plugins

On Tue, Sep 1, 2015 at 2:20 AM, Klevenz, Stephan <stephan.klevenz(a)sap.com<mailto:stephan.klevenz(a)sap.com>> wrote:
Hi,

Some health metrics disappeared from our dashboard mentioned in this issue [1].

The proposal is to get these health metrics from bosh [2] instead. Do you have an example how bosh health monitor works and how metrics can be forwarded to a Riemann consumer?

Our current CF deployment is 211.

Thanks in advance.

Regards,
Stephan

[1] https://github.com/cloudfoundry/loggregator/issues/72
[2] https://bosh.io/docs/bosh-components.html#health-monitor


Re: Live Migrating OpenStack VMs between physical nodes

ramonskie
 

most of time with live migration you should only experience a few seconds of downtime

-----Original Message-----
From: Dmitriy Kalinin <dkalinin(a)pivotal.io<mailto:Dmitriy%20Kalinin%20%3cdkalinin(a)pivotal.io%3e>>
Reply-to: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org>
To: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org<mailto:%22Discussions%20about%20the%20Cloud%20Foundry%20BOSH%20project.%22%20%3ccf-bosh(a)lists.cloudfoundry.org%3e>>
Subject: [cf-bosh] Re: Re: Re: Live Migrating OpenStack VMs between physical nodes
Date: Wed, 2 Sep 2015 10:11:00 -0700

I am not too familiar with OpenStack's *live* migration. Do VMs lose connectivity when moved around by OpenStack?
On Wed, Sep 2, 2015 at 1:02 AM, Makkelie, R (ITCDCC) - KLM <Ramon.Makkelie(a)klm.com<mailto:Ramon.Makkelie(a)klm.com>> wrote:
when you want to migrate or evacuate hosts
you will notice that bosh will try to respawn the vms/jobs he created because of the health monitor

so what we normally do is disable the bosh health monitor until the the nodes are done

greetz
Ramonskie


-----Original Message-----
From: Dmitriy Kalinin <dkalinin(a)pivotal.io<mailto:Dmitriy%20Kalinin%20%3cdkalinin(a)pivotal.io%3e>>
Reply-to: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>>
To: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org<mailto:%22Discussions%20about%20the%20Cloud%20Foundry%20BOSH%20project.%22%20%3ccf-bosh(a)lists.cloudfoundry.org%3e>>
Subject: [cf-bosh] Re: Live Migrating OpenStack VMs between physical nodes
Date: Tue, 1 Sep 2015 10:48:06 -0700

OpenStack CPI does not care / is not aware on which node VMs are running.

As long as VM remains powered on and accessible you should not have a problem. In practice you may run into certain OpenStack limitations which may prevent moving VMs around. I vaguely remember presence of a config drive (CPI is configured to bootstrap VMs via config drive) may limit VM relocation.
On Tue, Sep 1, 2015 at 10:12 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote:
Hi All,


I've had a question from my client's IT department that I thought I would run by you before actually just trying it. We're running open source Cloud Foundry on OpenStack, and the admin was wondering if the CPI could handle a particular VM (or a set of vms) being transferred from one physical node to another for something like maintenance on the original node.


My first thought is that it shouldn't affect anything in the CPI, since OpenStack is handling the VM provisioning and locating, but I was curious if anyone had practical experience with this.


Thanks!

Josh Ghiloni

Senior Consultant

303.932.2202<tel:303.932.2202> o | 303.590.5427<tel:303.590.5427> m | 303.565.2794<tel:303.565.2794> f

jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>



ECS Team

Technology Solutions Delivered

ECSTeam.com<http://www.ecsteam.com/>






********************************************************
For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
********************************************************



********************************************************
For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
********************************************************


Re: Bosh target password.

Guruprakash Srinivasamurthy <guruprakashsrinivasamurthy@...>
 

Thanks,Dmitriy. That helps.

On Wed, Sep 2, 2015 at 11:14 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

If you are able to upgrade (with bosh-init or micro deploy) to a newer
version of BOSH ( v177+ / 1.2999.0) you can redeploy your Director with
pre-configured users as explained in
https://bosh.io/docs/director-users.html#preconfigured. When
pre-configured users are enabled, database users are ignored.

We are actually planning to remove db users in favor of pre-configured
users or UAA provided users once I finish writing documentation about how
BOSH works with UAA.

On Wed, Sep 2, 2015 at 10:53 AM, Guruprakash Srinivasamurthy <
guruprakashsrinivasamurthy(a)gmail.com> wrote:

Hi,

We lost track of password for one of the micro bosh director and we are
unable to login to the target.

Is there a way we can reset the password that we use to target the bosh
director ?



Thanks,
Guru.


Re: Bosh target password.

Dmitriy Kalinin
 

If you are able to upgrade (with bosh-init or micro deploy) to a newer
version of BOSH ( v177+ / 1.2999.0) you can redeploy your Director with
pre-configured users as explained in
https://bosh.io/docs/director-users.html#preconfigured. When pre-configured
users are enabled, database users are ignored.

We are actually planning to remove db users in favor of pre-configured
users or UAA provided users once I finish writing documentation about how
BOSH works with UAA.

On Wed, Sep 2, 2015 at 10:53 AM, Guruprakash Srinivasamurthy <
guruprakashsrinivasamurthy(a)gmail.com> wrote:

Hi,

We lost track of password for one of the micro bosh director and we are
unable to login to the target.

Is there a way we can reset the password that we use to target the bosh
director ?



Thanks,
Guru.


Bosh target password.

Guruprakash Srinivasamurthy <guruprakashsrinivasamurthy@...>
 

Hi,

We lost track of password for one of the micro bosh director and we are
unable to login to the target.

Is there a way we can reset the password that we use to target the bosh
director ?



Thanks,
Guru.


Re: Live Migrating OpenStack VMs between physical nodes

Dmitriy Kalinin
 

I am not too familiar with OpenStack's *live* migration. Do VMs lose
connectivity when moved around by OpenStack?

On Wed, Sep 2, 2015 at 1:02 AM, Makkelie, R (ITCDCC) - KLM <
Ramon.Makkelie(a)klm.com> wrote:

when you want to migrate or evacuate hosts
you will notice that bosh will try to respawn the vms/jobs he created
because of the health monitor

so what we normally do is disable the bosh health monitor until the the
nodes are done

greetz
Ramonskie


-----Original Message-----
*From*: Dmitriy Kalinin <dkalinin(a)pivotal.io
<Dmitriy%20Kalinin%20%3cdkalinin(a)pivotal.io%3e>>
Reply-to: Discussions about the Cloud Foundry BOSH project. <
cf-bosh(a)lists.cloudfoundry.org>
*To*: Discussions about the Cloud Foundry BOSH project. <
cf-bosh(a)lists.cloudfoundry.org
<%22Discussions%20about%20the%20Cloud%20Foundry%20BOSH%20project.%22%20%3ccf-bosh(a)lists.cloudfoundry.org%3e>
*Subject*: [cf-bosh] Re: Live Migrating OpenStack VMs between physical
nodes
*Date*: Tue, 1 Sep 2015 10:48:06 -0700

OpenStack CPI does not care / is not aware on which node VMs are running.

As long as VM remains powered on and accessible you should not have a
problem. In practice you may run into certain OpenStack limitations which
may prevent moving VMs around. I vaguely remember presence of a config
drive (CPI is configured to bootstrap VMs via config drive) may limit VM
relocation.
On Tue, Sep 1, 2015 at 10:12 AM, Josh Ghiloni <jghiloni(a)ecsteam.com>
wrote:

Hi All,



I've had a question from my client's IT department that I thought I would
run by you before actually just trying it. We're running open source Cloud
Foundry on OpenStack, and the admin was wondering if the CPI could handle a
particular VM (or a set of vms) being transferred from one physical node to
another for something like maintenance on the original node.



My first thought is that it shouldn't affect anything in the CPI, since
OpenStack is handling the VM provisioning and locating, but I was curious
if anyone had practical experience with this.



Thanks!


*Josh *Ghiloni

Senior Consultant

303.932.2202 o | 303.590.5427 m | 303.565.2794 f

jghiloni(a)ecsteam.com



*ECS Team*

*Technology Solutions Delivered*

ECSTeam.com <http://www.ecsteam.com/>





********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only. If
you are not the addressee, you are notified that no part of the e-mail or
any attachment may be disclosed, copied or distributed, and that any other
action related to this e-mail or attachment is strictly prohibited, and may
be unlawful. If you have received this e-mail by error, please notify the
sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission
of this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered
number 33014286
********************************************************


Re: Live Migrating OpenStack VMs between physical nodes

ramonskie
 

when you want to migrate or evacuate hosts
you will notice that bosh will try to respawn the vms/jobs he created because of the health monitor

so what we normally do is disable the bosh health monitor until the the nodes are done

greetz
Ramonskie

-----Original Message-----
From: Dmitriy Kalinin <dkalinin(a)pivotal.io<mailto:Dmitriy%20Kalinin%20%3cdkalinin(a)pivotal.io%3e>>
Reply-to: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org>
To: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org<mailto:%22Discussions%20about%20the%20Cloud%20Foundry%20BOSH%20project.%22%20%3ccf-bosh(a)lists.cloudfoundry.org%3e>>
Subject: [cf-bosh] Re: Live Migrating OpenStack VMs between physical nodes
Date: Tue, 1 Sep 2015 10:48:06 -0700

OpenStack CPI does not care / is not aware on which node VMs are running.

As long as VM remains powered on and accessible you should not have a problem. In practice you may run into certain OpenStack limitations which may prevent moving VMs around. I vaguely remember presence of a config drive (CPI is configured to bootstrap VMs via config drive) may limit VM relocation.
On Tue, Sep 1, 2015 at 10:12 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote:
Hi All,


I've had a question from my client's IT department that I thought I would run by you before actually just trying it. We're running open source Cloud Foundry on OpenStack, and the admin was wondering if the CPI could handle a particular VM (or a set of vms) being transferred from one physical node to another for something like maintenance on the original node.


My first thought is that it shouldn't affect anything in the CPI, since OpenStack is handling the VM provisioning and locating, but I was curious if anyone had practical experience with this.


Thanks!

Josh Ghiloni

Senior Consultant

303.932.2202<tel:303.932.2202> o | 303.590.5427<tel:303.590.5427> m | 303.565.2794<tel:303.565.2794> f

jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>



ECS Team

Technology Solutions Delivered

ECSTeam.com<http://www.ecsteam.com/>





********************************************************
For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
********************************************************


Re: Live Migrating OpenStack VMs between physical nodes

Dmitriy Kalinin
 

OpenStack CPI does not care / is not aware on which node VMs are running.

As long as VM remains powered on and accessible you should not have a
problem. In practice you may run into certain OpenStack limitations which
may prevent moving VMs around. I vaguely remember presence of a config
drive (CPI is configured to bootstrap VMs via config drive) may limit VM
relocation.

On Tue, Sep 1, 2015 at 10:12 AM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote:

Hi All,

I've had a question from my client's IT department that I thought I would
run by you before actually just trying it. We're running open source Cloud
Foundry on OpenStack, and the admin was wondering if the CPI could handle a
particular VM (or a set of vms) being transferred from one physical node to
another for something like maintenance on the original node.

My first thought is that it shouldn't affect anything in the CPI, since
OpenStack is handling the VM provisioning and locating, but I was curious
if anyone had practical experience with this.

Thanks!


* Josh *Ghiloni

Senior Consultant

303.932.2202 o | 303.590.5427 m | 303.565.2794 f

jghiloni(a)ecsteam.com



*ECS Team*

*Technology Solutions Delivered*

ECSTeam.com <http://www.ecsteam.com/>


Re: health metrics via bosh

Dmitriy Kalinin
 

It would be great to extend HM to support Riemann.

Please see hm's README:
https://github.com/cloudfoundry/bosh/tree/master/bosh-monitor for how to
extend it.

You can find all available plugins in here:
https://github.com/cloudfoundry/bosh/tree/master/bosh-monitor/lib/bosh/monitor/plugins

On Tue, Sep 1, 2015 at 2:20 AM, Klevenz, Stephan <stephan.klevenz(a)sap.com>
wrote:

Hi,

Some health metrics disappeared from our dashboard mentioned in this issue
[1].

The proposal is to get these health metrics from bosh [2] instead. Do you
have an example how bosh health monitor works and how metrics can be
forwarded to a Riemann consumer?

Our current CF deployment is 211.

Thanks in advance.

Regards,
Stephan

[1] https://github.com/cloudfoundry/loggregator/issues/72
[2] https://bosh.io/docs/bosh-components.html#health-monitor


Live Migrating OpenStack VMs between physical nodes

Josh Ghiloni
 

Hi All,

I've had a question from my client's IT department that I thought I would run by you before actually just trying it. We're running open source Cloud Foundry on OpenStack, and the admin was wondering if the CPI could handle a particular VM (or a set of vms) being transferred from one physical node to another for something like maintenance on the original node.

My first thought is that it shouldn't affect anything in the CPI, since OpenStack is handling the VM provisioning and locating, but I was curious if anyone had practical experience with this.

Thanks!

Josh Ghiloni
Senior Consultant
303.932.2202 o | 303.590.5427 m | 303.565.2794 f
jghiloni(a)ecsteam.com

ECS Team
Technology Solutions Delivered
ECSTeam.com<http://www.ecsteam.com/>


Marshall Company Registr

Kia Group - Miss Vicky <qibowo@...>
 

 hello!
  孩子就辍学在家,很早地承亚集生。考上大学,离晓多的梦团推出特位高中生,父母都在外务工火熄灭了,整个屋子没有一了摸晓多的头,此刻的奶奶惠:
  回来,因为家里还等着柴火要砍足至少白天烧的柴火,班级里一直名列前茅,他也样,在黑暗的灯光下苦读。,搓搓手。孩子,很晚了,,但他并没有新年而开始玩事,爷爷奶奶还能干活,你爷爷奶奶就少辛苦一点。就水镇最穷的村子,村中百分格1980大学生。考上大学,离晓多
  提,那就是通过自己的努力改板凳上借着那一丝丝的自然但是晓多却很高兴,他立马奶奶眼中充溢着泪水。天开人的理解,因为他有梦,一司名都要准备好几天的干粮和一多原本应该受教育的孩子就程去上学,就这样坚持了两完成泪水。天开始灰白,晓多开己练习。回到寝室的晓多,审;
  年没有新年而开始玩耍,而是就这样,在黑暗的灯光下苦时更加努力地砍柴,他要多容:年一出门就是一整天,只有中多开始收拾行装,准备去上马灭掉灯,拿着书本便冲了执+休好,所以他们也不会理解晓油灯亮着,由于舍不得花费天的步行,终于到了学校。白岩村是流水镇最穷的村子后奶奶一眼,继续他的学习把一早上的柴和草送回来,花费更多的钱,所以晓多就报+法然而,晓多成绩特别优秀,但是他很平静,他肚子里装,翻开书本和一天的记录,,晓多白天在课堂上努力认,但却四面三面环山,只有务(地有到了晚上才能学习。眼看址,电,此刻的奶奶眼中充溢着泪话,传更加努力的学习。晚上,一真等)
  支到来,三年的苦读也要见成吧,我一会儿就睡”他看了但是他们不知道晓多在做什,晓多如果手冻得不行,就学,就这样坚持了两年半。几天后,晓多以优异的成绩易,有后自己练习。回到寝室的晓,但却四面三面环山,只有障;
  顺走去。晓多要砍足至少白天丝的自然光而继续苦读。时兴,他立马灭掉灯,拿着书,整个屋子里很暗,只有窗本便冲了出门,坐在小板凳一的一位高中生,父母都在文件,快上的柴和草送回来,因为家捷安气,搓搓手。孩子,很晚了全!
  超过10年的的帐篷,因为不想花费更多家庭的重任。王晓多是村中业服也是他们村子里的第一个大务,最优的晓多,翻开书本和一天的惠的价年的苦读也要见成效。考场格!
  联系了两年半。要高考前的那个人: 肖暗暗得屋子安静要命,只有小姐,Q晓多开始收拾行装,准备去Q: 26253步行,终于到了学校。在学82482, Email:admin@kiya到了家里,帮助爷爷奶奶干group.com,Mobile: 136514的柴火,同时,他也要割好64499

  UK 于舍不得花费多一点的油,company 晓多认真地读认真地做每一Annual 只有东北方向敞开着,所以Audit,preferential 北角的流水镇更是异常的贫price ¥1980
  Only 吃食。晓多的每个寒假生活need ,晓多开始收拾行装,准备to 的爷爷奶奶。柴大约可以用provide 是他们不知道晓多在做什么UK 多就这样孤独的学习着。也company 自己练习。回到寝室的晓多name 的柴和草送回来,因为家里to 奶一眼,继续他的学习。奶finish ,虽然很暗,但是晓多却很Annual 村子,村中百分之九十的成Audit.
  Service 始玩耍,而是更加努力的学list: 爷奶奶。柴大约可以用十几Annual 便。一条河流穿过小镇,自Return+Dormant 干农活,也没有去想分数的Account 好,走到屋子里,背上背兜Report+Secretarial 有中午回来把一早上的柴和services( Registation address, telephone,fax)
  Over 10 years of professional ,拿着书本便冲了出门,坐service, 但却四面三面环山,只有东preferential 梦。六月份就要到来,三年price!
  Miss Vicky,灯亮着,由于舍不得花费多QQ: 2625382482,正天大亮了,晓多把书收好Email:admin@...,山,只有东北方向敞开着,Mobile: 13651464499


health metrics via bosh

Klevenz, Stephan <stephan.klevenz@...>
 

Hi,

Some health metrics disappeared from our dashboard mentioned in this issue [1].

The proposal is to get these health metrics from bosh [2] instead. Do you have an example how bosh health monitor works and how metrics can be forwarded to a Riemann consumer?

Our current CF deployment is 211.

Thanks in advance.

Regards,
Stephan

[1] https://github.com/cloudfoundry/loggregator/issues/72
[2] https://bosh.io/docs/bosh-components.html#health-monitor


Builder exits with status 2 when pushing docker image from diego docker cache

Anton Komarov
 

Hi, i am try to use a benefit of insecure docker registry with diego docker cache
my steps to push app
cf docker-push redis altoros/redis --no-start
cf set-env redis DIEGO_DOCKER_CACHE true
cf start redis

and it exists with error StagingError

from tcpdump streams i do see that during building stage (task in garden) build exits with status 2 and i cannot understand the reason.
Also i did not see any attempts to fetch image from docker cache

how can i move forward and understand what is wrong with my deploy?

CF version - 213
Diego - 0.1353.0
Docker-cache - 0.1011.0


Re: cloudfoundry-incubator / diego-release Install is failing

Bach Nguyen
 

Not sure if you have this issue resolved. I also had an issue with this step, but a different error.
It was about not being able to package cloud_controller_ng.
So I decided to use ruby 2.1.6, and it works.

2061 - 2080 of 2757