[opnfv-tech-discuss] [Bottlenecks] Minutes for Weekly Call 20170927

2017-09-26 Thread Liyin (Ace)
Minutes of Bottlenecks Discussion on Sept. 27th, 2017 * Date and Time * Thursday at 0300-0400 UTC, Sept. 27th, 2017 * Thursday at 1100-1200 Beijing, Sept. 27th, 2017 * Wednesday at 0800-0900 PDT, Sept.

[opnfv-tech-discuss] [mano-wg] Meeting #47 Focus VNF usecase Orchestration and Testing in OPNFV / ONAP for Release F

2017-09-26 Thread Prakash Ramchandran
Hi all Please join us for mano-wg meeting this Wednesday. Thanks Prakash Sept 27, Wednesday : 14.00 UTC /7.00 PDT Meeting #47 Meeting Times: Wednesday (7.00 am PDT) at 14.00 UTC Agenda link : https://wiki.opnfv.org/pages/editpage.action?pageId=6827111 For IRC can use can use

[opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 27 Sep 2017

2017-09-26 Thread Cooper, Trevor
Proposed agenda topics ... - Euphrates upcoming milestones ... * October 3 - MS8 - Formal test execution completed * October 4 - MS9 - Documentation updated * October 5 - MS10 - JIRA cleanup * October 6 - MS11 - Tag repos / technical release of 5.0 *

Re: [opnfv-tech-discuss] Calipso request to release as an independent tool for Euphrates

2017-09-26 Thread David McBride
Koren, Can you describe how you will use OPNFV CI builds and testing? One potential issue I see is that we could have competition for resources with projects that are participating in a release. David On Tue, Sep 26, 2017 at 7:40 AM, Koren Lev (korlev) wrote: > Hi, > > > >

[opnfv-tech-discuss] [VSPERF][NFVBENCH] streamlining the jump host to data plane wiring

2017-09-26 Thread Alec Hothan (ahothan)
Hi Trevor and team, I’d like to get some feedback regarding the way jump hosts are wired to the data plane as that will have a direct impact on how software based traffic gen like TRex is configured on the jump host. My impression is that the wiring of traffic gen devices to the data plane has

Re: [opnfv-tech-discuss] [Auto] More RAM for Auto

2017-09-26 Thread Tina Tsou
Dear Parker et al, That was a typo, I meant 60G, not 16G. Test environment Lab POD OS CPU Memory Storage UNH laas Lab10.10.30.248CentOS 7.3.1611 Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz 60G 430G Thank you, Tina On Sep 26, 2017, at 9:53 AM, Parker Berberian

Re: [opnfv-tech-discuss] [Auto] More RAM for Auto

2017-09-26 Thread Tina Tsou
Dear Lincoln et al, Good to know. Please refer to the following, and also join Auto weekly call next Monday at 6am PT. Scenarios: https://wiki.opnfv.org/display/AUTO/Auto+Use+Cases https://wiki.opnfv.org/display/AUTO/Auto+Test+Cases Lab requirements:

Re: [opnfv-tech-discuss] [Auto] More RAM for Auto

2017-09-26 Thread Parker Berberian
Hi Tina, I'm sorry for the trouble. You said that you are using one of our x86 virtual pods? All of our pods have 64GB of RAM available. Can you please remind me what pod you are using? Thank you, Parker Berberian On Tue, Sep 26, 2017 at 11:48 AM, Lincoln Lavoie wrote:

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

2017-09-26 Thread HU, BIN
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

Re: [opnfv-tech-discuss] Discussion Topics for Weekly Technical Discussion this Thursday 09/28

2017-09-26 Thread HU, BIN
Thank you Jack and Bryan, I will put an agenda item to discuss: - Hardware Requirements in OPNFV and Sustainable Way to Evolve - Improvements on Pharos Specification Lab owners and Pharos owner(s), Would you participate in the discussion on Thursday? Thank you Bin From:

Re: [opnfv-tech-discuss] [Auto] More RAM for Auto

2017-09-26 Thread Lincoln Lavoie
Hi Tina, I'll check with Parker what we can do. For the virtual pods, we're limited on the total RAM in the host system. We might be able to allocate a complete HW blade to a pod for you, and increase the RAM, at the cost of one less pod available for anyone else to use. The servers for the ARM

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

2017-09-26 Thread Alexandru Avadanii
Hi, Julien, I agree on all the items below. Thank you for the feedback! BR, ALex From: Julien [mailto:julien...@gmail.com] Sent: Tuesday, September 26, 2017 5:52 PM To: david.blaisonn...@orange.com; Alexandru Avadanii; opnfv-tech-discuss@lists.opnfv.org Cc: Guillermo Herrero Subject: Re:

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

2017-09-26 Thread Julien
Hi Alex, Thanks for the conclusions of current working items in PDF. Some response from my side: 1. 'vlan: 0' vs 'vlan: native': 'vlan: native' is easier for understanding. it is not fixed and a specific vlan id will be required, while vlan 0 has some special meaning. 2. 'disk_rotation: ssd'

[opnfv-tech-discuss] Calipso request to release as an independent tool for Euphrates

2017-09-26 Thread Koren Lev (korlev)
Hi, As suggested in the TSC meeting I am sending a request to TSC using this email thread. Calipso code contributions are here : https://koren...@gerrit.opnfv.org/gerrit/a/calipso Master repo is here: https://git.opnfv.org/calipso/tree/ Documentation here:

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

2017-09-26 Thread Alexandru Avadanii
Hi, See inline. BR, Alex From: david.blaisonn...@orange.com [mailto:david.blaisonn...@orange.com] Sent: Tuesday, September 26, 2017 11:54 AM To: Alexandru Avadanii; opnfv-tech-discuss@lists.opnfv.org Cc: jack.mor...@intel.com; Guillermo Herrero Subject: Re: PDF feedback and questions from our

Re: [opnfv-tech-discuss] Discussion Topics for Weekly Technical Discussion this Thursday 09/28

2017-09-26 Thread SULLIVAN, BRYAN L (BRYAN L)
The one-size nature of the Pharos specs has always been one of the key weaknesses of the OPNFV program IMO. It does not reflect the likely diversity of hardware infra that will be used in different deployment environments, e.g. datacenter, edge, customer premises (enterprise, consumer),

Re: [opnfv-tech-discuss] [release][euphrates] Chinese National Day holiday in October

2017-09-26 Thread David McBride
I've only heard from one project in the Euphrates release, so far. Please respond if you believe that the release of your project next week will be affected by the holiday. Thanks. David On Fri, Sep 22, 2017 at 7:02 PM, David McBride wrote: > Team, > > As you

Re: [opnfv-tech-discuss] [announce] 2018 OPNFV release names

2017-09-26 Thread Dave Neary
Hi, On 09/25/2017 05:24 PM, Raymond Paik wrote: > Thanks for voting on the release naming poll. > > First, for G-release the winner is Gambia (the first African river for > OPNFV). > > For the F-release, the top vote getter was Fenix in Argentina. However, > after some research it looks

[opnfv-tech-discuss] Calipso project documentation

2017-09-26 Thread Koren Lev
Hi everyone, I Would like please to point people to recent documentation for the 'Calipso' project. it's an initial push, to be kept updated once in a while, but it's a good start for people who'd want to try it out right now: https://git.opnfv.org/calipso/tree/docs/release Note: clone is needed

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

2017-09-26 Thread MORTON, ALFRED C (AL)
+1 and thanks for the proposal, Alex! Al From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Frank Brockners (fbrockne) Sent: Tuesday, September 26, 2017 4:44 AM To: Alec Hothan (ahothan); opnfv-tech-discuss@lists.opnfv.org Subject:

Re: [opnfv-tech-discuss] PDF feedback and questions from our experience with Fuel

2017-09-26 Thread david.blaisonneau
Hi, I hope I don't offend you about net_config, it is an hard subject, not easy to summarize, and born during summer holidays without everyone around the gerrit pit. About network naming, I understand the need of anonymize the networks parts to not over specify the installer level, but by

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

2017-09-26 Thread Frank Brockners (fbrockne)
+1 – per what Alec mentioned below, the new tagging scheme is only a small change incremental change from the earlier plans, but offers a lot of flexibility moving forward. Frank From: Alec Hothan (ahothan) Sent: Montag, 25. September 2017 21:34 To: opnfv-tech-discuss@lists.opnfv.org Cc: David

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

2017-09-26 Thread Tianhongbo
+1 From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz Sent: 2017年9月26日 15:37 To: Alec Hothan (ahothan) ; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] urgent euphrates git tags

Re: [opnfv-tech-discuss] urgent euphrates git tags vote needed

2017-09-26 Thread Georg Kunz
+1 From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan (ahothan) Sent: Monday, September 25, 2017 9:34 PM To: opnfv-tech-discuss@lists.opnfv.org Subject: [opnfv-tech-discuss] urgent euphrates git tags vote needed I