Multi DEA pool in cloudfoundry


Amit Kumar Gupta
 

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 happen,
it's the only way I can think of. You'll also have to figure out the
networking so that the new DEAs can talk to the NATS servers securely
(ideally don't want to make the NATS publicly routable), and that the
routers can talk to the new DEAs securely.

Amit

On Fri, Sep 11, 2015 at 11:49 PM, ezhang <ezhang(a)pivotal.io> wrote:

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 nats config to installed CF
nats
3: setup different Stack for each DEA

then App can push though one cloud controller, and run on different IaaS
pool through stack. Each DEA managed by their own BOSH



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Multi-DEA-pool-in-cloudfoundry-tp1678.html
Sent from the CF Dev mailing list archive at Nabble.com.


James Bayer
 

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 focus for go-forward app workloads, the proposal is being
reworked with diego in-mind and updated for new requirements. the name of
this new proposal is called "isolation groups" and dieu has committed to
sharing that proposal with the cf community in the coming weeks.

[1] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki
[2]
https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Design-Documents
[3]
https://docs.google.com/document/d/1GNjQwGBh0BvfAYpX0LTUYn6h4oLz7v4P9pNy0xHZtMw/edit#heading=h.gjdgxs

On Fri, Sep 11, 2015 at 11:49 PM, ezhang <ezhang(a)pivotal.io> wrote:

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 nats config to installed CF
nats
3: setup different Stack for each DEA

then App can push though one cloud controller, and run on different IaaS
pool through stack. Each DEA managed by their own BOSH



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Multi-DEA-pool-in-cloudfoundry-tp1678.html
Sent from the CF Dev mailing list archive at Nabble.com.
--
Thank you,

James Bayer


ezhang <ezhang@...>
 

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 nats config to installed CF nats
3: setup different Stack for each DEA

then App can push though one cloud controller, and run on different IaaS
pool through stack. Each DEA managed by their own BOSH



--
View this message in context: http://cf-dev.70369.x6.nabble.com/Multi-DEA-pool-in-cloudfoundry-tp1678.html
Sent from the CF Dev mailing list archive at Nabble.com.