Hi all:
I have a suggestion:
Can we use this kind of categories:
1) outstanding committers
2) outstanding contributors
3) outstanding PTL
4) innovation awards
5) Community support/leadership
this kind of categories may encourage more people to act as the
The category looks good.
I think we may need publish key indicators and selection process for these
awards to make it open and transparent. Not sure there is already some
policy defined by TSC.
My two cents.
On Wed, Feb 8, 2017 at 2:45 PM Raymond Paik
wrote:
>
That's correct...
On Tue, Feb 7, 2017 at 10:37 PM, Yujun Zhang (ZTE) wrote:
> less frequently => do you mean from every quarter to each release?
>
> On Wed, Feb 8, 2017 at 6:21 AM Raymond Paik
> wrote:
>
>> Reviving the discussion after the
Hi OPNFV,
The Board meeting for Feb took place on Feb. 2nd . Please find a summary of the
meeting below.
* 2016 recap and year ahead: There was a review of 2016 accomplishments
such as Brahmaputra/Colorado releases, Summit, Plugfests, launch of the End
User Advisory Group, etc. Next,
Hi OpenRetrieverer:
Last meeting, we decided some actions in below:
#1 Write requirement document for Installer to integrate essential
openstack components.
Create a task : https://jira.opnfv.org/browse/CONTAINER-1
#2 Using ansible playbook to deploy a
Hello, team,
Agenda of Feb.9 2017
* (MS6) Test cases implemented, preliminary documentation completed, and stable
branch open
* Multisite deployment environment.
* Kingbird feature development.
* Open discussion
IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During
Reviving the discussion after the Chinese New Year holidays...
I wanted to propose the following new categories. Also, since we're doing
these awards less frequently we can award more than one person in each
category (shown in numbers in parentheses).
- Code development (3)
- Community
All,
Following up on an earlier discussion on the TSC call. First, changes to
the TSC Charter do require a Board approval. We did this about two years
ago for a minor wording change. Once the TSC agrees on the new text, the
TSC Chair can present to the Board for a vote.
Secondly, I looked at
Thanks Maryam.
Since you mentioned options / config :)When a common model is
chosen (VES / OpenConfig / etc...), will Collectd be open to having dynamic
configuration using that model?
Araon
On Tue, Feb 7, 2017 at 1:57 PM, Tahhan, Maryam
wrote:
> Or at least
Or at least to allow the option to disable polling... you might want both for
an out of band update :)
> -Original Message-
> From: Tahhan, Maryam
> Sent: Tuesday, February 7, 2017 6:56 PM
> To: opnfv-tech-discuss@lists.opnfv.org; Aaron Smith
> Cc: Mcmahon, Tony B
Hi Aaron and folks
I was wrong about the ovs polling configuration being optional, It looks like
the ovs events plugin does register for link status updates, but it also is
polling on a regular interval... so based on the discussion today I will add a
feature request to add a configuration
Hi OPNFV,
over the past few weeks we've distilled two proposals to add analytics and more
diagnostic capabilities to OPNFV and OPNFV scenarios. We've published the two
new project proposals on the wiki:
* Bamboo: https://wiki.opnfv.org/display/bamboo/Bamboo+Project+Proposal
*
Hi Brady,
While adding SFC and SFC Classifier, I can't see any valid errors in karaf.log.
Anyways, I am pasting WARN and ERROR logs of sfc in the below link:
Karaf warning messages:
http://pastebin.com/PCa4QFft
Karaf error messages:
http://pastebin.com/34CmBjZW
But, some of the karaf logs are
Hi Morgan,
Yes – I think this is the best place since it is common for all testing groups.
BR,
Sofia
From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: den 7 februari 2017 16:19
To: Sofia Wallin ; Kunzmann, Gerald
;
Team,
Today (Feb 7) is the first Asia / Pacific release meeting. This meeting is
intended to help APAC OPNFV members that have a difficult time attending
the regular weekly release meeting due to time zone differences.
The meeting will be held every other Tuesday at 7:30-8:00 p.m. (PST - 11:30
Hi Sofia
For Danube, the testing group initiated an umbrella doc, currently
hosted in opnfvdocs/docs/testing/ecosystem
is it OK?
Morgan
Le 07/02/2017 à 15:49, Sofia Wallin a écrit :
>
> Hi Gerald,
>
> The documentation is divided into 3 different entry points/areas so
> the structure will
Hi Gerald,
The documentation is divided into 3 different entry points/areas so the
structure will look as following,
/docs/release
/configguide
/installation
/release-notes
/scenarios
└── scenario.name
/userguide
/docs/developer
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
Srikanth,
The reason wget works and doesnt send packets to the VM is because your
classification rule (pasted below) matches on srcPort=2000 and
dstPort=80, but you dont specify the srcPort with wget, so the packets
dont match classification, and subsequently dont get sent to SFC (hence
Hi,
My setup includes:
* One Openstack Controller with ODL (of course with SFC) which is
deployed through OPNFV Colorado 3.0
* One aarch64 Compute Node (OpenStack Mitaka), which is attached to the
above OS Controller
I downloaded OVS 2.6.1 from OVS git hub and applied NSH
21 matches
Mail list logo