Hi James, It does work. I am not sure why it didn't last time. I will need to figure out what's difference between this sample app and my testing SB app. One more thing. In my previous apps, I have

Sounds like it could work, have you tried it? Naming the same stack differently on different IaaS is not the ideal way to accomplish placement on different IaaS, but until placement pools

armin, thanks for indicating an interest! hopefully you have a CLA on-file. you can see some of the contribution first steps here, including the CLA to fill out if you still need to do that step

Thanks for this simplification! Cyrille wrote: -- Cyrille Le Clerc email & gtalk : cleclerc(a)cloudbees.com / mob: +33-6.61.33.69.86 / skype: cyrille.leclerc CloudBees, Inc www.cloudbees.com

Hello! :) i was looking around tracker to find issues (probably low hanging ones to start with) to fix, while i might have found some that i could help with, i wanted to signal you guys as well so i

the sample app i referenced with the "initial" director works for me: $ curl http://jamesboot.cfapps.io Greetings from Spring Boot! here's the corresponding logs to the sample app once it's

Thanks James! You are right that it is pretty straight forward to build and deploy this sample project. However, I got the exact same behavior. The System.out worked when I ran the jar as a standalone

Thanks Naga. The sample project had this plugin in the pom file already.

Hi, This thread was originally posted at https://groups.google.com/a/cloudfoundry.org/forum/#!topic/admin-ui/6HICMfIlwIc but as the admin_ui is scanning information from Cloud Foundry's components, I

the cf oss wiki [1] has a design docs section [2] that lists an approach called "placement pools" [3]. the placement pools concept never moved beyond the proposal phase and now that diego is the

Can Cloudfoundry place specific app on specific IaaS pool. Install many CF is not a elegant option. Can we support it as below? 1: install full cf-release 2: install DEA on specific IaaS, change the

On nabble, your question appears updated: http://cf-dev.70369.x6.nabble.com/Multi-DEA-pool-in-cloudfoundry-td1674.html But in the emails that people have already received, and on the official cf-dev

Thanks Amit. The question is the same. I will update the question from PCF to CF -- View this message in context:

Hi, This is a mailing list for the open source Cloud Foundry project. Please use Pivotal's internal communication channels if your question is specifically related to PCF. Thanks, Amit

Many of customers asked for a feature that is they can place specific app on specific IaaS pool. Install many PCF is not a elegant option. Can we support it as below? 1: install full PCF 2: install

zongwei, i'm unclear why a single org with multiple spaces, each potentially with their own quota, which is what the cf system does today, does not satisfy the customer's request when using a single

Everything should still work as is. wrote:

I am glad for future simpler networking for bosh-lite manifests; I just know we have lots of infrastructure-warden.yml spiff templates in lots of bosh releases. Also, will bosh-lite stemcells keep

I know versioning is somewhat a lost cause for bosh-lite.  I guess my actual question is: will old manifests still work for new bosh-lite? I assume so as you said "you will not notice any

Perhaps worthy of a major version bump? wrote: