#acumos-meeting: Acumos TSC Community (Product) Committee

Meeting started by bryan_att at 17:03:03 UTC (full logs).

Meeting summary

    1. Bryan Sullivan (bryan_att, 17:04:51)

  2. Release Feature Input (bryan_att, 17:06:02)
    1. Ofer: last week we discussed the input on the etherpad https://etherpad.acumos.org/p/release-plan-athena (bryan_att, 17:07:06)
    2. Ofer: also we sent an email https://lists.acumos.org/g/acumosaicommunity/topic/athena_release_community/21898531?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21898531 which describes the result and next steps (bryan_att, 17:08:19)
    3. Ofer: in this meeting we will start reviewing the features that are included with some details, with further steps per the email (bryan_att, 17:09:38)
    4. The community committee will review all new feature descriptions, and provide an advisory vote on for each, on what work (e.g., analysis, design, implementation) seems essential for this release, to proceed to assessment of architectural impact etc. (as below) (bryan_att, 17:10:12)
    5. The architecture committee will assess (rough estimate) the impact to the architecture and related components for each feature determined essential by the community (bryan_att, 17:10:40)
    6. Respective PTLs and team SMEs will assess (rough estimate) the resources needed to implement the new features recommended by the community, and improvements as determined to be essential by the PTLs and teams for the components/etc. in scope of the project (bryan_att, 17:11:02)
    7. A subset of the recommended feature/improvement work items will be reviewed and approved by the TSC for the release (bryan_att, 17:11:17)
    8. Bryan: suggest to go thru the new features from the etherpad first; then the pre-existing items from Jira, and determine whether they are defined enough (or still valid) for further assessment by the Arch committee (bryan_att, 17:15:26)
    9. Rueben: we also need a broader end-user focused description of the goals so we end up with a cohesive product (bryan_att, 17:16:27)
    10. ACUMOS-1099; no objection to level of details, the ask is understood but questionable as to what can be delivered in this release (bryan_att, 17:20:55)
    11. ACUMOS-1098: Use Cases for Testing - we need more info from Jamil (bryan_att, 17:22:39)
    12. ACUMOS-1096 Automating functional test cases for every component - we need more info on what work will relate to this goal (bryan_att, 17:24:11)
    13. ACUMOS-1095 Sonar 50% code coverage requirement on every repo - similar - we need more input but no objection (bryan_att, 17:27:48)
    14. ACUMOS-1094 Security of the platform - relates to Jira items Bryan will link, with wiki refs (bryan_att, 17:29:08)
    15. ACUMOS-1093 Baseline performance criteria by identifying and measuring current performance of the components - needs to be aligned with ACUMOS-1092 Performance benchmarking on critical Operations - and further explained (bryan_att, 17:30:50)
    16. ACUMOS-1092 Performance benchmarking on critical Operations - see above (bryan_att, 17:31:37)
    17. ACUMOS-1091 Single logging system across components and generating usage reports - need more details but this is existing work in progress (bryan_att, 17:33:51)
    18. CUMOS-1089 RBAC: Role and Privilege based Operations - need more details (bryan_att, 17:34:29)
    19. ACUMOS-1088 Lifecycle management of model in production - Bryan will link Pantelis's input and earlier notes (bryan_att, 17:35:25)
    20. ACUMOS-1087 Deploy model to kubernetes environment - details exist, and will be discussed in the Deployment project team meeting - also relates to ACUMOS-1086 Deploy to local environment (bryan_att, 17:37:08)
    21. ACUMOS-1086 Deploy to local environment and ACUMOS-1081 Deploy model to Google cloud platform ( GCP) - similar to above (bryan_att, 17:38:21)
    22. ACUMOS-1079 Deploy Model to AWS similar to above (bryan_att, 17:38:45)
    23. ACUMOS-1077 Licensing - need input from Rueben on licensing goals and areas of functionality in scope (bryan_att, 17:43:12)
    24. Bryan: this is also one of those items that is probably roadmapped but we expect some work in this release to define the goals (bryan_att, 17:43:56)
    25. Rueben: there is a big community aspect for that - we need to focus on the intent of the community (bryan_att, 17:44:52)
    26. Reuben: and we need vendor input on this as well (bryan_att, 17:45:18)
    27. ACUMOS-1075 Model interchange using other standards - Bryan will link the input from Jamil (bryan_att, 17:47:30)
    28. ACUMOS-1072 Train model - Pantelis will have the 1st meeting on this project (Training) next week - also earlier analysis from AT&T will be described at a high level (scope of work) (bryan_att, 17:49:58)
    29. ACUMOS-1071 Support Directed Acyclic Graph - based Composite Solution Creation - aka support Split and Join Semantics - Kazi added a note "We have designed this feature and the User Stories are in JIRA. AT&T and Tech M teams are working on the development of this issue." (bryan_att, 17:51:15)
    30. ACUMOS-1044 Acumos project scanning for license/vulnerability - also relates ACUMOS-1041 Model scanning for license, vulnerability - details are provided on the wiki (bryan_att, 17:55:14)
    31. Anwar: how do we want to proceed on approval - it will take some time to go thru these and balance the priorities and resources - we can expect that a small subset of items will be deliverable for Nov (bryan_att, 17:58:01)
    32. Bryan: I can provide a form for collecting input from the committees (bryan_att, 18:01:14)
    33. Anwar: Arch session is thurs - we will use the time for discussion (bryan_att, 18:02:04)
    34. Ofer agree that a form to provide input is useful - but we need more info where possible (bryan_att, 18:03:14)
    35. Bryan to send out a form for input and use by the communities (bryan_att, 18:03:35)


Meeting ended at 18:06:53 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bryan_att (41)
  2. collabot_ (3)
  3. NAT_ (1)


Generated by MeetBot 0.1.4.