13:10:41 #startmeeting TSC Architecture Committee 13:10:41 Meeting started Thu May 24 13:10:41 2018 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:10:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:10:41 The meeting name has been set to 'tsc_architecture_committee' 13:10:53 #info Roll Call 13:11:01 #info Bryan Sullivan 13:11:42 #info attending Anwar, Nat, Manoop, Pantelis , Chris 13:12:39 #topic Agenda: Review requirements pipeline; review current architecture; review role of Community and Product committee; requirements for participation in Arch committee 13:13:26 #topic Requirements pipeline 13:14:32 #info Anwar presents overview slide from ONS, from slides at https://wiki.acumos.org/display/EVNT/Acumos+at+ONS+2018 13:18:47 #info ... (shows the "Acumos Architecture" slide) 13:20:58 #info Bryan: we need architecture diagrams at a component level, and at various key use cases in the UX of the platform e.g. deploy to cloud 13:24:16 #info Bryan: we need all components and the interfaces / dataflow between them to be documented 13:25:36 #info Pantelis: what is the function of the validation module 13:26:25 #info Bryan: it's a largely non-functional implementation of a workflow vision for license/vulnerability scanning - I will be taking a lead role in addressing its limitations in the first release 13:28:22 Bryan: the current vision for security and validation is on the wiki at https://wiki.acumos.org/display/SEC/Security+Scanning 13:28:53 #info ... this will be included in a design document for this release 13:29:09 ... and expanded with arch/dataflow details as needed 13:29:59 #info Pantelis is training currently supported? 13:30:12 #info Anwar: not in the current release, it's on the roadmap 13:31:25 #info Anwar describes the external interfaces E1-E7 13:32:13 #info attending: Ofer, Vishnu 13:34:11 Ofer: will E6 also be used for training? 13:34:23 #info Ofer: will E6 also be used for training? 13:35:12 #info Anwar: we need to discuss but we were thinking that for training you need to deploy and provide a dataset, which is similar to what you need to do for deployment 13:38:59 #info Bryan: who can work with me to gather documentation and publish it in the docs 13:40:54 #info Manoop: will help 13:42:02 #topic Requirements Pipeline 13:43:48 #info Anwar shows current collected input at https://etherpad.acumos.org/p/release-plan-athena 13:46:27 #info Anwar shows repo mapping at https://wiki.acumos.org/display/TSC/PTL+Nominations 13:49:12 #info Nat: recommend that PTLs bring reqs to the Requirements committee based upon their assessment of feasibility and priority 13:49:54 #info Nat: describes items he contributed to the etherpad 13:51:43 #info Bryan: we need to ensure that proposed features are analyzed at a high level at least, and documents are available for review 13:53:29 #info Bryan: deploy to Azure for example needs to be revisited 13:55:29 #info Manoop: platform security scanning is a very important one 13:55:54 #info ... also code quality - coverage is too low, we need to push for at least 50% coverage 13:58:21 #info Ofer: has a friend who started WhiteSource and can offer it as a tool for Acumos to use 13:59:33 #info Anwar: post-review and approval by TSC, we will need to assess what can be delivered in the current release 14:00:57 #info Anwar: any of these discussed so far that will have substantial impact on the current arch? 14:01:15 #info Bryan: security and validation are likely to disrupt current design 14:03:40 #endmeeting