+1 John
Vivek Titarmare wrote: > Thank you John, I have updated the Fasttrack and attached is the updated > document. > > Thanks, > ~Vivek R. Titarmare > > -----Original Message----- > From: John.Fischer at Sun.COM [mailto:John.Fischer at Sun.COM] > Sent: Thursday, May 07, 2009 11:56 PM > To: Vivek Titarmare > Cc: LSARC-ext at sun.com > Subject: Re: pywbem Ver 0.7 [LSARC/2009/258 FastTrack timeout 05/05/2009] > > Vivek, > > Python 2.4 and 2.5 are no longer supposed to be used by Sun projects. > That is what the Obsolete modifier tells the engineering community. > > Please also remove: > > >> The script file would go in "usr/bin/pywbem/" > > from the document. Once this is done I'll give you a +1. > > Thanks, > > John > > Vivek Titarmare wrote: >> Hi John, >> >> Thanks for the information. Also, on Python 2.4 & 2.5 which is still on > the >> build machines, do we really need to be removed from the ARC case > material. >> Pl. suggest. >> >> I have removed the Python 2.4 & 2.5 from the interface table and have > update >> rest of the information. >> Let me know if I am missing any in the attached ARC case material. >> >> Thanks, >> ~Vivek R. Titarmare >> >> >> -----Original Message----- >> From: John.Fischer at Sun.COM [mailto:John.Fischer at Sun.COM] >> Sent: Thursday, May 07, 2009 9:18 PM >> To: John.Fischer at Sun.COM >> Cc: Vivek Titarmare; Mark.Carlson at Sun.COM; LSARC-ext at sun.com >> Subject: Re: pywbem Ver 0.7 [LSARC/2009/258 FastTrack timeout 05/05/2009] >> >> Vivek, >> >> Of course, the formating of the interface tables got messed up by >> Thunderbird. So I'll let you work that part out. The Exported >> interface table should be similar to: >> >> pyweb >> Instance Provider >> EnumerateInstanceNames() >> >> or something like that. Pyweb would be the only line with an >> explicit definition of Uncommitted. >> >> Also now that I think about it you do not need to mention Python2.4 >> or Python2.5 as the project should not even support these releases. >> >> Thanks, >> >> John >> >> >> John Fischer wrote: >>> Vivek, >>> >>> This still isn't quite correct. The imported interface table needs to >>> be more like: >>> >>> Imported interface Classification Comments >>> ======================= ============== >>> =================================== >>> Python2.4 Committed Obsolete To run the pywbem scripts >>> Python2.5 Committed Obsolete To run the pywbem scripts >>> Python2.6 Uncommitted To run the pywbem scripts >>> Python3.0 Uncommitted To run the pywbem scripts >>> /usr/lib/python2.6/vendor-packages directory for Python 2.6 >>> Uncommitted modules shipped by Sun >>> see PSARC/2006/666 >>> /usr/lib/python3.0/vendor-packages directory for >>> Python 3.0 >>> Uncommitted modules shipped by Sun >>> see PSARC/2006/666 >>> >>> Furthermore, the project is producing a Python Module called pywbem. >>> This module needs to work with Python2.6 and Python3.0 and be installed >>> into /usr/lib/python2.6/vendor-packages and >>> /usr/lib/python3.0/vendor-packages. Thus the addition of the >>> directories into the imported interface table. >>> >>> Since the project is providing the pyweb.py script file it should also >>> provide the compiled bytecode (i.e., pyweb.pyc). Is this also planned? >>> >>> At least one of the following: >>> >>> pyweb module >>> pyweb.py >>> pyweb.pyc >>> >>> should be included in the Exported interface table. Listing the pyweb >>> module makes the most sense. The export interface table might look >>> something like: >>> >>> Exported Interface Classification Comment >>> -------------------------- ------------------ ---------------- >>> SUNWpyweb Uncommitted Package name >>> pyweb Uncommitted Python module >>> >>> Then if you want you can list the various operations below the pyweb. >>> So the interface table might look like: >>> >>> >>> Exported Interface Classification Comment >>> -------------------------- ------------------ ---------------- >>> SUNWpyweb Uncommitted Package name >>> pyweb Uncommitted Python module >>> Instance Provider CIM Operation Calls >>> EnumerateInstanceNames() >>> EnumerateInstances() >>> GetInstance() >>> ... >>> >>> With these changes I would be happy with the document. >>> >>> Thanks, >>> >>> John >>> >>> >>> Vivek Titarmare wrote: >>>> Hi Mark, >>>> >>>> >>>> >>>> The changes related to multiple Python version is done. Now this >>>> library can work with Python 2.4, 2.5, 2.6 and 3.0 versions. >>>> >>>> Also, the man page is to be removed from the ARC material. >>>> >>>> Attached is the updated ARC case material. >>>> >>>> Can you pl. help up upload the new ARC case material. >>>> >>>> >>>> >>>> Let me know if I need to and anything extra in this case material. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> ~Vivek R. Titarmare >>>> >>>> >>>> >>>> *From:* Mark.Carlson at Sun.COM [mailto:Mark.Carlson at Sun.COM] >>>> *Sent:* Tuesday, May 05, 2009 11:21 PM >>>> *To:* LSARC-ext at Sun.Com >>>> *Cc:* Vivek.Titarmare at Sun.COM >>>> *Subject:* Re: pywbem Ver 0.7 [LSARC/2009/258 FastTrack timeout >>>> 05/05/2009] >>>> >>>> >>>> >>>> The timer on this case has been extended to Friday 05/08/2009 >>>> to give additional time for review. >>>> >>>> -- mark >>>> >>>> Mark Carlson wrote: >>>> >>>> I am sponsoring this familiarity case for Vivek Titarmare. It requests >>>> minor binding and times out 05/05/2009. >>>> >>>> >>>> >>>> -- mark >>>> >>>> >>>> >>>> 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: >>>> >>>> pywbem Ver 0.7 >>>> >>>> 1.2. Name of Document Author/Supplier: >>>> >>>> Author: Vivek Titarmare >>>> >>>> 1.3 Date of This Document: >>>> >>>> 28 April, 2009 >>>> >>>> >>>> >>>> 2. Project Summary >>>> >>>> 2.1 Project Description >>>> >>>> >>>> >>>> Python WBEM Client and Provider Interface >>>> >>>> >>>> 4. Technical Description: >>>> >>>> >>>> >>>> PyWBEM is a Python library for making CIM operations over HTTP >>>> using the WBEM CIM-XML protocol. It is based on the idea that a good >>>> WBEM client should be easy to use and not necessarily require a large >>>> amount of programming knowlege. PyWBEM is suitable for a large range >>>> of tasks from simply poking around to writing web and GUI applications. >>>> >>>> >>>> >>>> 5. Interfaces >>>> >>>> >>>> The script file "pywbem" contains following interface. >>>> >>>> >>>> >>>> Exported interface Classification >>>> Interface type >>>> >>>> ============================= ============== >>>> ============== >>>> >>>> Instance Provider Uncommitted CIM >>>> Operation Calls >>>> >>>> EnumerateInstanceNames() >>>> EnumerateInstances() >>>> GetInstance() >>>> ModifyInstance() >>>> DeleteInstance() >>>> CreateInstance() >>>> Method Provider Uncommitted CIM >>>> Operation Calls >>>> >>>> InvokeMethod() >>>> Association Provider Uncommitted CIM >>>> Operation Calls >>>> >>>> Associators() >>>> AssociatorNames() >>>> References() >>>> ReferenceNames()() >>>> Schema Management Uncommitted CIM >>>> Operation Calls >>>> >>>> EnumerateClassNames() >>>> EnumerateClasses() >>>> GetClass() >>>> >>>> >>>> >>>> Imported interface Classification Comments >>>> >>>> ======================= ============== >>>> =================================== >>>> python committed To sun the pywbem scripts >>>> >>>> >>>> >>>> The script file would go in "usr/share/pywbem/" >>>> >>>> >>>> >>>> >>>> >>>> 6. Resources and Schedule >>>> >>>> 6.4. Steering Committee requested information >>>> >>>> 6.4.1. Consolidation C-team Name: >>>> >>>> SFW >>>> >>>> 6.5. ARC review type: FastTrack >>>> >>>> 6.6. ARC Exposure: open >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> <http://www.sun.com> >>>> >>>> >>>> >>>> *Mark A. Carlson * >>>> Sr. Architect >>>> >>>> *Systems Group* >>>> Phone x69559 / 303-223-6139 >>>> Email Mark.Carlson at Sun.COM <mailto:Mark.Carlson at Sun.COM> >>>> >>>> >>>> >>>> >>>>
