=== grumblr is now known as grumble [12:28] Is there any sort of 'empty' charm? I want to deploy some subordinate charms to all machines (e.g. lldp, snmp) but don't have a common charm to relate them to. To work around that, I was thinking of deploying an 'empty' charm to all machines that I can use to relate subordinates? If there's a better way to acheive this though i'm open to it! [12:53] KingJ: just use the ubuntu charm :) [12:53] that is as empty as you can get [12:53] the only thing you can configure is an override for the hostname [13:09] BlackDex: Perfect! I'll give that a try. Is deploying an 'empty' charm like this then relating the subordinates to it the best way to go about doing this overall, or is there a better way? [13:28] not that i know [13:28] i use it like this also [15:06] oke, trying to test something on aws with juju [15:06] how do i get a bigger rootfs? [15:06] my / is just ~7GB [15:07] i need more [15:09] preferably using settings in a bundle file [19:18] Is there a way to see a changelog of charm versions? [21:57] oké, i Just need to use the right constraint. root-disk that is [21:58] KingJ: the only way i know if is checking the sourcecode [21:59] and compare between the different versions [22:54] BlackDex: I had a peek, but it's hard to see the relation between the source tree and a given version - not really seeing any tags or branches inthe repo that allign with the charm version