14:03:28 #startmeeting Acumos TSC Architecture Committee 14:03:28 Meeting started Thu Jun 14 14:03:28 2018 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:28 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:03:28 The meeting name has been set to 'acumos_tsc_architecture_committee' 14:03:40 #info Bryan Sullivan 14:05:39 #info Agenda: continue discussion on proposed features; PTLs to add input on their areas re new features; ongoing input to the agenda for these calls 14:06:57 #topic New Features 14:07:49 #info Anwar: I added a new item on the list for ONAP integration at http://etherpad.acumos.org/p/release-plan-athena 14:09:07 #info Chuxin: describes aspects around ONAP integration 14:09:26 #info Guy: there are special things that are needed for ONAP integration 14:11:08 #info Chuxin: there are Jira items created for these aspects 14:11:40 #info Jamil: do you intend ONAP to be used to train a model? 14:11:54 #info Anwar: this for deployment, for any purpose 14:17:05 #info Pantelis: will help with ONAP integration 14:17:23 #info Guy: will help on building microservices 14:17:38 #info Jamil: will provide some help 14:18:19 #info Anwar: also added was OAM support for ELK stack 14:19:47 #info ... this includes standardizing logging across components 14:19:58 # info NAT - TechM 14:20:31 #info Anwar: Manoop to update this item with other related work 14:21:49 #info Anwar: working on this is Parichay (contributor/committer) 14:22:02 #info Bryan: we need at least two committers on each repo 14:22:53 #info Anwar: all participants should now determine what committers and contributors will be working on specific repos 14:23:33 #info ... the Release Manager will need to coordinate a sprint plan across projects 14:26:32 #info Anwar: showing the release plan at https://wiki.acumos.org/display/REL/Release+Planning 14:28:14 #info Jamil: describes the release plan per the diagram 14:32:10 #info Anwar: Jamil should work with the release manager to define the number of sprints in the development phase 14:32:42 #info Manoop: PTLs should be able to plan the # of sprints they need per the resources they have and the work to be done 14:33:25 #info Anwar: we need to take care of dependencies across the sprints 14:33:47 #info Manoop: these are mainly API dependencies, which will be delivered by API freeze 14:37:47 #info Anwar: before the 23rd, planning needs to be done so we can approve it in the 25th 14:40:27 #info Anwar: who can take lead on outlining the sprint schedule, since we don't have a release manager assigned yet? 14:40:40 #info Anwar: we need to raise the need for a release manager to the TSC 14:41:46 #info 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 14:42:06 #info Farheen: will work with the PTLs to define the sprint outline 14:43:09 #info Anwar: so Farheen will work with PTLs and provide a draft schedule by Monday (high level plan at least) 14:43:45 #info ... i.e. the outline of the sprint plan, # of sprints and dates. The PTLs can add the details for their project in that frame 14:44:12 #topic New Features from etherpad 14:46:24 #info Guy gives overview of the items he contributed at http://etherpad.acumos.org/p/release-plan-athena 14:46:39 #info Anwar: which has arch impact? 14:46:48 #info Guy: the refactoring item 14:48:48 #info Guy: microservice generation will be in the background, invoked when needed 14:49:37 #info Guy: also need UX changes related to what artifacts are just part of the microservice and shold not be presented to the user 14:50:00 #info Kazi: design studio works on microservices, not models 14:50:40 #info 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 14:51:18 #inf Anwar: Kazi summarize the new items 14:51:28 #info Anwar: Kazi summarize the new items 14:51:54 #info Kazi: the first is going beyond simple model, to an acyclic graph based model 14:52:16 #info Kazi: for the frst one we already have a design 14:52:34 #info Anwar: the databroker is also used in training right? 14:52:42 #info Kazi: yet it can 14:53:01 #info Anwar: so need to coordinate plans for that with the training project 14:53:49 #info Kazi: I am looking for community committments on supporting the development of the vision and the code for design studio 14:54:25 #info Manoop: recommend the items added be expanded 14:54:35 #info Kazi: the existing items will be linked 14:55:41 #info Anwar: on the item from Chuxin on authorship management 14:56:18 #info Chuxin: we have an analysis that goes into detail on the new work 14:56:48 #info Chuxin: this may be post-R1 14:57:09 #info Anwar: this is a high priority, as a blocker related to federation needs 14:58:09 #info Anwar: this is a use case where we need a common sprint plan since this will impact various components 15:00:30 #info Anwar: we will go thru the items Mukesh provided on a separate call 15:01:57 #info Anand: Chris Lott and I have created a design for the Admin notification enhancements 15:03:06 #info Anwar: the last two items are from Pantelis 15:03:40 #info ... one we are working on is deployment to k8s 15:04:34 #info Pantelis: giveb the PoC plan for Training, we will provide some cloud-native baseline code that will help 15:05:06 #info Anwar: reminder to all to vote your priorities for the features as requested via the list 15:05:09 #endmeeting