NWAM West: 8:30AM MPK/11:30AM BUR/4:30PM DUB Attendees: Alan, Anurag, Darren, Michael, Renee
1. Phase 1 development status: see task wiki at http://wikis.sun.com/display/NWAM/P1+Dev+Task+Status. 2. Project admin issues * PSARC: target 3/11 or 3/18 for commitment review. Means docs need to be ready by 3/4 (for 3/11 review) or 3/11 (for 3/18 review). One issue is with contracted interfaces needed by the GUI; those need to be nailed down and documented. * OpenSolaris installs for testing: Michael has a script that packages up nwam-related binaries from a proto area, and then copies them into place on a target system. With some updates to deal with the new users and permission changes, we should be able to use this to install the ON bits for test purposes. For the desktop bits, Darren will be able to give us a repo to update from. * Anurag suggested that mapping the original story boards to NCP/Location configs, as a way of documenting phase 1. 3. Development issues * The Name Services saga We can't seem to wrap this one up. Our current domain-property-per-ns strategy doesn't work, as NIS and LDAP both use the common system domain, as reported by the domainname(1M) command; they can't have different domain values. There are also other things that consume that domain value. The DNS-specific setting is the outlier. So, we'll have one location property, default_domain, that specifies the system domain. Those subsystems that have their own notion of domain (DNS, NFS) will have their own domain properties, dns_nameservice_domain and nfs_domain. * Check-conditions and domain values: there's also some confusion around the domain value when it's used as a conditional for profile activation. If it's a conditional for location activation, what we really mean is "the dhcp-server-specified domain value for the network to which we've connected"; if it's a conditional for enm activation, what is most likely meant is "the domain set on this system". So the conditionals need to be updated, allowing you to specify "advertised_domain" or "system_domain" as two different attributes, replace the one "domainname" attribute. advertised_domain will look at both DNSdmain and NISdmain values received from DHCP servers. * Use of sysevent framework for nwam events: Alan has an implementation using event channels; these work very nicely with one exception: the current implementation requires that both producer and consumer be root. CR 4791900 (which is old, but was very recently accepted) addresses this problem; Renee will track down status on this. * Events: there are some things the user can do via the gui (e.g. selecting a WLAN) that must also be possible via the command line; nwamadm is the right place for these. Alan will work on this. * IPFilter and the recently-integrated firewall project: NWAM locations will only support manual firewall/ipfilter configurations; it will not be possible to use the new firewall setup tool to create firewall settings for a location (that tool was designed to immediately apply config, it can't export settings for later activation). Anurag is working on updates to the way we save/restore the legacy location to take into account the changes to ipfilter configuration. NWAM East: 5:00PM MPK/9:00AM BJS Attendees: Karen, Eric, Alex, Lizhong, John, Renee 1. Test dev moving along; having stable, functional ON bits is the biggest need right now! - Rishi's work on the test driver (simulates different network devices and events) is moving along, but it is dependent on changes in solaris that he's also making. This will make it hard for us to use it (or at least to have test suites that depend on it) prior to its integration. -renee
