Thoughts about Juju local as Dev

[Michael Nelson]

On Fri, Dec 5, 2014 at 12:54 PM, Sebastian <sebas5384 at gmail.com> wrote:
> Hey guys!
>
> I'm using Juju as a local environment a while now, and trying to implement
> Juju local a default workflow of our developers, which half of them have
> generally an Ubuntu (or at least based) and the other Mac OS X, but all are
> using the Vagrant workflow.
>
> And I have to tell you, what a challenge.

Hi Sebastian!

Wow - on our team we're not yet using juju for the developer
workflow... we'd like to, but there are still quite a few complexities
(Simon Davy has made some great progress). What we are doing
currently, which is working quite well is:

1) Devs generally have a single lxc/vm for each project which has the
complete developer environment for branch, test, code, commit, submit
for review.
2) When a new commit lands on our trunk (after gated CI testing), an
automated test deployment runs using the relevant charms for the
project (basically a juju-deployer config), verifying that the
deployment (and upgrade) are still working.

This way, devs don't need to care about juju for development, only for
deployment. Some devs do both, some only development, but the key is
that it's a choice.

Note that to ensure that the dev enviroment is consistent with that
created by the charm, we have all dependencies defined in the code
branch itself. The charm refers to the dependencies.txt of the code
and apt-get installs them (or whatever package manager is relevant).

Hope that helps,
-Michael