14:09:37 #startmeeting 05May2017 14:09:37 Meeting started Fri May 5 14:09:37 2017 UTC. The chair is bobmon01. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:09:37 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:09:37 The meeting name has been set to '05may2017' 14:09:58 Hi folks...can we proceed on IRC only today? 14:10:13 Problems with GTM login 14:10:22 sure 14:11:00 #info Alexandru Avadanii (Enea) 14:11:21 #info Bob Monkman 14:12:08 Sorry for the problems today. IT once again has done me in. 14:12:30 #info So, we will proceed with an update on IRC 14:13:10 #info ALex and team had to cut a Danube 2.0 release yesterday. We did not realize it was mandatory to participate in interim release 14:13:51 #info Alex or Crsitina can you please give an update on plan for Danube 3.0 14:14:24 #info two main tracks for next few weeks- Danube 3.0 which is primiarily focused on JIRA issue cleanup 14:15:00 #info 2nd is that we shall seek some performance assessments using std OPNFV perf test, to see where we are at 14:16:31 about D3 plans ... mostly stabilization and minor improvements 14:17:13 we have to bump some packages (qemu 2.9.0 is now out for example), we still have 1-2 refcore tests that prevent our functest from reporting 100% success, although we are now at 99.9% overall 14:17:34 and depending on other projects, like sdnvpn, we might try to enable the bgpvpn scenario back 14:18:01 we should start planning for the E release rebase, which will have to be coordinated with Fuel@OPNFV 14:18:23 Alexandru Nemes proposed armband: Fuel-OSTF: Arch dependent Cirros ssh password https://gerrit.opnfv.org/gerrit/34363 14:18:30 it is highly probable the Fuel@OPNFV E release will be based on the new Mirantis Cloud Platform, which will have some impact on Armband too 14:18:35 #info what sort of coordination or hurdles do you expect with Fuel team 14:18:58 #info Ok, that sounds like a major work effort 14:19:37 #info I am very concerned that this could consume an inordinate amout of resources and time, leaving little time for anything else 14:20:39 it's not a light task for sure, but it's not going to hog all our bandwidth either - it's still Ubuntu 16.04 we are going to deploy 14:20:52 but look on the bright side - MCP has kubernetes integration 14:21:02 so this effort will come with a high reward 14:21:42 #info So you are saying that this kubernets integration could enable better support for containerized VNFs? 14:22:31 #info I want to work closely with Dan Radez and team on Apex Installer support as one of the highest priortiies 14:23:07 we have no container integration right now, so yes, that would be better than none :) 14:23:10 #info we want and need CentOS support and another installer 14:24:15 #info Dan R reports that he is in the final stages of getting Apex installer support for ARM back to where we was with OpenStack Newton, upgraded to Ocata in prep for E-release 14:25:10 #info I would like to see tech leads from Armband reach out to Dan and determine is help can be provided to ensure that we get APex support for Euphrates 14:26:15 Noted 14:26:19 #info Can we please mark this as a top priority for E-release? We need diversification here on Installers and of course base OS support wrt CENTOS 14:26:55 #info thanks Thomas 14:26:58 Ok 14:27:28 ... and ACK on the installer diversity priority. 14:27:49 #info ... and ACK on the installer diversity priority. 14:28:03 #info Besides Upgrading Fuel and adding Apex, the only major features I proposed for E-release platform were integrating better DPDK and ODP support for VNFs 14:28:48 #info From our last online Armband meeting, did I miss any other features in the Plan that we had discussed? 14:31:10 #info Due to last day of NFV World Congress being today, I need to get down to the event soon and so would prefer to keep this meeting short today 14:31:25 #info any other topics people wish to cover? 14:31:51 Not from me 14:32:15 Alexandru Nemes proposed armband: Fuel-OSTF: Arch dependent Cirros ssh password https://gerrit.opnfv.org/gerrit/34363 14:33:03 #info Ok...then I will close the meeting. We can iterate on tech-discuss in any urgent issues comes up between now and next meeting 2 weeks from today 14:33:16 #info I will have GTM sorted 14:33:26 #info endmeetings 14:33:38 #info endmeeting 14:33:54 #endmeeting