I was hoping it would be that simple, but it wasn't. I must have been in a hurry when I accepted the import suggestions. I updated to use the correct imports, but I still have the same issue (with a

What cloud are you referring to? Better ask the question in the cloud provider's forum. Jack

I am running a demo today which I've done many times before. I try to add the pipeline service to my liberty java application and it won't work. Error "Create service does not support Pipeline" Any

This is excellent. I think your blog post outlines exactly what I was looking for. Thank you for the help. Mark

It looks like the main problem is the type of connection bean you are expecting Spring Cloud Connectors to create. In the PivotalConfig class, you have this: import

---------- Forwarded message ---------- From: Flávio Henrique Schuindt da Silva <flavio.schuindt(a)gmail.com> Date: Wed, Dec 2, 2015 at 12:01 PM Subject: [cf-bosh] Getting error Staging error: no

Hi, guys. Suddently (after monthns of working fine), my CF instalation on aws started to fail. I'm getting this erros when trying to push an app: Staging error: no available stagers. Googling, I

https://github.com/cloudfoundry-community/cf-boshworkspace/tree/master/templates/tiny has some templates that collocate everything into 5-6 VMs; and can be 10-12 VMs in a HA mode. Ruben & others

Hey all, I know some people have worked on deploying CF on the minimum number of VMs possible. In theory, all of CF can run on one machine (indeed it does in BOSH-Lite deployments, but that's

The cf-boshworkspace project from Stark and Wayne: https://github.com/cloudfoundry-community/cf-boshworkspace provides an cf-aws-tiny.yml template, which I believe gets it down to 4 instances. In

Yes, it's still evolving. A couple of additional stories for example include adding events for droplets [1] and processes [2] [1] https://www.pivotaltracker.com/story/show/101936042 [2]

I'm trying to connect to RabbitMQ from our Pivotal CloudFoundry environment and I can't get it to work. The only artifact I don't have in my pom is org.cloudfoundry:auto-reconfiguration:1.7.0.RELEASE

Hi Dieu, thank you for the clarification. Is the list of events [1] for v3 api still evolving ? [1] - http://apidocs.cloudfoundry.org/225/events/list_all_events.html Piotr -----Dieu Cao <dcao@...>

Hi Mark, We have successfully deployed spring-boot-cf-service-broker-mongo on Cloud Foundry (DEA, not Diego) about 2 months before and wrote a blog post

Hi, I am looking at miminal-aws.yml in the release https://github.com/cloudfoundry/cf-release and realized that this deployment will consume 13 instances on AWS. Is it possible to reduce the number

this may be because https://www.pivotaltracker.com/story/show/106892318 and will be fixed in the next release for now, you should at least set the login.url and uaa.url properties with the hostname

Hey Tony, Sorry for the delayed response, we have been on Thanksgiving holiday here in the US. Based on https://github.com/sequenceiq/docker-uaa/issues/5#issuecomment-160185248 I take it you've

I'm attempting to connect Lattice 0.6.0 to a private Docker registry. In a previous version of Lattice (that used garden-linux 0.295.0), accomplishing that required passing the

Hello Guillaume, Thank you for your input. It seems I had not subscribed to all notifications in the doc; my mistake. The route service url must be https; this is enforced by the routing API and CC

Forgot to mention that cf-routing-release (tcp router) relies heavily on consul for service discovery and that's affected too.