Sowmini, On 05/25/10 11:09 AM, [email protected] wrote:
here are updates to the documentation that include the RTF_ZONE related changes, as well as those based on Erik's comments about allowing persistent interface configuration management in the non-global zone.
Thanks for the update, I've set a new timer on the case to expire on 06/02/2010.
One nit below:
--- zonecfg.txt 2010/05/19 19:28:37 1.2 +++ zonecfg.txt 2010/05/25 15:08:12 @@ -79,10 +79,20 @@ other zonecfg(1m) resources such as the "physical" datalink. At the same time, the zone boot process will also ensure 'ip-nospoof' protection for the datalink with the specified addresses used as input to the -'allowed-ips' property. The stored nvlist information for 'address' -and 'defrouter' will be retrieved and re-applied in the non-global zone -by the daemon associated with the ip-interface-management service -before any other IP configuration is applied. +'allowed-ips' property. On the first boot of an installed non-global +zone, the stored nvlist information for 'address' will be retrieved by +the ipmgmtd daemon which will create the interface persistently, and +apply the IP addresses non-persistently before any other IP +configuration is applied. On subsequent boots, any IP interface with +persistent configuration in the ipadm data-store will be recreated using +IP address information from the kernel's nvlists set up by zoneadmd.
The above semantics will be slightly different in solaris10 branded zones since there are no persistent interface objects in such zones. In such zones, I believe it would be sufficient for ipmgmtd to configure everything non-persistently and let the administrator's hostname.<intf> files customize interface parameters appropriately (I believe this should "just work").
-Seb _______________________________________________ opensolaris-arc mailing list [email protected]
