Fwd: [ANN] charm-tools 1.9.3

Awesome! Now I have an explanation for the weird behaviour I got today. `charm compose` was working fine until suddenly I started getting errors because wheel was not installed in the venv. Running `sudo apt-get update; sudo apt-get upgrade` fixed my problems, I guess this was right after fix

[ANN] charm-tools 1.9.3

Hello everyone! I'm happy to announce another charm-tools release today, this is the 1.9.3 which succeeds 1.8.0 as the latest release of charm-tools. If you've managed to install 1.9.0, 1.9.1, or 1.9.2 in the past several days please be sure to upgrade. As always, you can verify the version you

Re: Tuning ceph

Hi, In this particular case I just want to make sure that my settings for CRUSH are used for various pools and be able to define my own pools (see below). I'm trying to create two different pools for both nova-compute and cinder-ceph (one with SSDs the other with spinning drives). I have managed

Upgrading minimum Go version?

Hi (mostly Curtis), Is there a plan to bump the minimum Go version? Some of our dependencies do not build with Go 1.2. The LXD provider only builds with Go 1.3 (I think?), and I've got a PR up that updates the azure-sdk-for-go dependency, but it's blocked because the newer doesn't build with Go

Re: [ANN] charm-tools 1.9.3

On Wed, Nov 25, 2015 at 4:08 PM Simon Davy wrote: > On 25 November 2015 at 16:02, Marco Ceppi > wrote: > > ## Wheel House for layer dependencies > > > > Going forward we recommend all dependencies for layers and charms be > > packaged in a

Re: [ANN] charm-tools 1.9.3

On Wed, Nov 25, 2015 at 7:44 PM Rick Harding wrote: > On Wed, Nov 25, 2015 at 4:08 PM Simon Davy > >> I don't know where we are at with the resources work, but maybe that >> could have a part to play here? >> > > This is exactly what I wanted to bring up for

[Review Queue] ibm-platform-symphony

I took some time to review the ibm-platform-symphony charm today. This charm requires the IBM software to be downloaded (all 4.8 GB of it!) and manually hosted on an HTTP server before the deploy will succeed. This charm did not pass my review and you can read more about the specifics here:

Re: Tuning ceph

Hi, Yes, I got the the same conclusion, either write my own charms to try to get the features implemented upstream. In a way I think that having some sort of local 'overlay' for the hooks (that get's applied automatically, but doesn't modify the original charms) would make the things easier. At

Re: Tuning ceph

Pshem, If you have specific use cases around the setting of config options, please do share. The charms tend to be opinionated about configuration and make it simple to deploy the majority of installations. However, there will undoubtedly be config tweaks here and there. Your use cases can help

Re: [ANN] charm-tools 1.9.3

What if we only needed pure python modules? It seems like the toolchain will always be installed because of some of the dependencies of charmhelpers? Will these additional deps become optional once charmhelpers is refactored? On Wed, Nov 25, 2015, 11:18 PM Marco Ceppi

Coverage testing

It's been on my TODO list for a long time to set up regular coverage testing for Juju. I still haven't done it, but I've written a script that gets us a step closer: https://gist.github.com/axw/457a402b4dfb4e4267f9 If you have gocov (go get github.com/axw/gocov/gocov), then you can run the

Re: trouble with dependent repos

On 24 November 2015 at 15:51, Eric Snow wrote: > On Mon, Nov 23, 2015 at 9:32 PM, Nate Finch wrote: >> Last week, I had trouble landing code in gopkg.in/juju/charm.v6-unstable, > > I had a similar experience last week with backward-incompatible