14:06:45 #startmeeting SFC weekly meeting, September 16, 2015 14:06:45 Meeting started Wed Sep 16 14:06:45 2015 UTC. The chair is ebrjohn. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:06:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:06:45 The meeting name has been set to 'sfc_weekly_meeting__september_16__2015' 14:06:54 #info ebrjohn Brady Johnson 14:07:05 Can you guys info in again, now that the meeting has started 14:07:10 #char rprakash 14:07:16 #chair rprakash 14:07:16 Current chairs: ebrjohn rprakash 14:07:22 #chair bryan_att 14:07:22 Current chairs: bryan_att ebrjohn rprakash 14:07:35 #info David Dolson 14:07:37 #info Andre Fredette (afredette) 14:08:40 #info http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-September/005090.html Agenda 14:09:43 #info Manuel Rebellon 14:09:58 #tpopic I created a first version of a simple VnfMgr simulator script: 14:10:30 undo 14:10:32 #undo 14:10:32 Removing item from minutes: 14:10:40 #topic simple VnfMgr simulator script: 14:11:35 #link https://gerrit.opnfv.org/gerrit/1587 14:15:29 #action Brady ohnson to create document for sfc setup 14:15:30 #undo 14:15:30 Removing item from minutes: 14:15:49 #action Brady Johnson to create document for sfc setup 14:17:34 #info showing using GUI on opendaylight creating SFC path using the script showing VNF-M in the gerrit 14:18:30 #info next step is to create vm per sfc using openstack 14:19:18 #info Is there a plan to use Tacker as VNF-M 14:19:48 #info Yes currently its using simple code standalone and will be changes later to Tacker 14:20:59 #topic status of the Genesis installation requirements 14:23:26 #info Tacker can not be officially included in OPNFV release B 14:24:07 #info work around will be to use it post install but we will be use to test 14:26:30 #info post-install we can add up Tacker so this means we expect this only in Rele c as Dan Radez Redhat asks 14:27:51 #info Brady Johnso believes we can use as post-install for testing in Release B and later in Rel c with Berrylium we can decide what options we have 14:29:24 #info What do we get in Beryllium that we can not get in Lithium was the question from Bryan Sullivan 14:29:56 #info Bryan assumes that we focus on Lithium rther than Lithium 14:30:52 #info Lets us get whatever we can do with Lithium in B and in Rel C we cover both Tacker and Beryylium 14:31:55 #info have started with install scripts with static no pf vms for sfc so we are ok for now 14:32:40 #topic hash out the tasks for JIRA 14:33:13 #info Bryan Sullivan volunteer 14:33:28 #info lets do it in irc 14:33:37 #info How do we get started 14:34:24 #info Genisis there are number of issues created as user stries 14:34:32 #info 1st like install ODL 14:35:01 #info To do hat we need lab 14:35:08 #info Establish what features we include 14:35:29 #info basically Goals and Tasks to cover that 14:35:57 #info OVS version of x.y for ODL p.q etc 14:36:28 #info We need to get community lab access ofr sfc project 14:36:40 in LFL tehre is an arno is up 14:37:00 for our proposal 14:37:28 #info for short term just use laptop or some cloud server (sandbox) to get sfc moving and later we can get to CI pipeline like 3-nodes install in community lab etc 14:37:39 #info Can we start like using devstack to install thi? 14:37:41 Task 1 : create a procedure to create a developer env running 14:38:01 Task 1 : create a procedure to get a developer env running 14:38:16 1 thinl your python loader is a good starting point 14:38:43 Task 2 : OPNFV SFC installation scripts (to be broken down into sub install tasks) 14:39:06 #info As an OPNFV developer we need a build and test env for SFC 14:39:10 Change Task to Story 14:39:26 epic, user-story, task :) 14:40:17 #task we need to document for the tool chain is working for the project sfc 14:40:22 Story 3 : Documentation tool-chain in place 14:40:38 and is being generated 14:41:19 #info what is the required delivery for this Rel B. for SC 14:42:21 Story 4 : Access to Ericsson OPNFV blade(s) for SFC 14:42:24 #info Ericsson lab is available as pointed but will need to document and state how will this be made available 14:44:51 #info sfc gerrit env currently has info and we need to add all these including documents like to be added 14:45:06 #info Use cases which we will deliver through the stories 14:45:21 Story 5 : First minimal use case, slide 6 here: https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit#slide=id.gdd18a1c0d_38_0 14:46:07 what about the tests you need to execute? 14:46:23 #info managing use cases and requirements seperately 14:46:32 Story 6 : Testing (functest, yardstick, etc) 14:47:39 #info adding jenkins job builder (JJB) integration comes for upstream like Robot , Rally etc as well installers 14:47:48 #info CI testing usually comes from upstream 14:48:48 #info reference tests which need to be used that installers can use it 14:49:01 #info style checker for python code is required 14:49:21 #info It would be nice to have some style-checking tests in place for the limited OPNFV SFC code base 14:51:13 #info details of how we are going to do pre-fetch for nsh code for ovs until cisco & intel get it there 14:52:49 #info we need to pre-fetch nsh debian packages for install on local sandbox for use in sfc 14:53:09 #info currently they are unstable but when ready can use this and can be taken offline 14:54:23 #action to capture this stories into Jira (Brian Johnson) and show it in Jira, will send email and can start email dicussion to cl;ose beofre mile stone C deadline 14:54:36 #action ebrjohn to capture the stories and enter them in JIRA for the next week's meeting 14:54:52 #action bryan_att to help out with the documentation setup 14:55:23 #info we can get Jira items assigned to folks participating - Bryan Sullvan volunteers for documentation in Jira 14:55:34 #endmeeting