search

cloudfoundry / diego-notes

Diego Notes
Apache License 2.0
23 stars 7 forks source link

Multiple deployment strategies in the CC-Bridge #20

Closed tedsuo closed 7 years ago

tedsuo commented 9 years ago

The issue we are facing is the desire to support multiple Deployment strategies in CF (buildpack, docker, dot-net, app-container, etc...). Ideally these deployment strategies work like "plugins", in that each CF deployment can consist of a different set of deployment strategies.

To accomplish this in the CC-Bridge, we have the concept of App-Lifecycle's. This is currently sort-of pluggable, sort-of hardwired. How should we re-architect the lifecycles to be fully pluggable?

Proposal is here: https://github.com/pivotal-cf-experimental/diego-dev-notes/blob/master/proposals/lifecycle-design.md

tedsuo commented 9 years ago

An issue brought up today regarding lifecycles is that CC currently implements lifecycle-specific policy. For example, the admin can restrict which buildpacks are allowable. In the future, it's easy to see policies extended to other lifecycles, such as docker policies, etc. How should we handle this?

emalm commented 7 years ago

Closing this out, as the CAPI team owns the CC-Bridge and the equivalent functionality in Cloud Controller itself.