[opnfv-tech-discuss] Notification: Update of testapi this afternoon

[feng . xiaowei]

Hi all,

I plan to update testapi on testresults.opnfv.org this afternoon, 
so there will be a little breakoff for reporting test results.

Regards,
Serena___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Minutes of weekly meeting Aug.11

[joehuang]

Aug. 11 2016: Agenda & Minutes

  *   Agenda
 *   functest issues

 *   documentation review

 *   KB 0.2.0 tagging

  *   Minutes

  1.
 *   https://gerrit.opnfv.org/gerrit/#/c/18379/ 
(joehuang,
 07:18:03)
 *   https://gerrit.opnfv.org/gerrit/#/c/17687/ 
(joehuang,
 07:18:18)
 *   documentation should be complemented next Monday, Aug.15 
(joehuang,
 07:21:49)
 *   1 week window for stable branch creation for Colorado release, by 
Aug.22. 
(joehuang,
 07:22:18)
 *   https://gerrit.opnfv.org/gerrit/#/c/18379/ 
(SAshish,
 07:30:59)
 *   ACTION: should we keep CI/functest job for colorado release 
(joehuang,
 07:59:54)

  *   Link
 *   Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-11-07.01.html
 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-11-07.01.txt
 *   Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-11-07.01.log.html


From: joehuang
Sent: 10 August 2016 17:22
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss][multisite]Weekly meeting of Aug.11


Hello, team,



Good progress in functest integration, let's dicsuss the project in weekly 
meeting:


Agenda of Aug.11 2016
*   functest issues
* documentation review
* KB 0.2.0 tagging

IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.


Best Regards

Chaoyi Huang ( joehuang )




From: joehuang
Sent: 03 August 2016 16:00
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss][multisite]Weekly meeting of Aug.4

Hello,


Agenda of Aug.4 2016
*KB endpoint access issue and functest
**ser guide documentation
**KB 0.2.0 tagging

IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.


Best Regards

Chaoyi Huang ( joehuang )
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Network issues during OPFNV deployment

[Korynkevych, RomanX]

Hi Daniel,

On Fuel machine I have access:

* eth0 to compute/controller nodes through private network 10.20.0.0/24

[root@fuel ~]# fuel node
 id | status   | name   | cluster | ip | 
mac   | roles | pending_roles | online | group_id
 
---+--++-++---+---+---++-
  3 | ready| WCP-28095 (70:db) |   1 | 10.20.0.3   | 
2a:d1:1d:20:b1:f6 | controller  |   |  1 |  
  1
  8 | ready| WCP-28094 (0c:93)  |   1 | 10.20.0.11 | 
00:1e:67:d0:0c:93 | controller, mongo |   |  1 |1
  9 | ready| WCP-28098 (49:5c)  |   1 | 10.20.0.8   | 
2a:e3:a8:dc:b8:2b | compute   |   |  1 |
1
  6 | ready| WCP-28097 (49:71)  |   1 | 10.20.0.9   | 
42:39:02:32:08:fe  | compute   |   |  1 |   
 1
  4 | ready| WCP-28096 (e2:67)  |   1 | 10.20.0.10| 
16:dc:d8:b8:e3:07 | controller ||  1 |  
  1

* eth1 connected to external network

* eth0.101 connected to MGMT network (MGMT network is added to 101 VLAN)

Fuel machine cannot be the host for running OPFNV tests?

Regards,
Roman.

From: Daniel Smith [mailto:daniel.sm...@ericsson.com]
Sent: Wednesday, August 10, 2016 8:33 PM
To: Korynkevych, RomanX ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Network issues during OPFNV deployment

Hey  there.

Can you please confirm that your jumphost (that is running your FUEL node) has 
connectivity (over the bridges - I am assuming you are doing an nested 
installation ) to the COMPUTE/CONTROLLER Nodes once they are deployed?
It would appear that why you have FUEL talking to your nodes, you still need to 
have the HOST (running your FUEL node) talk to the controllers /computes on the 
MGMT network (not ADMIN)

D

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Korynkevych, 
RomanX
Sent: Wednesday, August 10, 2016 11:04 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Network issues during OPFNV deployment

Hi All,

I've trying to deploy OPFNV environment using Fuel (IP: 10.20.0.2) as Jump Host 
based on 
http://artifacts.opnfv.org/functest/brahmaputra/docs/configguide/configguide.pdf
 instructions. Problems occur on the step 3.3 Preparing the Functest 
environment. Execution of ${repos_dir}/functest/docker/prepare_env.sh fails 
because it cannot access 192.168.0.X auth server management network from the 
container. Also 10.20.0.X is not accessible. Anyway I can ping external 
(Internet) and public networks. Does anybody has seen this problem? Is anything 
missed in the instruction?

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

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[Carlos Goncalves]

Hi Ray, all,

I would like to nominate Ryota.

Nominee: Ryota Mibu
Employer: NEC
Statement: Ryota is one of the most active technical contributors in OPNFV and 
upstream in OpenStack. He is the Doctor Project Team Lead, active committer and 
contributor in several other OPNFV projects (e.g. Promise, Docs, Releng, Apex). 
These contributions led to cross-project collaborations (e.g. Doctor + SQFM). 
Ryota has been an instrumental person to OPNFV and its ecosystem.

Thanks,
Carlos

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: 08 August 2016 08:21
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

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] [Orchestra] new project proposal

[Odini, Marie-Paule (CMS ww)]

Cool name indeed ! and the logo :)

[cid:image002.png@01D1F3CF.64B92490]

Marie-Paule Odini
Distinguished Technologist
HPE Corporate CT Office - CMS/CSB
Phone: +33 672992772
Email: marie-paule.od...@hpe.com
[cid:image001.png@01D10CEA.16CEFEC0]





From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Thursday, August 11, 2016 1:21 AM
To: Bob Monkman 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

How about Bat-Mano?

On Aug 5, 2016, at 8:52 AM, Bob Monkman 
mailto:bob.monk...@arm.com>> wrote:
Guiseppe, Chris,
Good comments and I like fun names. I see both sides on this 
one. I thought it was worth a look, since Yuan brought it up and I could see 
how it could _possibly_ be misconstrued. As was said, if a critical mass were 
to think it an issue, the Open Baton team- else I do not feel strong enough to 
push on it. Good luck with the project Giuseppe and team.
Regards,
Bob

Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490

From: Carella, Giuseppe [mailto:giuseppe.care...@fokus.fraunhofer.de]
Sent: Friday, August 05, 2016 4:32 PM
To: Christopher Price
Cc: Bob Monkman; Liu Yuan; BIN; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi all,

indeed that was our intention, to have a funny name...considering our open 
"baton" we thought it would make sense to build an orchestra using the OPNFV 
instruments (projects) :-)

of course, I agree that if there are major concerns we'll have to reconsider it.

Cheers,
Giuseppe

Join us at the IEEE 5G Week in November in Berlin (http://www.berlin5gweek.org/)

On 05 Aug 2016, at 17:26, Christopher Price 
mailto:chrispric...@gmail.com>> wrote:

Hi Bob,

I tend to agree with you, but personally don't put that much stock into a name.
In the case of OPNFV-MANO the name was indicative of an area in OPNFV so we did 
ask that the team consider revising the name.  If a project was to propose the 
name OPNFV "orchestration" I would similarly ask them to reconsider.

Opera and Orchestra I thank are really fun names that refer to the MANO space 
and activities is service orchestration, I had thought it was an entertaining 
theme and to be honest was wondering if the OSM group might choose something 
similarly theatrical if/when they were to participate.

I guess I had not considered this name to be an issue, but if there are 
concerns with it let's discuss it openly every opinion counts here.

/ Chris


From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Bob Monkman mailto:bob.monk...@arm.com>>
Date: Friday 5 August 2016 at 16:59
To: Liu Yuan mailto:liuyuan_c...@hotmail.com>>, BIN 
mailto:bh5...@att.com>>, "Carella, Giuseppe" 
mailto:giuseppe.care...@fokus.fraunhofer.de>>
Cc: TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Yuan,
I can see your point. I think projects should avoid names that 
come to close to appearing to describe themselves as _the_ solution for some 
category of function, unless the project is an umbrella for multiple options. I 
am not judging that this was the intent with Orchestra, but one could argue 
such a name "grabs" the function for one option.

I think we made a mistake with Fast Data Stacks, but no one 
else seemed to question it. It comprises a single vendor solution for a broad 
function area that has innumerable options. I think teams should be sent back 
to the drawing board for a new name, as was asked of Open-O team.

One opinion,
Bob

Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Liu Yuan
Sent: Friday, August 05, 2016 10:25 AM
To: BIN; Carella, Giuseppe
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi,

I just recall the OPNFV OPEN-O project was named OPNFV-MANO at the beginning. 
And during the discussion, the team thought the scope were too broad, and 
needed focus or convergence. Then the project changed the name.

About the name of the Orchestra, I think have the similar situation. The 
meaning of Orchestra also includes broad scopes. So, I am wondering why there 
is a difference between these two projects.

Regards,
Yuan


Liu Yuan
liuyuan_c...@hotmail.com

From: liuyuan_c...@hotmail.com
Date: 2016-08-02 18:23
To: Care

[opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release documentation

[Sofia Wallin]

Clarification,
All projects are expected to store the documentation in their own repositories.

The docs project will not create a composite document to pull all content 
together, this was hard to manage in Brahmaputra and generated a very high 
pressure on the toolchain.
Instead, the user guide, installation & configuration will only contain an 
introduction of each document referring to the projects documentation.

The structure (which is very simplified) should look as following,
/docs//scenario.description.rst
/docs/userguide/feature.usage.rst
/docs/installationprocedure/installation.instruction.rst

//Sofia

From: Sofia Wallin
Sent: den 10 augusti 2016 14:08
To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org); TSC OPNFV 
(opnfv-...@lists.opnfv.org)
Subject: Update release documentation [opnfvdocs] [opnfv-tech-discuss]

Hi everyone,

After reviewing the status for Colorado we have agreed that:
Feature projects should produce a ”user guide” for their feature according to: 
https://gerrit.opnfv.org/gerrit/#/c/18311/
Scenario’s should also have a brief description provided by scenario owners 
according to: https://gerrit.opnfv.org/gerrit/#/c/18311/

The installation procedures as discussed on the project call should be handled 
by the installer projects. Use the installation instruction template that was 
used in Brahmaputra together with input from the scenario owners and with links 
to the scenario description documents.

The docs team will continue to work on the overall Colorado documents 
(overview, installation and user guide) however these will link to the project 
documents rather than importing text directly.


Let me know if you have any questions.

BR,
Sofia together with the docs team



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

Re: [opnfv-tech-discuss] Network issues during OPFNV deployment

[Daniel Smith]

Hey there.

Ok.. so fuel is running on the HOST machine and that is fine.

Can you show me the screen show of your "Node Interface" page on your FUEL UI?

As well, can you please do a "brtcl show" on the HOST machine (where you are 
running on the vM's).

Thanks
D

From: Korynkevych, RomanX [mailto:romanx.korynkev...@intel.com]
Sent: Thursday, August 11, 2016 4:49 AM
To: Daniel Smith 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Network issues during OPFNV deployment

Hi Daniel,

On Fuel machine I have access:

*eth0 to compute/controller nodes through private network 10.20.0.0/24

[root@fuel ~]# fuel node
 id | status   | name   | cluster | ip | 
mac   | roles | pending_roles | online | group_id
 
---+--++-++---+---+---++-
  3 | ready| WCP-28095 (70:db) |   1 | 10.20.0.3   | 
2a:d1:1d:20:b1:f6 | controller  |   |  1 |  
  1
  8 | ready| WCP-28094 (0c:93)  |   1 | 10.20.0.11 | 
00:1e:67:d0:0c:93 | controller, mongo |   |  1 |1
  9 | ready| WCP-28098 (49:5c)  |   1 | 10.20.0.8   | 
2a:e3:a8:dc:b8:2b | compute   |   |  1 |
1
  6 | ready| WCP-28097 (49:71)  |   1 | 10.20.0.9   | 
42:39:02:32:08:fe  | compute   |   |  1 |   
 1
  4 | ready| WCP-28096 (e2:67)  |   1 | 10.20.0.10| 
16:dc:d8:b8:e3:07 | controller ||  1 |  
  1

*eth1 connected to external network

*eth0.101 connected to MGMT network (MGMT network is added to 101 VLAN)

Fuel machine cannot be the host for running OPFNV tests?

Regards,
Roman.

From: Daniel Smith [mailto:daniel.sm...@ericsson.com]
Sent: Wednesday, August 10, 2016 8:33 PM
To: Korynkevych, RomanX 
mailto:romanx.korynkev...@intel.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Network issues during OPFNV deployment

Hey  there.

Can you please confirm that your jumphost (that is running your FUEL node) has 
connectivity (over the bridges - I am assuming you are doing an nested 
installation ) to the COMPUTE/CONTROLLER Nodes once they are deployed?
It would appear that why you have FUEL talking to your nodes, you still need to 
have the HOST (running your FUEL node) talk to the controllers /computes on the 
MGMT network (not ADMIN)

D

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Korynkevych, 
RomanX
Sent: Wednesday, August 10, 2016 11:04 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Network issues during OPFNV deployment

Hi All,

I've trying to deploy OPFNV environment using Fuel (IP: 10.20.0.2) as Jump Host 
based on 
http://artifacts.opnfv.org/functest/brahmaputra/docs/configguide/configguide.pdf
 instructions. Problems occur on the step 3.3 Preparing the Functest 
environment. Execution of ${repos_dir}/functest/docker/prepare_env.sh fails 
because it cannot access 192.168.0.X auth server management network from the 
container. Also 10.20.0.X is not accessible. Anyway I can ping external 
(Internet) and public networks. Does anybody has seen this problem? Is anything 
missed in the instruction?

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

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[Ulrich Kleber]

Hi,

I would like to nominate Mark Beierl.

Nominee: Mark Beierl
Employer: EMC
Statement: Beside his work on Storperf, Mark was the main worker during the 
wiki migration. Here he showed his integrating
and collaboration abilities and his broad understanding through the different 
areas of OPNFV.
I believe it would be a great help to have him on the TSC.

Cheers,
Uli



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: 08 August 2016 08:21
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

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] [Plugfest] December Plugfest Hardware

[Lincoln Lavoie]

Hello All,

I'd like to get a feel for who is planning to participate in the December
plugfest with hardware on site.  I've reached out to a number of
individuals, but just to hit the wider audience, I'm pinging the mailing
list as well.

If you are planning to participate in the plugfest, can you please respond
(publicly or privately), so we can start to get a sense of the equipment
availability / resources for the event.

Our next planning call is Monday, August 15, and I am planning to work on
the scope of the event with the group.  I'll send out a more formal agenda
for the call by the end of tomorrow.

If you have any questions, please let me know.

Cheers,
Lincoln
-- 
***
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies


www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
   


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 8/11/2016

[Reddy, Raghuveer]

Meeting logistics - https://wiki.opnfv.org/nfv-kvm

Agenda:

1)  C-Release

-Scenario Testing Status

-Milestones

-Jira

2)  Opens

Regards,
-Raghu
Ph: 408 765 4620
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[MORTON, ALFRED C (AL)]

+1, and to complete my #action from the testperf meeting this morning:

Statement: Mark is recognized as strong contributor to the test community,
and since our community is a key part of OPNFV, it was agreed (today)
that we should make at least two nominations from among the testers
for the available seats. Mark is one of our nominees, along with Morgan.

regards,
Al


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ulrich Kleber
Sent: Thursday, August 11, 2016 9:58 AM
To: Carlos Goncalves; Raymond Paik; opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Opening nominations for the 
Committers-at-Large TSC elections

Hi,

I would like to nominate Mark Beierl.

Nominee: Mark Beierl
Employer: EMC
Statement: Beside his work on Storperf, Mark was the main worker during the 
wiki migration. Here he showed his integrating
and collaboration abilities and his broad understanding through the different 
areas of OPNFV.
I believe it would be a great help to have him on the TSC.

Cheers,
Uli



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: 08 August 2016 08:21
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

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] Pharos Planning Week

[Morgan, Jack]

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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nThere are several issues that n
 eed input and focus. I’m scheduling a daily meeting for next week. I’l
 l be meeting at the same time and location each day to work through the ag
 enda below.  All are welcome to join any of these meetings and provide you
 r input. Pharos committers should attend as many meetings as they can. Tha
 nks in advance!\n\n\nGoToMeeting (6:00 am PST / 14:00 GMT)\nPlease join my
  meeting from your computer\, tablet or smartphone.\nhttps://global.gotome
 eting.com/join/349781141\n\nYou can also dial in using your phone.\nUnited
  States (Toll-free): 1 866 899 4679\nUnited States : +1 (312) 757-3117\n\n
 Access Code: 349-781-141\n\nMore phone numbers\nAustralia : +61 2 8355 103
 9\nAustria : +43 7 2088 1033\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (6
 47) 497-9379\nDenmark : +45 69 91 89 21\nFinland : +358 (0) 923 17 0555\nF
 rance : +33 (0) 170 950 585\nGermany : +49 (0) 692 5736 7301\nIreland : +3
 53 (0) 19 030 050\nItaly : +39 0 693 38 75 50\nNetherlands : +31 (0) 208 0
 80 208\nNew Zealand : +64 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +3
 4 911 82 9890\nSweden : +46 (0) 853 527 817\nSwitzerland : +41 (0) 435 016
 7 65\nUnited Kingdom : +44 (0) 330 221 0099\nFirst GoToMeeting? Try a test
  session: http://help.citrix.com/getready\n\n\nAgenda\n\nMonday:\n• 
   Pharos LAAS -  topics\no
discussion on scope of project\no   define milestones and roadm
 ap\n•   Pharos JIRA project clean up (link)\n\nTuesday:\n•   Pharos Specification\no   discussion current
  state and updates needed for Colorado release\n\nWednesday\n•   Pha
 ros Validator (link)\
 no   discussion on scope of project\no   define milestones and roa
 dmap\n\nThursday\n•   Pharos Dashboard - topics\no   discussion on scope of project\n
 o   define milestones and roadmap\n\nFriday\n•   Colorado Releas
 e (link)\no   git branching – final review\no   documentation – fina
 l review\n•   D release planning: Wiki and JIRA\
 n\n
RRULE:FREQ=WEEKLY;UNTIL=20160819T13Z;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR;WK
 ST=SU
SUMMARY;LANGUAGE=en-US:Pharos Planning Week
DTSTART;TZID=Pacific Standard Time:20160815T06
DTEND;TZID=Pacific Standard Time:20160815T07
UID:04008200E00074C5B7101A82E00800A51F19A6F3D101000
 01D9CF122929DF842A5845D63E9C5CE86
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160811T153519Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:946571232
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
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] [Plugfest] December Plugfest Hardware

[Jack Morgan]

  
  
Lincoln,
Intel will attend the next Plugfest. I've not thought through
the details yet but will try to prepare for Monday's meeting.
thanks


On 08/11/2016 07:39 AM, Lincoln Lavoie
  wrote:


  
  Hello All,


I'd like to get a feel for who is planning to participate
  in the December plugfest with hardware on site.  I've reached
  out to a number of individuals, but just to hit the wider
  audience, I'm pinging the mailing list as well.


If you are planning to participate in the plugfest, can you
  please respond (publicly or privately), so we can start to get
  a sense of the equipment availability / resources for the
  event.


Our next planning call is Monday, August 15, and I am
  planning to work on the scope of the event with the group. 
  I'll send out a more formal agenda for the call by the end of
  tomorrow.


If you have any questions, please let me know.


Cheers,
  Lincoln
  -- 
  

  

  

  ***
  
  Lincoln Lavoie
  
  Senior Engineer, Broadband Technologies
  
  
  
  
  www.iol.unh.edu
  
  21 Madbury Rd., Ste. 100, Durham, NH 03824
  Mobile: +1-603-674-2755
  
  lylav...@iol.unh.edu
  
  
  
  
  Ars sine scientia nihil est! -- Art without
science is nothing.
  
  Scientia sine ars est vacua! -- Science
without art is empty.
  ***
  

  

  

  

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



-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

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

[opnfv-tech-discuss] Fwd: [SPC Polestar WG] OPNFV Meeting TIme Suggestions

[Margaret Chiosi]

-- Forwarded message --
From: Margaret Chiosi 
Date: Thu, Aug 11, 2016 at 12:13 PM
Subject: [SPC Polestar WG] OPNFV Meeting TIme Suggestions
To: "[OPNFV SPC] (opnfv-strategic-plan-commit...@lists.opnfv.org)" <
opnfv-strategic-plan-commit...@lists.opnfv.org>


Folks: currently this group is meeting Every other Thursday at 11AM EST.
Let me know if folks from Europe or Asia would like a different time - and
which time they are suggesting. I could also rotate between two times which
make it convenient for 2 groups and not the other. Let me know. In the
meantime, look at the meeting notes and make comments on the IRC or wiki.
thanks.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release documentation

[HU, BIN]

Is the “/docs/configurationguide/*” directory gone? Where should the docs 
under “configurationguide” directory be put now?

Thanks
Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin
Sent: Thursday, August 11, 2016 4:03 AM
To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) 
; TSC OPNFV (opnfv-...@lists.opnfv.org) 
; Christopher Price 
Subject: [opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release 
documentation

Clarification,
All projects are expected to store the documentation in their own repositories.

The docs project will not create a composite document to pull all content 
together, this was hard to manage in Brahmaputra and generated a very high 
pressure on the toolchain.
Instead, the user guide, installation & configuration will only contain an 
introduction of each document referring to the projects documentation.

The structure (which is very simplified) should look as following,
/docs//scenario.description.rst
/docs/userguide/feature.usage.rst
/docs/installationprocedure/installation.instruction.rst

//Sofia

From: Sofia Wallin
Sent: den 10 augusti 2016 14:08
To: TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org);
 TSC OPNFV (opnfv-...@lists.opnfv.org)
Subject: Update release documentation [opnfvdocs] [opnfv-tech-discuss]

Hi everyone,

After reviewing the status for Colorado we have agreed that:
Feature projects should produce a ”user guide” for their feature according to: 
https://gerrit.opnfv.org/gerrit/#/c/18311/
Scenario’s should also have a brief description provided by scenario owners 
according to: https://gerrit.opnfv.org/gerrit/#/c/18311/

The installation procedures as discussed on the project call should be handled 
by the installer projects. Use the installation instruction template that was 
used in Brahmaputra together with input from the scenario owners and with links 
to the scenario description documents.

The docs team will continue to work on the overall Colorado documents 
(overview, installation and user guide) however these will link to the project 
documents rather than importing text directly.


Let me know if you have any questions.

BR,
Sofia together with the docs team



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

[opnfv-tech-discuss] TSC Committer At Large nomination: Jack Morgan

[Skerry, Brian J]

I'd like to nominate Jack Morgan:

* Nominee: Jack Morgan 
* Employer: Intel
* Jack is the PTL for Pharos and has been active in supporting multiple 
projects in our labs.  Since joining OPNFV last year he has been a key part of 
the Plugfest activities and has been chairing the INFRA working group meetings, 
coordinating between Pharos, Releng, Octopus, and Genesis.

Thanks,

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

Re: [opnfv-tech-discuss] TSC Committer At Large nomination: Jack Morgan

[Jack Morgan]

  
  
Thanks for the nomination as Committer At large. I accept the
nomination.


On 08/11/2016 10:00 AM, Skerry, Brian J
  wrote:


  
  
  
  
I'd like to nominate Jack Morgan:
 
* Nominee: Jack Morgan
  
* Employer: Intel
* Jack is the PTL for Pharos and has been
  active in supporting multiple projects in our labs.  Since
  joining OPNFV last year he has been a key part of the Plugfest
  activities and has been chairing the INFRA working group
  meetings, coordinating between Pharos, Releng, Octopus, and
  Genesis.
 
Thanks,
 
-- Brian
  
  
  
  
  ___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

___
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] December Plugfest Hardware

[Lincoln Lavoie]

Thanks Jack,

I assumed you (Intel) would be in the event, but it's always worth double
checking.

Cheers,
Lincoln

On Thu, Aug 11, 2016 at 11:36 AM, Jack Morgan  wrote:

> Lincoln,
>
> Intel will attend the next Plugfest. I've not thought through the details
> yet but will try to prepare for Monday's meeting. thanks
>
> On 08/11/2016 07:39 AM, Lincoln Lavoie wrote:
>
> Hello All,
>
> I'd like to get a feel for who is planning to participate in the December
> plugfest with hardware on site.  I've reached out to a number of
> individuals, but just to hit the wider audience, I'm pinging the mailing
> list as well.
>
> If you are planning to participate in the plugfest, can you please respond
> (publicly or privately), so we can start to get a sense of the equipment
> availability / resources for the event.
>
> Our next planning call is Monday, August 15, and I am planning to work on
> the scope of the event with the group.  I'll send out a more formal agenda
> for the call by the end of tomorrow.
>
> If you have any questions, please let me know.
>
> Cheers,
> Lincoln
> --
> 
> ***
> *Lincoln Lavoie*
> Senior Engineer, Broadband Technologies
>
> 
> www.iol.unh.edu
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> Mobile: +1-603-674-2755
> lylav...@iol.unh.edu
>    
> 
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> Scientia sine ars est vacua! -- Science without art is empty.
> 
> ***
>
>
> ___
> opnfv-tech-discuss mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
> --
> Jack Morgan
> OPNFV Pharos Intel Lab
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
***
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies


www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
   


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Plugfest Registration is now open

[Raymond Paik]

All,

The registration for the December Plugfest is now open and you can register
at https://www.regonline.com/OPNFVPlugfestDec2016

You can also find hotel and other information on the Plugfest Events page
at https://events.linuxfoundation.org/events/opnfv-plugfest

Thanks and let me know if you have any questions.

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] [Plugfest] December Plugfest Hardware

[Beierl, Mark]

Hey, Lincoln.

I saw your email and am just now getting a chance to respond.  EMC will attend 
and we also are working on some details around hardware.  I’ll be attending the 
Monday call too.

Regards,
Mark

Mark Beierl | Advisory Solutions Architect
Communication & Media Cloud – CTO Office
EMC Federation
+1 (613) 314-8106
@MarkBeierl

On Aug 11, 2016, at 1:14 PM, Lincoln Lavoie 
mailto:lylav...@iol.unh.edu>> wrote:

Thanks Jack,

I assumed you (Intel) would be in the event, but it's always worth double 
checking.

Cheers,
Lincoln

On Thu, Aug 11, 2016 at 11:36 AM, Jack Morgan 
mailto:jack.mor...@intel.com>> wrote:

Lincoln,

Intel will attend the next Plugfest. I've not thought through the details yet 
but will try to prepare for Monday's meeting. thanks

On 08/11/2016 07:39 AM, Lincoln Lavoie wrote:
Hello All,

I'd like to get a feel for who is planning to participate in the December 
plugfest with hardware on site.  I've reached out to a number of individuals, 
but just to hit the wider audience, I'm pinging the mailing list as well.

If you are planning to participate in the plugfest, can you please respond 
(publicly or privately), so we can start to get a sense of the equipment 
availability / resources for the event.

Our next planning call is Monday, August 15, and I am planning to work on the 
scope of the event with the group.  I'll send out a more formal agenda for the 
call by the end of tomorrow.

If you have any questions, please let me know.

Cheers,
Lincoln
--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]
  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png] 
   
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png] 


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***



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



--
Jack Morgan
OPNFV Pharos Intel Lab

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




--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]
  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png] 
   
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png] 


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
***
___
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] Opening nominations for the Committers-at-Large TSC elections

[Beierl, Mark]

I would like to thank both Uli and Al for the nominations.  I accept the 
nomination.

Regards,
Mark

Mark Beierl | Advisory Solutions Architect
Communication & Media Cloud – CTO Office
EMC Federation
+1 (613) 314-8106
@MarkBeierl

On Aug 11, 2016, at 10:52 AM, MORTON, ALFRED C (AL) 
mailto:acmor...@att.com>> wrote:

+1, and to complete my #action from the testperf meeting this morning:

Statement: Mark is recognized as strong contributor to the test community,
and since our community is a key part of OPNFV, it was agreed (today)
that we should make at least two nominations from among the testers
for the available seats. Mark is one of our nominees, along with Morgan.

regards,
Al


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ulrich Kleber
Sent: Thursday, August 11, 2016 9:58 AM
To: Carlos Goncalves; Raymond Paik; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Opening nominations for the 
Committers-at-Large TSC elections

Hi,

I would like to nominate Mark Beierl.

Nominee: Mark Beierl
Employer: EMC
Statement: Beside his work on Storperf, Mark was the main worker during the 
wiki migration. Here he showed his integrating
and collaboration abilities and his broad understanding through the different 
areas of OPNFV.
I believe it would be a great help to have him on the TSC.

Cheers,
Uli



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: 08 August 2016 08:21
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[Christopher Price]

Hi Ray,

I’d like to also nominate:

- Maryam Tahhan 
- Employer: Intel
Maryam has been PTL of the vSwitch perf project since the very early days of 
OPNFV.  She has been active across the testing areas of our community 
establishing best practices and leadership as an example for our community.  
Maryam would be a valuable member of the TSC with her experience working with 
open source communities and clear commitment and expertise in OPNFV and the NFV 
domain overall.

Cheers,
Chris

From:  on behalf of Raymond Paik 

Date: Monday 8 August 2016 at 08:21
To: TSC OPNFV , TECH-DISCUSS OPNFV 

Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

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] Opening nominations for the Committers-at-Large TSC elections

[Raymond Paik]

All,

I'd like to make a suggestion on the election...

We actually started this election early and as a lot of people are out on
vacation, I'd like to propose keeping the nomination period open for
another week.  The 3rd bullet on the wiki (
https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection)
talks about a week of "community debate & discussions" on
opnfv-tech-discuss, but I think it'd be more productive to open the
nomination for another week (discussions can still happen on the mailing
list).

We can definitely discuss this at the upcoming TSC call, but please let me
know if you have any questions or concerns.

Thanks,

Ray

On Wed, Aug 10, 2016 at 8:33 AM, Raymond Paik 
wrote:

> All,
>
> Just a quick reminder that the nomination period closes this Friday at 5pm
> Pacific Time.  Please send in your nominations or post self nominations at
> https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Larg
> e+TSC+Election+Self-Nominations
>
> Thanks,
>
> Ray
>
> On Sun, Aug 7, 2016 at 11:21 PM, Raymond Paik 
> wrote:
>
>> OPNFV Community:
>>
>> Based on feedback last week, the list of committers have been updated and
>> you can find the committers list at https://wiki.opnfv.org/disp
>> lay/DEV/OPNFV+Committers+List.
>>
>> Now, I'd like to open the nomination period for the Committers-at-Large
>> TSC elections.  As noted in the elections wiki page (
>> https://wiki.opnfv.org/display/DEV/Community+Election+Proce
>> dure#CommunityElectionProcedure-CommunityTSCmemberelection(
>> proposalpendingapproval), nominations can be either self-nominations or
>> anyone can nominate other committers. If a committer is nominated by
>> others, the nominee must accept the nomination for it to be valid.
>>
>> For self-nominations, I created a wiki page with a suggested template at
>> https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Larg
>> e+TSC+Election+Self-Nominations.  If you are interested in nominating
>> yourself, please add your nomination statements directly on the wiki page.
>>
>> If you'd like to nominate others, please send your nominations to
>> opnfv-tsc & opnfv-tech-discuss mailing lists so that your nominations can
>> be accepted (or declined) by the nominees on the mailing lists.
>>
>> I will close the nominations at 5pm Pacific Time on August 12th
>> (Friday).  Please let me know if you have any questions.
>>
>> 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] Opening nominations for the Committers-at-Large TSC elections

[Christopher Price]

Hi Ray,

 

Good catch, we should keep the nominations open until the published date to 
ensure we don’t miss anyone.  (Getting too efficient at these things.)

 

Given it will be a two-week nomination and discussion period it does make sense 
to simply move into the elections, let me bring that up on the TSC on Tuesday 
for any needed discussion and a decision.  For now, I guess at the minimum we 
should keep the nomination period open until the agreed and published date on 
the wiki.

 

/ Chris

 

From:  on behalf of Raymond Paik 

Date: Thursday 11 August 2016 at 19:45
To: TSC OPNFV , TECH-DISCUSS OPNFV 

Subject: Re: [opnfv-tech-discuss] Opening nominations for the 
Committers-at-Large TSC elections

 

All, 

 

I'd like to make a suggestion on the election...  

 

We actually started this election early and as a lot of people are out on 
vacation, I'd like to propose keeping the nomination period open for another 
week.  The 3rd bullet on the wiki 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection)
 talks about a week of "community debate & discussions" on opnfv-tech-discuss, 
but I think it'd be more productive to open the nomination for another week 
(discussions can still happen on the mailing list).

 

We can definitely discuss this at the upcoming TSC call, but please let me know 
if you have any questions or concerns.

 

Thanks, 

 

Ray

 

On Wed, Aug 10, 2016 at 8:33 AM, Raymond Paik  wrote:

All, 

 

Just a quick reminder that the nomination period closes this Friday at 5pm 
Pacific Time.  Please send in your nominations or post self nominations at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations

 

Thanks, 

 

Ray

 

On Sun, Aug 7, 2016 at 11:21 PM, Raymond Paik  wrote:

OPNFV Community:

 

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List. 

 

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

 

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.  

 

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

 

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

 

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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tsc] Opening nominations for the Committers-at-Large TSC elections

[Dave Neary]

Hi Ray,

In order to enable the start of discussions during the nomination
period, do you think it would be good to have a list of confirmed
nominees for election on the wiki, curated as new nominees are added?

I for one have lost track of how many nominations have been made, and I
don't know which nominations have been accepted (beyond those who
replied to the list).

Thanks,
Dave.

On 08/11/2016 01:45 PM, Raymond Paik wrote:
> All, 
> 
> I'd like to make a suggestion on the election...  
> 
> We actually started this election early and as a lot of people are out
> on vacation, I'd like to propose keeping the nomination period open for
> another week.  The 3rd bullet on the wiki
> (https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection)
> talks about a week of "community debate & discussions" on
> opnfv-tech-discuss, but I think it'd be more productive to open the
> nomination for another week (discussions can still happen on the mailing
> list).
> 
> We can definitely discuss this at the upcoming TSC call, but please let
> me know if you have any questions or concerns.
> 
> Thanks, 
> 
> Ray
> 
> On Wed, Aug 10, 2016 at 8:33 AM, Raymond Paik  > wrote:
> 
> All, 
> 
> Just a quick reminder that the nomination period closes this Friday
> at 5pm Pacific Time.  Please send in your nominations or post self
> nominations
> at 
> https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations
> 
> 
> 
> Thanks, 
> 
> Ray
> 
> On Sun, Aug 7, 2016 at 11:21 PM, Raymond Paik
> mailto:rp...@linuxfoundation.org>> wrote:
> 
> OPNFV Community:
> 
> Based on feedback last week, the list of committers have been
> updated and you can find the committers list
> at https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List
> . 
> 
> Now, I'd like to open the nomination period for the
> Committers-at-Large TSC elections.  As noted in the elections
> wiki page
> 
> (https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval)
> 
> ,
> nominations can be either self-nominations or anyone can
> nominate other committers. If a committer is nominated by
> others, the nominee must accept the nomination for it to be valid.
> 
> For self-nominations, I created a wiki page with a suggested
> template
> at 
> https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations
> 
> .
>  
> If you are interested in nominating yourself, please add your
> nomination statements directly on the wiki page.  
> 
> If you'd like to nominate others, please send your nominations
> to opnfv-tsc & opnfv-tech-discuss mailing lists so that your
> nominations can be accepted (or declined) by the nominees on the
> mailing lists.
> 
> I will close the nominations at 5pm Pacific Time on August 12th
> (Friday).  Please let me know if you have any questions.
> 
> Thanks, 
> 
> Ray
>   
> 
> 
> 
> 
> 
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
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-tsc] Opening nominations for the Committers-at-Large TSC elections

[Raymond Paik]

Dave,

Good point.  I'll create a wiki page (hopefully today) listing all the
accepted nominees.  I can then update it as we get more nominees/accepts.

Thanks,

Ray

On Thu, Aug 11, 2016 at 11:02 AM, Dave Neary  wrote:

> Hi Ray,
>
> In order to enable the start of discussions during the nomination
> period, do you think it would be good to have a list of confirmed
> nominees for election on the wiki, curated as new nominees are added?
>
> I for one have lost track of how many nominations have been made, and I
> don't know which nominations have been accepted (beyond those who
> replied to the list).
>
> Thanks,
> Dave.
>
> On 08/11/2016 01:45 PM, Raymond Paik wrote:
> > All,
> >
> > I'd like to make a suggestion on the election...
> >
> > We actually started this election early and as a lot of people are out
> > on vacation, I'd like to propose keeping the nomination period open for
> > another week.  The 3rd bullet on the wiki
> > (https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#
> CommunityElectionProcedure-CommunityTSCmemberelection)
> > talks about a week of "community debate & discussions" on
> > opnfv-tech-discuss, but I think it'd be more productive to open the
> > nomination for another week (discussions can still happen on the mailing
> > list).
> >
> > We can definitely discuss this at the upcoming TSC call, but please let
> > me know if you have any questions or concerns.
> >
> > Thanks,
> >
> > Ray
> >
> > On Wed, Aug 10, 2016 at 8:33 AM, Raymond Paik  > > wrote:
> >
> > All,
> >
> > Just a quick reminder that the nomination period closes this Friday
> > at 5pm Pacific Time.  Please send in your nominations or post self
> > nominations
> > at https://wiki.opnfv.org/display/DEV/2016+Commiters-at-
> Large+TSC+Election+Self-Nominations
> >  Large+TSC+Election+Self-Nominations>
> >
> > Thanks,
> >
> > Ray
> >
> > On Sun, Aug 7, 2016 at 11:21 PM, Raymond Paik
> > mailto:rp...@linuxfoundation.org>>
> wrote:
> >
> > OPNFV Community:
> >
> > Based on feedback last week, the list of committers have been
> > updated and you can find the committers list
> > at https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List
> > .
> >
> > Now, I'd like to open the nomination period for the
> > Committers-at-Large TSC elections.  As noted in the elections
> > wiki page
> > (https://wiki.opnfv.org/display/DEV/Community+
> Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(
> proposalpendingapproval)
> >  Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(
> proposalpendingapproval)>,
> > nominations can be either self-nominations or anyone can
> > nominate other committers. If a committer is nominated by
> > others, the nominee must accept the nomination for it to be
> valid.
> >
> > For self-nominations, I created a wiki page with a suggested
> > template
> > at https://wiki.opnfv.org/display/DEV/2016+Commiters-at-
> Large+TSC+Election+Self-Nominations
> >  Large+TSC+Election+Self-Nominations>.
> > If you are interested in nominating yourself, please add your
> > nomination statements directly on the wiki page.
> >
> > If you'd like to nominate others, please send your nominations
> > to opnfv-tsc & opnfv-tech-discuss mailing lists so that your
> > nominations can be accepted (or declined) by the nominees on the
> > mailing lists.
> >
> > I will close the nominations at 5pm Pacific Time on August 12th
> > (Friday).  Please let me know if you have any questions.
> >
> > Thanks,
> >
> > Ray
> >
> >
> >
> >
> >
> >
> > ___
> > opnfv-tsc mailing list
> > opnfv-...@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> >
>
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338
>
___
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-strategic-plan-committee] [SPC Polestar WG] OPNFV Meeting TIme Suggestions

[Min Yu]

Margaret,

Do you intend to send this to the tech-discuss mailing list too?

Here is the group's email address: opnfv-tech-discuss@lists.opnfv.org


--
Min Yu
Client Services Coordinator
The Linux Foundation
+1(530) 902-6464 (m)
m...@linuxfoundation.org
Skype: minyudecorah

On Thu, Aug 11, 2016 at 11:13 AM, Margaret Chiosi <
margaretchiosi.o...@gmail.com> wrote:

> Folks: currently this group is meeting Every other Thursday at 11AM EST.
> Let me know if folks from Europe or Asia would like a different time - and
> which time they are suggesting. I could also rotate between two times which
> make it convenient for 2 groups and not the other. Let me know. In the
> meantime, look at the meeting notes and make comments on the IRC or wiki.
> thanks.
>
> ___
> opnfv-strategic-plan-committee mailing list
> opnfv-strategic-plan-commit...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-strategic-plan-committee
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 8/12

[Tianhongbo]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Tianhongbo:MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Price:MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dave Neary
 :MAILTO:dne...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=marko.a.ku
 i...@nokia.com:MAILTO:marko.a.kui...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rautakumpu
 , Mika (Nokia - FI/Espoo)":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=sheng-ann.
 y...@ericsson.com:MAILTO:sheng-ann...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangjianyj
 y...@chinamobile.com:MAILTO:yangjian...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.jun3
 g...@zte.com.cn:MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="HU, BIN":MA
 ILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=lma@biigro
 up.cn:MAILTO:l...@biigroup.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tetsuya Na
 kamura:MAILTO:t.nakam...@cablelabs.com
DESCRIPTION;LANGUAGE=zh-CN:时间: 2016年8月12日星期五 22:00-23:00(UT
 C+08:00)北京，重庆，香港特别行政区，乌鲁木齐。\n\n注
 意: 以上 GMT 时差并不反映夏令时调整。\n\n*~*~*~*~*~*~*~*~*~
 *\n\nHi all:\n\nLet us discuss more about the dovetail.\n\n•   Weekl
 y on Friday at 1400-1500 UTC\n•   Gotomeeting Access\no   https:
 //global.gotomeeting.com/join/969604901\no   United States +1 (224) 50
 1-3318\no   Access Code: 458-547-813\n•   IRC channel\no
 #opnfv-meeting@ Freenode (Web Chat)\n\n\nFor more detail\, please refer to :\nhttps://wiki.opnf
 v.org/display/dovetail\n\nAgenda:\n1)  Test cases\n\nhttps://wiki.opnf
 v.org/pages/viewpage.action?pageId=6827269\n\n2)  Progress of SFC\, L3
 VPN and IPV6\n3)  Plan for the basic testing and other issues( IRC?).\
 n\nBest Regards\n\nhongbo\n\n
SUMMARY;LANGUAGE=zh-CN:[dovetail]dovetail weekly meeting 8/12
DTSTART;TZID=China Standard Time:20160812T22
DTEND;TZID=China Standard Time:20160812T23
UID:04008200E00074C5B7101A82E00830B0A4517AF4D101000
 0100049807D13A3F57D43B6155B9197868BED
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160812T012731Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-219379744
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] [opnfv-tsc] Opening nominations for the Committers-at-Large TSC elections

[Heather Kirksey]

Dave, I'm not sure what exactly you have in mind for "discussion" around
candidacies this election, but I would like to remind everyone that what
feels like open debate can, when applied to people, become problematic and
even abusive *very* quickly.

It's also easy for such discussion to devolve into politicking, and I think
we need look no further than the current US election cycle to see how badly
that can go.

Finally, let me say that if we do engage in any debate on various
candidates on tech-discuss, I will be monitoring those conversations
closely and I expect that nothing even resembling a violation of our code
of conduct will occur. We are building a good sense of community here at
OPNFV and these committer-at-large elections are meant to increase that,
not polarize it.

Heather



On Thu, Aug 11, 2016 at 11:04 AM, Raymond Paik 
wrote:

> Dave,
>
> Good point.  I'll create a wiki page (hopefully today) listing all the
> accepted nominees.  I can then update it as we get more nominees/accepts.
>
> Thanks,
>
> Ray
>
> On Thu, Aug 11, 2016 at 11:02 AM, Dave Neary  wrote:
>
>> Hi Ray,
>>
>> In order to enable the start of discussions during the nomination
>> period, do you think it would be good to have a list of confirmed
>> nominees for election on the wiki, curated as new nominees are added?
>>
>> I for one have lost track of how many nominations have been made, and I
>> don't know which nominations have been accepted (beyond those who
>> replied to the list).
>>
>> Thanks,
>> Dave.
>>
>> On 08/11/2016 01:45 PM, Raymond Paik wrote:
>> > All,
>> >
>> > I'd like to make a suggestion on the election...
>> >
>> > We actually started this election early and as a lot of people are out
>> > on vacation, I'd like to propose keeping the nomination period open for
>> > another week.  The 3rd bullet on the wiki
>> > (https://wiki.opnfv.org/display/DEV/Community+Election+
>> Procedure#CommunityElectionProcedure-CommunityTSCmemberelection)
>> > talks about a week of "community debate & discussions" on
>> > opnfv-tech-discuss, but I think it'd be more productive to open the
>> > nomination for another week (discussions can still happen on the mailing
>> > list).
>> >
>> > We can definitely discuss this at the upcoming TSC call, but please let
>> > me know if you have any questions or concerns.
>> >
>> > Thanks,
>> >
>> > Ray
>> >
>> > On Wed, Aug 10, 2016 at 8:33 AM, Raymond Paik <
>> rp...@linuxfoundation.org
>> > > wrote:
>> >
>> > All,
>> >
>> > Just a quick reminder that the nomination period closes this Friday
>> > at 5pm Pacific Time.  Please send in your nominations or post self
>> > nominations
>> > at https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+
>> TSC+Election+Self-Nominations
>> > > +TSC+Election+Self-Nominations>
>> >
>> > Thanks,
>> >
>> > Ray
>> >
>> > On Sun, Aug 7, 2016 at 11:21 PM, Raymond Paik
>> > mailto:rp...@linuxfoundation.org>>
>> wrote:
>> >
>> > OPNFV Community:
>> >
>> > Based on feedback last week, the list of committers have been
>> > updated and you can find the committers list
>> > at https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List
>> > .
>> >
>> > Now, I'd like to open the nomination period for the
>> > Committers-at-Large TSC elections.  As noted in the elections
>> > wiki page
>> > (https://wiki.opnfv.org/display/DEV/Community+Election+
>> Procedure#CommunityElectionProcedure-CommunityTSCmemberelect
>> ion(proposalpendingapproval)
>> > > Procedure#CommunityElectionProcedure-CommunityTSCmemberelect
>> ion(proposalpendingapproval)>,
>> > nominations can be either self-nominations or anyone can
>> > nominate other committers. If a committer is nominated by
>> > others, the nominee must accept the nomination for it to be
>> valid.
>> >
>> > For self-nominations, I created a wiki page with a suggested
>> > template
>> > at https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+
>> TSC+Election+Self-Nominations
>> > > +TSC+Election+Self-Nominations>.
>> > If you are interested in nominating yourself, please add your
>> > nomination statements directly on the wiki page.
>> >
>> > If you'd like to nominate others, please send your nominations
>> > to opnfv-tsc & opnfv-tech-discuss mailing lists so that your
>> > nominations can be accepted (or declined) by the nominees on the
>> > mailing lists.
>> >
>> > I will close the nominations at 5pm Pacific Time on August 12th
>> > (Friday).  Please let me know if you have any questions.
>> >
>> > Thanks,
>> >

Re: [opnfv-tech-discuss] Fwd: [SPC Polestar WG] OPNFV Meeting TIme Suggestions

[Yujun Zhang]

It is 11PM (1500UTC) in Shanghai, China. So I wonder if we could shift it
to an earlier timeslot but I can accept it if need be.

Because 1400UTC is already occupied by testperf meeting and 1300 UTC might
be too earlier for America.
--
Yujun

On Fri, Aug 12, 2016 at 12:14 AM Margaret Chiosi <
margaretchiosi.o...@gmail.com> wrote:

>
> -- Forwarded message --
> From: Margaret Chiosi 
> Date: Thu, Aug 11, 2016 at 12:13 PM
> Subject: [SPC Polestar WG] OPNFV Meeting TIme Suggestions
> To: "[OPNFV SPC] (opnfv-strategic-plan-commit...@lists.opnfv.org)" <
> opnfv-strategic-plan-commit...@lists.opnfv.org>
>
>
> Folks: currently this group is meeting Every other Thursday at 11AM EST.
> Let me know if folks from Europe or Asia would like a different time - and
> which time they are suggesting. I could also rotate between two times which
> make it convenient for 2 groups and not the other. Let me know. In the
> meantime, look at the meeting notes and make comments on the IRC or wiki.
> thanks.
>
> ___
> 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] [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

[Lijun (Matthew)]

Hi

Recently, I am running the test case in compass(Mitaka version), by running 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash
 it fails,

Also in the CI logs, if fails 
https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/190/consoleFull
 (although vm ssh timeoout, it is caused by port creation error)


It worked with Liberity version, with Mitaka it has some problems, 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n27

line 27 --port_security_enabled=False doesn't support now



https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n54
  line 54 the port creation status is DOWN, so the VM can't be created after 
this procedure.
@sridhar, do you have any ideas?


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

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[Lingli Deng]

Hi Ray,

I would like to nominate Qiao Fu from China Mobile, who has demonstrated her 
commitment to the community as PTL of the HA project, as a candidate of 
Committer-at-large election.

 

Thanks and Regards,

Lingli



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: 2016年8月8日 14:21
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

 

OPNFV Community:

 

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List. 

 

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

 

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.  

 

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

 

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

 

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] Wiki page for accepted nominees for the Committer-at-Large election

[Raymond Paik]

All,

Here's the wiki page that shows all accepted nominations.  I will be
updating the list as we get more accepts

https://wiki.opnfv.org/display/DEV/Accepted+Nominations+for+2016+Committer-at-Large+TSC+election


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] [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

[HU, BIN]

Matthew,

Thank you for letting us know. The failure of Line 27 (and 28) result in the 
failure of Line 54 (and 55).

We need to disable Security Groups in ML2 Setup first. See 
http://artifacts.opnfv.org/opnfvdocs/brahmaputra/docs/configguide/featureconfig-ipv6.html#id2,
 OPNFV-SEC-1, OPNFV-SEC-2 and OPNFV-SEC-3.

Can you double check the above settings in Mitaka deployment?

Thanks
Bin
From: Lijun (Matthew) [mailto:matthew.li...@huawei.com]
Sent: Thursday, August 11, 2016 6:59 PM
To: HU, BIN ; sridhar.gad...@redhat.com; Gaoliang (kubi) 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

Hi

Recently, I am running the test case in compass(Mitaka version), by running 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash
 it fails,

Also in the CI logs, if fails 
https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/190/consoleFull
 (although vm ssh timeoout, it is caused by port creation error)


It worked with Liberity version, with Mitaka it has some problems, 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n27

line 27 --port_security_enabled=False doesn't support now



https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n54
  line 54 the port creation status is DOWN, so the VM can't be created after 
this procedure.

@sridhar, do you have any ideas?


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

Re: [opnfv-tech-discuss] [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

[HU, BIN]

BTW, Matthew,

I checked Mitaka's docs, and it seems that they deprecated "security_group_api" 
in nova.conf in Mitaka (should still work though until Newton where it will be 
removed).

So another way is to change:


-  Line 27 and 28: remove the parameter "--port_security_enabled=False"

-  Line 54 and 55: add one more parameter "--no-security-groups"

Can you also try this?

Thanks
Bin

From: HU, BIN
Sent: Thursday, August 11, 2016 11:02 PM
To: 'Lijun (Matthew)' ; sridhar.gad...@redhat.com; 
Gaoliang (kubi) 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

Matthew,

Thank you for letting us know. The failure of Line 27 (and 28) result in the 
failure of Line 54 (and 55).

We need to disable Security Groups in ML2 Setup first. See 
http://artifacts.opnfv.org/opnfvdocs/brahmaputra/docs/configguide/featureconfig-ipv6.html#id2,
 OPNFV-SEC-1, OPNFV-SEC-2 and OPNFV-SEC-3.

Can you double check the above settings in Mitaka deployment?

Thanks
Bin
From: Lijun (Matthew) [mailto:matthew.li...@huawei.com]
Sent: Thursday, August 11, 2016 6:59 PM
To: HU, BIN mailto:bh5...@att.com>>; 
sridhar.gad...@redhat.com; Gaoliang (kubi) 
mailto:jean.gaoli...@huawei.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [ipv6][yardstick][mitaka] ipv6 test case failure with Mitaka

Hi

Recently, I am running the test case in compass(Mitaka version), by running 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash
 it fails,

Also in the CI logs, if fails 
https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/190/consoleFull
 (although vm ssh timeoout, it is caused by port creation error)


It worked with Liberity version, with Mitaka it has some problems, 
https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n27

line 27 --port_security_enabled=False doesn't support now



https://git.opnfv.org/cgit/yardstick/tree/yardstick/benchmark/scenarios/networking/ping6_setup.bash#n54
  line 54 the port creation status is DOWN, so the VM can't be created after 
this procedure.

@sridhar, do you have any ideas?


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

[opnfv-tech-discuss] [Bottlenecks] Minutes of Bottlenecks Weekly Meeting 20160811

[Yuyang (Gabriel)]

Hi All,

Please find the minutes of Thursday's bottlenecks meeting below and welcome to 
our next meeting!

Thanks,
Yang


Minutes of Bottlenecks Discussion on August 11, 2016

  *   Date and Time
 *   Thursday at 
0100-0200
 UTC, August 11, 2016
 *   Thursday at 0900-1000 Beijing, August 11, 2016
 *   Wednesday at 1800-1900 PDT, August 10, 2016
  *   Minutes
 *   Yang Yu
  *   Participants (8 peoples):
 *   Yang Yu
 *   Qi Liang
 *   Manuel Rebellon
 *   Lawrence Lamers
 *   4 Web users
Agenda:

  *   Bottlenecks Colorado Discuss  Yang
 *   Colorado Milestones
 *   Bottlenecks Colorado Testing Framework (Rubbos example)
  *   Proposals in Bottlenecks (Draft)Yang
 *   Goals and Scope (Draft)
 *   Proposals (Draft)
Discussion & Action Item
The meeting materials could be downloaded 
HERE.
 More information about our meeting could be found at Bottlenecks 
WIKI.

1. Bottlenecks Colorado Discuss

  *   Hongbo has another meeting to attend. So yang is delegated to organize 
the discussion
  *   Yang reports the discussion from the last Colorado release weekly meeting
 *   There will be a window period for stable branches and documents which 
lasts one week from August 15-22
 *   PTLs of each projects should determine their Milestone time that 
within this window period including Bottlenecks
 *   MS9:Stable branch created
*   Projects are branched from main
*   Commits are limited to critical issues
*   Commits must be cherry-picked
 *   MS10:Documentation completed
*   Updated
*   Reviewed
*   Verified
*   Committed to repo
  *   Yang briefly introduce the new Bottlenecks Colorado framework
 *   Bottleneck uses puppet to refactor the testing framework
*   Jumper server is the CI entrance for the Bottlenecks and will 
download all the codes
*   Environment and resources are configured and provided in the Jumper 
server
*   By taking Rubbos as an example, Yang introduce that the softwares 
that are needed in each nodes are downloaded and configured, and how puppet 
master/slave distributes. The Rubbos controller triggers the testing and the 
results will be sent to DB.

2. Proposals in Bottlenecks (Draft)

  *   Yang introduce the goals and scope of the proposals
 *   Goals of the proposals in Bottlenecks
*   Enhance interaction with other project
*   Add value to OPNFV Certification
*   Feedback development suggestions to upstream through OPNFV feature 
projects
*   Improve the performance of OPNFV reference platform
 *   Scope of the proposals in Bottlenecks
*   OPNFV Testing projects
*   OPNFV Feature projects
*   Modeling, Testing and Data analysis
*   Parameters choosing and Algorithms
  *   Yang gives an introduction about the development proposal in Bottlenecks
 *   Yang suggests that Bottlenecks communicates with testing and feature 
projects about the test cases, uses yardstick for testing and collects data 
from DB. Then the results will be analyzed and the bottlenecks will be 
classified into 5 categories. In addition, the bottlenecks analysis results 
will be feedback to each feature projects to output development suggestions to 
upstream projects.
 *   Manuel asks the connection between the feature/scenario from the 
feature projects and Bottlenecks project, and does Bottlenecks also act over 
those projects.
*   Yang explained that the proposal of Bottlenecks project classified 
the results into 5 categories and outputs the bottlenecks for each category. 
For each feature test case, the bottlenecks will be searching within the 5 
categories
 *   Manuel asks about the interconnection between the feature projects and 
Bottlenecks
*   Yang explained that the proposal of Bottlenecks expects that the 
feature projects should also participant the discussion for the test cases, 
target parameters, etc.
*   Yang also suggest to take the existing testing work in the 
community as advantages for Bottlenecks project.
  *   Yang volunteers to help organize the bottlenecks meeting and will discuss 
with Hongbo about the details of the proposals

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