search

julz / cube

a kube backend for cf, because k-why not
21 stars 8 forks source link

My app should be immediately started when I `cf start` (no waiting for convergence) #18

Open julz opened 6 years ago

julz commented 6 years ago

Acceptance:

  1. Deploy and enable eirini following instructions on repo
  2. cf push --no-start
  3. cf start
  4. See that the app is immediately started (i.e. deployments created and set to non-zero instance count), where immediately means doesn't wait for convergence loop (this may require a bit of white-box accepting, depending on how quick convergence is)
andrew-edgar commented 6 years ago

1 point

herrjulz commented 6 years ago

With cloud_controller_ng/3aaa4db , nsync / cc-bridge endpoints are gone and CC only communicates with the BBS through a single HTTP interface. We need Eirini to implement the relevant subset of the BBS API (prior NSYNC and TPS endpoints) and point CC to Eirini using cc.diego.bbs.url. The BBS API is described in bbs/doc/api-lrps.

The new implementation approach is to provide a single HTTP frontend (implementing the BBS API) and dispatch the relevant requests to the existing st8ger, sync, and tps code. The converter code can then be re-used to start apps immediately after cf start.

@julz, @andrew-edgar this story needs to be re-pointed.