This note serves as signatures from both the Supplier and Consumer of this
contract. The contract (Contract-01) has been posted to the case directory.
--
Rick Matthews

On 08/13/08 13:43, Gregory Matthews wrote:
> Allan, Paul, Diana,
>
> Rick tells me you need the acsls contract.  Attached with Mike's 
> agreement.
>
>  - Gregor
>
> Begin forwarded message:
>
>> *From:* "Michael P. Williams" <Michael.P.Williams at Sun.COM 
>> <mailto:Michael.P.Williams at Sun.COM>>
>> *Date:* May 16, 2008 2:19:27 PM CDT
>> *To:* Gregory Matthews <Gregory.Matthews at Sun.COM 
>> <mailto:Gregory.Matthews at Sun.COM>>
>> *Cc:* Michael.P.Williams at Sun.COM <mailto:Michael.P.Williams at Sun.COM>
>> *Subject:* *Re: Whoops, wrong Mike again.*
>>
>> Agreed
>>
>> Gregory Matthews wrote:
>>> Mike P. Williams!
>>>
>>> I just realized I sent this to the wrong Mike again.  Sorry.  I also 
>>> added
>>> a couple more interfaces that we do use.
>>>
>>> Thx,
>>>
>>> - Gregor
>>> ==============================================================
>>>
>>> Mike,
>>>
>>> I'd like to get this MMS/CDK contract signed this week of possible.
>>>
>>> Here are some of the changes I made:
>>>
>>> * Removed the SAM-QFS references, as it seems like they will need
>>>  a separate contract and are on different timelines than us.  This is an
>>>  MMS - CDK contract only.  Impacted section 3, 4, and 7c.
>>>
>>> * Updated the language specifying the CDK per Mitch.
>>>
>>> * Double-checked our interfaces in section 4 per Mitch.
>>>
>>> * Signed and dated for MMS.
>>>
>>> Mike, I'd appreciate it if you add your name and date.  I'm also 
>>> sending to
>>> Rick Matthews, as he will file with our PSARC case.
>>>
>>> Let me know if you concur, or need additional changes/info.  Thanks 
>>> much,
>>>
>>> - Gregor
>>>
>>>
>>> CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES
>>>
>>> 0. Number: PSARC/2007/420-01
>>>
>>> 1. This contract is between
>>>    a SUPPLIER of INTERFACES and
>>>    a CONSUMER of those INTERFACES,
>>> both of whom are entities within Sun Microsystems, Incorporated.
>>>
>>> 2. The SUPPLIER (definer and/or implementor) is identified by the 
>>> following:
>>> Product or Bundle: CSC Developer's Toolkit (CDK) Version 2.3
>>> Consolidation: Unbundled
>>> Department or Group: Systems/Network Storage/ACSLS development
>>> Bugster Product/Category/SubCategory:
>>> Responsible Manager: Mike Williams
>>>
>>> 3. The CONSUMER is identified by the following:
>>> Product or Bundle: Media Management System (MMS)
>>> Consolidation: MMS - NWS
>>> Department or Group: Software/Solaris/Archive Products Group
>>> Bugster Product/Category/SubCategory: mms
>>> Responsible Manager: Gregory Matthews
>>>
>>> 4. The INTERFACES are:
>>>
>>> MMS builds shared versions of these libraries. If you follow the 
>>> steps in the CDK 2.3 user guide
>>> you will build the static libraries, libcl.a libutl.a etc...)
>>>
>>>  libcl.so (libcl.a)
>>>  libutl.so (libutl.a)
>>>  libapi.so (libapi.a)
>>>  libipc.so (libipc.a)
>>>  libssixdr.so  (SSIXDR.a)
>>>
>>> MMS uses the following binaries: mini_el, ssi
>>>
>>> MMS uses a modified version of t_ssi.sh
>>>   Types used in lm_acs.h:
>>>
>>> SAM-QFS Includes (via src/robots/stk/stk.h):
>>> ACS_RESPONSE_TYPE
>>> SEQ_NO
>>> REQ_ID
>>> ALIGNED_BYTES
>>>
>>> Functions called by LM:
>>>
>>> Interface                                  Stability Level
>>> =========                                  ===============
>>> acs_type_response                          Contracted Project Private
>>> acs_query_server                           Contracted Project Private
>>> acs_query_drive                            Contracted Project Private
>>> acs_query_mount                            Contracted Project Private
>>> acs_query_volume                           Contracted Project Private
>>> acs_query_cap                              Contracted Project Private
>>> acs_status                                 Contracted Project Private
>>> acs_display                                Contracted Project Private
>>> acs_state                                  Contracted Project Private
>>> acs_response                               Contracted Project Private
>>> acs_enter                                  Contracted Project Private
>>> acs_eject                                  Contracted Project Private
>>> acs_mount                                  Contracted Project Private
>>> acs_dismount                               Contracted Project Private
>>> acs_get_packet_version                     Contracted Project Private
>>> acs_type                                   Contracted Project Private
>>> acs_query_lsm                              Contracted Project Private
>>>
>>> 5. The ARC controlling these INTERFACES is: PSARC
>>>
>>> 6. The CASE describing (Exporting) these INTERFACES is: TBD (ACSLS 
>>> is still in the
>>> PSARC process.
>>>
>>> 7. The following SPECIAL ARRANGEMENTS are made which modify the rules
>>> imposed by the stability levels listed in section 4 above:
>>>
>>> 7c. Although the stability level doesn't normally allow it, CONSUMER 
>>> will
>>>  import INTERFACES from a separate consolidation.
>>>
>>> 7d. If SUPPLIER decides to change (including replace or remove) any
>>>  portion of the INTERFACES, SUPPLIER will notify CONSUMER of the
>>>  proposed new version, no later than the application for ARC
>>>  approval of the new version.
>>>  If SUPPLIER and CONSUMER are contained in the same consolidation,
>>>  they have the option of arranging for simultaneous conversion
>>>  to the new interfaces.  If this is not possible, or if they are
>>>  not in the same consolidation, then SUPPLIER will either make best
>>>  effort to work with CONSUMER so that CONSUMER can detect which
>>>  version of INTERFACES is being supplied, or else SUPPLIER will
>>>  make best effort to supply both old and new versions of
>>>  INTERFACES.
>>>  If SUPPLIER cannot make both versions of INTERFACES available,
>>>  and SUPPLIER and CONSUMER cannot devise a method whereby
>>>  CONSUMER can detect which version of INTERFACES is being
>>>  supplied, and the old version of CONSUMER will not run with the
>>>  new version of SUPPLIER, then either the EOL process must be
>>>  followed by SUPPLIER, or else a major release of SUPPLIER will
>>>  be required, or the change will not be allowed.
>>>
>>> 8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make
>>> best effort to accommodate such changes, which shall then be
>>> treated in accordance with paragraph 7 above.
>>>
>>> 9. Notwithstanding paragraphs 7 and 8, a change to any portion
>>> of the INTERFACES shall be regarded as a completely new set of
>>> INTERFACES which require both ARC approval and execution of
>>> a new contract.
>>>
>>> 10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be
>>>  handled as follows:
>>>
>>>  SUPPLIER notifies CONSUMER, when changes are planned.
>>>
>>> 11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
>>>  follows:
>>>
>>>  CONSUMER is responsible for adapting to changed interfaces.
>>>
>>> 12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
>>>  follows:
>>>
>>>  SUPPLIER is responsible for documentation of these interfaces.
>>>
>>> 13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
>>>  tested as follows:
>>>
>>>  CONSUMER is responsible for testing interface.
>>>
>>> 14. SUPPLIER and CONSUMER agree that this contract can be terminated as
>>>  follows:
>>>
>>>   By mutual agreement.
>>>
>>> 15. This contract is not valid until "signed" via agreement from the
>>>  SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by
>>>  this contract.  E-mail agreement to the contract should be archived
>>>  in the mail archive of CASE; verbal agreement to the contract
>>>  should be noted in the meeting minutes.  This contract remains
>>>  valid until superseded or invalidated.
>>>
>>> For SUPPLIER:Mike Williams                   Date: 05/13/08
>>> For CONSUMER: Gregory Matthews  Date: 05/13/08
>>> For ARC:                        Date:
>>>
>>> A copy of this contract shall be deposited in the CASE directory as
>>> "contract-<digits>" or in a "contracts" subdirectory.
>>>
>>> 16. (Not to be filled in until superseded or invalidated.)
>>>  This contract was superseded or invalidated by CASE:
>>>  For ARC:                    Date:
>>>


-- 
---------------------------------------------------------------------
Rick Matthews                           email: Rick.Matthews at sun.com
Sun Microsystems, Inc.                  phone:+1(651) 554-1518
1270 Eagan Industrial Road              phone(internal): 54418
Suite 160                               fax:  +1(651) 554-1540
Eagan, MN 55121-1231 USA                main: +1(651) 554-1500          
---------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080813/7d39cefd/attachment.html>

Reply via email to