From sac-owner Tue Aug 19 10:42:35 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7JHgZF1019314 for ; Tue, 19 Aug 2008 10:42:35 -0700 (PDT) Received: from sunmail2sca.sfbay.sun.com (localhost [127.0.0.1]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m7JHgZ3M013982 for ; Tue, 19 Aug 2008 10:42:35 -0700 (PDT) Received: (from noaccess@localhost) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/Submit) id m7JHgZxu013976 for one-pager-not-2b-used-directly; Tue, 19 Aug 2008 10:42:35 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m7JHgXIh013945 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Tue, 19 Aug 2008 10:42:34 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5U0050LZUWFV00@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Tue, 19 Aug 2008 10:42:32 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5U00HHVZUV1R70@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Tue, 19 Aug 2008 10:42:32 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com (localhost [127.0.0.1]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m7JHgVdQ005524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Aug 2008 10:42:31 -0700 (PDT) Received: (from okie@localhost) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3/Submit) id m7JHgVDS005523 for one-pager@sun.com; Tue, 19 Aug 2008 10:42:31 -0700 (PDT) Date: Tue, 19 Aug 2008 10:42:31 -0700 From: Renee Danson Subject: [2008/532]NWAM Phase 1 To: one-pager@Sun.Com Message-id: <20080819174231.GB1910@jurassic-x4600.Eng.Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 X-Authentication-warning: jurassic-x4600.sfbay.sun.com: okie set sender to renee.danson@sun.com using -f User-Agent: Mutt/1.5.17 (2007-11-01) Status: RO Content-Length: 6509 Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Network Auto-Magic (NWAM) Phase 1 1.2. Name of Document Author/Supplier: Renee Danson 1.3. Date of This Document: 19-Aug-2008 1.3.1. Date this project was conceived: 15-Jan-2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Bill Franklin 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: victor.nelson@sun.com 1.5.2. Responsible Engineer: renee.danson@sun.com 1.5.3. Marketing Manager: jeff.mcmeekin@sun.com 1.5.4. Interest List: nwam-discuss@opensolaris.org 2. Project Summary 2.1. Project Description: A project to simplify and automate basic network configuration. 2.2. Risks and Assumptions: * This project has components that will live in two different consolidations: daemons, library, and CLI in ON, and GUI in Desktop. Timing of two separate putbacks must be coordinated. We are working closely with the desktop team in order to manage the cross-consolidation dependencies. 3. Business Summary 3.1. Problem Area: Network configuration on Solaris has always been complex, but does not need to be. This project will allow boxes to be automatically configured for the most part and will allow for more complex configurations to be simplified. This phase of the project specifically addresses basic ethernet and wifi configurations, and system-wide configuration profiles. 3.2. Market/Requester: Any Solaris user configuring or managing networking, especially developers and people installing Solaris for the first time. 3.3. Business Justification: Solaris network configuration continues to increase in complexity. This has become a significant barrier to entry for developer desktop and small business environments. These environments lack dedicated system/network administrators and have high expectations around ease-of-use for configuration and management. 3.4. Competitive Analysis: Microsoft, Apple & Red Hat Linux: we are behind; this catches us up, and in some areas puts us ahead. 3.5. Opportunity Window/Exposure: We're behind: we need to catch up ASAP. 3.6. How will you know when you are done?: * The NWAM GUI and CLI can be used to create profiles of both basic network (layer 2-3) configurations and system-wide network configuration attributes. * Profiles can be activated/deactivated automatically by the system depending on network conditions. 4. Technical Description: 4.1. Details: This case defines Phase 1 of the Network Auto-Magic project described in 2007/307. New features introduced in this phase will be: * profile support (automatically updating multiple system attributes when the underlying network conditions change) * a CLI * a GUI 4.2. Bug/RFE Number(s): The list is long; it will be included with the project materials. 4.3. In Scope: Configuration of "simple" network links and interfaces: IP plumbed on physical devices and tunnels; and system-wide network-related configuration (e.g. name services, security policy). 4.4. Out of Scope: Configuration of vlans, aggregations, vnics, IPMP groups. 4.5. Interfaces: * GUI: http://opensolaris.org/os/project/nwam/UIDesign/Phase1/ * CLI: http://opensolaris.org/os/project/nwam/p1spec/ui/CLI/ * libnwam interfaces (table TBD; interfaces defined in http://opensolaris.org/os/project/nwam/p1spec/API/) * libinetcfg extensions (table TBD) 4.6. Doc Impact: * man pages: netcfgd(1M), nwamd(1M), libnwam(3LIB) * docs: System Administration Guide, IP Services: new chapter for the CLI and troubleshooting. * help docs: a help system to go along with the GUI * Getting Started With OpenSolaris * Student System Admin Guide for School Kit 4.7. Admin/Config Impact: New GUI to configure/administer networking, new CLI to do the same. The need to use ifconfig(1M) et al. will be greatly reduced. Other disparate UIs will be coalesced. Elimination of /etc/hostname.{if} and /etc/dhcp.{if} files when using NWAM. 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: No impact per se, just some new messages to be translated as part of the ON and Desktop catalogs. 4.10. Packaging & Delivery: SUNWcsr will be modified. Install/upgrade are affected in that they will want to interact property with the new methodology; we are in touch with the appropriate I-teams. For the GUI components, which will be part of the Desktop consolidation, the SUNWgnome-nwam-manager-root and SUNWgnome-nwam-manager packages will be modified. 4.11. Security Impact: This does not impact any security-related APIs. Our daemons will be privilege aware. No new ports will be involved. 4.12. Dependencies: * PSARC 2008/473 Fine-Grained Privileges for Datalink Administration 5. Reference Documents: Overall NWAM Design doc: http://opensolaris.org/os/project/nwam/design/ Phase 1 Specification: http://opensolaris.org/os/project/nwam/p1spec/ 6. Resources and Schedule: 6.1. Projected Availability: Q3 FY09 6.2. Cost of Effort: Development: 56 engineer-months (4 eng * 14 months) GUI Development: 22 engineer-months (2 eng * 8 months + 1 HCI eng * 6 months) Test Development: 9 engineer-months (3 eng * 3 months) GUI Test Development: 2 engineer-months GUI Testing: 3 engineer-months Docs: 3 writer-months (1 writer * 3 months) 6.3. Cost of Capital Resources: No additional resources needed. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: ON, JDS 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: TBD 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: snv_110 6.4.8. Target Code Design Review Date: Jan 2009 6.4.9. Update approval addition: Nevada only, *not* targeting a Solaris 10 update. 6.5. ARC review type: Standard 6.6. ARC Exposure: open 7. Prototype Availability: 7.1. Prototype Availability: n/a 7.2. Prototype Cost: n/a