[opnfv-tech-discuss] Committer Board Election update

[Raymond Paik]

All,

The nomination period for the Committer Board Election closed at 5pm
Pacific Time today, and I only received one nomination from Chris Price.
Although this may seem like a formality, according to the OPNFV Bylaws, we
still need to have an election.

Committers listed on
https://wiki.opnfv.org/display/DEV/2016+Committer+Board+Election+-+Committers+List
will be receiving a link for Condorcet voting in the next few days.

Thanks,

Ray
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes

[HU, BIN]

Hongbo and all,

Thank you for the minutes.

I think the agreement is that we will move forward with patch 
https://gerrit.opnfv.org/gerrit/#/c/20719/ as IPv6 test case template, and 
Chris will submit a new patch in new directory for general template. It means:

-  If there is any technical issue regarding patch 20719, it should be 
commented by Monday (9/26) as Prakash suggested

-  Otherwise, it should be approved and merged by committers.
The action item you mentioned for Chris and myself was actually the action item 
from last week’s meeting (9/16), which is no longer applicable based on the 
agreement made on the meeting this morning (9/23).

Let me know if I am mistaken.
Thanks

Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tianhongbo
Sent: Friday, September 23, 2016 7:58 PM
To: 'TECH-DISCUSS OPNFV' 
Subject: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes

Hi all:

Here is the minutes for the this dovetail weekly meeting.
If I missed something, please send the email to me.

Minutes of DoveTail Discussion

  *   Date and Time: Friday at 
1400-1500
 UTC, September 23, 2016
  *   Convener: Hongbo (Huawei)
  *   Participants:
 *   Bin Hu (AT)
 *   Prakash (Huawei)
 *   Chris Price (Ericsson)

* Sajeev Manikkoth (IEEE)

 *   Leo Wang (Huawei)
 *   Dave Neary (Red Hat)

* Mika Rautakumpu (Nokia)

 *   Yu Yang (Huawei)

  *   Agenda:

 *   Approval of the last minutes
 *   update the IPV6 template
 *   Update proposal for Dovetail tool prototype
 *   Update proposal for Test plan list
 *   Other issues.
Discussion & Action Item
IRC：

  *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-23-13.57.html
  *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-23-13.57.txt
  *   Log:  
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-23-13.57.log.html
  *   Minutes from last week for reference:
 *   
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-16-13.59.html
Suggestion and Agreement
*The last minutes is approved
*Leo present the dovetail tool demo. all the codes are in the dovetail git

 *   https://git.opnfv.org/cgit/dovetail/tree/
 *   for build https://build.opnfv.org/ci/view/dovetail/
 *   Leo introduces the code structure and functions
 *   The test case is already implemented
 *   Dave wanted to make sure that the docker tests can be execute on os 
other than ubuntu like cetos, suse etc.
*Bin mentions that the IPv6 template patch has been uploaded more than two 
weeks

 *   8 comments on patch set 4 and 13 comments on Patch set 6 were all 
addressed
 *   Most recent patch set 7 was uploaded on 9/14. Not any technical 
comment since then for 9 days
 *   On Monday 9/19, this issue was discussed in Board C Committee. Chris 
Price summarized the guidance from Board C Committee
 *   The test specification for our compliance suites should be detailed 
and step by step
 *   They should be detailed enough to
*   enable, if necessary, someone to execute the tests in a manual 
fashion
*   write a test case for a specific framework or implementation
 *   Looking at Patch set 7 of 20719, clearly it conforms to the guidance 
from Board C, because
*   Detailed test case example of IPv6 that can be executed in both 
automatic and manual fashion
*   Test case for OpenStack Neutron API, which is a specific framework 
or implementation
 *   Bin is asking for moving forward with this patch, unless there is 
significant technical issue
*   Prakash suggested to approve it
*   Bin indicated that he wanted this patch to be handled in the same 
way as a prior patch
   *   https://gerrit.opnfv.org/gerrit/#/c/18151/
   *   In this patch 18151, there were unaddressed comments posted by 
IPv6 PTL on August 10
   *   August 11th, it was concluded that “Good discussion and a lot of 
it is out of scope for the intention of this patch. Let's discuss all of this 
on Fridays call and identify how and where to carry some of these conversations 
forward
   *   It was merged on the same day August 11
   *   Meeting took place on August 12
   *   Prakash suggested to give time by Monday
*   All agreed to move forward with patch 20719
  *   Chris will submit a new patch with new directory for general template
 *   Bin suggested to remove reference to IPv6 in general template
Action items
*Hongbo to take the currently identified dovetail areas for test and 
present them to the C committee asking for feedback and prioritization.

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

[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
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:https://global.gotomeeting.com/join/599078381\n+
 1-773-945-1031x599078381#\n\nHello team\,\n\nHere is the information of ou
 r IPv6 project meeting #49 to check the status update.\n\n-   When: Fr
 iday 8:00-9:00 PDT (15:00-16:00 UTC) October 7th\, 2016\no   Your loca
 l time\n-   Bridge: GoTo Meeting:\no   Web Confere
 ncing: https://global.gotomeeting.com/join/599078381\no   Dial-in only
 :\n•   United States (Long distance): +1 (773) 945-1031 / Access Cod
 e: 599-078-381\n•   More phone numbers: https://global.gotomeeting.c
 om/599078381/numbersdisplay.html\n-   Meeting page: https://wiki.opnfv
 .org/display/meetings/ipv6 for agenda and minutes\n-   Project wiki pa
 ge: https://wiki.opnfv.org/display/ipv6/IPv6+Home for all information and 
 resources related to IPv6 project\n\nLook forward to working with everyone
 .\n\nThanks\nBin\n\n
SUMMARY;LANGUAGE=en-US:[IPv6] Project Meeting #49
DTSTART;TZID=Pacific Standard Time:20161007T08
DTEND;TZID=Pacific Standard Time:20161007T09
UID:04008200E00074C5B7101A82E0088018941BB515D201000
 010001A2CACFC0988B1499D279AF31B74182C
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160923T231114Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:+1-773-945-1031x599078381#
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1384671264
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

[Gregory Elkinbard]

+1

On Fri, Sep 23, 2016 at 3:20 AM, Stefan Berg K 
wrote:

> +1
> --
> *Från:* opnfv-tech-discuss-boun...@lists.opnfv.org <
> opnfv-tech-discuss-boun...@lists.opnfv.org> för Daniel Smith <
> daniel.sm...@ericsson.com>
> *Skickat:* den 23 september 2016 08:52:47
> *Till:* Jonas Bjurel; opnfv-tech-discuss@lists.opnfv.org; Alexandru
> Avadanii
> *Ämne:* Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii
>
>
> +1
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Jonas Bjurel
> *Sent:* Thursday, September 22, 2016 2:36 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii <
> alexandru.avada...@enea.com>
> *Subject:* [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii
>
>
>
> I would like to nominate Alexandru Avadanii (ENEA) as a committer in
> Fuel@OPNFV, I have been in contact
>
> with Alexandru and his willing to take on the role.
>
> Alexandru is one of the main architects/committers in Armband which is a
> port of Fuel@OPNFV to the ARM
>
> Architecture, he has also been very active in Fuel@OPNFV.
> This month, Alexandru is the OPNFV committer with the most commits.
>
>
>
> OPNFV committers, reply to this mail with your vote (-1, 0, +1).
>
>
>
> BR/Jonas
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Plugfest registration reminder plus the co-located Hackfest

[Raymond Paik]

Thanks Bryan.

Also want to remind people who already registered to start populating your
Participant Pages under
https://wiki.opnfv.org/display/EVNT/C-Plugfest+Participant+Pages

The next bi-weekly call is on Monday (Sep. 26th)  at 7am Pacific Time and
you can find the call logistics at
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Colorado+Release

Ray

On Thu, Sep 22, 2016 at 4:26 PM, SULLIVAN, BRYAN L  wrote:

> I added three topics to that page:
>
> · Creating VNF blueprint tests: approaches to creating automated
> scripts that install VNFMs, blueprints, lifecycle-manage them, etc.
>
> · Integrating VES agent code into your VNFs.
>
> · Hacking policies thru Congress.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik
> *Sent:* Tuesday, September 06, 2016 11:17 PM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] Plugfest registration reminder plus the
> co-located Hackfest
>
>
>
> All,
>
>
>
> A reminder that you can now register for the 2nd OPNFV Plugfest at
> https://www.regonline.com/OPNFVPlugfestDec2016.
>
>
>
> Also, as was discussed on the TSC call last week, the Q4 Hackfest will be
> co-located with the Plugfest.  Under the Plugfest wiki, I created a
> Hackfest planning page at https://wiki.opnfv.org/display/EVNT/Co-located+
> Hackfest+Planning+Page
>
>
>
> During our first plugfest, we had some great sessions led by project team
> members from testing and installer projects and those are good examples of
> hacking sessions that we could repeat at UNH-IOL.  Please add your
> topic/session ideas to the wiki page.
>
>
>
> Thanks,
>
>
>
> Ray
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Packaging CI

[Alexandru Avadanii]

Hi,

I started a very small etherpad for gathering ideas about packaging CI in 
OPNFV, see [1].
I am aware our purpose is upstreaming our changes, but this is not always 
possible or effective, hence the need for some form of our own package 
distribution systems.
Hopefully, this could be a nice addition, and not something encouraging 
spinning distro forks of CentOS/Ubuntu etc.

Looking forward to your thoughts on this one.

BR,
Alex

[1] https://etherpad.openstack.org/p/OPNFV_packaging_CI
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Functest] Project organization

[Jose Lausuch]

Hi,

I think it is a good idea, Morgan. 
Another way to do this would be to have elections after each release (6 month 
cadence) where the PTL can always be re-elected but never more than 2 times in 
a row.

For this election, I also nominate myself as a candidate for Functest PTL.

Thanks,
Jose



-Original Message-
From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] 
Sent: Tuesday, September 20, 2016 15:10 PM
To: serena.feng@gmail.com; ollivier.ced...@gmail.com; Jose Lausuch; 
mei...@huawei.com; valentin.bouc...@orange.com; lanqingl...@huawei.com; 
viktor.tikka...@nokia.com; ";juha.kosonen"@nokia.com; zhanghao...@huawei.com; 
raghavendrachari.kams...@hpe.com; lixiaoguang (C)
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [Functest] Project organization

Hi,

as discussed quickly this morning during our weekly meeting, I would like to 
plan the next Functest PTL election.

My idea for Functest is to call for PTL election every 2 releases.

The PTL will thus be legitimate by the core developpers, it should help 
reflecting the diversity within the project, ease the transition between PTL 
generations and bring new energy and creativity.

I think it makes also sense to put a limit in term of relections => 1 possible 
re-election =  2 mandates = 4 releases = 2 years max per PTL

If no objection from the core developers, I would like to plan the first 
election on the 11th of October 2016 correspoding to Colorado release.
The vote will be done by IRC durung the weekly meeting (8 UTC).
All Functest core devs can vote and if they cannot be present they can delegate 
their vote.

For this election I will be candidate to my reelection :) but other 
candidatures are more than welcome.

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law; they should not be distributed, used 
or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
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] [functest] [D release]

[SULLIVAN, BRYAN L]

Morgan,

That's a big page so I'm not sure where to put this input, but here are some 
things in scope for Danube:

* Models: several new VNFs and VNFM tests, some already listed at 
https://wiki.opnfv.org/display/models/testing. Some of these will be used in 
the Colorado Plugfest - see the "VNF Portability" section on the page 
https://wiki.opnfv.org/display/EVNT/Colorado+Plugfest+Test+Cases. VNFMs will 
include Tacker, Cloudify, OpenBaton, etc. The tests will focus on simple to 
medium-complexity VNFs, specific TOSCA-based resource requirements as supported 
by those VNFMs, and YANG-based application control via ODL.

* VES: Deployment of a VES Hello World VNF, and reference (real) VNFs 
integrated with VES

* Copper: additional policy test cases

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Friday, September 23, 2016 8:09 AM
To: Jose Lausuch ; serena feng 
; OLLIVIER Cédric IMT/OLN 
; Jose Lausuch ; 
Tikkanen, Viktor (Nokia - FI/Espoo) ; Kosonen, Juha 
(Nokia - FI/Espoo) ; Gaynor, Colum (Nokia - FI/Espoo) 
; Haapavirta, Juha (Nokia - FI/Espoo) 
; Kamsali, Raghavendrachari 
; Meimei ; valentin 
boucher 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [OPNFV] [functest] [D release]

Hi

based on the discussion initiated during last Functest weekly meeting, I
created the Danube page for the project.

https://wiki.opnfv.org/display/functest/Functest+Danube

as mentioned in the beginning of the page, this page is a draft

The goal is to collect element to prepare the D release.

Functest evolutions are expected in

- the Functest framework (reflexion on the relations between the test
projects (API), dockerization, CI evolution, reporting, dashboard)

- new tools and libs

- the new tests (unit, functional, VNF onboarding,...)

If you want to participate to Functest D release feel free to modify the
page and/or create new pages referenced from this one

You can also obviously use the mailing list or meet us during the weekly
meeting (Every Tuesday 8 AM UTC #opnfv-functest)

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV] [functest] [D release]

[morgan.richomme]

Hi

based on the discussion initiated during last Functest weekly meeting, I
created the Danube page for the project.

https://wiki.opnfv.org/display/functest/Functest+Danube

as mentioned in the beginning of the page, this page is a draft

The goal is to collect element to prepare the D release.

Functest evolutions are expected in

- the Functest framework (reflexion on the relations between the test
projects (API), dockerization, CI evolution, reporting, dashboard)

- new tools and libs

- the new tests (unit, functional, VNF onboarding,...)

If you want to participate to Functest D release feel free to modify the
page and/or create new pages referenced from this one

You can also obviously use the mailing list or meet us during the weekly
meeting (Every Tuesday 8 AM UTC #opnfv-functest)

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [ovsnfv] [vsperf] Analysis of Microburst on VSwitch

[Lee, Chunghan]

Hi, 

Thank you for interesting my work.
I'm also glad to discuss my work together.
Moreover, I'm also interested in the behavior of DPDK side.

> There is a vSwitch testing project in OPNFV - vsperf 
> https://wiki.opnfv.org/display/vsperf/?s[]=vsperf
I knew this project, but I did not check this in thesedays.
I will check the current status of vsperf.

I'll share the experiment commands, such as iperf and tcpdump.
Please give me a time to arrange them. ;-)

Regards,
Chunghan Lee

--
Chunghan Lee
Cloud Network Project. Fujitsu Laboratories Ltd.
4-1-1 Kamikodanaka, Nakahara-ku, 
Kawasaki-shi, Kanagawa 211-8588, Japan
E-mail： lee.chung...@jp.fujitsu.com
--


-Original Message-
From: O Mahony, Billy [mailto:billy.o.mah...@intel.com] 
Sent: Wednesday, September 21, 2016 6:26 PM
To: Lee, Chunghan/李 忠翰; opnfv-tech-discuss@lists.opnfv.org
Cc: Gray, Mark D; therb...@redhat.com; Michal Skalski
Subject: [ovsnfv] [vsperf] Analysis of Microburst on VSwitch

Hi Chunghan,

Thanks for your presentation on Monday 
(https://wiki.opnfv.org/download/attachments/5046510/0919_ovsnfv.pdf?version=1=1474280389000=v2
 ). It was very interesting to see where packets are lost when OVS is 
overloaded.

There is a vSwitch testing project in OPNFV - vsperf 
https://wiki.opnfv.org/display/vsperf/?s[]=vsperf

This has a set of standardized tests that can be run on vSwitches - currently 
it supports OVS and OVS-DPDK. The tests have been defined and codified in an 
IETF draft 
https://wiki.opnfv.org/display/vsperf/Vswitchperf+Ietf+Draft+Submission , 
though not all those tests are supported yet. It currently supports IXIA (h/w) 
and Moongen (s/w) traffic generators.

Hope you find that info useful, 
/Billy.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

[Stefan Berg K]

+1


Från: opnfv-tech-discuss-boun...@lists.opnfv.org 
 för Daniel Smith 

Skickat: den 23 september 2016 08:52:47
Till: Jonas Bjurel; opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii
Ämne: Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

+1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jonas Bjurel
Sent: Thursday, September 22, 2016 2:36 PM
To: opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii 

Subject: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

I would like to nominate Alexandru Avadanii (ENEA) as a committer in 
Fuel@OPNFV, I have been in contact
with Alexandru and his willing to take on the role.
Alexandru is one of the main architects/committers in Armband which is a port 
of Fuel@OPNFV to the ARM
Architecture, he has also been very active in Fuel@OPNFV.
This month, Alexandru is the OPNFV committer with the most commits.

OPNFV committers, reply to this mail with your vote (-1, 0, +1).

BR/Jonas
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [daisy4nfv] Meeting minutes for IRC meeting 0800UTC Sep. 23 2016

[hu . zhijiang]

Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.html
 

Minutes (text): 
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.txt
 

Log:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.log.html
 



Have a good weekend!

B.R.,
Zhijiang

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [SFC] Nominating Manuel Buil as committer

[Brady Allen Johnson]

Thanks for your votes everybody!

With my +1 vote, there were 6 votes cast all together: all of them being 
+1, which makes it more than unanimous.


Congratulations Manuel.

I'll formalize this with the TSC.

Regards,

Brady


On 22/09/16 20:49, Vishal Murgai (vmurgai) wrote:


+1

*From:*opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Sam 
Hague

*Sent:* Thursday, September 22, 2016 11:12 AM
*To:* Paul Quinn (paulq) 
*Cc:* opnfv-tech-discuss@lists.opnfv.org
*Subject:* Re: [opnfv-tech-discuss] [SFC] Nominating Manuel Buil as 
committer


+1

On Thu, Sep 22, 2016 at 10:46 AM, Paul Quinn (paulq) > wrote:


+1

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Follow up on Upstreaming Questions

[Daniel Smith]

Hello Everyone.

thank you all for your responses.  I can see that this will require some more 
discussion and work.   When we started OPNFV (and in fact through Arno 
(remember the Fish on the Sweater?), our tenant and marketing has indicated 
that one of the main value adds for OPNFV is that we push requirements back 
upstream.

From the threads I can summarize a couple of things:

1st – We don’t have a method of knowing/pushing things upstream in a holistic 
OPNFV group method (from Bryan’s comments – people should do this on their 
own).  In my mind that is a bit of a hard one for me to see how that would 
work/be more effective than a individual pushing a blueprint to say Openstack.  
  My understanding was that the scope, size and relationships established by 
the TSC and Governance board were to put such paths in place so that OPNFV is 
see *by upstream communities – as a valid vehicle for this work.

2nd – We are three years in and while we have thought about this and then 
shelved it, I wonder what that communicates to the people who have delivered 
requirements projects (or however you want to call it – I really think we spend 
too much time debating labels ) in the previous two releases and in Colorado.   
To me, the thread indicates that OPNFV doesn’t have a method to “do something” 
with what is produced

3rd – While we are very adept at creating documents, wiki’s and the like – in 
the thread I haven’t really seen an answer to the question – again, going back 
to the three line of the Missions statement of OPNFV when it was started – that 
being that OPNFV as a organization delivers requirements from the NFV/NFV space 
 back to upstream communities.  In Vancouver there was discussion with the 
Openstack Telco WorkGroup regarding this very topic, so I would wonder “who” in 
OPNFV is chasing this down to ensure that the marketing and mission statements 
that we make (and thus use to have Companies provide money, resources and 
people )to OPNFV is actually being met – in short – where is the Proof that we 
are doing this.


Thanks again for all the commentary, I hope that at the very least this thread 
causes the “forming TSC” and more importantly the Governance board to take a 
look at the number and amount of information that is being generated by people, 
that as far as I can tell up to now, is delivered and then sits.  I don’t think 
that you can say to a group that joined OPNFV (as this vehicle) that the PTLs 
then have go chase down the upstream communities – if that is the case, then 
why do it in OPNFV? (not being nasty – but we should sometimes ask ourselves 
some tough questions about what we are doing with the output by the masses).

Regards,
Daniel Smith


From: Heather Kirksey [mailto:hkirk...@linuxfoundation.org]
Sent: Thursday, September 22, 2016 6:11 PM
To: Dave Neary 
Cc: Daniel Smith ; David McBride 
; Fatih Degirmenci 
; jack.mor...@intel.com; Christopher Price 
; Ray Paik ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Follow up on Upstreaming Questions

On the "Requirements phase" discussion specifically:

It might depend on what you, as a project, are interested in and what is 
helpful. As Dave says, we've generally taken a fairly laissez-faire approach to 
this, and it's generally resulted in a project using their requirements 
document as a project-internal tool to facilitate a set of upstream 
contributions as they've decided such blueprints, patches, Jira tickets, etc., 
make sense.

If projects in this phase of their work think getting more eyes outside of the 
project would benefit their work, let's think about how to highlight some of 
this rather than waiting for extremely interested parties to visit the repo. 
Not to make work, but if requirements-phase projects think it would be 
beneficial.

I think on a similar thread folks suggested a wiki page or something like that. 
It could perhaps be linked to on the general upstream blueprint progress 
tracking page (if that's even up to date) and perhaps our EUAG page (for 
end-user input).

This wouldn't be something like a gate or requirement but a facilitation of 
information sharing. (This may or may not be related to some of what you were 
thinking, Ash).

What do y'all as projects doing this work want?  What serves your needs?

Heather

On Thu, Sep 22, 2016 at 12:58 PM, Dave Neary 
> wrote:
Hi,

On 09/20/2016 12:57 PM, Daniel Smith wrote:
> Several weeks ago as part of the inclusion of Requirements Projects,  I
> asked how we know that people are looking at what we are producing in
> Requirements projects and how we (OPNFV) ensure that deliverables from
> Requirements projects are being reviewed and taken into account upstream
> (from an OPNFV overall standpoint).
>
> Would any of you 

Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

[Daniel Smith]

+1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jonas Bjurel
Sent: Thursday, September 22, 2016 2:36 PM
To: opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii 

Subject: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

I would like to nominate Alexandru Avadanii (ENEA) as a committer in 
Fuel@OPNFV, I have been in contact
with Alexandru and his willing to take on the role.
Alexandru is one of the main architects/committers in Armband which is a port 
of Fuel@OPNFV to the ARM
Architecture, he has also been very active in Fuel@OPNFV.
This month, Alexandru is the OPNFV committer with the most commits.

OPNFV committers, reply to this mail with your vote (-1, 0, +1).

BR/Jonas
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss