[opnfv-tech-discuss] [announce] No Technical Community meeting this week

[Raymond Paik]

All,

I don't believe there are any topics for this week so wanted to let
everyone know that there will be no Technical Community meeting this week
(I'm helping Bin while he's on vacation for 2 weeks).  If you have any
topics you want to suggest for next week (July 20th) please send them to
me...

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] [Bottlenecks] Minutes of Bottlenecks Discussion on July 13, 2017

[Yuyang (Gabriel)]

Minutes of Bottlenecks Discussion on July 13, 2017

  *   Date and Time
 *   Thursday at 
0100-0200
 UTC, July 13, 2017
 *   Thursday at 0900-1000 Beijing, July 13, 2017
 *   Wednesday at 1800-1900 PDT, July 13, 2017
  *   Minutes
 *   Yang Yu
  *   Participants (2 peoples):
 *   Ace Lee
Agenda:

  *   Stress Testing Discuss & Release Discuss
  *   Action Items Review
Discussion & Action Item

1.  Stress Testing Discuss & Release Discuss

  *   Long duration POD for stress testing
 *   Report from last TSC meeting
*   A concrete proposal is need that TSC could vote on
   *   Morgan has provide a proposal that include clear benefit and 
plan of the long duration test
   *   Discussion in Testperf meeting suggests only consider mid-term 
goal based on current situation
 *   Cross project stress is under consideration
*   Running VSperf while StorPerf is excuted
*   Bottlenecks act as load manager while monitoring/analyzing
  *   Intern Projects
 *   Have contacted the intern for CPU limit
*   Might need voice communication/interview before official start
*   Action on Gabriel to confirm and initiate the process
  *   Euphrates Planning updated
 *   https://wiki.opnfv.org/display/bottlenecks/Bottlenecks+Release+Plan
 *   Testing Framework Refactoring
*   Monitoring module has been assigned high priority
   *   Decide to integrate Prometheus with Collectd exporter and maybe 
some host monitoring tools
   *   Prakash feedback about the node monitoring process suggesting 
included in Bottlenecks for stress testing monitoring
*   Top logic for tuning test should be included in JIRA
 *   Initiate Container Testing
*   This plan has been assigned low priority
*   Prakash should feedback about Kola deployment/testing
*   K8S, OpenRetriever, ...
 *   Initiate Tuning Testing
*   WIKI page should be elaborated
   *   https://wiki.opnfv.org/pages/viewpage.action?pageId=12386549
*   Ceph or CPU tuning is under consideration now
   *   Need investigation work
   *   Action item on Gabriel

2.  Project Engagement

  *   More contributors are welcome to Bottlenecks
  *   Cooperation with other projects
 *   Integration with upstream
  *   Non-active committer contact
 *   Has sent out emails to confirm the involvement plan of committers for 
E release

3.  Action Item Review

  *   https://wiki.opnfv.org/display/bottlenecks/Release+Plan
  Euphrates:

  *   How to use Quota - Prakash
 *   Reliability project in Openstack - Prakash
 *   WIKI page restructured for closely updating project details @done 
(17-05-11 09:20)
 *   Testing framework
*   General env pre commond for all test cases? Maybe different test 
cases call diffrent functions?
  *   Requirements investigation of DPDK and SR-IOV in Bottlenecks
 *   Which categories we should put them in?
 *   What the structure of their report?
 *   Is there any existing implementation we could use?
 *   Do we need to separate the env pre and test executing operations?
  *   Test report
 *   (Automatically) Test result report to MongoDB @done
 *   Landing page (on-going, in plan)
  *   Stress testing
 *   Implementing the rest stress test cases discussed during Danube
 *   Collect stress test case
 *   Request/maintaining long duration pod
 *   Work with VSPERF & StorPerf
  *   Initiate Tuning Test
 *   Ceph Tuning ( installer deployment tuning?)
 *   Comparison results
  *   Initiate Container Testing
 *   K8S, OpenRetriever,  unicore
 *   Work with installers team for Kola deployment testing
 *   Prakash to check OpenStack for Kola testing
  *   Testing Framework Refactoring
 *   Overall framework design
 *   Abandon docker-compose usage and adaptively testing sourcing OPNFV 
credentials.
 *   Determine requirements & Initiate the overall framework design
 *   Unified entrance/top logic for system limit/tuning test
 *   Initiate top logic design & investigation
 *   Separated monitoring module
*   Work with StorPerf & VSPERF adding monitoring function
*   Monitoring using yardstick? Barometer?
 *   Stand-alone & offline
  *   More Contributors in Bottlenecks
 *   Intern projects
 *   Integrate upstream
 *   More contributors in project

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

[opnfv-tech-discuss] 答复: [opnfv-tsc] TSC vote requested for Danube 3.0 release

[Fu Qiao]

Hi, I think I send out my vote yesterday as soon as I read this email. It seems 
that it is not getting out…

My +1

 

发件人: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] 代表 Raymond Paik
发送时间: 2017年7月11日 23:50
收件人: opnfv-...@lists.opnfv.org
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tsc] TSC vote requested for Danube 3.0 release

 

All, 

 

After checking with several scenarios owners during the Release call today, 
there was a consensus that people were ready to tag for the Danube 3.0 release 
on July 14th.  There were some scenarios with degradation compared to 1.0 or 
2.0 releases, but they would be explained in documentations (e.g. due to 
upstream bug).

 

So, I'd like to ask the TSC members to vote on the following by 5pm Pacific 
Time July 12th.

 

"Does the TSC approve the Danube 3.0 release date of July 14?  (+1, 0, -1)"

 

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] [VSPERF]

[MORTON, ALFRED C (AL)]

Thanks to Trevor, I have what I need...

From: MORTON, ALFRED C (AL)
Sent: Wednesday, July 12, 2017 3:30 PM
To: 'Goldammer, MartinX'; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [VSPERF]

Hi VSPERF,

One of my Action Requests from today's meeting is:
*  ACTION: Al to review latency output (histogram table) from TREX provided by 
Martin Godalmer and provide feedback 
(trevor_intel,
 15:14:27)

I searched the recent e-mail and minutes,
but haven't found a link to the TREX histogram.

Could someone please share the location or histogram file with me?

thanks,
Al

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Goldammer, 
MartinX
Sent: Wednesday, January 11, 2017 4:29 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] I would like to contribute to the project

Hi,
I'd like to contribute to the VSPERF project - please add me as a Contributor
Thank you very much
Martin Goldammer

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF]

[MORTON, ALFRED C (AL)]

Hi VSPERF,

One of my Action Requests from today's meeting is:
*  ACTION: Al to review latency output (histogram table) from TREX provided by 
Martin Godalmer and provide feedback 
(trevor_intel,
 15:14:27)

I searched the recent e-mail and minutes,
but haven't found a link to the TREX histogram.

Could someone please share the location or histogram file with me?

thanks,
Al

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Goldammer, 
MartinX
Sent: Wednesday, January 11, 2017 4:29 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] I would like to contribute to the project

Hi,
I'd like to contribute to the VSPERF project - please add me as a Contributor
Thank you very much
Martin Goldammer

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[Alec Hothan (ahothan)]

July/August is tricky with PTOs.
Perhaps we should start the discussion by email on this mailer and discuss 
about it in 2 weeks at the test-wg meeting? 
Do you guys usually use a text document reviewed with gerrit to 
discuss/collaborate on a spec? Or any other method? Please let me know and I 
can get a head start on this.

Thanks

  Alec

On 7/12/17, 8:54 AM, "morgan.richo...@orange.com"  
wrote:

I will be in PTO too :)

Unfortunately the weekly meeting was today at 8 UTC (APAC slot)
we will use the slot of tomorrow to organize an ad-hoc meeting with 
Bitergia on result vizualization
not sure we will have 15 minutes for another topic

It is maybe possible to organize an ad-hoc meeting on this topic after 
the point with Bitergia?

Do not hesitate to modify directly the agenda at your convenience 
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)

/Morgan



On 12/07/2017 17:43, Alec Hothan (ahothan) wrote:
> Morgan,
>
> Unfortunately, I won’t be able to attend next week (on PTO).
> Can this be squeezed into tomorrow’s meeting (July 13)? We could shorten 
it and follow up with a separate meeting or on email/IRC.
>
> Thanks
>
>Alec
>
>
>
> On 7/12/17, 8:32 AM, "morgan.richo...@orange.com" 
 wrote:
>
>  topic added for the next meeting (20th of July)
>  
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting
>  
>  Mark and Jose are already involved in several activities dealing with
>  docker.
>  Cedric has a good view on this topic.
>  
>  /Morgan
>  
>  On 12/07/2017 17:27, Alec Hothan (ahothan) wrote:
>  > I’d like to add this topic to the next weekly meeting of the 
test-wg and would like to know if anybody else from test-wg would be interested 
to help redact a proposal for enhancing the docker container versioning and 
build workflow in OPNFV. As I understand this will only concern a subset of 
test projects for now at least.
>  >
>  > To the agenda:
>  > - Problem statement for those who have not followed the email 
thread
>  > - General goals
>  > - Get feedback from current projects wrt current container 
versioning scheme, Q
>  > - Who would like to participate and how to proceed
>  > We might need about 15’ to go over these points (no question we 
will need more detailed discussion which can be better done through email or 
IRC after that meeting).
>  >
>  > What would be great is for those concerned project owners to think 
about how the requirements of their respective project wrt to their container 
versioning:
>  > - How often do you think you need to build your containers
>  > - Any hurdles experienced while building/managing container images
>  > - How do your container images relate to OPNFV releases (e.g. do 
you have a 1 container version per release of do you prefer to have 1 version 
that tackles all supported releases)
>  > - How do you “bundle” your containers to OPNFV releases (or how do 
your users know what version of container to use for a given release)
>  >
>  > We can also use email to get a head start or for those who cannot 
attend the meeting.
>  > I hope we can get a draft proposal by early August.
>  >
>  > Thanks
>  >
>  >Alec
>  >
>  >
>  > On 7/11/17, 8:29 AM, "Fatih Degirmenci"  wrote:
>  >
>  >  +1 to "Can we work on a proposal and get every project that 
deals with containers involved?"
>  >
>  >  It is mainly test projects who use containers so I again let 
testing community to take the lead and point you to where/how the conversation 
started.
>  >
>  >  We can then try to generalize it later on.
>  >
>  >  /Fatih
>  >
>  >  On 11 Jul 2017, at 17:16, Alec Hothan (ahothan) 
 wrote:
>  >
>  >  Can we work on a proposal and get every project that deals 
with containers involved?
>  >
>  > ___
>  > test-wg mailing list
>  > test...@lists.opnfv.org
>  > https://lists.opnfv.org/mailman/listinfo/test-wg
>  
>  
>  --
>  Morgan Richomme
>  Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>  
>  Network architect for innovative services
>  Future of the Network community member
>  Open source Orange community manager
>  
>  
>  tel. +33 (0) 296 072 106
>  mob. +33 (0) 637 753 326
>  morgan.richo...@orange.com
>  
>  
>  

Re: [opnfv-tech-discuss] [release][danube] Danube 3 release on July 14

[David McBride]

Reminder - testing should be complete today, followed by documentation and
JIRA updates tomorrow.  Let me know if you have questions.

David

On Mon, Jul 10, 2017 at 5:27 PM, David McBride  wrote:

> Reminder...
>
> On Thu, Jul 6, 2017 at 5:20 PM, David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Reminder... as approved by the TSC last week, Danube 3 will be released 1
>> week from tomorrow on July 14.  The schedule is as follows:
>>
>>- July 12 - complete testing
>>- July 13 - finish document updates / update JIRA
>>- July 14 - tag repos and release
>>- Week of July 17 - download page goes live
>>
>> Let me know if you have questions.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



-- 
*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] [test-wg] docker container versioning

[morgan.richomme]

I will be in PTO too :)

Unfortunately the weekly meeting was today at 8 UTC (APAC slot)
we will use the slot of tomorrow to organize an ad-hoc meeting with 
Bitergia on result vizualization

not sure we will have 15 minutes for another topic

It is maybe possible to organize an ad-hoc meeting on this topic after 
the point with Bitergia?


Do not hesitate to modify directly the agenda at your convenience 
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)


/Morgan



On 12/07/2017 17:43, Alec Hothan (ahothan) wrote:

Morgan,

Unfortunately, I won’t be able to attend next week (on PTO).
Can this be squeezed into tomorrow’s meeting (July 13)? We could shorten it and 
follow up with a separate meeting or on email/IRC.

Thanks

   Alec



On 7/12/17, 8:32 AM, "morgan.richo...@orange.com"  
wrote:

 topic added for the next meeting (20th of July)
 https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting
 
 Mark and Jose are already involved in several activities dealing with

 docker.
 Cedric has a good view on this topic.
 
 /Morgan
 
 On 12/07/2017 17:27, Alec Hothan (ahothan) wrote:

 > I’d like to add this topic to the next weekly meeting of the test-wg and 
would like to know if anybody else from test-wg would be interested to help redact 
a proposal for enhancing the docker container versioning and build workflow in 
OPNFV. As I understand this will only concern a subset of test projects for now at 
least.
 >
 > To the agenda:
 > - Problem statement for those who have not followed the email thread
 > - General goals
 > - Get feedback from current projects wrt current container versioning 
scheme, Q
 > - Who would like to participate and how to proceed
 > We might need about 15’ to go over these points (no question we will 
need more detailed discussion which can be better done through email or IRC after 
that meeting).
 >
 > What would be great is for those concerned project owners to think about 
how the requirements of their respective project wrt to their container versioning:
 > - How often do you think you need to build your containers
 > - Any hurdles experienced while building/managing container images
 > - How do your container images relate to OPNFV releases (e.g. do you 
have a 1 container version per release of do you prefer to have 1 version that 
tackles all supported releases)
 > - How do you “bundle” your containers to OPNFV releases (or how do your 
users know what version of container to use for a given release)
 >
 > We can also use email to get a head start or for those who cannot attend 
the meeting.
 > I hope we can get a draft proposal by early August.
 >
 > Thanks
 >
 >Alec
 >
 >
 > On 7/11/17, 8:29 AM, "Fatih Degirmenci"  wrote:
 >
 >  +1 to "Can we work on a proposal and get every project that deals with 
containers involved?"
 >
 >  It is mainly test projects who use containers so I again let 
testing community to take the lead and point you to where/how the conversation 
started.
 >
 >  We can then try to generalize it later on.
 >
 >  /Fatih
 >
 >  On 11 Jul 2017, at 17:16, Alec Hothan (ahothan)  
wrote:
 >
 >  Can we work on a proposal and get every project that deals with 
containers involved?
 >
 > ___
 > test-wg mailing list
 > test...@lists.opnfv.org
 > https://lists.opnfv.org/mailman/listinfo/test-wg
 
 
 --

 Morgan Richomme
 Orange/ IMT/ OLN/ CNC/ NCA/ SINA
 
 Network architect for innovative services

 Future of the Network community member
 Open source Orange community manager
 
 
 tel. +33 (0) 296 072 106

 mob. +33 (0) 637 753 326
 morgan.richo...@orange.com
 
 
 _
 
 Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

 pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
recu ce message par erreur, veuillez le signaler
 a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
 Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.
 
 This message and its attachments may contain confidential or privileged information that may be protected by law;

 they should not be distributed, used or copied without authorisation.
 If you have received this email in error, please notify the sender and 
delete this message and its attachments.
 As emails may be altered, Orange is not liable 

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[Alec Hothan (ahothan)]

Morgan,

Unfortunately, I won’t be able to attend next week (on PTO).
Can this be squeezed into tomorrow’s meeting (July 13)? We could shorten it and 
follow up with a separate meeting or on email/IRC.

Thanks

  Alec



On 7/12/17, 8:32 AM, "morgan.richo...@orange.com"  
wrote:

topic added for the next meeting (20th of July)
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting

Mark and Jose are already involved in several activities dealing with 
docker.
Cedric has a good view on this topic.

/Morgan

On 12/07/2017 17:27, Alec Hothan (ahothan) wrote:
> I’d like to add this topic to the next weekly meeting of the test-wg and 
would like to know if anybody else from test-wg would be interested to help 
redact a proposal for enhancing the docker container versioning and build 
workflow in OPNFV. As I understand this will only concern a subset of test 
projects for now at least.
>
> To the agenda:
> - Problem statement for those who have not followed the email thread
> - General goals
> - Get feedback from current projects wrt current container versioning 
scheme, Q
> - Who would like to participate and how to proceed
> We might need about 15’ to go over these points (no question we will need 
more detailed discussion which can be better done through email or IRC after 
that meeting).
>
> What would be great is for those concerned project owners to think about 
how the requirements of their respective project wrt to their container 
versioning:
> - How often do you think you need to build your containers
> - Any hurdles experienced while building/managing container images
> - How do your container images relate to OPNFV releases (e.g. do you have 
a 1 container version per release of do you prefer to have 1 version that 
tackles all supported releases)
> - How do you “bundle” your containers to OPNFV releases (or how do your 
users know what version of container to use for a given release)
>
> We can also use email to get a head start or for those who cannot attend 
the meeting.
> I hope we can get a draft proposal by early August.
>
> Thanks
>
>Alec
>
>
> On 7/11/17, 8:29 AM, "Fatih Degirmenci"  wrote:
>
>  +1 to "Can we work on a proposal and get every project that deals 
with containers involved?"
>  
>  It is mainly test projects who use containers so I again let testing 
community to take the lead and point you to where/how the conversation started.
>  
>  We can then try to generalize it later on.
>  
>  /Fatih
>  
>  On 11 Jul 2017, at 17:16, Alec Hothan (ahothan)  
wrote:
>  
>  Can we work on a proposal and get every project that deals with 
containers involved?
>
> ___
> test-wg mailing list
> test...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/test-wg


-- 
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com



_

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

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



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

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[morgan.richomme]

topic added for the next meeting (20th of July)
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting

Mark and Jose are already involved in several activities dealing with 
docker.

Cedric has a good view on this topic.

/Morgan

On 12/07/2017 17:27, Alec Hothan (ahothan) wrote:

I’d like to add this topic to the next weekly meeting of the test-wg and would 
like to know if anybody else from test-wg would be interested to help redact a 
proposal for enhancing the docker container versioning and build workflow in 
OPNFV. As I understand this will only concern a subset of test projects for now 
at least.

To the agenda:
- Problem statement for those who have not followed the email thread
- General goals
- Get feedback from current projects wrt current container versioning scheme, 
Q
- Who would like to participate and how to proceed
We might need about 15’ to go over these points (no question we will need more 
detailed discussion which can be better done through email or IRC after that 
meeting).

What would be great is for those concerned project owners to think about how 
the requirements of their respective project wrt to their container versioning:
- How often do you think you need to build your containers
- Any hurdles experienced while building/managing container images
- How do your container images relate to OPNFV releases (e.g. do you have a 1 
container version per release of do you prefer to have 1 version that tackles 
all supported releases)
- How do you “bundle” your containers to OPNFV releases (or how do your users 
know what version of container to use for a given release)

We can also use email to get a head start or for those who cannot attend the 
meeting.
I hope we can get a draft proposal by early August.

Thanks

   Alec


On 7/11/17, 8:29 AM, "Fatih Degirmenci"  wrote:

 +1 to "Can we work on a proposal and get every project that deals with 
containers involved?"
 
 It is mainly test projects who use containers so I again let testing community to take the lead and point you to where/how the conversation started.
 
 We can then try to generalize it later on.
 
 /Fatih
 
 On 11 Jul 2017, at 17:16, Alec Hothan (ahothan)  wrote:
 
 Can we work on a proposal and get every project that deals with containers involved?


___
test-wg mailing list
test...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/test-wg



--
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com


_

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

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

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

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

[Alec Hothan (ahothan)]

I’d like to add this topic to the next weekly meeting of the test-wg and would 
like to know if anybody else from test-wg would be interested to help redact a 
proposal for enhancing the docker container versioning and build workflow in 
OPNFV. As I understand this will only concern a subset of test projects for now 
at least.

To the agenda:
- Problem statement for those who have not followed the email thread
- General goals
- Get feedback from current projects wrt current container versioning scheme, 
Q
- Who would like to participate and how to proceed
We might need about 15’ to go over these points (no question we will need more 
detailed discussion which can be better done through email or IRC after that 
meeting).

What would be great is for those concerned project owners to think about how 
the requirements of their respective project wrt to their container versioning:
- How often do you think you need to build your containers
- Any hurdles experienced while building/managing container images
- How do your container images relate to OPNFV releases (e.g. do you have a 1 
container version per release of do you prefer to have 1 version that tackles 
all supported releases)
- How do you “bundle” your containers to OPNFV releases (or how do your users 
know what version of container to use for a given release)

We can also use email to get a head start or for those who cannot attend the 
meeting.
I hope we can get a draft proposal by early August.

Thanks

  Alec


On 7/11/17, 8:29 AM, "Fatih Degirmenci"  wrote:

+1 to "Can we work on a proposal and get every project that deals with 
containers involved?"

It is mainly test projects who use containers so I again let testing 
community to take the lead and point you to where/how the conversation started.

We can then try to generalize it later on.

/Fatih

On 11 Jul 2017, at 17:16, Alec Hothan (ahothan)  wrote:

Can we work on a proposal and get every project that deals with containers 
involved?

___
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] TSC vote requested for Danube 3.0 release

[Tim Irnich]

My vote is +1

Regards, Tim

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Wednesday, July 12, 2017 16:51
To: SULLIVAN, BRYAN L 
Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] TSC vote requested for Danube 3.0 
release

Thanks Bryan

Other TSC members and proxies, a reminder to please cast your votes in the next 
~9 hours.

Ray

On Wed, Jul 12, 2017 at 7:44 AM, SULLIVAN, BRYAN L 
> wrote:
For myself and Bin (out of office), +1

Thanks,
Bryan Sullivan | AT

From: Raymond Paik >
Date: Tue, Jul 11, 2017 at 8:49 AM
Subject: TSC vote requested for Danube 3.0 release
To: "opnfv-...@lists.opnfv.org" 
>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
>

All,

After checking with several scenarios owners during the Release call today, 
there was a consensus that people were ready to tag for the Danube 3.0 release 
on July 14th.  There were some scenarios with degradation compared to 1.0 or 
2.0 releases, but they would be explained in documentations (e.g. due to 
upstream bug).

So, I'd like to ask the TSC members to vote on the following by 5pm Pacific 
Time July 12th.

"Does the TSC approve the Danube 3.0 release date of July 14?  (+1, 0, -1)"

Thanks,

Ray


___
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

Re: [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release

[Ulrich Kleber]

My vote is -1.
I would rather drop Danube 3.0 completely than releasing something that is 
worse than Danube 2.0.
It was meant to be a maintenance release.

Cheers,
Uli

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Tuesday, 11 July, 2017 17:50
To: opnfv-...@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] TSC vote requested for Danube 3.0 release

All,

After checking with several scenarios owners during the Release call today, 
there was a consensus that people were ready to tag for the Danube 3.0 release 
on July 14th.  There were some scenarios with degradation compared to 1.0 or 
2.0 releases, but they would be explained in documentations (e.g. due to 
upstream bug).

So, I'd like to ask the TSC members to vote on the following by 5pm Pacific 
Time July 12th.

"Does the TSC approve the Danube 3.0 release date of July 14?  (+1, 0, -1)"

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] [mano-wg] Summary of meeting #37 Bestpractices in OPNFV D and future mano testing

[Prakash Ramchandran]

Hi all,

Appreciate all your support in getting mano descriptor work refined in release 
D and providing example based on OpenBaton/Orchestra and  JOID, until ONAP gets 
rebooted  through Opera in following releases.

Here is the summary and will continue on what we could not complete this week 
to next.

The irc summary is here for
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-07-12-13.59.html

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

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

[Cooper, Trevor]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Akram Al 
 Sawaf':MAILTO:sa...@eantc.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
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='Alan McNa
 mee':MAILTO:alan...@openet.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='Cathy Zha
 ng':MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.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='Jerome To
 llet (jtollet)':MAILTO:jtol...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'MORTON, A
 LFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marco Var
 lese':MAILTO:marco.varl...@suse.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='Prashant 
 Sunkari':MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yunchao h
 u':MAILTO:yunchao...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
DESCRIPTION;LANGUAGE=en-US:Time\n\nWednesday UTC 15h00\, Ireland (UTC/GMT +
 1) 16h00\, PDT 8h00 (UTC/GMT -7)\n\nCurrently observing daylight saving\n\
 n\n\nIRC\n\nfreenode https://freenode.net/\n\nchannel: #opnfv-vswitchperf 
 http://webchat.freenode.net/?channels=opnfv-vswitchperf\n\n\n\nMeetBot htt
 p://meetbot.opnfv.org/meetings/opnfv-vswitchperf/2017/\n\n\n\nAudio\n\nhtt
 ps://global.gotomeeting.com/join/391235029\n\nYou can also dial in using y
 our phone.  United States: +1 (571) 317-3116  Access Code: 391-235-029\n\n
 Phone numbers from other countries are here … https://wiki.opnfv.org/dis
 play/meetings\n
SUMMARY;LANGUAGE=en-US:[VSPERF] Weekly Call
DTSTART;TZID=America/Los_Angeles:20170712T08
DTEND;TZID=America/Los_Angeles:20170712T09
UID:04008200E00074C5B7101A82E008E0E68EB371C9D201000
 01000CF541241B5F8FE4295470E921531C8E2
RECURRENCE-ID;TZID=America/Los_Angeles:20170712T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170712T142520Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and IRC channel #opnfv-vswitchperf
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT10M
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] [dovetail] Use-cases for Dovetail Danube Release

[Wenjing Chu]

The use cases that will work well are simpler ones that capture the main design 
pattern but not full brown complex solutions like VOLTE.

Wenjing

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Tuesday, July 11, 2017 4:00 PM
To: Wenjing Chu ; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube 
Release

Hi Wenjing

Yes its new thread.

Re. EUAG I am aware of the Pain Points Wiki page however it's not clear to me 
how this is feeding initial scope of CVP. The CVP page 
https://wiki.opnfv.org/pages/viewpage.action?pageId=11700688 does not have any 
feedback yet from what I can see ... any idea on how we can facilitate getting 
some feedback?

I take your point about complexity of those applications and common patterns 
... but what was the suggestion for an alternative "use-case approach"? I 
assumed it meant using specific use-models e.g. VOLTE to derive platform 
capabilities that we should include in scope of tests ... this also seems to be 
what you are saying but I don't think that analysis has been done in Dovetail 
yet, correct?

/Trevor

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Tuesday, July 11, 2017 11:16 AM
To: Cooper, Trevor >; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube 
Release

Hi Trevor

I'm not sure if your email is a follow-up of a previous message or not. I 
couldn't find another email so I'm assuming this is a new thread. Let me know 
if I'm mistaken.

First of all, we did receive detailed feedbacks from EUAG as far back as Feb 
and most recently during the Summit in June. So additional feedbacks are 
welcome but we are not waiting/gating on anything from EUAG at this time. As 
part of action items during the Summit when CVP was discussed with the EUAG, we 
agreed to set up a wiki in EUAG for tracking additional feedbacks. It's under 
the EUAG wiki page and just follow the link for cvp feedbacks.

I personally use the term "use case approach" in the context of CVP to mean 
that for a given SUT, we identify common use patterns, and develop automated 
test cases to exercise such patterns. I agree with Bryan's comment in 
yesterday's c call that applications like VOLTE and vCPE are too complex for 
our purposes - it won't be easy to separate issues of the application's 
implementation from the issues of SUT (the latter is what we wish to identify). 
A better approach is abstract the common design patterns out of a complex 
application, and develop test cases around those common patterns that have more 
general applicability to all similar applications.

For example, vPING is a common pattern of "2 virtual machines with virtual 
network connectivity between them". This can be seen as the simplest use 
pattern. Another use pattern may be multiple virtual machines load balancing to 
provide a common service. vCPE, if narrowly defined, can be a pattern of secure 
gateway between two network domains. I personally think this space between 
simplicity of a vPING to a well understood gateway function may be the most 
productive area we can focus on.

Many of OPNFV projects can contribute these use pattern test cases, by 
abstracting and by clarifying what the test intention is, in some cases. This 
is a great area of 'low hanging fruit' during the E release cycle.

Regards
Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor
Sent: Monday, July 10, 2017 4:50 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube Release

My notes on the "use-case approach" with VOLTE and vCPE ... capture that EUAG 
supports the approach and will get back with some suggestions. Are we still 
waiting on the EUAG to get back? If yes what are our expectations for receiving 
guidance? Can we try to define the "use-case approach" better ... e.g. meld 
this with our current approach to say identify gaps/deficiencies with the test 
cases? What approach should we take for identifying and organizing VOLTE and 
vCPE capabilities and their relevant test-cases?

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

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

[Cooper, Trevor]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Akram Al 
 Sawaf':MAILTO:sa...@eantc.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
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='Alan McNa
 mee':MAILTO:alan...@openet.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='Cathy Zha
 ng':MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.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='Jerome To
 llet (jtollet)':MAILTO:jtol...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'MORTON, A
 LFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marco Var
 lese':MAILTO:marco.varl...@suse.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='Prashant 
 Sunkari':MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yunchao h
 u':MAILTO:yunchao...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
DESCRIPTION;LANGUAGE=en-US:Time\n\nWednesday UTC 15h00\, Ireland (UTC/GMT +
 1) 16h00\, PDT 8h00 (UTC/GMT -7)\n\nCurrently observing daylight saving\n\
 n\n\nIRC\n\nfreenode https://freenode.net/\n\nchannel: #opnfv-vswitchperf 
 http://webchat.freenode.net/?channels=opnfv-vswitchperf\n\n\n\nMeetBot htt
 p://meetbot.opnfv.org/meetings/opnfv-vswitchperf/2017/\n\n\n\nAudio\n\nhtt
 ps://global.gotomeeting.com/join/391235029\n\nYou can also dial in using y
 our phone.  United States: +1 (571) 317-3116  Access Code: 391-235-029\n\n
 Phone numbers from other countries are here … https://wiki.opnfv.org/dis
 play/meetings\n
SUMMARY;LANGUAGE=en-US:[VSPERF] Weekly Call
DTSTART;TZID=America/Los_Angeles:20170712T08
DTEND;TZID=America/Los_Angeles:20170712T09
UID:04008200E00074C5B7101A82E008E0E68EB371C9D201000
 01000CF541241B5F8FE4295470E921531C8E2
RECURRENCE-ID;TZID=America/Los_Angeles:20170712T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170712T142520Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and IRC channel #opnfv-vswitchperf
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT10M
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] [dovetail] Use-cases for Dovetail Danube Release

[SULLIVAN, BRYAN L]

EUAG input to the CVP use case priorities will be a topic in the upcoming EUAG 
call (next week). I discussed some proposed agenda items with Steven yesterday 
and this was included, along with:
- reframing the pain points to be more actionable by the tech community, e.g. 
for future projects or programs such as CVP
- health-check on the role of the EUAG, how it's influencing the tech 
community, and how the community is serving the end-user interests overall

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Cooper, Trevor 
[trevor.coo...@intel.com]
Sent: Tuesday, July 11, 2017 4:00 PM
To: Wenjing Chu; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube 
Release

Hi Wenjing

Yes its new thread.

Re. EUAG I am aware of the Pain Points Wiki page however it’s not clear to me 
how this is feeding initial scope of CVP. The CVP page 
https://wiki.opnfv.org/pages/viewpage.action?pageId=11700688
 does not have any feedback yet from what I can see … any idea on how we can 
facilitate getting some feedback?

I take your point about complexity of those applications and common patterns … 
but what was the suggestion for an alternative “use-case approach”? I assumed 
it meant using specific use-models e.g. VOLTE to derive platform capabilities 
that we should include in scope of tests ... this also seems to be what you are 
saying but I don’t think that analysis has been done in Dovetail yet, correct?

/Trevor

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Tuesday, July 11, 2017 11:16 AM
To: Cooper, Trevor ; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube 
Release

Hi Trevor

I’m not sure if your email is a follow-up of a previous message or not. I 
couldn’t find another email so I’m assuming this is a new thread. Let me know 
if I’m mistaken.

First of all, we did receive detailed feedbacks from EUAG as far back as Feb 
and most recently during the Summit in June. So additional feedbacks are 
welcome but we are not waiting/gating on anything from EUAG at this time. As 
part of action items during the Summit when CVP was discussed with the EUAG, we 
agreed to set up a wiki in EUAG for tracking additional feedbacks. It’s under 
the EUAG wiki page and just follow the link for cvp feedbacks.

I personally use the term “use case approach” in the context of CVP to mean 
that for a given SUT, we identify common use patterns, and develop automated 
test cases to exercise such patterns. I agree with Bryan’s comment in 
yesterday’s c call that applications like VOLTE and vCPE are too complex for 
our purposes – it won’t be easy to separate issues of the application’s 
implementation from the issues of SUT (the latter is what we wish to identify). 
A better approach is abstract the common design patterns out of a complex 
application, and develop test cases around those common patterns that have more 
general applicability to all similar applications.

For example, vPING is a common pattern of “2 virtual machines with virtual 
network connectivity between them”. This can be seen as the simplest use 
pattern. Another use pattern may be multiple virtual machines load balancing to 
provide a common service. vCPE, if narrowly defined, can be a pattern of secure 
gateway between two network domains. I personally think this space between 
simplicity of a vPING to a well understood gateway function may be the most 
productive area we can focus on.

Many of OPNFV projects can contribute these use pattern test cases, by 
abstracting and by clarifying what the test intention is, in some cases. This 
is a great area of ‘low hanging fruit’ during the E release cycle.

Regards
Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor
Sent: Monday, July 10, 2017 4:50 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube Release

My notes on the “use-case approach” with VOLTE and vCPE … capture that EUAG 
supports the approach and will get back with some suggestions. Are we still 
waiting on the EUAG to get back? If yes what are our expectations for receiving 
guidance? Can we try to define the “use-case approach” better … e.g. meld this 
with our current approach to say identify gaps/deficiencies with the test 
cases? What approach should we take for identifying and organizing VOLTE and 
vCPE 

[opnfv-tech-discuss] SFC weekly cancelled this week

[Manuel Buil]

Hi,

After asking around, it does not seem like there was much progress this
week + some people are on vacation. So we cancel the meeting this week.

In case of doubts, problems or discussions, come to our IRC channel
#opnfv-sfc or use this mailing list!

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

[opnfv-tech-discuss] [Bottlenecks] Bottlenecks weekly meeting 7-13 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

[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=Tianhongbo
 :MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lijun (Mat
 thew):MAILTO:matthew.li...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=liangqi (D
 ):MAILTO:liang...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Liyiting:M
 AILTO:liyit...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='mrebellon
 @sandvine.com':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='michael.a
 .ly...@intel.com':MAILTO:michael.a.ly...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=limingjian
 g:MAILTO:limingji...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=邓灵莉/
 Lingli Deng:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='qwyang012
 6...@gmail.com':MAILTO:qwyang0...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prakash Ra
 mchandran:MAILTO:prakash.ramchand...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=zh-CN:Hi\,\n\nThe Bottlenecks weekly meeting will be h
 eld at 1:00-2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT
  18:00-19:00 Wednesday.\nWelcome to join our discussion. Details of this m
 eeting are shown below.\n\n\nAgenda:\n1.  Bottlenecks D Rel. Discussio
 n\n2.  Bottlenecks E Rel. Discussion\n3.  Stress testing Discussio
 n\n4.  Action Item Review\n\nMeeting Resources\n\nPlease join the meet
 ing from your computer\, tablet or smartphone.\nhttps://global.gotomeeting
 .com/join/391235029\n\nYou can also dial in using your phone.\nUnited Stat
 es (Toll-free): 1 877 309 2070\nUnited States : +1 (312) 757-3119\n\n\nAcc
 ess Code: 882-532-573\n\n\nBest\,\nYang\n\n\n\n\n
SUMMARY;LANGUAGE=zh-CN:[Bottlenecks] Bottlenecks weekly meeting 7-13 (1:00-
 2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT 18:00-19:00
  Wednesday )
DTSTART;TZID=W. Australia Standard Time:20170713T09
DTEND;TZID=W. Australia Standard Time:20170713T10
UID:04008200E00074C5B7101A82E0087049450E46FBD201000
 01000533B93B43073D94BA033DD633722C38D
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170712T113545Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:384595937
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] [release][euphrates] Milestone 3.2 - installers deploy scenario with integrated SDN and pass health check

[Michael Polenchuk]

Hi,

There are the results for Fuel/MCP:
https://build.opnfv.org/ci/job/functest-fuel-virtual-daily-master/1941/console
Health check passed for os-odl_l2-nofeature-noha scenario.

On Mon, Jul 10, 2017 at 7:49 PM, David McBride  wrote:

> Installer teams,
>
> Milestone 3.2 is scheduled for tomorrow, July 11.  Please provide the
> following:
>
>- Identify a scenario that includes an integrated SDN controller that
>demonstrates that your installer meets the requirements of MS3.2.
>- Provide a pointer to test results that demonstrate that health check
>passes for the identified scenario.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Fwd: Voting for Manuel Buil as OPNFV SFC PTL

[Brady Johnson]

Im forwarding Vishal Murgai's vote for Manuel Buil as OPNFV SFC PTL to the
opnfv-tech-discuss list.

Regards,

Brady
bjohn...@inocybe.ca


-- Forwarded message --
From: Vishal Murgai (vmurgai) 
Date: Mon, Jul 10, 2017 at 6:24 PM
Subject: Re: Voting for Manuel Buil as OPNFV SFC PTL
To: Sam Hague 
Cc: Brady Johnson , Manuel Buil ,
james n guichard , Reinaldo Penno <
rape...@gmail.com>, "Rozet, Tim" 


Hi Brady

+2 for this.

Regards
Vishal.

Sent from my iPhone

> On Jul 10, 2017, at 9:47 PM, Sam Hague  wrote:
>
> +2 here and on the gerrit.
>
>> On Mon, Jul 10, 2017 at 11:52 AM, Brady Johnson 
wrote:
>>
>> Hey Guys,
>>
>> Can I please get a +2, 0, or -2 vote from you (Manuel, you too) on this
>> gerrit to nominate Manuel Buil as OPNFV SFC PTL.
>>
>> https://gerrit.opnfv.org/gerrit/#/c/37125/
>>
>> Thanks,
>>
>> Brady
>> bjohn...@inocybe.ca
>>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [mano-wg] meeting #37 Wednesday 7 PDT/14 UTC/ 22 BJT - MANO Bestpractices from D release and future test plans

[Prakash Ramchandran]

Hi all,

Here is the invite for [mano-wg] meeting #37,  plan for contributions and 
discussions to make it useful for all participants and mano-wg.

Thanks
Prakash


Meeting Times: Every  Wednesday (7.00 am PDT)  at 14.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/229632485
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136

Access Code: 229-632-485
Weekly  meetings for 2017 Q2
Schedules  for next meetings:
July 12th, Wednesday : 14.00 UTC /7.00 PDT  Meeting #37
1.Agenda Bashing
2. Orchestra Release 
plans - 
JOID/PoDs/Builds/Scenario/Deploy/Test
 -Orchestra/JOID Teams,
3. Opera revival & ONAP multiVIM 
requirements  / 
Laas
 -Opera Team changes to scope any and need to review? and seek approvals?
4. Scenario Descriptor on MANO use 
case to choose for it / Sample VNF team inputs.
5. Best Practices - On-boarding , Packaging, LCM (Orchestra vs 
Opera
 base on ONAP)
6. Use case discussions from Summit...VoIP 
Presentation



Thanks

Prakash


Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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