[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes 9th October 2013
Meeting Minutes 9th October 2013
Attendees:
US Department of Defense (DoD) Michael Behrens Voting Member
Oracle Mark Carlson Voting Member
Oracle Martin Chapman Chair
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 Voting Member
Oracle Gilbert Pilz Voting Member
Red Hat Krishna Raman Voting Member
Fujitsu Limited Tom Rutt Voting Member
Software AG, Inc. Prasad Yendluri Voting Member
Intro:
Michael Behrens assumes scribe duties.
Roll: Attendees listed above: 12 of 14 (85%), meeting is quorate.
Agenda:
- Gil requests moving CAMP-111 to the top of the issues discussion list
There is also another new issue: https://tools.oasis-open.org/issues/browse/CAMP-145 AssemblyTemplate not very useful
Agenda reviewed and approved as modified.
Minutes:
2nd October 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201310/msg00019.html
MOTION: Ashok moved, Krishna second approve Minutes 2nd October 2013
passed w/o
Administrivia:
F2F discussion wrt scheduling bridge for the formal meeting will be open 3:30-5:30 uk time Mon-Wednesday.
Starting F2F agenda is all the unfinished items from this meetings agenda.
New Issues:
Camp-142: https://tools.oasis-open.org/issues/browse/CAMP-142 - recorded as duplicate of CAMP-29.
Anish Karmarkar: the component is PR, that should suffice as a reminder
Adrian Otto (Rackspace): we could create a subtask of CAMP-29 to notify the comment submitter.
Martin Responded to submitter, however need to reply to the submitter for 142. Discussion on process for tracking responses.
MOTION: Adrian motions, Alex seconds, to close 142, no action.
Anish suggest using tracking system log. A report can be generated.
passed w/o
CAMP-143: https://tools.oasis-open.org/issues/browse/CAMP-143
MOTION: Gil motions to open 143 as a P2. Alex seconds.
Motion passes, no objections.
CAMP-144: https://tools.oasis-open.org/issues/browse/CAMP-144
Gil provides an overview of 144.
MOTION: Gil moves to open 144 as a P2.
Krishna seconds.
Motion carries.
CAMP-145: https://tools.oasis-open.org/issues/browse/CAMP-145
MOTION: Alex to Open CAMP-145 as a P1
Adrian seconds.
Adrian discusses complexity issues with templates and need for running state of an application in a PaaS. Recommends lighter weight CAMP by having templates as an option.
Motion Carries. CAMP-145 opened as a P1.
Issue Discussions:
Triage Request made last week, need additional triage work. Tom and Adrian to do before the F2F
CAMP-111 https://tools.oasis-open.org/issues/browse/CAMP-111
Gil: Presents proposal https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50939/camp-spec-v1.1-issue111-v2.doc
general agreement that consumerMutable proposal is straight-forward. Removed references where not applicable.
MOTION: Gil moves to resolve CAMP-111 with v2 proposal. Adrian seconds.
Motion carries to resolve CAMP-111.
CAMP-18: https://tools.oasis-open.org/issues/browse/CAMP-18
Adrian opens discussions.
Adrian: Main change in Transfer Protocol section 6.1. Proposal is to add a authScheme attribute. Discussions on proposed changes. Removed word "standard".
Anish asks for clarification on required...authScheme attribute is optional, regardless of whether minter uses authentication.
Mark asks for location of specific verbiage on when it is required. Answer: section 5.6. Discussion on "MAY".
Mark: What about proprietary authentication? If attribute is empty, does that mean there is no authentication theme (added).
Alex: Additional names and more descriptive strings suggested. Multiple security endpoints
Anish: Advertising authentication is not best practice.
Anish: Best security practice. Not sure that empty should mean no authentication.
Gil: Agrees. Views this is a handy way to know what the authentication mechanism is. It's optional, not required.
Alex Heneveld: +1 Gil
Alex Heneveld: +1 Mark - this is an improvement on Basic only !
Mark: If one does not advertise, interoperability is sacrificed.
Mike: Being able to not advertise security is somethings best security practice. Configurable would be good. Unknown should be assumed if empty.
Anish: In case of security, banners/advertisements need to be controlled. Minor barrier overall.
Mark: Attribute is not required. Attribute present of None perhaps, vice empty attribute. Absence would mean not advertized.
Michael: +1
MOTION: Adrian moves to resolve CAMP-18 with the R3 proposal in JIRA. Seconded by Gil.
Adrian Otto (Rackspace): Here is the link to the revised proposal for CAMP-18: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/50987/camp-spec-v1.1-wd24-issue18-r3-ajo.doc
Motion Carries. CAMP-18 is resolved.
CAMP-31: https://tools.oasis-open.org/issues/browse/CAMP-31
Gil provides an overview/discussion of issue.
Gil: cleared up representationSkew. Added status attribute. Proposes to go with proposal as it is written now.
Anish: Agrees. As long as providers are not prevented setting status for critical components.
MOTION: Gil motions to resolve CAMP-31 with v3 proposal in JIRA.
Tom seconds.
Motion carries. CAMP-31 is resolved.
CAMP-44: https://tools.oasis-open.org/issues/browse/CAMP-44
Gil: Opens discussion on inheritance. Would like to be able to add attributes. An assembly has links to application components, which currently creates a new resource type. Gil urges TC members to read new Resource Types and Sub-Types section. Discussion follows.
Tom Rutt (Fujitsu): do we require an implementation to support behavioural substitutability of a subtype for a supertype?
Anish Karmarkar: http://en.wikipedia.org/wiki/Covariance_and_contravariance_%28computer_science%29
Tom: Likes concepts. To what level is this required to be supported by implementers? Substitute for their parent types? Yes.
Anish: When referencing endpoints...the links to a platform (or other type), would also be linkable to subtypes. Perhaps a global note can be added.
Tom Rutt (Fujitsu): I think subtyping of the base types needs to be a separate issue. This issue is for resource types only
Mark: Language needs to be more normative. Use resource-type vice type. Keep adjectives present.
Tom: Agrees - say resource-type.
UML diagrams need editing. Direction is okay.
AOB:
Stragglers for the roll: Mark, Anish, Derek.
F2F Reminder for next week. Times will be in official calendar invite. Weekly telecon cancelled for next week.
Meeting Adjourned
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]