Hi, we have several service brokers (for "normal" backend services and quite a few route services) and we don't use PlanID (or ServiceID) in most of them. There are exceptions (as always), but those

Our implementation of Service Broker [1] ignores Plan Id and Service Id input during the bind requests and the bindings are valid even post plan update. Jagadish [1] – Service Fabrik

Please see below for information on a high-severity UAA CVE. Sree Tummidi can provide more details if you have questions. Thanks, Molly Crowther CFF Security Team CVE-2018-1192: UAA SessionID present

We do use the plan_id in the binding request. Usually to help look up credential config for parts of a service's credentials that are more static. But, we also don't have any services where updating

For folks who build Service Brokers, I would like to get your input on this issue [1] in the OSBAPI spec project. Today the spec doesn't give any guidance on what should happen to bindings when a

Should I deploy "cf deploy" again with the haproxy file and build all virtual machines? --------------------------------------------

​Hello Russell Assuming your ​domain for management is pcontroller You need to configure the dns to resolve all *.pcontroler to a routing layer, either by lb or directly gorouter. Try enable

Hi cf devvers, the garden team have a proposal about using Containerd to run containers in garden-runc. It's called "Proposal: Use Containerd to run containers in Garden-RunC". The link is here

SSH into the virtual machine via bosh ssh -d cf api and do a sudo su, then monitor summary. If something there is failing, please provide the logs from

Hi, I created cloud foundry with the following virtual machines. What is the problem with api the virtual machine? bosh -e bosh-1 vms Instance

Hi, 1- Using the cf-deployment, the virtual machines of cloud foundry on openstack IaaS were created. 2- cf CLI also installed There is the following problem to log into the cloud foundry

Error creating four virtual machines has been fixed. (router, tcp-router, scheduler and smoke-test) --------------------------------------------

Russell, can you provide cloud-config.yml after removing lbaas config parts ? Regards,

The attached guide shows you how to enable and verify the LBaaS service in OpenStack Pike - https://docs.openstack.org/neutron/pike/admin/config-lbaas.html It is indeed possible to install OpenStack

In the file of cloud-config.yml , I commented on LBaaS part. Error creating four virtual machines (router,tcp-router, schedular, smoke-test) solved. Very

Version of openstack is Pike. I have not used LBaaS. Do you need to install it?? --------------------------------------------

From the json in the message body it appears to be an issue with OpenStack's LBaaS service. This service has had many changes in the lifetime of OpenStack from V1 to V2 to the Octavia project. See

Hi Matthias - We have this vision as well and we recently just got together to discuss related topics as a new initiative and there has been some chatter about it in the Loggregator github repo.

Seems vm extension related issue. If not configured in your environmental then remove it . On 27-Jan-2018 5:15 PM, "Russell Blue via Lists.Cloudfoundry.Org" <bluerussell20=yahoo.com@...> wrote:

Yes, The following command is "bosh director vm" and it does not cause an error with the network. bosh/0:~$ sudo curl http://pcontroller:9696 {"versions": [{"status": "CURRENT", "id": "v2.0",