If you are trying to get the actual JWT token of your current UAA instance
targeted by UAAC, you can try:
$uaac context


On Wed, Feb 10, 2016 at 6:10 AM, Corentin Dupont <
corentin.dupont(a)create-net.org> wrote:

Still struggling...

I have already an account with CF, so I tried:

$ uaac token client get
Client ID: admin
Client secret: ************

Successfully fetched token via client credentials grant.
Target: http://uaa.172.16.0.191.xip.io
Context: admin, from client admin

Then:
$ uaac token decode

Note: no key given to validate token signature

jti: 908139b9-28be-4490-9ffd-a0e6b2f1XXXX
sub: admin
authorities: password.write scim.write clients.write clients.read
scim.read
uaa.admin clients.secret
scope: scim.read uaa.admin password.write scim.write clients.write
clients.read clients.secret
client_id: admin
cid: admin
azp: admin
grant_type: client_credentials
rev_sig: 78635a00
iat: 1455113000
exp: 1455156200
iss: https://uaa.172.16.0.191.xip.io/oauth/token
zid: uaa
aud: admin scim uaa password clients


There is nothing looking like the "Authorization: bearer" code from the
cURL command below...
Should I use the "jti" field?

Thanks a lot Hristo!!
Corentin


On Wed, Feb 10, 2016 at 12:38 AM, Hristo Iliev <hsiliev(a)gmail.com> wrote:

You should create a client with the proper permissions/authorities. For
bosh-lite this is done with:

gem install cf-uaac
uaac target uaa.bosh-lite.com --skip-ssl-validation
uaac token client get admin -s admin-secret
uaac client add id --authorized_grant_types client_credentials --authorities cloud_controller.admin --secret secret


The ones above (CC.admin) are perhaps too much for just reading the
events.

2016-02-09 18:11 GMT+02:00 Corentin Dupont <
corentin.dupont(a)create-net.org>:

Thanks Hristo.
I'm trying to retrieve the info from the API:

curl "https://api.[your-domain.com]/v2/app_usage_events?results-per-page=1&after_guid=5f9db08a-3e18-4b1e-a09b-14be78eb3dab" -X GET \
-H "Authorization: bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoidWFhLWlkLTQ2MSIsImVtYWlsIjoiZW1haWwtMzMyQHNvbWVkb21haW4uY29tIiwic2NvcGUiOlsiY2xvdWRfY29udHJvbGxlci5hZG1pbiJdLCJhdWQiOlsiY2xvdWRfY29udHJvbGxlciJdLCJleHAiOjE0NTQ0NTE2Mzl9.4MWgEkbhuyG21w9vyZ_p8UhkY_YU0UoiGdscbqvr5bM" \
-H "Host: example.org" \
-H "Cookie: "

But how can I get my authorization token?



---------- Forwarded message ----------

From: Hristo Iliev <hsiliev(a)gmail.com>
To: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
Cc: dc4cities-project <dc4cities-project(a)create-net-ml.org>
Date: Tue, 9 Feb 2016 17:27:42 +0200
Subject: Re: [cf-dev] apps logs
Hi,

You can check the the App Usage Events API [1]. They are discarded
after some time (default: a month), so you should move the info to a
dedicated DB if you need audit events.

Regards,
Hristo Iliev

[1]
http://apidocs.cloudfoundry.org/230/app_usage_events/list_all_app_usage_events.html

2016-02-09 16:26 GMT+02:00 Corentin Dupont <
corentin.dupont(a)create-net.org>:

Hi guys,
I would like to know if there is a log somewhere containing the number
of apps in CF (result of cf apps)? Or a log of the scale up/down commands?
I need to make an analysis of all the scaling up/down operations that
happened on the infrastructure.

Thanks a lot,
Corentin


--

Corentin Dupont
Researcher @ Create-Netwww.corentindupont.info

---------- Forwarded message ----------
From: dc4cities-project-request(a)create-net-ml.org
To:
Cc:
Date: Tue, 09 Feb 2016 16:28:08 +0100
Subject: confirm 44bfd373419fd479aecf4b351db7ff6b9772b32e
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message. Do this if the message is
spam. If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. The Approved: header can also appear in the first line
of the body of the reply.

--

Corentin Dupont
Researcher @ Create-Netwww.corentindupont.info

--

Corentin Dupont
Researcher @ Create-Netwww.corentindupont.info

--
http://www.twitter.com/sivabalans

Hi, all,

Based on recent low attendance and engagement, it's time we perhaps tweak
the call.

After briefly discussing with Colin, Chip, Sam, Chris, Stormy, and a few
others, here is a short anonymous survey (5 minutes max) that I'd encourage
you to take to help shape the future of the CAB call.

https://goo.gl/83F726

I'll leave this open for one week. I'll send a reminder end of this week
with an idea of how many responses we have and again next week before
closing it on Wednesday 17th @ midnight.

I'll share the results soon after and hopefully we can use the feedback to
improve where we go from here.

All the best,

dr.max
ibm cloud labs
sillicon valley, ca

Sent from my iPhone

You can obtain the "Authorization: bearer" token using the cf cli.

cf login
cf oauth-token

Still struggling...

I have already an account with CF, so I tried:

$ uaac token client get
Client ID: admin
Client secret: ************

Successfully fetched token via client credentials grant.
Target: http://uaa.172.16.0.191.xip.io
Context: admin, from client admin

Then:
$ uaac token decode

Note: no key given to validate token signature

jti: 908139b9-28be-4490-9ffd-a0e6b2f1XXXX
sub: admin
authorities: password.write scim.write clients.write clients.read
scim.read
uaa.admin clients.secret
scope: scim.read uaa.admin password.write scim.write clients.write
clients.read clients.secret
client_id: admin
cid: admin
azp: admin
grant_type: client_credentials
rev_sig: 78635a00
iat: 1455113000
exp: 1455156200
iss: https://uaa.172.16.0.191.xip.io/oauth/token
zid: uaa
aud: admin scim uaa password clients


There is nothing looking like the "Authorization: bearer" code from the
cURL command below...
Should I use the "jti" field?

Thanks a lot Hristo!!
Corentin

--

Corentin Dupont
Researcher @ Create-Netwww.corentindupont.info

Hi Darren,

We had put it on hold when we thought someone was going to open source a solution that matched our proposal in functionality.
Apologies to everyone who responded at the time and have been waiting for an update!

We still see a need for this in CF and have recently decided to restart it.
I'm still working on assigning resources but fingers crossed we'll be progressing soon.

Cheers,
Dies Koper
diesk(a)fast.au.fujitsu.com

Hi, Nanduni,

The diego-release README does recommend deploying the runtime-passed branch
of cf-release alongside the master branch of diego-release. Although the
two are typically compatible, development instability can sometimes cause
that not to be the case. That's unfortunately true right now because of
recent changes to certain cf-release property names that need to flow into
the Diego deployment manifest.

If you're only looking for releases of CF and Diego to deploy to BOSH-Lite
in order to try pushing some apps, you may be more interested in deploying
the latest stable CF release and an associated compatible Diego release. At
the moment, that's CF v230, and you can find the Diego release version and
other related releases listed at the end of the CF v230 release notes:
https://github.com/cloudfoundry/cf-release/releases/tag/v230

To use these versions, check out cf-release and diego-release to the
appropriate version tags, and make sure the submodules are up-to-date. This
corresponds to slightly revised instructions for steps 3 and 4 in the
diego-release README:

cd ~/workspace/cf-release
git checkout v230
./scripts/update

cd ~/workspace/diego-release
git checkout v0.1450.0
./scripts/update

With the release repositories at those versions, you should then be able to
proceed with the README instructions to generate the deployment manifests,
create and upload the releases, and deploy CF and Diego.

Hope that helps! If you need further assistance, please let us know here,
or join us on the Cloud Foundry Slack channels at
https://slack.cloudfoundry.org/.

Best,
Eric, CF Runtime Diego PM

On Wed, Feb 10, 2016 at 1:36 AM, Nanduni Nimalsiri <nandunibw(a)gmail.com>
wrote:

Hi all,

Sorry for troubling again. I generated the CF manifests successfully. But
I am getting errors while generating the Diego manifests. I gives me the
following error.

nanduni(a)nanduni-TECRA-M11:~/workspace/diego-release$
./scripts/generate-bosh-lite-manifests
~/workspace/diego-release ~/workspace/diego-release
2016/02/10 14:54:28 error generating manifest: unresolved nodes:
(( merge )) in
././scripts/../manifest-generation/config-from-cf-internal.yml
properties.metron_agent.tls_client.cert
(properties.metron_agent.tls_client.cert)
(( merge )) in
././scripts/../manifest-generation/config-from-cf-internal.yml
properties.metron_agent.tls_client.key
(properties.metron_agent.tls_client.key)
(( merge )) in
././scripts/../manifest-generation/config-from-cf-internal.yml
properties.loggregator.tls.ca (properties.loggregator.tls.ca)
(( properties.metron_agent.tls_client.cert )) in dynaml
config_from_cf.metron_agent.tls_client.cert ()
(( properties.metron_agent.tls_client.key )) in dynaml
config_from_cf.metron_agent.tls_client.key ()
(( properties.loggregator.tls.ca )) in dynaml
config_from_cf.loggregator.tls.ca ()

How can I get over this? Any help is highly appreciated.

Best regards,
Nanduni.

Hi all,

Sorry for troubling again. I generated the CF manifests successfully. But I am getting errors while generating the Diego manifests. I gives me the following error.

nanduni(a)nanduni-TECRA-M11:~/workspace/diego-release$ ./scripts/generate-bosh-lite-manifests
~/workspace/diego-release ~/workspace/diego-release
2016/02/10 14:54:28 error generating manifest: unresolved nodes:
(( merge )) in ././scripts/../manifest-generation/config-from-cf-internal.yml properties.metron_agent.tls_client.cert (properties.metron_agent.tls_client.cert)
(( merge )) in ././scripts/../manifest-generation/config-from-cf-internal.yml properties.metron_agent.tls_client.key (properties.metron_agent.tls_client.key)
(( merge )) in ././scripts/../manifest-generation/config-from-cf-internal.yml properties.loggregator.tls.ca (properties.loggregator.tls.ca)
(( properties.metron_agent.tls_client.cert )) in dynaml config_from_cf.metron_agent.tls_client.cert ()
(( properties.metron_agent.tls_client.key )) in dynaml config_from_cf.metron_agent.tls_client.key ()
(( properties.loggregator.tls.ca )) in dynaml config_from_cf.loggregator.tls.ca ()

How can I get over this? Any help is highly appreciated.

Best regards,
Nanduni.

Hi Daniel,

I got this issue solved. The cause had been setting the path incorrectly.
Thank you very much. Looking forward for more help in upcoming issues.

Best Regards,
Nanduni

Since the code in those executables is meant to be ruby, you'll need the
appropriate shebang line, like this:

https://github.com/cloudfoundry/ruby-buildpack/blob/45b22922827c02e6b7af0650cf1b02600455d3cd/bin/compile#L1

Does yours look different?

It doesn't matter that it's a java buildpack, even the standard java
buildpack uses ruby for those scripts:

https://github.com/cloudfoundry/java-buildpack/blob/master/bin/compile#L1

The compilation takes place in CF (inside a container running in one of the
CF nodes). It is looking for ruby in the compilation container. The root
filesystem for the compilation containers probably defaults to cflinuxfs2
in your CF installation:

https://github.com/cloudfoundry/stacks/tree/master/cflinuxfs2

This root FS has ruby in it (that's how the standard buildpacks work), you
can even see that ruby is installed in the Dockerfile script used to build
this root FS image.

On Tue, Feb 9, 2016 at 11:11 PM, nitin padalia <padalia.nitin(a)gmail.com>
wrote:

Its a java buildpack, but detect, compile and release are written in ruby.

One question I've is: does this compilation takes place in CF or its done
on the client machine where CF CLI is residing?

Where its looking for ruby?
Is there any file in buildpack which update PATH variable for ruby search?

-Nitin

Its a java buildpack, but detect, compile and release are written in ruby.

One question I've is: does this compilation takes place in CF or its done on the client machine where CF CLI is residing?

Where its looking for ruby?
Is there any file in buildpack which update PATH variable for ruby search?

-Nitin

Thank you Kayode.

I followed your instructions. That helped me. Now it is working fine. Thanks again. Looking forward for more help in upcoming issues.

Best Regards,
Nanduni.

Thank you Tomoe.

You are exactly correct. I almost forgot that I have set path to a binary file. It is now working fine. Thank you very much. Looking forward for more help in upcoming issues.

Best Regards,
Nanduni.

In addition, make sure you have GO installed. Also make sure GOPATH and
GOROOT env are set correctly.

For example:
export GOPATH=$HOME/projects/goprojects
export GOROOT=/usr/local/opt/go/libexec

On Wed, Feb 10, 2016 at 8:06 AM, Tomoe Sugihara <tsugihara(a)pivotal.io>
wrote:

On Wed, Feb 10, 2016 at 2:55 PM, Nanduni Nimalsiri <nandunibw(a)gmail.com>
wrote:

Thank you for the reply.

Yes I did as you have told. But it gives me errors. I'll tell what I did
so that you might be able to figure out my mistake.

1. I downloaded this binary:

https://github.com/cloudfoundry-incubator/spiff/releases/download/v1.0.7/spiff_linux_amd64.zip
Now it is in my Downloads folder.
2. I extracted it there.
3. Then I used the command: sudo gedit ~/.profile and set the path as
below.
export SPIFF_HOME=/home/nanduni/Downloads/spiff
export PATH=$PATH:$SPIFF_HOME
Then I saved and refreshed that content using : source ~/.profile

Isn't /home/nanduni/Downloads/spiff a binary file?
If so, you should have /home/nanduni/Downloads/ in your PATH as opposed
to /home/nanduni/Downloads*/spiff*

Best,
Tomoe

On Wed, Feb 10, 2016 at 2:55 PM, Nanduni Nimalsiri <nandunibw(a)gmail.com>
wrote:

Thank you for the reply.

Yes I did as you have told. But it gives me errors. I'll tell what I did
so that you might be able to figure out my mistake.

1. I downloaded this binary:

https://github.com/cloudfoundry-incubator/spiff/releases/download/v1.0.7/spiff_linux_amd64.zip
Now it is in my Downloads folder.
2. I extracted it there.
3. Then I used the command: sudo gedit ~/.profile and set the path as
below.
export SPIFF_HOME=/home/nanduni/Downloads/spiff
export PATH=$PATH:$SPIFF_HOME
Then I saved and refreshed that content using : source ~/.profile

Isn't /home/nanduni/Downloads/spiff a binary file?
If so, you should have /home/nanduni/Downloads/ in your PATH as opposed to
/home/nanduni/Downloads*/spiff*

Best,
Tomoe

Mohit,

Have you tried Ops metrics,
https://docs.pivotal.io/pivotalcf/customizing/use-metrics.html . You can
easily view memory usage using JMX client jconsole

HTH

--
Odeyemi 'Kayode O.
http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde

Thank you for the reply.

Yes I did as you have told. But it gives me errors. I'll tell what I did so that you might be able to figure out my mistake.

1. I downloaded this binary:
https://github.com/cloudfoundry-incubator/spiff/releases/download/v1.0.7/spiff_linux_amd64.zip
Now it is in my Downloads folder.
2. I extracted it there.
3. Then I used the command: sudo gedit ~/.profile and set the path as below.
export SPIFF_HOME=/home/nanduni/Downloads/spiff
export PATH=$PATH:$SPIFF_HOME
Then I saved and refreshed that content using : source ~/.profile

Then I ran the following to generate the CF manifest.
$ cd ~/workspace/cf-release
$ ./scripts/generate-bosh-lite-dev-manifest

But it gives me the following error.
nanduni(a)nanduni-TECRA-M11:~/workspace/cf-release$ ./scripts/generate-bosh-lite-dev-manifest
Aborted. Please install spiff by following https://github.com/cloudfoundry-incubator/spiff#installation
Incorrect YAML structure in `/home/nanduni/workspace/cf-release/bosh-lite/deployments/cf.yml': expected Hash at the root

Can you tell me where I have gone wrong?

Best Regards,
Nanduni.

Hi Nanduni,

Hi all,

I want to deploy Docker images to Cloud Foundry. I am still a newbie and I do not know much about it. My intention is to experience this locally in my machine via Bosh-Lite. So I suppose I need to follow the README[1] in BOSH Release for Diego (cloudfoundry-incubator/diego-release).
[1] https://github.com/cloudfoundry-incubator/diego-release#deploying-diego-to-bosh-lite

In brief, I want to deploy Diego to Bosh-Lite, but I am stuck with this for days. The README does not provide more details on this process. I am unable to install spiff which I suppose is a tool for generating the BOSH manifests. I followed spiff README[2]. But I failed to install spiff. Then I tried to install it by executable binaries as well as through its git hub repo by 'go get'. I followed this tutorial[3] too. But I could not succeed in any of the ways.
[2] https://github.com/cloudfoundry-incubator/spiff
[3] http://www.evoila.de/2015/03/13/installing-cloudfoundry-spiff-on-ubuntu/?lang=en

Can any one help me to install spiff or provide me any resource for this. If some one can teach me the process of deploying Diego to Bosh-Lite, it would be a great relief for me. If you find any good blog post on this subject, share it with me. Please help.

Best Regards,
Nanduni.

Thanks Daniel. I was struggling with this for days and your explanation on PWS solved all my doubts.
I have already used bosh-lite set up and deployed applications locally in my machine using that.
In case of integrating Docker support with Bosh-lite, I followed the following BOSH release for Docker(cloudfoundry-incubator/diego-release)[1].
[1]https://github.com/cloudfoundry-incubator/diego-release#deploying-diego-to-bosh-lite

But I came up with several errors. That wants me to install spiff, which I suppose is a tool for generating BOSH manifests. I followed spiff README[2]. But I failed to install spiff. I tried to install it by executable binaries as well as through its git hub repo by 'go get'. I followed this tutorial[3] too. But I could not succeed in any of the ways.
[2] https://github.com/cloudfoundry-incubator/spiff
[3] http://www.evoila.de/2015/03/13/installing-cloudfoundry-spiff-on-ubuntu/?lang=en
Can you please help me to install spiff or can you provide me any resource for this.

Best Regards,
Nanduni.

​Hi Team,

I am deploying application on cloud foundry with 1 Gb memory. It fails
after sometime when i push load on it. Could you help me the tool with
which I can analyse my memory usage on cloud foundry.
At my end I deployed my app on localmachine (deployed on system in tomcat)
and analysed with new relic, and everything was fine.I tried to integrate
Newrelic with my app but failed to do thus unable to analyse the app.

Please help me in integrating the new relic with my app or suggest me tool
for cloud foundry.

Thanks in advance,
Mohit Garg