#acumos-meeting: TSC Architecture Committee

Meeting started by bryan_att at 13:10:41 UTC (full logs).

Meeting summary

    1. Roll Call (bryan_att, 13:10:53)
    2. Bryan Sullivan (bryan_att, 13:11:01)
    3. attending Anwar, Nat, Manoop, Pantelis , Chris (bryan_att, 13:11:42)

  1. Agenda: Review requirements pipeline; review current architecture; review role of Community and Product committee; requirements for participation in Arch committee (bryan_att, 13:12:39)
  2. Requirements pipeline (bryan_att, 13:13:26)
    1. Anwar presents overview slide from ONS, from slides at https://wiki.acumos.org/display/EVNT/Acumos+at+ONS+2018 (bryan_att, 13:14:32)
    2. ... (shows the "Acumos Architecture" slide) (bryan_att, 13:18:47)
    3. 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 (bryan_att, 13:20:58)
    4. Bryan: we need all components and the interfaces / dataflow between them to be documented (bryan_att, 13:24:16)
    5. Pantelis: what is the function of the validation module (bryan_att, 13:25:36)
    6. 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 (bryan_att, 13:26:25)
    7. ... this will be included in a design document for this release (bryan_att, 13:28:53)
    8. Pantelis is training currently supported? (bryan_att, 13:29:59)
    9. Anwar: not in the current release, it's on the roadmap (bryan_att, 13:30:12)
    10. Anwar describes the external interfaces E1-E7 (bryan_att, 13:31:25)
    11. attending: Ofer, Vishnu (bryan_att, 13:32:13)
    12. Ofer: will E6 also be used for training? (bryan_att, 13:34:23)
    13. 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 (bryan_att, 13:35:12)
    14. Bryan: who can work with me to gather documentation and publish it in the docs (bryan_att, 13:38:59)
    15. Manoop: will help (bryan_att, 13:40:54)

  3. Requirements Pipeline (bryan_att, 13:42:02)
    1. Anwar shows current collected input at https://etherpad.acumos.org/p/release-plan-athena (bryan_att, 13:43:48)
    2. Anwar shows repo mapping at https://wiki.acumos.org/display/TSC/PTL+Nominations (bryan_att, 13:46:27)
    3. Nat: recommend that PTLs bring reqs to the Requirements committee based upon their assessment of feasibility and priority (bryan_att, 13:49:12)
    4. Nat: describes items he contributed to the etherpad (bryan_att, 13:49:54)
    5. Bryan: we need to ensure that proposed features are analyzed at a high level at least, and documents are available for review (bryan_att, 13:51:43)
    6. Bryan: deploy to Azure for example needs to be revisited (bryan_att, 13:53:29)
    7. Manoop: platform security scanning is a very important one (bryan_att, 13:55:29)
    8. ... also code quality - coverage is too low, we need to push for at least 50% coverage (bryan_att, 13:55:54)
    9. Ofer: has a friend who started WhiteSource and can offer it as a tool for Acumos to use (bryan_att, 13:58:21)
    10. Anwar: post-review and approval by TSC, we will need to assess what can be delivered in the current release (bryan_att, 13:59:33)
    11. Anwar: any of these discussed so far that will have substantial impact on the current arch? (bryan_att, 14:00:57)
    12. Bryan: security and validation are likely to disrupt current design (bryan_att, 14:01:15)


Meeting ended at 14:03:40 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bryan_att (38)
  2. collabot` (3)


Generated by MeetBot 0.1.4.