[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes 13 March 2013
Meeting Minutes 13th March 2013
Attendees:
Rackspace Hosting, Inc. Roshan Agrawal Voting Member
US Department of Defense (DoD) Michael Behrens Member
Software AG, Inc. Bhaskar Reddy Byreddy Voting Member
Oracle Mark Carlson Voting Member
Oracle Martin Chapman Chair
Cloud4SOA Francesco D'Andria Member
Fujitsu Limited Jacques Durand Voting Member
Cloudsoft Corporation Limited Alex Heneveld Voting Member
Individual Gershon Janssen Member
Cloudsoft Corporation Limited Duncan Johnston-Watt Voting Member
Oracle Anish Karmarkar Voting Member
Oracle Ashok Malhotra Voting Member
Rackspace Hosting, Inc. Adrian Otto Secretary
Oracle Gilbert Pilz Voting Member
Red Hat Krishna Raman Voting Member
JumpSoft Charles Tupitza Voting Member
Software AG, Inc. Prasad Yendluri Voting Member
Into:
Michael Behrens assume scribe duties
Roll: Attendees listed above 14 of 15, 93%, meeting is quorate
Martin introduces Francesco D'Andria, from Cloud4SOA: Overview/Introduction: PaaS portability. Joined TC. Welcome.
Agenda Approved as posted
Minutes:
6th March 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201303/msg00024.html
MOTION: m: Alex, s: Adrian moves to approve 6 March minutes, Adrian seconds
MOTION PASSES by Unanimous Consent
Administrivia:
F2F
Ballot closes in a couple of days for next F2F. Please confirm attendance via ballot even if just dialling in.
Jacques F2F Note: Network connectivity...unless tunnelling used, they may have some VPN issues. Working on this.
Timeline discussion. Significant milestone, 50%.
Scheduling update: None. Looks clean
PDP discussion review:
5-6 people met yesterday to brainstorm basic requirements for PDP and identified main open questions. Chat transcript captured. See Issue for details.
New Issues:
None
Issue Discussions:
https://tools.oasis-open.org/issues/browse/CAMP-30 Parameter Scheme
Adrian presents his proposal
Adrian/Alex/Anish discussion on possible resolution wrt parameter "definition" - to avoid two step process to name a new resource. Discussion on requirement for extension.
Gil: Make simple case simple. Recommends name be optional when creating assemblies, but something that SHOULD be implemented by platform. CAMP spec
could then specify the name of the name (used as an Assembly ID in automation, perhaps).
Anish: Discussion on view of it as a bi-directional contract (between developer, platform, and ?)
Alex: Return object reference would avoid "anti-pattern". Need to be clear on "when" it happens. Analogy made between object constructor and fields within the object.
More comfortable with patch in terms of pattern. Name attribute, in addition to construction values.
Alex Heneveld (Cloudsoft): i'm strongly in favour of parameterDefinition instead of "temporary"
Alex Heneveld (Cloudsoft): i'm okay with accepting attributeDefinitions at creation time, to avoid proliferation of duplication in parameterDefinition namespace
Alex Heneveld (Cloudsoft): although personally i think that duplication might be simpler than trying to figure out which attributes are also parameters
Alex Heneveld (Cloudsoft): (ie i prefer _parameters_ are used at creation time, and _attribute_ patches done afterwards -- simple model)
Alex Heneveld (Cloudsoft): +1 Anish, we supply a parameterDefinition for name, along with attributeDefinition
Alex Heneveld (Cloudsoft): +1 metadata for parameters must be navigable
Summarize #30: Adrian summarizes possible ways in issue. Is there alignment on URI (parameter or attribute), based on type. Discussion on only using parameter approach. Gil
would prefer spec to be clear on specific "tag". Maybe add: isParameter? check, etc. Anish: Suggest that metadata/tags can be specified to be allowed/accepted/available/navigable.
Gil: Suggest that simple use of "name" would be sufficient - if documented in spec.
Anish Karmarkar (Oracle): i see three possible solutions for this now
Anish Karmarkar (Oracle): (1) params only no reflection, (2) params only with reflection, (3) params + attributes
Adrian will update his proposal based in the discussion.
https://tools.oasis-open.org/issues/browse/CAMP-40 version array resource/thing has a number of problems
Adrian presents his proposal
Anish Karmarkar (Oracle): perhaps call it PlatformEndpoints (?)
Adrian/Gil provide an overview of 40 - using the version as part of the link, however there may be many reasons for different platform instance (i.e. region, etc). This then
introduces the concept of "Endpoints"
Discussion of section 6.8 wrt discovery and authorization to the platform resource
Rashan: good to separate version/resource. Specification version compatibility: How to ensure consistent/non-duplicative info?
Anish: Endpoints URL: good name, better than versions. It's optional. Main use-case is to ensure interoperability between versions. Perhaps it should be required - Mandatory.
Anish Karmarkar (Oracle): btw, i prefer plt endpoint rather than endpoint
Anish Karmarkar (Oracle): maybe it is my background, but endpoint is just too general and any URL is potentially an endpoint
General agreement to place emphasis on endpoints. Discussion on compatibility list on platform.
Anish Karmarkar (Oracle): don't want to see EPRs again (endpoint reference, that is)
Jacques (Fujitsu): PLATE (PLATform Endpoint)
MOTION: m:Adrian, s: Anish, move to resolve CAMP-40 using camp-spec-v1.1-wd07-issue40-v5.doc, with modifications: Place the order of the platformEndpoint resource first rather than last, and rename endpoint platformEndpoint, and make platformEndpointURI required=true.
MOTION PASSES BY Unanimous Consent
https://tools.oasis-open.org/issues/browse/CAMP-21 Clarify whether App Developers/Admins can assume what the Assembly template tree looks like until post-deploy
Gil went over the issues
Adrian Otto (Rackspace) : https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48374/AppModeling.pdf
AOB:
During AOB white smoke was seen coming from the Vatican - unconnected to this TC of course!
Straggler roll: add Duncan
MEETING ADJOURNED
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]