Jan Damborsky <Jan.Damborsky at Sun.COM> writes:
>> If configuring multiple user accounts turns out to be required, how would
>> this be accommodated? Multiple user_account_xx property groups?
>
> To be honest, I initially haven't thought about this possibility,
> but it could be addressed as you propose.
In addition, I'd request the opposite possibility: not to create a local
non-root account. Since it will be possible to configure root as a
normal account instead of a role, it is a matter of site policy if a
local user is need/desired. This shouldn't be enforced, though perhaps
recommended.
>> What about providing for an alternate path to the user's home directory?
>
> I was not sure if there is a need for this and if there might be a
> potential issue when we would like to provide user with mechanism
> to specify name of ZFS dataset, since home dir is to be created on shared
> ZFS dataset and name of target root pool might not be known at the time
> System Configuration manifest is constructed.
>
> If we would like to allow the user only to customize ZFS mountpoint of
> <root_pool>/export/home/<login> ZFS dataset, I think that should be fine.
>
> If not specified or set to '' (e.g. in SC portion in default AI manifest),
> it would expand to /export/home/<login> as it does today.
>
> Do you think it could cover the user's needs or there might be also need
> to customize name of ZFS dataset ?
I think this is required: there may be site policy on dataset naming in
place, and forcing something else down the throat of users would be a
mistake. There's even more need for configurability here (though not
this spec, but related): I've just filed
15307 AI root pool datasets should be more configurable
to handle the rool pool and initial BE names.
Apart from that, the spec looks fine, thanks for doing this.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
