Microsoft and Docker team up to make packaging cloud-native applications easier

Post by mnoorali » Tue, Dec 04, 2018, 7:37 PM UTC

sytse wrote: post #41

gabrtv wrote: post #4

Gabe from Microsoft here. Happy to answer any questions. A few links to help you explore the spec and tooling: - https://cnab.io - https://duffle.sh/ - https://open.microsoft.com/2018/12/04/announcing-cnab-cloud-...

The announcement talks about "reliably provision application resources in different environments". Does that mean multiple clouds? I'm asking because in the Ansible example in https://github.com/deislabs/bundles/blob/master/ansiblebase/... I see AZURE_TENANT AZURE_CLIENT_ID AZURE_SECRET AZURE_SUBSCRIPTION_ID but nothing for other clouds. Would you have to add configuration for every cloud you have to support?

Post by bacongobbler » Tue, Dec 04, 2018, 7:46 PM UTC

donmcronald wrote: post #30

gabrtv wrote: post #22

Earlier quoted context omitted.

CNAB makes reproducibility possible by providing unified lifecycle management, packaging, and distribution. Of course if bundle authors don't take care to work around problems with imperative logic, that's a risk. In practice, we see declarative models for building bundles offer more reproducibility. For example, see how you can build a CNAB using a Terraform base image: https://github.com/deislabs/bundles/tree/maste…

Yeah. I read through some of those existing configs and I see how it works now. My first instinct when I see `cnab/app/run install` is to think it's for installing the app, but now I see it's for provisioning / deploying to the environment. As soon as I think of install, uninstall as deploy, undeploy then it clicks for me.

Post by sytse » Tue, Dec 04, 2018, 7:57 PM UTC

mnoorali wrote: post #42

sytse wrote: post #41

Earlier quoted context omitted.

The announcement talks about "reliably provision application resources in different environments". Does that mean multiple clouds? I'm asking because in the Ansible example in https://github.com/deislabs/bundles/blob/master/ansiblebase/... I see AZURE_TENANT AZURE_CLIENT_ID AZURE_SECRET AZURE_SUBSCRIPTION_ID but nothing for other clouds. Would you have to add configuration for every cloud you have to support?

The format is cloud agnostic. Here is an example of a bundle that Bitnami built that provisions wordpress and Amazon RDS https://github.com/bitnami/cnab-bundles/tree/master/wordpres...

Post by bdburns » Tue, Dec 04, 2018, 8:08 PM UTC

sytse wrote: post #46

mnoorali wrote: post #42

Earlier quoted context omitted.

The format is cloud agnostic. Here is an example of a bundle that Bitnami built that provisions wordpress and Amazon RDS https://github.com/bitnami/cnab-bundles/tree/master/wordpres...

Thanks! In https://github.com/bitnami/cnab-bundles/blob/master/wordpres... I see AWS but not Azure. It seems that in this context cloud agnostic means any cloud can be supported. I'm interested in application portability [0]. To do this with CNAB you need to add every cloud to the bundle. This is contrast to something like Crossplane [1] that intents to support multi-cloud with a single specification. 0. https://medi…

Post by sytse » Tue, Dec 04, 2018, 9:44 PM UTC

gabrtv wrote: post #26

philips wrote: post #24

Earlier quoted context omitted.

I see it a bit differently. To me it looks like CNAB invents a new way of describing and deploying an application that looks nothing like a Kubernetes API while Crossplane is trying to use the existing Kubernetes API tooling to interoperate with and leverage that ecosystem. Just because you are using a Kubernetes API doesn't mean you are presuming a Kubernetes cluster IMHO. The work being done with virtual kubelet[1]…

As I said, we have lots of customers who need a packaging format that targets clouds APIs which in some cases don't have any containers (hence no need for Kubernetes). Functions + datastore + service bus being a good example. I know there's lots of love for Kubernetes, containers, and operators -- with me too. Still we can't and shouldn't presume the existence of Kubernetes or Kubernetes APIs to solve the problems CN…