On 09/25/10 12:31 AM, Dave Miner wrote:
On 09/20/10 01:30 PM, Jan Damborsky wrote:
Hi Frank,
as you pointed out below, since SCI tool will serve for interactive
configuration of non-global
zones and for system configuration during text installation, we are
mostly targeting sys admins
residing in enterprise world and we can assume high level of technical
skills.
I agree with you that it is reasonable to provide screens for
configuration of parameters which
are likely to be frequently configured when deploying non-global zone.
At this point, in addition what we already provide in text installer, we
think about following
parameters:
[1] Manual networking configuration
- IPv4 address, netmask, default route for one network interface
As far as IPv6 is concerned, I have looked at what legacy sysid tools
provide
and they only allow to enable/disable IPv6 support for already
configured IPv4
interface.
We could certainly provide at least that, but we can provide for more if
needed,
as PSARC/2010/164 allows better control. We can configure
* static address or addrconf type of configuration as described in
ipadm(1M) man page
* in case of addrconf, stateless & stateful IPv6 parameters as described
in ipadm(1M) man page
* default IPv6 route
Please work out design that includes all of the IPv6 options above,
without any dependency on also configuring IPv4 on the interface. We
are likely to need it sooner rather than later, so I think it makes
sense to implement IPv6 configuration options at this time.
I see. Assuming that IPv4 and IPv6 are treated separately, I think we need
to work out UI which will provide user with possibility to configure one
of possible scenarios:
- configure one IPv4 NIC
- configure one IPv6 NIC
- configure one IPv4 and on IPv6 NIC (NICs might be the same or different)
As there might be various approaches to accomplish this, we will work
with Frank
on correct way to do that.
Then if user wants to set up IPv6, one will need to specify following:
[1] name of IPv6 NIC (could be perhaps skipped if there is only one NIC)
[2] IPv6 configuration mechanism (required)
'static' or 'auto configuration'
Then for 'static' case only:
[3] IPv6 address (required)
[4] prefix length (optional)
And for 'auto configuration case' only:
[3] Interface ID (optional, default is MAC address)
[4a] stateless configuration - 'yes' or 'no' (default would be 'yes')
[4b] stateful configuration - 'yes' or 'no' (default would be 'yes')
Common to both:
[5] IPv6 default route (optional)
We will work with Frank on how it might map to SysConfig screens.
[2] DNS (when manual networking configuration is selected)
Legacy sysid tools provide three screens for configuring DNS:
* domain name
* nameservers (max three)
* search domains (max six)
I think we should provide the same level of configuration.
In configuring DNS, domain and search are mutually exclusive, last
listed in resolv.conf taking precedence. My recommendation would be
to dispense with domain name and merely use the more flexible domain
search list.
That sounds reasonable. It will simplify SysConfig UI.
Thank you very much,
Jan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
