#acumos-meeting: Acumos TSC Architecture Committee

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

Meeting summary

    1. Bryan Sullivan (bryan_att, 14:03:40)
    2. Agenda: continue discussion on proposed features; PTLs to add input on their areas re new features; ongoing input to the agenda for these calls (bryan_att, 14:05:39)

  2. New Features (bryan_att, 14:06:57)
    1. Anwar: I added a new item on the list for ONAP integration at http://etherpad.acumos.org/p/release-plan-athena (bryan_att, 14:07:49)
    2. Chuxin: describes aspects around ONAP integration (bryan_att, 14:09:07)
    3. Guy: there are special things that are needed for ONAP integration (bryan_att, 14:09:26)
    4. Chuxin: there are Jira items created for these aspects (bryan_att, 14:11:08)
    5. Jamil: do you intend ONAP to be used to train a model? (bryan_att, 14:11:40)
    6. Anwar: this for deployment, for any purpose (bryan_att, 14:11:54)
    7. Pantelis: will help with ONAP integration (bryan_att, 14:17:05)
    8. Guy: will help on building microservices (bryan_att, 14:17:23)
    9. Jamil: will provide some help (bryan_att, 14:17:38)
    10. Anwar: also added was OAM support for ELK stack (bryan_att, 14:18:19)
    11. ... this includes standardizing logging across components (bryan_att, 14:19:47)
    12. Anwar: Manoop to update this item with other related work (bryan_att, 14:20:31)
    13. Anwar: working on this is Parichay (contributor/committer) (bryan_att, 14:21:49)
    14. Bryan: we need at least two committers on each repo (bryan_att, 14:22:02)
    15. Anwar: all participants should now determine what committers and contributors will be working on specific repos (bryan_att, 14:22:53)
    16. ... the Release Manager will need to coordinate a sprint plan across projects (bryan_att, 14:23:33)
    17. Anwar: showing the release plan at https://wiki.acumos.org/display/REL/Release+Planning (bryan_att, 14:26:32)
    18. Jamil: describes the release plan per the diagram (bryan_att, 14:28:14)
    19. Anwar: Jamil should work with the release manager to define the number of sprints in the development phase (bryan_att, 14:32:10)
    20. Manoop: PTLs should be able to plan the # of sprints they need per the resources they have and the work to be done (bryan_att, 14:32:42)
    21. Anwar: we need to take care of dependencies across the sprints (bryan_att, 14:33:25)
    22. Manoop: these are mainly API dependencies, which will be delivered by API freeze (bryan_att, 14:33:47)
    23. Anwar: before the 23rd, planning needs to be done so we can approve it in the 25th (bryan_att, 14:37:47)
    24. Anwar: who can take lead on outlining the sprint schedule, since we don't have a release manager assigned yet? (bryan_att, 14:40:27)
    25. Anwar: we need to raise the need for a release manager to the TSC (bryan_att, 14:40:40)
    26. Bryan: in the meantime, we need leads to work together to create plans and share them, similar to how leads need to take on interim PTL roles for projects that do not yet have a PTL (bryan_att, 14:41:46)
    27. Farheen: will work with the PTLs to define the sprint outline (bryan_att, 14:42:06)
    28. Anwar: so Farheen will work with PTLs and provide a draft schedule by Monday (high level plan at least) (bryan_att, 14:43:09)
    29. ... i.e. the outline of the sprint plan, # of sprints and dates. The PTLs can add the details for their project in that frame (bryan_att, 14:43:45)

  3. New Features from etherpad (bryan_att, 14:44:12)
    1. Guy gives overview of the items he contributed at http://etherpad.acumos.org/p/release-plan-athena (bryan_att, 14:46:24)
    2. Anwar: which has arch impact? (bryan_att, 14:46:39)
    3. Guy: the refactoring item (bryan_att, 14:46:48)
    4. Guy: microservice generation will be in the background, invoked when needed (bryan_att, 14:48:48)
    5. Guy: also need UX changes related to what artifacts are just part of the microservice and shold not be presented to the user (bryan_att, 14:49:37)
    6. Kazi: design studio works on microservices, not models (bryan_att, 14:50:00)
    7. Guy: we need to determine when the microservice needs to be created, e.g. through a new UI element or as part of a workflow (bryan_att, 14:50:40)
    8. Anwar: Kazi summarize the new items (bryan_att, 14:51:28)
    9. Kazi: the first is going beyond simple model, to an acyclic graph based model (bryan_att, 14:51:54)
    10. Kazi: for the frst one we already have a design (bryan_att, 14:52:16)
    11. Anwar: the databroker is also used in training right? (bryan_att, 14:52:34)
    12. Kazi: yet it can (bryan_att, 14:52:42)
    13. Anwar: so need to coordinate plans for that with the training project (bryan_att, 14:53:01)
    14. Kazi: I am looking for community committments on supporting the development of the vision and the code for design studio (bryan_att, 14:53:49)
    15. Manoop: recommend the items added be expanded (bryan_att, 14:54:25)
    16. Kazi: the existing items will be linked (bryan_att, 14:54:35)
    17. Anwar: on the item from Chuxin on authorship management (bryan_att, 14:55:41)
    18. Chuxin: we have an analysis that goes into detail on the new work (bryan_att, 14:56:18)
    19. Chuxin: this may be post-R1 (bryan_att, 14:56:48)
    20. Anwar: this is a high priority, as a blocker related to federation needs (bryan_att, 14:57:09)
    21. Anwar: this is a use case where we need a common sprint plan since this will impact various components (bryan_att, 14:58:09)
    22. Anwar: we will go thru the items Mukesh provided on a separate call (bryan_att, 15:00:30)
    23. Anand: Chris Lott and I have created a design for the Admin notification enhancements (bryan_att, 15:01:57)
    24. Anwar: the last two items are from Pantelis (bryan_att, 15:03:06)
    25. ... one we are working on is deployment to k8s (bryan_att, 15:03:40)
    26. Pantelis: giveb the PoC plan for Training, we will provide some cloud-native baseline code that will help (bryan_att, 15:04:34)
    27. Anwar: reminder to all to vote your priorities for the features as requested via the list (bryan_att, 15:05:06)


Meeting ended at 15:05:09 UTC (full logs).

Action items

  1. (none)


People present (lines said)

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


Generated by MeetBot 0.1.4.