14:01:14 <s3wong> #startmeeting clover
14:01:14 <collabot> Meeting started Mon Jan  8 14:01:14 2018 UTC.  The chair is s3wong. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:14 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:01:14 <collabot> The meeting name has been set to 'clover'
14:01:54 <amitgkp> Hello everyone
14:02:20 <amitgkp> I guess we have meeting here or on slack
14:02:39 <s3wong> amitgkp: meeting is here, and you are currently in the middle of meeting :-)
14:03:07 <s3wong> #topic Logistics
14:03:21 <s3wong> Welcome to the first ever OPNFV Clover meeting
14:03:38 <yujunz> \o/
14:03:48 <amitgkp> Thanks :s3wong for quick response.
14:03:55 <dneary> Hi all
14:04:00 <dneary> #info Dave
14:04:07 <liangqi_> #info liangqi
14:04:11 <zhipeng> #info Howard
14:04:13 <ywu> #info ywu
14:04:18 <amitgkp> #info Amit
14:04:18 <xuanjia> #info xuanjia
14:04:27 <dneary> amitgkp, I prefer to avoid Slack, if possible.
14:04:48 <amitgkp> dne
14:04:52 <amitgkp> Okay
14:04:56 <dneary> Hi xuanjia! We missed you in Austin
14:05:05 <s3wong> At the very least, we need Meetbot, so our meeting log will be saved
14:05:23 <amitgkp> Alright Stephen.
14:05:24 <ywu> irc meeting is ok
14:05:54 <s3wong> Here are the logistic info
14:06:19 <s3wong> Our repo is #link  https://github.com/opnfv/clover
14:06:35 <s3wong> An example of our gerrit review is:
14:06:45 <s3wong> #link https://gerrit.opnfv.org/gerrit/#/c/46697/
14:07:42 <s3wong> And if you are to file (or view) JIRA items, it is under project Clover on lira.opnfv,org
14:07:51 <s3wong> jira.opnfv.org
14:07:56 <dneary> s3wong, xuanjia: What are the key questions where we need to agree on answers?
14:08:08 <s3wong> (Sorry, auto correction)
14:08:11 <dneary> I have some ideas - certainly I have some questions of my own
14:08:21 <s3wong> dneary: go ahead
14:08:32 <s3wong> #topic Open questions
14:08:38 <dneary> I think we need clarity on work items
14:08:56 <dneary> #info Dave thinks we need clarity on work items
14:09:52 <dneary> #info It seems we can take on Clover from one of two sides - start with container projects, and figure out what is missing for Telco applications, or start with a Telco application, and figure out how to leverage container projects like Istio to get them running on k8s
14:10:25 <dneary> #info Dave's preference is for the 2nd approach - dicument the application use-case first, and how we use CNCF projects to move to a container platform
14:10:39 <dneary> s3wong, In fact, that's the main question I have
14:10:53 <s3wong> dneary: good question (and suggestion)
14:10:54 <xuanjia> hi dneary, glad to see you here. i prefer the second choise. start with a telco application .
14:11:34 <dneary> xuanjia, We have a few options - we can do an easy one (like Clearwater) first, or we can aim for a hard one (like CRAN) and see how far we get
14:11:45 <amitgkp> Hi dneary, I agree with second option
14:11:59 <s3wong> Clover was proposed to investigate the question: "How can one build VNFs as cloud native applications?"
14:12:08 <dneary> I think there's a middle ground possible too. Does anyone have a candidate VNF to containerize?
14:12:43 <s3wong> dneary: I think the simple starting VNF is Metaswitch's Clearwater (IMS)
14:13:03 <zhipeng> FYI we are starting to form a Policy WG in Kubernetes, which could also take inputs from Clover project discussion
14:13:09 <zhipeng> #link https://docs.google.com/document/d/1Ht8wpj4j9YfAA7aVv9Yn3Ci1T_MLMWt0DBr0QmxI2OM/edit?usp=sharing
14:13:44 <dneary> s3wong, Yes
14:13:57 <ywu> has clearwater VNF been converted to containerized? i did not find much information about this on their website.
14:13:58 <s3wong> zhipeng: and that is Policy WG under Kubernetes (not under OPNFV)?
14:14:15 <zhipeng> yes, so that would be a upstream WG for OPNFV I suppose
14:14:21 <dneary> s3wong, There is also an intern working on deploying Clearwater on k8s for containers4nfv - we could leverage her work too
14:14:24 <s3wong> ywu: in fact, there are two repos on Clearwater k8s
14:14:39 <xuanjia> zhipeng, ywu https://github.com/opnfv/container4nfv/tree/master/src/vagrant/kubeadm_clearwater
14:14:44 <s3wong> #link. https://github.com/Metaswitch/clearwater-docker
14:14:54 <s3wong> The above one is from MetaSwitch themselves
14:15:04 <ywu> thanks, s3wong and xuanjia, i will take a look after meeting.
14:15:10 <s3wong> #link  https://github.com/Intel-Corp/clearwater-kubernertes
14:15:12 <zhipeng> xuanjia gr8t link, I will add it to the reference
14:15:16 <s3wong> The second one is from Intel
14:15:45 <xuanjia> the script is running by vagrant. it's very easy to use.
14:15:48 <amitgkp> Yes, s3wong that above Intel repo is a good start.
14:15:54 <dneary> ywu, s3wong: The intern is enriquetaso - I think it would be a good way to get us started to build on her internship project
14:16:17 <s3wong> dneary: good --- will definitely like to leverage. I guesss his/her work is on the link xuanjia  just provides?
14:16:20 <s3wong> provided
14:17:45 <s3wong> OK, with dneary 's question as starting point --- we should move into Fraser release discussion
14:17:54 <s3wong> #topic Fraser goals
14:18:04 <xuanjia> so if we want to use service mesh in clearwater..i thin we need to add Metaswitch people in .
14:18:15 <xuanjia> s/thin/think/g
14:18:22 <dneary> s3wong, She pointed me at https://github.com/opnfv/container4nfv/blob/master/src/vagrant/kubeadm_clearwater/examples/create_and_apply.sh
14:18:43 <dneary> s3wong, I think we might want to move towards having a Helm chart for it
14:19:02 <dneary> xuanjia, I agree.
14:19:17 <dneary> xuanjia, Also, we should re-engage with the F5 people who we met in Austin
14:19:30 <xuanjia> that's awesome!
14:19:45 <s3wong> So with the discussion so far, the team seems to agree on doing Clearwater on k8s with Istio as a good initial goal for Fraser
14:20:02 <amitgkp> Agree.
14:20:06 <yujunz> Agree
14:20:09 <liangqi_> +1
14:20:11 <xuanjia> +1
14:20:19 <ywu> Agreed
14:20:25 <s3wong> #info Fraser goal: Clearwater IMS on k8s with Istio as service mesh
14:21:07 <s3wong> dneary, xuanjia: looking into Clearwater current architecture, I agree it would be beneficial to have MetaSwitch folks to participate
14:21:42 <s3wong> As Clearwater does its own load-balancing (based on DNS), so Envoy would need to take over. Inevitably there will likely be some code changes
14:22:42 <dneary> +1
14:22:57 <s3wong> Let's go into possible / initial task lists to achieve our Fraser goal
14:23:09 <dneary> s3wong, Yes - there may be some push-back from them too
14:23:37 <dneary> They want to make sure their application is cloud native across VMs and containers, on public and private infrastructure
14:23:46 <s3wong> dneary: agreed. Will need to identify the changes and work with the Clearwater community
14:24:26 <s3wong> #topic Fraser tasks
14:24:59 <s3wong> We will need to leverage other projects' k8s installation
14:25:31 <dneary> Agreed - we should connect with containers4nfv to make sure that we can use their pods
14:26:14 <s3wong> dneary: +1
14:26:15 <xuanjia> we can use vagrant way to install our basic enviroment. https://github.com/opnfv/container4nfv/tree/master/src/vagrant/kubeadm_basic
14:26:46 <xuanjia> For the pod, i will let ruijing and JackChen give your answer.
14:27:38 <liangqi_> compass4nfv support k8s installation
14:27:56 <s3wong> xuanjia: what version of k8s is installed via these installation scripts?
14:28:34 <yujunz> I suppose it is 1.9.1 ?
14:28:59 <s3wong> yujunz: nice, so latest release all the time...
14:29:08 <xuanjia> s3wong, now we privode 1.7. If we want to use 1.9, i can let ruijing upgrate it.
14:29:28 <ywu> i don't have preference of k8s installation tool, but I don't know current Clearwater IMS k8s scripts has dependencies on specific k8s and docker version or not.
14:30:07 <dneary> xuanjia, s3wong: I see upstream moving towards Helm as a standard template for k8s apps - I suggest ewe have "deploy Clearwater with Helm" as a task
14:30:08 <xuanjia> From my understanding, we don't want to put too much work on Installers project in OPNFV. we need to demo it and run it as our first priorty task.
14:30:23 <s3wong> xuanjia: official 1.7 is an interesting choice --- as there may be dependency on Istio to use an alpha k8s feature there is more commonly support around 1.7.5
14:30:40 <dneary> Similar to ywu, I have no preference on k8s installation tool at this point (well, OpenShift would be nice, but... ;-) )
14:30:44 <s3wong> dneary: good suggestion. Let's add that as a task
14:31:18 <dneary> #info Leverage containers4nfv deployment of Kubernetes
14:31:39 <dneary> #info Aim to have Clearwater deployed using Helm by Fraser
14:31:40 <s3wong> ywu: no, I don't have preference neither (and k8s installation itself is out of scope for Clover, though it is clearly a dependency)
14:32:29 <s3wong> We will also need to have a task on Istio installation
14:32:49 <ywu> if we don't have preference, maybe we should decide which k8s, istio, and docker version in short term.
14:34:44 <ywu> and clearwater IMS version.
14:35:08 <s3wong> For Istio sidecar injection, if we are going to use the "initializer" feature, we need to have at least k8s 1.7
14:35:46 <xuanjia> okay. i put container4nfv support k8s 1.9.0 as a task for me.
14:36:09 <s3wong> xuanjia: thanks
14:36:58 <s3wong> #info xuanjia will take up support of k8s 1.9 for container4nfv installation
14:38:00 <s3wong> In fact, according to  https://istio.io/docs/setup/kubernetes/quick-start.html, you would need k8s 1.7.3 or newer... so moving to 1.9 would be great
14:38:31 <amitgkp> +1
14:38:40 <xuanjia> Okay.
14:39:05 <amitgkp> K8s 1.9.1 has CoreDNS support also
14:39:58 <s3wong> Anyone interested in taking a look at Clearwater Helm charts?
14:41:04 <yujunz> I can volunteer myself for the task
14:41:06 <dneary> s3wong, I will take the task of moving it along
14:41:17 <s3wong> dneary, yujunz: Thanks!
14:41:20 <liangqi_> add me
14:41:20 <dneary> I don't think I will be able to do the work (but I can certainly try).
14:41:48 <dneary> liangqi_, yujunz: Can one of you take the lead, in that case?
14:42:06 * dneary has to step away for a moment...
14:42:10 <s3wong> #info yujunz, dneary, and liangqi_ will coordinate to work on Helm charts for Clearwater
14:42:47 <yujunz> I can try it.
14:42:54 <s3wong> yujunz: thanks!
14:43:11 <s3wong> #info yujunz will take the lead on the Clearwater Helm charts task
14:45:45 <s3wong> Script to do Istio installation on k8s 1.9 can be done in parallel
14:47:08 <s3wong> Anyone interested to take up the task of Istio installation and verifying the installation?
14:47:38 <ywu> I can help on this.
14:47:46 <s3wong> ywu: Thanks!
14:48:30 <s3wong> #info ywu to work on Istio installation on k8s 1.9
14:49:43 <s3wong> We should also investigate the changes needed for Clearwater to run on top of Istio, and generate the list so we can contact Clearwater community (if needed)
14:51:23 <s3wong> I can look into that --- anyone else interested?
14:51:55 <ywu> i am interested as well. but i don't have much experience in Clearwater yet.
14:52:17 <amitgkp> Alright. I can help on this.
14:52:32 <dneary> Let's make sure that we get enriquetaso looped in to what we want to do
14:52:47 <s3wong> dneary: sure
14:52:57 <s3wong> ywu, amitgkp: cool!
14:53:38 <amitgkp> Sure
14:53:56 <s3wong> #info s3wong, ywu and amitgkp will look into gaps on Clearwater running on Istio
14:54:10 <s3wong> I think that is a good list of tasks for now
14:54:40 <s3wong> #topic Open discussion
14:54:57 <s3wong> Anything else?
14:55:17 <amitgkp> Yes, we also have to get a vPOD
14:56:01 <xuanjia> amitgkp, i ask my team if we have one , if possible we can share it.
14:56:09 <yujunz> Do we aim to set up CI jobs for all the tasks mentioned above?
14:56:21 <s3wong> xuanjia: thanks
14:56:27 <ywu> what is vPOD?
14:57:16 <dneary> virtual pod
14:57:26 <amitgkp> Thanks xuanjia
14:57:52 <s3wong> yujunz: good question... we need to have test cases for the tasks in place (at least verifying installations are done). So we should have a CI jobs for them
14:59:05 <yujunz> Yes, I think that might be mandatory as a release criteria.
15:00:07 <s3wong> yujunz: indeed. Deploy jobs in OPNFV CI is a milestone (MS5)... so definitely we need to work on that
15:01:30 <s3wong> Thanks everyone for a great discussion!
15:01:51 <s3wong> That would a good first meeting. Looking forward to working with you guys to get the first release out
15:02:13 <ywu> thanks!
15:02:33 <s3wong> Thanks everyone!
15:02:38 <s3wong> #endmeeting