tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
Vivek Titarmare
Vivek.Titarmare at Sun.COM
Wed May 6 04:34:38 PDT 2009
Hi Tom/Margot,
--cut--
Also, from the project page, it would seem like the AF_TIPC family of socket
interface is a significant interface that should be listed in the exported
table, and that Volo (PSARC 2007/587) is a significant imported interface,
especially as the Volo interfaces for adding new socket families are all
either Project Private or Consolidation Private to ON, while this states
it's targeting SFW, so would need contracts.
[VIVEK]: The code changes are such that we do not require Volo for running TIPC. The socket families are implemented in the TIPC code itself. So the interfaces of volo would not be required by TIPC. We can use Volo, however for this to work we need to change the TIPC code.
Let me know if you require more details on the same.
Best Regards,
~Vivek R. Titarmare
-----Original Message-----
From: Margot Miller [mailto:Margot.Miller at Sun.COM]
Sent: Tuesday, May 05, 2009 10:02 PM
To: Vivek Titarmare
Cc: 'Mark A. Carlson'; 'Tom Childers'; lsarc-ext at sun.com; psarc-ext at sun.com
Subject: Re: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
Vivek,
You still need to address Alan's issue:
Also, from the project page, it would seem like the AF_TIPC family of socket
interface is a significant interface that should be listed in the exported
table, and that Volo (PSARC 2007/587) is a significant imported interface,
especially as the Volo interfaces for adding new socket families are all
either Project Private or Consolidation Private to ON, while this states
it's
targeting SFW, so would need contracts.
Please read over the entire mail log for the case and make sure
every issue has been addressed.
http://sac.eng/arc/LSARC/2009/239/mail
Thanks
Margot
Vivek Titarmare wrote:
> Resending to add to the logs.
>
> Thanks,
> ~Vivek R. Titarmare
>
> -----Original Message-----
> From: Vivek Titarmare [mailto:Vivek.Titarmare at Sun.com]
> Sent: Monday, May 04, 2009 11:24 AM
> To: 'Margot Miller'
> Cc: 'Mark A. Carlson'; 'Tom Childers'
> Subject: RE: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
>
> Hi Morgot,
>
> Yes, I had replied to TOM's mail.
> About tipc-config: it is removed from the material and so the man pages would not be required.
>
> Thanks,
> ~Vivek R. Titarmare
>
> -----Original Message-----
> From: Margot Miller [mailto:Margot.Miller at Sun.COM]
> Sent: Thursday, April 30, 2009 10:46 PM
> To: Vivek Titarmare
> Cc: 'Mark A. Carlson'; Tom Childers
> Subject: Re: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
>
> Hi Vivek,
>
> Did you respond to Tom Childer's email? I noticed
> that it isn't in the mail log- there was some problems
> with sac losing mail. TOM, do you have the email
> you sent out with your issues on this case? I
> remember one of them was about tipc-config but
> can't remember the other ones. Thanks!
>
> Also, please reread the email log and make sure you have
> answered every email thread -
> http://sac.sfbay/LSARC/2009/239/mail
>
> Ex.
>
> From Alan:
>
> But the project page says:
>
>> TIPC then ensures that only applications within that portion of the network
>> (i.e. the same node, the same cluster, or the same zone) can access the port
>> using that name.
>>
>
> Also, from the project page, it would seem like the AF_TIPC family of socket
> interface is a significant interface that should be listed in the exported
> table, and that Volo (PSARC 2007/587) is a significant imported interface,
> especially as the Volo interfaces for adding new socket families are all
> either Project Private or Consolidation Private to ON, while this states it's
> targeting SFW, so would need contracts.
>
> Thanks
> Margot
>
>
> Vivek Titarmare wrote:
>
>> Hi Margot,
>>
>> Yes, I have replied to almost all Alan's mail. And hoping that all issues are resolved.
>>
>> Thanks,
>> ~Vivek R. Titarmare
>>
>> -----Original Message-----
>> From: Margot Miller [mailto:Margot.Miller at Sun.COM]
>> Sent: Wednesday, April 29, 2009 8:32 PM
>> To: Vivek Titarmare
>> Cc: 'Mark A. Carlson'
>> Subject: Re: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
>>
>> Hi Vivek,
>>
>> The best thing to do would be to reply to Alan's email and answer
>> each point directly that he raises.
>>
>> It's good that you have updated the materials but we need to ensure
>> that each issue has been addressed and maybe Alan will still
>> have issues with your replies. So if you address each of his
>> issues in the email thread we make sure that nothing falls through
>> the cracks.
>>
>> Please look over the mail log and make sure that all issues
>> have been addressed by responding to each email. I have
>> found a few issues in this case or pdsh (can't remember
>> which) that were never addressed.
>>
>> Also, I would suggest not sending emails out with status. I think
>> that is fine to Mark and me and a few others but the aliases
>> that you are sending out to have about a hundred people on
>> them.
>>
>> Thanks
>> Margot
>>
>> Vivek Titarmare wrote:
>>
>>
>>> Hi Alan,
>>>
>>> I have update the man pages and the FOSS check list. Will send the material to Mark for review.
>>>
>>> Thanks,
>>> ~Vivek R. Titarmare
>>>
>>> -----Original Message-----
>>> From: Alan.Coopersmith at Sun.COM [mailto:Alan.Coopersmith at Sun.COM]
>>> Sent: Tuesday, April 28, 2009 10:30 PM
>>> To: Mark A. Carlson
>>> Cc: Vivek Titarmare; psarc-ext at sun.com; LSARC-ext at sun.com
>>> Subject: Re: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
>>>
>>> The case materials are inconsistent - the delivery location is still
>>> listed as /opt in:
>>> materials/FOSS_tipc.txt - Section 3.1.1S
>>> materials/tipc.1
>>> materials/tipc.txt
>>>
>>> but as /usr in:
>>> materials/FOSS_tipc.txt - Section 4.0
>>> materials/Fasttrack_tipc.txt
>>>
>>> Is the /usr location correct and the others just missed in updating?
>>>
>>> Also, I thought the headers under the solaris directory were not going
>>> to be packaged because they weren't needed by consumers, but they're listed
>>> here - did I misunderstand that?
>>>
>>> BTW, section 1 (i.e. tipc(1) or .../man1/tipc.1) is incorrect for the man
>>> page - section 1 is for commands you run, while libraries appear in section
>>> 3 and network interfaces in section 7. For a list of sections and to see
>>> what man pages are in each, see:
>>> http://docs.sun.com/app/docs/coll/40.10
>>>
>>>
>>> -alan-
>>>
>>> Mark A. Carlson wrote:
>>>
>>>
>>>
>>>> The case directory has been updated with new materials.
>>>>
>>>> Any last issues before I close this case?
>>>>
>>>> -- mark
>>>>
>>>> Vivek Titarmare wrote:
>>>>
>>>>
>>>>
>>>>> Hi Alan,
>>>>>
>>>>> Yes, we are prepared. I should be doing the required changes and update the ARC case accordingly.
>>>>>
>>>>> Thanks,
>>>>> ~Vivek R. Titarmare
>>>>>
>>>>> -----Original Message-----
>>>>> From: Alan.Coopersmith at Sun.COM [mailto:Alan.Coopersmith at Sun.COM]
>>>>> Sent: Wednesday, April 22, 2009 7:44 PM
>>>>> To: Vivek Titarmare
>>>>> Cc: 'Joerg Schilling'; Darren.Moffat at Sun.COM; PSARC-ext at sun.com; LSARC-ext at sun.com
>>>>> Subject: Re: tipc Ver 1.7.6 [LSARC/2009/239 FastTrack timeout 04/20/2009]
>>>>>
>>>>> Vivek Titarmare wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Hi Joerg,
>>>>>>
>>>>>> In this we have to change the source code. Pl. suggest.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> Integrating to Solaris often involves changing the source code.
>>>>> If you're not prepared to do this, you're not prepared to own
>>>>> the product, fix bugs and maintain it long term.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> <http://www.sun.com> * Mark A. Carlson *
>>>> Sr. Architect
>>>>
>>>> *Systems Group*
>>>> Phone x69559 / 303-223-6139
>>>> Email Mark.Carlson at Sun.COM
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>
More information about the opensolaris-arc
mailing list