[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes 12th June 2013
Meeting Minutes 12th June 2013
Attendees:
US Department of Defense (DoD) Michael Behrens Voting Member
Oracle Mark Carlson Voting Member
Oracle Martin Chapman Chair
Fujitsu Limited Jacques Durand Voting Member
Cloudsoft Corporation Limited Alex Heneveld Voting Member
Oracle Anish Karmarkar Voting Member
Oracle Ashok Malhotra Voting Member
Rackspace Hosting, Inc. Adrian Otto Secretary
Vnomic Derek Palma Member
Oracle Gilbert Pilz Voting Member
Fujitsu Limited Tom Rutt Voting Member
JumpSoft Charles Tupitza Voting Member
Software AG, Inc. Prasad Yendluri Voting Member
Intro:
Adrian assumes scribe duties
Roll Call: attendees listed above, 12 of 13 - 92%, meeting is quorate.
Topic Agenda: Approved with no objections.
Topic: Minutes from June 5.
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201306/msg00026.html
MOTION: Gil moves to accept minutes from June 5
Ashok seconds.
Minutes are accepted unan.
Topic: July F2F
Venue remains Omni Interlocken in Broomfield, CO.
Topic: Project Schedule update.
martin: CAMP-4 is a "log jam"
Topic: Editors Update
Jacques posted a draft of a test assertions document. Please review and comment.
https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201306/msg00030.html
MOTION: Adrian proposes to add Tom Rutt to editing team, Tom Seconds
motion passed unan.
Gil: offers to fold in open issues to a new working draft
offer accepted by Adrian and Anish
Topic: New Issue Discussion
https://tools.oasis-open.org/issues/browse/CAMP-69
Derek Palma presents CAMP-69
Issue concerns the question "How do CAMP clients learn the endpoints to communicate with CAMP servers?"
Alex: acknowledged that this would be desired. Opens the discussion about what normative types are.
Alex prefers that we not specify this, and leave it up to implementers.
.... May be a can of worms. A common name may be a solution.
Alex Heneveld (Cloudsoft): (correction to issue summary above: how do clients learn the endpoint(s) associated with a component _external_ to the CAMP platforms
Anish, asks for additional clarity on the question.
Tom also asks for clarity on the question.
Gil supports opening the issue so it can be discussed further
Michael Behrens indicates that the scope of the issue may be extended to include administrative URLs
MOTION: Gil moved to open CAMP-69, Seconded by Tom Rutt
Anish Karmarkar: priority for the issue?
Tom Rutt (Fujitsu): p3
with priority: P3
MOTION revised: Gil moved to open CAMP-69 as P3, Seconded by Tom Rutt
Alex clarifies that he does not have any objection to opening the issue
Alex Heneveld (Cloudsoft): ^^^ this will force some interesting discussion
Anish indicates that spec text may not be the only resolution to the issue in the future.
Michael Behrens: I'll add a comment on 69 regarding Admin + end user urls.
Anish Karmarkar: oasis has a concept of application notes which can be committee notes
motion passed unan, CAMP-69 opened.
Alex Heneveld (Cloudsoft): +1 Anish -- it will be important to have some good ancillary documentation -- "app notes" is good
Topic: Summary of this week's PDP work meeting
the v4 of the CAMP-4 proposal was discussed.
Alex presents via WebEx
Section 4.2 was adjusted.
Alex gives an overview of the open subjects for discussion.
Discussion begins.
Ashok asks about Example 4.
Gil Pilz (Oracle): Ashok sent me something that looked like this -
01 name: VitaMinder
02 components:
03 -
04 name: VitaMinder WAR
05 type: com.example.java:WAR
06 content: { href: vitaminder.war }
07 requirements:
08 -
09 type: com.example:HostedOn
10 javaVersion: [1.6,)
11 -
12 type: com.example.java:JdbcDependency
13 injectionMode: CDI
15 fulfillment: id:db
16 -
17 name: VitaMinder SQL
18 type: com.example.sql:SqlScript
19 content: { href: vitaminder.sql }
20 requirements:
21 -
22 type: com.example.db:RunAt
23 fulfillment: id:db
24 requirements:
25 -
26 name: VitaMinder DB
27 type: com.example.db:RDBM
28 id: db
29 replicas: 2
30 replication: com.example.dbptimistic[g1]
[g1]Component Spec with no content.
Gil Pilz (Oracle): if you let me present, I can show what Ashok is talking about
Ashok suggested a two-part deployment plan, such as the one shown above.
Tom Rutt (Fujitsu): is the type: under requirements: a requirementType, while the type: under the top level is a component type?
.....Will we have type hierarchies for either or both of these two type systems?
Alex Heneveld (Cloudsoft): both are _specification types_ --> "component spec type", "req spec type"
Alex Heneveld (Cloudsoft): yes, think of requirements as mix-ins, or marker interfaces, or traits
Anish Karmarkar: +1 to creation of AT even if the platform does not understand all the requirements
Anish Karmarkar: this would allow an admin to wire things the way she wants to
Michael Behrens: External requirements?
Tom Rutt (Fujitsu): If an AT is created from the PDP even though it does not understand all the requirements, will we populate the Resources with
.....Requirement Resources for all the request requirements? We already have an issue resolution on how to indicate if requirements are satisfied.
.... The manual wiring can ignore Requirements i think.
Alex Heneveld (Cloudsoft): +1 Gil answering Tom - use Mark's resolution to requirements links.
Alex will set up another PDP discussion meeting for this week.
AOB:
Straggler Roll.
Meeting adjourned.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]