Thanks for sharing James.  Renat, cool. We look forward to your feedback. Best, Max — Sent from Mailbox

Oh yeah baby. +1 Andrei, Kirill, please join in. Perhaps we can help with some contributions. From the first look it probably makes sense to get Ksenia to review this. Renat

for reference, this is how kubernetes is categorizing various volumes types and capabilities [1] as discussed on this tweet

Hello, I have over 5 years of transcription experienceand have been supporting several clients with their transcriptionrequirements. I assure you of quality work and most importantlyconfidentiality

The original problem didn’t look like a missing dependency issue. What’s the exact error and stack trace you are getting after fixing the import to use the spring-rabbitmq ConnectionFactory? Or

The Java Main Container configuration documentation[1] describes the appropriate way to set command line arguments. Configuration can be done either with a fork of the buildpack or an environment

I spoke too soon, I think that is the opposite of what you are looking for, sorry!

Hey! I think the thing you are looking for is the JAVA_OPTS env variable: https://github.com/cloudfoundry/java-buildpack/blob/master/docs/framework-java_opts.md lmukkama(a)cisco.com> wrote:

Hi CF dev team, I want to pass command line arguments to the spring java app. I have tried the option of setting them using the env 'JBP_CONFIG_JAVA_MAIN' as suggested in

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]