[opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 18 Apr 2018 (ww62)

2018-04-17 Thread Rao, Sridhar
Agenda:

  1.  Development Update
  2.  CI Wiki Review.
  3.  VSPERF Workshop Requirements
  4.  Overview of Visibility Landscape - A Presentation.

Meeting minutes

  *   WW61 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-04-11-15.00.html
  *   WW60 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-04-04-15.00.html
  *   WW59 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-03-14-14.59.html

Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064





Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

2018-04-17 Thread Jessica Wagantall
Hi Thanh,

Thanks for organizing this. I agree is best to have the meeting next week
and then following ones
according to the plan.

Thanks!
Jess

On Tue, Apr 17, 2018 at 7:06 AM, Thanh Ha 
wrote:

> Hi Everyone,
>
> Firstly I'd like to say that I plan to start moving this conversation over
> to the mailing list. Please sign up to the new mailing list if you have no
> done so already as future correspondence will be done via the list.
>
> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>
> Also for those who use IRC our channel is #lf-docs @ irc.freenode.net
>
> With that said I've finalized the Doodle https://doodle.com/
> poll/dykpgubs3fvd2agw and it looks like Wednesdays at 5 PM UTC seems to
> be the winner. That is the following localized times if I'm not mistaken:
>
> 10 AM PT
> 1 PM ET
> 7 PM Stockholm
> 3 AM Brisbane
>
> (I believe Doodle will also show in your local time)
>
> We need to pick a date, Sofia had a previous suggestion that it be the 3rd
> week of the month but that would mean our first meeting is tomorrow which I
> think would be too little notice. I was thinking maybe we can have our
> first one next week instead and then following ones will be on the 3rd
> Wednesday of every month. Thoughts?
>
> If there's no strong opinions I will send out the invite tomorrow.
>
> Thanks,
> Thanh
>
>
> On Thu, Apr 12, 2018 at 4:30 PM, Thanh Ha 
> wrote:
>
>> Hi Everyone,
>>
>> I will pick a time next week. Just wanted to send a final reminder for
>> folks who haven't filled out the doodle yet and would like to participate.
>>
>> https://doodle.com/poll/dykpgubs3fvd2agw
>>
>> Also please join the new lf-docs mailing list as we'll use that for
>> future correspondence.
>>
>> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>>
>> Thanks,
>> Thanh
>>
>>
>> On Tue, Apr 10, 2018 at 2:49 PM, Thanh Ha 
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> I have acquired a mailing list for us to use moving forward. Please
>>> subscribe to this one:
>>>
>>> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>>>
>>> I have been told it will eventually migrate to groups.io but the
>>> transition will be seamless for us so we can start using the mailman list
>>> for now. I have also added the list to cc so this should be officially the
>>> first email on the list.
>>>
>>> Thanks,
>>> Thanh
>>>
>>>
>>> On Thu, Apr 5, 2018 at 7:26 PM, Thanh Ha 
>>> wrote:
>>>
 On Thu, Apr 5, 2018 at 6:03 PM, Thanh Ha 
 wrote:

> Hi Everyone,
>
> I believe I've included everyone who has indicated they were
> interested in cross community docs efforts. If you are not interested feel
> free to mute this thread.
>
> I've tried to include community mailing lists where existing to reach
> hopefully the right audience for this email. If anyone knows of folks who
> should be included please feel free to add them to this thread.
>
> At ONS we few of us from the ODL, OPNFV, and ONAP communities got
> together to discuss some cross community documentation efforts we've been
> pushing. We discussed lfdocs [0][1] and lfdocs-conf [2][3] projects who's
> purpose is to enable projects to easily share common configuration as well
> as create common documentation that projects can link to using
> intersphinx linking rather than rewriting their own.
>
> One of the things that came out of the meeting was that it would be
> good to create a cross-project-docs community so that we can ask questions
> and share ideas since all of us are using very similar tooling to build 
> our
> docs.
>
> For a start I've created an IRC channel #lf-docs @ irc.freenode.net
> which I hope folks will join and discuss docs related things in. It could
> be a valuable resource rather than all of us hanging in our own small docs
> communities I'm sure we are all understaffed as it is.
>
> We should setup a mailing list somewhere, I'll work with LF to figure
> out where the best place for such a list is such that it is not specific 
> to
> any project.
>
> Also there was discussion about setting up some kind of regular
> meeting maybe once a month where we can all get together and sync up to
> share any ideas we have. I think there are 2 things we need to figure out
> together:
>
> 1. How often is the right amount as to not overload everyone with
> meetings but give us time to get together?
> 2. What is the best time for the meeting?
>
> For 2 I've created a doodle poll please ignore the dates as we are
> only interested in finding out during any given week which times are
> generally good for folks. Please respond with the times that are okay with
> you and we'll try to pick a time that is good for the most 

Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

2018-04-17 Thread Charles La Voy
+1

~Charles

On Tue, Apr 17, 2018 at 1:24 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Hi Thanh,
>
> Thanks for organizing this. I agree is best to have the meeting next week
> and then following ones
> according to the plan.
>
> Thanks!
> Jess
>
> On Tue, Apr 17, 2018 at 7:06 AM, Thanh Ha 
> wrote:
>
>> Hi Everyone,
>>
>> Firstly I'd like to say that I plan to start moving this conversation
>> over to the mailing list. Please sign up to the new mailing list if you
>> have no done so already as future correspondence will be done via the list.
>>
>> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>>
>> Also for those who use IRC our channel is #lf-docs @ irc.freenode.net
>>
>> With that said I've finalized the Doodle https://doodle.com/poll
>> /dykpgubs3fvd2agw and it looks like Wednesdays at 5 PM UTC seems to be
>> the winner. That is the following localized times if I'm not mistaken:
>>
>> 10 AM PT
>> 1 PM ET
>> 7 PM Stockholm
>> 3 AM Brisbane
>>
>> (I believe Doodle will also show in your local time)
>>
>> We need to pick a date, Sofia had a previous suggestion that it be the
>> 3rd week of the month but that would mean our first meeting is tomorrow
>> which I think would be too little notice. I was thinking maybe we can have
>> our first one next week instead and then following ones will be on the 3rd
>> Wednesday of every month. Thoughts?
>>
>> If there's no strong opinions I will send out the invite tomorrow.
>>
>> Thanks,
>> Thanh
>>
>>
>> On Thu, Apr 12, 2018 at 4:30 PM, Thanh Ha 
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> I will pick a time next week. Just wanted to send a final reminder for
>>> folks who haven't filled out the doodle yet and would like to participate.
>>>
>>> https://doodle.com/poll/dykpgubs3fvd2agw
>>>
>>> Also please join the new lf-docs mailing list as we'll use that for
>>> future correspondence.
>>>
>>> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>>>
>>> Thanks,
>>> Thanh
>>>
>>>
>>> On Tue, Apr 10, 2018 at 2:49 PM, Thanh Ha 
>>> wrote:
>>>
 Hi Everyone,

 I have acquired a mailing list for us to use moving forward. Please
 subscribe to this one:

 https://lists.linuxfoundation.org/mailman/listinfo/lf-docs

 I have been told it will eventually migrate to groups.io but the
 transition will be seamless for us so we can start using the mailman list
 for now. I have also added the list to cc so this should be officially the
 first email on the list.

 Thanks,
 Thanh


 On Thu, Apr 5, 2018 at 7:26 PM, Thanh Ha 
 wrote:

> On Thu, Apr 5, 2018 at 6:03 PM, Thanh Ha  > wrote:
>
>> Hi Everyone,
>>
>> I believe I've included everyone who has indicated they were
>> interested in cross community docs efforts. If you are not interested 
>> feel
>> free to mute this thread.
>>
>> I've tried to include community mailing lists where existing to reach
>> hopefully the right audience for this email. If anyone knows of folks who
>> should be included please feel free to add them to this thread.
>>
>> At ONS we few of us from the ODL, OPNFV, and ONAP communities got
>> together to discuss some cross community documentation efforts we've been
>> pushing. We discussed lfdocs [0][1] and lfdocs-conf [2][3] projects who's
>> purpose is to enable projects to easily share common configuration as 
>> well
>> as create common documentation that projects can link to using
>> intersphinx linking rather than rewriting their own.
>>
>> One of the things that came out of the meeting was that it would be
>> good to create a cross-project-docs community so that we can ask 
>> questions
>> and share ideas since all of us are using very similar tooling to build 
>> our
>> docs.
>>
>> For a start I've created an IRC channel #lf-docs @ irc.freenode.net
>> which I hope folks will join and discuss docs related things in. It could
>> be a valuable resource rather than all of us hanging in our own small 
>> docs
>> communities I'm sure we are all understaffed as it is.
>>
>> We should setup a mailing list somewhere, I'll work with LF to figure
>> out where the best place for such a list is such that it is not specific 
>> to
>> any project.
>>
>> Also there was discussion about setting up some kind of regular
>> meeting maybe once a month where we can all get together and sync up to
>> share any ideas we have. I think there are 2 things we need to figure out
>> together:
>>
>> 1. How often is the right amount as to not overload everyone with
>> meetings but give us time to get together?
>> 2. What is the best time for the meeting?
>>
>> For 2 

Re: [opnfv-tech-discuss] [compass] Virtual install on single node

2018-04-17 Thread wutianwei
Hi Mark,

If you have a single node, you could try the virtual deployment quick start, 
more information refer to the wiki page[1].
When virtual deployment, there are no requirement about multiple physical 
networks, but need access to Internet.
btw, it is necessary to launch VMs,  and each VM need 8vCPU and 16 GB memory as 
default.
The ha scenarios need 5 VMs, and the noha scenarios need 2 VMs. So the single 
node need a powerful performance.

[1] 
https://wiki.opnfv.org/display/compass4nfv/Containerized+Compass#ContainerizedCompass-QuickStart:

Thanks,
Tianwei Wu
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Beierl, Mark
发送时间: 2018年4月17日 22:17
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [compass] Virtual install on single node

Hello,

What are the requirements for deploying compass in a virtual environment.  I am 
trying to use the LaaS pods, and I only have one IP address for management.  
Therefore, there is no provider network.  Can I just create a non-routed 
interface on one of the unused NICs, or do I need to have multiple physical 
networks in place?  Alternatively, should I create a VM with the networks in 
place and use that for all the deployments?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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


[opnfv-tech-discuss] Planning for Plugtest //RE: Guideline for participants //RE: Discussion about Fraser Plugfest/Plugtest from Testperf

2018-04-17 Thread Yuyang (Gabriel)
Hi,

First, here are some updates about OPNFV Testperf participating ETSI plugtest.
To my knowledge, Dovetail and Bottlenecks projects has already signed up for 
the plugtest (I see @Trevor also registered, is VSPERF planning to join?).
It is a very good news that we are actually trying to find out ways of 
cooperated testing with mutual benefits.

As a matter of fact, there are NS, VNF, MANO, VIM, HW and TOOLS categories 
for plugtest participants. In my mind, Dovetail and Bottlenecks better fit in 
TOOLS category.
In addition, some deadlines of the ETSI plugtest will be end of this month. So 
I suggest we start to make our plans accordingly.

As Pierre mentioned before, we should either provide interoperability test 
cases or have a separate track in ETSI plugtest, i.e., Dovetail track. In the 
meanwhile, I would like to explore more options/values here (Correct me if 
there is anything inappropriate).
For example, in a interoperability test session, we could run some of Dovetail 
test cases (mostly functest and yardstick tests) at the beginning and in the 
end of the test to validate if the platforms behave consistently during 
interoperations. It might be able to help improve the test passing rate or 
reduce the testing efforts (we could verify if Dovetail can do this during 
pre-testing).
As another example, we might be able to run optional tests during the 
Dovetail/Separate track as experiment testing, e.g, Bottleneks tests, VSPERF 
tests, etc.
Moreover, free style tests (after each 2h interoperability session) are also 
beneficial for the maturity of both SUTs and testing tools/cases which in turn 
improves the overall KPIs in the next testing activities.

I believe we will find/develop more common interests/plans that will benefit us 
in either short term or long term. If you have any other suggestion/comment, 
please feel free to add.
It would be better we can have a more concrete/practical proposal before/in 
this week's Testperf meeting based on our email discussion.
And I hope, this time, we could build our reputations and prove our values 
bi-directionally!

Please also find the following in case you want to add anything now
https://etherpad.opnfv.org/p/testperf_plugtest_plugfest_fraser


Thanks,
Gabriel


From: pierre.ly...@keysight.com [mailto:pierre.ly...@keysight.com]
Sent: Wednesday, April 04, 2018 10:39 PM
To: Yuyang (Gabriel) 
Cc: test...@lists.opnfv.org; ross.b.bratt...@intel.com; 
trevor.coo...@intel.com; acmor...@att.com; georg.k...@ericsson.com; 
tim.irn...@ericsson.com; ahot...@cisco.com; mark.bei...@emc.com; 
cedric.oliv...@orange.com
Subject: Re: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hello all,

First: looks like I am not subscribed to the test-wg list, so my last email 
bounced back to me. I didn’t find it on the OPNFV mailing lists site….can 
someone please subscribe me to that? New email: 
pierre.ly...@keysight.com

I spoke with Silvia Almagia, the Plugtest organizer at ETSI.


  *   I told her about the plan to brainstorm in the community which scenarios 
(features) could be brought to the Plugtest. It will be like I described: each 
scenario would be listed as a separate platform for scheduling purposes.
  *   There is no formal process to insert test cases directly into the test 
plan. It’s done by suggesting and discussing it on the Plugtest email list, and 
then discussing it during the weekly meeting. There are people who will help to 
format it correctly, etc.
 *   In order to do this, you need to be registered to the Plugtest.
 *   The test case should involve interoperability. That’s the goal of the 
Plugtest, so it should involve the three functional blocks: Platform 
(NFVI+VIM), MANO and VNF(s)
 *   If it doesn’t meet the criteria above, it can still be done in a 
separate track
  *   Dovetail
 *   We can include a separate (optional) track to have Dovetail testing at 
the Plugtest. I can introduce it to the team at a weekly meeting, and then we 
can start planning it. This would likely involve finding out who of the 
platform vendors would like to attempt it

The most important point: time is getting critical. If a VPN connection to HIVE 
is necessary, it takes a bit of time. Plus there is pre-testing to be done 
between now and the Plugtest event itself. We really need to get moving with 
this.


Best Regards,

Pierre

***Please note the new email and phone number***
Pierre Lynch
Lead Technologist
Ixia Solutions Group
Keysight Technologies
M: +19193788248
pierre.ly...@keysight.com


From: Pierre Lynch 

[opnfv-tech-discuss] 答复: [release][gambia] Intent to Participate in theOPNFV Gambia Release

2018-04-17 Thread shang.xiaodong
HI, David.






Parser will participate in the OPNFV Gambia Release. and






1. We intend to follow the traditional track.
















尚小冬 shangxiaodong















原始邮件



发件人:DavidMcBride 
收件人:TECH-DISCUSS OPNFV opnfv-project-leads 

抄送人:TSC OPNFV 
日 期 :2018年04月13日 06:37
主 题 :[opnfv-tech-discuss] [release][gambia] Intent to Participate in theOPNFV 
Gambia Release


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


Team,

Tomorrow (April 13) marks the opening of the intent-to-participate window for 
the Gambia release (i.e. MS0).  Please find the procedure here.  The window 
closes as of MS1 on May 11.


NEW FOR GAMBIA. PLEASE READ CAREFULLY.

As you probably know by now, we are supporting two release tracks for Gambia: 
1) traditional (i.e., the process we've been using) and 2) continuous delivery 
(as implemented by XCI and Apex).  So, in addition to the usual procedure found 
in the link above.  Please let me know which release track you intend to 
participate in by including one of the following statements in your intent to 
participate notification:

We intend to follow the traditional track.


We intend to follow the continuous delivery track

We intend to follow both the traditional track and the continuous delivery track



Also, please remember that if you are planning a new project for the Gambia 
release, you have two weeks to submit your proposal to the TSC and still have 
time to be approved and to join the release before the intent-to-participate 
window closes.


Let me know if you have questions.  Thanks.

David
-- 




David McBride
Release Manager, OPNFV

Mobile: +1.805.276.8018

Email/Google Talk: dmcbr...@linuxfoundation.org

Skype: davidjmcbride1

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


Re: [opnfv-tech-discuss] [barometer] Weekly Meeting Agenda 03-04-2018

2018-04-17 Thread Yuki Kasuya

Hi Barometer Team,

At this meeting, Tomo introduced DMA architecture and start the 
discussion to integrate a part of DMA function as Barometer local agent. 
Below is the discussion point of local agent.

https://etherpad.opnfv.org/p/barometer-localagent

If you have any use cases, implementation idea and feature, could you 
add your comment?


Best regards,
Yuki

On 4/3/18 02:42, Aaron Smith wrote:

Hi All,

Items for this week

  * ONS Summit Recap
  * DMA Project Presentation
  * Discussion of DMA project for possible inclusion in Barometer
  * Development Updates

Please feel free to bring additional items to the meeting.

Aaron

--

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat



314 Littleton Rd, Westford, MA 01886

aasm...@redhat.com M: 617.877.4814







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



--
-
KDDI Research, Inc.
Integrated Core Network Control
And Management Laboratory
Yuki Kasuya
yu-kas...@kddilabs.jp
+81 80 9048 8405
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [release][fraser] Fraser release date changed to April 27

2018-04-17 Thread David McBride
Team,

Today, the TSC approved a change to the release date for Fraser 6.0.  This
does not affect Fraser 6.1, 6.2, or the Gambia release.

Milestones next week:

   -
   - MS8 - complete formal testing - April 24
   - MS9 - complete final documentation - April 25
   - MS10 - JIRA cleanup - April 26
   - MS11 - technical release - April 27
   - Download page goes live - May 1

Let me know if you have any questions.

David

-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [dovetail] agenda for weekly meeting - 2018-04-18

2018-04-17 Thread Georg Kunz
Hi all,

This is the preliminary agenda for this week's Dovetail call:


  *   Review release plan proposal for OVP 2018.08 release
  *   Additional test case candidates in Fraser
 *   https://wiki.opnfv.org/display/SWREL/Fraser+Release+Key+Updates
 *   Functest
*   OpenStack
   *   neutron_trunk
   *   patrole
   *   juju_epc
*   Kubernetes
   *   k8s_smoke
   *   k8s_conformance
   *   stor4nfv
   *   clover
 *   Yardstick
*   OpenStack
   *   HA test cases
  *   restructuring and renaming of test cases
  *   Framework refactoring

Meeting Info

  *   Weekly Technical Discussion Wednesday at 14:00-15:00 UTC (7:00-8:00AM 
Pacific Daylight Time)
  *   IRC channel: IRC channel: #opnfv-dovetail@ Freenode (Web 
Chat)
  *   https://zoom.us/j/2362828999
  *   IRC Meeting Logs: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-dovetail/
Best regards
Georg
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [OVN4NFV] Weekly Meeting (17th April 2018)

2018-04-17 Thread Trinath Somanchi
Minutes -
http://ircbot.wl.linuxfoundation.org/meetings/ovn4nfv-meeting/2018/ovn4nfv-meeting.2018-04-17-16.30.html


On Tue, Apr 17, 2018 at 11:51 AM, Trinath Somanchi 
wrote:

> Hi OVN4NFV team-
>
> Please find the agenda for today'weekly meeting -  at
> https://wiki.opnfv.org/display/OV/Meeting+Agenda
>
> Also, please feel free to add topics if you find interesting.
>
>
> /Trinath Somanchi.
>
>
___
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] Summary of Weekly Technical Community Discussion Thursday April 12, 2018

2018-04-17 Thread Julien
Hi Bin,

Can you send me the model files in ONAP which can be used in Pharos?



HU, BIN 于2018年4月12日周四 下午6:50写道:

> Hello community,
>
>
>
> Thank you all for attending the technical discussion today.
>
>
>
> Today, we discussed Fraser Release Checkpoint led by David McBride
> . David will ask PTLs to report
> most recent status on Monday 4/16. And TSC will discuss and make
> “go”/”no-go” decision based on the information from David.
>
>
>
> We then discussed Pharos 2.0 proposal by Julien
> . Bin and Julien will sync up
> in terms of the infrastructure resource model in ONAP and the Pharos spec
> in OPNFV.
>
>
>
> For more details, please refer to the meeting minutes page [1], which
> includes attendees list and IRC log [2].
>
>
>
> On April 19th next week, we will discuss:
>
> -  A new project proposal Capstone
> 
> by Jing Lu .
>
> -  Test Framework Capability to Conduct Self-Test against a
> Known-Good DUT by Cedric Ollivier
> .
>
>
>
> Thanks
>
> Bin
>
>
>
> [1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20180412
>
> [2]
> http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-12-13.00.html
>
>
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [compass] Virtual install on single node

2018-04-17 Thread Beierl, Mark
Hello,

What are the requirements for deploying compass in a virtual environment.  I am 
trying to use the LaaS pods, and I only have one IP address for management.  
Therefore, there is no provider network.  Can I just create a non-routed 
interface on one of the unused NICs, or do I need to have multiple physical 
networks in place?  Alternatively, should I create a VM with the networks in 
place and use that for all the deployments?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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


Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

2018-04-17 Thread Thanh Ha
Hi Everyone,

Firstly I'd like to say that I plan to start moving this conversation over
to the mailing list. Please sign up to the new mailing list if you have no
done so already as future correspondence will be done via the list.

https://lists.linuxfoundation.org/mailman/listinfo/lf-docs

Also for those who use IRC our channel is #lf-docs @ irc.freenode.net

With that said I've finalized the Doodle
https://doodle.com/poll/dykpgubs3fvd2agw and it looks like Wednesdays at 5
PM UTC seems to be the winner. That is the following localized times if I'm
not mistaken:

10 AM PT
1 PM ET
7 PM Stockholm
3 AM Brisbane

(I believe Doodle will also show in your local time)

We need to pick a date, Sofia had a previous suggestion that it be the 3rd
week of the month but that would mean our first meeting is tomorrow which I
think would be too little notice. I was thinking maybe we can have our
first one next week instead and then following ones will be on the 3rd
Wednesday of every month. Thoughts?

If there's no strong opinions I will send out the invite tomorrow.

Thanks,
Thanh


On Thu, Apr 12, 2018 at 4:30 PM, Thanh Ha 
wrote:

> Hi Everyone,
>
> I will pick a time next week. Just wanted to send a final reminder for
> folks who haven't filled out the doodle yet and would like to participate.
>
> https://doodle.com/poll/dykpgubs3fvd2agw
>
> Also please join the new lf-docs mailing list as we'll use that for future
> correspondence.
>
> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>
> Thanks,
> Thanh
>
>
> On Tue, Apr 10, 2018 at 2:49 PM, Thanh Ha 
> wrote:
>
>> Hi Everyone,
>>
>> I have acquired a mailing list for us to use moving forward. Please
>> subscribe to this one:
>>
>> https://lists.linuxfoundation.org/mailman/listinfo/lf-docs
>>
>> I have been told it will eventually migrate to groups.io but the
>> transition will be seamless for us so we can start using the mailman list
>> for now. I have also added the list to cc so this should be officially the
>> first email on the list.
>>
>> Thanks,
>> Thanh
>>
>>
>> On Thu, Apr 5, 2018 at 7:26 PM, Thanh Ha 
>> wrote:
>>
>>> On Thu, Apr 5, 2018 at 6:03 PM, Thanh Ha 
>>> wrote:
>>>
 Hi Everyone,

 I believe I've included everyone who has indicated they were interested
 in cross community docs efforts. If you are not interested feel free to
 mute this thread.

 I've tried to include community mailing lists where existing to reach
 hopefully the right audience for this email. If anyone knows of folks who
 should be included please feel free to add them to this thread.

 At ONS we few of us from the ODL, OPNFV, and ONAP communities got
 together to discuss some cross community documentation efforts we've been
 pushing. We discussed lfdocs [0][1] and lfdocs-conf [2][3] projects who's
 purpose is to enable projects to easily share common configuration as well
 as create common documentation that projects can link to using
 intersphinx linking rather than rewriting their own.

 One of the things that came out of the meeting was that it would be
 good to create a cross-project-docs community so that we can ask questions
 and share ideas since all of us are using very similar tooling to build our
 docs.

 For a start I've created an IRC channel #lf-docs @ irc.freenode.net
 which I hope folks will join and discuss docs related things in. It could
 be a valuable resource rather than all of us hanging in our own small docs
 communities I'm sure we are all understaffed as it is.

 We should setup a mailing list somewhere, I'll work with LF to figure
 out where the best place for such a list is such that it is not specific to
 any project.

 Also there was discussion about setting up some kind of regular meeting
 maybe once a month where we can all get together and sync up to share any
 ideas we have. I think there are 2 things we need to figure out together:

 1. How often is the right amount as to not overload everyone with
 meetings but give us time to get together?
 2. What is the best time for the meeting?

 For 2 I've created a doodle poll please ignore the dates as we are only
 interested in finding out during any given week which times are generally
 good for folks. Please respond with the times that are okay with you and
 we'll try to pick a time that is good for the most people.

 https://doodle.com/poll/dykpgubs3fvd2agw

 Regards,
 Thanh

 [0] http://docs.releng.linuxfoundation.org/en/latest/
 [1] https://gerrit.linuxfoundation.org/infra/#/admin/project
 s/releng/docs
 [2] http://docs.releng.linuxfoundation.org/projects/lfdocs-c
 onf/en/latest/index.html
 [3] 

Re: [opnfv-tech-discuss] Gerrit Reviewers Plugin

2018-04-17 Thread Georg Kunz
Hi Trevor,

I like the idea. From a Dovetail perspective, we have already created a group 
in Gerrit some time ago to simplify the process of adding all reviewers to a 
patch. Automating this process is even better. So, once the plugin is 
installed, we would make use of it.

Best regards
Georg


> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On Behalf Of Trevor Bramwell
> Sent: Tuesday, April 17, 2018 1:33 AM
> To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> Cc: infra...@lists.opnfv.org
> Subject: [opnfv-tech-discuss] Gerrit Reviewers Plugin
> 
> Hi All,
> 
> The XCI team requested the gerrit-reviewers[1] plugin be installed on the
> OPNFV Gerrit server, and this morning the Infra-WG agreed[2] to the
> request. I wanted to give some context on what the plugin does and provide
> time to hear any concerns or feedback at the next TSC meeting.
> 
> Simply put: gerrit-reviewers plugin allows you to automatically add reviewers
> to patchsets.
> 
> This is configured on a per-project basis through a 'reviewers.config'
> file. As projects don't have access to where this file is stored, they'll 
> need to
> send a request to helpd...@opnfv.org in order to have the configuration
> added.
> 
> For example, for the releng-xci project this file would look like:
> 
>   [filter "*"]
> reviewer = xci
> 
> 'xci' here is a group defined in Gerrit, and everyone in the xci group would
> automatically be added to any new patches created in the releng-xci repo.
> 
> Something else the plugin allows is for defining a 'reviewers.config'
> file in the All-Projects repo, which gets inheritied to every project.
> 
> This would all us to do something like:
> 
>   [filter "file:^docs/.*"]
> reviewer = docs-reviewers
> 
> Where changes to any projects docs would automatically have a docs-
> reviewers group added to the patchset. I'm not proposing this idea, just
> giving an example of one way we could take advantage of it.
> 
> One issue currently with the plugin is that it doesn't allow for using LDAP
> groups. This means each project that would like to use it will also need to
> have a corresponding group created for them. We're (the LF Releng team) is
> looking at ways we might automate creating these groups, but for now
> they'd have been be manually created.
> 
> Our plan is to install this plugin after the intial Fraser release as it will 
> require a
> brief restart to Gerrit.
> 
> Please reply if you have concerns or questions or bring them to next TSC
> meeting.
> 
> Regards,
> Trevor Bramwell
> 
> [1]
> https://gerrit.googlesource.com/plugins/reviewers/+doc/master/src/main/r
> esources/Documentation/config.md
> [2] http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-
> meeting.2018-04-16-14.58.html
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [Bottlenecks] Weekly Call

2018-04-17 Thread Yuyang (Gabriel)
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia 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=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Brattain,
  Ross B'":MAILTO:ross.b.bratt...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'S, Deepak
 '":MAILTO:deepa...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Rutuja Su
 rve':MAILTO:rutuja.r.su...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=AMIT KUMAR
  JAISWAL:MAILTO:amitkumarj...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Manuel Reb
 ellon:MAILTO:mrebel...@sandvine.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangyaogua
 ng (A):MAILTO:sunshine.w...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Liyin (Ace
 ):MAILTO:liyi...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Manoj Nir
 ania':MAILTO:manojnira...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shubham A
 garwal':MAILTO:shubham.agarwal.co...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Limingjian
 g (Rex):MAILTO:limingji...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenjianku
 n (JackChan):MAILTO:chenjiank...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Bernier, 
 Daniel'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jose Ange
 l Lausuch':MAILTO:jalaus...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Anubhav G
 uleria':MAILTO:anugule...@grads.cds.iisc.ac.in
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ray Wong'
 :MAILTO:ray.w...@deltaww.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Nicolas B
 outhors':MAILTO:nicolas.bouth...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sun, Jimi
 ng'":MAILTO:jiming@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Cooper, T
 revor'":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Carlos Br
 avo':MAILTO:carlos.br...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Ramia, Ka
 nnan Babu'":MAILTO:kannan.babu.ra...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Wang, Sha
 ne'":MAILTO:shane.w...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tim Irnic
 h':MAILTO:tim.irn...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ken Gray 
 (kegray)':MAILTO:keg...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Seiler, G
 lenn'":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Perala, T
 imo (Nokia - FI/Espoo)'":MAILTO:timo.per...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ahmed Elb
 ornou (amaged)':MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Piyush Sa
 rwal':MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Reddy, Ra
 ghuveer'":MAILTO:raghuveer.re...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='최강일
 ':MAILTO:forerun...@etri.re.kr
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Kevin Gla
 vin':MAILTO:kevin.gla...@riverbed.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 

Re: [opnfv-tech-discuss] [JOID] Virtual installation

2018-04-17 Thread Trinath Somanchi
Hi Mark-

Please find JOID documentation at https://wiki.opnfv.org/display/joid/JOID+Home

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Monday, April 16, 2018 9:14 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [JOID] Virtual installation

Hello,

I'm trying to install JOID in one of the OPNFV LaaS servers.  I cannot seem to 
find documentation on how to do a virtual deployment, and was wondering if 
anyone can point me in the right direction.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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


[opnfv-tech-discuss] [OVN4NFV] Weekly Meeting (17th April 2018)

2018-04-17 Thread Trinath Somanchi
 Hi OVN4NFV team-

Please find the agenda for today'weekly meeting -  at
https://wiki.opnfv.org/display/OV/Meeting+Agenda

Also, please feel free to add topics if you find interesting.


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