OASIS Web Services
Distributed Management
Technical Committee
April 14, 15 Face to Face #6
CA
Islandia, NY
Objectives
• Preliminary Interoperability testing for
0.5
• Scope 1.0 specifications for MUWS and
MOWS
– Issues list
– New function list
• Work items for specifications for 1.0
• Work items for interoperability demo for
0.5 in May
Agenda April 14th
8:00 - 9:00 Welcome and TC Administrivia
Action Item tracking
Attendance
9:00 - 12:00 MUWS 1.0
1. Review WDSM 1.0 Spec issues list
2. Review WSDM 1.0 Spec line-items list
3. Identify candidate line items
4. Organize line items
5. Champions for line items
12:00 - 1:00 - Lunch
1:00 – 1:30 – Scenario Review
1:30 - 5:30 – Interoperability work session
7:30 Group Dinner
go by Shuttle Bus at 7:00
Agenda April 15th
8:00 am, Arrival and setup, breakfast
9:00 am, Interop post mortem (if we need it)
10:00 am, MOWS 1.0
–
–
–
–
Review line items, discussions outstanding for 1.0
Identify 1.0 candidates
Organize candidates into Capabilities
Identify champions for Capabilities
12:00 pm, Lunch
1:00 am, WSDM use of WS-Notifications
– WSDM use of other WS-RF specifications, i.e. Service Group, etc.
– Review action items
– Timelines for 1.0 specifications
3:00 pm, Wrap up
– Next F2F planning, location and interop follow on
– Action Item review
– Organizing calls, teams to progress on specifications
5:00 pm, End of meetings
MUWS Action Items
•
•
•
•
Introduction - Andreas
Arch (WV) – intro (HK), composability, logical model update (Igor), roles
(Andreas), Processing model section (Igor) 18th
Platform (WV) – paragraphs – (HK, HP) 18th
Identity – updates, resource properties, 13th
– Xml - William
•
State - William, add in – 18th
– Uml - karl
– resource properties - Igor
– Operations - igor
•
Metrics – Andreas (Richard) -27th
– Uml – andreas/richard
– Properties (xml – Igor/Fred) – 18th, assessment
– Operations - Richard
•
•
•
Discovery - <use ws, identity marker> - William – 27th
URN/URL – Igor/William – 27th
Roadmap – Heather, Winston
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)
MOWS Action Items
• Intro – Igor • Versioning – add new uml diagram from Perks/Brian, text –
Perks/Igor – feb 20
• Identification of manageable ws
– Change to ws-addressing epr
– Independent of Identity
• Configuration removed till 1.0
• State – MOWS sub states on MUWS?
1.0 can markup models
for 0.5, 3 states are enough
Request processing model
state events next time
counters now -> metrics (HK)
• Metrics
1.0 Issues
•
•
Identity needs to be hotly discussed.
What can you do if the resource doesn't
give you a useful identity?
Resource State. What do you do if the
manageable resource doesn't have an
inherent state?
1.0 Topics
• Discovery of manageability.
• Multiple WSDL documents. (0.5 uses just
one WSDL document for functional and
manageability).
• Multiple manageability providers for one
manageable resource.
• One manageability provider for multiple
manageable resources.
• Need to figure out how to handle various
issues related to ResourceType, as
discussed at F2F5.
1.0 Topics
• Need to resolve the issue of “marker
function” - how to tell if a Web Service is a
WSDM provider of manageability for a
manageable resource.
• Get to more robust Resource State –
define all the sub-states, use a standard
(almost all has two high level states for
operational states), probably relook at two
high level states, valid transitions,
operations to go from one state to another.
1.0 Topics
• Notifications and Events. Fill out specific
details in each applicable section.
• Do we need asynchronous operations?
• Composability of WS-Security onto WSDM
1.0.
• Need to figure out what parameters the
operations should have.
• Address grouping of metrics and related
time information.
.
1.0 Topics
• Should you allow both individual
metrics being reset as well as groups
of metrics?
• MOWS State Model. Sub-states, etc.
• Have to have a MOWS Request
Processing State in 1.0. Orthogonal
to Resource State.
• MUWS Metrics. How to model extra
things, like InitialValue / ResetValue.
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
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
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
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
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
• Review Draft
MUWS State
– 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 - Metrics
Things to think about
1. Metric Organization – sets?
2. Metric Metadata – Units, …?
3. Metric Events – Metric change? Reset
occurred? …
4. Metric Operations – Get?, Reset?...
5. Discovery and Introspection
1.
2.
finding manageable resources
introspecting manageability capabilities
Do we need this for V1.0?
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
MOWS Spec Outline
1.
Overview of manageability model of Web
service endpoint, use of MUWS
2. Identification
3. Configuration
4. Relationship
5. Metrics
6. Lifecycle / Status
7. Change Description and Notification
8. Sessions (may stand alone or merge into previous)
9. Example, separate Primer document?
AppendixA: Representation with schemas, etc.
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
Editors
• MOWS Specification - Igor, BryanM.,
BrianC., Fred, Heather
• MUWS Specification - John DeCarlo,
WilliamV., PaulL., Heather
– Identity – WilliamV.
– State – Ellen
– Metrics - Warren
• Glossary - Mark Potts, Andrea W.,
Heather, Judi (Andrea lead)
Models to WSDL Mappings
•
•
•
•
•
•
•
Inheritance
Property Representation & Access i.e. Get
Other property access? i.e. GetState
Method/Operation Representation
MetaData Representation
Events
Bindings
Teams
WSDM Call Use
Do we need Focus teams?
When do they meet?
Editor Calls
Timelines & Milestones
• MUWS WS Platform
• Manageability
– Models – Identity, State, Metrics, …
– Representations – Identity, State, Metrics, …
• MOWs Model
• MOWs Representations
Specification Roadmap
• 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.0
1.
2.
3.
4.
5.
6.
7.
Configuration
Relationships
Security
Operational support
Events
Aliases
Standard Substates
WSDM 2.0
1. Update support for WS platform
2. Accommodate Policy
WSDM and Laisons
• DMTF: Winston to create dmtf work
register, ballot. Name Laisons:
– Applications
– State/Behavior
– Utility
– Interop
• OGSA/OGSI
• CMM
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