================================
#onap-meeting: ARC July 11, 2017
================================


Meeting started by gildaslanilis at 14:07:22 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-07-11-14.07.log.html
.



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

* Lingli Deng, China Mobile  (Lingli_, 14:08:57)
* Terminology  (gildaslanilis, 14:10:12)
  * , as far as possible recommendation is to use ETSI terminology.
    (gildaslanilis, 14:11:47)
  * Review of SO definition  (gildaslanilis, 14:13:24)
  * , SO description presented is necessary but not completely
    sufficient.  (gildaslanilis, 14:19:07)
  * Review of NFV definition  (gildaslanilis, 14:19:52)
  * Clarification that system is stateful when it performs a particular
    action, the system remains stateful until the requested action is
    completed.  (gildaslanilis, 14:24:02)
  * Review of VNFM definition  (gildaslanilis, 14:31:28)
  * Presentation of mapping between ONAP components and the above
    definitions.  (gildaslanilis, 14:32:14)

* Paul presented slides detailling Orchestration  (gildaslanilis,
  14:39:58)
  * Paul presents options to align APPC, NFV and SO.  (gildaslanilis,
    14:43:51)
  * Goal is to avoid 2 silos approach.  (gildaslanilis, 14:44:31)
  * It is up to ONAP community to decide how ETSI MANO compliant ONAP
    should be.  (gildaslanilis, 14:50:15)
  * The alignment could be achieve through a phase approach.
    (gildaslanilis, 14:50:54)

* Deployment Options  (gildaslanilis, 14:59:12)
  * 3 options are presented and iscussed.  (gildaslanilis, 15:04:37)
  * Point that a VNF should not care about the type of manager (APP-C or
    VF-C) it is handle with.  (gildaslanilis, 15:13:16)

* Details SO flows by Seshu  (gildaslanilis, 15:23:53)
  * Suggestion made to create a separate branch to experiment longer
    term functionality. Project team has to decide on this option.
    (gildaslanilis, 15:53:20)
  * Concern on resource availability to hit the Amsterdam Release
    target.  (gildaslanilis, 15:54:00)
  * AGREED: Starting for Baseline (option 1) and then moving to option 2
    (Jamil) for the long term.  (gildaslanilis, 16:00:35)
  * AGREED: SO team to look up to better alignment with Architecture
    (opt 1)  (gildaslanilis, 16:01:19)



Meeting ended at 16:01:42 UTC.



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

* gildaslanilis (23)
* collabot` (3)
* Lingli_ (1)



Generated by `MeetBot`_ 0.1.4