Hi all,
I spent some time this week reviewing a charm, and have some questions
about some of the Charm Store Policy requirements. I want to make sure I
understand these requirements well enough to explain them to people
who's charms I review, and to be able to give them direction on how they
can b
Hi Curtis,
On 02/26/2015 01:47 PM, Curtis Hovey-Canonical wrote:
> juju-core 1.22-beta4
>
> Development releases use the 'devel' simple-streams. You must configure
> the 'agent-stream' option in your environments.yaml to use the matching
> juju agents.
>
> agent-stream: devel
There don't se
, also seeing that.
>>
>> On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs
>> wrote:
> ...
> Thanks,https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:devel:tools.sjson
>>>
>>> or
>>>
>>>
>>> https://streams.canonical.com/
On 03/27/2015 10:08 AM, Matt Rae wrote:
> Also noting that running MAAS in a vm has worked fine in my experience. Are
> there any pitfalls with using a vm?
Nope - that should work just fine as long as you're using a bridged
interface for the network you want to manage.
I typically run MAAS in an
Hi Daniel,
There is some documentation for installing MAAS in a container here:
https://maas.ubuntu.com/docs/install.html#container-install
It's focused on 2.0 but the same steps should work for 1.9.3 too. It covers
setting up the loop devices.
Hope this helps,
Jason
On Sat, Aug 6, 2016 at 10:
/apparmor.d/lxc-custom-default contains:
>
> profile lxc-container-extx-mounts
> flags=(attach_disconnected,mediate_deleted) {
> #include
> mount fstype=ext4 -> /**,
> mount fstype=ext3 -> /**,
> mount fstype=ext2 -> /**,
> }
>
> Any suggestions as to
I'm trying to understand why config-changed is being triggered on my units
when I'm not changing application config settings.
>From doc/charms-in-action.txt:
"The `config-changed` hook always runs once immediately after the install
hook,
and likewise after the upgrade-charm hook. It also runs whe
I noticed that for the juju snap, edge and beta channels have older
releases than candidate. Shouldn't they always be at least the same
version as candidate, if not newer?
stable:2.1.3 (1922) 24MB classic
candidate: 2.2-rc2 (1929) 25MB classic
beta:
-alpha1) and now are being
> published again.
>
> Nicholas
>
> On 06/12/2017 11:18 AM, Jason Hobbs wrote:
>
>> I noticed that for the juju snap, edge and beta channels have older
>> releases than candidate. Shouldn't they always be at least the same
>&g
