[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 2/23/2017

2017-02-22 Thread Reddy, Raghuveer
Meeting logistics - https://wiki.opnfv.org/nfv-kvm Weekly on Thursday at 2330 UTC (4:30PM PDT) Goto Meeting Link Agenda: 1) Project Status/Milestone check 2) Sc

[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 2/22/2017

2017-02-22 Thread Reddy, Raghuveer
Meeting logistics - https://wiki.opnfv.org/nfv-kvm Weekly on Thursday at 2330 UTC (4:30PM PDT) Goto Meeting Link Agenda: 1) Project Status/Milestone check 2) Scen

Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

2017-02-22 Thread HU, BIN
Lightweight OpenStack is very important. However, our current use case of L3VPN doesn't intend to address edge cloud scenario. Perhaps in the future. Thanks Bin From: joehuang [mailto:joehu...@huawei.com] Sent: Wednesday, February 22, 2017 6:29 PM To: Prakash Ramchandran ; Georg Kunz ; HU, BIN

[opnfv-tech-discuss] Canceled: [Compass4nfv] Weekly meeting

2017-02-22 Thread gang chi
Hi team, Due to temporary meeting conflict, I can't attend this weekly meeting. Sorry. Regards Justin ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] MS6 compliance assessment

2017-02-22 Thread Yujun Zhang (ZTE)
See below for QTIP project On Thu, Feb 23, 2017 at 4:31 AM David McBride wrote: > Team, > > I'd like to request that the PTLs for projects participating in Danube > respond to the following questions, designed to assess compliance with MS6. > Test Framework Projects > >1. Please provide a li

[opnfv-tech-discuss] [functest]multisite test executed, but test cases not being execeuted

2017-02-22 Thread joehuang
After kingbird installation in Functest was restored, the multisite test was executed, but test cases not being execeuted https://build.opnfv.org/ci/view/multisite/job/functest-fuel-virtual-suite-master/259/console 2017-02-23 03:07:39,016 - Tempest - INFO - Tempest multisite success_rate is

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 2/24

2017-02-22 Thread Tianhongbo
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT E

[opnfv-tech-discuss] [Bottlenecks] Minutes of Bottlenecks Discussion on February 23, 2017

2017-02-22 Thread Yuyang (Gabriel)
Minutes of Bottlenecks Discussion on February 23, 2017 * Date and Time * Thursday at 0100-0200 UTC, February 23, 2017 * Thursday at 0900-1000 Beijing, February 23, 2017 * Wednesday at 1800-1900 PDT

Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

2017-02-22 Thread joehuang
Hello, When we talk about edge cloud, if it's vCPE scenario, then the resource is very limited. I am not sure Gluon L3VPN will try to address this scenario or not. If Gluon L3VPN plans to do so, then where the OpenStack/SDN Controller will be deployed? In limited resource edge site? If OpenStac

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] MS6 compliance assessment

2017-02-22 Thread joehuang
Hello, David, The status of multisite is as follows: Enabling testing for your project in the Functest repo (or other test framework repo if you are not using functest) 1) multisite deployments refactoring was finished: https://build.opnfv.org/ci/view/multisite/builds 2) kingbird test restorati

Re: [opnfv-tech-discuss] [release][danube] MS6 compliance assessment

2017-02-22 Thread Georg Kunz
Hi David, Here are the requested infos for NetReady: · NetReady test case enabled in FuncTest: https://gerrit.opnfv.org/gerrit/#/c/28615/ · Test case implementation in NetReady: https://gerrit.opnfv.org/gerrit/#/c/28917/ https://gerrit.opnfv.org/gerrit/#/c/28999/ ·

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Update - Migration to readthedocs

2017-02-22 Thread Georg Kunz
Hi Aric, Thanks for the explanation. Just one comment: In general, I would say that if a project intends to contribute any kind of documentation to Danube despite not officially participating in the release, this project shall nevertheless create a stable/danube branch. That's how we did it fo

[opnfv-tech-discuss] [release][danube] MS6 compliance assessment

2017-02-22 Thread David McBride
Team, I'd like to request that the PTLs for projects participating in Danube respond to the following questions, designed to assess compliance with MS6. Feature Projects 1. Please provide a list of commits for the following: 1. Enabling testing for your project in the Functest repo (or o

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Update - Migration to readthedocs

2017-02-22 Thread Aric Gardner
Hi Georg, The job will always recursively clone the submodules under opnfvfocs, so each submodule will be on the tip of (branch) and if relevant the current $GERRIT_PATCHSET. But that does have me wondering what kind of breakage we will face if $project is not cutting (eg not participating) in Da

Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

2017-02-22 Thread Prakash Ramchandran
George, Following your drive to add vSwitch HA and other use cases encouraged to find if Gluon L3VPN use case is addressed before I can look at Edge Cloud. If I missed any review on L3VPN point to me and will follow up. If not yet, this time we can move NETREADY-7

[opnfv-tech-discuss] [Infra] Infra WG Meeting Minutes - Feb. 222nd

2017-02-22 Thread Jack Morgan
February 22nd Agenda: Review topics from last week Test and Performance WG discussion on Bitergia How can we collaborate with Infra WG - looking for way to map scenario testing to hardware resources Action Item Rev

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Update - Migration to readthedocs

2017-02-22 Thread Georg Kunz
Hi Sofia, One question regarding the submodules: how do you manage the versioning of the submodules? Do we need to manually bump the version of the respective project submodule after submitting new documentation to our project repo or will your Jenkins job automatically bump the version? Thank

[opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

2017-02-22 Thread Georg Kunz
Hi all, As promised in the last NetReady meeting, I would like to start a discussion about potential topics for the upcoming plugfest and hackfest and bounce them with the team. The plugfest / hackfest will take place in Paris (France) April 24 - 28. Potential hackfest agenda items for the Net

[opnfv-tech-discuss] [ha][netready]: Networking HA requirements

2017-02-22 Thread Csatari, Gergely (Nokia - HU/Budapest)
Hi, I'm working on the netready requirements related to the HA of VIM networking. I've created a patch to collect the requirements to the netready requirements document: https://gerrit.opnfv.org/gerrit/#/c/28283/ I have trouble to identify the gaps to the current OpenStack solution. Is it really

[opnfv-tech-discuss] [mano-wg] Meeting#19 Summary of E-Release Priority & Architecture Discussions (Cont.)

2017-02-22 Thread Prakash Ramchandran
Hi all, Here is quick summary from IRC will update Wiki after we have E-Release discussions through emails by end of week. Thanks Prakash Meeting summary 1. * rprakash (rprakash, 15:

Re: [opnfv-tech-discuss] [release] E-release schedule

2017-02-22 Thread Ash Young
+1 to micro releases. David, this is what we discussed in Tahoe, over lunch. I still contend that it's a lot easier to do smaller, more incremental releases to introduce features. When we last discussed this, during the Brahmaputra timeframe, the concern raised was the work for the installer teams

Re: [opnfv-tech-discuss] [release] E-release schedule

2017-02-22 Thread Frank Brockners (fbrockne)
That makes sense. The whole point of micro-releases would be to release scenarios once they are ready - and it falls into the responsibility of a scenario owner to shepherd the process. Micro-releases should *not* be a vehicle to push other teams to go out of their way. Frank -Original Me

Re: [opnfv-tech-discuss] [release] E-release schedule

2017-02-22 Thread Tim Rozet
I think having maintenance releases makes sense. From an installer perspective, if folks want to add a new scenario for a maintenance release then they need to carry most of the weight of integrating it. It is hard for a small team like Apex to juggle adding features for a previous release whi

Re: [opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

2017-02-22 Thread Sofia Wallin
Hi Gerald, I think that the best approach is that the docs project creates the first version of this. BR, Sofia From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com] Sent: den 22 februari 2017 14:57 To: Sofia Wallin ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv-projec

[opnfv-tech-discuss] [netready] Agenda for today's meeting

2017-02-22 Thread Georg Kunz
Hi all, This is the agenda for today's meeting: * Gluon integration * OPNFV documentation * Update on requirements document * AOB Best regards Georg ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

2017-02-22 Thread Kunzmann, Gerald
Hi Sofia, all, The current content of the userguide.introduction.rst doesn't at all look like the example in http://docs.opnfv.org/en/latest/how-to-use-docs/include-documentation.html#include-documentation vim opnfvdocs/docs/release/userguide.introduction.rst This opens the text editor. Identif

[opnfv-tech-discuss] [SFC] Weekly meeting cancelled, February 22, 2017

2017-02-22 Thread Brady Allen Johnson
The subject says it all :) Brady ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [release] E-release schedule

2017-02-22 Thread Ulrich Kleber
Hi, what Randy explains would mean that we should move to a very strict concept of maintenance releases. That would mean we carry through our milestones properly to get the 1.0 release out. After that we should only do bug fixing. Not a single feature. If we do that, 2.0 and 3.0 will not take big

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 2/24

2017-02-22 Thread Tianhongbo
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT E

[opnfv-tech-discuss] 答复: [dovetail]dovetail weekly meeting 2/24

2017-02-22 Thread Tianhongbo
Hi Chris: Ok, I will put these as the first point on the agenda. Yes, that is true that before the dovetail wok, we need to get the clear strategy from the CVP. Last week, wenjing shared the feedback from board. We can discuss and get the consensus on that. It will make the dovetail go to right

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

2017-02-22 Thread Sofia Wallin
Hello, As many of you already know, as part of the Danube release we are migrating all our documentation to readthedocs, an online documentation service. There are a few changes with respect to documentation that everyone should be aware of: Distinct release, development and testing documentati

[opnfv-tech-discuss] [Bottlenecks] Bottlenecks weekly meeting 2-23 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

2017-02-22 Thread Yuyang (Gabriel)
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT E

Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting 2/24

2017-02-22 Thread Christopher Price
Hi Hongbo, I would like to ensure we are discussing the CVP test strategy document as a priority point on the agenda. My recollection of the discussion from last week was that our Jira planning, utilization and structure would be best done in conjunction with the document of how we will test a

[opnfv-tech-discuss] [multisite]weekly meeting of Feb.23

2017-02-22 Thread joehuang
Hello, team, Agenda of Feb.23 2017 * Multisite deployment/functest environment readiness/restoration. * D-release preparation. * Kingbird feature development. * Open discussion IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During winter time, means CET 9:00 AM). Other