14:06:16 <bryan_att> #startmeeting Acumos Community (Product) Meeting
14:06:16 <collabot`> Meeting started Wed May 16 14:06:16 2018 UTC.  The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:16 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:06:16 <collabot`> The meeting name has been set to 'acumos_community__product__meeting'
14:06:28 <bryan_att> #info Roll Call
14:06:38 <bryan_att> #topic Roll Call
14:07:50 <bryan_att> #info Bryan Sullivan
14:08:20 <bryan_att> #chair bryan_att, aimeeu
14:08:20 <collabot`> Current chairs: aimeeu bryan_att
14:08:38 <bryan_att> #info Agenda
14:08:54 <bryan_att> #info Mission statement
14:09:51 <bryan_att> #link https://wiki.acumos.org/display/MEET
14:11:25 <bryan_att> #info High level process for product requirements
14:12:51 <bryan_att> #info Licensing
14:13:42 <bryan_att> #info Model name uniqueness
14:14:08 <bryan_att> #topic Mission statement
14:16:30 <bryan_att> #info Pantelis presents input sent in https://lists.acumos.org/g/acumosaicommunity/topic/strategic_positioning_of/19200063?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,19200063
14:22:09 <bryan_att> #info Pantelis: Jamil proposed a plan for the 1st release in the TSC meeting last week, and the TSC agreed on the M0 date as May 21 (start of release planning);
14:22:16 <bryan_att> #link https://wiki.acumos.org/download/attachments/4653595/Orange-TSC-Release%20A-2.pdf?version=1&modificationDate=1525729143000&api=v2
14:22:34 <bryan_att> #info Final release date Nov 7
14:23:24 <bryan_att> #info Pantelis: so no specific date yet for M1, let's review the proposal
14:26:33 <bryan_att> #info Pantelis: Acumos has too broad an initial scope per the mission statement on Acumos.org
14:27:08 <bryan_att> #info Pantelis: propose two things for Acumos: (1) orchestration; (2) marketplace
14:29:59 <bryan_att> #info Bryan: it seems the proposed mission statement is broader / more ambitious than the current
14:30:16 <bryan_att> #info Ofer: also not clear what is meant by the orchestrator
14:31:40 <bryan_att> #info Pantelis describes the user/contributor role diagram from his document
14:34:37 <bryan_att> #info Bryan: the roles on the right of the diagram seem beyond the current Acumos scope, into the application/business domain addressing goals of specific business application of AI models
14:37:45 <bryan_att> #info Bryan: the right side roles seem more related to e.g. ONAP for the Telecom domain, other orgs probably for other domains
14:40:17 <bryan_att> #info Ofer: this seems intended to define different goals for Acumos
14:41:43 <bryan_att> #info Pantelis: the paper focuses on differentiation for Acumos
14:43:20 <bryan_att> #info Jamil: the term orchestrator is somewhat confusing - orchestrator is a function of the platform e.g. in ONAP
14:44:48 <bryan_att> #info Jamil: re the roles on the diagram right, it may be interesting to expand focus to this role; others (e.g. infra) are probably better beyond Acumos
14:46:42 <bryan_att> #info Pantelis: suggest some high level requirements be written down, e.g. modeler support for imperative and declarative ways to interact with the platform
14:47:38 <bryan_att> #info Bryan: we should start with the existing platform and derive these requirements as a start
14:48:47 <bryan_att> #info Pantelis: model onboarding needs to be revisited, e.g. use of github for onboarding the source to build a model
14:49:56 <bryan_att> #info Pantelis: the rest of the paper addresses some existing AI/ML platform solutions
14:51:37 <bryan_att> #info Pantelis: deployment to private cloud / specialized runtime environments seem to be a differentiator for Acumos
14:53:33 <bryan_att> #info Pantelis: the Acumos architecture is not cloud-native
14:54:24 <bryan_att> #info Jamil: seems to be mixing things; do we need an orchestrator as in ONAP? this could be  discussed;
14:55:28 <bryan_att> #info Jamil: re the new roles (beyond modeler, user, operator); we need a clear description of the platform support for that role
14:59:33 <bryan_att> #info Bryan: orchestration is an existing component. e.g. to deploy in diverse cloud envs; also focusing the microservices on docker runtimes is already inline with key cloud-native requirements, and we can extend the deployment support to k8s envs
15:00:29 <bryan_att> #info Pantelis: suggest that we adopt the kubeflow project
15:01:13 <bryan_att> #info Pantelis: shows the resulting proposed stack
15:02:21 <bryan_att> #info Ofer: will continue these meetings
15:02:39 <bryan_att> #info Bryan: will provide a doodle poll
15:03:35 <bryan_att> #info Bryan: will create a draft agenda
15:03:41 <bryan_att> #endmeeting