From James.Gates@Sun.COM Thu Feb 5 08:54:22 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n15GsLGb001322 for ; Thu, 5 Feb 2009 08:54:21 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n15GsLsM051105 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 5 Feb 2009 09:54:21 -0700 (MST) 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 <0KEL00M1RQYKPY00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 05 Feb 2009 08:54:20 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEL00B2RQYG9V90@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 05 Feb 2009 08:54:17 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n15GsGZ2001204 for ; Thu, 05 Feb 2009 16:54:16 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEL00E00OCA7X00@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 05 Feb 2009 16:54:16 +0000 (GMT) Received: from [192.168.1.100] ([unknown] [129.150.65.53]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEL00FQ8QXPPEB0@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 05 Feb 2009 16:54:01 +0000 (GMT) Date: Thu, 05 Feb 2009 11:52:52 -0500 From: James Gates Subject: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] Sender: James.Gates@Sun.COM To: lsarc-ext@Sun.COM Cc: Trond Norbye Message-id: <498B1964.8070907@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_bpNgwFl9sZrlUI/Q9P451A)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 23103 This is a multi-part message in MIME format. --Boundary_(ID_bpNgwFl9sZrlUI/Q9P451A) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT I'm sponsoring this case on behalf of Trond Norbye. This is actually a version upgrade as memcached 1.2.5 & libmemcached 0.16 are already integrated info sfwnv. However, the FOSS checklist was not in existence at the time of the original ARC case, and completing it this time for version 1.4.x identifies some areas where an ARC review is required. The main difference between versions 1.2 & 1.4 (other than bug fixes) is the introduction of a new (binary) network communications protocol. There are also proposed changes to the way we implement the SMF service. -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql --Boundary_(ID_bpNgwFl9sZrlUI/Q9P451A) Content-type: text/plain; name=memcached_foss_checklist.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=memcached_foss_checklist.txt FCL--FOSS Check List 0. Introduction 0.1 Document History Version Author Changes Date 0.1 John Fischer Initial Draft 01/11/2008 0.2 John Fischer Modified based upon feedback from ARC members 01/29/2008 0.3 John Fischer Modified based upon feedback during committee 02/12/2008 review 0.4 John Fischer Modified based upon SAC review feedback 04/01/2008 0.5 John Fischer Modified based upon LSARC business meeting 06/10/2008 adding familiarity question and mod dates. 0.6 John Fischer Modified based upon user feedback about 06/20/2008 sections that were unanswerable. 0.2 Purpose Architecture review at Sun has allowed the company to evolve our projects within multiple disjoint groups while still maintaining a cohesive product line. Each architecture review was conducted within Sun's control. With the advent of Free Open Source Software processes the control that Sun as a company can wield has been diminished. Now that Sun is moving to a more fluid delivery mechanism with project Indiana we need to evolve the architecture review process. This document is meant to aid in the architecture review process. Each new project must complete this check list to help ensure that the overall resulting product conforms to Sun product standards. If the project deviates from these standards further review would be necessary by an architecture review committee. After the check list is completed the project team should be able to determine if a project can be automatically approved. This will occur if all checks result in no "ARC review required" answers. A committee member will assist the project team in filing the automatically approved fast track. An automatically approved fast track is still required in order to record the interfaces for future reference. If the project needs to have further review then follow the regular process for getting projects reviewed. 1.0 Project Information 1.1 Name of project/component Memcached 1.2 Author of document Trond Norbye 2.0 Project Summary 2.1 Project Description Upgrade memcached 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [ ] Yes [X] No 2.4 Originating Community 2.4.1 Community Name Memcached 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [X] Contributor [ ] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [N] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [N] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [N] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [X] Yes [ ] No If yes are these components packaged to be shared with the other FOSS? [X] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [X] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [X] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [X] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [X] Yes - ARC review required [ ] No I want to let the user be able to specify a "privileged" port without having to edit the manifest, so I would like to assign PRIV_NET_PRIVADDR. Previously the user _had_ to modify the default SMF configuration to specify a user to run the memcached deamon as (and the service would go to maintenance state if one tried to start it without specifying a user). We would like to modify this behavior and start memcaced as "noaccess" unless another user is specified. During startup Memcached will bind to the port and drop all privileges _before_ it accepts clients, so it is not using any privileges while running. 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [X] Yes [ ] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [X] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [X] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [X] No - ARC review required [ ] N/A When the service is enabled it will accept all connections. no security is enforced. This behavior is unchanged from the ARC case filed for version 1.2.5 (LSARC/2008/126) Is inbound data checked to prevent content-based attacks? [X] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [X] No - ARC review required [ ] N/A This behavior is unchanged from the ARC case filed for version 1.2.5 (LSARC/2008/126) Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [X] No - ARC review required [ ] N/A This behavior is unchanged from the ARC case filed for version 1.2.5 (LSARC/2008/126) 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [X] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [X] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [X] No - ARC review required The text protocol used should be covered by the ARC case filed for version 1.2.5 (LSARC/2008/126) The new binary protocol offers the same capabilites but removes the ambiguity in the text protocol. Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [X] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [X] N/A There is no authentication 3.5 Networking Do the components access the network? [X] Yes [ ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [X] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [X] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ------------------- --------------------------- See section 4.5 in the onepager. 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- Appendix A - References 1. Solaris Installation Locations Policy http://opensolaris.org/os/community/arc/policies/install-locations/ 2. /usr/gnu Installation ARC case http://opensolaris.org/os/community/arc/caselog/2007/047/ 3. Secure By Default Policy http://opensolaris.org/os/community/arc/policies/secure-by-default/ 4. Network Install Time Securityuy Policy http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ 5. Adding RBAC Authorizations Policy http://opensolaris.org/os/community/arc/bestpractices/rbac-auths/ 6. When to use setuid -vs- RBAC roles and profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and 7. Building RBAC Rights Profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ 8. Solaris Audit Policy http://opensolaris.org/os/community/arc/policies/audit-policy/ 9. Security questionaire http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 10. Interface Taxonomy http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ 11. Plugable Authentication Modules -- PAM http://opensolaris.org/os/community/arc/policies/PAM/ 12. Reusable Passwords In Command Line Arguments and Environment Variables http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ 13. Storing Reusable Passwords on a Filesystem http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 14. Release Taxonomy http://opensolaris.org/os/community/arc/policies/release-taxonomy/ 15. Service Management Facility (SMF) usage http://opensolaris.org/os/community/arc/policies/SMF-policy/ Appendix B - Suggested case materials 1. man pages 2. SMF manifests 3. links to contracts Appendix C - Definitions Submitter an agent responsible for creation of an ARC project along with the materials describing that project. Owner the ARC agent responsible for shepherding the case through review and ensuring a formal opinion is written where required. Maintainer an agent responsible for releasing new versions of a program, typically the "main" contributor or person incharge of making Architectural decisions for the project Contributor an agent who make contributions to a project, typically has a voice in making Architectural decisions for the project Monitoring an agent who is only following the changes made in the community and has no Architectural input into the project Volatile* interfaces that are very fluid and typically follow the originating community. Typically these interfaces can not be imported by other projects. Uncommitted* interfaces that are still evolving but will most likely be present from release to release. Committed* interfaces that are stable and with Sun guaranteeing some level of compatibility from release to release. Project Private* interfaces that are exposed only to or intended to be used only by the project being reviewed. These interfaces can not be imported by other projects. Not-An-Interface* components that are not interfaces. Contracted* (interface modifier) - ARC review of Contract required interfaces that do not allow another project to import can be *Note: see http://opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details --Boundary_(ID_bpNgwFl9sZrlUI/Q9P451A) Content-type: text/plain; name=memcached_onepager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=memcached_onepager.txt Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: memcached 1.4.x to be included in OpenSolaris 1.2. Name of Document Author/Supplier: Trond Norbye 1.3. Date of This Document: 12/09/08 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Webstack 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Heidi.Bergh-hoff@sun.com 1.4.4. The name of your business unit: Application Platform Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Heidi.Bergh-Hoff@sun.com 1.5.2. Responsible Engineer: Trond.Norbye@sun.com 1.5.3. Marketing Manager: Jimmy.Guerrero@sun.com 1.5.4. Interest List: memcached-interest@sun.com 2. Project Summary 2.1. Project Description: Update memcached in OpenSolaris from version 1.2.5 to 1.4.x Update libmemcached version 0.16 to 0.2x Add support the binary protocol Refer also ARC case LSARC/2008/126 that added memcached 1.2.5 Refer also ARC case LSARC/2007/385 that added memcached 1.2.2. 2.2. Risks and Assumptions: None 3. Business Summary 3.1. Problem Area: Memcached 1.4.x adds support for the new binary protocol 3.2. Market/Requester: Memcached is a key ingredience in web 2.0 applications 4. Technical Description: 4.1. Details: The update to the memcached server and libmemcached contains an implementation of the new binary protocol. The ascii and binary protocol use the same port, and the server will auto-detect if the client use the binary or ascii protocol. An additional option (-C): To disable the allocation of CAS for each item (to save 8 bytes pr item) An additional option (-R): To specify the maximum number of network events to handle pr. client before serving the next client to avoid starvation. 4.2. Bug/RFE Number(s): 6709308 - memcached should run with restricted privileges 6708805 - memcached service fails out of box 4.5. Interfaces: Id Interface name Stability Comment ------------------------------------------------------------------ E?? daemon command line Uncommitted Removed option -b E?? deferred deletion Uncommitted Removed from protocol E38 DTrace probes Uncommitted Probe modifications for binary protocol E39 daemon command line Uncommitted New option: -C Disable CAS E40 daemon command line Uncommitted New option: -R E41 Binary protocol Uncommitted Support for new client protocol E42 Default instance Uncommitted Default user noaccess instead of root 4.6. Doc Impact: Man page update for command line options must be updated 4.7. Admin/Config Impact: Only if application tuning is required. 4.8. HA Impact: None 4.9. I18N/L10N Impact: None 4.11. Security Impact: Updated the default SMF instance so that memcached runs with uid noaccess instead of root by default. 4.12. Dependencies: No changes 5. Reference Documents: 6. Resources and Schedule: 6.1. Projected Availability: CY 2009 Q1 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.7. Target RTI Date/Release: SNV build XXX?? 6.5. ARC review type: FastTrack 6.6. ARC Exposure: Open --Boundary_(ID_bpNgwFl9sZrlUI/Q9P451A)-- From sacadmin Sun Feb 8 23:45:22 2009 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 n197jMlC028463 for ; Sun, 8 Feb 2009 23:45:22 -0800 (PST) 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 n197jIkG022462 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Sun, 8 Feb 2009 23:45:21 -0800 (PST) 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 <0KES00F03G7LWX00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Sun, 08 Feb 2009 23:45:21 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KES00ANHG7L7H20@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Sun, 08 Feb 2009 23:45:21 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n197jLrR022725 for ; Sun, 08 Feb 2009 23:45:21 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KES00700G3E6X00@fe-sfbay-09.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Sun, 08 Feb 2009 23:45:21 -0800 (PST) Received: from [129.145.154.87] ([unknown] [129.145.154.87]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KES00HZZG7KU840@fe-sfbay-09.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Sun, 08 Feb 2009 23:45:21 -0800 (PST) Date: Sun, 08 Feb 2009 23:45:17 -0800 From: Edward Hunter Subject: memcached 1.4.x LSARC/2009/067 Sender: Ed.Hunter@sun.com To: lsarc@sun.com, Trond.Norbye@sun.com Message-id: <498FDF0D.6070602@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 206 You mention a new binary communications protocol which according to the checklist requires ARC review but I see not pointers to any documentation on it. Also, is there a spec for the SMF changes? -edh From James.Gates@Sun.COM Wed Feb 25 07:34:41 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1PFYeeM014841 for ; Wed, 25 Feb 2009 07:34:41 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1PFYcmf023422 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 25 Feb 2009 15:34:39 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFM00F0HOLQWZ00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 25 Feb 2009 07:34:38 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFM00AK9OLN7380@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 25 Feb 2009 07:34:36 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n1PFYZCU016431 for ; Wed, 25 Feb 2009 15:34:35 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFM00G00NQP3600@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 25 Feb 2009 15:34:35 +0000 (GMT) Received: from [192.168.1.101] ([unknown] [67.45.218.181]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFM003YAOL6E3E0@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 25 Feb 2009 15:34:28 +0000 (GMT) Date: Wed, 25 Feb 2009 10:33:21 -0500 From: James Gates Subject: Re: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] In-reply-to: <498B1964.8070907@sun.com> Sender: James.Gates@Sun.COM To: LSARC-ext@Sun.COM Cc: Trond Norbye Message-id: <49A564C1.9090406@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <498B1964.8070907@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081023) Status: RO Content-Length: 939 Based on some comments from Ed Hunter, in the case directory we now have updated materials (slight change to SMF implementation) and a new document describing the binary protocol. I've reset the timer to Friday this week. James Gates wrote: > I'm sponsoring this case on behalf of Trond Norbye. This is actually a > version upgrade as memcached 1.2.5 & libmemcached 0.16 are already > integrated info sfwnv. However, the FOSS checklist was not in existence > at the time of the original ARC case, and completing it this time for > version 1.4.x identifies some areas where an ARC review is required. > > The main difference between versions 1.2 & 1.4 (other than bug fixes) is > the introduction of a new (binary) network communications protocol. > There are also proposed changes to the way we implement the SMF service. > -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql From Jyri.Virkki@sun.com Thu Feb 26 16:46:02 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1R0k2Bk025600 for ; Thu, 26 Feb 2009 16:46:02 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1R0jwFa042630; Thu, 26 Feb 2009 17:45:59 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFP00C0J8SM0S00@nwk-avmta-2.sfbay.sun.com>; Thu, 26 Feb 2009 16:45:58 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFP0037P8SKM990@nwk-avmta-2.sfbay.sun.com>; Thu, 26 Feb 2009 16:45:56 -0800 (PST) Received: from dm-usca19-13.red.iplanet.com (host-179-56-18-192.iplanet.com [192.18.56.179] (may be forged)) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1R0juuS024344; Fri, 27 Feb 2009 00:45:56 +0000 (GMT) Received: from buye.red.iplanet.com (buye [192.18.65.224]) by dm-usca19-13.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2) with ESMTP id n1R0jts16515; Thu, 26 Feb 2009 16:45:55 -0800 (PST) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id n1R0jtrA006592; Thu, 26 Feb 2009 16:45:55 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id n1R0jtX1006591; Thu, 26 Feb 2009 16:45:55 -0800 (PST) Date: Thu, 26 Feb 2009 16:45:55 -0800 From: Jyri Virkki Subject: Re: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] In-reply-to: <49A564C1.9090406@sun.com> To: James Gates Cc: LSARC-ext@sun.com, Trond Norbye , Sriram.Natarajan@sun.com Message-id: <20090227004555.GC3524@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 References: <498B1964.8070907@sun.com> <49A564C1.9090406@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 686 James Gates wrote: > > Based on some comments from Ed Hunter, in the case directory we now have > updated materials (slight change to SMF implementation) and a new > document describing the binary protocol. I've reset the timer to Friday > this week. Is memcached 1.4.* released yet? Looking at the download page at http://danga.com/memcached/download.bml there is only a 1.2.*. Or is it published elsewhere now? (This question probably doesn't really impact this case, except that if 1.4 is not yet released and interfaces change in it by the time it does release, the case might need some updates later to sync up.) -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From Trond.Norbye@sun.com Fri Feb 27 02:27:33 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1RARXP3022961 for ; Fri, 27 Feb 2009 02:27:33 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1RAROJ4022999 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 27 Feb 2009 10:27:31 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFP0021FZPUCH00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 27 Feb 2009 02:27:30 -0800 (PST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFP00JMUZPSEGB0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 27 Feb 2009 02:27:29 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n1RARSwZ001378 for ; Fri, 27 Feb 2009 10:27:28 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFP00C00YLFGD00@fe-emea-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 27 Feb 2009 10:27:28 +0000 (GMT) Received: from [129.159.112.225] ([unknown] [129.159.112.225]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFP000Y5ZPE6700@fe-emea-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 27 Feb 2009 10:27:14 +0000 (GMT) Date: Fri, 27 Feb 2009 11:27:12 +0100 From: Trond Norbye Subject: Re: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] In-reply-to: <20090227004555.GC3524@sun.com> Sender: Trond.Norbye@sun.com To: Jyri Virkki Cc: James Gates , LSARC-ext@sun.com, Sriram.Natarajan@sun.com Message-id: <49A7C000.7040602@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <498B1964.8070907@sun.com> <49A564C1.9090406@sun.com> <20090227004555.GC3524@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090203) Status: RO Content-Length: 860 Jyri Virkki wrote: > James Gates wrote: > >> Based on some comments from Ed Hunter, in the case directory we now have >> updated materials (slight change to SMF implementation) and a new >> document describing the binary protocol. I've reset the timer to Friday >> this week. >> > > Is memcached 1.4.* released yet? Looking at the download page at > http://danga.com/memcached/download.bml > there is only a 1.2.*. Or is it published elsewhere now? > > (This question probably doesn't really impact this case, except that if > 1.4 is not yet released and interfaces change in it by the time it > does release, the case might need some updates later to sync up.) > > 1.4 is not released yet, so there is a risk of interface changes. If the interface change I will present those to ARC before we start the integration process. Cheers, Trond From Jyri.Virkki@sun.com Fri Feb 27 10:14:56 2009 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 n1RIEu0S017553 for ; Fri, 27 Feb 2009 10:14:56 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1RIErg9008007; Fri, 27 Feb 2009 10:14:54 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFQ0061ZLCT5A00@brm-avmta-1.central.sun.com>; Fri, 27 Feb 2009 11:14:53 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFQ00K2LLCQH490@brm-avmta-1.central.sun.com>; Fri, 27 Feb 2009 11:14:50 -0700 (MST) Received: from dm-usca19-13.red.iplanet.com (host-179-56-18-192.iplanet.com [192.18.56.179] (may be forged)) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1RIEnUu015537; Fri, 27 Feb 2009 18:14:50 +0000 (GMT) Received: from buye.red.iplanet.com (buye [192.18.65.224]) by dm-usca19-13.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2) with ESMTP id n1RIEns05411; Fri, 27 Feb 2009 10:14:49 -0800 (PST) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id n1RIEnN6007774; Fri, 27 Feb 2009 10:14:49 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id n1RIEn9m007773; Fri, 27 Feb 2009 10:14:49 -0800 (PST) Date: Fri, 27 Feb 2009 10:14:49 -0800 From: Jyri Virkki Subject: Re: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] In-reply-to: <49A7C000.7040602@sun.com> To: Trond Norbye Cc: LSARC-ext@sun.com, Sriram.Natarajan@sun.com Message-id: <20090227181449.GA6508@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 References: <498B1964.8070907@sun.com> <49A564C1.9090406@sun.com> <20090227004555.GC3524@sun.com> <49A7C000.7040602@sun.com> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 710 Trond Norbye wrote: > > >Is memcached 1.4.* released yet? Looking at the download page at > >http://danga.com/memcached/download.bml > >there is only a 1.2.*. Or is it published elsewhere now? > > > >(This question probably doesn't really impact this case, except that if > >1.4 is not yet released and interfaces change in it by the time it > >does release, the case might need some updates later to sync up.) > > 1.4 is not released yet, so there is a risk of interface changes. > > If the interface change I will present those to ARC before we start the > integration process. Thanks, sounds good. I have no further questions on this case. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From James.Gates@sun.com Mon Mar 2 13:57:26 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n22LvQcr018686 for ; Mon, 2 Mar 2009 13:57:26 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n22LvOXH006360 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 2 Mar 2009 14:57:25 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFW00M0LFNO9C00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 02 Mar 2009 14:57:24 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFW00GXLFNM6R40@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 02 Mar 2009 14:57:23 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n22LvM2j025164 for ; Mon, 02 Mar 2009 21:57:22 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFW00600FM2SS00@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 02 Mar 2009 21:57:22 +0000 (GMT) Received: from [192.168.1.101] ([unknown] [67.45.218.181]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFW00HD7FNBBY50@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 02 Mar 2009 21:57:22 +0000 (GMT) Date: Mon, 02 Mar 2009 16:56:14 -0500 From: James Gates Subject: Re: memcached 1.4.x to be included in OpenSolaris [LSARC/2009/067 FastTrack timeout 02/13/2009] In-reply-to: <498B1964.8070907@sun.com> Sender: James.Gates@sun.com To: lsarc-ext@sun.com, Trond Norbye Message-id: <49AC55FE.8040109@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <498B1964.8070907@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081023) Status: RO Content-Length: 999 This case is now approved. Name: memcached 1.4.x to be included in OpenSolaris Submitter: Trond Norbye Owner: James Gates Interest: Trond.Norbye@sun.com,jim.gates@sun.com Status: closed approved fast-track 02/27/2009 Exposure: open Comment: James Gates wrote: > I'm sponsoring this case on behalf of Trond Norbye. This is actually a > version upgrade as memcached 1.2.5 & libmemcached 0.16 are already > integrated info sfwnv. However, the FOSS checklist was not in existence > at the time of the original ARC case, and completing it this time for > version 1.4.x identifies some areas where an ARC review is required. > > The main difference between versions 1.2 & 1.4 (other than bug fixes) is > the introduction of a new (binary) network communications protocol. > There are also proposed changes to the way we implement the SMF service. > -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql