13:58:27 <dfarrell07> #startmeeting testperf
13:58:27 <collabot`> Meeting started Thu Sep  8 13:58:27 2016 UTC.  The chair is dfarrell07. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:58:27 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:58:27 <collabot`> The meeting name has been set to 'testperf'
13:58:55 <dfarrell07> #info CPerf (dfarrell07) is chair, VSPerf (acm) is taking minutes (for first 30 mins or so)
13:59:04 <dfarrell07> #link https://wiki.opnfv.org/display/meetings/TestPerf Agenda in the normal place
14:00:13 <acm> #info Al Morton
14:00:25 <dfarrell07> #info Feel free to #info in while we wait on someone to start the gotomeeting
14:00:33 <morgan_orange> #info Morgan Richomme
14:00:41 <morgan_orange> I will open the GTM
14:02:25 <dfarrell07> #topic Action follow-up
14:02:33 <dfarrell07> #info (last week #action) morgan_orange initiate a wiki page on POD allocation for test projects (short/mid/long term) after the C release
14:02:39 <dfarrell07> #info (last week #action) kubi001 morgan_orange plan an update on grafana/ELK in September
14:02:40 <yuyang> #info yuyang
14:02:45 <dfarrell07> #info (last week #action) mbeierl to summarize stable branch guidelines for testperf members
14:02:50 <dfarrell07> #info (last week #action) yuyang morgan_orange kubi001 create patch and put test people in review
14:02:55 <dfarrell07> #info (last week #action) jose_lausuch bryan_att sync how to push results in artifact from copper
14:02:57 <kubi001> #info kubi
14:03:22 <acm> #info no progress on POD allocation
14:03:26 <dfarrell07> #action (carry-over, after release)kubi001 morgan_orange plan an update on grafana/ELK in September
14:04:10 <dfarrell07> #info POD #action will happen after release
14:04:17 <acm> #info Finish the release first (on POD alloca)
14:04:21 <jose_lausuch> :)
14:04:25 <dfarrell07> #info (done) jose_lausuch bryan_att sync how to push results in artifact from copper
14:04:47 <dfarrell07> #info docs review inter-project has started
14:05:12 <dfarrell07> #topic Colorado status
14:05:16 <acm> #info Colorado Status
14:06:13 <dfarrell07> #info functest reports that things are fairly green for C status, were not in such good shape with A and B, so progress, some bugs to be fixed but that's expect
14:06:30 <dfarrell07> #info All installers and scenarios seem to be making progress
14:07:11 <acm> #info same pod for release and feature test - issues
14:07:18 <dfarrell07> #info Feature projects need time for integration, are causing some false-negatives errors that installers are seeing because feature projects are using same pods
14:07:39 <acm> #info red status in Jenkins is not end-of -world...
14:07:52 <dfarrell07> #info Better to get feedback about what's working and not, vs green on smaller set of things
14:08:44 <jose_lausuch> related to this: https://wiki.opnfv.org/display/INF/CI+Evolution
14:09:11 <dfarrell07> #info kubi001 from yardstick gives updates
14:09:16 <kubi001> https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status
14:09:24 <acm> #info Yardstick - new wiki to track stable branch (above)
14:09:32 <dfarrell07> #link https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status Yardstick status
14:10:30 <acm> #info 4 successful builds in a row, need to track daily builds and fix bugs
14:10:47 <dfarrell07> #info Yardstick is working on moving to automatic reporting, vs updating this wiki, as functest demo'd recently
14:11:11 <dfarrell07> #action morgan_orange to help yardstick with getting automatic test results
14:11:59 <dfarrell07> #info Maryam reports that VSPerf is quite green
14:12:25 <dfarrell07> #info yuyang reports bottlekneck green
14:12:32 <acm> #info mthahan some reds with intel pod going down over weekend
14:12:46 <acm> #info bottlenecks green
14:13:48 <morgan_orange> kubi001: colorado/yardstick online http://testresults.opnfv.org/reporting/yardstick/release/stable/colorado/index-status-apex.html
14:13:54 <acm> #topic OPEN Air Interface -- Rohit
14:14:26 <dfarrell07> #info OAI had a demo at Summit
14:14:46 <dfarrell07> #info They have an open source VNF we are interested in integrating into functional testing
14:15:49 <acm> #info presented in berlin summit - not clear if integration possible, some licenses proprietary in open source VNF
14:16:16 <acm> #info (the usuall sharing issues)
14:16:40 <dfarrell07> #info There's a set of slides that we'll try to get a link to later
14:17:12 <morgan_orange> kubi001: issue with fig due to the path on the template you precise ../../images but the results are in  release/master and release/stable/colorado
14:17:42 <acm> #info many use cases, including MEC
14:17:53 <acm> #info will send slides...
14:18:43 <dfarrell07> #info Already have various PoCs going on
14:18:46 <acm> slides not moving form me ???
14:18:47 <dfarrell07> #info Working with many partners
14:19:16 <acm> #info me too
14:19:40 <acm> wfm same
14:20:37 <dfarrell07> #info eurocom is a major group, many members, Orange included (which is how we got linked I guess)
14:20:47 <acm> #info EURECOM - research and teaching, many affiliations.
14:21:13 <acm> #info yes
14:21:45 <kubi001> morgan_orange: got it, thanks
14:22:04 <acm> #info soft impl of eNodeB , other elements
14:22:52 <dfarrell07> #info Looking to work with more open source communities, like OPNFV
14:22:53 <acm> #info running on intel
14:23:24 <acm> #info IPR rich area - free for non-comercial use
14:23:52 <dfarrell07> #info RAN has license complexities, but is under Apache license with non-commercial clause
14:24:44 <acm> #info this should be disruptive for 5G
14:25:31 <acm> #info RF part - they have their own board, others are available.
14:25:34 <dfarrell07> #info Working with many different hardware projects/vendors
14:26:13 <acm> #info I have to go...
14:26:43 <dfarrell07> acm: okay, thanks for help :)
14:27:12 <dfarrell07> #info We're not lawyers, but there are efforts to make working with open source possible
14:28:21 <dfarrell07> #info OSA has big scope, but also quite focused on SDN 5G
14:28:48 <dfarrell07> #info Working with OpenStack
14:29:44 <dfarrell07> #info Interactions with ETSI, PoCs
14:31:52 <dfarrell07> #info Looking for thoughts about best way to use OAI as an upstream to test/integrate in OPNFV
14:33:02 <dfarrell07> #info Seem to be mostly looking at Fuel/JOID installers at the moment
14:33:38 <dfarrell07> #info morgan_orange +1s targeting D release to integrate a VNF into OPNFV
14:34:47 <dfarrell07> #info Basic steps 1) Deploy orchestrator 2) deploy VNF 3) develop tests to validate VNF 4) Get that running in CI so functest can validate
14:35:41 <dfarrell07> #info OPNFV is MANO, controller, installer agnostic, so should be able to get VNF deploying in various scenarios
14:36:31 <dfarrell07> #info Hardware and license are kinda hard with 5G space in general, morgan_orange says, but pushing to make it happen
14:37:46 <dfarrell07> #info First goal should be getting simple VNF like for vEPC (DB with algos to manage connectivity) running in community labs, which we can give you access to
14:38:19 <dfarrell07> #info Juju people have prio to show as VNFM for D
14:38:49 <dfarrell07> #info morgan_orange scopes this as possible for D
14:40:24 <dfarrell07> #info Discussion about how hardware isn't too bad to get, can be simulated
14:41:10 <dfarrell07> #info OSA folks need feedback about functest architecture, they will join weekly functest meeting for info, morgan_orange will also send pointers
14:41:21 <jose_lausuch> http://artifacts.opnfv.org/functest/docs/configguide/
14:41:32 <jose_lausuch> http://artifacts.opnfv.org/functest/docs/userguide/
14:42:02 <dfarrell07> #info OSA people will try to continue joining calls
14:42:27 <dfarrell07> #link http://artifacts.opnfv.org/functest/docs/userguide/ User guide for Functest
14:42:39 <dfarrell07> #link http://artifacts.opnfv.org/functest/docs/configguide/ config guide for functest
14:43:18 <dfarrell07> #info Discussion will continue in IRC-only functest meeting
14:43:59 <dfarrell07> #info Question about how to take part in community labs
14:44:11 <dfarrell07> #info "can we still work with you all" YES! :)
14:44:19 <acm> #info Al Morton back
14:44:49 <dfarrell07> #info OPNFV is an open source project, but more importantly has an open development model, you don't need to be a member to contribute
14:45:09 <acm> #info OPNFV membership not needed to work with us, have access to labs, with some variation across labs
14:45:13 <dfarrell07> #info we can give you pubkey ssh access to get into labs
14:46:24 <acm> #info create LF account for acces to other project aspects - Wikui, JIRA, etc.
14:47:05 <dfarrell07> #action morgan to send link to docs about getting started as dev, IRC access, similar
14:47:58 <dfarrell07> #link https://wiki.opnfv.org/display/DEV/Developer+Getting+Started Overall OPNFV dev guide
14:48:27 <acm> #info http://webchat.freenode.net/?channels=opnfv-testperf
14:49:45 <acm> HI trevor, welcome back!!
14:50:11 <dfarrell07> #info bryan_att asks if there's going to be hardware/software brought in that allows us to interact with OAI, to do some of this specialized stuff
14:50:29 <trevor_intel> acm: thanks :)
14:51:41 <dfarrell07> #info OAI stuff can run in software (but with a specialized kernel), will be slow-ish but testing should be okay
14:52:55 <dfarrell07> #info Sounds like there will be changes to installers required, kernel mods/versions
14:53:18 <acm> #info there are still challenges to run OPEN Air on GP intel and ARM,
14:53:52 <dfarrell07> #info bryan_att asks if intent is to eventually add hardware to Pharos, Rohit says would rather do this in generic Intel/AMD
14:54:13 <acm> #info challenges to runt the code in KVM or Docker...
14:55:03 <dfarrell07> #topic Discussions on Scenario generic/specific
14:55:39 <dfarrell07> #info morgan_orange talks about needed config per scenario
14:55:48 <acm> #info scenaio owners are the installers -
14:56:33 <dfarrell07> #info installers own laying down scenarios, but don't know this specific stuff, need to clarify how generic or specific logic is handled
14:57:01 <bryan_att> I meant the type of hardware that provides the access network interfaces for ON.Lab projects such as M-CORD (mobile) and R-CORD (optical residential). Augmenting OPNFV Pharos PODs with such hardware would enable OPNFV/CORD testing, e.g. such as would use the open air interface.
14:57:45 <acm> #info morgan_orange believes this idea of specific scenarios makes sense.
14:57:53 <bryan_att> But emulating those access network elements is also possible, though the performance will be impacted as noted.
14:58:18 <dfarrell07> bryan_att: I'm just going to #info that if okay
14:58:24 <bryan_att> sure
14:58:27 <dfarrell07> #info I meant the type of hardware that provides the access network interfaces for ON.Lab projects such as M-CORD (mobile) and R-CORD (optical residential). Augmenting OPNFV Pharos PODs with such hardware would enable OPNFV/CORD testing, e.g. such as would use the open air interface.
14:58:33 <dfarrell07> #undo
14:58:33 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2c66e90>
14:58:39 <dfarrell07> #info (bryan_att) I meant the type of hardware that provides the access network interfaces for ON.Lab projects such as M-CORD (mobile) and R-CORD (optical residential). Augmenting OPNFV Pharos PODs with such hardware would enable OPNFV/CORD testing, e.g. such as would use the open air interface.
14:58:51 <dfarrell07> #info (bryan_att) But emulating those access network elements is also possible, though the performance will be impacted as noted.
14:59:15 <acm> #info Rohit: is it too soon to present this project to the TCS (heather and Ray suggested this as follow-up)
15:00:24 <acm> #info bryan: prefer the weekly tech discussion on thursday tech meeting, takes pressure off TSC
15:01:43 <dfarrell07> #info Discussion will continue on tech calls, mailing lists, clarifying and making progress, then after release may be better to bring to TSC
15:01:49 <acm> #info morgan_orange better to delay until late Sept October, after release.
15:02:50 * dfarrell07 will give a few seconds for any other notes ppl want to add
15:03:43 <dfarrell07> #endmeeting