Re: Should 'juju status' always include a timestamp

Yes, a timestamp is always appropriate. On Wed, Apr 18, 2018 at 3:12 AM, Merlijn Sebrechts wrote: > +1 > > Op wo 18 apr. 2018 om 09:19 schreef John A Meinel > : >> >> I was just going over a list of pastes from James Beedy on this bug: >>

Re: Juju 2.2-rc2 has been released

(2.3-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 >> ve

Re: Juju 2.2-rc2 has been released

(2.3-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 >> ve

Re: Juju 2.2-rc2 has been released

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:

Re: Juju 2.2-rc2 has been released

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:

config-changed from transient unit agent errors

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

Re: upcoming change in Juju 2.0 to bootstrap arguments

Thanks for the heads up Ian - we will adjust our scripts to accomodate. Jason On Thu, Oct 13, 2016 at 12:36 AM, Ian Booth wrote: > See https://bugs.launchpad.net/juju/+bug/1632919 > > The order of the cloud/region and controller name arguments will be > swapped. > >

Re: maas in a container

mor.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 wh

Re: maas in a container

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

Re: requirements for

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

Re: juju devel 1.22-beta4 is available for testing.

, also seeing that. On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs jason.ho...@canonical.com wrote: ... Thanks,https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:devel:tools.sjson or https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.sjson

Re: juju devel 1.22-beta4 is available for testing.

, also seeing that. On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs jason.ho...@canonical.com wrote: ... Thanks,https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:devel:tools.sjson or https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.sjson

questions on Charm Store Policy

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