Juju state as code?
patrik.karisch at gmail.com
Thu Oct 6 08:28:06 UTC 2016
one thing which mocks my head, when evaluating Juju is, the state is only
in the controller which gets deployed with commands. Which means I have
IMHO no docs/history of how my current state of machines and charms was
As a side note: I'm used to Ansible and Puppet, which means I have all my
infrastructe in a Git repository which describes my whole infrastructure
and works always in a reproducable and idempotent way. How can I map this
concept to Juju? I fear a little bit to loose this automation concept while
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju