authorized-keys is now optional

Hi users of the add-model API, The authorized-keys config is now only required at bootstrap time, because bootstrapping involves an SSH step. This means you no longer need to specify authorized-keys in your config for add-model. The Juju CLI will now automatically read ~/.ssh/id_rsa.pub and

Re: Automatic hook retries in Juju 2.0

This should really be added to the docs about the automatic retry and how to shut it off. I created an issue and linked it to this discussion. https://github.com/juju/docs/issues/1235 Can someone from core or more familiar with the feature document it for the rest of us? - Matt Bruzek

Windows and --race tests are now gating

Hi Juju developers, As requested by juju-core, we have added --race and Windows unit tests to gated landings. These tests are run concurrently, not sequentially, but all must complete before code can be landed. As a practical matter, this means that landings are now impossible until the Windows

Correction: Juju Office Hours, 15 July, 2100UTC/1600EDT/1300PDT

Sorry for the mixup everyone, it's 15 July, not the 25th. :) On Thu, Jul 7, 2016 at 10:52 AM, Jorge O. Castro wrote: > Hello everyone, a bunch of us have been on the road hitting up > devopsdays, Berlin Buzzwords, and other conferences, so we'd thought > we'd take a quick

Re: Reliably share a persistent filesystem between units

Thanks Mark that's super helpful. I'll read through the storage spec and inspect that bundle when I get a sec, and update here with thoughts on how it might help solve my problem. On Thu, Jul 7, 2016 at 3:35 PM Mark Shuttleworth wrote: > On 07/07/16 10:28, Robin Winslow wrote:

Juju Office Hours, 25 July, 2100UTC/1600EDT/1300PDT

Hello everyone, a bunch of us have been on the road hitting up devopsdays, Berlin Buzzwords, and other conferences, so we'd thought we'd take a quick timeout to have an office hours to share what we've been learning and doing over the past month: Juju Office Hours is a freeflow meeting where we

Re: Reliably share a persistent filesystem between units

On 07/07/16 10:28, Robin Winslow wrote: > Thanks everyone, some really helpful suggestions there. > > > On the storage roadmap we have shared filesystems, so your underlying > > cloud could provide these and Juju would organise them to be in the > > right place for each unit. > > Is there any

Re: Reliably share a persistent filesystem between units

Thanks everyone, some really helpful suggestions there. > On the storage roadmap we have shared filesystems, so your underlying > cloud could provide these and Juju would organise them to be in the > right place for each unit. Is there any information online that you could link me to about these

Re: Reliably share a persistent filesystem between units

Robin, there's a few ways to go about it. CephFS has come up with some of our team and at this time it's not something that folks are relying on production so I'm hesitant to vote up/down on that. You question on the NFS charm got me thinking that we do have a storage subordinate that's been used

Re: Reliably share a persistent filesystem between units

I should also have mentioned that there are IIRC a few bundles which actually setup an NFS server and clients in the bundle in order to provide this entirely internally to the bundle (i.e. without any cloud or juju mediated storage management). Mark -- Juju mailing list Juju@lists.ubuntu.com

Re: Reliably share a persistent filesystem between units

Hi Robin, Interesting question, I'm expecting a lot of answers and comments :). Here are mines: * If the volume of data is small and its life expectancy is long, with few writes, but potentially lots of reads (like config files for example), you may want to use a simple system like etcd or

Re: Reliably share a persistent filesystem between units

On 07/07/16 06:02, Robin Winslow wrote: > Does anyone know of the best way to share a folder between Juju units > in a persistent and reliable way? On the storage roadmap we have shared filesystems, so your underlying cloud could provide these and Juju would organise them to be in the right place

Reliably share a persistent filesystem between units

Does anyone know of the best way to share a folder between Juju units in a persistent and reliable way? Up until now we've been dealing with shared data that needs persistence by storing it in Swift, and so I have written my applications to interact with a Swift server directly (and therefore the