=======================
#opnfv-mano: opnfv-mano
=======================


Meeting started by pramchan at 14:58:12 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-11-29-14.58.log.html
.



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

* pramchan  (pramchan, 14:58:35)
* agenda bashing  (pramchan, 15:05:09)
  * https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111
    (pramchan, 15:05:31)

* ONAP R1 release overview  (pramchan, 15:07:17)
  * LINK: https://wiki.onap.org/display/DW/Amsterdam+Release+Status
    (pramchan, 15:08:42)
  * LINK:
    https://www.sdxcentral.com/articles/news/onap-rolls-amsterdam-release/2017/11/
    (pramchan, 15:09:41)
  * The release also includes verified blueprints for two initial use
    cases: VoLTE (Voice Over LTE), which allows voice to be unified onto
    IP networks. By virtualizing the core network, the open source code
    is used to design, deploy, monitor, and manage the lifecycle of an
    end-to-end VoLTE service.  (pramchan, 15:10:21)
  * The second use case is residential vCPE. All services are provided
    in-network, which means service providers can add new services
    rapidly and on-demand to their residential customers to create new
    revenue streams to counter competitors.  (pramchan, 15:11:16)
  * Note that ONAP is already implemented in Docker containers, and
    there is a project to include Kubernetes as well that helps with
    enterprise data centers.”  (pramchan, 15:12:49)
  * LINK: https://wiki.onap.org/  (pramchan, 15:13:42)
  * note release 2 'Bejing' will focus on “The focus is on getting
    SD-WAN [software-defined wide-area network] type cases in the next
    release but also packaging the platform for enterprise data
    centers,”  (pramchan, 15:15:30)
  * LINK: https://wiki.onap.org/display/DW/Setting+Up+ONAP  (pramchan,
    15:17:15)
  * ONAP on Kubernetes is available at link
    https://wiki.onap.org/display/DW/ONAP+on+Kubernetes  (pramchan,
    15:18:48)

* 3. Container Integration in NFV Reference Architecture(RA)  (pramchan,
  15:19:18)
  * this is the current state of OPNFV  where we use Docker conatiners
    and Ubuntu JOID has some k8 scenarios  (pramchan, 15:22:49)
  * refer on Euphretes release scenario -
    https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
    (pramchan, 15:25:20)
  * k8-nosdn-lb-noha  JOID         Narinder Gupta & Ruijing Guo   Yes
    Y       Y                Target E 1.0  (pramchan, 15:26:11)
  * LINK:
    https://review.openstack.org/#/c/511991/10/specs/queens/kubernetes-type-for-containerized-VNF.rst
    (phuoc, 15:27:10)
  * k8s-nosdn-nofeature-ha        Compass4NFV     Justin chi      Y
    Y       Y               Target E 1.0  (pramchan, 15:27:11)
  * Implement containerized VNF in Kubernetes VIM  (pramchan, 15:29:39)
  * LINK: http://paste.openstack.org/show/627728/  (phuoc, 15:29:46)
  * which other VIM you are proposing?  (pramchan, 15:29:56)
  * the use case 2 is what you have proposed in link
    http://paste.openstack.org/show/627728/  (pramchan, 15:32:33)
  * In this plan, we will introduce Kubernetes infra driver in VNFM,
    that will be used to manage c-VNF in Kubernetes VIM. Kubernetes
    infra driver use Kubernetes APIs through Kubernetes python client to
    create Kubernetes resources like Service, Deployment, ConfigMap,
    Horizontal Pod Autoscaling, etc, which will be used as a C-VNF.
    Kuryr-Kubernetes also use to connect between VM based and container
    based VNFs.  (pramchan, 15:34:03)
  * c-VNF is conatinerized VNF  (pramchan, 15:35:16)
  * so you need Tacker Openstack module to deploy c-VNF  (pramchan,
    15:36:02)
  * the interface to NFVO be implemented withou Tacker like ONAP?
    (pramchan, 15:37:01)
  * may be if the module can be independent of Tacker then ONAP or
    OpenBagton both can use it, think and answer, ofcourse implement an
    dtest with Takcer but consider the other options  (pramchan,
    15:38:26)
  * that sounds good  (pramchan, 15:38:52)
  * road map of Tacker in Openstack is to implement kubernetes to mnagae
    c-VNF (Container VNF) and this will be in Queen?  (pramchan,
    15:40:45)
  * LINK:
    https://github.com/openstack/tacker/blob/master/samples/tosca-templates/vnfd/tosca-vnfd-hello-world.yaml
    (phuoc, 15:43:29)
  * tosca_simple_profile_for_nfv_1_0_0 and we need to know what VDU, CP
    and VL translate to in c-VNF for kubernetes  (pramchan, 15:49:06)
  * kubectl describe c-VNF is what we need equivalent of  (pramchan,
    15:49:53)
  * the spec field of c-VNF.yaml must contain details of image and
    attributes  (pramchan, 15:53:11)
  * containers:       - name: c-VNF         image: TOSCA:c-VNF
    ports:         - containerPort: ??         volumeMounts:         -
    name: hostvol           mountPath: /usr/share/c-VNF/html
    volumes:         - name: hostvol           hostPath:
    path: /host/doccker/vol  (pramchan, 15:56:02)



Meeting ended at 16:01:18 UTC.



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

* pramchan (53)
* phuoc (28)
* collabot (3)



Generated by `MeetBot`_ 0.1.4