[opnfv-tech-discuss] [VSPERF] topology description scheme

Hi folks I've been thinking about this and I think I have a possible suggestion Lettering: It's case sensitive L - Local R - Remote S - vSwitch P- Physical NIC V - Virtual NIC pp - patch port O - Overlay port - not sure if we need... Numbering: Numeric values can follow any of the

Re: [opnfv-tech-discuss] Evolution of OPNFV mailing lists

Yunhong, Sorry for the delay. Please see my comments below Thanks, Ray On Tue, Aug 30, 2016 at 5:22 PM, yunhong jiang < yunhong.ji...@linux.intel.com> wrote: > On Mon, 29 Aug 2016 09:41:46 -0700 > Raymond Paik wrote: > > > All, > > > > One of the topics

Re: [opnfv-tech-discuss] Infra Working Group Weekly Meeting

Hello Jack et al I have an offsite meeting tomorrow at 1pm and have to travel there in advance so I wont be able to make the call. >From my side (INFRA): - I have 3 slides almost ready (should post by end of the week) on possible approaches to having multi-scenario (thus multi-installer)

[opnfv-tech-discuss] 2017 OPNFV Summit website, registration & sponsorship details live

Hello OPNFV Tech Community, Heads-up that we've officially launched details for the 2017 OPNFV Summit taking place June 12-15 in Beijing. A media advisory went live this morning,

Re: [opnfv-tech-discuss] [Parser]Verigraph Presentation slide

Hi Ulas, As far as I understand, verigraph currently focus on the orchestration layer of ESCAPE which is mainly a service funcation chaining engine. For verigraph's integration with Parser, we do need certain modifications so that verigraph

Re: [opnfv-tech-discuss] [opnfv-tsc] harmonized configuration set for OPNFV

I agree. We should track this issue in JIRA. Which project shall we put it in? Pharos? Besides the configuration harmonization, we have also spotted some performance deviation between environments deployed by different installers. Theoretically , a consistent environment should be targeted no

Re: [opnfv-tech-discuss] [Apex] puppet logging for debug

Hi Tim, Thanks for your answer. I also find the debug logs in /run/heat-confg/deployed on the nodes is very helpful for debugging the puppet issue. BRs, On Wed, Sep 7, 2016 at 12:54 AM, Tim Rozet wrote: > Hi Peng, > On the jump host you can do opnfv-util debug-stack. That

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

Hi Is there any final conclusion to this mail thread ? Are the documents of the requirement project going to be part of the C release? Thanks Adi From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin Sent: Wednesday,

Re: [opnfv-tech-discuss] [dovetail]issures and suggestion: to upload the dovetail codes to the git/gerrit

Hi Hongbo, Since Dovetail is not participating in the C release, we should not have a C release branch, I think - I would suggest that we work in master only. I do not understand why we would need to be on a C branch to run our test suite against a C release branch. Thanks, Dave. On 09/05/2016

Re: [opnfv-tech-discuss] harmonized configuration set for OPNFV

Yujun, Thanks for raising this issue. This is a longer term issue to solve but for now I've added it as a topic for to the Infra WG weekly meeting. I'm hoping to solve this for the D release and been tasked by the TSC to help drive this effort. Please join

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

Hi Ray, thanks for posting the initial cut. IMHO a "composite score", as proposed on the page, could be *very* misleading, especially for projects which do most of the work upstream. So unless we track all upstream repos and upstream Jiras (or similar), I would suggest to *not* compute a

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #28648] AutoReply: [qtip] Nomination of Committer promotion for jiang.zhif...@zte.com.cn

Hi, I have sent jiang.zhif...@zte.com.cn an invite to join the qtip submitters group. In the future please do all of the voting on the same channel (Ie gerrit or email) as this is easier to keep track of and refer to. Regards, Aric On Tue, Sep 6, 2016 at 9:32 AM, zhangyujun+...@gmail.com via

Re: [opnfv-tech-discuss] [VSPERF] topology description scheme

Hi Maryam, Thanks for initial proposal. It looks good overall. It seems, we are going to define a grammar of a small language. In that case it might be useful to define it well for both human and machine processing. Just for case, we would like to create a class, which will be able to prepare

[opnfv-tech-discuss] [netready] NetReady weekly project meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Europe/Berlin BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Re: [opnfv-tech-discuss] harmonized configuration set for OPNFV

I’d suggest a Jira issue be created that we can add details to. I agree that this will be a very helpful effort. Right now there is substantial variation in the deployed platform e.g. even to such things as: - Number and names of networks, routers, etc created by default -

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

Hi Adi, We had a discussion on this in the docs meeting last week and to my understanding we came to the agreement that the requirement docs should be included. The exact location and the naming still needs to be decided upon. For instance, it should be clear for users of the release that the

Re: [opnfv-tech-discuss] [VSPERF] topology description scheme

Hi Martin Comment inline From: Klozik, MartinX Sent: Tuesday, September 6, 2016 3:16 PM To: Tahhan, Maryam ; opnfv-tech-discuss@lists.opnfv.org Subject: RE: [VSPERF] topology description scheme Hi Maryam, Thanks for initial proposal. It looks good overall. It seems, we

Re: [opnfv-tech-discuss] [Apex] puppet logging for debug

Hi Peng, On the jump host you can do opnfv-util debug-stack. That will print out the reason for heat stack failure, including puppet errors. If that doesn't give you enough information, then look at each /var/log/messages on the nodes themselves. That will contain all the puppet and other

[opnfv-tech-discuss] [SPC Polestar] Minutes from the OPNFV Polestar Working Group call (September 1, 2016)

Attendees: Anthony Soong, Chris Price, Larry Lamers, Margaret Chiosi, Pierre Lynch, Steven Wright, Tapio Tallgren, Toby Ford, Uli Kleber, Yunjun Zhang, Min Yu - Meeting Minutes/Agenda: approved - There was a suggestion to meet weekly beyond September. A concern was raised

[opnfv-tech-discuss] [SFQM] contributor request

Hi all, I would like to sign up to be a contributor to SFQM. Thanks, Taras. -- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

David, I think we can brainstorm how to better manage those projects that produce docs only in D Release, including requirement projects. For example, when we set up milestones, we can define which milestones are applicable to those projects that produce docs only. Just like we defined one

Re: [opnfv-tech-discuss] [opnfv-tsc] harmonized configuration set for OPNFV

Hey All Just as a question of JIRA - this is/was a defined goal of Genesis, back when the original PHAROS specification (which is basically support for the 5 basical OStack networks (tagged/untagged), 3 Controller/2Compute Topology and supporting either VLAN or VXLAN (so as to support ODL) as