On 07/27/10 06:43 PM, Ethan Quach wrote:
On 07/27/10 08:16, Dave Miner wrote:
On 07/27/10 06:53 AM, Jan Damborsky wrote:
Hi Dave,
thank you very much for your comments.
Please see my response in line.
Jan
On 07/26/10 05:35 PM, Dave Miner wrote:
On 07/26/10 09:26 AM, Jan Damborsky wrote:
Hi Ethan,
could I please ask you for reviewing the changes for following bugs ?
7850 RFE would like support for static network instead of nwam config
10781 RFE - AI Needs to Support DNS Name Service Configuration for
Clients
webrev:
Related ON CRs:
6923163 Automated Install requires mechanism for configuring
static IP
addresses
6923168 Automated Install requires a mechanism for configuring name
services for clients
The install portion of changes is merely about enhancing default
AI manifest (SC portion) with template specifying configuration
of new smf services allowing configuration of static IP and DNS.
I'm a little leery of the default values you've used in the addresses
here, because they're almost certainly invalid.
To be honest, I am not quite sure where the problem is -
could you please be more specific about what should be changed ?
The issue is that the values are unlikely to be correct for any
actual network, but they appear relatively "valid" so some very naive
users may think that they're some sort of magic values that they can
just use. I'd rather not have support dealing with calls like that :-)
I have tried to validate SC portion of default AI manifest using
'svccfg
apply -n'
on build 144 (since this is where support for new smf types
net_address,
net_address_list was introduced) and it succeeded.
Would it make more sense to use invalid values so that this default
configuration can't actually be applied?
I am a little bit confused - do you suggest to use invalid values in
default manifest ?
I assume we want the opposite, otherwise the installation would fail at
the end
during syntactic validation of smf profile.
If the default manifest is set up to use NWAM, then perhaps these
shouldn't be in there unless we change the default, in which case a
failed validation would be the right answer. I'm concerned about
providing a default manifest that mis-configures systems.
As an alternative, could we just provide an additional SC profile with
static IP specified, and document how users can use it?
Hi Ethan,
I like this solution - I introduced additional AI manifest with
SC profile for 'static IP' scenario. Invalid addresses are put there,
so that user is forced to change them - I have updated webrev
accordingly:
http://cr.opensolaris.org/~dambi/bug-7850-cr/
Thank you,
Jan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
