We will have our regular TOSCA Community meeting on Wednesday September 9 at 5:00pm CET, at 4:00pm in the UK, at 8:00am US Pacific Time, and 10:00am US Central Time. Please join at https://us02web.zoom.us/j/83059314783?pwd=QZ0ria97PMZsFMDrQb1uXAwaLassq9.1
Last week we went through all eight proposals in the abstract profile document. Five were agreed, two of them with pieces left open that return this week. RelationalDatabase is open again, and the network properties were taken provisionally. The 0.1 release now waits on the edits and on four decisions. Four proposals on this agenda have never been discussed, so we take them early.
The proposal document is at
https://github.com/oasis-open/tosca-community-contributions/blob/master/profiles/community/tosca/docs/abstract-profile-proposed-changes.md
The proposed agenda is in the same repository, under governance. Please read both.
Core as a standard library
- Section 2.9 moves the three base capability types and the three base relationship types out of core and into abstract.base.
- It leads because it is the one release-path proposal nobody has seen.
Orchestrated credentials
- A first look at credentials the orchestrator creates rather than is given. The write-up is new since last week, with a worked example.
- Open: which profile the Credential capability type belongs in, and whether the node types are abstract or technology.
The three questions last week opened
- mgmt-address as a URL or a structured type, the container-platform credential vocabulary, and RelationalDatabase as a derived type or a technology value.
- All three are on the release path; the last can also be deferred.
Also on the agenda
- control-host, the requirement section 2.3 did not finish, and three resolutions drafted in the design guide and never ratified.
- The artifact calling convention, and two proposed amendments to specification section 1.2.2.
Thanks, Chris