Greetings everyone, I spent some time hacking up a deep dive on how to work with layer-docker, the darling layer from the ~containers team making onboarding users looking to use docker in their juju experience even easier.
http://dasroot.net/posts/2016-08-03-layer-docker-deep-dive/ This breaks down a multi-factor application comprising of: - A Python webapp which lets you vote between two options - A Redis queue which collects new votes - A .Net worker which consumes votes from redis and stores them in a database. - A Postgres database backed by a Docker volume - A Node.js webapp which shows the results of the voting in real time You'll learn how to deploy this "bundle" (i didn't include bundle instructions) as a stand-alone charm for evaluation purposes, and then how to connect to external services for proper scale out production workloads where data persistence and horizontal scalability is a key factor. I wrote this post in tandem with doing the charming work. If you notice any issues please either file a comment on the post, ping me here on the mailing list, or file a bug against any of the mentioned repositories in the post. (except the core vote-app-example from docker inc, they didn't help in this post, so it's likely to get closed as wontfix). This is also a prelim document that I plan on extracting for the juju docs, if this was helpful, I'd love to know that too! Thanks and all the best, Charles -- Juju Charmer Canonical Group Ltd. Ubuntu - Linux for human beings | www.ubuntu.com Juju - The fastest way to model your service | www.jujucharms.com
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
