On 05/ 3/11 10:21 AM, Jan Damborsky wrote:
- it was verified that following configuration screens were displayed: hostname, networking (NIC with 'allowed-address' mandated from global zone was filtered out), timezone, users. System was correctly configured.
Did you test this with the anet resource as well as the net resource? When you say that the NISC and address were filtered out, I assume you mean that the admin wasn't prompted for them. But are the mandated values displayed anywhere?
* interactive configuration of non-global zone (NGZ) with shared IP stack - it was verified that following configuration screens were displayed: hostname, timezone, users System was correctly configured. Known issues: * Since DNS configuration is currently part of networking screens, DNS can't be configured in non-global zone with shared IP stack. That will be adjusted (if needed) after naming services screens are separated as a result of enhancing SCI tool with support for NIS and LDAP naming services (CR7031613). * SCI tool does not support all permutations of configuration screens (e.g. configuring just user/root account does not currently work). In order to support that, SCI code will need to be refactored. It will be addressed as separate issue, since it does not affect supported zones scenarios.
When an SC profile is provided by the administrator prior to first boot, are there any SCI screens displayed? Does the answer depend on the contents of the profile?
I have zoneconfig files and SC profiles that I'd like to test. These are both generated by the txzonemgr shell script. What is the best way for these to get tested prior to the integration into snv 167?
--Glenn _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
