[ Docs ] - Charming with Docker

[Kapil Thangavelu]

i think participating in the burgeoning docker ecosystem is a worthwhile
goal by making it easier to write charms that utilize docker. I do have
some concerns though about the complexity of the layering that's taking
place in the charm ecosystem. I've found that juju has been fairly hard to
teach and adapt to real world usage and the layering of frameworks at the
charm authoring level makes learning and productivity for new users even
harder to achieve (ie those docs reference, charm helpers, reactive charm
helpers, docker reactive 'layer', charm composition), all of which are
fairly advanced concepts to a new user, and frankly is all of that
nescessary to understand running a shell script
https://github.com/juju-solutions/layer-docker/blob/master/scripts/install_docker.sh
which is effectively the jujuized version of (curl get.docker.com | sh) ..
now say i want to configure an insecure registry or any other docker cli
param i have to break apart the layer abstraction anyways. It does seem
like a useful intro to some of the advanced/additional concepts in charm
authoring ecosystem, but at the same time the burden seems high (ie. kiss
violation) for how to run a docker container.

cheers,

Kapil


On Fri, Sep 11, 2015 at 11:40 AM, Charles Butler <
charles.butler at canonical.com> wrote:

> If anyone here is interested in delivering Docker App Containers with
> Juju, mbruzek and I have put together some documents around a hot new
> process using composer layers and the reactive framework.
>
> This is interesting because you the charm author will only be concerned
> with how to deliver your application layers logic. You don't need to worry
> about installing docker, or how to scaffold out a full charm boilerplate.
> This entire process reduces the total cost of ownership of the author to
> just managing their app layer + container.
>
>  https://github.com/juju/docs/pull/672
>
> And we've constructed/linked to an example charm using this process.
> There's probably holes in this document, and welcome feedback directly on
> the pull request to suss them out.
>
> We're fully interested in receiving your feedback about this, as its
> important that we are properly engaging our users that are interested in
> delivering their dockerized app with Juju, and that we've given you the
> proper lessons to do so easily, and made the right decisions in tooling.
>
> All the best,
>
>
> Charles Butler <charles.butler at canonical.com> - Juju Charmer
> Come see the future of datacenter orchestration: http://jujucharms.com
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20150915/fa4f8b98/attachment.html>