===================================================
#acumos-meeting: Acumos Community (Product) Meeting
===================================================


Meeting started by bryan_att at 14:06:16 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/acumos-meeting/2018/acumos-meeting.2018-05-16-14.06.log.html
.



Meeting summary
---------------

* Roll Call  (bryan_att, 14:06:28)
* Roll Call  (bryan_att, 14:06:38)
  * Bryan Sullivan  (bryan_att, 14:07:50)
  * Agenda  (bryan_att, 14:08:38)
  * Mission statement  (bryan_att, 14:08:54)
  * LINK: https://wiki.acumos.org/display/MEET  (bryan_att, 14:09:51)
  * High level process for product requirements  (bryan_att, 14:11:25)
  * Licensing  (bryan_att, 14:12:51)
  * Model name uniqueness  (bryan_att, 14:13:42)

* Mission statement  (bryan_att, 14:14:08)
  * 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
    (bryan_att, 14:16:30)
  * 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);  (bryan_att, 14:22:09)
  * LINK:
    https://wiki.acumos.org/download/attachments/4653595/Orange-TSC-Release%20A-2.pdf?version=1&modificationDate=1525729143000&api=v2
    (bryan_att, 14:22:16)
  * Final release date Nov 7  (bryan_att, 14:22:34)
  * Pantelis: so no specific date yet for M1, let's review the proposal
    (bryan_att, 14:23:24)
  * Pantelis: Acumos has too broad an initial scope per the mission
    statement on Acumos.org  (bryan_att, 14:26:33)
  * Pantelis: propose two things for Acumos: (1) orchestration; (2)
    marketplace  (bryan_att, 14:27:08)
  * Bryan: it seems the proposed mission statement is broader / more
    ambitious than the current  (bryan_att, 14:29:59)
  * Ofer: also not clear what is meant by the orchestrator  (bryan_att,
    14:30:16)
  * Pantelis describes the user/contributor role diagram from his
    document  (bryan_att, 14:31:40)
  * 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  (bryan_att, 14:34:37)
  * Bryan: the right side roles seem more related to e.g. ONAP for the
    Telecom domain, other orgs probably for other domains  (bryan_att,
    14:37:45)
  * Ofer: this seems intended to define different goals for Acumos
    (bryan_att, 14:40:17)
  * Pantelis: the paper focuses on differentiation for Acumos
    (bryan_att, 14:41:43)
  * Jamil: the term orchestrator is somewhat confusing - orchestrator is
    a function of the platform e.g. in ONAP  (bryan_att, 14:43:20)
  * 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  (bryan_att, 14:44:48)
  * Pantelis: suggest some high level requirements be written down, e.g.
    modeler support for imperative and declarative ways to interact with
    the platform  (bryan_att, 14:46:42)
  * Bryan: we should start with the existing platform and derive these
    requirements as a start  (bryan_att, 14:47:38)
  * Pantelis: model onboarding needs to be revisited, e.g. use of github
    for onboarding the source to build a model  (bryan_att, 14:48:47)
  * Pantelis: the rest of the paper addresses some existing AI/ML
    platform solutions  (bryan_att, 14:49:56)
  * Pantelis: deployment to private cloud / specialized runtime
    environments seem to be a differentiator for Acumos  (bryan_att,
    14:51:37)
  * Pantelis: the Acumos architecture is not cloud-native  (bryan_att,
    14:53:33)
  * Jamil: seems to be mixing things; do we need an orchestrator as in
    ONAP? this could be  discussed;  (bryan_att, 14:54:24)
  * Jamil: re the new roles (beyond modeler, user, operator); we need a
    clear description of the platform support for that role  (bryan_att,
    14:55:28)
  * 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  (bryan_att,
    14:59:33)
  * Pantelis: suggest that we adopt the kubeflow project  (bryan_att,
    15:00:29)
  * Pantelis: shows the resulting proposed stack  (bryan_att, 15:01:13)
  * Ofer: will continue these meetings  (bryan_att, 15:02:21)
  * Bryan: will provide a doodle poll  (bryan_att, 15:02:39)
  * Bryan: will create a draft agenda  (bryan_att, 15:03:35)



Meeting ended at 15:03:41 UTC.



People present (lines said)
---------------------------

* bryan_att (43)
* collabot` (4)
* aimeeu (0)



Generated by `MeetBot`_ 0.1.4