alexey.zakharov(a)altoros.com> wrote: Have you looked at the `uaac` tool? I'm not quite sure I understand what you're trying to do, but you can map an LDAP group DN to a UAA group with `uaac`. Then

wrote: Set an environment variable called `MEMORY_LIMIT`. When the build pack runs it'll look at that env variable to see the max memory assigned to the container. Dan

Hi Team, I am trying to customize the java build-pack with oracle jre. however, when trying to debug it locally , using the below commands  : export VCAP_APPLICATION="{}" export

One(?) thing I want to know about this issue is what (or which) way the major public service providers (Pivotal, IBM, HP, Anynines, etc.) do. If you can tell, please let me know. -- View this

A useless question: Why is the team called MEGA? There is no 'M' 'E' 'G' 'A' in the initial characters of 'The OSS Release Integration team.' -- View this message in context:

Hi guys! Sorry if my question is newbie or it was discussed before. I want to use LDAP for users authentication/authorisation. And I’ve successfully bound CF to LDAP, and managed to configure uaac

Thought so. :-) Great news. Thanks for the detailed overview Amit! Cornelia Sent from my iPhone

this shows how to use drupal which is a cms with wiki functions http://blog.pivotal.io/pivotal-cloud-foundry/products/how-to-deploy-drupal-to-pivotal-cf-within-seconds if you're in a private

Hi James, Thank you for reply. I think I didn't describe it clearly. Sorry about that. The CentOS 6.5 is the OS underlying our OpenStack. And we are using Ubuntu Trusty

cf project does not support or test cf-release with centos6.5, only ubuntu 14.04. etcd nodes should not necessarily be aware of which AZs they are in. the only difference might be in the bosh

Ah, copy-paste fail! Zak is a Pivotal engineer, not IBM.

Hi all, As some of you may already be aware, the Runtime team has recently been refactored: - The "CAPI" team will be responsible for the Cloud Controller and Services API - The Routing team will be

Hi Amit, Let me explain the error I got in details. My env info: CentOS 6.5, Openstack Icehouse, Single-AZ 2 hm9000 instances, 3 etcd instances, Manifest: - name: etcd_z1 instances: 3

Hi Amit, Thank you very much for your clear explanation. I got the release info(I called it "release Note") from CF release

Hi Gwenn, Can you elaborate? Are you saying you've actually deployed 3 etcd nodes to 1 zone and you're currently experiencing problems? If so, can you give some details on the

Hi Tony, All options are possible. You can run: - one instance in a one-zone deployment - one instance in one zone of a multi-zone deployment - three instances in a one-zone deployment, will all

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 michele.santuari(a)create-net.org>

wrote: 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

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

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: