Is CloudFoundry viable for small deployments (1-5 machines)?


Mike M
 

We are looking to use Cloud Foundry for an on-premises "fog" platform. We would like to keep a minimal footprint and run on 1-5 small servers in production. Is this practical with Cloud Foundry? I know OpenStack struggles to run on 1-2 machines.

Thanks,
Mike


David Sabeti
 

Hey Mike,

I don't think there's currently a recommended way in the OSS CF to get your
VM footprint to that size (I think some vendors support a way to do this),
but I did want to let you know that the CF Release Integration team has
this issue on our radar. When we get to working on that for
cf-deployment[0], it would be great if I could reach and get some more
details about your needs.

In the meantime, you'll probably need to experiment yourself with a
deployment architecture as we've never tested a specific minimal
configuration. You might try a few things like this:
1. You could probably colocate consul, etcd, nats, and datastores into an
"infrastructure" job
2. You could also probable consolidate the Cloud Controller jobs, the CC
bridge jobs, the Diego BBS and Auctioneer/Brain jobs, and UAA into a
"control plane"
3. Router, Loggregator Traffic Controllers, and SSH Proxy jobs are the
"front door" to the CF installation. Maybe you could merge those?

Good luck!

David Sabeti
CF Release Integration Project Lead


[0] https://github.com/cloudfoundry/cf-deployment

On Thu, Aug 17, 2017 at 2:42 PM Mike M <shotgunwilly99(a)gmail.com> wrote:

We are looking to use Cloud Foundry for an on-premises "fog" platform. We
would like to keep a minimal footprint and run on 1-5 small servers in
production. Is this practical with Cloud Foundry? I know OpenStack
struggles to run on 1-2 machines.

Thanks,
Mike


Daniel Jones
 

Hi Mike,

Our fine friends at Altoros gave a talk on this subject a few years ago,
and I think their suggestion was that 5 VMs is doable.

https://www.youtube.com/watch?v=RJx9tLoa2ug

Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

On 18 August 2017 at 18:18, David Sabeti <dsabeti(a)pivotal.io> wrote:

Hey Mike,

I don't think there's currently a recommended way in the OSS CF to get
your VM footprint to that size (I think some vendors support a way to do
this), but I did want to let you know that the CF Release Integration team
has this issue on our radar. When we get to working on that for
cf-deployment[0], it would be great if I could reach and get some more
details about your needs.

In the meantime, you'll probably need to experiment yourself with a
deployment architecture as we've never tested a specific minimal
configuration. You might try a few things like this:
1. You could probably colocate consul, etcd, nats, and datastores into an
"infrastructure" job
2. You could also probable consolidate the Cloud Controller jobs, the CC
bridge jobs, the Diego BBS and Auctioneer/Brain jobs, and UAA into a
"control plane"
3. Router, Loggregator Traffic Controllers, and SSH Proxy jobs are the
"front door" to the CF installation. Maybe you could merge those?

Good luck!

David Sabeti
CF Release Integration Project Lead


[0] https://github.com/cloudfoundry/cf-deployment

On Thu, Aug 17, 2017 at 2:42 PM Mike M <shotgunwilly99(a)gmail.com> wrote:

We are looking to use Cloud Foundry for an on-premises "fog" platform. We
would like to keep a minimal footprint and run on 1-5 small servers in
production. Is this practical with Cloud Foundry? I know OpenStack
struggles to run on 1-2 machines.

Thanks,
Mike