[opnfv-tech-discuss] [opnfvdocs] [release] MS6 Preliminary documentation completed

Hi, Please be aware of MS6 ‘Preliminary documentation completed’ that is upcoming March 16. Projects are expected to have their document structure in place. This also includes placehold

Re: [opnfv-tech-discuss] [yardstick] : failed to "yardstick task start samples/ping.yaml"

Hi Jaewook, Thanks for your feedback. This is not a known problem for now. So you are using yardstick on Openstack Queen installed by devstack. As I can see from your log, the error occurred when yardstick call Heat to create a stack. I want to check: 1) Can you create a server using Opens

Re: [opnfv-tech-discuss] [release] [k8s] test support for Kubernetesscenarios

Hi，Ross， I am more concerned with yardstick HA test cases on Kubernetes scenarios，especially those testcases that though kill openstack service to implement HA test，such as yardstick TC019(Nova)，TC045(Neutron), TC046(Keystone), TC047(glance), TC048(Cinder), TC049(Swift). As far as I know in Kub

[opnfv-tech-discuss] Canceled: [armband] Weekly Meetings Established for ARMBand project

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] high availability project meeting

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 16.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;

[opnfv-tech-discuss] 转发: [release][fraser] MS6 - test case implementation / prelim documentation - March 16

Hi, all. MS6 is on March. 16, which requires the implementation of TCs. I suggest we have another IRC meeting next Wednesday on Feb. 28 to check the status of the current TCs and make sure they can be submitted in time. Next Meeting on 13:00-14:00 UTC, Wednesday, Feb. 28 IRC Channel: #opnfv

[opnfv-tech-discuss] [release][fraser] MS6 - test case implementation / prelim documentation - March 16

Team, MS6 is scheduled in three weeks, on March 16. MS6 has two requirements: 1. Implementation of test cases documented in MS2. 2. Completion of preliminary documentation. As a minimum, this means putting the directory structure and placeholder documents in place, in accordance wit

Re: [opnfv-tech-discuss] [dovetail] Resigning as a committer

Hi Dave, First of all, thank you very much for your contributions to the project and the first release of OVP. According to [1], it suffices to send an email to the project (done). I will forward your email to the TSC mailing list and update the INFO.yml file correspondingly. [1] https://wik

[opnfv-tech-discuss] [dovetail] Resigning as a committer

Hi all, I have said for several months that it was my intention to resign as a committer of Dovetail after the initial launch of the CVP. Vendor diversity of the committers is something that's important to me, and since Zenghui Shi has joined the Dovetail committer team, I want to ensure I am prac

Re: [opnfv-tech-discuss] [release][fraser] MS5 - scenario integration - March 02

MS 5 - scenario integration - is scheduled one week from Friday on March 2. if you are receiving this email, then that means that you are identified as the scenario owner for one or more scenarios on the Fraser scenario status page . Pl

Re: [opnfv-tech-discuss] [onap-discuss] [OPNFV Auto] installation of ONAP on the Auto Arm pod

Dear Gerard, If I remember correctly, Bryan Sullivan built docker image for Pramod‘ code before. Thank you, Tina On Feb 22, 2018, at 5:29 AM, Roger Maitland mailto:roger.maitl...@amdocs.com>> wrote: The ONAP OOM team is working with the DCAE team on a fully containerized version of DCAE. C

[opnfv-tech-discuss] Weekly Technical Discussion #112

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02000

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday February 22, 2018

t Visibility Lightning Talk o Please sign up if your project is interested in giving a lightning talk. Thanks Bin [1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20180222 [2] http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-02-22-14.00.html ___

[opnfv-tech-discuss] [yardstick] : failed to "yardstick task start samples/ping.yaml"

Hi, this is Jaewook from Soongsil University in Korea. I'm now facing issue in running yardstick test case. When I run a sample test, 'yardstick task start samples/ping.yaml', following error is occurring continuously. BadRequest: Expecting to find domain in project. The server could not comply

Re: [opnfv-tech-discuss] [nfvbench] testpmd

I think there is a bug in that new piece of code, let me check with the person who wrote it. In the meantime if you want a workaround, you could go ahead and remove that whole if block (in container, edit /nfvbench/nfvbench/nfvbench.py L169) - it can be safely removed. Thanks Alec From: "Ba

[opnfv-tech-discuss] SFC weekly MoMs

Hi, Here are the MoMs from this week: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc. 2018-02-21-15.03.html Regards, Manuel___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/li

[opnfv-tech-discuss] Abgesagt: OPNFV Promise meeting

smime.p7m Description: S/MIME encrypted message ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss