Re: admin is dead, long live $USER

[John Meinel]

We ssh into the machine to finish setting it up. I don't think we use
cloud-init much for the initial machine. That way we can set up secret
passwords, etc.

John
=:->
On Mar 4, 2016 11:09 AM, "Ian Booth"  wrote:

> Hey Tim
>
> The new bootstrap UX has not removed any --admin-user flag.
> I can see that the server jujud bootstrap command has an --admin-user
> argument
> but it appears this is never set anywhere in the cloud init scripts. Or
> not that
> I can see. I've checked older version of the relevant files and can't see
> where
> we've ever used this.
>
> So maybe we have a capability to bootstrap the controller agent with a
> specified
> admin-user but have not hooked it up yet?
>
> On 04/03/16 08:11, Tim Penhey wrote:
> > Ah... it used to be there :-) At least it is on my feature branch, but I
> > don't think I have merged the most recent master updates that has the
> > work to re-work bootstrap for the new cloud credentials stuff.
> >
> > Tim
> >
> > On 04/03/16 10:09, Rick Harding wrote:
> >> If we do that we need to also make it configurable on bootstrap as an
> >> option.
> >>
> >> +1 overall
> >>
> >>
> >> On Thu, Mar 3, 2016, 4:07 PM Tim Penhey  >> > wrote:
> >>
> >> Hi folks,
> >>
> >> I was thinking that with the upcoming big changes with 2.0, we
> should
> >> tackle a long held issue where we have the initial user called
> "admin".
> >>
> >> There was a request some time back that we should use the current
> user's
> >> name. The reason it wasn't implemented at that time was due to
> logging
> >> into the GUI issues. These have been resolved some time back with
> the
> >> multiple user support that was added.
> >>
> >> All the server side code handles the ability to define the initial
> user
> >> for the controller model, and we do this in all the tests, so the
> >> default test user is actually called "test-admin".
> >>
> >> I *think* that all we need to do is change the default value we use
> in
> >> the bootstrap command for the AdminUserName (--admin-user flag) from
> >> "admin" to something we derive from the current user.
> >>
> >> Probably worth doing now.
> >>
> >> Thoughts?
> >>
> >> Tim
> >>
> >> --
> >> Juju-dev mailing list
> >> Juju-dev@lists.ubuntu.com 
> >> Modify settings or unsubscribe at:
> >> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> >>
> >
> >
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: admin is dead, long live $USER

[Ian Booth]

Hey Tim

The new bootstrap UX has not removed any --admin-user flag.
I can see that the server jujud bootstrap command has an --admin-user argument
but it appears this is never set anywhere in the cloud init scripts. Or not that
I can see. I've checked older version of the relevant files and can't see where
we've ever used this.

So maybe we have a capability to bootstrap the controller agent with a specified
admin-user but have not hooked it up yet?

On 04/03/16 08:11, Tim Penhey wrote:
> Ah... it used to be there :-) At least it is on my feature branch, but I
> don't think I have merged the most recent master updates that has the
> work to re-work bootstrap for the new cloud credentials stuff.
> 
> Tim
> 
> On 04/03/16 10:09, Rick Harding wrote:
>> If we do that we need to also make it configurable on bootstrap as an
>> option.
>>
>> +1 overall
>>
>>
>> On Thu, Mar 3, 2016, 4:07 PM Tim Penhey > > wrote:
>>
>> Hi folks,
>>
>> I was thinking that with the upcoming big changes with 2.0, we should
>> tackle a long held issue where we have the initial user called "admin".
>>
>> There was a request some time back that we should use the current user's
>> name. The reason it wasn't implemented at that time was due to logging
>> into the GUI issues. These have been resolved some time back with the
>> multiple user support that was added.
>>
>> All the server side code handles the ability to define the initial user
>> for the controller model, and we do this in all the tests, so the
>> default test user is actually called "test-admin".
>>
>> I *think* that all we need to do is change the default value we use in
>> the bootstrap command for the AdminUserName (--admin-user flag) from
>> "admin" to something we derive from the current user.
>>
>> Probably worth doing now.
>>
>> Thoughts?
>>
>> Tim
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com 
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
> 
> 

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

Juju 2.0 and local charm deployment

[Ian Booth]

Hi folks

TL;DR we want to remove support for old style local charm repositories in Juju 
2.0

Hopefully everyone is aware that Juju 2.0 and the charm store will support
multi-series charms. To recap, a multi-series charm is one which can declare
that it supports more than just the one series; you no longer need to have a
separate copy of the charm for precise vs trusty vs xenial. Note that all series
must be for the same OS so you'll still need separate charm sources for Windows
vs Ubuntu vs Centos.

Here's a link to the release notes
https://jujucharms.com/docs/devel/temp-release-notes#multi-series-charms

Juju 2.0 will also support deploying bundles natively
https://jujucharms.com/docs/devel/temp-release-notes#native-support-for-charm-bundles

So, with multi-series charm support, local charm deployment is now also a lot
easier. Back in Juju 1.x, to deploy local charms you needed to set up a
so-called charm repository, with a proscribed directory layout. The directory
layout has one directory per series.

_ mycharms
 |_precise
  |_mysql
 |_trusty
  |_mysql
 |_bundle
  |_openstack

You deployed using a local URL syntax:

$ juju deploy --repository ~/mycharms local:trusty/mysql

$ juju deploy --repository ~/mycharms local:bundle/openstack

The above structure was fine for when charms were duplicated for each series.
But one of the limitations is that you can't easily git checkout mycharm and
deploy straight from the vcs source on disk.

Juju 2.0 supports deploying charms and bundles straight from any directory,
including where you've checked out your launchpad/github charm source.

$ juju deploy ~/mygithubstuff/mysql

$ juju deploy ~/mygithubstuff/openstack/bundle.yaml

So the above combined with the consolidation of charms for many series into the
one source tree means that the old local repo support is not needed.

Will anyone complain if we drop local repos in Juju 2.0? Is there a use case
where it's absolutely required to retain this?






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

Re: admin is dead, long live $USER

[Tim Penhey]

Ah... it used to be there :-) At least it is on my feature branch, but I
don't think I have merged the most recent master updates that has the
work to re-work bootstrap for the new cloud credentials stuff.

Tim

On 04/03/16 10:09, Rick Harding wrote:
> If we do that we need to also make it configurable on bootstrap as an
> option.
> 
> +1 overall
> 
> 
> On Thu, Mar 3, 2016, 4:07 PM Tim Penhey  > wrote:
> 
> Hi folks,
> 
> I was thinking that with the upcoming big changes with 2.0, we should
> tackle a long held issue where we have the initial user called "admin".
> 
> There was a request some time back that we should use the current user's
> name. The reason it wasn't implemented at that time was due to logging
> into the GUI issues. These have been resolved some time back with the
> multiple user support that was added.
> 
> All the server side code handles the ability to define the initial user
> for the controller model, and we do this in all the tests, so the
> default test user is actually called "test-admin".
> 
> I *think* that all we need to do is change the default value we use in
> the bootstrap command for the AdminUserName (--admin-user flag) from
> "admin" to something we derive from the current user.
> 
> Probably worth doing now.
> 
> Thoughts?
> 
> Tim
> 
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com 
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> 


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

Re: admin is dead, long live $USER

[Rick Harding]

If we do that we need to also make it configurable on bootstrap as an
option.

+1 overall

On Thu, Mar 3, 2016, 4:07 PM Tim Penhey  wrote:

> Hi folks,
>
> I was thinking that with the upcoming big changes with 2.0, we should
> tackle a long held issue where we have the initial user called "admin".
>
> There was a request some time back that we should use the current user's
> name. The reason it wasn't implemented at that time was due to logging
> into the GUI issues. These have been resolved some time back with the
> multiple user support that was added.
>
> All the server side code handles the ability to define the initial user
> for the controller model, and we do this in all the tests, so the
> default test user is actually called "test-admin".
>
> I *think* that all we need to do is change the default value we use in
> the bootstrap command for the AdminUserName (--admin-user flag) from
> "admin" to something we derive from the current user.
>
> Probably worth doing now.
>
> Thoughts?
>
> Tim
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

admin is dead, long live $USER

[Tim Penhey]

Hi folks,

I was thinking that with the upcoming big changes with 2.0, we should
tackle a long held issue where we have the initial user called "admin".

There was a request some time back that we should use the current user's
name. The reason it wasn't implemented at that time was due to logging
into the GUI issues. These have been resolved some time back with the
multiple user support that was added.

All the server side code handles the ability to define the initial user
for the controller model, and we do this in all the tests, so the
default test user is actually called "test-admin".

I *think* that all we need to do is change the default value we use in
the bootstrap command for the AdminUserName (--admin-user flag) from
"admin" to something we derive from the current user.

Probably worth doing now.

Thoughts?

Tim

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