Hi Glenn,
thank you very much for looking at this.
Please see my response in line.
Jan
On 05/ 3/11 09:46 PM, Glenn Faden wrote:
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?
I assume you mean combination of NICs with and without 'allowed-address'
mandated from global zone ?
If my assumption is correct, then yes, I configured zone with
one 'allowed-address' specified NIC and one without that.
I verified that on NIC configuration screen, user was provided only
with NIC w/o 'allowed-address' mandated from global zone.
Please let me know if my understanding is correct.
When you say that the NISC and address were filtered out, I assume you
mean that the admin wasn't prompted for them.
Yes, that is correct.
But are the mandated values displayed anywhere?
No, this information is currently not presented to the user.
I can see it would be nice to have that information presented
to user, though the problem is that would require more invasive
changes in User Interface which should be consulted with UI guys.
Given the lack of resources and the fact that this already targets
one of late binding builds (LB request has been recently approved),
if we think it is more SHOULD-HAVE rather than MUST-HAVE, then
I would like to address that as a separate RFE.
Please let me know if it's acceptable.
* 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?
It depends on what that profile contains.
In general, SCI tool is displayed only if following boolean type
smf properties of system/config smf service are set to following values:
configuration/configure = true
configuration/interactive_config = true
Those properties could be set via smf profile.
So to answer your question, if those properties are defined in a profile
which administrator supplies, then yes, SCI tool is invoked.
If those properties are not defined in supplied SC profile,
then SCI tool is not displayed regardless of what that
profile configures.
Does the answer depend on the contents of the profile?
Yes, please see above.
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?
Let me describe steps which I currently use to test new
SC within zones.
* install zone via 'zoneadm install'
* install additional necessary packages:
- system/install/configuration - contains new SC framework
- security/sudo - needed if we want to utilize sudo for initial user
account
created by new SysConfig
Starting build 165, this step is no longer necessary, as Susan pushed
those changes into zones code
* deactivate legacy SC framework
# rm <zone_root>/etc/.UNCONFIGURED
* drop SC profile into <zone_root>/etc/svc/profile/site/ directory
* boot the zone
* pray (not mandatory, but sometimes it seems to help)
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
