3 ms·

The announcement talks about "reliably provision application resources in different environments". Does that mean multiple clouds? I'm asking because in the An

by sytse 8y ago

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/bundle.json 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?

mnoorali 8y ago
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/wordpress-k8s-rds https://github.com/bitnami/cnab-bundles/tree/master/wordpres...
- sytse 8y ago
  Thanks! In https://github.com/bitnami/cnab-bundles/blob/master/wordpress-k8s-rds/bundle.cnab 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://medium.com/gitlab-magazine/multi-cloud-maturity-model-2de185c01dd7 https://medium.com/gitlab-magazine/multi-cloud-maturity-mode... 1. https://news.ycombinator.com/item?id=18600603#18601961 https://news.ycombinator.com/item?id=18600603#18601961
  - bdburns 8y ago
    You can build a kubernetes based bundle that is cloud agnostic.
- amouat 8y ago
  I'm a little confused by this. I get the specification is cloud agnostic. But it looks like the developer needs to write the underlying code to provision and maintain the application on the various clouds. It feels like a too thin abstraction. And it seems pretty leaky currently; the examples all have hard and specific requirements e.g. Azure, k8s etc. What am I missing? Is the idea that we will create tooling to automatically create the provisioning and maintenance code?

by sytse 8y ago

mnoorali 8y ago

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/wordpress-k8s-rds https://github.com/bitnami/cnab-bundles/tree/master/wordpres...

sytse 8y ago
Thanks! In https://github.com/bitnami/cnab-bundles/blob/master/wordpress-k8s-rds/bundle.cnab 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://medium.com/gitlab-magazine/multi-cloud-maturity-model-2de185c01dd7 https://medium.com/gitlab-magazine/multi-cloud-maturity-mode... 1. https://news.ycombinator.com/item?id=18600603#18601961 https://news.ycombinator.com/item?id=18600603#18601961
- bdburns 8y ago
  You can build a kubernetes based bundle that is cloud agnostic.
amouat 8y ago
I'm a little confused by this. I get the specification is cloud agnostic. But it looks like the developer needs to write the underlying code to provision and maintain the application on the various clouds. It feels like a too thin abstraction. And it seems pretty leaky currently; the examples all have hard and specific requirements e.g. Azure, k8s etc. What am I missing? Is the idea that we will create tooling to automatically create the provisioning and maintenance code?