Logistics
Roll-call
Other
Business
Business
In Order
Action
Items & Motions
References
Meeting Date |
09/18/2002 |
Meeting Time |
9:00 pm PDT |
Location |
Face-to-Face: Cisco Building 21, San Jose Dial-in Number: To be added International: To be added |
Duration |
9:00 AM to 5:00 PM |
Chair |
Winston Bumpus |
Recording Secretary |
Hedy Alban |
Agenda |
As published [1] |
|
|
|
Member (before Sept 4) |
4-Sep |
9/18/2002 (F2F) |
Alan
Davies |
AD |
SeeBeyond |
Y |
N |
Regrets |
Anand
Akela |
AA |
HP |
Y |
N |
N |
Andrea
Westerinen |
AW |
Cisco |
Y |
Y |
Y |
Andreas
Maier |
AM |
IBM |
Y |
Y |
Y |
Aravinda
Gollapudi |
AG |
Verisign |
Y |
N |
N |
Darran
Rolls |
DR |
Waveset |
Y |
N |
N |
Dennis Ho |
DH |
Iona |
Y |
N |
N |
Dick
Spellman |
DS |
Sun
Microsystems Inc. |
Y |
N |
Y |
Ellen
Stokes |
ES |
IBM |
Y |
N |
N |
Fred
Carter |
FC |
|
Y |
Y |
Y |
Gil
Kirkpatrick |
GK |
NetPro |
Y |
Y |
N |
Guru Bhat |
GB |
Sun
Microsystems Inc. |
Y |
N |
N |
Heather
Kreger |
HK |
IBM |
Y |
Y |
Y |
Hedy
Alban |
HED |
Max
Shevet Consulting |
Y |
Y |
Y |
Homayoun
Pourheidari |
HP |
HP |
Y |
Y |
Y |
Jim
Willits |
JW |
HP |
Y |
Y |
Y |
Julie
Schott |
JS |
Cisco |
Y |
Y |
Y |
Ken
Crozier |
KC |
Cisco |
Y |
Y |
Y |
Karl
Schopmeyer |
KS2 |
Independent |
Y |
Y |
Y |
Krishna
Sankar |
KS1 |
Cisco |
Y |
Y |
N |
Michael
Thatcher |
MT |
Microsoft |
Y |
Y |
Y |
Robert
Baafi |
RB |
Iona |
Y |
N |
N |
Sekhar
Saukkai |
SS |
Corporate
Oxygen Inc. |
Y |
N |
N |
Srinivas
Vadhri |
SV |
CommerceOne |
Y |
N |
N |
Veena
Subrahmanyam |
VS |
HP |
Y |
Y |
Y |
Winston
Bumpus |
WB |
Novell |
Y |
Y |
Y |
|
|
|
|
|
|
New
Members |
|
|
|
|
|
Kevin
Brinkley |
KB |
Intel |
1/3 |
N |
N |
Jim Davis |
JD |
Sun |
2/3 |
N |
N |
Bart
Whitely |
BW |
Caldera
International |
1/3 |
N |
N |
George
Ariola |
GA |
Web Serv
Mgmt Co |
N |
Y |
Y |
George
Erricson |
GE |
EMC |
1/3 |
N |
N |
Richard
Nikula |
RN |
BMC |
N |
Y |
Y |
Ravi
Fernando |
RS |
HP |
N |
N |
Y |
Igor
Sedukhin |
IS |
|
N |
N |
N |
Bill
Dunigan |
BD |
Cyclone
Commerce |
N |
N |
N |
Jeff
Boulin |
JB |
WebMethods |
N |
N |
Y |
Yoshimasa
Masuoka |
YM |
Hitachi |
N |
N |
Y |
Takaki
Kuroda |
TK |
Hitachi |
N |
N |
Y |
WB |
|
|
Minutes |
|
Minutes of Sept 4 meeting were approved as amended. The amendment stated that Karl Schopmeyer will assume responsibility for the Requirements document and will maintain it on an ongoing basis. |
|
OASIS TC Process Update |
|
Winston reviewed changes that were made this month to the OASIS TC Process. These are: (1) The process for submitting a specification for review, comment, and voting has been shortened. A specification is accepted with a majority vote of OASIS members. Ten percent constitutes a quorum for this purpose. (2) TC members are required to attend two consecutive meetings out of the previous three. If a member fails to maintain this level of attendance, the committee chair will dispatch a warning notice and, if the member fails to attend the following meeting, s/he will cease to be a member of the committee. To re-establish membership, the member must contact the chairperson and attend three consecutive meetings. However, each member may receive one leave of absence per calendar year during which attendance requirements are suspended. |
|
OMI Presentation |
|
Veena led the OMI presentation that covered highlights, architecture, current status, and future of the OMI. Co-authored by HP and WebMethods, the purpose of OMI is to connect the business process layer of management information with the lower layers of management information. OMI is based on XML and SOAP over http. OMI provides the interface between the OMI client and server. It is up to the vendors to supply the interface, including discovery, between the server and the vendor’s product; each vendor can implement this interface in its own way. The protocol is in an early phase of development; tiered levels, for example, are still in development. The protocol is lightweight and generic. It should be possible to map it to any model developed with XML, including CIM. OMI supports notifications, both push and pull. It has a small object dictionary. CIM was not used as the basis of objects in OMI because it was felt that CIM is too large and expensive; perhaps if it could be slivered that it would be more usable. Ken Crozier asked whether it was possible for a vendor product to access an OMI directly, bypassing the server. Veena said that this capability is not available directly out of the box. |
|
CIM/WBEM Presentation |
|
Julie reviewed history, major features and goals of the CIM specification. Some discussion items were inheritance, separation of policy content from policy model, information-based roles, metric for unit of work. She also discussion the customer support consortium: Consortium for Service Innovation (CSI) -- how to define .known problems and fixes. Currently there is no CIM SOAP specification. CIM does not have migration, copy, backup/restore. These are extrinsic methods – extensions to the core CIM functions. |
|
Hitachi over SOAP presentation |
|
Yoshi reviewed the TrueNorth specification. Hitachi’s TrueNorth provides a CIM/SOAP over http protocol for storage management. Hitachi is looking for a wider and more generic SOAP specification that encompasses more than storage. This standard should avoid the need for multiple WSDL definitions for each type of message. Hitachi chose SOAP for TrueNorth because they believe it is more flexible and will be compatible with future web services as they emerge. TrueNorth has a single WSDL definition; everything else is inside the message. |
|
W3C Presentation
|
|
Heather reviewed the goals and requirements defined by W3C
for Management and Provisioning, and listed the specifications under
development in the Management Task Force, Web Services Architecture Working
Group. |
|
Requirements Discussion
|
|
Attendees reduces the list of 41 requirements to 14. These
14 will be kept as the current requirements list. |
|
|
5 |
Motion to adjourn |
|
Meeting adjourned at 5:00 PDT to re-convene on Thursday, September 19, at the Cisco site. |
|
Owner |
Action Item/Motion |
|
Winston |
Move the MPTC meeting time to 7 AM Pacific time since this hour will be somewhat convenient to all members, including those in Europe and Japan. We will move to this time for our meeting of Wed, Oct 2. Next week, Sept 25, we will meet at the usual time of 10:00 AM Pacific time. |
|
Heather |
MPTC should work with CIM, W3C, and OGSA to avoid duplication of effort. MPTC should also work with The Open Group, Storage Network Industry Association, JMX, DMTF. |
|
Winston |
Ask Dick Spellman to put together a set of ops required by JMX. We want to understand their requirements as we build our own specs. |
|
Motions |
|
|
|
|
[1] published agenda URL