From sacadmin Tue Aug 25 15:47:42 2009 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 n7PMlglm008972; Tue, 25 Aug 2009 15:47:42 -0700 (PDT) Received: (from dp@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n7PMlg1o008968; Tue, 25 Aug 2009 15:47:42 -0700 (PDT) Date: Tue, 25 Aug 2009 15:47:42 -0700 (PDT) From: Dan Price Message-Id: <200908252247.n7PMlg1o008968@sac.sfbay.sun.com> To: PSARC-record@sac.sfbay.sun.com Subject: Logical Domains Agents on Solaris [PSARC/2009/459 FastTrack timeout 09/01/2009] Status: RO Content-Length: 573 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Logical Domains Agents on Solaris 1.2. Name of Document Author/Supplier: Author: Alexandre Chartre 1.3 Date of This Document: 25 August, 2009 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From dp@eng.sun.com Tue Aug 25 15:53:52 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 n7PMrqI5009317 for ; Tue, 25 Aug 2009 15:53:52 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n7PMrpdw018046 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 25 Aug 2009 15:53:51 -0700 (PDT) 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 <0KOY00A05FKYE500@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 25 Aug 2009 15:53:22 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KOY0098XFKX9Q10@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 25 Aug 2009 15:53:21 -0700 (PDT) Received: from sac (sac.SFBay.Sun.COM [129.146.226.132]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n7PMrLV1542285 for ; Tue, 25 Aug 2009 15:53:21 -0700 (PDT) Date: Tue, 25 Aug 2009 15:53:21 -0700 From: Dan Price Subject: PSARC 2009/459 Logical Domains Agents on Solaris To: psarc-ext@sun.com Message-id: <20090825225317.GA9059@eng.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 User-Agent: Mutt/1.5.14 (2007-02-12) Status: RO Content-Length: 10425 I'm sponsoring the following case, entitled "Logical Domains Agents on Solaris" for Alexandre Chartre. The timer is set for Sep 1 2009. The case and manual page are included below. -dp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Introduction 1.1 Project/Component Working Name Logical Domains Agents on Solaris 1.2 Name of Document Author/Supplier Alexandre Chartre 1.3 Date of This Document 13-AUG-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: alexandre.chartre@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 Agents on Solaris. A Logical Domains Agent is an entity running in a LDoms domain and able to provide information or to interact with the control domain. The full description of Logical Domains Agents is available in FWARC 2009/426 (Logical Domains Agents). On the Solaris operating system, Logical Domains agents will be implemented as a SMF service and a userland daemon using the libds library provided by PSARC 2008/568 (Logical Domain's Domain Services). 2.2 Risks and Assumptions None. 3. Business Summary 3.1 Problem Area In an LDoms system, the control domain has no way to query information about the system configuration of another domain. For example, it is unable to validate a device path which is associated with (i.e., local to) another domain, or to know what release of an operating system another domain is running. This causes various operational problems when creating virtual device services in other domains which in turn are exported to guest domains, or to know if domain is able to support a particular LDoms operation. For example, an LDoms system allows the creation of "service domains" which provide services to other guest domains, such as a domain with a vds (virtual disk service) which can export virtual disk devices to other domains. When exporting devices hosted by a vds in another domain, the user specifies a backend (a simple file, a disk slice, a disk drive, etc.) for the vds device by supplying the filesystem path of that backend. If the user supplies an invalid backend path, the LDoms Manager has currently no way to determine if the path to the backend is valid. Even at the time the service domain is bound, such an error remains undetected. A similar situation occurs when specifying the physical network interface associated with a virtual switch. An example of the type of problem this can cause is when the virtual disk which relies on an invalid backend path is the boot device. In that case, the boot of the domain will fail in a such a way that the cause of the problem is difficult for the user to determine. 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 do not suffer this type of problem. 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 agents 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 agents will be implemented as a SMF service "svc:/ldoms/agents" and a userland daemon "/usr/lib/ldoms/ldmad" using the libds library provided by PSARC/2008/568 (Logical Domain's Domain Services). To simplify Logical Domains installation and deployment and for ease of use, the Logical Domains agents SMF service will be enabled by default. The Logical Domains agents service has to be enabled to ensure proper functionality of all features provided by the domain manager on the control domain. See FWARC/2009/426 for more information about the mechanism used by Logical Domains agents to communicate with the control domain. 4.2 Bug/RFE Number(s) 6813200 Logical Domains Agents 6734518 LDoms needs Domain Service to allow device paths to be validated across domains 6447740 Ldom Mgr should validate specified vdsdev & net-dev entries 6669994 Add a domain service to support OS identification (Solaris) 6506767 Add a domain service to support OS identification (LDoms Manager) 4.3 Scope Not Applicable. 4.4 Out of Scope Not Applicable. 4.5 Interfaces 4.5.1 Interfaces The new interface is embodied in the format of the messages passed between the control domain and the different agents. See FWARC/2009/426. 4.5.2 Imported Interfaces Interface Classification Comments ================================================================= Domain Services API Consolidation Private PSARC/2008/568 (libds.so.1) Service Management Evolving PSARC/2002/547 Facility (SMF) 4.5.3 Exported Interfaces Interface Classification Comments ================================================================ Domain Services ID Sun Private service id ("ldm-agent-device" and "ldm-agent-system") to represent the new agents. See FWARC/2009/426. Agent Message Sun Private Describes format of Formats messages exchanged between the LDoms Manager and the agents. See FWARC/2009/426. 4.6 Doc Impact Man page for the Solaris LDoms agent daemon, ldmad(1M). 4.7 Admin/Config Impact Current behavior: Pathname errors when specifying devices in certain LDoms Manager CLI commands go undetected until a guest domain attempting to use the corresponding service encounters a problem. New behavior: Such pathname errors will be detected by LDoms Manager when binding a domain which references a service for which an invalid path was specified. 4.8 HA Impact None. 4.9 I18N/L10N Not affected. 4.10 Packaging & Delivery The Logical Domains Agents daemon and SMF service will be delivered as part of the existing Solaris LDoms packages (SUNWldomu and SUNWldomr). 4.11 Security Impact None. 4.12 Dependencies None. 5. Reference Documents FWARC 2009/426 Logical Domains Agents PSARC 2008/568 Logical Domain's Domain Services 6. Resources and Schedule 6.1 Projected Availability Q4FY10 (S10U9) 6.2 Cost of Effort 2 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 September 2009 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - System Administration Commands ldmad(1M) NAME ldmad - Logical Domains Agents daemon SYNOPSIS /usr/lib/ldoms/ldmad DESCRIPTION The ldmad daemon is part of the framework that enables Logi- cal Domain agents to run on a Logical Domain. A Logical Do- main agent is a component which interacts with the control domain for providing features or information. ldmad is responsible for running agents on a Logical Domain and must be enabled to ensure proper functionality of all features provided by the domain manager on the control do- main. It is started at boot time and has no configuration options. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | Availability | SUNWldomu | |_____________________________|_____________________________| | Interface Stability | Unstable | |_____________________________|_____________________________| SEE ALSO svcs(1), svcadm(1M), syslog(3C), syslog.conf(4), attri- butes(5), smf(5) ERRORS ldmad uses syslog(3C) to report status and error messages. All of the messages are logged with the LOG_DAEMON facility. Error messages are logged with the LOG_ERR and LOG_NOTICE priorities, and informational messages are logged with the LOG_INFO priority. The default entries in the /etc/syslog.conf file log all the ldmad error messages to the /var/adm/messages log. NOTES The ldmad service is managed by the service management fac- ility, smf(5), under the service identifier: svc:/ldoms/agents:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The service's status can be queried using the svcs(1) command. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp From Darren.Moffat@sun.com Wed Aug 26 01:30:19 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 n7Q8UJJC014964 for ; Wed, 26 Aug 2009 01:30:19 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n7Q8UF30021439 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 26 Aug 2009 01:30:18 -0700 (PDT) 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 <0KOZ0060T6AGIA00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 01:30:16 -0700 (PDT) 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 <0KOZ0047E6AFLN20@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 01:30:16 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n7Q8UEg6001005 for ; Wed, 26 Aug 2009 08:30:15 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KOZ008003SO0C00@fe-emea-10.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 09:30:05 +0100 (BST) Received: from [192.168.1.105] (cpc2-rdng20-2-0-cust917.15-3.cable.virginmedia.com [86.28.167.150]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KOZ00GMI69VIU00@fe-emea-10.sun.com>; Wed, 26 Aug 2009 09:29:55 +0100 (BST) Date: Wed, 26 Aug 2009 09:29:54 +0100 From: Darren J Moffat Subject: Re: PSARC 2009/459 Logical Domains Agents on Solaris In-reply-to: <20090825225317.GA9059@eng.sun.com> Sender: Darren.Moffat@sun.com To: Dan Price Cc: psarc-ext@sun.com Message-id: <4A94F282.6090609@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: <20090825225317.GA9059@eng.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 842 Dan Price wrote: > On the Solaris operating system, Logical Domains agents will > be implemented as a SMF service "svc:/ldoms/agents" and a xvm (ie the Xen derived stuff) on x86 has its services including agents under: svc:/system/xvm/ I expected this case to use svc:/system/ldoms If there are there existing services under svc:/ldoms/ fair enough but otherwise I'd recommend this be under svc:/system since at the moment we only have the following top level hierarchies: svc:/application svc:/milestone svc:/network svc:/system Is it possible and desirable to have a separate SMF service (and thus fault boundary) for the different LDOM services the agents represent or is this really all done as a single fault boundary ? I expected that there would be separate SMF services for disk and network agents. -- Darren J Moffat From Alexandre.Chartre@sun.com Wed Aug 26 09:17: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 n7QGHuZ8014296 for ; Wed, 26 Aug 2009 09:17:56 -0700 (PDT) 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 n7QGHr94028369 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 26 Aug 2009 09:17:56 -0700 (PDT) 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 <0KOZ0030JRXUY700@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 10:17:54 -0600 (MDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KOZ0011URXT4T40@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 10:17:53 -0600 (MDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n7QGHq8B029247 for ; Wed, 26 Aug 2009 16:17:52 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KOZ00A00RE3H600@fe-emea-10.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 17:17:38 +0100 (BST) Received: from [129.146.96.20] ([unknown] [129.146.96.20]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KOZ005IXRXCFLA0@fe-emea-10.sun.com>; Wed, 26 Aug 2009 17:17:38 +0100 (BST) Date: Wed, 26 Aug 2009 09:15:49 -0700 From: Alexandre Chartre Subject: Re: PSARC 2009/459 Logical Domains Agents on Solaris In-reply-to: <4A94F282.6090609@Sun.COM> Sender: Alexandre.Chartre@sun.com To: Darren J Moffat Cc: Dan Price , PSARC-ext@sun.com Message-id: <4A955FB5.5050501@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: <20090825225317.GA9059@eng.sun.com> <4A94F282.6090609@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 1264 Hi Darren, On 08/26/09 01:29, Darren J Moffat wrote: > Dan Price wrote: >> On the Solaris operating system, Logical Domains agents will >> be implemented as a SMF service "svc:/ldoms/agents" and a > > xvm (ie the Xen derived stuff) on x86 has its services including agents > under: svc:/system/xvm/ > > I expected this case to use svc:/system/ldoms > > If there are there existing services under svc:/ldoms/ fair enough but > otherwise I'd recommend this be under svc:/system since at the moment we > only have the following top level hierarchies: There are already existing services under svc:/ldoms/ : svc:/ldoms/vntsd - virtual network terminal server svc:/ldoms/ldmd - LDoms manager > svc:/application > svc:/milestone > svc:/network > svc:/system > > Is it possible and desirable to have a separate SMF service (and thus > fault boundary) for the different LDOM services the agents represent or > is this really all done as a single fault boundary ? I expected that > there would be separate SMF services for disk and network agents. There is a single fault boundary: all LDoms agents are run as a single Solaris daemon (ldmad). Enabling svc:/ldoms/agents starts the ldmad process and thus enables all LDoms agents. alex. From Darren.Moffat@sun.com Wed Aug 26 10:08:45 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 n7QH8iOD016142 for ; Wed, 26 Aug 2009 10:08:45 -0700 (PDT) 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 n7QH8exJ027127 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 26 Aug 2009 11:08:44 -0600 (MDT) 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 <0KOZ00H0HUAJ5100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 26 Aug 2009 10:08:43 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KOZ00D9RUAHW950@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 26 Aug 2009 10:08:42 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n7QH8fAP005006 for ; Wed, 26 Aug 2009 17:08:41 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KOZ00500U9J0J00@fe-emea-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 26 Aug 2009 18:08:32 +0100 (BST) Received: from [192.168.1.105] (cpc2-rdng20-2-0-cust917.15-3.cable.virginmedia.com [86.28.167.150]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KOZ00G5HUA8IUD0@fe-emea-10.sun.com>; Wed, 26 Aug 2009 18:08:32 +0100 (BST) Date: Wed, 26 Aug 2009 18:08:32 +0100 From: Darren J Moffat Subject: Re: PSARC 2009/459 Logical Domains Agents on Solaris In-reply-to: <4A955FB5.5050501@sun.com> Sender: Darren.Moffat@sun.com To: Alexandre Chartre Cc: Dan Price , psarc-ext@sun.com Message-id: <4A956C10.9000409@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: <20090825225317.GA9059@eng.sun.com> <4A94F282.6090609@Sun.COM> <4A955FB5.5050501@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090623) Status: RO Content-Length: 1427 Alexandre Chartre wrote: > > Hi Darren, > > On 08/26/09 01:29, Darren J Moffat wrote: >> Dan Price wrote: >>> On the Solaris operating system, Logical Domains agents will >>> be implemented as a SMF service "svc:/ldoms/agents" and a >> >> xvm (ie the Xen derived stuff) on x86 has its services including >> agents under: svc:/system/xvm/ >> >> I expected this case to use svc:/system/ldoms >> >> If there are there existing services under svc:/ldoms/ fair enough but >> otherwise I'd recommend this be under svc:/system since at the moment >> we only have the following top level hierarchies: > > There are already existing services under svc:/ldoms/ : > > svc:/ldoms/vntsd - virtual network terminal server > svc:/ldoms/ldmd - LDoms manager Okay thanks. >> svc:/application >> svc:/milestone >> svc:/network >> svc:/system >> >> Is it possible and desirable to have a separate SMF service (and thus >> fault boundary) for the different LDOM services the agents represent >> or is this really all done as a single fault boundary ? I expected >> that there would be separate SMF services for disk and network agents. > > There is a single fault boundary: all LDoms agents are run as a single > Solaris daemon (ldmad). Enabling svc:/ldoms/agents starts the ldmad process > and thus enables all LDoms agents. Given the above two answers I'm happy with the case as specified. -- Darren J Moffat From unixconsole@yahoo.com Wed Aug 26 14:12:45 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 n7QLCiKN001649 for ; Wed, 26 Aug 2009 14:12:45 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n7QLCgR4008162 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 26 Aug 2009 22:12:43 +0100 (BST) 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 <0KP000A015L7NL00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 15:12:43 -0600 (MDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KP000DFE5L69ZC0@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 15:12:42 -0600 (MDT) Received: from relay44i.sun.com ([192.5.209.118]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n7QLCgAr013818 for ; Wed, 26 Aug 2009 21:12:42 +0000 (GMT) Received: from mmp43es.mmp.us.syntegra.com ([160.41.221.12] [160.41.221.12]) by relay44i.sun.com with ESMTP id BT-MMP-70730 for psarc-ext@sun.com; Wed, 26 Aug 2009 21:12:42 +0000 (Z) Received: from relay43i.sun.com (relay43i.sun.com [192.5.209.74]) by mmp43es.mmp.us.syntegra.com with ESMTP id BT-MMP-1712988 for psarc-ext@sun.com; Wed, 26 Aug 2009 21:12:40 +0000 (Z) Received: from web30802.mail.mud.yahoo.com ([68.142.200.145] [68.142.200.145]) by relay4i.sun.com id BT-MMP-392675 for psarc-ext@sun.com; Wed, 26 Aug 2009 21:03:59 +0000 (Z) Received: (qmail 12011 invoked by uid 60001); Wed, 26 Aug 2009 21:02:44 +0000 Received: from [67.232.108.234] by web30802.mail.mud.yahoo.com via HTTP; Wed, 26 Aug 2009 14:02:44 -0700 (PDT) Date: Wed, 26 Aug 2009 14:02:44 -0700 (PDT) From: Octave Orgeron Subject: Re: PSARC 2009/459 Logical Domains Agents on Solaris In-reply-to: <20090825225317.GA9059@eng.sun.com> To: Dan Price , psarc-ext@sun.com, Alexandre Chartre Message-id: <299859.11425.qm@web30802.mail.mud.yahoo.com> MIME-version: 1.0 X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251320564; bh=faqvIJZ3RHd0RzfSqx2I3iK0pviSAF7paViqT97iNL8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=I4yP210aSfH955NYHj+jeF9L/6OHeurbbLAsYMb34MqRsExBMpFG07Fr4Kwe0mAM4Y2ZaFwJ5Bp3MBCr2Rpz3BJckl8tX394mYBZdfYL4Rc2yY0qRk/N6HpdSNhQdTkk6JsAG2ZTM/xhI6jnzUzNVWbBnjrmInoxlDb67HcQCIM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JbnaVDx10R1jVxjmlOsNwFfqNh2g1CZGNOANy5/evsAYaYvReORSbGJd5uRKwzAxURZ9PFwe8C9O+HC+yP+NYoxqyQOqWYC9UynbnfTwimJBqoR581d/qX0Fs/6VouoXxbYnEddfrBS0glCts0XFPbtlZZ6O7wJLOUC8na9tpSI=; X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-YMail-OSG: udtleGQVM1mb7tOZaV58viTsa_sWUZWHNr3ks1M.aG8eDbUj6yIwNBRUkuFnnxS4dsjhJeWuqQ2JgosNCakTPLNVtYOGKI5Hue287oR32DWuzzpZa_KS3MZ0xYFH.46_BCWundr5gxR1FkOlgHZ85PhuQ1jtC9LdAbLqVHSvgnIfq7T9shtND.bbm.sGpRYvjOrv26lOLprxZIQFnJ.W2kCgVHdnZ7feTJEyVPcN6hx5M5_iOjUoH490ZxGYPztk55sqXJ6pLkWONKPkaUKILCogeI2Oq_s6JcuKWd.TtDwyO78zNcwHJwJ10BGV9Y5AWcu0bdcttbHR3I2Ug0PxynLDqQK4N.9VNiaDdmbwH1f4.FGg0YVijZ.c3558d9na X-Antispam: No, score=-2.6/5.0, scanned in 0.204sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <20090825225317.GA9059@eng.sun.com> Status: RO Content-Length: 11816 Hi, Looks like a very useful and necessary service going forward for LDoms. Would this be enabled across all SPARC installs or just sun4v? I believe the vntsd and drd SMF servces are only installed and enabled by default on sun4v platforms. Also, would inter-domain traffic flow over the same control LDC channel for each domain, or would it require a separate LDC channel? Thanks *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: unixconsole@yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Dan Price To: psarc-ext@sun.com Sent: Tuesday, August 25, 2009 5:53:21 PM Subject: PSARC 2009/459 Logical Domains Agents on Solaris I'm sponsoring the following case, entitled "Logical Domains Agents on Solaris" for Alexandre Chartre. The timer is set for Sep 1 2009. The case and manual page are included below. -dp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Introduction 1.1 Project/Component Working Name Logical Domains Agents on Solaris 1.2 Name of Document Author/Supplier Alexandre Chartre 1.3 Date of This Document 13-AUG-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: alexandre.chartre@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 Agents on Solaris. A Logical Domains Agent is an entity running in a LDoms domain and able to provide information or to interact with the control domain. The full description of Logical Domains Agents is available in FWARC 2009/426 (Logical Domains Agents). On the Solaris operating system, Logical Domains agents will be implemented as a SMF service and a userland daemon using the libds library provided by PSARC 2008/568 (Logical Domain's Domain Services). 2.2 Risks and Assumptions None. 3. Business Summary 3.1 Problem Area In an LDoms system, the control domain has no way to query information about the system configuration of another domain. For example, it is unable to validate a device path which is associated with (i.e., local to) another domain, or to know what release of an operating system another domain is running. This causes various operational problems when creating virtual device services in other domains which in turn are exported to guest domains, or to know if domain is able to support a particular LDoms operation. For example, an LDoms system allows the creation of "service domains" which provide services to other guest domains, such as a domain with a vds (virtual disk service) which can export virtual disk devices to other domains. When exporting devices hosted by a vds in another domain, the user specifies a backend (a simple file, a disk slice, a disk drive, etc.) for the vds device by supplying the filesystem path of that backend. If the user supplies an invalid backend path, the LDoms Manager has currently no way to determine if the path to the backend is valid. Even at the time the service domain is bound, such an error remains undetected. A similar situation occurs when specifying the physical network interface associated with a virtual switch. An example of the type of problem this can cause is when the virtual disk which relies on an invalid backend path is the boot device. In that case, the boot of the domain will fail in a such a way that the cause of the problem is difficult for the user to determine. 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 do not suffer this type of problem. 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 agents 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 agents will be implemented as a SMF service "svc:/ldoms/agents" and a userland daemon "/usr/lib/ldoms/ldmad" using the libds library provided by PSARC/2008/568 (Logical Domain's Domain Services). To simplify Logical Domains installation and deployment and for ease of use, the Logical Domains agents SMF service will be enabled by default. The Logical Domains agents service has to be enabled to ensure proper functionality of all features provided by the domain manager on the control domain. See FWARC/2009/426 for more information about the mechanism used by Logical Domains agents to communicate with the control domain. 4.2 Bug/RFE Number(s) 6813200 Logical Domains Agents 6734518 LDoms needs Domain Service to allow device paths to be validated across domains 6447740 Ldom Mgr should validate specified vdsdev & net-dev entries 6669994 Add a domain service to support OS identification (Solaris) 6506767 Add a domain service to support OS identification (LDoms Manager) 4.3 Scope Not Applicable. 4.4 Out of Scope Not Applicable. 4.5 Interfaces 4.5.1 Interfaces The new interface is embodied in the format of the messages passed between the control domain and the different agents. See FWARC/2009/426. 4.5.2 Imported Interfaces Interface Classification Comments ================================================================= Domain Services API Consolidation Private PSARC/2008/568 (libds.so.1) Service Management Evolving PSARC/2002/547 Facility (SMF) 4.5.3 Exported Interfaces Interface Classification Comments ================================================================ Domain Services ID Sun Private service id ("ldm-agent-device" and "ldm-agent-system") to represent the new agents. See FWARC/2009/426. Agent Message Sun Private Describes format of Formats messages exchanged between the LDoms Manager and the agents. See FWARC/2009/426. 4.6 Doc Impact Man page for the Solaris LDoms agent daemon, ldmad(1M). 4.7 Admin/Config Impact Current behavior: Pathname errors when specifying devices in certain LDoms Manager CLI commands go undetected until a guest domain attempting to use the corresponding service encounters a problem. New behavior: Such pathname errors will be detected by LDoms Manager when binding a domain which references a service for which an invalid path was specified. 4.8 HA Impact None. 4.9 I18N/L10N Not affected. 4.10 Packaging & Delivery The Logical Domains Agents daemon and SMF service will be delivered as part of the existing Solaris LDoms packages (SUNWldomu and SUNWldomr). 4.11 Security Impact None. 4.12 Dependencies None. 5. Reference Documents FWARC 2009/426 Logical Domains Agents PSARC 2008/568 Logical Domain's Domain Services 6. Resources and Schedule 6.1 Projected Availability Q4FY10 (S10U9) 6.2 Cost of Effort 2 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 September 2009 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - System Administration Commands ldmad(1M) NAME ldmad - Logical Domains Agents daemon SYNOPSIS /usr/lib/ldoms/ldmad DESCRIPTION The ldmad daemon is part of the framework that enables Logi- cal Domain agents to run on a Logical Domain. A Logical Do- main agent is a component which interacts with the control domain for providing features or information. ldmad is responsible for running agents on a Logical Domain and must be enabled to ensure proper functionality of all features provided by the domain manager on the control do- main. It is started at boot time and has no configuration options. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | Availability | SUNWldomu | |_____________________________|_____________________________| | Interface Stability | Unstable | |_____________________________|_____________________________| SEE ALSO svcs(1), svcadm(1M), syslog(3C), syslog.conf(4), attri- butes(5), smf(5) ERRORS ldmad uses syslog(3C) to report status and error messages. All of the messages are logged with the LOG_DAEMON facility. Error messages are logged with the LOG_ERR and LOG_NOTICE priorities, and informational messages are logged with the LOG_INFO priority. The default entries in the /etc/syslog.conf file log all the ldmad error messages to the /var/adm/messages log. NOTES The ldmad service is managed by the service management fac- ility, smf(5), under the service identifier: svc:/ldoms/agents:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The service's status can be queried using the svcs(1) command. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp _______________________________________________ opensolaris-arc mailing list opensolaris-arc@opensolaris.org From alexandre.chartre@sun.com Wed Aug 26 14:22:38 2009 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 n7QLMcZk001809 for ; Wed, 26 Aug 2009 14:22:38 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n7QLMbG2027545 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 26 Aug 2009 14:22:38 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KP000H0L61OBM00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 14:22:36 -0700 (PDT) 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 <0KP0008LT61NXQ60@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 14:22:36 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n7QLMZfA009378 for ; Wed, 26 Aug 2009 21:22:35 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KP000L005UX4E00@fe-emea-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 26 Aug 2009 22:22:18 +0100 (BST) Received: from [129.146.96.20] ([unknown] [129.146.96.20]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KP0005P9612HB60@fe-emea-09.sun.com>; Wed, 26 Aug 2009 22:22:17 +0100 (BST) Date: Wed, 26 Aug 2009 14:20:12 -0700 From: Alexandre Chartre Subject: Re: PSARC 2009/459 Logical Domains Agents on Solaris In-reply-to: <299859.11425.qm@web30802.mail.mud.yahoo.com> Sender: alexandre.chartre@sun.com To: Octave Orgeron Cc: Dan Price , psarc-ext@sun.com Message-id: <4A95A70C.1050907@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: <20090825225317.GA9059@eng.sun.com> <299859.11425.qm@web30802.mail.mud.yahoo.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 12518 Hi Octave, > Looks like a very useful and necessary service going forward for LDoms. Would > this be enabled across all SPARC installs or just sun4v? I believe the vntsd > and drd SMF servces are only installed and enabled by default on sun4v platforms. This will only be on sun4v: the LDoms Agents will be part of the LDoms packages which are only installed on sun4v platforms. In addition the SMF start method will check that the platform is effectively sun4v before starting the service. > Also, would inter-domain traffic flow over the same control LDC channel for each > domain, or would it require a separate LDC channel? The agents service is implemented using the userland domain services (libds, PSARC 2008/568 Logical Domain's Domain Services) which uses a single LDC channel for each domain. alex. > ----- Original Message ---- > From: Dan Price > To: psarc-ext@sun.com > Sent: Tuesday, August 25, 2009 5:53:21 PM > Subject: PSARC 2009/459 Logical Domains Agents on Solaris > > > I'm sponsoring the following case, entitled "Logical Domains Agents on > Solaris" for Alexandre Chartre. The timer is set for Sep 1 2009. > > The case and manual page are included below. > > -dp > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > 1. Introduction > > 1.1 Project/Component Working Name > > Logical Domains Agents on Solaris > > 1.2 Name of Document Author/Supplier > > Alexandre Chartre > > 1.3 Date of This Document > > 13-AUG-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: alexandre.chartre@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 Agents on > Solaris. A Logical Domains Agent is an entity running in a > LDoms domain and able to provide information or to interact > with the control domain. The full description of Logical > Domains Agents is available in FWARC 2009/426 (Logical Domains > Agents). > > On the Solaris operating system, Logical Domains agents will > be implemented as a SMF service and a userland daemon using > the libds library provided by PSARC 2008/568 (Logical Domain's > Domain Services). > > 2.2 Risks and Assumptions > > None. > > 3. Business Summary > > 3.1 Problem Area > > In an LDoms system, the control domain has no way to query > information about the system configuration of another domain. > For example, it is unable to validate a device path which is > associated with (i.e., local to) another domain, or to know > what release of an operating system another domain is running. > This causes various operational problems when creating virtual > device services in other domains which in turn are exported to > guest domains, or to know if domain is able to support a > particular LDoms operation. > > For example, an LDoms system allows the creation of "service > domains" which provide services to other guest domains, such > as a domain with a vds (virtual disk service) which can export > virtual disk devices to other domains. When exporting devices > hosted by a vds in another domain, the user specifies a > backend (a simple file, a disk slice, a disk drive, etc.) > for the vds device by supplying the filesystem path of that > backend. > > If the user supplies an invalid backend path, the LDoms > Manager has currently no way to determine if the path to the > backend is valid. Even at the time the service domain is > bound, such an error remains undetected. A similar situation > occurs when specifying the physical network interface > associated with a virtual switch. > > An example of the type of problem this can cause is when the > virtual disk which relies on an invalid backend path is the > boot device. In that case, the boot of the domain will fail > in a such a way that the cause of the problem is difficult for > the user to determine. > > 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 do not suffer this type of problem. > > 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 agents 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 agents will > be implemented as a SMF service "svc:/ldoms/agents" and a > userland daemon "/usr/lib/ldoms/ldmad" using the libds > library provided by PSARC/2008/568 (Logical Domain's Domain > Services). To simplify Logical Domains installation and > deployment and for ease of use, the Logical Domains agents SMF > service will be enabled by default. The Logical Domains agents > service has to be enabled to ensure proper functionality of > all features provided by the domain manager on the control > domain. > > See FWARC/2009/426 for more information about the mechanism > used by Logical Domains agents to communicate with the control > domain. > > 4.2 Bug/RFE Number(s) > > 6813200 Logical Domains Agents > > 6734518 LDoms needs Domain Service to allow device paths to be > validated across domains > > 6447740 Ldom Mgr should validate specified vdsdev & net-dev entries > > 6669994 Add a domain service to support OS identification (Solaris) > > 6506767 Add a domain service to support OS identification (LDoms Manager) > > 4.3 Scope > > Not Applicable. > > 4.4 Out of Scope > > Not Applicable. > > 4.5 Interfaces > > 4.5.1 Interfaces > > The new interface is embodied in the format of the > messages passed between the control domain and the > different agents. See FWARC/2009/426. > > 4.5.2 Imported Interfaces > > Interface Classification Comments > ================================================================= > > Domain Services API Consolidation Private PSARC/2008/568 > (libds.so.1) > > Service Management Evolving PSARC/2002/547 > Facility (SMF) > > > 4.5.3 Exported Interfaces > > Interface Classification Comments > ================================================================ > > Domain Services ID Sun Private service id ("ldm-agent-device" > and "ldm-agent-system") to > represent the new agents. > See FWARC/2009/426. > > Agent Message Sun Private Describes format of > Formats messages exchanged between > the LDoms Manager and the > agents. See FWARC/2009/426. > > 4.6 Doc Impact > > Man page for the Solaris LDoms agent daemon, ldmad(1M). > > 4.7 Admin/Config Impact > > Current behavior: > > Pathname errors when specifying devices in certain LDoms Manager CLI > commands go undetected until a guest domain attempting to use the > corresponding service encounters a problem. > > New behavior: > > Such pathname errors will be detected by LDoms Manager when binding > a domain which references a service for which an invalid path was > specified. > > 4.8 HA Impact > > None. > > 4.9 I18N/L10N > > Not affected. > > 4.10 Packaging & Delivery > > The Logical Domains Agents daemon and SMF service will be > delivered as part of the existing Solaris LDoms packages > (SUNWldomu and SUNWldomr). > > 4.11 Security Impact > > None. > > 4.12 Dependencies > > None. > > 5. Reference Documents > > FWARC 2009/426 Logical Domains Agents > PSARC 2008/568 Logical Domain's Domain Services > > 6. Resources and Schedule > > 6.1 Projected Availability > > Q4FY10 (S10U9) > > 6.2 Cost of Effort > > 2 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 > > September 2009 > > 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. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > System Administration Commands ldmad(1M) > > NAME > ldmad - Logical Domains Agents daemon > > SYNOPSIS > /usr/lib/ldoms/ldmad > > DESCRIPTION > The ldmad daemon is part of the framework that enables Logi- > cal Domain agents to run on a Logical Domain. A Logical Do- > main agent is a component which interacts with the control > domain for providing features or information. > > ldmad is responsible for running agents on a Logical Domain > and must be enabled to ensure proper functionality of all > features provided by the domain manager on the control do- > main. It is started at boot time and has no configuration > options. > > ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > ____________________________________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE | > |_____________________________|_____________________________| > | Availability | SUNWldomu | > |_____________________________|_____________________________| > | Interface Stability | Unstable | > |_____________________________|_____________________________| > > > SEE ALSO > svcs(1), svcadm(1M), syslog(3C), syslog.conf(4), attri- > butes(5), smf(5) > > ERRORS > ldmad uses syslog(3C) to report status and error messages. > All of the messages are logged with the LOG_DAEMON facility. > Error messages are logged with the LOG_ERR and LOG_NOTICE > priorities, and informational messages are logged with the > LOG_INFO priority. The default entries in the > /etc/syslog.conf file log all the ldmad error messages to > the /var/adm/messages log. > > NOTES > The ldmad service is managed by the service management fac- > ility, smf(5), under the service identifier: > > svc:/ldoms/agents:default > > Administrative actions on this service, such as enabling, > disabling, or requesting restart, can be performed using > svcadm(1M). The service's status can be queried using the > svcs(1) command. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > >