Date   

Re: cf push fails (goroutine errors)

James Bayer
 

i believe this could be related to this:
https://github.com/cloudfoundry/cli/issues/509
tracked it this story:
https://www.pivotaltracker.com/story/show/98672332

On Thu, Jul 16, 2015 at 6:42 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:



On 16 July 2015 at 13:06, Alexander Lomov <alexander.lomov(a)altoros.com>
wrote:

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.
You are right, I forget to activate the trace. Here
<https://drive.google.com/open?id=0B8Z5KYzSwwx3TURrbUtfMnNCa2c> is the
log, but I do not really understand the 'goroutine' problem. Do you have
any idea?


- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry
I will try to run the Acceptance Tests.



Best wishes,
Alex L.
Best and thank you,



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

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and
the applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
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


--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

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


--
Thank you,

James Bayer


Re: cf push fails (goroutine errors)

Michele Santuari <michele.santuari@...>
 

On 16 July 2015 at 13:06, Alexander Lomov <alexander.lomov(a)altoros.com>
wrote:

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.
You are right, I forget to activate the trace. Here
<https://drive.google.com/open?id=0B8Z5KYzSwwx3TURrbUtfMnNCa2c> is the log,
but I do not really understand the 'goroutine' problem. Do you have any
idea?


- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry
I will try to run the Acceptance Tests.



Best wishes,
Alex L.
Best and thank you,



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

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
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


--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.


Re: CF client library

Noburou TANIGUCHI
 

Thank you James, for telling about the ActiveStates' library and proposing to
publish the information about client libraries on docs.cloudfoundry.org.

I think the information on this thread is helpful not only for me but other
Cloud Foundry users / developers. So it seems very good idea to publish and
maintain it on the official site.





--
View this message in context: http://cf-dev.70369.x6.nabble.com/CF-client-library-tp712p750.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: cf push fails (goroutine errors)

Alexander Lomov <alexander.lomov@...>
 

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.

- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry

Best wishes,
Alex L.

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

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

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


cf push fails (goroutine errors)

Michele Santuari <michele.santuari@...>
 

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.


Re: 3 etcd nodes don't work well in single zone

Gwenn Etourneau
 

I guess ,
It can run with 3 nodes but it seems it not doing well with the 3 nodes on
the same zone.



On Thu, Jul 16, 2015 at 10:18 AM, Li, Tony <Tonyl(a)fast.au.fujitsu.com>
wrote:

Hi,



We installed CF210 recently (in single AZ).

Single etcd instance(instance number is 1) runs very well.

But multi etcd instances(instance number is 3) don't work well in single
AZ.



And from the release Notes on
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210,
there is one term I’m confused about:



“Upgrade etcd server to 2.0.1 details
<https://www.pivotaltracker.com/story/show/91070214>

Should be run as 1 node (for small deployments) or 3 nodes spread across
zones (for HA)”



May I ask it means:



“1. Should be run as 1 node (but can NOT be run as 3 nodes) in
environment with only one zone.

2. Should be run as 3 nodes in environment with more than one zones.
should spread them across zones.”



Or means:

“1. can be run as 1 node, (and can also be run as 3 nodes) in
environment with only one zone.

2. Should be run as 3 nodes in environment with more than one zones.
should spread them across zones.”



Thanks,



*Tony*
Disclaimer

The information in this e-mail is confidential and may contain content
that is subject to copyright and/or is commercial-in-confidence and is
intended only for the use of the above named addressee. If you are not the
intended recipient, you are hereby notified that dissemination, copying or
use of the information is strictly prohibited. If you have received this
e-mail in error, please telephone Fujitsu Australia Software Technology Pty
Ltd on + 61 2 9452 9000 or by reply e-mail to the sender and delete the
document and all copies thereof.

Whereas Fujitsu Australia Software Technology Pty Ltd would not knowingly
transmit a virus within an email communication, it is the receiver’s
responsibility to scan all communication and any files attached for
computer viruses and other defects. Fujitsu Australia Software Technology
Pty Ltd does not accept liability for any loss or damage (whether direct,
indirect, consequential or economic) however caused, and whether by
negligence or otherwise, which may result directly or indirectly from this
communication or any files attached.

If you do not wish to receive commercial and/or marketing email messages
from Fujitsu Australia Software Technology Pty Ltd, please email
unsubscribe(a)fast.au.fujitsu.com


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


3 etcd nodes don't work well in single zone

Tony
 

Hi,

We installed CF210 recently (in single AZ).
Single etcd instance(instance number is 1) runs very well.
But multi etcd instances(instance number is 3) don't work well in single AZ.

And from the release Notes on http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210, there is one term I’m confused about:

“Upgrade etcd server to 2.0.1 details<https://www.pivotaltracker.com/story/show/91070214>
Should be run as 1 node (for small deployments) or 3 nodes spread across zones (for HA)”

May I ask it means:

“1. Should be run as 1 node (but can NOT be run as 3 nodes) in environment with only one zone.
2. Should be run as 3 nodes in environment with more than one zones. should spread them across zones.”

Or means:
“1. can be run as 1 node, (and can also be run as 3 nodes) in environment with only one zone.
2. Should be run as 3 nodes in environment with more than one zones. should spread them across zones.”

Thanks,

Tony
Disclaimer

The information in this e-mail is confidential and may contain content that is subject to copyright and/or is commercial-in-confidence and is intended only for the use of the above named addressee. If you are not the intended recipient, you are hereby notified that dissemination, copying or use of the information is strictly prohibited. If you have received this e-mail in error, please telephone Fujitsu Australia Software Technology Pty Ltd on + 61 2 9452 9000 or by reply e-mail to the sender and delete the document and all copies thereof.


Whereas Fujitsu Australia Software Technology Pty Ltd would not knowingly transmit a virus within an email communication, it is the receiver’s responsibility to scan all communication and any files attached for computer viruses and other defects. Fujitsu Australia Software Technology Pty Ltd does not accept liability for any loss or damage (whether direct, indirect, consequential or economic) however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication or any files attached.


If you do not wish to receive commercial and/or marketing email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe(a)fast.au.fujitsu.com


Re: Incubation Proposal: Project CF-Abacus

Chris Sterling
 

This looks like a useful service. Thanks for the contribution!

Chris Sterling
chris.sterling(a)gmail.com
twitter: @csterwa
linkedin: http://www.linkedin.com/in/chrissterling

On Wed, Jul 15, 2015 at 8:37 AM, Duncan Johnston Watt <
duncan.johnstonwatt(a)cloudsoftcorp.com> wrote:

+1 this looks incredibly useful.

Best

Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

On 15 July 2015 at 15:07, James Bayer <jbayer(a)pivotal.io> wrote:

thanks to ibm for this proposal! we're excited to review this in more
depth.

what this means for service authors is that they would have a standard
system component and format for to track custom billing metrics for service
usage other than "how long was this service deployed". consider an email
service, you could track usage for every email sent or for a data service
you could track the amount of disk usage for data storage. it opens up a
lot of flexibility for how to do chargeback and showback.

for operators, in addition to apps, if the services provided on the
platform use this approach or are translated to this, it provides a
standard way to roll-up usage for a tenant across all of their platform
usage and present it nicely aggregated.

looking forward to the feedback,

james

On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim(a)us.ibm.com>
wrote:

Hi,

This email is to introduce and propose project Abacus to the CF
community for incubation.

*What?*

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and
metering component such that users can project and drill down on the costs
they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use
to provide usage data, but also, how to aggregate that information, as well
as a component to expose the aggregated data into a format (JSON) that can
be subsequently consumed by users — this is done via a drill down UI in
Bluemix.

Project Abacus is an extracted Open Source Software version (under
Apache 2.0 license) of the APIs, usage metering, and aggregation components
from the Bluemix feature.

Finally, it’s important to state that project Abacus uses a
micro-services architecture and is written in Node.js with CouchDB
compatible DBs as datastore and for map/reduce aggregations. Also, all
components can actually run as CF apps or be externalized. In Bluemix they
run as apps.

In other words, this is a bit different from other CF components,
however, we have reviewed Abacus with our colleagues from Pivotal and they
also believe it warrants incubation.

*When?*

Now.

Find the first self-contained release here:
https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README
<https://github.com/jsdelfino/cf-abacus/blob/master/README.md>that can
help you setup and try this first release. The team has included a fake
broker that can be used to generate usage data so you can try the whole
thing out of the box.

*How?*

We plan to introduce this as part of the CAB call discussion tomorrow
07/15 and field any questions.

The next step will be to get approval and become an incubation project.
Once this is done we will be staffing the project with a team (many from
the Bluemix engineers that created it) as well as a PM, and follow the CFF
guidelines for new projects.

We are ready to move on this with no delays and we welcome all
interested parties to try out the first release and to help us refine the
APIs and subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone

_______________________________________________
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

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: Incubation Proposal: Project CF-Abacus

Duncan Johnston-Watt <duncan.johnstonwatt@...>
 

+1 this looks incredibly useful.

Best

Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

On 15 July 2015 at 15:07, James Bayer <jbayer(a)pivotal.io> wrote:

thanks to ibm for this proposal! we're excited to review this in more
depth.

what this means for service authors is that they would have a standard
system component and format for to track custom billing metrics for service
usage other than "how long was this service deployed". consider an email
service, you could track usage for every email sent or for a data service
you could track the amount of disk usage for data storage. it opens up a
lot of flexibility for how to do chargeback and showback.

for operators, in addition to apps, if the services provided on the
platform use this approach or are translated to this, it provides a
standard way to roll-up usage for a tenant across all of their platform
usage and present it nicely aggregated.

looking forward to the feedback,

james

On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim(a)us.ibm.com>
wrote:

Hi,

This email is to introduce and propose project Abacus to the CF community
for incubation.

*What?*

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and
metering component such that users can project and drill down on the costs
they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use to
provide usage data, but also, how to aggregate that information, as well as
a component to expose the aggregated data into a format (JSON) that can be
subsequently consumed by users — this is done via a drill down UI in
Bluemix.

Project Abacus is an extracted Open Source Software version (under Apache
2.0 license) of the APIs, usage metering, and aggregation components from
the Bluemix feature.

Finally, it’s important to state that project Abacus uses a
micro-services architecture and is written in Node.js with CouchDB
compatible DBs as datastore and for map/reduce aggregations. Also, all
components can actually run as CF apps or be externalized. In Bluemix they
run as apps.

In other words, this is a bit different from other CF components,
however, we have reviewed Abacus with our colleagues from Pivotal and they
also believe it warrants incubation.

*When?*

Now.

Find the first self-contained release here:
https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README
<https://github.com/jsdelfino/cf-abacus/blob/master/README.md>that can
help you setup and try this first release. The team has included a fake
broker that can be used to generate usage data so you can try the whole
thing out of the box.

*How?*

We plan to introduce this as part of the CAB call discussion tomorrow
07/15 and field any questions.

The next step will be to get approval and become an incubation project.
Once this is done we will be staffing the project with a team (many from
the Bluemix engineers that created it) as well as a PM, and follow the CFF
guidelines for new projects.

We are ready to move on this with no delays and we welcome all interested
parties to try out the first release and to help us refine the APIs and
subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone

_______________________________________________
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

--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.


Re: R: Cant login from cf CLI, "Missing grant type"

Filip Hanik
 

Make sure you use the latest version of the CLI, that could be an issue too

On Wed, Jul 15, 2015 at 9:25 AM, Filip Hanik <fhanik(a)pivotal.io> wrote:

You shouldn't have to add the client to the manifest, as it is
automatically added here:

https://github.com/cf-identity/cf-release/blob/identity-latest/jobs/uaa/templates/uaa.yml.erb#L128-L137

If you wish to add it, it would look like:

properties:
uaa:
clients:
cf:
authorities: "uaa.none"
authorized-grant-types: "implicit,password,refresh_token"
scope:
"cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write,doppler.firehose"
secret: ""




On Wed, Jul 15, 2015 at 7:35 AM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Minimal update, I attach the new manifest, cf login trace and uaa.log
relevant part.

I am thinking that is related to the uaa->clients part of the manifest

thank you.
Michael

Il 15/07/15 08:57, *Michael Grifalconi * <
michael.grifalconi(a)studenti.unimi.it> ha scritto:

Hello all,

I can login using the web interface (login.mydomain.com) but when I try
on the cf CLI, I get:

Server error, status code 400, error code: invalid_request, message:
Missing grant type

Am I missing something in the (attached)manifest?

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


Re: R: Cant login from cf CLI, "Missing grant type"

Filip Hanik
 

You shouldn't have to add the client to the manifest, as it is
automatically added here:
https://github.com/cf-identity/cf-release/blob/identity-latest/jobs/uaa/templates/uaa.yml.erb#L128-L137

If you wish to add it, it would look like:

properties:
uaa:
clients:
cf:
authorities: "uaa.none"
authorized-grant-types: "implicit,password,refresh_token"
scope:
"cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write,doppler.firehose"
secret: ""




On Wed, Jul 15, 2015 at 7:35 AM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Minimal update, I attach the new manifest, cf login trace and uaa.log
relevant part.

I am thinking that is related to the uaa->clients part of the manifest

thank you.
Michael

Il 15/07/15 08:57, *Michael Grifalconi * <
michael.grifalconi(a)studenti.unimi.it> ha scritto:

Hello all,

I can login using the web interface (login.mydomain.com) but when I try
on the cf CLI, I get:

Server error, status code 400, error code: invalid_request, message:
Missing grant type

Am I missing something in the (attached)manifest?

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


Re: Incubation Proposal: Project CF-Abacus

Christopher B Ferris <chrisfer@...>
 

Thanks, James.
 
We're excited to begin collaboration around this with the other members.
 
Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Open Cloud
IBM Software Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris
blog: http://thoughtsoncloud.com/index.php/author/cferris/
phone: +1 508 667 0402
 
 

----- Original message -----
From: James Bayer <jbayer@...>
Sent by: cf-dev-bounces@...
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Cc:
Subject: Re: [cf-dev] Incubation Proposal: Project CF-Abacus
Date: Wed, Jul 15, 2015 10:07 AM
 
thanks to ibm for this proposal! we're excited to review this in more depth.
 
what this means for service authors is that they would have a standard system component and format for to track custom billing metrics for service usage other than "how long was this service deployed". consider an email service, you could track usage for every email sent or for a data service you could track the amount of disk usage for data storage. it opens up a lot of flexibility for how to do chargeback and showback.
 
for operators, in addition to apps, if the services provided on the platform use this approach or are translated to this, it provides a standard way to roll-up usage for a tenant across all of their platform usage and present it nicely aggregated.
 
looking forward to the feedback,
 
james
 
On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim@...> wrote:
Hi,

This email is to introduce and propose project Abacus to the CF community for incubation.

What?

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and metering component such that users can project and drill down on the costs they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use to provide usage data, but also, how to aggregate that information, as well as a component to expose the aggregated data into a format (JSON) that can be subsequently consumed by users — this is done via a drill down UI in Bluemix.

Project Abacus is an extracted Open Source Software version (under Apache 2.0 license) of the APIs, usage metering, and aggregation components from the Bluemix feature.

Finally, it’s important to state that project Abacus uses a micro-services architecture and is written in Node.js with CouchDB compatible DBs as datastore and for map/reduce aggregations. Also, all components can actually run as CF apps or be externalized. In Bluemix they run as apps.

In other words, this is a bit different from other CF components, however, we have reviewed Abacus with our colleagues from Pivotal and they also believe it warrants incubation.

When?

Now. 

Find the first self-contained release here: https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README that can help you setup and try this first release. The team has included a fake broker that can be used to generate usage data so you can try the whole thing out of the box.

How?

We plan to introduce this as part of the CAB call discussion tomorrow 07/15 and field any questions.

The next step will be to get approval and become an incubation project. Once this is done we will be staffing the project with a team (many from the Bluemix engineers that created it) as well as a PM, and follow the CFF guidelines for new projects.

We are ready to move on this with no delays and we welcome all interested parties to try out the first release and to help us refine the APIs and subsequent releases.

------
Best,

IBM CF team

 
dr.max
ibm cloud labs
silicon valley, ca
 
Sent from my iPhone

_______________________________________________
cf-dev mailing list
cf-dev@...
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
 
 
 
--
Thank you,
 
James Bayer
_______________________________________________
cf-dev mailing list
cf-dev@...
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: CF client library

James Bayer
 

i believe activestate also maintains a javascript client [1]. i'm not sure
how closely that tracks the cloud controller api and if it has other non-cf
foundation extensions that map only to activestate stackato functionality.
we can add this detail to a docs page on docs.cloudfoundry.org and note
which ones are in the cf foundation and which ones are public, but not
foundation projects.

[1] https://github.com/ActiveState/cloud-foundry-client-js

On Wed, Jul 15, 2015 at 4:29 AM, Noburou TANIGUCHI <dev(a)nota.m001.jp> wrote:

Or just DIY... cloudcontroller are pretty well documented.
Yes. I've just forgotten it. Thanks ;-).





--
View this message in context:
http://cf-dev.70369.x6.nabble.com/CF-client-library-tp712p736.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
--
Thank you,

James Bayer


Re: Incubation Proposal: Project CF-Abacus

James Bayer
 

thanks to ibm for this proposal! we're excited to review this in more depth.

what this means for service authors is that they would have a standard
system component and format for to track custom billing metrics for service
usage other than "how long was this service deployed". consider an email
service, you could track usage for every email sent or for a data service
you could track the amount of disk usage for data storage. it opens up a
lot of flexibility for how to do chargeback and showback.

for operators, in addition to apps, if the services provided on the
platform use this approach or are translated to this, it provides a
standard way to roll-up usage for a tenant across all of their platform
usage and present it nicely aggregated.

looking forward to the feedback,

james

On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim(a)us.ibm.com>
wrote:

Hi,

This email is to introduce and propose project Abacus to the CF community
for incubation.

*What?*

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and
metering component such that users can project and drill down on the costs
they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use to
provide usage data, but also, how to aggregate that information, as well as
a component to expose the aggregated data into a format (JSON) that can be
subsequently consumed by users — this is done via a drill down UI in
Bluemix.

Project Abacus is an extracted Open Source Software version (under Apache
2.0 license) of the APIs, usage metering, and aggregation components from
the Bluemix feature.

Finally, it’s important to state that project Abacus uses a micro-services
architecture and is written in Node.js with CouchDB compatible DBs as
datastore and for map/reduce aggregations. Also, all components can
actually run as CF apps or be externalized. In Bluemix they run as apps.

In other words, this is a bit different from other CF components, however,
we have reviewed Abacus with our colleagues from Pivotal and they also
believe it warrants incubation.

*When?*

Now.

Find the first self-contained release here:
https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README
<https://github.com/jsdelfino/cf-abacus/blob/master/README.md>that can
help you setup and try this first release. The team has included a fake
broker that can be used to generate usage data so you can try the whole
thing out of the box.

*How?*

We plan to introduce this as part of the CAB call discussion tomorrow
07/15 and field any questions.

The next step will be to get approval and become an incubation project.
Once this is done we will be staffing the project with a team (many from
the Bluemix engineers that created it) as well as a PM, and follow the CFF
guidelines for new projects.

We are ready to move on this with no delays and we welcome all interested
parties to try out the first release and to help us refine the APIs and
subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone

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


--
Thank you,

James Bayer


Incubation Proposal: Project CF-Abacus

Michael Maximilien
 

Hi,

This email is to introduce and propose project Abacus to the CF community for incubation.

What?

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and metering component such that users can project and drill down on the costs they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use to provide usage data, but also, how to aggregate that information, as well as a component to expose the aggregated data into a format (JSON) that can be subsequently consumed by users — this is done via a drill down UI in Bluemix.

Project Abacus is an extracted Open Source Software version (under Apache 2.0 license) of the APIs, usage metering, and aggregation components from the Bluemix feature.

Finally, it’s important to state that project Abacus uses a micro-services architecture and is written in Node.js with CouchDB compatible DBs as datastore and for map/reduce aggregations. Also, all components can actually run as CF apps or be externalized. In Bluemix they run as apps.

In other words, this is a bit different from other CF components, however, we have reviewed Abacus with our colleagues from Pivotal and they also believe it warrants incubation.

When?

Now.

Find the first self-contained release here: https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README that can help you setup and try this first release. The team has included a fake broker that can be used to generate usage data so you can try the whole thing out of the box.

How?

We plan to introduce this as part of the CAB call discussion tomorrow 07/15 and field any questions.

The next step will be to get approval and become an incubation project. Once this is done we will be staffing the project with a team (many from the Bluemix engineers that created it) as well as a PM, and follow the CFF guidelines for new projects.

We are ready to move on this with no delays and we welcome all interested parties to try out the first release and to help us refine the APIs and subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone


R: Cant login from cf CLI, "Missing grant type"

Michael Grifalconi <michael.grifalconi@...>
 

Minimal update, I attach the new manifest, cf login trace and uaa.log relevant part.

I am thinking that is related to the uaa->clients part of the manifest

thank you.
Michael

Il 15/07/15 08:57, Michael Grifalconi <michael.grifalconi(a)studenti.unimi.it> ha scritto:

Hello all,

I can login using the web interface (login.mydomain.com) but when I try on the cf CLI, I get:

Server error, status code 400, error code: invalid_request, message: Missing grant type

Am I missing something in the (attached)manifest?

Thank you!

Michael

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


Re: App placement in Diego

Ken Ojiri
 

Hi Eric,

I am very interested in this topic.
If I use Diego on hybrid(public+private) cloud environment, I will
surely use the feature.

Some '+placement-constraints' labeled tickets on Diego tracker have a
link to a proposal document (
https://github.com/pivotal-cf-experimental/diego-dev-notes/blob/master/accepted_proposals/placement_pools.md
), but I can not access it. (GitHub says 404...)
Could you let us see it?

Thanks,
Ken

---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 23, 2015 at 5:25 AM, Eric Malm <emalm(a)pivotal.io> wrote:
Hi, Josh,

You're probably remembering some discussion about the 'placement pools' or
'placement constraints' feature. We haven't implemented any of that
functionality yet in Diego, but we do have a series of stories in the Diego
tracker (https://www.pivotaltracker.com/n/projects/1003146) with the
'+placement-constraints' label that represents the currently planned work on
that track. As we complete the necessary work to get Diego to be ready for
production use, we do expect it to be among the first of the new features we
start work on.

Thanks,
Eric, CF Runtime Diego PM


On Thu, Jun 18, 2015 at 9:04 AM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote:

Hi All,

One of the features of Diego I heard about a while ago, when I first heard
about Diego, was the ability to restrict an application’s placement to
certain availability zones / cells / etc. I’ve been looking around for
documentation on this — specifically, if it’s in Diego already and if not, a
roadmap, but I’m coming up short. Can anyone here point me to some
documentation on this feature? Our client is quite interested in it. 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






_______________________________________________
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: CF client library

Noburou TANIGUCHI
 

Or just DIY... cloudcontroller are pretty well documented.
Yes. I've just forgotten it. Thanks ;-).





--
View this message in context: http://cf-dev.70369.x6.nabble.com/CF-client-library-tp712p736.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: Deploying diego on openstack

Lev Berman <lev.berman@...>
 

Hello!

I described my experience and posted some samples here -
http://cf-dev.70369.x6.nabble.com/cf-dev-Recipe-to-install-Diego-tp40.html

On Mon, Jul 6, 2015 at 4:34 PM, Pramod Mandagere <nagapramod(a)gmail.com>
wrote:

Hi All,
All the documentation and github code (manifest stubs) deal with deploying
diego with bosh-lite. Are there any pointer/docs for generating an
openstack manifest for diego deployment using microbosh?
If some one has an example deployment, can u post a sample manifest,
Regards,



--
Lev Berman

Altoros - Cloud Foundry deployment, training and integration

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


Re: CF client library

Gwenn Etourneau
 

Or just DIY... cloudcontroller are pretty well documented.

On Wed, Jul 15, 2015 at 4:01 PM, Noburou TANIGUCHI <dev(a)nota.m001.jp> wrote:

Thank you Alex, and everyone.

I'd like to summarize the current status:

- 1) Language-independent
-- 1a) Use `cf curl` as external command (
https://github.com/cloudfoundry/cli )
-- 1b) Use CF cli RPC server like cli plugins do (
https://github.com/cloudfoundry/cli )

- 2) Language-dependent
-- 2a) Golang (official): cli: https://github.com/cloudfoundry/cli
-- 2b) Java (official): cf-java-client:
https://github.com/cloudfoundry/cf-java-client
-- 2c) .Net (incubator): cf-dotnet-sdk:
https://github.com/cloudfoundry-incubator/cf-dotnet-sdk
-- 2d) Golang (community): go-cfclient:
https://github.com/cloudfoundry-community/go-cfclient
-- 2e) Ruby (attic - outdated?): cfoundry:
https://github.com/cloudfoundry-attic/cfoundry (*1)
-- 2f) Node.js (attic -outdated?): vcap-node:
https://github.com/cloudfoundry-attic/vcap-node (*2)

(*1) There are some personal? forks such as
https://github.com/lukehwang/cfoundry
(*2) I've found recently

If there is another one, please let me know.



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/CF-client-library-tp712p732.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

8641 - 8660 of 9425