From hyw@sac.sfbay.sun.com Mon Jan 4 15:01:02 2010 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 o04N12oT001634 for ; Mon, 4 Jan 2010 15:01:02 -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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o04N11Tg014707; Mon, 4 Jan 2010 15:01:01 -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 <0KVQ0050ZVXPTL00@brm-avmta-1.central.sun.com>; Mon, 04 Jan 2010 16:01:01 -0700 (MST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KVQ00DZ6VXMO070@brm-avmta-1.central.sun.com>; Mon, 04 Jan 2010 16:00:59 -0700 (MST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o04N0vJd028882; Mon, 04 Jan 2010 15:00:57 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o04N0tP7001629; Mon, 04 Jan 2010 15:00:55 -0800 (PST) Received: (from hyw@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id o04N0tAO001625; Mon, 04 Jan 2010 15:00:55 -0800 (PST) Date: Mon, 04 Jan 2010 15:00:55 -0800 (PST) From: Huay-Yong Wang Subject: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] To: PSARC-ext@sun.com Cc: Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com, Michael.Christensen@sun.com Message-id: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 8812 I am sponsoring this fasttrack for Michael Christensen. The project team is requesting a patch/micro release binding. The 3 manpages (ldminfo.1m, libldom.3lib & ldoms_capabilities.3ldoms) and the libldoms.h include file are placed in the case directory. The timer is set to expire on 1/14/10. ------- 1. Introduction 1.1 Project/Component Working Name Logical Domains Information API and ldminfo program 1.2 Name of Document Author/Supplier Michael Christensen 1.3 Date of This Document 18-DEC-2009 1.4 Name of Major Document Customer(s)/Consumer(s) 1.4.1 The PAC or CPT you expect to review your project 1.4.2 The ARC(s) you expect to review your project PSARC 1.4.3 The Director/VP who is sponsoring this project jerriann.meyer@sun.com 1.4.4 The Name of Your Business Unit Solaris Core OS 1.5 Email Aliases 1.5.1 Responsible Manager: jay.jayachandran@sun.com 1.5.2 Responsible Engineer: michael.christensen@sun.com 1.5.3 Marketing Manager: duncan.hardie@sun.com 1.5.4 Interest List: ldoms-internal@sun.com 2. Project Summary 2.1 Project Description This project will implement Logical Domains Information API and ldminfo program on Solaris. The API and ldminfo program will provide information about the currently running domain. Among the items that may be provided are: - Domain type (control, guest, I/O, service, root) - LDom Manager's LDom name for this domain (Domain name) - Domain Universally Unique ID (UUID) - Domain's control domain network nodename - Chassis Serial Number the domain is running on. None of the above items are currently easily obtainable from within a guest domain. As an example, many customers have expressed a desire to run LDom manager scripts on the control domain initiated from a guest domain. However, there is no easy way to either identify the network nodename of the control domain or to identify the LDom Manager's name for the current domain, which would be required for LDom Manager commands. Further, many customers have requested a means of uniquely identifying each domain and also identifying the hardware platform that the domain is running on for accounting or resourcing. On the Solaris operating system, the Logical Domains Information API will be implemented as a library (libldoms) using information from the Guest Domain's Machine Description provided by FWARC 2005/115 (sun4v machine description), the sun4v MD uuid property from FWARC 2009/680 (Domain UUID property), the libds library provided by PSARC 2008/568 (Logical Domain's Domain Services) and using domain services provided by the logical domain agent daemon provided by PSARC 2009/459 (Logical Domains Agents on Solaris) and FWARC 2009/426 (Logical Domains Agents). The ldminfo program will utilize the libldoms library to display the various items of information provided. 2.2 Risks and Assumptions None. 3. Business Summary 3.1 Problem Area In an LDoms system, a user program or user has no easy way to identify what type of domain the program is being run on (e.g. control domain, guest domain, I/O domain, service domain). Also a guest domain has no easy way to identify the network nodename of its control domain, what name the LDoms Manager running on the control domain uses to identify this domain, what is the domain's Universally Unique Identifier that The LDoms Manager uses to identify this domain or what the Chassis Serial Number of the platform it is currently running on. 3.2 Market/Requestor See FWARC 2005/633. 3.3 Business Justification See FWARC 2005/633. 3.4 Competitive Analysis The problems listed in 3.1 have been the subject of bug reports from customers. Virtualization solutions provided by competitors have equivalent functionality. 3.5 Opportunity Window/Exposure See FWARC 2005/663. 3.6 How will you know when you are done? The work will be completed when the final code changes to implement Logical Domains Information API and ldminfo program are integrated into the Solaris Nevada gate and Solaris 10 Update gates. 4. Technical Description 4.1 Overview On the Solaris operating system, Logical Domains Information API will be implemented as a user library "libldoms.so.1" and a user program "ldminfo" will be provided to display this information. This information will be provided either via the sun4v Machine Description (FWARC/2005/115 and FWARC 2009/680) or via a domain service (FWARC/2009/426) provided by the logical domains agent daemon (PSARC/2009/459) on the control domain. 4.2 Bug/RFE Number(s) 6680702 - Want a mechanism for Solaris to know if it is an LDOM and if so what type 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking 6712763 - Need information about control domain from within a guest domain 4.3 Scope Not Applicable. 4.4 Out of Scope Not Applicable. 4.5 Interfaces 4.5.1 Interfaces 4.5.2 Imported Interfaces Interface Classification Comments ================================================================= Domain Services API Consolidation Private PSARC/2008/568 (libds.so.1) Logical Domains Sun Private PSARC/2009/459 Agents on Solaris Logical Domains Sun Private FWARC/2009/426 Agents Machine Description Sun Private FWARC/2005/115 Device (/dev/mdesc) Domain UUID property Consolidation Private FWARC/2009/680 UUID library API Evolving PSARC/2002/094 (libuuid.so.1) 4.5.3 Exported Interfaces Interface Classification Comments ================================================================ /usr/sbin/ldminfo Committed See ldminfo(1M) /usr/lib/libldoms.so Committed 32-bit library /usr/lib/sparcv9/libldoms.so Committed 64-bit library /usr/include/libldoms.h Committed Header file ldoms_capabilities() Committed ldoms_domain_roles() Committed ldoms_domain_name() Committed ldoms_domain_uuid() Committed ldoms_control_domain() Committed ldoms_platform_serialno() Committed LDMCAP_SUPPORTED Committed LDMCAP_ENABLED Committed LDMROLE_CONTROL Committed LDMROLE_IO Committed LDMROLE_SERVICE Committed LDMROLE_ROOT Committed 4.6 Doc Impact Man pages for ldminfo (1M), libldoms (3LIB), ldoms_capabilities(3LDOMS), ldoms_domain_roles(3LDOMS), ldoms_domain_name(3LDOMS), ldoms_domain_uuid(3LDOMS), ldoms_control_domain(3LDOMS), ldoms_platform_serialno(3LDOMS) 4.7 Admin/Config Impact None. 4.8 HA Impact None. 4.9 I18N/L10N Not affected. 4.10 Packaging & Delivery The Logical Domains Information API library libldoms and ldminfo program will be delivered as part of the existing Solaris packages SUNWcsl (Solaris 32bit libraries), SUNWcslx (Solaris 64bit libraries), SUNWcsu (Solaris User Core), SUNWhea (Solaris headers) on Sparc platforms only. 4.11 Security Impact None. 4.12 Dependencies None. 5. Reference Documents PSARC 2008/568 Logical Domain's Domain Services PSARC 2009/459 Logical Domain's Agents on Solaris FWARC 2005/115 sun4v machine description FWARC 2009/680 Domain UUID property 6. Resources and Schedule 6.1 Projected Availability Q4FY10 (S10U9) 6.2 Cost of Effort 1 person month 6.3 Cost of Capital Resources 6.4 Product Approval Committee requested information 6.4.1 Consolidation Or Component Name OS-Networking (ON) 6.4.3 Type of CPT Approval Expected FastTrack 6.4.4 Project Boundary Conditions 6.4.5 Is this a necessary project for OEM agreements: No. 6.4.6 Notes 6.4.7 Target RTI Date/Release February 2010 6.4.8 Target Code Design Review Date: 6.4.9 Update approval addition: Not applicable 6.5 ARC review type FastTrack 6.6 ARC Exposure open 7. Prototype Availability: 7.1 Prototype Availability A prototype is already available. 7.2 Prototype Cost: A prototype is already available. From Huay-Yong.Wang@Sun.COM Tue Jan 12 13:19:09 2010 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o0CLJ9Sh013003 for ; Tue, 12 Jan 2010 13:19:09 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0CLJ820016377 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 12 Jan 2010 15:19:08 -0600 (CST) 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 <0KW500H2BKJWOA00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 12 Jan 2010 13:19:08 -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 <0KW500GMVKJTQ500@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 12 Jan 2010 13:19:05 -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 o0CLJ5NZ001406 for ; Tue, 12 Jan 2010 13:19:05 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW500800KDS9I00@fe-sfbay-09.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Tue, 12 Jan 2010 13:19:04 -0800 (PST) Received: from [129.153.85.39] ([unknown] [129.153.85.39]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW500J1ZKJBOSD0@fe-sfbay-09.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Tue, 12 Jan 2010 13:18:48 -0800 (PST) Date: Tue, 12 Jan 2010 13:18:47 -0800 From: Huay-Yong Wang Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> Sender: Huay-Yong.Wang@Sun.COM To: PSARC-ext@Sun.COM Cc: Alexandre.Chartre@Sun.COM, Eric.Sharakan@Sun.COM, Michael.Christensen@Sun.COM Message-id: <4B4CE737.8070107@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20090910) Status: RO Content-Length: 9713 I have not seen any comments or discussions for this fasttrack. Earlier, I have asked the project team to attend ARC business in the next psarc meeting (1/13) to answer questions but realized that there is no meeting that day. Can folks review this and hopefully ack the case with some +1s. The timer expires this thursday (1/14) Thanks. On 01/04/10 15:00, Huay-Yong Wang wrote: > I am sponsoring this fasttrack for Michael Christensen. > The project team is requesting a patch/micro release binding. > The 3 manpages (ldminfo.1m, libldom.3lib & > ldoms_capabilities.3ldoms) and the libldoms.h include > file are placed in the case directory. > > The timer is set to expire on 1/14/10. > > ------- > > 1. Introduction > > 1.1 Project/Component Working Name > > Logical Domains Information API and ldminfo program > > 1.2 Name of Document Author/Supplier > > Michael Christensen > > 1.3 Date of This Document > > 18-DEC-2009 > > 1.4 Name of Major Document Customer(s)/Consumer(s) > > 1.4.1 The PAC or CPT you expect to review your project > > 1.4.2 The ARC(s) you expect to review your project > > PSARC > > 1.4.3 The Director/VP who is sponsoring this project > > jerriann.meyer@sun.com > > 1.4.4 The Name of Your Business Unit > > Solaris Core OS > > 1.5 Email Aliases > > 1.5.1 Responsible Manager: jay.jayachandran@sun.com > > 1.5.2 Responsible Engineer: michael.christensen@sun.com > > 1.5.3 Marketing Manager: duncan.hardie@sun.com > > 1.5.4 Interest List: ldoms-internal@sun.com > > 2. Project Summary > > 2.1 Project Description > > This project will implement Logical Domains Information API > and ldminfo program on Solaris. The API and ldminfo > program will provide information about the currently running > domain. Among the items that may be provided are: > > - Domain type (control, guest, I/O, service, root) > - LDom Manager's LDom name for this domain (Domain name) > - Domain Universally Unique ID (UUID) > - Domain's control domain network nodename > - Chassis Serial Number the domain is running on. > > None of the above items are currently easily obtainable from > within a guest domain. As an example, many customers have > expressed a desire to run LDom manager scripts on the > control domain initiated from a guest domain. However, there > is no easy way to either identify the network nodename of the > control domain or to identify the LDom Manager's name for the > current domain, which would be required for LDom Manager > commands. Further, many customers have requested a means of > uniquely identifying each domain and also identifying the > hardware platform that the domain is running on for > accounting or resourcing. > > On the Solaris operating system, the Logical Domains Information > API will be implemented as a library (libldoms) using > information from the Guest Domain's Machine Description provided > by FWARC 2005/115 (sun4v machine description), the sun4v MD > uuid property from FWARC 2009/680 (Domain UUID property), the > libds library provided by PSARC 2008/568 (Logical Domain's Domain > Services) and using domain services provided by the logical > domain agent daemon provided by PSARC 2009/459 (Logical Domains > Agents on Solaris) and FWARC 2009/426 (Logical Domains Agents). > The ldminfo program will utilize the libldoms library to display > the various items of information provided. > > 2.2 Risks and Assumptions > > None. > > 3. Business Summary > > 3.1 Problem Area > > In an LDoms system, a user program or user has no easy way > to identify what type of domain the program is being run > on (e.g. control domain, guest domain, I/O domain, service > domain). Also a guest domain has no easy way to identify the > network nodename of its control domain, what name the LDoms > Manager running on the control domain uses to identify this > domain, what is the domain's Universally Unique Identifier that > The LDoms Manager uses to identify this domain or what the > Chassis Serial Number of the platform it is currently running > on. > > 3.2 Market/Requestor > > See FWARC 2005/633. > > 3.3 Business Justification > > See FWARC 2005/633. > > 3.4 Competitive Analysis > > The problems listed in 3.1 have been the subject of bug > reports from customers. Virtualization solutions provided by > competitors have equivalent functionality. > > 3.5 Opportunity Window/Exposure > > See FWARC 2005/663. > > 3.6 How will you know when you are done? > > The work will be completed when the final code changes to > implement Logical Domains Information API and ldminfo program > are integrated into the Solaris Nevada gate and Solaris 10 > Update gates. > > 4. Technical Description > > 4.1 Overview > > On the Solaris operating system, Logical Domains Information > API will be implemented as a user library "libldoms.so.1" and > a user program "ldminfo" will be provided to display this > information. This information will be provided either via > the sun4v Machine Description (FWARC/2005/115 and > FWARC 2009/680) or via a domain service (FWARC/2009/426) > provided by the logical domains agent daemon (PSARC/2009/459) > on the control domain. > > 4.2 Bug/RFE Number(s) > > 6680702 - Want a mechanism for Solaris to know if it is an LDOM > and if so what type > > 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking > > 6712763 - Need information about control domain from within a > guest domain > > 4.3 Scope > > Not Applicable. > > 4.4 Out of Scope > > Not Applicable. > > 4.5 Interfaces > > 4.5.1 Interfaces > > 4.5.2 Imported Interfaces > > Interface Classification Comments > ================================================================= > > Domain Services API Consolidation Private PSARC/2008/568 > (libds.so.1) > > Logical Domains Sun Private PSARC/2009/459 > Agents on Solaris > > Logical Domains Sun Private FWARC/2009/426 > Agents > > Machine Description Sun Private FWARC/2005/115 > Device (/dev/mdesc) > > Domain UUID property Consolidation Private FWARC/2009/680 > > UUID library API Evolving PSARC/2002/094 > (libuuid.so.1) > > > 4.5.3 Exported Interfaces > > Interface Classification Comments > ================================================================ > > /usr/sbin/ldminfo Committed See ldminfo(1M) > /usr/lib/libldoms.so Committed 32-bit library > /usr/lib/sparcv9/libldoms.so Committed 64-bit library > /usr/include/libldoms.h Committed Header file > > ldoms_capabilities() Committed > ldoms_domain_roles() Committed > ldoms_domain_name() Committed > ldoms_domain_uuid() Committed > ldoms_control_domain() Committed > ldoms_platform_serialno() Committed > > LDMCAP_SUPPORTED Committed > LDMCAP_ENABLED Committed > LDMROLE_CONTROL Committed > LDMROLE_IO Committed > LDMROLE_SERVICE Committed > LDMROLE_ROOT Committed > > 4.6 Doc Impact > > Man pages for ldminfo (1M), libldoms (3LIB), > ldoms_capabilities(3LDOMS), ldoms_domain_roles(3LDOMS), > ldoms_domain_name(3LDOMS), ldoms_domain_uuid(3LDOMS), > ldoms_control_domain(3LDOMS), ldoms_platform_serialno(3LDOMS) > > 4.7 Admin/Config Impact > > None. > > 4.8 HA Impact > > None. > > 4.9 I18N/L10N > > Not affected. > > 4.10 Packaging & Delivery > > The Logical Domains Information API library libldoms and > ldminfo program will be delivered as part of the existing > Solaris packages SUNWcsl (Solaris 32bit libraries), SUNWcslx > (Solaris 64bit libraries), SUNWcsu (Solaris User Core), > SUNWhea (Solaris headers) on Sparc platforms only. > > 4.11 Security Impact > > None. > > 4.12 Dependencies > > None. > > 5. Reference Documents > > PSARC 2008/568 Logical Domain's Domain Services > PSARC 2009/459 Logical Domain's Agents on Solaris > FWARC 2005/115 sun4v machine description > FWARC 2009/680 Domain UUID property > > 6. Resources and Schedule > > 6.1 Projected Availability > > Q4FY10 (S10U9) > > 6.2 Cost of Effort > > 1 person month > > 6.3 Cost of Capital Resources > > 6.4 Product Approval Committee requested information > > 6.4.1 Consolidation Or Component Name > > OS-Networking (ON) > > 6.4.3 Type of CPT Approval Expected > > FastTrack > > 6.4.4 Project Boundary Conditions > > 6.4.5 Is this a necessary project for OEM agreements: > > No. > > 6.4.6 Notes > > 6.4.7 Target RTI Date/Release > > February 2010 > > 6.4.8 Target Code Design Review Date: > > 6.4.9 Update approval addition: > > Not applicable > > 6.5 ARC review type > > FastTrack > > 6.6 ARC Exposure > > open > > 7. Prototype Availability: > > 7.1 Prototype Availability > > A prototype is already available. > > 7.2 Prototype Cost: > > A prototype is already available. > > From Richard.Matthews@sun.com Wed Jan 13 15:55:25 2010 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 o0DNtPZN028564 for ; Wed, 13 Jan 2010 15:55:25 -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.4) with ESMTP id o0DNtNPe006150 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 13 Jan 2010 16:55:25 -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 <0KW700L25MGCW100@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 13 Jan 2010 15:55:24 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW700DTLMG8ET30@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 13 Jan 2010 15:55:20 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0DNtJW8012274 for ; Wed, 13 Jan 2010 23:55:19 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW700A00MBWN200@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 13 Jan 2010 16:55:19 -0700 (MST) Received: from [129.152.9.11] ([unknown] [129.152.9.11]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW7007LXMG64M80@mail-amer.sun.com>; Wed, 13 Jan 2010 16:55:19 -0700 (MST) Date: Wed, 13 Jan 2010 17:55:17 -0600 From: Rick Matthews Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> Sender: Richard.Matthews@sun.com To: Huay-Yong Wang Cc: PSARC-ext@sun.com, Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com, Michael.Christensen@sun.com Reply-to: Richard.Matthews@sun.com Message-id: <4B4E5D65.6040505@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20090910) Status: RO Content-Length: 10272 There was no meeting scheduled for Jan. 13. I believe a question was asked (and if not, I'll ask it) as to why an LDOMs specific virtualization query? Would there be a query that could give the caller "generic" virtualization information (working for both Zen and LDOMs)? Was this considered? Could a generic call identify the virtualization technology, and then, if needed, technology specific queries could be made? -- Rick On 01/04/10 17:00, Huay-Yong Wang wrote: > I am sponsoring this fasttrack for Michael Christensen. > The project team is requesting a patch/micro release binding. > The 3 manpages (ldminfo.1m, libldom.3lib & > ldoms_capabilities.3ldoms) and the libldoms.h include > file are placed in the case directory. > > The timer is set to expire on 1/14/10. > > ------- > > 1. Introduction > > 1.1 Project/Component Working Name > > Logical Domains Information API and ldminfo program > > 1.2 Name of Document Author/Supplier > > Michael Christensen > > 1.3 Date of This Document > > 18-DEC-2009 > > 1.4 Name of Major Document Customer(s)/Consumer(s) > > 1.4.1 The PAC or CPT you expect to review your project > > 1.4.2 The ARC(s) you expect to review your project > > PSARC > > 1.4.3 The Director/VP who is sponsoring this project > > jerriann.meyer@sun.com > > 1.4.4 The Name of Your Business Unit > > Solaris Core OS > > 1.5 Email Aliases > > 1.5.1 Responsible Manager: jay.jayachandran@sun.com > > 1.5.2 Responsible Engineer: michael.christensen@sun.com > > 1.5.3 Marketing Manager: duncan.hardie@sun.com > > 1.5.4 Interest List: ldoms-internal@sun.com > > 2. Project Summary > > 2.1 Project Description > > This project will implement Logical Domains Information API > and ldminfo program on Solaris. The API and ldminfo > program will provide information about the currently running > domain. Among the items that may be provided are: > > - Domain type (control, guest, I/O, service, root) > - LDom Manager's LDom name for this domain (Domain name) > - Domain Universally Unique ID (UUID) > - Domain's control domain network nodename > - Chassis Serial Number the domain is running on. > > None of the above items are currently easily obtainable from > within a guest domain. As an example, many customers have > expressed a desire to run LDom manager scripts on the > control domain initiated from a guest domain. However, there > is no easy way to either identify the network nodename of the > control domain or to identify the LDom Manager's name for the > current domain, which would be required for LDom Manager > commands. Further, many customers have requested a means of > uniquely identifying each domain and also identifying the > hardware platform that the domain is running on for > accounting or resourcing. > > On the Solaris operating system, the Logical Domains Information > API will be implemented as a library (libldoms) using > information from the Guest Domain's Machine Description provided > by FWARC 2005/115 (sun4v machine description), the sun4v MD > uuid property from FWARC 2009/680 (Domain UUID property), the > libds library provided by PSARC 2008/568 (Logical Domain's Domain > Services) and using domain services provided by the logical > domain agent daemon provided by PSARC 2009/459 (Logical Domains > Agents on Solaris) and FWARC 2009/426 (Logical Domains Agents). > The ldminfo program will utilize the libldoms library to display > the various items of information provided. > > 2.2 Risks and Assumptions > > None. > > 3. Business Summary > > 3.1 Problem Area > > In an LDoms system, a user program or user has no easy way > to identify what type of domain the program is being run > on (e.g. control domain, guest domain, I/O domain, service > domain). Also a guest domain has no easy way to identify the > network nodename of its control domain, what name the LDoms > Manager running on the control domain uses to identify this > domain, what is the domain's Universally Unique Identifier that > The LDoms Manager uses to identify this domain or what the > Chassis Serial Number of the platform it is currently running > on. > > 3.2 Market/Requestor > > See FWARC 2005/633. > > 3.3 Business Justification > > See FWARC 2005/633. > > 3.4 Competitive Analysis > > The problems listed in 3.1 have been the subject of bug > reports from customers. Virtualization solutions provided by > competitors have equivalent functionality. > > 3.5 Opportunity Window/Exposure > > See FWARC 2005/663. > > 3.6 How will you know when you are done? > > The work will be completed when the final code changes to > implement Logical Domains Information API and ldminfo program > are integrated into the Solaris Nevada gate and Solaris 10 > Update gates. > > 4. Technical Description > > 4.1 Overview > > On the Solaris operating system, Logical Domains Information > API will be implemented as a user library "libldoms.so.1" and > a user program "ldminfo" will be provided to display this > information. This information will be provided either via > the sun4v Machine Description (FWARC/2005/115 and > FWARC 2009/680) or via a domain service (FWARC/2009/426) > provided by the logical domains agent daemon (PSARC/2009/459) > on the control domain. > > 4.2 Bug/RFE Number(s) > > 6680702 - Want a mechanism for Solaris to know if it is an LDOM > and if so what type > > 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking > > 6712763 - Need information about control domain from within a > guest domain > > 4.3 Scope > > Not Applicable. > > 4.4 Out of Scope > > Not Applicable. > > 4.5 Interfaces > > 4.5.1 Interfaces > > 4.5.2 Imported Interfaces > > Interface Classification Comments > ================================================================= > > Domain Services API Consolidation Private PSARC/2008/568 > (libds.so.1) > > Logical Domains Sun Private PSARC/2009/459 > Agents on Solaris > > Logical Domains Sun Private FWARC/2009/426 > Agents > > Machine Description Sun Private FWARC/2005/115 > Device (/dev/mdesc) > > Domain UUID property Consolidation Private FWARC/2009/680 > > UUID library API Evolving PSARC/2002/094 > (libuuid.so.1) > > > 4.5.3 Exported Interfaces > > Interface Classification Comments > ================================================================ > > /usr/sbin/ldminfo Committed See ldminfo(1M) > /usr/lib/libldoms.so Committed 32-bit library > /usr/lib/sparcv9/libldoms.so Committed 64-bit library > /usr/include/libldoms.h Committed Header file > > ldoms_capabilities() Committed > ldoms_domain_roles() Committed > ldoms_domain_name() Committed > ldoms_domain_uuid() Committed > ldoms_control_domain() Committed > ldoms_platform_serialno() Committed > > LDMCAP_SUPPORTED Committed > LDMCAP_ENABLED Committed > LDMROLE_CONTROL Committed > LDMROLE_IO Committed > LDMROLE_SERVICE Committed > LDMROLE_ROOT Committed > > 4.6 Doc Impact > > Man pages for ldminfo (1M), libldoms (3LIB), > ldoms_capabilities(3LDOMS), ldoms_domain_roles(3LDOMS), > ldoms_domain_name(3LDOMS), ldoms_domain_uuid(3LDOMS), > ldoms_control_domain(3LDOMS), ldoms_platform_serialno(3LDOMS) > > 4.7 Admin/Config Impact > > None. > > 4.8 HA Impact > > None. > > 4.9 I18N/L10N > > Not affected. > > 4.10 Packaging & Delivery > > The Logical Domains Information API library libldoms and > ldminfo program will be delivered as part of the existing > Solaris packages SUNWcsl (Solaris 32bit libraries), SUNWcslx > (Solaris 64bit libraries), SUNWcsu (Solaris User Core), > SUNWhea (Solaris headers) on Sparc platforms only. > > 4.11 Security Impact > > None. > > 4.12 Dependencies > > None. > > 5. Reference Documents > > PSARC 2008/568 Logical Domain's Domain Services > PSARC 2009/459 Logical Domain's Agents on Solaris > FWARC 2005/115 sun4v machine description > FWARC 2009/680 Domain UUID property > > 6. Resources and Schedule > > 6.1 Projected Availability > > Q4FY10 (S10U9) > > 6.2 Cost of Effort > > 1 person month > > 6.3 Cost of Capital Resources > > 6.4 Product Approval Committee requested information > > 6.4.1 Consolidation Or Component Name > > OS-Networking (ON) > > 6.4.3 Type of CPT Approval Expected > > FastTrack > > 6.4.4 Project Boundary Conditions > > 6.4.5 Is this a necessary project for OEM agreements: > > No. > > 6.4.6 Notes > > 6.4.7 Target RTI Date/Release > > February 2010 > > 6.4.8 Target Code Design Review Date: > > 6.4.9 Update approval addition: > > Not applicable > > 6.5 ARC review type > > FastTrack > > 6.6 ARC Exposure > > open > > 7. Prototype Availability: > > 7.1 Prototype Availability > > A prototype is already available. > > 7.2 Prototype Cost: > > A prototype is already available. > > -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Michael.Christensen@sun.com Thu Jan 14 11:12:06 2010 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id o0EJC6E6003386 for ; Thu, 14 Jan 2010 11:12:06 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0EJC25S023469 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 14 Jan 2010 11:12:06 -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 <0KW90051D406P100@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 14 Jan 2010 12:12:06 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KW900HV0404YA80@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 14 Jan 2010 12:12:04 -0700 (MST) 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 o0EJC4Mi009753 for ; Thu, 14 Jan 2010 11:12:04 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KW9005002H4EU00@fe-sfbay-09.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 14 Jan 2010 11:12:04 -0800 (PST) Received: from [129.153.85.9] ([unknown] [129.153.85.9]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KW90016X402OTA0@fe-sfbay-09.sun.com>; Thu, 14 Jan 2010 11:12:03 -0800 (PST) Date: Thu, 14 Jan 2010 11:12:02 -0800 From: Mike Christensen Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <4B4E5D65.6040505@Sun.COM> Sender: Michael.Christensen@sun.com To: Richard.Matthews@sun.com Cc: Huay-Yong Wang , PSARC-ext@sun.com, Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com Reply-to: Michael.Christensen@sun.com Message-id: <4B4F6C82.3060808@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> <4B4E5D65.6040505@Sun.COM> User-Agent: Thunderbird 2.0.0.23 (X11/20090910) Status: RO Content-Length: 10721 On 01/13/10 15:55, Rick Matthews wrote: > There was no meeting scheduled for Jan. 13. > > I believe a question was asked (and if not, I'll ask it) as to why an > LDOMs specific > virtualization query? Would there be a query that could give the caller > "generic" virtualization > information (working for both Zen and LDOMs)? Was this considered? No, we didn't really consider Xen support. I'm engaging the Xen group right now to see if there's easily achievable common ground. > Could a generic call identify the virtualization technology, and > then, if needed, technology specific queries could be made? Yes, if it's not easy to converge with Xen, we can supply that. It's probably going to take me a couple of days to resolve these issues. Mike > -- > Rick > > On 01/04/10 17:00, Huay-Yong Wang wrote: >> I am sponsoring this fasttrack for Michael Christensen. >> The project team is requesting a patch/micro release binding. >> The 3 manpages (ldminfo.1m, libldom.3lib & >> ldoms_capabilities.3ldoms) and the libldoms.h include >> file are placed in the case directory. >> >> The timer is set to expire on 1/14/10. >> >> ------- >> >> 1. Introduction >> >> 1.1 Project/Component Working Name >> >> Logical Domains Information API and ldminfo program >> >> 1.2 Name of Document Author/Supplier >> >> Michael Christensen >> >> 1.3 Date of This Document >> >> 18-DEC-2009 >> >> 1.4 Name of Major Document Customer(s)/Consumer(s) >> >> 1.4.1 The PAC or CPT you expect to review your project >> >> 1.4.2 The ARC(s) you expect to review your project >> >> PSARC >> >> 1.4.3 The Director/VP who is sponsoring this project >> >> jerriann.meyer@sun.com >> >> 1.4.4 The Name of Your Business Unit >> >> Solaris Core OS >> >> 1.5 Email Aliases >> >> 1.5.1 Responsible Manager: jay.jayachandran@sun.com >> >> 1.5.2 Responsible Engineer: michael.christensen@sun.com >> >> 1.5.3 Marketing Manager: duncan.hardie@sun.com >> >> 1.5.4 Interest List: ldoms-internal@sun.com >> >> 2. Project Summary >> >> 2.1 Project Description >> >> This project will implement Logical Domains Information API >> and ldminfo program on Solaris. The API and ldminfo >> program will provide information about the currently running >> domain. Among the items that may be provided are: >> >> - Domain type (control, guest, I/O, service, root) >> - LDom Manager's LDom name for this domain (Domain name) >> - Domain Universally Unique ID (UUID) >> - Domain's control domain network nodename >> - Chassis Serial Number the domain is running on. >> >> None of the above items are currently easily obtainable from >> within a guest domain. As an example, many customers have >> expressed a desire to run LDom manager scripts on the >> control domain initiated from a guest domain. However, there >> is no easy way to either identify the network nodename of the >> control domain or to identify the LDom Manager's name for the >> current domain, which would be required for LDom Manager >> commands. Further, many customers have requested a means of >> uniquely identifying each domain and also identifying the >> hardware platform that the domain is running on for >> accounting or resourcing. >> >> On the Solaris operating system, the Logical Domains Information >> API will be implemented as a library (libldoms) using >> information from the Guest Domain's Machine Description provided >> by FWARC 2005/115 (sun4v machine description), the sun4v MD >> uuid property from FWARC 2009/680 (Domain UUID property), the >> libds library provided by PSARC 2008/568 (Logical Domain's Domain >> Services) and using domain services provided by the logical >> domain agent daemon provided by PSARC 2009/459 (Logical Domains >> Agents on Solaris) and FWARC 2009/426 (Logical Domains Agents). >> The ldminfo program will utilize the libldoms library to display >> the various items of information provided. >> >> 2.2 Risks and Assumptions >> >> None. >> >> 3. Business Summary >> >> 3.1 Problem Area >> >> In an LDoms system, a user program or user has no easy way >> to identify what type of domain the program is being run >> on (e.g. control domain, guest domain, I/O domain, service >> domain). Also a guest domain has no easy way to identify the >> network nodename of its control domain, what name the LDoms >> Manager running on the control domain uses to identify this >> domain, what is the domain's Universally Unique Identifier that >> The LDoms Manager uses to identify this domain or what the >> Chassis Serial Number of the platform it is currently running >> on. >> >> 3.2 Market/Requestor >> >> See FWARC 2005/633. >> >> 3.3 Business Justification >> >> See FWARC 2005/633. >> >> 3.4 Competitive Analysis >> >> The problems listed in 3.1 have been the subject of bug >> reports from customers. Virtualization solutions provided by >> competitors have equivalent functionality. >> >> 3.5 Opportunity Window/Exposure >> >> See FWARC 2005/663. >> >> 3.6 How will you know when you are done? >> >> The work will be completed when the final code changes to >> implement Logical Domains Information API and ldminfo program >> are integrated into the Solaris Nevada gate and Solaris 10 >> Update gates. >> >> 4. Technical Description >> >> 4.1 Overview >> >> On the Solaris operating system, Logical Domains Information >> API will be implemented as a user library "libldoms.so.1" and >> a user program "ldminfo" will be provided to display this >> information. This information will be provided either via >> the sun4v Machine Description (FWARC/2005/115 and >> FWARC 2009/680) or via a domain service (FWARC/2009/426) >> provided by the logical domains agent daemon (PSARC/2009/459) >> on the control domain. >> >> 4.2 Bug/RFE Number(s) >> >> 6680702 - Want a mechanism for Solaris to know if it is an LDOM >> and if so what type >> >> 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking >> >> 6712763 - Need information about control domain from within a >> guest domain >> >> 4.3 Scope >> >> Not Applicable. >> >> 4.4 Out of Scope >> >> Not Applicable. >> >> 4.5 Interfaces >> >> 4.5.1 Interfaces >> >> 4.5.2 Imported Interfaces >> >> Interface Classification Comments >> >> ================================================================= >> >> Domain Services API Consolidation Private >> PSARC/2008/568 >> (libds.so.1) >> >> Logical Domains Sun Private >> PSARC/2009/459 >> Agents on Solaris >> >> Logical Domains Sun Private >> FWARC/2009/426 >> Agents >> >> Machine Description Sun Private >> FWARC/2005/115 >> Device (/dev/mdesc) >> >> Domain UUID property Consolidation Private >> FWARC/2009/680 >> >> UUID library API Evolving >> PSARC/2002/094 >> (libuuid.so.1) >> >> >> 4.5.3 Exported Interfaces >> >> Interface Classification Comments >> ================================================================ >> >> /usr/sbin/ldminfo Committed See ldminfo(1M) >> /usr/lib/libldoms.so Committed 32-bit library >> /usr/lib/sparcv9/libldoms.so Committed 64-bit library >> /usr/include/libldoms.h Committed Header file >> >> ldoms_capabilities() Committed >> ldoms_domain_roles() Committed >> ldoms_domain_name() Committed >> ldoms_domain_uuid() Committed >> ldoms_control_domain() Committed >> ldoms_platform_serialno() Committed >> >> LDMCAP_SUPPORTED Committed >> LDMCAP_ENABLED Committed >> LDMROLE_CONTROL Committed >> LDMROLE_IO Committed >> LDMROLE_SERVICE Committed >> LDMROLE_ROOT Committed >> >> 4.6 Doc Impact >> >> Man pages for ldminfo (1M), libldoms (3LIB), >> ldoms_capabilities(3LDOMS), ldoms_domain_roles(3LDOMS), >> ldoms_domain_name(3LDOMS), ldoms_domain_uuid(3LDOMS), >> ldoms_control_domain(3LDOMS), ldoms_platform_serialno(3LDOMS) >> >> 4.7 Admin/Config Impact >> >> None. >> >> 4.8 HA Impact >> >> None. >> >> 4.9 I18N/L10N >> >> Not affected. >> >> 4.10 Packaging & Delivery >> >> The Logical Domains Information API library libldoms and >> ldminfo program will be delivered as part of the existing >> Solaris packages SUNWcsl (Solaris 32bit libraries), SUNWcslx >> (Solaris 64bit libraries), SUNWcsu (Solaris User Core), >> SUNWhea (Solaris headers) on Sparc platforms only. >> >> 4.11 Security Impact >> >> None. >> >> 4.12 Dependencies >> >> None. >> >> 5. Reference Documents >> >> PSARC 2008/568 Logical Domain's Domain Services >> PSARC 2009/459 Logical Domain's Agents on Solaris >> FWARC 2005/115 sun4v machine description >> FWARC 2009/680 Domain UUID property >> >> 6. Resources and Schedule >> >> 6.1 Projected Availability >> >> Q4FY10 (S10U9) >> >> 6.2 Cost of Effort >> >> 1 person month >> >> 6.3 Cost of Capital Resources >> >> 6.4 Product Approval Committee requested information >> >> 6.4.1 Consolidation Or Component Name >> >> OS-Networking (ON) >> >> 6.4.3 Type of CPT Approval Expected >> >> FastTrack >> >> 6.4.4 Project Boundary Conditions >> >> 6.4.5 Is this a necessary project for OEM agreements: >> >> No. >> >> 6.4.6 Notes >> >> 6.4.7 Target RTI Date/Release >> >> February 2010 >> >> 6.4.8 Target Code Design Review Date: >> >> 6.4.9 Update approval addition: >> >> Not applicable >> >> 6.5 ARC review type >> >> FastTrack >> >> 6.6 ARC Exposure >> >> open >> >> 7. Prototype Availability: >> >> 7.1 Prototype Availability >> >> A prototype is already available. >> >> 7.2 Prototype Cost: >> >> A prototype is already available. >> >> > > From Michael.Christensen@sun.com Tue Jan 26 16:36:18 2010 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 o0R0aIrA006807 for ; Tue, 26 Jan 2010 16:36:18 -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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id o0R0aGHq011879 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 26 Jan 2010 16:36:18 -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 <0KWV00C0LR0IKK00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 26 Jan 2010 17:36:18 -0700 (MST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KWV000WHR0G7590@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 26 Jan 2010 17:36:17 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id o0R0aB8v027917 for ; Tue, 26 Jan 2010 16:36:16 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KWV00500QXBT400@fe-sfbay-09.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Tue, 26 Jan 2010 16:36:16 -0800 (PST) Received: from [129.153.85.9] ([unknown] [129.153.85.9]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KWV00KACR08MK50@fe-sfbay-09.sun.com>; Tue, 26 Jan 2010 16:36:08 -0800 (PST) Date: Tue, 26 Jan 2010 16:36:07 -0800 From: Mike Christensen Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <4B4E5D65.6040505@Sun.COM> Sender: Michael.Christensen@sun.com To: Richard.Matthews@sun.com Cc: Huay-Yong Wang , PSARC-ext@sun.com, Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com Reply-to: Michael.Christensen@sun.com Message-id: <4B5F8A77.8000806@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_S7chWOWQbBmhA/rPoidb2g)" X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> <4B4E5D65.6040505@Sun.COM> User-Agent: Thunderbird 2.0.0.23 (X11/20090910) Status: RO Content-Length: 10294 This is a multi-part message in MIME format. --Boundary_(ID_S7chWOWQbBmhA/rPoidb2g) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 01/13/10 15:55, Rick Matthews wrote: > There was no meeting scheduled for Jan. 13. > > I believe a question was asked (and if not, I'll ask it) as to why an > LDOMs specific > virtualization query? Would there be a query that could give the caller > "generic" virtualization > information (working for both Zen and LDOMs)? Was this considered? > > Could a generic call identify the virtualization technology, and > then, if needed, technology specific queries could be made? > -- > Rick After discussions with the Xen group, I have reworked this proposal to cater to Xen (and other virtualization technologies) implementing this. This involved mostly name changes (e.g. libldoms in the original proposal is now libv12n, function names are now v12n_* rather than ldoms_*, and manifest constants are now V12N_*) and new bit(s) in the v12n_capabilities function to return virtualization implementation technology. The case materials in the directory have been updated and attached is the new case. Thanks. Mike --Boundary_(ID_S7chWOWQbBmhA/rPoidb2g) Content-type: text/plain; name=virtinfo.arc Content-transfer-encoding: 7BIT Content-disposition: inline; filename=virtinfo.arc 1. Introduction 1.1 Project/Component Working Name Virtualization Domain Information API and virtinfo program 1.2 Name of Document Author/Supplier Michael Christensen 1.3 Date of This Document 19-JAN-2009 1.4 Name of Major Document Customer(s)/Consumer(s) 1.4.1 The PAC or CPT you expect to review your project 1.4.2 The ARC(s) you expect to review your project PSARC 1.4.3 The Director/VP who is sponsoring this project jerriann.meyer@sun.com 1.4.4 The Name of Your Business Unit Solaris Core OS 1.5 Email Aliases 1.5.1 Responsible Manager: jay.jayachandran@sun.com 1.5.2 Responsible Engineer: michael.christensen@sun.com 1.5.3 Marketing Manager: duncan.hardie@sun.com 1.5.4 Interest List: ldoms-internal@sun.com, matrix-eng@sun.com 2. Project Summary 2.1 Project Description This project will implement Virtualization Domain Information API and virtinfo program on Solaris. The API and virtinfo program will provide information about the currently running domain. Among the items that may be provided are: - Virtualization Implementation (LDoms, Xen) - Domain type (control, guest, I/O, service, root) - Virtualization domain name for this domain - Domain Universally Unique ID (UUID) - Domain's control domain/dom0 network nodename - Chassis Serial Number the domain is running on. None of the above items are currently easily obtainable from within a guest domain. As an example, many LDoms customers have expressed a desire to run LDom manager scripts on the control domain initiated from a guest domain. However, there is no easy way to either identify the network nodename of the control domain or to identify the LDom Manager's name for the current domain, which would be required for LDom Manager commands. Further, many LDoms customers have requested a means of uniquely identifying each domain and also identifying the hardware platform that the domain is running on for accounting or resourcing. On the Solaris operating system, the Virtualization Domain Information API will be implemented as a library (libv12n) on Solaris. For sun4v/LDoms this information will be obtain by using the Guest Domain's Machine Description provided by FWARC 2005/115 (sun4v machine description), the sun4v MD uuid property from FWARC 2009/680 (Domain UUID property), the libds library provided by PSARC 2008/568 (Logical Domain's Domain Services) and using domain services provided by the logical domain agent daemon provided by PSARC 2009/459 (Logical Domains Agents on Solaris) and FWARC 2009/426 (Logical Domains Agents). The virtinfo program will utilize the libv12n library to display the various items of information provided. 2.2 Risks and Assumptions None. 3. Business Summary 3.1 Problem Area In an LDoms system, a user program or user has no easy way to identify what type of domain the program is being run on (e.g. control domain, guest domain, I/O domain, service domain). Also a guest domain has no easy way to identify the network nodename of its control domain, what name the LDoms Manager running on the control domain uses to identify this domain, what is the domain's Universally Unique Identifier that The LDoms Manager uses to identify this domain or what the Chassis Serial Number of the platform it is currently running on. 3.2 Market/Requestor See FWARC 2005/633. 3.3 Business Justification See FWARC 2005/633. 3.4 Competitive Analysis The problems listed in 3.1 have been the subject of bug reports from customers. Virtualization solutions provided by competitors have equivalent functionality. 3.5 Opportunity Window/Exposure See FWARC 2005/663. 3.6 How will you know when you are done? The work will be completed when the final code changes to implement Virtualization Domain Information API and virtinfo program are integrated into the Solaris Nevada gate and Solaris 10 Update gates. 4. Technical Description 4.1 Overview On the Solaris operating system, Virtualization Domain Information API will be implemented as a user library "libv12n.so.1" and a user program "virtinfo" will be provided to display this information. For implementation on sun4v/LDoms, this information will be provided either via the sun4v Machine Description (FWARC/2005/115 and FWARC 2009/680) or via a domain service (FWARC/2009/426) provided by the logical domains agent daemon (PSARC/2009/459) on the control domain. 4.2 Bug/RFE Number(s) 6680702 - Want a mechanism for Solaris to know if it is an LDOM and if so what type 6873151 - RFE: unique ID for LDOMs to facillitate asset tracking 6712763 - Need information about control domain from within a guest domain 4.3 Scope Not Applicable. 4.4 Out of Scope Not Applicable. 4.5 Interfaces 4.5.1 Interfaces 4.5.2 Imported Interfaces Interface Classification Comments ================================================================= Domain Services API Consolidation Private PSARC/2008/568 (libds.so.1) Logical Domains Sun Private PSARC/2009/459 Agents on Solaris Logical Domains Sun Private FWARC/2009/426 Agents Machine Description Sun Private FWARC/2005/115 Device (/dev/mdesc) Domain UUID property Consolidation Private FWARC/2009/680 UUID library API Evolving PSARC/2002/094 (libuuid.so.1) 4.5.3 Exported Interfaces Interface Classification Comments ================================================================ /usr/sbin/virtinfo Committed See virtinfo(1M) /usr/lib/libv12n.so Committed 32-bit library /usr/lib/sparcv9/libv12n.so Committed 64-bit library /usr/include/libv12n.h Committed Header file v12n_capabilities() Committed v12n_domain_roles() Committed v12n_domain_name() Committed v12n_domain_uuid() Committed v12n_control_domain() Committed v12n_platform_serialno() Committed V12N_NAME_MAX Committed V12N_CAP_SUPPORTED Committed V12N_CAP_ENABLED Committed V12N_CAP_IMPL_LDOMS Committed V12N_CAP_IMPL_XEN Committed V12N_ROLE_CONTROL Committed V12N_ROLE_DOM0 Committed V12N_ROLE_IO Committed V12N_ROLE_SERVICE Committed V12N_ROLE_ROOT Committed 4.6 Doc Impact Man pages for virtinfo (1M), libv12n (3LIB), v12n_capabilities(3V12N), v12n_domain_roles(3V12N), v12n_domain_name(3V12N), v12n_domain_uuid(3V12N), v12n_ctrl_domain(3V12N), v12n_platform_serialno(3V12N) 4.7 Admin/Config Impact None. 4.8 HA Impact None. 4.9 I18N/L10N Not affected. 4.10 Packaging & Delivery The Virtualization Domain Information API library libv12n and virtinfo program will be delivered as part of the existing Solaris packages SUNWcsl (Solaris libraries), SUNWcsu (Solaris User Core), SUNWhea (Solaris headers) on Sparc platforms only. 4.11 Security Impact None. 4.12 Dependencies None. 5. Reference Documents PSARC 2008/568 Logical Domain's Domain Services PSARC 2009/459 Logical Domain's Agents on Solaris FWARC 2005/115 sun4v machine description FWARC 2009/680 Domain UUID property 6. Resources and Schedule 6.1 Projected Availability Q4FY10 (S10U9) 6.2 Cost of Effort 1 person month 6.3 Cost of Capital Resources 6.4 Product Approval Committee requested information 6.4.1 Consolidation Or Component Name OS-Networking (ON) 6.4.3 Type of CPT Approval Expected FastTrack 6.4.4 Project Boundary Conditions 6.4.5 Is this a necessary project for OEM agreements: No. 6.4.6 Notes 6.4.7 Target RTI Date/Release February 2010 6.4.8 Target Code Design Review Date: 6.4.9 Update approval addition: Not applicable 6.5 ARC review type FastTrack 6.6 ARC Exposure open 7. Prototype Availability: 7.1 Prototype Availability A prototype is already available. 7.2 Prototype Cost: A prototype is already available. --Boundary_(ID_S7chWOWQbBmhA/rPoidb2g)-- From Richard.Matthews@sun.com Thu Jan 28 08:43:52 2010 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 o0SGhquX012822 for ; Thu, 28 Jan 2010 08:43:52 -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.4) with ESMTP id o0SGhjuS030075 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 28 Jan 2010 09:43:52 -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 <0KWY00I1VUH2C100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 28 Jan 2010 08:43:50 -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 <0KWY00G38UH12840@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 28 Jan 2010 08:43:50 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0SGhn3C012243 for ; Thu, 28 Jan 2010 16:43:49 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KWY00300T136K00@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 28 Jan 2010 09:43:49 -0700 (MST) Received: from dhcp-ublm03-9-40.central.sun.com ([unknown] [129.152.9.40]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KWY00KCYUGCKIG0@mail-amer.sun.com>; Thu, 28 Jan 2010 09:43:26 -0700 (MST) Date: Thu, 28 Jan 2010 10:43:26 -0600 From: Rick Matthews Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <4B5F8A77.8000806@Sun.COM> Sender: Richard.Matthews@sun.com To: Michael.Christensen@sun.com Cc: Huay-Yong Wang , PSARC-ext@sun.com, Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com Message-id: <4B61BEAE.6020306@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> <4B4E5D65.6040505@Sun.COM> <4B5F8A77.8000806@Sun.COM> User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Status: RO Content-Length: 1797 Mike, Thanks to you and the team for following up on this, and making the interfaces general to virtualization, rather than LDOMs specific. I believe that will lead to a better user experience. I have re-reviewed this, and offer a +1. -- Rick Mike Christensen wrote: > On 01/13/10 15:55, Rick Matthews wrote: >> There was no meeting scheduled for Jan. 13. >> >> I believe a question was asked (and if not, I'll ask it) as to why an >> LDOMs specific >> virtualization query? Would there be a query that could give the >> caller "generic" virtualization >> information (working for both Zen and LDOMs)? Was this considered? >> >> Could a generic call identify the virtualization technology, and >> then, if needed, technology specific queries could be made? >> -- >> Rick > > After discussions with the Xen group, I have reworked this proposal > to cater to Xen (and other virtualization technologies) implementing > this. This involved mostly name changes (e.g. libldoms in the > original proposal is now libv12n, function names are now > v12n_* rather than ldoms_*, and manifest constants are now > V12N_*) and new bit(s) in the v12n_capabilities function to return > virtualization implementation technology. > > The case materials in the directory have been updated and attached > is the new case. Thanks. > > Mike -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Huay-Yong.Wang@sun.com Wed Feb 3 13:18:09 2010 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 o13LI9BN023013 for ; Wed, 3 Feb 2010 13:18:09 -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.4) with ESMTP id o13LI8re056913 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 3 Feb 2010 14:18:08 -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 <0KXA00C0HB68JO00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 03 Feb 2010 13:18:08 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KXA001AIB6729D0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 03 Feb 2010 13:18:08 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id o13LI7tt011796 for ; Wed, 03 Feb 2010 13:18:07 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KXA00F00B48TZ00@fe-sfbay-10.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 03 Feb 2010 13:18:07 -0800 (PST) Received: from [129.150.226.29] ([unknown] [129.150.226.29]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KXA00K84B62XO50@fe-sfbay-10.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 03 Feb 2010 13:18:07 -0800 (PST) Date: Wed, 03 Feb 2010 13:18:00 -0800 From: Huay-Yong Wang Subject: Re: Logical Domains Information API and ldminfo [PSARC/2010/004 FastTrack timeout 01/14/2010] In-reply-to: <4B61BEAE.6020306@Sun.COM> Sender: Huay-Yong.Wang@sun.com To: PSARC-ext@sun.com Cc: Michael.Christensen@sun.com, Alexandre.Chartre@sun.com, Eric.Sharakan@sun.com Message-id: <4B69E808.8070702@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <201001042300.o04N0tAO001625@sac.sfbay.sun.com> <4B4E5D65.6040505@Sun.COM> <4B5F8A77.8000806@Sun.COM> <4B61BEAE.6020306@Sun.COM> User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) Status: RO Content-Length: 55 fyi. This case is approved in today's psarc meeting.