I think I did remove some of that code, because it wasn't being used and wasn't clear why it was there. Easy enough to put back in.
Cheers, Andrew On Mon, Mar 7, 2016 at 8:40 AM Tim Penhey <tim.pen...@canonical.com> wrote: > Ah yeah... it is mostly coming back to me now. > > I actually have a branch lying around that does most of this. > > Perhaps I should look at it again :-) > > Tim > > On 04/03/16 20:08, 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 <tim.pen...@canonical.com > >>> <mailto:tim.pen...@canonical.com>> 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 <mailto: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
