Hi Jason,

For example, when connecting to the database we set the client application
name on the connection.
If the db becomes heavily loaded, the db admin can check the expensive
statements view and see which applications generate them.
Also for end to end tracing when a transaction goes through multiple
components, we have to record each involved component name.
So we need an application name that is human readable and unique.

Best regards,
Petar


On Tue, Oct 18, 2016 at 12:39 AM, Jason Sherron <jsherron(a)pivotal.io>
wrote:

Hi Peter,

Can you detail your supportability needs for external services? I'm
wondering if this is something that could be filtered at the network level
and if that might help. We're building ways to identify and filter network
traffic sources by application. It wouldn't include arbitrary text like
org/space, but would be mapped to an application via an identifier and
perhaps IP address.

Jason - Container Networking


On Mon, Oct 17, 2016 at 1:26 PM Peter Dotchev <dotchev(a)gmail.com> wrote:

Hi,

We have the same issue.
For supportability reasons we need the app to identify itself when
connecting to external services.
application_id is not suitable in this case as the operator/admin cannot
easily decipher it.
It would be best to identify the app using org_name + space_name +
app_name.
All of these are present in VCAP_APPLICATION except org_name.
Is it omitted intentionally? If not, can it be added?

Best regards,
Peter


On Thu, Oct 13, 2016 at 6:19 PM, Vinod Singh <vinoddandy(a)gmail.com>
wrote:

Friends,

I am working to retrieve org/space/application-name in CF via System
provided environmental variables.
Unfortunately I could not "org" in list. Is it not a good idea to
include "org" also in System Provided list ?

cf env <appname>

System-Provided:


{
"VCAP_APPLICATION": {
"application_id": "74b3e1a6-ba9f-4dcb-9ae3-e68e1dbfa417",
"application_name": "mylogapp",
"application_uris": [
"xxxx.xxxx.xxx"
],
"application_version": "e43c2d12-cd8e-46d3-9298-ce0905651c0e",
"limits": {
"disk": 1024,
"fds": 16384,
"mem": 128
},
"name": "mylogapp",
"space_id": "4d942c57-e41e-43e2-ba3a-0665ceaa976b",
"space_name": "demo2",
"uris": [
"xxxxx.xxxxx.xxxxx"
],
"users": null,
"version": "e43c2d12-cd8e-46d3-9298-ce0905651c0e"
}
}


Regards,
Vinod

Hi Anuj,

For scheduling, you might want to look into the Advanced Python Scheduler
[1]. You would push the scheduler as a separate app to Cloud Foundry.

You could also experiment with V3 Tasks that we are close to releasing.
You can think of Tasks as commands to run against your app code that only
take up resources while executing. As of CF-245, you can push an
application and then run a task against it. There’s currently only support
via curl [2], but we are working on supporting this via CLI.


[1] http://apscheduler.readthedocs.io/en/3.0/
[2] http://v3-apidocs.cloudfoundry.org/version/release-candidate/#push-v2-
app-and-run-a-v3-task


Thanks,

Nick

--
Nicholas Calugar

On October 18, 2016 at 8:03:38 AM, Anuj Jain (anuj17280(a)gmail.com) wrote:

Hi,


We have an application (lets say django app) - which we deployed on
Cloud Foundry - now there are few commands which we want to run
periodically (cron jobs) - what is the best way to handle this with Cloud
Foundry.



Thanks

- Anuj

Hi Abhishek,
Yes, you should be able to use UAA outside of CF and integrate it with any
IdP of your choice. At GE we have UAA deployed on CF and our performance
numbers are CF based. The numbers should not be very different on a non-CF
env. Attached pdf should give you some performance numbers from our tests

-Siva

On Tue, Oct 18, 2016 at 3:04 PM, Sree Tummidi <stummidi(a)pivotal.io> wrote:

+ Siva & Ilya from GE

Can you please help.

Thanks,
Sree Tummidi
Staff Product Manager
Identity - Pivotal Cloud Foundry


On Tue, Oct 18, 2016 at 11:43 AM, abhishek jain <intelccdodemo(a)gmail.com>
wrote:

Hi

Can we use UAA outside cloud foundry as standalone service with LDAP or
any other social networking provider ? Where can i find performance bench
marking related statistics on UAA service ?

Thank you

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

+ Siva & Ilya from GE

Can you please help.

Thanks,
Sree Tummidi
Staff Product Manager
Identity - Pivotal Cloud Foundry


On Tue, Oct 18, 2016 at 11:43 AM, abhishek jain <intelccdodemo(a)gmail.com>
wrote:

Hi

Can we use UAA outside cloud foundry as standalone service with LDAP or
any other social networking provider ? Where can i find performance bench
marking related statistics on UAA service ?

Thank you

Hi Peter,

Can you detail your supportability needs for external services? I'm
wondering if this is something that could be filtered at the network level
and if that might help. We're building ways to identify and filter network
traffic sources by application. It wouldn't include arbitrary text like
org/space, but would be mapped to an application via an identifier and
perhaps IP address.

Jason - Container Networking


On Mon, Oct 17, 2016 at 1:26 PM Peter Dotchev <dotchev(a)gmail.com> wrote:

Hi,

We have the same issue.
For supportability reasons we need the app to identify itself when
connecting to external services.
application_id is not suitable in this case as the operator/admin cannot
easily decipher it.
It would be best to identify the app using org_name + space_name +
app_name.
All of these are present in VCAP_APPLICATION except org_name.
Is it omitted intentionally? If not, can it be added?

Best regards,
Peter


On Thu, Oct 13, 2016 at 6:19 PM, Vinod Singh <vinoddandy(a)gmail.com>
wrote:

Friends,

I am working to retrieve org/space/application-name in CF via System
provided environmental variables.
Unfortunately I could not "org" in list. Is it not a good idea to include
"org" also in System Provided list ?

cf env <appname>

System-Provided:


{
"VCAP_APPLICATION": {
"application_id": "74b3e1a6-ba9f-4dcb-9ae3-e68e1dbfa417",
"application_name": "mylogapp",
"application_uris": [
"xxxx.xxxx.xxx"
],
"application_version": "e43c2d12-cd8e-46d3-9298-ce0905651c0e",
"limits": {
"disk": 1024,
"fds": 16384,
"mem": 128
},
"name": "mylogapp",
"space_id": "4d942c57-e41e-43e2-ba3a-0665ceaa976b",
"space_name": "demo2",
"uris": [
"xxxxx.xxxxx.xxxxx"
],
"users": null,
"version": "e43c2d12-cd8e-46d3-9298-ce0905651c0e"
}
}


Regards,
Vinod

Hey folks,

In the last few months there's been a noticeable growth in activity on
Stack Overflow related to Cloud Foundry questions. Folks who are active on
the cf-dev and cf-bosh mailing lists may be interested in helping out on
Stack Overflow as well, so I thought I'd share a tool I use to track to get
email notifications for SO activity.

1. Go to https://stackexchange.com/filters and log in the way you
normally would for any stackexchange site such as StackOverflow (or sign up
if you don't already have an account).
2. Click on *New filter.*
3. In section 1, select *Just questions tagged with the* cloudfoundry *tag
on...* All Sites, and click *Add rule*.
4. Repeat the above step with other tags such as cloudfoundry-uaa and
bosh. You could also add your favourite vendor distributions here
such as pivotal-cloud-foundry, ibm-bluemix, swisscomdev, etc.
5. In section 2, name your filter, e.g. Cloud Foundry.
6. In section 3, check the box to say *Yes, send to *<your-email> and
choose your frequency every 15 minutes / every 3 hours / every day.
7. Click *Save Changes*.

Happy StackOverflowing!

Best,
Amit

On Oct 18, 2016, at 1:27 AM, Julz Friedman <julz.friedman(a)gmail.com> wrote:

Hi cf-dev,

This is a very exciting email to write! I'm extremely proud to announce that garden-runC, the new cloud foundry container runtime for Linux, based on the OCI specification and its reference implementation “runC”, is now 1.0!

ACTION REQUIRED: Given that garden-runc is now ready to use and fully compatible with garden-linux, we intend to end-of-life garden-linux immediately. More details on this and an explanation for the accelerated timescale are at the bottom of this email.

About garden-runc: At this point garden-runC has been successfully running 100% of the production traffic on PWS for around a month (it has been running a smaller portion of the load for a longer time as we gained confidence). The Diego team has been testing with and listing compatible releases of both g-l and g-r for several months. It has also been the only supported linux backend for concourse for several months, thereby being used in a broad range of environments and deployment scenarios. In all cases it has held up remarkably well. Given this I'm happy to recommend people move over to garden-runC as soon as possible (diego’s manifest generation scripts should make this extremely simple -- just pass the `-g` flag to diego manifest generation -- but please note you MUST recreate any cells that previously ran garden-linux as part of the transition or you WILL have problems. An easy way to do this is to combine the transition to garden-runc with a stemcell deploy).

As well as being based on open standards and using a low-level container runtime developed with a large community and many eyeballs, garden-runC has some other significant benefits:

AppArmor is configured and enforced by default and out of the box for all unprivileged containers.
Seccomp whitelisting is used to restrict the set of system calls a container can access, hugely reducing the surface area for break-out exploits. Again this is set up out of the box, you don't need to do anything.
We've been able to simplify and modularise the garden code base extensively as part of this transition, allowing pluggable networking and rootfs management. This enables (and will be required by) the fast-developing container-to-container networking work and the new “grootfs” OCI-compliant rootfs downloader
Garden-runC uses the exact same low-level container execution code as docker/k8s for running containers, so when you run container images you know they run identically in CF as elsewhere

I'm immensely proud of the cross-foundation team that has delivered this, including engineers from Pivotal, IBM and SAP.

GARDEN-LINUX END OF LIFE: 28/10/2016 - ACTION REQUIRED: Now that garden-runC is ready we’re extremely keen to avoid maintaining two code-bases for any longer than necessary, so we would like to move everyone to garden-runC immediately, with the next Diego-release update (as mentioned above, apart from the need to recreate the cells this is a 1-1 transition). Doing this on an accelerated timescale is particularly important because we have encountered a regression in the 4.4 kernel that causes problems during container destruction for garden-linux. We are working to track this down, but it is proving extremely difficult to rectify or work around. If anyone intends to use stemcells with 4.4 kernels, until we identify a fix, they should immediately move to garden-runC to avoid issues.

If anyone has huge problems moving off garden-linux now please reach out to me asap and we’ll see what we can do, otherwise I will suggest diego stop supporting generating manifests for garden-linux with the next release, and will propose moving garden-linux to the attic shortly after that. Either way, we will no longer be developing new features for garden-linux or accepting pull requests from this point. Unless anyone has a strong reason otherwise (if so please do say!), we will end support for garden-linux 28/10/2016.

Thanks all very much, and again a huge thanks to the garden team!

Julz Friedman
Garden Core PM