Re: Logging into the API on Juju 2.0

Ok perfect, i'll try these tags out with the api. Thanks again On Fri, Feb 26, 2016 at 9:01 PM, Ian Booth wrote: > The admin user tag for aws is the same as described below. The @local > suffix > pertains to the controller not the cloud - think of it as users for a >

Re: Logging into the API on Juju 2.0

Thanks that makes sense now. I don't have aws or anything but what would the admin user tag for those clouds look like? On Fri, Feb 26, 2016 at 7:07 PM, Andrew Wilkins < andrew.wilk...@canonical.com> wrote: > On Sat, Feb 27, 2016 at 1:10 AM Adam Stokes > wrote: > >>

Re: Logging into the API on Juju 2.0

On Sat, Feb 27, 2016 at 1:10 AM Adam Stokes wrote: > Also, will the API support non admin users to login and query the various > modelmanager methods they have access to? If so, will this be available by > GA release? > > On Fri, Feb 26, 2016 at 11:45 AM, Adam Stokes

Fwd: Charm build doesn't update interface layers

Dropped the list accidentally on my reply. Also, meant to note that you only need to use charm-build (hyphenated) until the new top-level charm command is available. -- Forwarded message -- From: Cory Johns Date: Fri, Feb 26, 2016 at 4:27 PM Subject:

Re: Hooks and interfaces!

I'd just like to note that the "relation: interface" headers in the "Connects to:" box on charm pages on jujucharms.com are links that will take you to a search of all the charms that can be connected to that relation. For example, all charms that you could conceivably connect the Gitlab charm to

Re: LXD Bootstrap

No worries Serge I was just some Friday fun to get me out of the daily grind. Thanks for the update. Tom On 26 Feb 2016 8:02 pm, "Serge E. Hallyn" wrote: > On Fri, Feb 26, 2016 at 02:42:51PM +, Tom Barber wrote: > > Afternoon, got bored decided to try Jorge's blog post

Re: LXD Bootstrap

On Jorge's advice I rolled all the way back to the juju 1.26 beta 2 tag, lxd beta 2 and xenial and still it fails with connection refused weird. On 26 Feb 2016 16:02, "Tom Barber" wrote: > I've tried rolling back on Juju but still can't find a combination, its > not

Re: Logging into the API on Juju 2.0

Also, will the API support non admin users to login and query the various modelmanager methods they have access to? If so, will this be available by GA release? On Fri, Feb 26, 2016 at 11:45 AM, Adam Stokes wrote: > Currently, the only way to login to the Juju 2.0 api

Logging into the API on Juju 2.0

Currently, the only way to login to the Juju 2.0 api is to use the Tag of 'user-admin'. However, all the files created by juju during bootstrap (accounts.yaml, models.yaml, controllers.yaml) only mention the admin user as 'admin@local' for the controller. When will the API login support logging

Re: LXD Bootstrap

I've tried rolling back on Juju but still can't find a combination, its not the end of the world, I was curious. Anyway, if I lxc exec into the machine I find SSH is down which sorta explains the connection failure: cloud init runs but then seems to get no futher

Re: LXD Bootstrap

Sorry forgot to mention, Juju was built from trunk this morning. Tom -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart

LXD Bootstrap

Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS I'd read on a few posts about the requirement for LXD beta2 because of API incompatibilities so I found the deb's and installed them. Its up and running and images start fine, but juju bootstrap fails with connection

Re: Hooks and interfaces!

Hey Marco Its not a problem, its also me trying to wrap my head around this stuff better. But if they go offpiste there should be a big fat warning somewhere in the readme etc that indicates that its not compatible, that way I wouldn't spend an afternoon trying to stand up Gitlab against Apache2

Re: Hooks and interfaces!

Hey Tom, sorry you've hit something that was one of the driving forces behind interface layers - the http interface. It's been a heavily contested and unique interface because it was originally defined as just hostname and port. However, other charms don't agree on this simple implementation and

Re: Hooks and interfaces!

Thanks Merlijn I'm not just spouting complete nonsense then! ;) Tom -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart

Re: Hooks and interfaces!

Hey Merlijn Thanks for the response(great presentation in Gent by the way). Having slept on it a bit, and poked around a bit more this morning I see that the http interface does implement the hooks, so I guess I'm just getting confused with hook execution in the new reactive layer. Currently its

Re: Hooks and interfaces!

Hi Tom First of all, thank you for sharing your experiences. The reactive approach is quite new and feedback like this is very valuable. I understand the frustration, I've had similar experiences with the reactive framework. I think that there is still significant work needed in both `charm