1 / 32

OASIS Web Services Distributed Management Technical Committee

OASIS Web Services Distributed Management Technical Committee. Feb 9,10 Face to Face #5 HP Winterpark, CO. Objectives. Finalize Technical Discussions for 0.5 specifications for MUWS and MOWS Architecture Platform Identity Metrics State WSDL Mapping Work items for specifications for 0.5

peri
Download Presentation

OASIS Web Services Distributed Management Technical Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OASIS Web Services Distributed Management Technical Committee Feb 9,10 Face to Face #5 HP Winterpark, CO

  2. Objectives • Finalize Technical Discussions for 0.5 specifications for MUWS and MOWS • Architecture • Platform • Identity • Metrics • State • WSDL Mapping • Work items for specifications for 0.5 • Work items for interoperability demo for 0.5

  3. Agenda Feb 9th - Morning • 9am Welcome/Attendance/TC Administrivia • Action Item tracking • WSDM 1.0 Spec line-items List • Editor coordination • 9:30 - 10:00 Interoperability Scenario Review • 10:00-12:30 - WS Resource Framework - Tom Maguire/William • Statefull services and the Implied Resource Model • Specification review – • WS-Addressing, • WS-Notification, • WS-Resource Properties • Q and A • Discussion on relevance to WSDM Specifications - All • Vote on how to leverage in WSDM Specifications - All • WSDM Platform resolutions - outstanding issues, path for resolution

  4. Agenda Feb 9th - afternoon 12:30 - 1:00 - Lunch 1:00-5:30 MUWS Review and Agreement of Documents 1:00 Architecture 1:30 Platform 2:00 Identity 3:00 State 6:00 Group Dinner go by Shuttle Bus at 5:45

  5. Agenda Feb 10th 8:30am Welcome/Attendance 8:30-11:30 MUWS Metrics – All Metric Organization – sets? Metric Metadata – Units, …? Metric Events – Metric change? Reset occurred? … Metric Operations – Get?, Reset?... 11:30-12:30 MUWS Specification, roadmap for completion of 0.5 12:30-1:00 Lunch 1:00-2:00 - MOWS Review, Issues, & Roadmap for completion- Igor • Handling the Request State Model - Igor • Versioning – Mike Perks/Bryan 2:00-4:00 - WSDL Mapping from UML

  6. Agenda Feb 10th 4:00-5:00 - Specification Roadmap LineItems for WSDM Spec 1.0 WSDM Spec 2.0 Action Item Review and assignment Editor Coordination Subteam Coordination (if any) Laison Coordination (if any) Plan for next Face to Face - Islandia in April?

  7. Work Items from last F2F • 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

  8. WS-Resource Framework Review • Please consider as the additional WS platform technologies that we require: • Stateful Resource handling • Addressing • Properties • Notification • Specification Review • Stateful services and the Implied Resource Model • Specification review – • WS-Addressing, • WS-Notification, • WS-Resource Properties • Q and A • Discussion on relevance to WSDM Specifications - All • Vote on how to leverage in WSDM Specifications - All • WSDM Platform resolutions - outstanding issues, path for resolution • MetaData

  9. 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

  10. MUWS Action Items - UArch • UArch • fix diagrams - Igor • unify logical models and roles – Igor/Homayun • information model - William • delegation model - William • processing model – buckets - Igor

  11. MUWS Architecture • Conceptual model – picture • Logical model • Role & Artifacts definition • Responsibilities • Capabilities • Interaction patterns • Manageability Info meta model • Distribution arch

  12. 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 • 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

  13. MUWS Action Items - UPlat • Platform – Immediate (WSDM V0.5) • Attributes – Heather • Metadata – Homayun • Addressing – Heather • Notification – Igor • Spec version – WSDM • Service versioning – Platform? MOWS? • Platform Future, wait for market development • Security – high, John DeCarlo (Hal, Fred help) (WSDM v1) • Policy – med, wait for market development • Transactions – med, wait for market development • Lifecycle Model – med, of resource instances • Name Resolution – med

  14. MUWS Action Items - UPlat • MMB- • Identity of Resource • State Model – of resources • Resource version • Collection • Relationships • No Additional Requirements • Identity of Endpoint – from WSDL • Registration/Discovery – no addt’l reqts

  15. 4. Manageability Identify functionality/capabilities required to support describing and using manageability of resources using Web services (bubbles on chart2 +) • Properties, operations, events & metadata, uml • 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<<??? For March?>> • Metric description • Configuration • Change control

  16. MUWS Identity • Review Draft • WSDL Representation • Properties • Specific Access Operations?

  17. MUWS State • Review Draft • 3 States standard – Available, Unavailable, Semi-Available • Substates to V1 • Operations: • Get State • Get State Model • Enable • Disable • Control Events • WSDL Mapping • State model • State transitions • State events • Operations affecting state • Operations - required state • Properties - required state

  18. MUWS - Metrics • Things to think about • Metric Organization – sets? • Metric Metadata – Units, …? • Metric Events – Metric change? Reset occurred? … • Metric Operations – Get?, Reset?...

  19. 5. Discovery and Introspection • finding manageable resources • introspecting manageability capabilities Do we need this for V0.5?

  20. MUWS Spec Tasks/Editors Tasks: • Meta/Architecture task – UArch – WilliamV. lead, Heather, Winston, Igor, GeoffB. Richard N., KarlS., Andrea, Rajiv • WSPlatform requirements/recommendations task – Homayoun, lead, Heather, Igor, Homm., AndreasD., TomS. • Manageability Building Blocks – Ellen Stokes Editors – John DeCarlo, WilliamV., PaulL., Heather

  21. MOWS Spec Outline • Overview of manageability model of Web service endpoint, use of MUWS • Identification • Configuration • Relationship • Metrics • Lifecycle / Status • Change Description and Notification • Sessions (may stand alone or merge into previous) • Example, separate Primer document? AppendixA: Representation with schemas, etc.

  22. MOWS Spec Tasks, Editors Tasks: UML Models Task – Igor lead, BrianC, BryanM., Mark, Dan, FredC., Andrea, GeoffB, WilliamV., KarlS. Editors: Igor, BryanM., BrianC., Fred, Heather

  23. MOWS Action Items • Proposals on manageability endpoint managing one wsdl:endpoint (Igor) vs managing multiple wsdl:endpoint (William) • Clarify Versioning requirements (Igor, Brian, Mike) • Fix Versioning UMLs (Igor, Brian, Mike)

  24. Editors • MOWS Specification - Igor, BryanM., BrianC., Fred, Heather • MUWS Specification - John DeCarlo, WilliamV., PaulL., Heather • Identity – WilliamV. • State – Ellen • Metrics - Warran • Glossary - Mark Potts, Andrea W., Heather, Judi (Andrea lead)

  25. Models to WSDL Mappings • Inheritance • Property Representation & Access i.e. Get • Other property access? i.e. GetState • Method/Operation Representation • MetaData Representation • Events • Bindings

  26. Teams WSDM Call Use Do we need Focus teams? When do they meet? Editor Calls

  27. Timelines & Milestones • MUWS Arch • MUWS WS Platform • Manageability • Models – Identity, State, Metrics • Representations – Identity, State, Metrics • MOWs Model • MOWs Representations

  28. Specification Phases • Roadmap • WSDM 0.5 – MUWS/MOWS, Identity, Metrics, State, Events? • WSDM 1.0 – Configuration, Relationships, Security, Operational support, Events, Aliases.. • WSDM 2.0 – Update support for WS platform, policy, … • Glossary

  29. WSDM 1.0 • Configuration • Relationships • Security • Operational support • Events • Aliases • Standard Substates

  30. WSDM 2.0 • Update support for WS platform • Accommodate Policy

  31. WSDM and Laisons • DMTF: Winston to create dmtf work register, ballot. Name Laisons: • Applications • State/Behavior • Utility • Interop • OGSA/OGSI • CMM

  32. Liaisons & contact points • for staying in synch, we depend on them and they depend on us • Points of contact w/in Oasis that can keep in touch, informal liaisons • GGF CMM – Ellen & Jim Willits (close) • OASIS Provisioning – Darren Rolls (close) • WS-Security – Hal Lockhart (not close) • 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

More Related