Yes he also listens to udp4. By allowing udp 3456 and 3457, it worked.

Do you know why 3457 is used when the incoming listening port for
loggregator is specified as 3456?

Sent from my iPhone

On Jun 5, 2015, at 1:58 AM, Lev Berman <lev.berman(a)altoros.com> wrote:

We found the loggregator was listening on port 3456 and 3457 with upd6.


He also probably listens for udp4 connections. Have you tried to allow
udp4 traffic to ports 3456-3457 and check if loggregator collects the logs
after it?

On Fri, Jun 5, 2015 at 4:17 AM, Meng, Xiangyi <xiangyi.meng(a)emc.com>
wrote:

We found the loggregator was listening on port 3456 and 3457 with upd6.



udp6 0 0 [::]:3457 [::]:*





But we can’t use ipv6 in our env. So is there any way to force
loggregator to use ipv4?



Thanks,

Maggie



*From:* cf-dev-bounces(a)lists.cloudfoundry.org [mailto:
cf-dev-bounces(a)lists.cloudfoundry.org] *On Behalf Of *Lev Berman
*Sent:* 2015年6月2日 20:05

*To:* Discussions about Cloud Foundry projects and the system overall.
*Subject:* Re: [cf-dev] What ports will be needed to support hm and
loggregator



Sorry, I've missed your notes about the firewalls you configure for each
CF machine - this firewalls is what needs to be configured to accept UDP
traffic to ports 3456 and 3457 from any host. vSphere itself will probably
allow this traffic without any additional configuration.



On Tue, Jun 2, 2015 at 1:51 PM, Berman Lev <lev.berman(a)altoros.com>
wrote:

I have never worked with vSphere, unfortunately. I've googled a bit and
found this table which shows which TCP and UDP ports are open by default on
vSphere VMs -
https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.security.doc/GUID-ECEA77F5-D38E-4339-9B06-FF9B78E94B68.html.
Consult the vSphere documentation to find out how to add UDP 3456 and 3457
ports to this list.



On Tue, Jun 2, 2015 at 1:32 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com>
wrote:

I deployed my CF on vshpere server.



*From:* cf-dev-bounces(a)lists.cloudfoundry.org [mailto:
cf-dev-bounces(a)lists.cloudfoundry.org] *On Behalf Of *Lev Berman
*Sent:* 2015年6月2日 18:30


*To:* Discussions about Cloud Foundry projects and the system overall.
*Subject:* Re: [cf-dev] What ports will be needed to support hm and
loggregator



You have posted your Application Security Groups -
http://docs.pivotal.io/pivotalcf/adminguide/app-sec-groups.html. This
groups are created and managed by Cloud Foundry.

But the issue here is with security groups configured in your
infrastructure - AWS, OpenStack, etc. Which one is your CF deployed on?



On Tue, Jun 2, 2015 at 1:23 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com>
wrote:

Hi, Lev



Would you please let me know what exactly I should add to my security
group? Following are the current configuration.



- name: public_networks

rules:

- protocol: all

destination: 0.0.0.0-9.255.255.255

- protocol: all

destination: 11.0.0.0-169.253.255.255

- protocol: all

destination: 169.255.0.0-172.15.255.255

- protocol: all

destination: 172.32.0.0-192.167.255.255

- protocol: all

destination: 192.169.0.0-255.255.255.255

- name: dns

rules:

- protocol: tcp

destination: 0.0.0.0/0

ports: '53'

- protocol: udp

destination: 0.0.0.0/0

ports: '53'

default_running_security_groups:

- public_networks

- dns

default_staging_security_groups:

- public_networks

- dns



Thanks,

Maggie



*From:* cf-dev-bounces(a)lists.cloudfoundry.org [mailto:
cf-dev-bounces(a)lists.cloudfoundry.org] *On Behalf Of *Lev Berman
*Sent:* 2015年6月2日 18:16
*To:* Discussions about Cloud Foundry projects and the system overall.
*Subject:* Re: [cf-dev] What ports will be needed to support hm and
loggregator



Hi,

At least for loggregator to successflly talk to metron agents, you need
to add a rule to a security group for your private subnet allowing the
ingress UDP traffic through ports 3456 and 3457 from all hosts (0.0.0.0/0).
See more about security group rules needed for CF here -
http://docs.cloudfoundry.org/deploying/common/security_groups.html.




On Tue, Jun 2, 2015 at 1:04 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com>
wrote:

Hi,



I am updating my cf env from 172 to 197. But I found some issues after
upgrade is done. I couldn’t get the correct running application instance
number:



CF_TRACE=true cf apps

…

"running_instances": -1,

…

application started ?/3



Another issue is I can’t get log information from loggregator. “cf logs”
showed nothing after I restarted my application.



I think this may be related to our firewall configuration. Because in
another environment where no firewall is configured, hm and loggregator
work perfectly well. We have firewalls for deas, routers and all other
components separately(three firewalls). So would anyone please tell me what
ports we should open for deas, routers or other components?



Thanks,

Maggie





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



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





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



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





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



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





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



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

--
Lev Berman

Altoros - Cloud Foundry deployment, training and integration

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

_______________________________________________
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

Yes, I do recall that the feature did not work on bosh-lite but that was when kernel logging was disabled on the trusty stemcell.

Michael, could you send the json for the application security group you've applied to the space you're looking at?


-Dieu
CF Runtime PM





On Fri, Jun 5, 2015 at 5:48 PM, James Bayer <jbayer(a)pivotal.io> wrote:

i seem to remember something about app security group logging having an issue with bosh-lite that isn't present when you have a DEA in a VM. i remember something about that. i'll see if dieu remembers.





On Fri, Jun 5, 2015 at 1:06 PM, Michael <michael.grifalconi(a)studenti.unimi.it> wrote:

Hello, 


as you suggested, I looked deeper in this matter, and I can see that on the DEA VM:


 I get the right iptables rules, but I still can not see the logs on /var/log/messages


[Im using bosh-lite, latest stemcell, CF version 207]


Do you know what should I do to allow this information to be logged?


ref:https://www.pivotaltracker.com/n/projects/966314/stories/90078842


Thank you!


Best regards,

Michael



****************
Per destinare il 5x1000 all'Universita' degli Studi di Milano: indicare nella dichiarazione dei redditi il codice fiscale 80012650158.

http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille

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

--

Thank you,

James Bayer

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

We found the loggregator was listening on port 3456 and 3457 with upd6.

He also probably listens for udp4 connections. Have you tried to allow udp4 traffic to ports 3456-3457 and check if loggregator collects the logs after it?

On Fri, Jun 5, 2015 at 4:17 AM, Meng, Xiangyi <xiangyi.meng(a)emc.com> wrote:


We found the loggregator was listening on port 3456 and 3457 with upd6.



udp6 0 0 [::]:3457 [::]:*





But we can’t use ipv6 in our env. So is there any way to force loggregator to use ipv4?



Thanks,

Maggie



From: cf-dev-bounces(a)lists.cloudfoundry.org [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Lev Berman
Sent: 2015年6月2日 20:05


To: Discussions about Cloud Foundry projects and the system overall.
Subject: Re: [cf-dev] What ports will be needed to support hm and loggregator


Sorry, I've missed your notes about the firewalls you configure for each CF machine - this firewalls is what needs to be configured to accept UDP traffic to ports 3456 and 3457 from any host. vSphere itself will probably allow this traffic without any additional configuration.



On Tue, Jun 2, 2015 at 1:51 PM, Berman Lev <lev.berman(a)altoros.com> wrote:

I have never worked with vSphere, unfortunately. I've googled a bit and found this table which shows which TCP and UDP ports are open by default on vSphere VMs - https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.security.doc/GUID-ECEA77F5-D38E-4339-9B06-FF9B78E94B68.html. Consult the vSphere documentation to find out how to add UDP 3456 and 3457 ports to this list.



On Tue, Jun 2, 2015 at 1:32 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com> wrote:

I deployed my CF on vshpere server.



From: cf-dev-bounces(a)lists.cloudfoundry.org [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Lev Berman
Sent: 2015年6月2日 18:30


To: Discussions about Cloud Foundry projects and the system overall.
Subject: Re: [cf-dev] What ports will be needed to support hm and loggregator



You have posted your Application Security Groups - http://docs.pivotal.io/pivotalcf/adminguide/app-sec-groups.html. This groups are created and managed by Cloud Foundry.

But the issue here is with security groups configured in your infrastructure - AWS, OpenStack, etc. Which one is your CF deployed on?



On Tue, Jun 2, 2015 at 1:23 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com> wrote:

Hi, Lev



Would you please let me know what exactly I should add to my security group? Following are the current configuration.



- name: public_networks

rules:

- protocol: all

destination: 0.0.0.0-9.255.255.255

- protocol: all

destination: 11.0.0.0-169.253.255.255

- protocol: all

destination: 169.255.0.0-172.15.255.255

- protocol: all

destination: 172.32.0.0-192.167.255.255

- protocol: all

destination: 192.169.0.0-255.255.255.255

- name: dns

rules:

- protocol: tcp

destination: 0.0.0.0/0

ports: '53'

- protocol: udp

destination: 0.0.0.0/0

ports: '53'

default_running_security_groups:

- public_networks

- dns

default_staging_security_groups:

- public_networks

- dns



Thanks,

Maggie



From: cf-dev-bounces(a)lists.cloudfoundry.org [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Lev Berman
Sent: 2015年6月2日 18:16
To: Discussions about Cloud Foundry projects and the system overall.
Subject: Re: [cf-dev] What ports will be needed to support hm and loggregator



Hi,

At least for loggregator to successflly talk to metron agents, you need to add a rule to a security group for your private subnet allowing the ingress UDP traffic through ports 3456 and 3457 from all hosts (0.0.0.0/0). See more about security group rules needed for CF here - http://docs.cloudfoundry.org/deploying/common/security_groups.html.





On Tue, Jun 2, 2015 at 1:04 PM, Meng, Xiangyi <xiangyi.meng(a)emc.com> wrote:

Hi,



I am updating my cf env from 172 to 197. But I found some issues after upgrade is done. I couldn’t get the correct running application instance number:



CF_TRACE=true cf apps

…

"running_instances": -1,

…

application started ?/3



Another issue is I can’t get log information from loggregator. “cf logs” showed nothing after I restarted my application.



I think this may be related to our firewall configuration. Because in another environment where no firewall is configured, hm and loggregator work perfectly well. We have firewalls for deas, routers and all other components separately(three firewalls). So would anyone please tell me what ports we should open for deas, routers or other components?



Thanks,

Maggie





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



Github: https://github.com/ldmberman





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



Github: https://github.com/ldmberman





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



Github: https://github.com/ldmberman





--

Lev Berman

Altoros - Cloud Foundry deployment, training and integration



Github: https://github.com/ldmberman

--
Lev Berman

Altoros - Cloud Foundry deployment, training and integration

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

i seem to remember something about app security group logging having an
issue with bosh-lite that isn't present when you have a DEA in a VM. i
remember something about that. i'll see if dieu remembers.

On Fri, Jun 5, 2015 at 1:06 PM, Michael <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello,


as you suggested, I looked deeper in this matter, and I can see that on
the DEA VM:


I get the right iptables rules, but I still can not see the logs on
/var/log/messages


[Im using bosh-lite, latest stemcell, CF version 207]


Do you know what should I do to allow this information to be logged?


ref:https://www.pivotaltracker.com/n/projects/966314/stories/90078842


Thank you!


Best regards,

Michael



****************
Per destinare il 5x1000 all'Universita' degli Studi di Milano: indicare
nella dichiarazione dei redditi il codice fiscale 80012650158.


http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille

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

--
Thank you,

James Bayer

Date: Wed, 3 Jun 2015 17:18:43 -0700
From: Supraja Yasoda <ykmsupraja(a)gmail.com>
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Service offering testService not found
Message-ID:
<
CADnEmc45Wckbup+GNBtCm_TRjx-Y7jwXBFk2YkqQZ8YO5RxRLw(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

I have deleted service broker by removing service instances. I created
again but now I am unable to enable-service-access to Service. I get error
"Service offering testService not found".
When I do get I see catalog gets service Id, name under service definition.
Could someone suggest one the same.
--

*Regards,*
-------------- next part --------------

Hi,

We had a meeting for the Runtime PMC earlier this week.
Notes available here:

https://github.com/cloudfoundry/pmc-notes/blob/master/Runtime/2015-06-02-runtime.md

-Dieu

Replying myself :I
i think it was due the fact that something was messed up during updating
git sub modules before creating release, recreating to make sure it's ok.


---
Armin ranjbar


On Fri, Jun 5, 2015 at 6:28 PM, Armin Ranjbar <zoup(a)zoup.org> wrote:

Hello,

when trying to deploy CF, i get this error during build process of HM9000.
CF RELEASE : 210+dev.2 , commit hash: c6f46acd
bosh-openstack-kvm-ubuntu-trusty-go_agent v2978

Started compiling packages >
hm9000/b27306493cef0f36b94eacb6821ce0e53fc386d6. Failed: Action Failed
get_task: Task 57eec963-9620-42a8-43dd-3b193d7b928f result: Compiling
package hm9000: Running packaging script: Command exited with 1; Stdout: ,
Stderr: ++ readlink -nf /var/vcap/packages/golang1.4
+ export
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+ export
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ export GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ go install github.com/cloudfoundry/hm9000
hm9000/src/
github.com/cloudfoundry/hm9000/actualstatelistener/actual_state_listener.go:16:2:
cannot find package "github.com/cloudfoundry/yagnats" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/cloudfoundry/yagnats (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/cloudfoundry/yagnats
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm9000.go:11:2: no buildable
Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/codegangsta/cli
hm9000/src/
github.com/cloudfoundry/storeadapter/etcdstoreadapter/etcd_store_adapter.go:10:2:
cannot find package "github.com/coreos/go-etcd/etcd" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/coreos/go-etcd/etcd (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/coreos/go-etcd/etcd
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry/hm9000/apiserver/handlers/basic_auth_handler.go:6:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/goji/httpauth
hm9000/src/github.com/cloudfoundry/gunk/diegonats/fake_nats_client.go:8:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/nu7hatch/gouuid
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/onsi/gomega
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/nats_client_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/pivotal-golang/lager
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:11:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:12:2:
cannot find package "github.com/tedsuo/ifrit/ginkgomon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:10:2:
cannot find package "github.com/tedsuo/ifrit/grouper" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/grouper (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/grouper
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:16:2: cannot
find package "github.com/tedsuo/ifrit/http_server" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/http_server (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/http_server (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:11:2:
cannot find package "github.com/tedsuo/ifrit/restart" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/restart (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/restart
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:17:2: cannot
find package "github.com/tedsuo/ifrit/sigmon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/sigmon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/sigmon
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/apiserver/routes.go:3:8: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/rata
(00:05:56)

Error 450001: Action Failed get_task: Task
57eec963-9620-42a8-43dd-3b193d7b928f result: Compiling package hm9000:
Running packaging script: Command exited with 1; Stdout: , Stderr: ++
readlink -nf /var/vcap/packages/golang1.4
+ export
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+ export
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ export GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ go install github.com/cloudfoundry/hm9000
hm9000/src/
github.com/cloudfoundry/hm9000/actualstatelistener/actual_state_listener.go:16:2:
cannot find package "github.com/cloudfoundry/yagnats" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/cloudfoundry/yagnats (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/cloudfoundry/yagnats
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm9000.go:11:2: no buildable
Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/codegangsta/cli
hm9000/src/
github.com/cloudfoundry/storeadapter/etcdstoreadapter/etcd_store_adapter.go:10:2:
cannot find package "github.com/coreos/go-etcd/etcd" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/coreos/go-etcd/etcd (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/coreos/go-etcd/etcd
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry/hm9000/apiserver/handlers/basic_auth_handler.go:6:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/goji/httpauth
hm9000/src/github.com/cloudfoundry/gunk/diegonats/fake_nats_client.go:8:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/nu7hatch/gouuid
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/onsi/gomega
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/nats_client_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/pivotal-golang/lager
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:11:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:12:2:
cannot find package "github.com/tedsuo/ifrit/ginkgomon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:10:2:
cannot find package "github.com/tedsuo/ifrit/grouper" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/grouper (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/grouper
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:16:2: cannot
find package "github.com/tedsuo/ifrit/http_server" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/http_server (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/http_server (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:11:2:
cannot find package "github.com/tedsuo/ifrit/restart" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/restart (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/restart
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:17:2: cannot
find package "github.com/tedsuo/ifrit/sigmon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/sigmon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/sigmon
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/apiserver/routes.go:3:8: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/rata



---
Armin ranjbar

Hello,

when trying to deploy CF, i get this error during build process of HM9000.
CF RELEASE : 210+dev.2 , commit hash: c6f46acd
bosh-openstack-kvm-ubuntu-trusty-go_agent v2978

Started compiling packages >
hm9000/b27306493cef0f36b94eacb6821ce0e53fc386d6. Failed: Action Failed
get_task: Task 57eec963-9620-42a8-43dd-3b193d7b928f result: Compiling
package hm9000: Running packaging script: Command exited with 1; Stdout: ,
Stderr: ++ readlink -nf /var/vcap/packages/golang1.4
+ export
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+ export
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ export GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ go install github.com/cloudfoundry/hm9000
hm9000/src/
github.com/cloudfoundry/hm9000/actualstatelistener/actual_state_listener.go:16:2:
cannot find package "github.com/cloudfoundry/yagnats" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/cloudfoundry/yagnats (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/cloudfoundry/yagnats
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm9000.go:11:2: no buildable Go
source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/codegangsta/cli
hm9000/src/
github.com/cloudfoundry/storeadapter/etcdstoreadapter/etcd_store_adapter.go:10:2:
cannot find package "github.com/coreos/go-etcd/etcd" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/coreos/go-etcd/etcd (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/coreos/go-etcd/etcd
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry/hm9000/apiserver/handlers/basic_auth_handler.go:6:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/goji/httpauth
hm9000/src/github.com/cloudfoundry/gunk/diegonats/fake_nats_client.go:8:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/nu7hatch/gouuid
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/onsi/gomega
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/nats_client_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/pivotal-golang/lager
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:11:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:12:2: cannot
find package "github.com/tedsuo/ifrit/ginkgomon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/ginkgomon
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:10:2:
cannot find package "github.com/tedsuo/ifrit/grouper" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/grouper (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/grouper
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:16:2: cannot
find package "github.com/tedsuo/ifrit/http_server" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/http_server (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/http_server (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:11:2:
cannot find package "github.com/tedsuo/ifrit/restart" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/restart (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/restart
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:17:2: cannot
find package "github.com/tedsuo/ifrit/sigmon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/sigmon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/sigmon
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/apiserver/routes.go:3:8: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/rata
(00:05:56)

Error 450001: Action Failed get_task: Task
57eec963-9620-42a8-43dd-3b193d7b928f result: Compiling package hm9000:
Running packaging script: Command exited with 1; Stdout: , Stderr: ++
readlink -nf /var/vcap/packages/golang1.4
+ export
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+
GOROOT=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39
+ export
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+
PATH=/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/bin:/var/vcap/bosh/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
+ export GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ GOPATH=/var/vcap/data/compile/hm9000/hm9000
+ go install github.com/cloudfoundry/hm9000
hm9000/src/
github.com/cloudfoundry/hm9000/actualstatelistener/actual_state_listener.go:16:2:
cannot find package "github.com/cloudfoundry/yagnats" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/cloudfoundry/yagnats (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/cloudfoundry/yagnats
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm9000.go:11:2: no buildable Go
source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/codegangsta/cli
hm9000/src/
github.com/cloudfoundry/storeadapter/etcdstoreadapter/etcd_store_adapter.go:10:2:
cannot find package "github.com/coreos/go-etcd/etcd" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/coreos/go-etcd/etcd (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/coreos/go-etcd/etcd
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry/hm9000/apiserver/handlers/basic_auth_handler.go:6:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/goji/httpauth
hm9000/src/github.com/cloudfoundry/gunk/diegonats/fake_nats_client.go:8:2:
no buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/nu7hatch/gouuid
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/onsi/gomega
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/nats_client_runner.go:10:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/pivotal-golang/lager
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:11:2: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit
hm9000/src/
github.com/cloudfoundry/gunk/diegonats/gnatsd_test_runner.go:12:2: cannot
find package "github.com/tedsuo/ifrit/ginkgomon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/ginkgomon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/ginkgomon
(from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:10:2:
cannot find package "github.com/tedsuo/ifrit/grouper" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/grouper (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/grouper
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:16:2: cannot
find package "github.com/tedsuo/ifrit/http_server" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/http_server (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/ifrit/http_server (from $GOPATH)
hm9000/src/
github.com/cloudfoundry-incubator/natbeat/background_heartbeat.go:11:2:
cannot find package "github.com/tedsuo/ifrit/restart" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/restart (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/restart
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/hm/serve_api.go:17:2: cannot
find package "github.com/tedsuo/ifrit/sigmon" in any of:

/var/vcap/data/packages/golang1.4/f57ddbc8d55d7a0f08775bf76bb6a27dc98c7ea7.1-99cad68115a543a556da19ff44cca94ba0ff7d39/src/
github.com/tedsuo/ifrit/sigmon (from $GOROOT)
/var/vcap/data/compile/hm9000/hm9000/src/github.com/tedsuo/ifrit/sigmon
(from $GOPATH)
hm9000/src/github.com/cloudfoundry/hm9000/apiserver/routes.go:3:8: no
buildable Go source files in /var/vcap/data/compile/hm9000/hm9000/src/
github.com/tedsuo/rata



---
Armin ranjbar

Finally, it works after I changed the configuration related to memory and
disk for dea.

< disk_mb: 2048
---

disk_mb: 10000

1025c1029
< memory_overcommit_factor: 3
---

memory_overcommit_factor: 8

1028c1032
< staging_disk_limit_mb: 6144
---

staging_disk_limit_mb: 4096

[#1] Received on [staging.advertise] :
'{"id":"0-2b2f83b4755749aba3c31cc58a69a306","stacks":["lucid64","cflinuxfs2"],"available_memory":8192,"available_disk":20000}'
[#2] Received on [staging.advertise] :
'{"id":"0-2b2f83b4755749aba3c31cc58a69a306","stacks":["lucid64","cflinuxfs2"],"available_memory":8192,"available_disk":20000}'

After I deployed a simple php-demo application, they are changed to

[#8] Received on [staging.advertise] :
'{"id":"0-2b2f83b4755749aba3c31cc58a69a306","stacks":["lucid64","cflinuxfs2"],"available_memory":8064,"available_disk":18976}'
[#9] Received on [staging.advertise] :
'{"id":"0-2b2f83b4755749aba3c31cc58a69a306","stacks":["lucid64","cflinuxfs2"],"available_memory":8064,"available_disk":18976}'


However, I still cannot understand why my previous configuration led to
"Staging error: no available stagers" as the nats messages below said it
has enough resource. My php application is only consuming 128M memory and
1G disk. Who can share some insights?

[#41] Received on [staging.advertise] :
'{"id":"0-05b732df21c54f9cab3ac42869b4be64","stacks":["lucid64","cflinuxfs2"],"available_memory":3072,"available_disk":4096}'


ubuntu(a)boshclivm:~/apps/cf-php-demo$ cat manifest.yml
---
applications:
- name: cf-php-demo
memory: 128M
instances: 1
host: cf-php-demo
path: .

ubuntu(a)boshclivm:~/apps/cf-php-demo$ cf apps
name requested state instances memory disk urls
cf-php-demo started 1/1 128M 1G
cf-php-demo.runmyapp.io



On Thu, Jun 4, 2015 at 5:08 PM, Guangcai Wang <guangcai.wang(a)gmail.com>
wrote:

I got the nats message on 'staging.advertise'. It has the enough
resource. but it seems not correct. And it also cannot explain the error -
Server error, status code: 400, error code: 170001, message: Staging error:
no available stagers.

[#41] Received on [staging.advertise] :
'{"id":"0-05b732df21c54f9cab3ac42869b4be64","stacks":["lucid64","cflinuxfs2"],"available_memory":3072,"available_disk":4096}'
[#42] Received on [staging.advertise] :
'{"id":"0-05b732df21c54f9cab3ac42869b4be64","stacks":["lucid64","cflinuxfs2"],"available_memory":3072,"available_disk":4096}'
[#43] Received on [staging.advertise] :
'{"id":"0-05b732df21c54f9cab3ac42869b4be64","stacks":["lucid64","cflinuxfs2"],"available_memory":3072,"available_disk":4096}'
[#44] Received on [staging.advertise] :
'{"id":"0-05b732df21c54f9cab3ac42869b4be64","stacks":["lucid64","cflinuxfs2"],"available_memory":3072,"available_disk":4096}'



+------------------------------------+---------+---------------+---------------+
| Job/index | State | Resource Pool |
IPs |

+------------------------------------+---------+---------------+---------------+
| api_worker_z1/0 | running | small_z1 |
100.64.0.23 |
| api_z1/0 | running | medium_z1 |
100.64.0.21 |
| clock_global/0 | running | medium_z1 |
100.64.0.22 |
| etcd_z1/0 | running | medium_z1 |
100.64.1.8 |
| ha_proxy_z1/0 | running | router_z1 |
100.64.1.0 |
| | | |
137.172.74.90 |
| hm9000_z1/0 | running | medium_z1 |
100.64.0.24 |
| loggregator_trafficcontroller_z1/0 | running | small_z1 |
100.64.0.27 |
| loggregator_z1/0 | running | medium_z1 |
100.64.0.26 |
| login_z1/0 | running | medium_z1 |
100.64.0.20 |
| nats_z1/0 | running | medium_z1 |
100.64.1.2 |
| nfs_z1/0 | running | medium_z1 |
100.64.1.3 |
| postgres_z1/0 | running | medium_z1 |
100.64.1.4 |
| router_z1/0 | running | router_z1 |
100.64.1.5 |
| runner_z1/0 | running | runner_z1 |
100.64.0.25 |
| stats_z1/0 | running | small_z1 |
100.64.0.18 |
| uaa_z1/0 | running | medium_z1 |
100.64.0.19 |

+------------------------------------+---------+---------------+---------------+


- 100.64.0.25

m1.large | 8GB RAM | 4 VCPU | 20.0GB Disk

92cf66ec-f2e1-4505-bd25-28c02e991535 | m1.large | 8192 |
20 | 20 | | 4 | 1.0 | True


On Thu, Jun 4, 2015 at 11:57 AM, Guangcai Wang <guangcai.wang(a)gmail.com>
wrote:

From the source code
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/dea/app_stager_task.rb:26,
it seems there is no enough for memory or disk.

def stage(&completion_callback)
@stager_id = @stager_pool.find_stager(@app.stack.name,
staging_task_memory_mb, staging_task_disk_mb)
raise Errors::ApiError.new_from_details('StagingError', 'no
available stagers') unless @stager_id


However, this is my first app. It should be light. The DEA is using
m1.large which is
m1.large | 4096 | 20

Anyone has the same error? and any suggestion on manifest or debug tips?

Another question, I want to add more debug information in
cloud_controller_ng.log. I tried to add some code in
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/dea/app_stager_task.rb,
but it did not show in the log. How to do?


On Thu, Jun 4, 2015 at 10:14 AM, Guangcai Wang <guangcai.wang(a)gmail.com>
wrote:

attached the deployment manifest. This is generated by spiff and then I
modified it.

On Thu, Jun 4, 2015 at 12:47 AM, Takeshi Morikawa <moog0814(a)gmail.com>
wrote:

Please check the 'staging.advertise' of nats message
https://github.com/cloudfoundry/dea_ng#staging

sample command:
bundle exec nats-sub -s
nats://[nats.user]:[nats.password]@[nats_ipaddress]:[nats.port]
'staging.advertise'


I have one additional request
Can you share your bosh deployment manifest?

_______________________________________________
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

On 4 Jun 2015, at 01:05, Onsi Fakhouri <ofakhouri(a)pivotal.io> wrote:

Well done Services API! This is an awesome milestone!

On Wed, Jun 3, 2015 at 5:04 PM, Chip Childers <cchilders(a)cloudfoundry.org> wrote:
Awesome news! Long time coming, and it opens up a whole world of additional capabilities for users.

Nice work everyone!

On Jun 4, 2015, at 9:00 AM, Shannon Coen <scoen(a)pivotal.io> wrote:

On behalf of the Services API team, including Dojo participants from IBM and SAP, I'm pleased to announce experimental availability and published documentation for this much-anticipated feature.

As of cf-release v208 and CLI v6.11.1, Cloud Foundry now supports an enhanced service broker integration in support of long-running provisioning, update, and delete operations. This significantly broadens the supported use cases for Cloud Foundry Marketplace Services, and I can't wait to hear what creative things the ecosystem does with it. Provision VMs, orchestrate clusters, install software, move data... yes, your broker can even open support tickets to have those things done manually!

This feature is currently considered experimental, as we'd like you all to review our docs, try out the feature, and give us feedback. We very interested to hear about any confusion in the docs or the UX, and any sticky issues you encounter in implementation. Our goal is for our docs enable a painless, intuitive (can we hope for joyful?) implementation experience.

We have not bumped the broker API yet for this feature. You'll notice that our documentation for the feature is separate from the stable API docs at this point. Once we're confident in the design (we're relying on your feedback!), we'll bump the broker API version, move the docs for asynchronous operations into the stable docs, AND implement support for asynchronous bind/create-key and unbind/delete-key.

Documentation:
- http://docs.cloudfoundry.org/services/asynchronous-operations.html
- http://docs.cloudfoundry.org/services/api.html
Example broker for AWS (contributed by IBM):
- http://docs.cloudfoundry.org/services/examples.html
- https://github.com/cloudfoundry-samples/go_service_broker
Demo of the feature presented at CF Summit 2015:
- https://youtu.be/Ij5KSKrAq9Q

tl;dr

Cloud Foundry expects broker responses within 60 seconds. Now a broker can return an immediate response indicating that a provision, update, or delete operation is in progress. Cloud Foundry then returns a similar response to the client, and begins polling the broker for the status of the operation. Users, via API clients, can discover the status of the operation ("in progress", "succeeded", or "failed"), and brokers can provide user-facing messages in response to each poll which are exposed to users (e.g. "VMs provisioned, installing software, 30% complete").

Thank you,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
_______________________________________________
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