Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

UPDATE Oct 13, 2017 *Scenario Summary* Total (listed on scenario status page and found in Jenkins) 52 Pass Deploy 63% Fail Deploy 19% Not Running 17% Functest results 69% YardStick results 58% *UPDATE on Issues:* 1. *Chinese National Holiday. *The Huawei lab is back online and Joid,

[opnfv-tech-discuss] [IPv6] Project Meeting #70

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

[opnfv-tech-discuss] new project proposal: clover

Hi OPNFV TSC, and community To better support cloud native computing for NFV use cases, we are proposing a new project "clover" for the OPNFV community. We've put the project proposal on the wiki: https://wiki.opnfv.org/display/PROJ/Clover. We are scheduling a discussion at the OPNFV tech

Re: [opnfv-tech-discuss] Arch-specific Docker tags

I think the key point is about using multiple repositories or multiple tags to differenciate the architectures listed in manifests. Multiple repositories (eg: opnfv/functest-core_amd64 & opnfv/functest-core_arm64) are more flexible (stable could be linked to different versions according to the

Re: [opnfv-tech-discuss] Arch-specific Docker tags

Hello, Of course I will vote for 1. I consider 2 and 3 as false from a Docker point of view. Yes we already have published manifests which are suitable solutions to avoid duplicating Dockerfiles and jenkins jobs. Let me know if you want much technical details. I must precise that the choice

Re: [opnfv-tech-discuss] Arch-specific Docker tags

I would prefer limiting the number of container images because we’re going to have a lot more image versions for some projects (to tackle versioned XCI/CD) So option 2 does not look great for me. I’d vote for option 1. Have you guys looked at support for multi-arch docker images? I find it

[opnfv-tech-discuss] Arch-specific Docker tags

Hi, Cédric pointed out that Docker uses DEB/kernel format for describing the architecture of a Docker container. To align with this, the Functest Docker tags were updated from "x86_64-latest"/"aarch64-latest" to "amd64-latest"/"arm64-latest". Although the arch-naming convention is not enforced

Re: [opnfv-tech-discuss] [barometer] Vote for new barometer PTL

Congrats to Aaron, our new barometer PTL! :) BR Maryam From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam Sent: Wednesday, October 11, 2017 5:13 PM To: MORTON, ALFRED C (AL) ; Foley, Emma L

[opnfv-tech-discuss] [OPNFV] xci /functest

Hi we made some tests using Functest (opnfv/functest-healthcheck and functest-smoke - eupĥrates) on xci-baremetal in our labs. we have reproducible results and would like to discuss with xci group I did not see xci/functest recent logs on our Jenkins, do I miss something? As far as I

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

Hi Tim, My only concern is that by implementing this function inside the test case, we might run into exceptions raised if there is a problem with SSH keys or whatever other problem accessing the nodes. Collecting logs when the test fails makes sense, but it doesn’t harm if we collect it

Re: [opnfv-tech-discuss] [HA] OPNFV HA test case evolution

Awesome, thank you! Cheers, Georg From: Fu Qiao [mailto:fuq...@chinamobile.com] Sent: Friday, October 13, 2017 11:05 AM To: Georg Kunz ; 'Yamei Fan' Cc: 'Gaoliang (kubi)' ; 'Brattain, Ross B'

[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

[opnfv-tech-discuss] 答复: [HA] OPNFV HA test case evolution

Sure. I will update the agenda to include this. I will check with Yamei to see if she can still make next week’s call. If not, we will arrange another meeting the week after the next. 发件人: Georg Kunz [mailto:georg.k...@ericsson.com] 发送时间: 2017年10月13日 16:49 收件人: Fu Qiao

[opnfv-tech-discuss] [HA] OPNFV HA test case evolution

Hi, [Adding the mailing list, so that everyone interested in this topic can follow.] Well, I wouldn’t mind starting the conversation earlier, but if Yamei is out of office, we can of course move the meeting. Just a thought: maybe we can have a first call next week to get started. We could

Re: [opnfv-tech-discuss] [xci] xci - aio installation failed on a ubuntu 16.04 VM

On 12/10/17 19:33, Srikanth Vavilapalli wrote: > Hi Markos > > The following is the error I get when I start the opnfv domain. It says > "cannot allocate memory". I have 4GB RAM assigned to my vagrant VM where I am > bringing up the XCI. May I know what are minimum RAM needs fro XCI AIO flavor?

Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Hi, Jack, No problem, thank you very much for fixing it so fast! BR, Alex From: chenjiankun [mailto:chenjiank...@huawei.com] Sent: Friday, October 13, 2017 4:40 AM To: Alexandru Avadanii Cc: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV; Michail Polenchuk; David McBride Subject: RE:

[opnfv-tech-discuss] [dovetail][test-wg] Feedback from Dovetail to Test WG

Hi, Including the tech-discuss mailing list for better visibility. Cheers Georg From: Georg Kunz Sent: Thursday, October 12, 2017 1:06 PM To: Tianhongbo ; Georg Kunz ; Wenjing Chu ; Cooper, Trevor

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

Jose, I see the point of avoiding log collection in the code for test execution to avoid false negatives in case something with the log collection itself goes wrong (although I’m wondering a bit if that cannot also be handled by carefully implementing the test pass/fail criteria). There are

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

Hi, When it comes to log collection, I strongly believe it should be done post-job in our CI pipeline, not as part of the test case. Users can always collect logs manually regardless of the installer tools they use… And regarding making it automated in OPNFV after Functest/Yardstick

Re: [opnfv-tech-discuss] New PTL for VSPERF

Congratulations, Sridhar Rao! -- Yujun Zhang On Fri, Oct 13, 2017 at 12:53 AM Singh, Gurpreet wrote: > Congratulations Sridhar! > > > Original message > From: "Cooper, Trevor" > Date: 10/12/17 12:43 PM (GMT-05:00) > To:

[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

[opnfv-tech-discuss] [availability]High Availability Project meeting on Oct. 18

Hi, all. I would like to arrange a project meeting to start the discussion about HA test cases development for F release and future releases. I would like to invite my colleague Fan Yamei to introduce the current high availability test cases in our specification, which we also plan to develop