From Sebastien.Roy@sun.com Mon Aug 4 13:20:26 2008 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 m74KKQqQ029488 for ; Mon, 4 Aug 2008 13:20:26 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m74KKOlK005944 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 4 Aug 2008 13:20:26 -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 <0K5300A1PF628Q00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Mon, 04 Aug 2008 13:20:26 -0700 (PDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5300A34F607200@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Mon, 04 Aug 2008 13:20:25 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m74KKON5020371 for ; Mon, 04 Aug 2008 20:20:24 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5300E01F1MAN00@mail-amer.sun.com> (original mail from Sebastien.Roy@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 04 Aug 2008 14:20:24 -0600 (MDT) Received: from [10.0.0.100] ([72.45.167.130]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K53003CHF5ZED50@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 04 Aug 2008 14:20:24 -0600 (MDT) Date: Mon, 04 Aug 2008 16:20:22 -0400 From: Sebastien Roy Subject: PSARC 2008/498 datalink sysevents Sender: Sebastien.Roy@sun.com To: psarc-ext Cc: Cathy Zhou Message-id: <1217881222.1098.6.camel@seb> Organization: Sun Microsystems MIME-version: 1.0 X-Mailer: Evolution 2.22.2 Content-type: text/plain Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 1112 I'm submitting this case for Cathy Zhou. It is being filed as closed approved automatic. Datalink sysevents ------------------ release binding: patch Summary ------- This case proposes to introduce a new EC_DATALINK sysevent class to report data-link related sysevents. For now, only one subclass (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated when a new physical data-link shows up on the system. In the future, the EC_DATALINK sysevent class can be extended to report other data-link sysevents, such as a data-link renaming event. Since we are still experimenting the new sysevent class, the format of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project Private. Interface Table --------------- ------------------------------------------------------------- Interface Commitment Level Comments ------------------------------------------------------------- EC_DATALINK Consolidation Private Event class ESC_DATALINK_PHYS_ADD Project Private Event subclass From Kais.Belgaied@sun.com Tue Aug 5 00:23:17 2008 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 m757N6Iu018352 for ; Tue, 5 Aug 2008 00:23:17 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m757Mmue025681; Tue, 5 Aug 2008 08:22:57 +0100 (BST) 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 <0K5400L039U9GN00@nwk-avmta-2.sfbay.sun.com>; Tue, 05 Aug 2008 00:22:57 -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 <0K5400KST9U85ZE0@nwk-avmta-2.sfbay.sun.com>; Tue, 05 Aug 2008 00:22:57 -0700 (PDT) Received: from [129.146.11.145] (sr1-jurassic-02.SFBay.Sun.COM [129.146.11.145]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m757MuJm468954; Tue, 05 Aug 2008 00:22:56 -0700 (PDT) Date: Tue, 05 Aug 2008 00:22:56 -0700 From: Kais Belgaied Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <1217881222.1098.6.camel@seb> To: Sebastien Roy Cc: psarc-ext , Cathy Zhou Reply-to: Kais.Belgaied@sun.com Message-id: <4897FFD0.9030909@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> User-Agent: Thunderbird 2.0.0.12 (X11/20080228) Status: RO Content-Length: 1274 completeness question: who's the intended consumer for this event? Kais Sebastien Roy wrote: > I'm submitting this case for Cathy Zhou. It is being filed as closed > approved automatic. > > Datalink sysevents > ------------------ > > release binding: patch > > Summary > ------- > > This case proposes to introduce a new EC_DATALINK sysevent class to > report data-link related sysevents. For now, only one subclass > (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated > when a new physical data-link shows up on the system. In the future, > the EC_DATALINK sysevent class can be extended to report other > data-link sysevents, such as a data-link renaming event. > > Since we are still experimenting the new sysevent class, the format > of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project > Private. > > Interface Table > --------------- > > ------------------------------------------------------------- > Interface Commitment Level Comments > ------------------------------------------------------------- > EC_DATALINK Consolidation Private Event class > ESC_DATALINK_PHYS_ADD Project Private Event subclass > > > > From Cathy.Zhou@sun.com Tue Aug 5 10:26:17 2008 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 m75HQGWO007536 for ; Tue, 5 Aug 2008 10:26:16 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m75HQCLV012281 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 5 Aug 2008 18:26:15 +0100 (BST) 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 <0K550000B1RQFE00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 10:26:14 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K55000AT1RP4200@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 10:26:14 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m75HQCZN017003 for ; Tue, 05 Aug 2008 17:26:12 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5500H011MH8G00@mail-apac.sun.com> (original mail from Cathy.Zhou@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 01:26:12 +0800 (SGT) Received: from [129.146.104.84] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K55009111RM8FBD@mail-apac.sun.com>; Wed, 06 Aug 2008 01:26:12 +0800 (SGT) Date: Tue, 05 Aug 2008 10:25:22 -0700 From: Cathy Zhou Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <4897FFD0.9030909@Sun.COM> Sender: Cathy.Zhou@sun.com To: Kais.Belgaied@sun.com Cc: Sebastien Roy , psarc-ext Message-id: <48988D02.3010603@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> <4897FFD0.9030909@Sun.COM> User-Agent: Thunderbird 2.0.0.12 (X11/20080422) Status: RO Content-Length: 1539 This event will be consumed by a syseventd module which in turn will generate a RCM event which will then be consumed by the RCM modules. But the usage of the EC_DATALINK class would not be limited to this. - Cathy > completeness question: who's the intended consumer for this event? > > Kais > > Sebastien Roy wrote: >> I'm submitting this case for Cathy Zhou. It is being filed as closed >> approved automatic. >> >> Datalink sysevents >> ------------------ >> >> release binding: patch >> >> Summary >> ------- >> >> This case proposes to introduce a new EC_DATALINK sysevent class to >> report data-link related sysevents. For now, only one subclass >> (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated >> when a new physical data-link shows up on the system. In the future, >> the EC_DATALINK sysevent class can be extended to report other >> data-link sysevents, such as a data-link renaming event. >> >> Since we are still experimenting the new sysevent class, the format >> of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project >> Private. >> >> Interface Table >> --------------- >> >> ------------------------------------------------------------- >> Interface Commitment Level Comments >> ------------------------------------------------------------- >> EC_DATALINK Consolidation Private Event class >> ESC_DATALINK_PHYS_ADD Project Private Event subclass >> >> >> >> > From gdamore@Sun.COM Tue Aug 5 10:34:35 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m75HYYRp007691 for ; Tue, 5 Aug 2008 10:34:34 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m75HYQdJ018734 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 01:34:33 +0800 (SGT) 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 <0K5500D0J25KQQ00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 11:34:32 -0600 (MDT) 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 <0K55003VC25IGM80@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 11:34:30 -0600 (MDT) 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 m75HYUC1027087 for ; Tue, 05 Aug 2008 10:34:30 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5500M011PGR000@fe-sfbay-10.sun.com> (original mail from gdamore@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 10:34:30 -0700 (PDT) Received: from [10.7.251.172] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K55000IM25D6IC0@fe-sfbay-10.sun.com>; Tue, 05 Aug 2008 10:34:26 -0700 (PDT) Date: Tue, 05 Aug 2008 10:29:20 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <48988D02.3010603@sun.com> Sender: Garrett.Damore@Sun.COM To: Cathy Zhou Cc: Kais.Belgaied@Sun.COM, Sebastien Roy , psarc-ext Message-id: <48988DF0.8000903@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> <4897FFD0.9030909@Sun.COM> <48988D02.3010603@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 1778 RCM is "normally" (historically, anyway) used for device *removal*, rather than addition. What do you intend the RCM module to do with this event? -- Garrett Cathy Zhou wrote: > This event will be consumed by a syseventd module which in turn will > generate a RCM event which will then be consumed by the RCM modules. > > But the usage of the EC_DATALINK class would not be limited to this. > > - Cathy > >> completeness question: who's the intended consumer for this event? >> >> Kais >> >> Sebastien Roy wrote: >>> I'm submitting this case for Cathy Zhou. It is being filed as closed >>> approved automatic. >>> >>> Datalink sysevents >>> ------------------ >>> >>> release binding: patch >>> >>> Summary >>> ------- >>> >>> This case proposes to introduce a new EC_DATALINK sysevent class to >>> report data-link related sysevents. For now, only one subclass >>> (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated >>> when a new physical data-link shows up on the system. In the >>> future, >>> the EC_DATALINK sysevent class can be extended to report other >>> data-link sysevents, such as a data-link renaming event. >>> >>> Since we are still experimenting the new sysevent class, the format >>> of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project >>> Private. >>> >>> Interface Table >>> --------------- >>> >>> ------------------------------------------------------------- >>> Interface Commitment Level Comments >>> ------------------------------------------------------------- >>> EC_DATALINK Consolidation Private Event class >>> ESC_DATALINK_PHYS_ADD Project Private Event subclass >>> >>> >>> >>> >> > From Cathy.Zhou@sun.com Tue Aug 5 10:36:10 2008 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 m75HaAsE007792 for ; Tue, 5 Aug 2008 10:36:10 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m75Ha87S010111 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 5 Aug 2008 10:36:09 -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 <0K5500M01289T600@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 10:36:09 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5500MAX2875510@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 10:36:08 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m75Ha7gH013629 for ; Tue, 05 Aug 2008 17:36:07 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5500L01277II00@mail-apac.sun.com> (original mail from Cathy.Zhou@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 01:36:07 +0800 (SGT) Received: from [129.146.104.84] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5500BD1285RGTS@mail-apac.sun.com>; Wed, 06 Aug 2008 01:36:07 +0800 (SGT) Date: Tue, 05 Aug 2008 10:35:14 -0700 From: Cathy Zhou Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <48988DF0.8000903@sun.com> Sender: Cathy.Zhou@sun.com To: "Garrett D'Amore" Cc: Kais.Belgaied@sun.com, Sebastien Roy , psarc-ext Message-id: <48988F52.8060600@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> <4897FFD0.9030909@Sun.COM> <48988D02.3010603@sun.com> <48988DF0.8000903@sun.com> User-Agent: Thunderbird 2.0.0.12 (X11/20080422) Status: RO Content-Length: 1986 RCM is also used to restore all the configuration when the device is plugged back in and that is when this sysevent will be used. - Cathy > RCM is "normally" (historically, anyway) used for device *removal*, > rather than addition. > > What do you intend the RCM module to do with this event? > > -- Garrett > > Cathy Zhou wrote: >> This event will be consumed by a syseventd module which in turn will >> generate a RCM event which will then be consumed by the RCM modules. >> >> But the usage of the EC_DATALINK class would not be limited to this. >> >> - Cathy >> >>> completeness question: who's the intended consumer for this event? >>> >>> Kais >>> >>> Sebastien Roy wrote: >>>> I'm submitting this case for Cathy Zhou. It is being filed as closed >>>> approved automatic. >>>> >>>> Datalink sysevents >>>> ------------------ >>>> >>>> release binding: patch >>>> >>>> Summary >>>> ------- >>>> >>>> This case proposes to introduce a new EC_DATALINK sysevent class to >>>> report data-link related sysevents. For now, only one subclass >>>> (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated >>>> when a new physical data-link shows up on the system. In the >>>> future, >>>> the EC_DATALINK sysevent class can be extended to report other >>>> data-link sysevents, such as a data-link renaming event. >>>> >>>> Since we are still experimenting the new sysevent class, the format >>>> of the ESC_DATALINK_PHYS_ADD sysevent will be classified as Project >>>> Private. >>>> >>>> Interface Table >>>> --------------- >>>> >>>> ------------------------------------------------------------- >>>> Interface Commitment Level Comments >>>> ------------------------------------------------------------- >>>> EC_DATALINK Consolidation Private Event class >>>> ESC_DATALINK_PHYS_ADD Project Private Event subclass >>>> >>>> >>>> >>>> >>> >> > From gdamore@sun.com Tue Aug 5 12:28:05 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m75JS5Wf011313 for ; Tue, 5 Aug 2008 12:28:05 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m75JS3Qq021615 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 5 Aug 2008 12:28:04 -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 <0K5500D1L7ESG000@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 12:28:04 -0700 (PDT) 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 <0K55000H57ER46B0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 12:28:03 -0700 (PDT) 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 m75JS3Bd024825 for ; Tue, 05 Aug 2008 12:28:03 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5500G0178CCB00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 05 Aug 2008 12:28:03 -0700 (PDT) Received: from [10.7.251.172] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5500D5G7EQX120@fe-sfbay-09.sun.com>; Tue, 05 Aug 2008 12:28:03 -0700 (PDT) Date: Tue, 05 Aug 2008 12:22:57 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <48988F52.8060600@sun.com> Sender: Garrett.Damore@sun.com To: Cathy Zhou Cc: Kais.Belgaied@sun.com, Sebastien Roy , psarc-ext Message-id: <4898A891.2060707@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> <4897FFD0.9030909@Sun.COM> <48988D02.3010603@sun.com> <48988DF0.8000903@sun.com> <48988F52.8060600@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 2676 Thanks for the clarification. (I wasn't aware that RCM was being used this way. I recall that once upon a time there was a separate "sysevent" architecture where insertion events were handled without RCM interposing. The point, at the time, of having a separate RCM from sysevent was that RCM could "interpose", and ultimately "refuse" certain operations, based on consuming nodes. Of course, this goes back to the Solaris 8 timeframes and the design discussions I had surrounding RCM. Ancient history, now. Anyway, your suggested usage seems sane to me.) -- Garrett Cathy Zhou wrote: > RCM is also used to restore all the configuration when the device is > plugged back in and that is when this sysevent will be used. > > - Cathy > >> RCM is "normally" (historically, anyway) used for device *removal*, >> rather than addition. >> >> What do you intend the RCM module to do with this event? >> >> -- Garrett >> >> Cathy Zhou wrote: >>> This event will be consumed by a syseventd module which in turn will >>> generate a RCM event which will then be consumed by the RCM modules. >>> >>> But the usage of the EC_DATALINK class would not be limited to this. >>> >>> - Cathy >>> >>>> completeness question: who's the intended consumer for this event? >>>> >>>> Kais >>>> >>>> Sebastien Roy wrote: >>>>> I'm submitting this case for Cathy Zhou. It is being filed as closed >>>>> approved automatic. >>>>> >>>>> Datalink sysevents >>>>> ------------------ >>>>> >>>>> release binding: patch >>>>> >>>>> Summary >>>>> ------- >>>>> >>>>> This case proposes to introduce a new EC_DATALINK sysevent >>>>> class to >>>>> report data-link related sysevents. For now, only one subclass >>>>> (ESC_DATALINK_PHYS_ADD) will be introduced. It will be generated >>>>> when a new physical data-link shows up on the system. In the >>>>> future, >>>>> the EC_DATALINK sysevent class can be extended to report other >>>>> data-link sysevents, such as a data-link renaming event. >>>>> >>>>> Since we are still experimenting the new sysevent class, the >>>>> format >>>>> of the ESC_DATALINK_PHYS_ADD sysevent will be classified as >>>>> Project >>>>> Private. >>>>> >>>>> Interface Table >>>>> --------------- >>>>> >>>>> ------------------------------------------------------------- >>>>> Interface Commitment Level Comments >>>>> ------------------------------------------------------------- >>>>> EC_DATALINK Consolidation Private Event class >>>>> ESC_DATALINK_PHYS_ADD Project Private Event subclass >>>>> >>>>> >>>>> >>>>> >>>> >>> >> > From Kais.Belgaied@sun.com Tue Aug 5 14:45:42 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m75LjfWJ017177 for ; Tue, 5 Aug 2008 14:45:42 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m75LjZr9014806; Wed, 6 Aug 2008 05:45:37 +0800 (SGT) 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 <0K5500A05DRZ8G00@nwk-avmta-2.sfbay.sun.com>; Tue, 05 Aug 2008 14:45:35 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K55008TEDRYZR10@nwk-avmta-2.sfbay.sun.com>; Tue, 05 Aug 2008 14:45:34 -0700 (PDT) Received: from [129.146.11.145] (sr1-jurassic-02.SFBay.Sun.COM [129.146.11.145]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m75LjYZT171437; Tue, 05 Aug 2008 14:45:34 -0700 (PDT) Date: Tue, 05 Aug 2008 14:45:34 -0700 From: Kais Belgaied Subject: Re: PSARC 2008/498 datalink sysevents In-reply-to: <4898A891.2060707@sun.com> To: "Garrett D'Amore" Cc: Cathy Zhou , Sebastien Roy , psarc-ext Reply-to: Kais.Belgaied@sun.com Message-id: <4898C9FE.1080803@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <1217881222.1098.6.camel@seb> <4897FFD0.9030909@Sun.COM> <48988D02.3010603@sun.com> <48988DF0.8000903@sun.com> <48988F52.8060600@sun.com> <4898A891.2060707@sun.com> User-Agent: Thunderbird 2.0.0.12 (X11/20080228) Status: RO Content-Length: 2836 Garrett D'Amore wrote: > Thanks for the clarification. ditto. Kais > > (I wasn't aware that RCM was being used this way. I recall that once > upon a time there was a separate "sysevent" architecture where > insertion events were handled without RCM interposing. The point, at > the time, of having a separate RCM from sysevent was that RCM could > "interpose", and ultimately "refuse" certain operations, based on > consuming nodes. Of course, this goes back to the Solaris 8 > timeframes and the design discussions I had surrounding RCM. Ancient > history, now. Anyway, your suggested usage seems sane to me.) > > -- Garrett > > > Cathy Zhou wrote: >> RCM is also used to restore all the configuration when the device is >> plugged back in and that is when this sysevent will be used. >> >> - Cathy >> >>> RCM is "normally" (historically, anyway) used for device *removal*, >>> rather than addition. >>> >>> What do you intend the RCM module to do with this event? >>> >>> -- Garrett >>> >>> Cathy Zhou wrote: >>>> This event will be consumed by a syseventd module which in turn >>>> will generate a RCM event which will then be consumed by the RCM >>>> modules. >>>> >>>> But the usage of the EC_DATALINK class would not be limited to this. >>>> >>>> - Cathy >>>> >>>>> completeness question: who's the intended consumer for this event? >>>>> >>>>> Kais >>>>> >>>>> Sebastien Roy wrote: >>>>>> I'm submitting this case for Cathy Zhou. It is being filed as >>>>>> closed >>>>>> approved automatic. >>>>>> >>>>>> Datalink sysevents >>>>>> ------------------ >>>>>> >>>>>> release binding: patch >>>>>> >>>>>> Summary >>>>>> ------- >>>>>> >>>>>> This case proposes to introduce a new EC_DATALINK sysevent >>>>>> class to >>>>>> report data-link related sysevents. For now, only one subclass >>>>>> (ESC_DATALINK_PHYS_ADD) will be introduced. It will be >>>>>> generated >>>>>> when a new physical data-link shows up on the system. In the >>>>>> future, >>>>>> the EC_DATALINK sysevent class can be extended to report other >>>>>> data-link sysevents, such as a data-link renaming event. >>>>>> >>>>>> Since we are still experimenting the new sysevent class, the >>>>>> format >>>>>> of the ESC_DATALINK_PHYS_ADD sysevent will be classified as >>>>>> Project >>>>>> Private. >>>>>> >>>>>> Interface Table >>>>>> --------------- >>>>>> >>>>>> ------------------------------------------------------------- >>>>>> Interface Commitment Level Comments >>>>>> ------------------------------------------------------------- >>>>>> EC_DATALINK Consolidation Private Event class >>>>>> ESC_DATALINK_PHYS_ADD Project Private Event subclass >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > >