OASIS Web Services OASIS Web Services Distributed Management Distributed Management

Technical CommitteeTechnical CommitteeFeb 9,10 Face to Face #5Feb 9,10 Face to Face #5

HPHP

Winterpark, COWinterpark, CO

ObjectivesObjectives• 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

Agenda Feb 9Agenda Feb 9thth - Morning - Morning9am Welcome/Attendance/TC Administrivia

1. Action Item tracking2. WSDM 1.0 Spec line-items List3. Editor coordination

9:30 - 10:00 Interoperability Scenario Review10:00-12:30 - WS Resource Framework - Tom Maguire/William

1. Statefull services and the Implied Resource Model 2. Specification review –

1. WS-Addressing, 2. WS-Notification, 3. WS-Resource Properties

3. Q and A4. Discussion on relevance to WSDM Specifications - All5. Vote on how to leverage in WSDM Specifications - All6. WSDM Platform resolutions - outstanding issues, path for

resolution

Agenda Feb 9Agenda Feb 9thth - afternoon - afternoon

12:30 - 1:00 - Lunch1:00-5:30 MUWS Review and Agreement of Documents

1:00 Architecture1:30 Platform2:00 Identity3:00 State

6:00 Group Dinner go by Shuttle Bus at 5:45

Agenda Feb 10thAgenda Feb 10th8:30am Welcome/Attendance8: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 Lunch1:00-2:00 - MOWS Review, Issues, & Roadmap for

completion- Igor1.Handling the Request State Model - Igor2.Versioning – Mike Perks/Bryan

2:00-4:00 - WSDL Mapping from UML

Agenda Feb 10thAgenda Feb 10th

4:00-5:00 - Specification Roadmap LineItems for WSDM Spec 1.0WSDM Spec 2.0

Action Item Review and assignmentEditor CoordinationSubteam Coordination (if any)Laison Coordination (if any)Plan for next Face to Face - Islandia in April?

Work Items from last F2FWork 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

WS-Resource Framework WS-Resource Framework ReviewReview

1. Please consider as the additional WS platform technologies that we require:

– Stateful Resource handling– Addressing– Properties– Notification

2. Specification Review– Stateful services and the Implied Resource Model – Specification review –

• WS-Addressing, • WS-Notification, • WS-Resource Properties

3. Q and A4. Discussion on relevance to WSDM Specifications - All5. Vote on how to leverage in WSDM Specifications - All6. WSDM Platform resolutions - outstanding issues, path for resolution

• MetaData

MUWS Spec OutlineMUWS 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

MUWS Action Items - UArchMUWS Action Items - UArch

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

MUWS ArchitectureMUWS Architecture

• Conceptual model – picture

• Logical model– Role & Artifacts definition

• Responsibilities• Capabilities

– Interaction patterns– Manageability Info meta model– Distribution arch

3. WS Platform Requirements 3. WS Platform Requirements SectionSection

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

MUWS Action Items - UPlatMUWS Action Items - UPlat•Platform – Immediate (WSDM V0.5)

Attributes – HeatherMetadata – HomayunAddressing – HeatherNotification – IgorSpec version – WSDMService versioning – Platform? MOWS?

•Platform Future, wait for market developmentSecurity – high, John DeCarlo (Hal, Fred help) (WSDM v1)Policy – med, wait for market developmentTransactions – med, wait for market developmentLifecycle Model – med, of resource instancesName Resolution – med

MUWS Action Items - UPlatMUWS Action Items - UPlat•MMB-

Identity of ResourceState Model – of resourcesResource versionCollection Relationships

•No Additional RequirementsIdentity of Endpoint – from WSDLRegistration/Discovery – no addt’l reqts

4. Manageability 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

MUWS IdentityMUWS Identity

• Review Draft

• WSDL Representation– Properties– Specific Access Operations?

MUWS StateMUWS 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

MUWS - MetricsMUWS - Metrics

• Things to think about1. Metric Organization – sets?2. Metric Metadata – Units, …?3. Metric Events – Metric change? Reset

occurred? …4. Metric Operations – Get?, Reset?...

5. Discovery and Introspection5. Discovery and Introspection

1. finding manageable resources

2. introspecting manageability capabilities

Do we need this for V0.5?

MUWS Spec Tasks/EditorsMUWS Spec Tasks/EditorsTasks:• 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

MOWS Spec OutlineMOWS 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, EditorsMOWS Spec Tasks, Editors

Tasks:UML Models Task – Igor lead, BrianC, BryanM., Mark,

Dan, FredC., Andrea, GeoffB, WilliamV., KarlS.

Editors: Igor, BryanM., BrianC., Fred, Heather

MOWS Action Items 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)

EditorsEditors

• 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)

Models to WSDL MappingsModels to WSDL Mappings

• Inheritance

• Property Representation & Access i.e. Get

• Other property access? i.e. GetState

• Method/Operation Representation

• MetaData Representation

• Events

• Bindings

TeamsTeams

WSDM Call Use

Do we need Focus teams?

When do they meet?

Editor Calls

Timelines & MilestonesTimelines & Milestones

• MUWS Arch

• MUWS WS Platform

• Manageability– Models – Identity, State, Metrics– Representations – Identity, State, Metrics

• MOWs Model

• MOWs Representations

Specification PhasesSpecification 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

WSDM 1.0WSDM 1.0

1. Configuration

2. Relationships

3. Security

4. Operational support

5. Events

6. Aliases

7. Standard Substates

WSDM 2.0WSDM 2.0

1. Update support for WS platform

2. Accommodate Policy

WSDM and LaisonsWSDM and Laisons

• DMTF: Winston to create dmtf work register, ballot. Name Laisons:– Applications– State/Behavior– Utility– Interop

• OGSA/OGSI

• CMM

Liaisons & contact pointsLiaisons & 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