Re: Bitnami wordpress charm development

[Samuel Cozannet]

Hi Ney,

I've got myself in the same issue in the past, and found this pretty
useful: dos2unix. You can apt-get install it, then you get a dos2unix and a
unix2dos commands.

If you succeed with the bitnami -> charm, do you think you could create a
generic bitnami converter? That would be interesting.

Good charming!
Best,
Sam


--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of Cloud
Ubuntu   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]


On Tue, Mar 1, 2016 at 1:46 AM, Ney Moura  wrote:

> I was thinking that i missed some configurations to ran those commands
> properly only.
>
> Since I use nano, I wasn't able to see those.
>
> Thanks for the tip about hook environment and the command!
>
> Mainly for the quick response =D
>
> 2016-02-29 21:31 GMT-03:00 José Antonio Rey :
>
>> Glad that was it! When I opened it on vim, it said [dos] at the bottom,
>> and after googling the error I saw what it was.
>>
>> About the command, what happens is right. You should not be able to
>> execute any of those commands. The commands are only executable in a 'hook
>> environment', meaning only hooks will be able to run them. If you really
>> want to execute one of them, you can use 'juju run --service
>> wordpress-single "command goes here"'.
>>
>> Why do you want to run that manually? Anything missing?
>>
>> --
>> José Antonio Rey
>>
>> On Mon, Feb 29, 2016, 19:22 Ney Moura  wrote:
>>
>>> Thanks everyone!
>>>
>>> José Antonio, you were right!
>>>
>>> How did you discover that?
>>>
>>>
>>> But let me challenge you guys even more!
>>>
>>> I need to install something in the VM before using the juju commands,
>>> like status-set? I'm asking this because I wasn't able to run these
>>> commands in there.
>>>
>>>
>>> Thanks again!
>>>
>>> 2016-02-29 19:15 GMT-03:00 José Antonio Rey :
>>>
 This is because you are using Windows line breaks instead of Linux/Unix
 line breaks. Try saving your file with Linux/Unix line breaks and give it a
 go.


 On 02/29/2016 05:12 PM, David Britton wrote:

> On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
>
>>
>> But I keep having erros with the install hook. It says file not found.
>>
>>
> Maybe I missed it in the tarball -- could you attach a juju debug-log
> capture while you deploy it?
>
> Or, /var/log/all-machines.log from the bootstrap node is the same
> thing.
>
> Thanks!
>
>
 --
 José Antonio Rey

>>>
>>>
>>>
>>> --
>>> *Ney Moura Conceição*
>>>
>>
>
>
> --
> *Ney Moura Conceição*
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Ian Booth]

No, you are right.

$ juju list-controllers --format yaml

is better.

On 01/03/16 14:49, John Meinel wrote:
> Is there a reason to tell people to look at "controllers.yaml" rather than
> having the official mechanism be something like "juju list-controllers
> --format=yaml" ? I'd really like to avoid tying 3rd party scripts to our
> on-disk configuration. We can keep CLI compatibility, but on-disk
> structures aren't something we really want to commit to forever.
> 
> John
> =:->
> 
> On Tue, Mar 1, 2016 at 8:22 AM, Ian Booth  wrote:
> 
>> Just to be clear, the remote APi for listing models for a given controller
>> exists. But you do need to look at controllers.yaml to see what
>> controllers you
>> have bootstrapped or have access to in order to make the remote list
>> models api
>> call.
>>
>> On 01/03/16 13:14, Adam Stokes wrote:
>>> Got it squared away, being able to replicate `juju list-controllers`
>> didn't
>>> have a remote api. So I will continue to read from
>>> ~/.local/share/juju/controllers.yaml. My intention was to basically see
>>> what controllers were already bootstrapped and gather the models for
>> those
>>> controllers using the remote juju api. But that doesn't exist so I will
>>> mimic what `juju list-controllers` does and read from the yaml file for
>>> controllers that are local to my admin and users.
>>>
>>> On Mon, Feb 29, 2016 at 9:40 PM, Tim Penhey 
>>> wrote:
>>>
 It is the controller that you have logged into for the API.

 What are you wanting?

 You need a different API connection for each controller.

 Tim

 On 01/03/16 15:05, Adam Stokes wrote:
> Right, but how do you specify which controller you want to list the
> models for? The only way I can see is to manually `juju switch
> ` then re-login to the API and run the AllModels method. Is
> there a way (as an administrator) to specify which controller you want
> to list the models for?
>
> On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth  > wrote:
>
>
>
> On 01/03/16 11:25, Adam Stokes wrote:
> > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
> >
> > wrote:
> >
> >> On 01/03/16 03:48, Adam Stokes wrote:
> >>> Is there a way to list all models for a specific controller?
> >>
> >> Yes.
> >
> >
> > Mind pointing me to the api docs that has that capability?
> >
>
>
 https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
>
>


>>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
> 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[John Meinel]

Is there a reason to tell people to look at "controllers.yaml" rather than
having the official mechanism be something like "juju list-controllers
--format=yaml" ? I'd really like to avoid tying 3rd party scripts to our
on-disk configuration. We can keep CLI compatibility, but on-disk
structures aren't something we really want to commit to forever.

John
=:->

On Tue, Mar 1, 2016 at 8:22 AM, Ian Booth  wrote:

> Just to be clear, the remote APi for listing models for a given controller
> exists. But you do need to look at controllers.yaml to see what
> controllers you
> have bootstrapped or have access to in order to make the remote list
> models api
> call.
>
> On 01/03/16 13:14, Adam Stokes wrote:
> > Got it squared away, being able to replicate `juju list-controllers`
> didn't
> > have a remote api. So I will continue to read from
> > ~/.local/share/juju/controllers.yaml. My intention was to basically see
> > what controllers were already bootstrapped and gather the models for
> those
> > controllers using the remote juju api. But that doesn't exist so I will
> > mimic what `juju list-controllers` does and read from the yaml file for
> > controllers that are local to my admin and users.
> >
> > On Mon, Feb 29, 2016 at 9:40 PM, Tim Penhey 
> > wrote:
> >
> >> It is the controller that you have logged into for the API.
> >>
> >> What are you wanting?
> >>
> >> You need a different API connection for each controller.
> >>
> >> Tim
> >>
> >> On 01/03/16 15:05, Adam Stokes wrote:
> >>> Right, but how do you specify which controller you want to list the
> >>> models for? The only way I can see is to manually `juju switch
> >>> ` then re-login to the API and run the AllModels method. Is
> >>> there a way (as an administrator) to specify which controller you want
> >>> to list the models for?
> >>>
> >>> On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth  >>> > wrote:
> >>>
> >>>
> >>>
> >>> On 01/03/16 11:25, Adam Stokes wrote:
> >>> > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
> >>> >
> >>> > wrote:
> >>> >
> >>> >> On 01/03/16 03:48, Adam Stokes wrote:
> >>> >>> Is there a way to list all models for a specific controller?
> >>> >>
> >>> >> Yes.
> >>> >
> >>> >
> >>> > Mind pointing me to the api docs that has that capability?
> >>> >
> >>>
> >>>
> >> https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
> >>>
> >>>
> >>
> >>
> >
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Ian Booth]

Just to be clear, the remote APi for listing models for a given controller
exists. But you do need to look at controllers.yaml to see what controllers you
have bootstrapped or have access to in order to make the remote list models api
call.

On 01/03/16 13:14, Adam Stokes wrote:
> Got it squared away, being able to replicate `juju list-controllers` didn't
> have a remote api. So I will continue to read from
> ~/.local/share/juju/controllers.yaml. My intention was to basically see
> what controllers were already bootstrapped and gather the models for those
> controllers using the remote juju api. But that doesn't exist so I will
> mimic what `juju list-controllers` does and read from the yaml file for
> controllers that are local to my admin and users.
> 
> On Mon, Feb 29, 2016 at 9:40 PM, Tim Penhey 
> wrote:
> 
>> It is the controller that you have logged into for the API.
>>
>> What are you wanting?
>>
>> You need a different API connection for each controller.
>>
>> Tim
>>
>> On 01/03/16 15:05, Adam Stokes wrote:
>>> Right, but how do you specify which controller you want to list the
>>> models for? The only way I can see is to manually `juju switch
>>> ` then re-login to the API and run the AllModels method. Is
>>> there a way (as an administrator) to specify which controller you want
>>> to list the models for?
>>>
>>> On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth >> > wrote:
>>>
>>>
>>>
>>> On 01/03/16 11:25, Adam Stokes wrote:
>>> > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
>>> >
>>> > wrote:
>>> >
>>> >> On 01/03/16 03:48, Adam Stokes wrote:
>>> >>> Is there a way to list all models for a specific controller?
>>> >>
>>> >> Yes.
>>> >
>>> >
>>> > Mind pointing me to the api docs that has that capability?
>>> >
>>>
>>>
>> https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
>>>
>>>
>>
>>
> 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Adam Stokes]

Got it squared away, being able to replicate `juju list-controllers` didn't
have a remote api. So I will continue to read from
~/.local/share/juju/controllers.yaml. My intention was to basically see
what controllers were already bootstrapped and gather the models for those
controllers using the remote juju api. But that doesn't exist so I will
mimic what `juju list-controllers` does and read from the yaml file for
controllers that are local to my admin and users.

On Mon, Feb 29, 2016 at 9:40 PM, Tim Penhey 
wrote:

> It is the controller that you have logged into for the API.
>
> What are you wanting?
>
> You need a different API connection for each controller.
>
> Tim
>
> On 01/03/16 15:05, Adam Stokes wrote:
> > Right, but how do you specify which controller you want to list the
> > models for? The only way I can see is to manually `juju switch
> > ` then re-login to the API and run the AllModels method. Is
> > there a way (as an administrator) to specify which controller you want
> > to list the models for?
> >
> > On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth  > > wrote:
> >
> >
> >
> > On 01/03/16 11:25, Adam Stokes wrote:
> > > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
> > >
> > > wrote:
> > >
> > >> On 01/03/16 03:48, Adam Stokes wrote:
> > >>> Is there a way to list all models for a specific controller?
> > >>
> > >> Yes.
> > >
> > >
> > > Mind pointing me to the api docs that has that capability?
> > >
> >
> >
> https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
> >
> >
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Tim Penhey]

It is the controller that you have logged into for the API.

What are you wanting?

You need a different API connection for each controller.

Tim

On 01/03/16 15:05, Adam Stokes wrote:
> Right, but how do you specify which controller you want to list the
> models for? The only way I can see is to manually `juju switch
> ` then re-login to the API and run the AllModels method. Is
> there a way (as an administrator) to specify which controller you want
> to list the models for?
> 
> On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth  > wrote:
> 
> 
> 
> On 01/03/16 11:25, Adam Stokes wrote:
> > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
> >
> > wrote:
> >
> >> On 01/03/16 03:48, Adam Stokes wrote:
> >>> Is there a way to list all models for a specific controller?
> >>
> >> Yes.
> >
> >
> > Mind pointing me to the api docs that has that capability?
> >
> 
> https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
> 
> 


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Adam Stokes]

Right, but how do you specify which controller you want to list the models
for? The only way I can see is to manually `juju switch ` then
re-login to the API and run the AllModels method. Is there a way (as an
administrator) to specify which controller you want to list the models for?

On Mon, Feb 29, 2016 at 8:46 PM, Ian Booth  wrote:

>
>
> On 01/03/16 11:25, Adam Stokes wrote:
> > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey 
> > wrote:
> >
> >> On 01/03/16 03:48, Adam Stokes wrote:
> >>> Is there a way to list all models for a specific controller?
> >>
> >> Yes.
> >
> >
> > Mind pointing me to the api docs that has that capability?
> >
>
> https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Ian Booth]

On 01/03/16 11:25, Adam Stokes wrote:
> On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey 
> wrote:
> 
>> On 01/03/16 03:48, Adam Stokes wrote:
>>> Is there a way to list all models for a specific controller?
>>
>> Yes.
> 
> 
> Mind pointing me to the api docs that has that capability?
> 

https://godoc.org/github.com/juju/juju/api/controller#Client.AllModels

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Adam Stokes]

On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey 
wrote:

> On 01/03/16 03:48, Adam Stokes wrote:
> > Is there a way to list all models for a specific controller?
>
> Yes.


Mind pointing me to the api docs that has that capability?
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bitnami wordpress charm development

[Ney Moura]

I was thinking that i missed some configurations to ran those commands
properly only.

Since I use nano, I wasn't able to see those.

Thanks for the tip about hook environment and the command!

Mainly for the quick response =D

2016-02-29 21:31 GMT-03:00 José Antonio Rey :

> Glad that was it! When I opened it on vim, it said [dos] at the bottom,
> and after googling the error I saw what it was.
>
> About the command, what happens is right. You should not be able to
> execute any of those commands. The commands are only executable in a 'hook
> environment', meaning only hooks will be able to run them. If you really
> want to execute one of them, you can use 'juju run --service
> wordpress-single "command goes here"'.
>
> Why do you want to run that manually? Anything missing?
>
> --
> José Antonio Rey
>
> On Mon, Feb 29, 2016, 19:22 Ney Moura  wrote:
>
>> Thanks everyone!
>>
>> José Antonio, you were right!
>>
>> How did you discover that?
>>
>>
>> But let me challenge you guys even more!
>>
>> I need to install something in the VM before using the juju commands,
>> like status-set? I'm asking this because I wasn't able to run these
>> commands in there.
>>
>>
>> Thanks again!
>>
>> 2016-02-29 19:15 GMT-03:00 José Antonio Rey :
>>
>>> This is because you are using Windows line breaks instead of Linux/Unix
>>> line breaks. Try saving your file with Linux/Unix line breaks and give it a
>>> go.
>>>
>>>
>>> On 02/29/2016 05:12 PM, David Britton wrote:
>>>
 On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:

>
> But I keep having erros with the install hook. It says file not found.
>
>
 Maybe I missed it in the tarball -- could you attach a juju debug-log
 capture while you deploy it?

 Or, /var/log/all-machines.log from the bootstrap node is the same thing.

 Thanks!


>>> --
>>> José Antonio Rey
>>>
>>
>>
>>
>> --
>> *Ney Moura Conceição*
>>
>


-- 
*Ney Moura Conceição*
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bitnami wordpress charm development

[José Antonio Rey]

Glad that was it! When I opened it on vim, it said [dos] at the bottom, and
after googling the error I saw what it was.

About the command, what happens is right. You should not be able to execute
any of those commands. The commands are only executable in a 'hook
environment', meaning only hooks will be able to run them. If you really
want to execute one of them, you can use 'juju run --service
wordpress-single "command goes here"'.

Why do you want to run that manually? Anything missing?

--
José Antonio Rey

On Mon, Feb 29, 2016, 19:22 Ney Moura  wrote:

> Thanks everyone!
>
> José Antonio, you were right!
>
> How did you discover that?
>
>
> But let me challenge you guys even more!
>
> I need to install something in the VM before using the juju commands, like
> status-set? I'm asking this because I wasn't able to run these commands in
> there.
>
>
> Thanks again!
>
> 2016-02-29 19:15 GMT-03:00 José Antonio Rey :
>
>> This is because you are using Windows line breaks instead of Linux/Unix
>> line breaks. Try saving your file with Linux/Unix line breaks and give it a
>> go.
>>
>>
>> On 02/29/2016 05:12 PM, David Britton wrote:
>>
>>> On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
>>>

 But I keep having erros with the install hook. It says file not found.


>>> Maybe I missed it in the tarball -- could you attach a juju debug-log
>>> capture while you deploy it?
>>>
>>> Or, /var/log/all-machines.log from the bootstrap node is the same thing.
>>>
>>> Thanks!
>>>
>>>
>> --
>> José Antonio Rey
>>
>
>
>
> --
> *Ney Moura Conceição*
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Tim Penhey]

On 01/03/16 03:48, Adam Stokes wrote:
> Is there a way to list all models for a specific controller?

Yes.

> https://godoc.org/github.com/juju/juju/api/controller
> and https://godoc.org/github.com/juju/juju/api/modelmanager seem to do
> the same thing wrt listing models. This also only does it for whatever
> the current controller is set to before making the api call. I also
> don't see a way to list all active controllers, is there a way to do
> that as well?

There is a subtle difference.

> I also think the API is a bit confusing when it comes to distinguishing
> between a Controller and its Models. There are at least 2 places in the
> api that call out to listing models:
> 
> https://github.com/juju/juju/blob/master/api/controller/controller.go#L35
> https://github.com/juju/juju/blob/master/api/modelmanager/modelmanager.go#L78

The ModelManager facade is accessible by all users, and any user can
list environments that they have access to in a controller.

The Controller facade is accessible only by controller admins, those
users that have access to the controller model. This allows admins to
list all models in the controller, not just those they have access to.

Admins are special, and there needs to be a way for them to manage the
controller that may host environments for other people. Also, they
should not be listed as having regular access to environments that
aren't shared with them.


> And there are other areas where you create a model via modelmanager but
> can only gather information about a model via the client, why not just
> put all model related api code under modelmanager?

This is just historical garbage that hasn't been cleaned up yet.

Originally all access to the api server from the CLI was through the
"Client" facade. This rapidly became unwieldy and aspects have been
moved off.

Tim


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bitnami wordpress charm development

[Ney Moura]

Thanks everyone!

José Antonio, you were right!

How did you discover that?


But let me challenge you guys even more!

I need to install something in the VM before using the juju commands, like
status-set? I'm asking this because I wasn't able to run these commands in
there.


Thanks again!

2016-02-29 19:15 GMT-03:00 José Antonio Rey :

> This is because you are using Windows line breaks instead of Linux/Unix
> line breaks. Try saving your file with Linux/Unix line breaks and give it a
> go.
>
>
> On 02/29/2016 05:12 PM, David Britton wrote:
>
>> On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
>>
>>>
>>> But I keep having erros with the install hook. It says file not found.
>>>
>>>
>> Maybe I missed it in the tarball -- could you attach a juju debug-log
>> capture while you deploy it?
>>
>> Or, /var/log/all-machines.log from the bootstrap node is the same thing.
>>
>> Thanks!
>>
>>
> --
> José Antonio Rey
>



-- 
*Ney Moura Conceição*
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Tom Barber]

Its pretty weird, because a few reboots and it failed, now its magically
working post reboot. Worst comes to the worst I can flatten the machine
again and I'm sure it will reappear as it did the previous 2 occasions.

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 February 2016 at 23:35, Serge E. Hallyn  wrote:

> Hi Casey,
>
> I haven't reproduced that here in VMs.  If you can reproduce this at will
> (by
> rebooting the host) could you file a bug against the kernel (
> pad.lv/u/linux) ?
>
> thanks,
> -serge
>
> Quoting Casey Marshall (casey.marsh...@canonical.com):
> > On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber 
> wrote:
> >
> > > Seemingly the image name and key are the same, LXD and Juju are the
> same,
> > > so you've either done something magic or I'm confused with its now
> seeming
> > > happiness of the kernel debug mountpoint! :)
> > >
> >
> > I ran into a similar issue today. xenial host, running latest juju out of
> > master for LXD API compatibility. I was unable to bootstrap and sshd was
> > not starting in the controller instance.
> >
> > Remounted kernel debug on the host, and bootstrap started working, sshd
> > starting up now in my trusty instances.
> >
> > Did not refresh my images. If it happens after rebooting the host, I'll
> try
> > to collect more info.
> >
> > -Casey
> >
> >
> > > --
> > >
> > > Director Meteorite.bi - Saiku Analytics Founder
> > > Tel: +44(0)5603641316
> > >
> > > (Thanks to the Saiku community we reached our Kickstart
> > > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > > goal, but you can always help by sponsoring the project
> > > )
> > >
> > > On 29 February 2016 at 22:43, Tom Barber 
> wrote:
> > >
> > >> Hi Serge
> > >>
> > >> Fresh reboot and updated image, image boots with SSHD working fine, so
> > >> whatever you did, i assume worked or is a freak occurrence. I don't
> have
> > >> any old images kicking around and the import I copied from your email
> > >> appears to have stomped on the old image.
> > >>
> > >> FYI
> > >>
> > >> bugg@tomsdevbox:~$ lxc config show t1
> > >> name: t1
> > >> profiles:
> > >> - default
> > >> config:
> > >>   volatile.base_image:
> > >> 510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
> > >>   volatile.eth0.hwaddr: 00:16:3e:94:d5:66
> > >>   volatile.last_state.idmap:
> > >>
> '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
> > >>   volatile.lo.hwaddr: 00:16:3e:d2:98:62
> > >> devices:
> > >>   root:
> > >> path: /
> > >> type: disk
> > >> ephemeral: false
> > >>
> > >>
> > >> juju bootstrap now seems to run fine without remounting the kernel
> debug.
> > >>
> > >> Thanks for your help!
> > >>
> > >> Tom
> > >>
> > >>
> > >> --
> > >>
> > >> Director Meteorite.bi - Saiku Analytics Founder
> > >> Tel: +44(0)5603641316
> > >>
> > >> (Thanks to the Saiku community we reached our Kickstart
> > >> <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > >> goal, but you can always help by sponsoring the project
> > >> )
> > >>
> > >> On 29 February 2016 at 21:45, Serge E. Hallyn 
> wrote:
> > >>
> > >>> On Mon, Feb 29, 2016 at 09:45:14AM +, Tom Barber wrote:
> > >>> > Hi Serge
> > >>> >
> > >>> > I rebooted the host to see what happened and the lxc images that
> were
> > >>> > running fine all now have broken SSHD. This, to make absolutely
> clear
> > >>> > doesn't affect the Xenial image, just the trusty one I test with.
> > >>> >
> > >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
> > >>> > Creating fix-server2
> > >>> > Starting fix-server2
> > >>> >
> > >>> > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
> > >>> > root@fix-server2:~# ps aux |grep ssh
> > >>> > root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00
> grep
> > >>> > --color=auto ssh
> > >>> >
> > >>> > exit
> > >>> >
> > >>> > umount and remount kernel debug
> > >>> >
> > >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
> > >>> > Creating fix-server3
> > >>> > Starting fix-server3
> > >>> > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
> > >>> > root@fix-server3:~# ps aux |grep ssh
> > >>> > root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
> > >>> > /usr/sbin/sshd -D
> > >>> > root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00
> grep
> > >>> > --color=auto 

Re: LXD Bootstrap

[Serge E. Hallyn]

Hi Casey,

I haven't reproduced that here in VMs.  If you can reproduce this at will (by
rebooting the host) could you file a bug against the kernel (pad.lv/u/linux) ?

thanks,
-serge

Quoting Casey Marshall (casey.marsh...@canonical.com):
> On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber  wrote:
> 
> > Seemingly the image name and key are the same, LXD and Juju are the same,
> > so you've either done something magic or I'm confused with its now seeming
> > happiness of the kernel debug mountpoint! :)
> >
> 
> I ran into a similar issue today. xenial host, running latest juju out of
> master for LXD API compatibility. I was unable to bootstrap and sshd was
> not starting in the controller instance.
> 
> Remounted kernel debug on the host, and bootstrap started working, sshd
> starting up now in my trusty instances.
> 
> Did not refresh my images. If it happens after rebooting the host, I'll try
> to collect more info.
> 
> -Casey
> 
> 
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > 
> > goal, but you can always help by sponsoring the project
> > )
> >
> > On 29 February 2016 at 22:43, Tom Barber  wrote:
> >
> >> Hi Serge
> >>
> >> Fresh reboot and updated image, image boots with SSHD working fine, so
> >> whatever you did, i assume worked or is a freak occurrence. I don't have
> >> any old images kicking around and the import I copied from your email
> >> appears to have stomped on the old image.
> >>
> >> FYI
> >>
> >> bugg@tomsdevbox:~$ lxc config show t1
> >> name: t1
> >> profiles:
> >> - default
> >> config:
> >>   volatile.base_image:
> >> 510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
> >>   volatile.eth0.hwaddr: 00:16:3e:94:d5:66
> >>   volatile.last_state.idmap:
> >> '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
> >>   volatile.lo.hwaddr: 00:16:3e:d2:98:62
> >> devices:
> >>   root:
> >> path: /
> >> type: disk
> >> ephemeral: false
> >>
> >>
> >> juju bootstrap now seems to run fine without remounting the kernel debug.
> >>
> >> Thanks for your help!
> >>
> >> Tom
> >>
> >>
> >> --
> >>
> >> Director Meteorite.bi - Saiku Analytics Founder
> >> Tel: +44(0)5603641316
> >>
> >> (Thanks to the Saiku community we reached our Kickstart
> >> 
> >> goal, but you can always help by sponsoring the project
> >> )
> >>
> >> On 29 February 2016 at 21:45, Serge E. Hallyn  wrote:
> >>
> >>> On Mon, Feb 29, 2016 at 09:45:14AM +, Tom Barber wrote:
> >>> > Hi Serge
> >>> >
> >>> > I rebooted the host to see what happened and the lxc images that were
> >>> > running fine all now have broken SSHD. This, to make absolutely clear
> >>> > doesn't affect the Xenial image, just the trusty one I test with.
> >>> >
> >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
> >>> > Creating fix-server2
> >>> > Starting fix-server2
> >>> >
> >>> > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
> >>> > root@fix-server2:~# ps aux |grep ssh
> >>> > root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00 grep
> >>> > --color=auto ssh
> >>> >
> >>> > exit
> >>> >
> >>> > umount and remount kernel debug
> >>> >
> >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
> >>> > Creating fix-server3
> >>> > Starting fix-server3
> >>> > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
> >>> > root@fix-server3:~# ps aux |grep ssh
> >>> > root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
> >>> > /usr/sbin/sshd -D
> >>> > root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00 grep
> >>> > --color=auto ssh
> >>>
> >>> If you pull a fresh image using
> >>>
> >>> lxd-images import ubuntu --alias newtrusty trusty amd64
> >>>
> >>> and launch that
> >>>
> >>> lxc launch newtrusty t1
> >>>
> >>> does it have the same failure?
> >>>
> >>> What does
> >>>
> >>> lxc config show fix-server2 show?
> >>>
> >>
> >>
> >
> > --
> > Juju mailing list
> > Juju@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju
> >
> >

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Tom Barber]

Seemingly the image name and key are the same, LXD and Juju are the same,
so you've either done something magic or I'm confused with its now seeming
happiness of the kernel debug mountpoint! :)

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 February 2016 at 22:43, Tom Barber  wrote:

> Hi Serge
>
> Fresh reboot and updated image, image boots with SSHD working fine, so
> whatever you did, i assume worked or is a freak occurrence. I don't have
> any old images kicking around and the import I copied from your email
> appears to have stomped on the old image.
>
> FYI
>
> bugg@tomsdevbox:~$ lxc config show t1
> name: t1
> profiles:
> - default
> config:
>   volatile.base_image:
> 510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
>   volatile.eth0.hwaddr: 00:16:3e:94:d5:66
>   volatile.last_state.idmap:
> '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
>   volatile.lo.hwaddr: 00:16:3e:d2:98:62
> devices:
>   root:
> path: /
> type: disk
> ephemeral: false
>
>
> juju bootstrap now seems to run fine without remounting the kernel debug.
>
> Thanks for your help!
>
> Tom
>
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> On 29 February 2016 at 21:45, Serge E. Hallyn  wrote:
>
>> On Mon, Feb 29, 2016 at 09:45:14AM +, Tom Barber wrote:
>> > Hi Serge
>> >
>> > I rebooted the host to see what happened and the lxc images that were
>> > running fine all now have broken SSHD. This, to make absolutely clear
>> > doesn't affect the Xenial image, just the trusty one I test with.
>> >
>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
>> > Creating fix-server2
>> > Starting fix-server2
>> >
>> > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
>> > root@fix-server2:~# ps aux |grep ssh
>> > root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00 grep
>> > --color=auto ssh
>> >
>> > exit
>> >
>> > umount and remount kernel debug
>> >
>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
>> > Creating fix-server3
>> > Starting fix-server3
>> > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
>> > root@fix-server3:~# ps aux |grep ssh
>> > root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
>> > /usr/sbin/sshd -D
>> > root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00 grep
>> > --color=auto ssh
>>
>> If you pull a fresh image using
>>
>> lxd-images import ubuntu --alias newtrusty trusty amd64
>>
>> and launch that
>>
>> lxc launch newtrusty t1
>>
>> does it have the same failure?
>>
>> What does
>>
>> lxc config show fix-server2 show?
>>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Tom Barber]

Hi Serge

Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't have
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.

FYI

bugg@tomsdevbox:~$ lxc config show t1
name: t1
profiles:
- default
config:
  volatile.base_image:
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
  volatile.eth0.hwaddr: 00:16:3e:94:d5:66
  volatile.last_state.idmap:
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
  volatile.lo.hwaddr: 00:16:3e:d2:98:62
devices:
  root:
path: /
type: disk
ephemeral: false


juju bootstrap now seems to run fine without remounting the kernel debug.

Thanks for your help!

Tom


--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 February 2016 at 21:45, Serge E. Hallyn  wrote:

> On Mon, Feb 29, 2016 at 09:45:14AM +, Tom Barber wrote:
> > Hi Serge
> >
> > I rebooted the host to see what happened and the lxc images that were
> > running fine all now have broken SSHD. This, to make absolutely clear
> > doesn't affect the Xenial image, just the trusty one I test with.
> >
> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
> > Creating fix-server2
> > Starting fix-server2
> >
> > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
> > root@fix-server2:~# ps aux |grep ssh
> > root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00 grep
> > --color=auto ssh
> >
> > exit
> >
> > umount and remount kernel debug
> >
> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
> > Creating fix-server3
> > Starting fix-server3
> > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
> > root@fix-server3:~# ps aux |grep ssh
> > root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
> > /usr/sbin/sshd -D
> > root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00 grep
> > --color=auto ssh
>
> If you pull a fresh image using
>
> lxd-images import ubuntu --alias newtrusty trusty amd64
>
> and launch that
>
> lxc launch newtrusty t1
>
> does it have the same failure?
>
> What does
>
> lxc config show fix-server2 show?
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bitnami wordpress charm development

[José Antonio Rey]

This is because you are using Windows line breaks instead of Linux/Unix 
line breaks. Try saving your file with Linux/Unix line breaks and give 
it a go.


On 02/29/2016 05:12 PM, David Britton wrote:

On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:


But I keep having erros with the install hook. It says file not found.



Maybe I missed it in the tarball -- could you attach a juju debug-log
capture while you deploy it?

Or, /var/log/all-machines.log from the bootstrap node is the same thing.

Thanks!



--
José Antonio Rey

--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bitnami wordpress charm development

[David Britton]

On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
> 
> But I keep having erros with the install hook. It says file not found.
> 

Maybe I missed it in the tarball -- could you attach a juju debug-log
capture while you deploy it?

Or, /var/log/all-machines.log from the bootstrap node is the same thing.

Thanks!

-- 
David Britton 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Serge E. Hallyn]

On Mon, Feb 29, 2016 at 09:45:14AM +, Tom Barber wrote:
> Hi Serge
> 
> I rebooted the host to see what happened and the lxc images that were
> running fine all now have broken SSHD. This, to make absolutely clear
> doesn't affect the Xenial image, just the trusty one I test with.
> 
> bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
> Creating fix-server2
> Starting fix-server2
> 
> bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
> root@fix-server2:~# ps aux |grep ssh
> root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00 grep
> --color=auto ssh
> 
> exit
> 
> umount and remount kernel debug
>
> bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
> Creating fix-server3
> Starting fix-server3
> bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
> root@fix-server3:~# ps aux |grep ssh
> root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
> /usr/sbin/sshd -D
> root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00 grep
> --color=auto ssh

If you pull a fresh image using

lxd-images import ubuntu --alias newtrusty trusty amd64

and launch that

lxc launch newtrusty t1

does it have the same failure?

What does

lxc config show fix-server2 show?

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Serge E. Hallyn]

On Sat, Feb 27, 2016 at 11:42:51PM +, Tom Barber wrote:
> Okay I think I worked it out, but i dont' cause the cause in reality:
> 
> in upstart mountall was failing during the boot of the containers
> 
> so I did:
> 
> root@tomsdevbox ~ # umount /sys/kernel/debug
> root@tomsdevbox ~ # mount -t debugfs none /sys/kernel/debug

Is this on the host (vm, whatever), or in the container?

What does /proc/self/mountinfo show before and after the
remount?

-serge

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: juju.worker.dependency engine.go:304 failed to start "uniter" manifold worker: dependency not available

[David Britton]

On Sat, Feb 27, 2016 at 12:12:24PM +0100, Stian Aurdal wrote:
> Hello,
> 
> Im having some errors while trying to deploy landscape on a KVM using the 
> openstack-install autopilot. I have an issue going at 
> https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/870
>  
> 
> 
> but we found some juju warnings we did not understand:
> unit-haproxy-0[891]: 2016-02-26 19:58:58 WARNING juju.worker.dependency 
> engine.go:304 failed to start "uniter" manifold worker: dependency not 
> available
> Any help much appreciated. 
> 

Hi Stian --

We've encountered this error before too. Could you add your findings to
this bug?  There are a couple workaround you can try there.

https://bugs.launchpad.net/juju-core/+bug/1513667

Thanks!

-- 
David Britton 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] apache2, cassandra, haproxy, ibm-java-sdk, midonet-gateway

[Cory Johns]

Hello all.  The Big Data Team (myself, Kevin, Andrew, and Kostas) spent
some time last week on the review queue:

Feb 25, 2016: Andrew/Cory/Kevin/Kostas

   -

   apache2 (add apt config options)
   -


  
https://code.launchpad.net/~evarlast/charms/trusty/apache2/trunk/+merge/278220
  -

  This feature has been plagued with unrelated apache test failures for
  a while now.  These have all been resolved!
  -

  The latest updates merged cleanly, tests passed, and we verified apt
  config settings are working as expected.
  -

  +1, merged.
  -

   cassandra (thrift)
   -


  
https://code.launchpad.net/~stub/charms/trusty/cassandra/ensure-thrift/+merge/279869
  -

  This merged, but the change in how the config option is handled
  created issues with other charms depending on this one, which also had to
  be reviewed and merged as well:
  -


 
https://code.launchpad.net/~celebdor/charms/trusty/midonet-api/cassandra/+merge/287334
 -


 
https://code.launchpad.net/~celebdor/charms/trusty/neutron-agents-midonet/cassandra/+merge/287336
 -


 
https://code.launchpad.net/~celebdor/charms/trusty/midonet-agent/cassandra/+merge/287338
 -

   haproxy-updates
   -


  
https://code.launchpad.net/~jacekn/charms/precise/haproxy/haproxy-updates/+merge/272559
  -

  The previous comments refer to broken tests which now all pass first
  run, Approved.
  -

   ibm-java-sdk
   -

  https://bugs.launchpad.net/charms/+bug/1477067
  -

  Provided some small suggested improvements via a MR
  -

   midonet-gateway
   -

  https://bugs.launchpad.net/charms/+bug/1541735
  -

  The charm did not include any tests. There was no clear way to deploy
  the charm using only information from the readme file. There was no
  description on how to see the effects of the charm after deployment.
  - We asked the author to address the above points. We cannot move on
  with this charm at the moment.
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Logging into the API on Juju 2.0

[Adam Stokes]

Is there a way to list all models for a specific controller?

https://godoc.org/github.com/juju/juju/api/controller and
https://godoc.org/github.com/juju/juju/api/modelmanager seem to do the same
thing wrt listing models. This also only does it for whatever the current
controller is set to before making the api call. I also don't see a way to
list all active controllers, is there a way to do that as well?

I also think the API is a bit confusing when it comes to distinguishing
between a Controller and its Models. There are at least 2 places in the api
that call out to listing models:

https://github.com/juju/juju/blob/master/api/controller/controller.go#L35
https://github.com/juju/juju/blob/master/api/modelmanager/modelmanager.go#L78

And there are other areas where you create a model via modelmanager but can
only gather information about a model via the client, why not just put all
model related api code under modelmanager?


On Fri, Feb 26, 2016 at 9:02 PM, Adam Stokes 
wrote:

> 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
>> controller
>> you bootstrap yourself are local to that controller.
>>
>> On 27/02/16 11:29, Adam Stokes wrote:
>> > 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:
>> >>
>> >>> 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 <
>> adam.sto...@canonical.com>
>> >>> wrote:
>> >>>
>>  Currently, the only way to login to the Juju 2.0 api is to use the
>> Tag
>>  of 'user-admin'.
>> 
>> >>>
>> >> You can log in with additional users. With the CLI, you can do:
>> >>   - juju add-user bob
>> >>   - juju change-user-password bob
>> >>   - juju switch-user bob
>> >> (or you could use the "register" command to add another controller
>> entry;
>> >> you'll still end up with the "bob" user)
>> >>
>> >> 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.
>> 
>> >>>
>> >> "admin" is equivalent to "admin@local"; the latter form is canonical.
>> >> What you're passing over the API is a different form altogether: it is
>> a
>> >> "tag". The tag form of a user is: user-[@domain].
>> >>
>> >> So for the "admin@local" user, the tag form is "user-admin@local". You
>> >> can also supply just "user-admin", and the "local" is implied.
>> >>
>> >> When will the API login support logging in as the admin user for the
>>  specified controller?
>> 
>>  An example of the request being passed to the api server:
>> 
>>  {'Type': 'Admin',
>>   'Version': 3,
>>   'Request': 'Login',
>>   'RequestId': 1,
>>   'Params': {'auth-tag': user,
>> 'credentials': password}}
>> 
>>  user = 'user-admin' and not 'admin@local' as seen in the yaml
>> configs.
>> 
>> >>>
>> >> That should be working. Please file a bug if it's not, with steps to
>> >> reproduce.
>> >>
>> >> Cheers,
>> >> Andrew
>> >>
>> >
>> >
>> >
>>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Semver instead of revisions for charms?

[Rick Harding]

Thanks for the feedback Patrik and Stuart, I've added a note to look at the
gateway revisions to our next set of discussions.

On Mon, Feb 29, 2016 at 7:00 AM Mark Shuttleworth  wrote:

>
> The approach we are discussing in the snappy world is to use "gateway"
> revisions, which are both forward and backward compatible, which encode
> the transition logic. They essentially handle the difficult upgrade, and
> enable subsequent revisions to drop support for the older schemes.
> Upgrades would then be guaranteed to go through those gateway revisions
> (i.e. from rev-current to rev-stable via a series of rev-gateways). If
> this sounds useful we could plan for the same approach in charms.
>
> Mark
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Semver instead of revisions for charms?

[Mark Shuttleworth]

The approach we are discussing in the snappy world is to use "gateway"
revisions, which are both forward and backward compatible, which encode
the transition logic. They essentially handle the difficult upgrade, and
enable subsequent revisions to drop support for the older schemes.
Upgrades would then be guaranteed to go through those gateway revisions
(i.e. from rev-current to rev-stable via a series of rev-gateways). If
this sounds useful we could plan for the same approach in charms.

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: LXD Bootstrap

[Tom Barber]

Hi Serge

I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.

bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
Creating fix-server2
Starting fix-server2

bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
root@fix-server2:~# ps aux |grep ssh
root  1597  0.0  0.0   8868   660 ?S+   09:41   0:00 grep
--color=auto ssh

exit

umount and remount kernel debug


bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
Creating fix-server3
Starting fix-server3
bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
root@fix-server3:~# ps aux |grep ssh
root  1759  0.0  0.0  61380  3816 ?Ss   09:42   0:00
/usr/sbin/sshd -D
root  1944  0.0  0.0   8868   604 ?S+   09:43   0:00 grep
--color=auto ssh


bugg@tomsdevbox:~$ lxc-config -l
lxc.default_config
lxc.lxcpath
lxc.bdev.lvm.vg
lxc.bdev.lvm.thin_pool
lxc.bdev.zfs.root
lxc.cgroup.use
lxc.cgroup.pattern


Cheers

Tom



--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 29 February 2016 at 07:57, Serge E. Hallyn  wrote:

> Hi Tom,
>
> can you reproduce this with lxd alone?
>
> What does 'lxc config show tomsdevbox' show?
>
> -serge
>
> On Sat, Feb 27, 2016 at 11:42:51PM +, Tom Barber wrote:
> > Okay I think I worked it out, but i dont' cause the cause in reality:
> >
> > in upstart mountall was failing during the boot of the containers
> >
> > so I did:
> >
> > root@tomsdevbox ~ # umount /sys/kernel/debug
> > root@tomsdevbox ~ # mount -t debugfs none /sys/kernel/debug
> >
> >
> > and suddenly trusty images started booting..
> >
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > goal, but you can always help by sponsoring the project
> > )
> >
> > On 27 February 2016 at 22:26, Tom Barber 
> wrote:
> >
> > > Also, right on boot, like the moment the image spins up if I force the
> > > runlevel to 5, then the node gets bootstrapped without issue. So it is
> > > something to do with:
> > > https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337 or similar,
> > > just with a Xenial host.
> > >
> > > --
> > >
> > > Director Meteorite.bi - Saiku Analytics Founder
> > > Tel: +44(0)5603641316
> > >
> > > (Thanks to the Saiku community we reached our Kickstart
> > > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > > goal, but you can always help by sponsoring the project
> > > )
> > >
> > > On 27 February 2016 at 22:11, Tom Barber 
> wrote:
> > >
> > >> Okay trusty images are failing for me because upstart borks and I get
> > >> dumped into runlevel unknown.
> > >>
> > >> Serge might have an idea as he was involved in a similar bug issue a
> > >> while ago on launchpad
> > >>
> > >> --
> > >>
> > >> Director Meteorite.bi - Saiku Analytics Founder
> > >> Tel: +44(0)5603641316
> > >>
> > >> (Thanks to the Saiku community we reached our Kickstart
> > >> <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > >> goal, but you can always help by sponsoring the project
> > >> )
> > >>
> > >> On 27 February 2016 at 16:49, Tom Barber 
> wrote:
> > >>
> > >>> Okay so a summary from IRC investigations with Rick H.
> > >>>
> > >>> I thought yesterday on trusty manual sshd was running, i may have
> been
> > >>> wrong.
> > >>>
> > >>> Xenial image has a running sshd but I can't bootstrap it due to
> missing
> > >>> tools
> > >>>
> > >>> If anyone has a snippet for generating and using tools locally
> instead
> > >>> of from the platform, feel free to share so I can bootstrap a xenial
> node
> > >>> currently its failing with missing tools.
> > >>>
> > >>> Cheers
> > >>>
> > >>> Tom
> > >>>
> > >>> --
> > >>>
> > >>> Director Meteorite.bi - Saiku Analytics Founder
> > >>> Tel: +44(0)5603641316
> > >>>
> > >>> (Thanks to the Saiku community we reached our Kickstart
> > >>> <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > >>> goal, but you can always help by sponsoring the project
> > >>> )
> > >>>
> > >>> On