Re: Update Parallelization in Cloud Foundry

Amit Kumar Gupta

If by "hard dependency" you mean something that has to be up strictly
before another thing for a deploy to possibly succeed, I'm not sure if
there are any such hard dependencies. PCFDev (formerly MicroPCF) brings up
all the components simultaneously on a single VM [1
<>]. Some processes will flap until
other ones are up, but they eventually do all come up.

There probably isn't a single solution to minimizing update time while
guaranteeing 100% uptime, as the answer will depend on a lot of different
things. Are you running DEA and/or Diego? External database and/or
external blobstore? Are you just talking about uptime of apps, or also of
the platform API? What about services as well?

If you find a colocation/update strategy that works for you, I think the
community would really appreciate hearing about it.

(Just for fun, there's also nanocf [2 <>]
which is a Docker image with all of CF in it, and a bunch of videos where I
run nanocf in nanocf in BOSH-Lite CF [3



On Thu, Mar 10, 2016 at 2:24 AM, Omar Elazhary <omazhary(a)> wrote:

Thanks everyone. What I understood from Amit's response is that I can
parallelize certain components. What I also understood from both Amit's and
Dieu's responses is that some components have hard dependencies, while
others only have soft ones, and some components have no dependencies at
all. My question is: how can I figure out these dependencies? Are they
listed somewhere? The cloud foundry docs do a great job of describing each
component separately, but they do not explain which should be up before
which. That is what I need in order to work an execution plan in order to
minimize update time, all the while keeping CF 100% available.



Join { to automatically receive all group messages.