Re: Authenticating to model on shared controller

Through Identity manager and SSO with macaroons. You'll have them in ~/.go-cookies and ~/.local/share/juju/usso-store-token (or something like that). Feel free to ask in #jaas On Fri, Nov 4, 2016 at 6:51 PM, Tim Van Steenburgh < tim.van.steenbu...@canonical.com> wrote: > If I `juju register` a

Authenticating to model on shared controller

If I `juju register` a shared controller and add a model to it, how does the juju client authenticate to that model, since AFAICT there is no password locally? I'm asking b/c I need to be able to make other clients (python) work for this case. For the heck of it I tried with a blank password but

Re: Crashdump plugin

Oooh, nice. Glad to know that pulling relevant info for all those projects with plugins is nice and easy. New build in the ppa with some flags just for anybody who wants to get down and dirty... (-s --enable-sos) & (-S --sos-options), made it optional for now, but if it works well (and maybe we

Re: How to reproduce the same build output binaries?

I made the comparison yesterday of interfaces.juju.solutions performing a similar role to maven central and providing artifact versions to releases that ask for that release. On 4 Nov 2016 08:12, "Konstantinos Tsakalozos" wrote: > Indeed, layer and interface

Re: How to reproduce the same build output binaries?

Indeed, layer and interface versioning should please some release managers. Thanks, Konstantinos On Thu, Nov 3, 2016 at 5:53 PM, Ryan Beisner wrote: > As far as I know, there is no notion of a stable Layer or a stable > Interface. That makes it difficult to carry

Re: Crashdump plugin

Hello, Le 04/11/2016 à 03:43, Adam Stokes a écrit : > Nice, one thing you could do is tie this in with sosreport and just run that > against the machines. It already has support for juju, lxd, openstack, etc. > > https://github.com/sosreport/sos > > And a list of all the plugins we support are