Small comment while mentioning charm-helpers:
What I would really like to see is the project's tests running in CI,
before things start moving around. The last few times we ran them we
discovered many were broken (I suspect people need to put out fires
and don't bother running the tests before
.
On Wed, Aug 12, 2015 at 6:59 AM Christopher Glass trib...@gmail.com wrote:
Small comment while mentioning charm-helpers:
What I would really like to see is the project's tests running in CI,
before things start moving around. The last few times we ran them we
discovered many were broken (I
Hi Vasiliy,
I'm not entirely familiar with the KVM aspect of this, but I'm used to
deploying stuff on LXC with the local provider. Maybe somebody with
more KVM+juju experience can chime in.
Try deploying your first charm normally (without --to). That should
create a machine1 VM, then you can
at 10:55 AM, Christopher Glass trib...@gmail.com
wrote:
Hi all,
I've started playing with and deploying my ubuntu-mirror charm, that
leverages the excellent storage subordinate charm to create full
ubuntu mirrors.
That allows you to mirror a lot of the bits that make up ubuntu: the
apt
Hi all,
I've started playing with and deploying my ubuntu-mirror charm, that
leverages the excellent storage subordinate charm to create full
ubuntu mirrors.
That allows you to mirror a lot of the bits that make up ubuntu: the
apt repositories of course, but also cdimages, releases, ports and
Maybe we should ask github to ping him.
I did the same for an similar situation and their reaction was: they
sent him a couple of emails about it, and gave me the name after they
didn't get a response for X days. I guess mentioning that it also
happens to be our trademark might help, too.
Since
For the record, we can easily send branches against charms that matter
to us for this particular case (as we will for few other
landscape-owned branches waiting for review [1] [2] [3], hint hint :)
).
But this seems like a problem in need of a more general (and scalable) solution.
- Chris
