OASIS Web Services Distributed Management Technical

Committee

Dec 2,3 Face to Face #4

Dell

Austin, TX

Agenda Dec 2nd• 8:30-12 MUWS: Architecture (John DeCarlo to

coordinate),– 1. Context - Heather.– 2. Concepts - Igor.– 3. Logical Architecture - Igor.– 4. Implementation Architecture – Igor.

• Start next subgroup for Manageability Building Blocks (Heather)

• 12-12:30 Lunch• 12:30-1:30 Glossary (Karl Schopmeyer)• 1:30-5:30 MUWS: Web services Platform

(Homayoun to coordinate)

Agenda Dec 3rd

• 8:30-11:30 MOWS: Web Services Model (Igor Sedukhin)

• 11:30-12 DCML (Igor Sedukhin)

• 12-12:30 Lunch

• 12:30-2:30 Specification phasing

• 2:30-5:30 Action Items/Planning/Laisons/Wrapup/Next F2F

Remembering the last F2F…Oct F2F Timelines & Milestones

• MUWS Arch – Nov 1 – first draft– Dec 1 - done

• MUWS WS Plat– Nov 1 – identify req’d, recommend approach– Dec 1 – draft req’ds for first submission

• Manageability– Nov 1 - start– Dec 1 – scope , State model, event fmt, umls for base manageability

model• MOWs Model

– Nov 1 first draft– Dec 1 models

MUWS Spec Outline• 1. Meta Model• 2. Architecture – extensive in sep doc; brief in this doc; manager motivation, expose mgbility ifc

about resource• 3. WS Platform Requirements • identify platform functionality required, which specs should be used, the interim

solution if there are not existing specs, or pointer to future• bubbles on chart1• i.e. ID, version, notification, collection, relationship, registry, policy , security,

addressing, etc.• 4. Manageability • identify functionality/capabilities required to support describing and using

manageability of resources using Web services• bubbles on chart2 + • i.e. Resource state model, event format, configuration, metrics, operations, identity,

version, change control, basic relationships for manageability• 5. Discovery and Introspection• finding manageable resources• introspecting manageability interfaces • 6. Defining a manageability interface for a manageable resource using this specification • how to mix in functions in section 3 and 4 – probably normative• profiles of manageable resources? ( configurable? monitorable? ) not sure if normative• how to satisfy some of the main usage scenarios? – sep doc• Appendix for full schemas, namespaces, types• ? How do we represent in each section with text do we exhibit: schema, example fragment instances

(not normative for understanding), and/or other representation of allowable syntax (like in ws-s docs). We have a multiple ifcs issue for examples. Pseudo may help here. Schema defines syntax but is not required as long as syntax is correct ( a convention from soap )

MUWS Spec Tasks/Editors1. Meta Model2. Architecture 3. WS Platform Requirements 4. Manageability 5. Discovery and Introspection6. Defining a manageability interface for a manageable

resource using this specification Tasks:• Meta/Architecture task – UArch – Zulah lead, Heather,

Winston, Igor, GeoffB. Richard N., KarlS., Andrea, Rajiv• WSPlatform requirements/recommendations task –

WilliamV. lead, Heather, Igor, Homm., AndreasD., TomS.

Editors – John DeCarlo, WilliamV., PaulL., Heather

MUWS Architecture

• Conceptual model – picture

• Logical model– Role & Artifacts definition

• Responsibilities

• Capabilities

– Interaction patterns– Manageability Info meta model– Distribution arch

3. WS Platform Requirements Section Identify platform functionality required (in addition to WS-I basic profile), which specs should be used,

the interim solution if there are not existing specs, or pointer to future (source bubbles2 chart)

• Identification – Unique Id for svcs• Version – version of service, in URIs today, w3c tab? sufficient?• Attributes • Metadata• Addressing – like ws-addressing and gsr/gsh• Security - +bootstrap security mode?• Flow• Policy – may not be reqd for vers 1• Negotiation

• Notification Mechanism• Registration/discovery• Collection• Name Resolution• Relation• Relationship Service?• Logging• Policy Decision Point/Policy Enforcement Point• Lifecycle Support

4. Manageability Identify functionality/capabilities required to support describing and using

manageability of resources using Web services (bubbles on chart2 +) • Properties, operations, events & metadata

– Identity– Version– Change control– Metrics– Configuration– State– Relationships

• Resource State Model – description of states/transitions• Basic relationships for manageability (metadata?)• Event Format and basic Types• Metric description• Configuration ?• Change control

5. Discovery and Introspection

1. finding manageable resources

2. introspecting manageability capabilities

Agenda Dec 3rd

• 8:30-11:30 MOWS: Web Services Model (Igor Sedukhin)

• 11:30-12 DCML (Igor Sedukhin)

• 12-12:30 Lunch

• 12:30-2:30 Specification phasing

• 2:30-5:30 Action Items/Planning/Laisons/Wrapup/Next F2F

MOWS Spec Outline1. Overview of manageability model of Web service

endpoint, use of MUWS2. Identification 3. Configuration 4. Relationship5. Metrics6. Lifecycle / Status7. Change Description and Notification8. Sessions (may stand alone or merge into previous)9. Example, separate Primer document?AppendixA: Representation with schemas, etc.

MOWS Spec Tasks, Editors1. Overview of manageability model of Web service

endpoint, use of MUWS2. Identification 3. Configuration 4. Relationship5. Metrics6. Lifecycle / Status7. Change Description and Notification8. Sessions (may stand alone or merge into previous)Tasks:UML Models Task – Igor lead, BrianC, BryanM., Mark,

Dan, FredC., Andrea, GeoffB, WilliamV., KarlS.Editors: Igor, BryanM., BrianC., Fred, Heather

Editors

• MOWS Specification - Igor, BryanM., BrianC., Fred, Heather

• MUWS Specification - John DeCarlo, WilliamV., PaulL., Heather

• Glossary - Mark Potts, Andrea W., Heather, Judi (Andrea lead)

Wrap Up Dec 3rdMini Specifications

• Champions• dates

Main Specifications• dates• phases• Content for phases

Roadmap for completion • Milestones for delivery - done• TC Subgroup operations - done• Planning for next Face to Face – done

Review and assignment of action itemsNext F2F

Oct F2F Action Items till next F2FAbout a month behind…

• Post approved MUWS requirements, HK, next week• Igor send HK approved MOWS requirements next week• Post approved MOWS requirements, HK, next week• UArch Draft – Zulah/team, Nov 1• UPlat first set of recommendations, William/team, Nov 1• OMod models – Igor/team, Nov 1• Form UMan team Nov 1, HK/Winston• WDSM/DMTF work register, Winston, next week• Work through CMM collaboration technicalities – Fred,

Ellen, Heather, Winston, Jamie• Glossary terminology draft, Andrea/team, Nov 1• HK/Winston update calendars to reflect • Is call timing an issue for CMM collaboration? And for

which calls? 2 weeks.

Specification Phases ideas

• Define at next F2F, Beg Dec

• Stack o’Specs/Bubbles/Roadmap?

• MUWS arch, plat recommendation, manageability?, discovery?

• Glossary

• MOWs models & representations

Specification Phases• March, 2004 - Should be implementable, Not get

laughed at, Interop Demo?– Roadmap (specs and capabilities and interop)– MOWS – aligned w/ MUWS subset (monitoring) –

identity, state, metrics, read only– Glossary– MUWS Alternatives:

• Rev 1 – Architecture and Platform – Attributes(HK/FM), Notifications(IS/HP), Metadata(HP/HK), Addressing(HK)?

• Rev 1 monitoring? – read only, multiple capabilities (identity, state, metrics), maybe notifications if we can

• Rev 1? All of identification• Rev 2? Notifications, Update, Relationships

Work Items for March 31• WSDM Roadmap – Winston/Heather• MUWS Architecture finish – William

– John DeCarlo editorial action items– William and John to decide if Arch wg is done or needs more meetings

• MUWS Platform recommendations for: – Editorial - Andreas – Attributes – Heather/Fred M./Homayoun– Metadata – Homayoun/Heather– Notifications – Igor/Homayoun– Addressing? - Heather

• MUWS Manageability Building Blocks (Props/Ops/Events) Models and WSDLS for: (Ellen)

– Identity – of managed resource - Winston– State – valid states/transitions, current state – Karl/Ellen– Metrics - Richard

• MOWS Models & WSDLs for: (Igor)– Identity – OMOD – w/ MUWS Identity– State – OMOD - w/ MUWS State– Metrics – OMD – up/down time, counters – w/ MUWS Metrics

• MUWS 0.5 Spec – Editor: Andreas & William• MOWS 0.5 Spec – Editor: John & Igor

Meetings

• UArch to schedule if needed• UPlat done• OMod done• WSDM calls

– Capabilities• Identity - #1 – Dec 11, 18• State - #2 – Jan 8• Metrics - #3 Jan 15

– Platform specs • Attributes, Metadata (Start working w/ GGF next week) • Notifications (Hom/Igor to evaluate)• Addressing (Heather to make a recommendation)

Roadmap ideas• Manageability interface looks like…. Model and wsdl• Capabilities – Properties, Metadata, Read only, Update, Operations,

Notifications– Identity – Version– Change control– Metrics– Configuration– State – Relationships

• Resource State Model – description of states/transitions• Basic relationships for manageability (metadata?)• Event Format and basic Types• Metric description• Configuration ?• Change control

Teams and Meetings

WSDM – Attendance/reports/issues from teams, Th 12:00-2:00

Calls – Reuse existing time

Work an issue during each call

Mailinglist – Use wsdm list with prefixes for topics

MUWS Action Items

UArch- fix diagrams - Igor- unify logical models and roles – Igor/Homayun- information model - William- delegation model - William- processing model – buckets - Igor

UMBB – Ellen Stokes

MUWS Action Items UPlat - assigned champions, rearranged

- Identity of Endpoint – from WSDL- Identity of Resource – to MMB- Versioning – Brian

spec version – WSDMresource version – to MMBservice versioning – Platform? MOWS?

- Attributes – Heatherresource attributes – to MMB? Grid coop?

- Metadata – Grid coop? Homayun- Addressing – Heather- Notification – Igor

interim solution?- Relationships – to MMB

MUWS Action Items UPlat

- Security – high, John DeCarlo (Hal, Fred help)- Registration/Discovery – no addt’l reqts

if we need a resource registry it will bemanagement specific

- Policy – med, wait for market development- Collection – high, to MMB- Transactions – med, wait for market development- State Model – of resources, to MMB- Lifecycle Model – med, of resource instances,

for market development- Name Resolution – med

if we need a resource name to reference resolutionwe will do it management specific

MOWS Action Items

•Proposals on manageability endpointmanaging one wsdl:endpoint (Igor)vs managing multiple wsdl:endpoint (William)

•Clarify Versioning requirements (Igor, Brian, Mike)

•Fix Versioning UMLs (Igor, Brian, Mike)

Next Face to Face – Feb• Location - Islandia• Host by CA• Proposed Dates: Feb 11,12• Prereqs for next F2F:

Liaisons

•DMTF – work register from Winston, Winston will take to DMTF and post it for approval

•GGF CMM – members of CMM join WSDM to do base workand use WSDM specs in CMM work. ? CMM concepts glossary useful for our glossary?

DCML Liaison? Not yet , Igor informally through CA

Liaisons & contact points• for staying in synch, we depend on them• depend on us?• Points of contact w/in Oasis that can keep in touch, informal liaisons• GGF CMM – Ellen & Jim Willits • OASIS Provisioning – Darren Rolls • WS-Security – Hal Lockhart • DMTF – Andrea Westerinen + Karl• TOG – Karl Schopmeyer• W3C-WSArch – Heather Kreger• W3C – WSDL 1.2 – Igor Sedukhin• Oasis – BPEL - Sanjeev• IETF/netConf – watch• JCP/JSR077 round 2 – watch (guru bhat, karl s.)• WS-I – basic profile implications• WS-I - manageable profile in future• DCML – Igor Sedukhin