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:

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

I guess , It can run with 3 nodes but it seems it not doing well with the 3 nodes on the same zone. 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

This looks like a useful service. Thanks for the contribution! Chris Sterling chris.sterling(a)gmail.com twitter: @csterwa linkedin:

+1 this looks incredibly useful. Best Duncan Johnston-Watt CEO | Cloudsoft Corporation Twitter | @duncanjw Mobile | +44 777 190 2653 Skype | duncan_johnstonwatt Linkedin |

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

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

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

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