#acumos-meeting: Acumos TSC Architecture Committee

Meeting summary

1. Pantelis: Community approval of Data Pipeline and Model Training Pipeline features for Release A & B (bryan_att, 14:08:14)
   1. per the Jira items ACUMOS-1367, 1420, 1466, 1418 (bryan_att, 14:17:08)
   2. and description at https://wiki.acumos.org/display/TRAIN (bryan_att, 14:17:38)
   3. and specifically https://wiki.acumos.org/display/TRAIN/E2E+Project+Requirements (bryan_att, 14:18:28)
   4. For data pipeline, https://wiki.acumos.org/display/TRAIN/DP+Requirements (bryan_att, 14:22:07)
   5. Bryan: additional explanation on what "kubernetes native APIs" and the role of the Acumos platform in supporting "diverse environments" for aspects of the data pipeline, would be helpful for understanding and agreement with these requirements (bryan_att, 14:23:24)
   6. Bryan: an architectural concept would also be very helpful to clarify the role of the Acumos platform and the interfaces it needs to support to these diverse environments, and how those interfaces might depend on "kubernetes native APIs" is that's part of the intent of that requirement (bryan_att, 14:24:41)
   7. Anwar: how are ETL components linked to training? (bryan_att, 14:29:18)
   8. Anwar: how will this fit into leveraging CMLP code? (bryan_att, 14:30:07)
   9. Adi: for data pipline, we have some components that can be leveraged. We have kafka for example, but need to understand the overall experience expected, to be sure we can leverage the assets we have implemented. (bryan_att, 14:31:00)
   10. Anwar: any of those reqs planned for Nov release? (bryan_att, 14:31:12)
   11. Adi: already have data set mgmt capabilities (bryan_att, 14:31:26)
   12. Anwar: for Acumos Nov release? (bryan_att, 14:31:47)
   13. Adi: that's unclear yet, need deeper dive on that (bryan_att, 14:32:05)
   14. Anwar: Pantelis, recommend you participate in that discussion (bryan_att, 14:32:26)
   15. Pantelis: it's important to ensure the DP arch moving forward can be supported in all the envs using a cloud-native approach (bryan_att, 14:33:05)
   16. Anwar: is CMLP implementation k8s-based (bryan_att, 14:33:29)
   17. Adi: yes (bryan_att, 14:33:46)
   18. Bryan: does this mean cloud-native, or just that it runs under k8s (bryan_att, 14:34:04)
   19. Adi: just runs under k8s (bryan_att, 14:34:11)
   20. Bryan: e.g. functional resiliency, microservice-oriented means specific things about the ephermerality of services - and will cause us to need to restructure/refactor platform components probably (bryan_att, 14:36:17)
   21. Pantelis: moving on to https://wiki.acumos.org/display/TRAIN/MTP+Requirements (bryan_att, 14:37:01)
   22. Anwar: for the Community Committee, has there been a review and agreement with these requirements? (bryan_att, 14:47:12)
   23. Ofer: not specifically (bryan_att, 14:47:29)
   24. Anwar: there may be some things e.g. data set management that the CMLP team can commit for Athena - but we will check (bryan_att, 14:48:10)
   25. Manoop: will all of this be CMLP seed code? (bryan_att, 14:48:28)
   26. Anwar: only the data set management, maybe other things, but this is much larger (bryan_att, 14:48:51)
   27. Manoop: assume most of this is for future releases; hat team will develop this? (bryan_att, 14:49:26)
   28. Anwar: need to hear from Nat or otherwise know what related to this will be delivered in Athena, high-level epics at least (bryan_att, 14:50:01)
   29. Nat: we have requested the input from PTLs and have some, but not all (bryan_att, 14:50:40)
   
   
2. Portal API review (bryan_att, 14:50:53)
   1. Mukesh: shares https://wiki.acumos.org/display/PUX/Athena+M3+Portal+Deliverables+for+API+Freeze+Milestone+Checklist (bryan_att, 14:51:37)
   2. Bryan: the API spec needs to define the request/response objects (bryan_att, 14:54:34)

Action items

1. (none)

People present (lines said)

1. bryan_att (34)
2. collabot (3)
3. talasila (1)