On Tue, Nov 20, 2012 at 11:05 AM, Steve Loughran <[email protected]> wrote: > On 20 November 2012 17:46, Adrian Cole <[email protected]> wrote: > >> I'll agree with you in that policy should be separate from mechanism. If >> running in your laptop or some other env where you feel root is ok >> (policy), whirr should allow this. >> >> At any rate, I'm not sure how intentional this is. You might be bumping >> into a guard that avoids attempts to create a user called root. There is >> probably logic we can change that avoids this. >> > > If it's not by design, then yes, it's fixable yep, by design to not try to create root. not by design to forbid root in general (at least as far as I'm aware).
> > >> >> Also, I doubt that byon forbids declaring the user 'root' in itself. If >> so, please raise a jclouds bug in github. >> >> HTH >> On Nov 20, 2012 8:52 AM, "Steve Loughran" <[email protected]> wrote: >> >> > Why is that root installation is so forbidden that you can't use Whirr >> > against a BYON cluster with whirr.cluster-user=root? >> > >> > I understand why you'd be reluctant to do it in an infrastructure that >> > blocked ssh root@ logins, but for an internal cluster via BYON? It >> seems a >> > bit of overkill >> > >>
