TL;DR there is a new testing tool for Juju and you should check it out at
https://github.com/juju-solutions/matrix
Paraphrasing Netflix, "If you can't run chaos monkey in production you're
not really prepared to deal with failure". And it's true. It quickly
becomes a question of constraints if doi
The observation which might be too basic here is that for an Amulet test to
do something useful it needs to exercise the relations. This implies
(almost always) another charm. When your testing depends on more than one
charm (in what might be a synthetic situation) you are talking about
bundles. By
I really appreciate this kind of thinking, looking for root causes is the
hallmark of better systems design. That said I'd suggest the difference
between _event_ and _state_ as you describe them are really only a usage
convention around the same abstraction.
The semantics you seem to be pointing t
Hi Adam,
This has been pushed to the index. In the future people should be able to
add layers themselves with a Launchpad Account. Some of the things you do
here might be able to find a home in the basic layer (for example the pep8
code). I'd be happy if over time this layer could be smaller, and
Currently you have to ask a ~charmer and this list is a fine way to do
that. We plan on lowering the barrier to modifying the index in the very
near term. That said you have this layer as a nested directory in a repo.
We currently only support linking to top level repos though if this sort of
struc
Charm Composition is a small tool facilitating a new pattern for developing
and maintain Juju Charms. In its simplest form it lets you combine
directories, called Layers, of files to create a charm. Rather than just
copying files around however it keeps track of which files came from which
Layer so
While convention is great there is an additional path, you can if your
project differs from the de facto standards, include an explicit list of
targets in your tests/tests.yaml file
makefile:
- lint
- unit_test
- something_else
That file allows customization of much of bundletesters p
This appears to be an issue with the default version of Python.
juju-deployer is a Python 2 application and still uses Python 2 syntax in a
number of places as this traceback shows. Can you attempt the install using
a version of Python 2.7?
-Ben
On Mon, Feb 3, 2014 at 3:43 PM, Daniele Stroppa
wr
