date:20170323

[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting 2017-03-27

2017-03-23 Thread Yujun Zhang (ZTE)

https://etherpad.opnfv.org/p/qtip-meetings-2017-03-27

*# QTIP project weekly meeting on 2017-03-27*


   - time: UTC0730


   - irc://#opnfv-qtip@freenode


   - index: https://etherpad.opnfv.org/p/qtip-meetings


*## Action followup*


   - SerenaFeng to help investigate the logging issue JIRA: QTIP-230


   - all review https://gerrit.opnfv.org/gerrit/#/c/30971/ and finish
   document for Danube


   - Taseer to publish QTIP document to opnfv site


   - yujunz send Beijing Summit CFP draft for review


*## Topics*


   - CFP OPNFV Summit Beijing - https://goo.gl/rEtl13


   - Danube release - https://etherpad.opnfv.org/p/qtip-danube


   - E release planning - https://etherpad.opnfv.org/p/qtip-euphrates


*## Recurring*


   - active sprint followup
   https://jira.opnfv.org/secure/RapidBoard.jspa?projectKey=QTIP=135


   - CI status https://build.opnfv.org/ci/view/qtip/


   - new tasks in JIRA https://jira.opnfv.org/issues/?filter=11198

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

Re: [opnfv-tech-discuss] REMINDER: OPNFV Summit CFP Closes March 27

2017-03-23 Thread Brandon Wick

Hi Bryan,

Thanks for flagging your concerns. The "extra" CFP page now directs to the
latest CFP info/submission link.

There's a lot of history around the move to a new CFP tool for OPNFV, but
essentially, this new tool:

   - Gives the track chairs/program committee more flexibility for
   viewing/scoring sessions by track, track assignments, and scheduling from
   within the tool
   - Flexibility to use the CFP for different types of submissions with
   different fields (e.g. PoC Submissions)

With all the CFP tools, it's always a balance of satisfying the submitters
and reviewers and overall we think this tool does well.

We'll follow up with you directly on your specific issues.

Best,


Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org

*The OPNFV Summit CFP Closes 3/27!
*

On Thu, Mar 23, 2017 at 7:49 AM, SULLIVAN, BRYAN L  wrote:

> Brandon,
>
>
>
> Some feedback on the CFP tool:
>
> -  We should use the LF CFP tool (not sure why we are using a
> different one this time). It’s much more efficient to use a consistent tool
> with the history of proposals we have made to earlier summits.
>
> -  The tool requires you to enter all fields each time (a real
> pain), i.e. does not save them as a profile
>
> -  We should have the ability to edit proposals, rather than
> consulting “technical support”.
>
> -  A google search for “opnfv summit cfp” take you to
> http://events.linuxfoundation.org/events/opnfv-summit/program/cfp which
> says “The Call For Participation (CFP) will be announced soon. Please check
> back.”
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Brandon Wick
> *Sent:* Friday, March 10, 2017 3:45 PM
> *To:* opnfv-tech-dis. 
> *Subject:* [opnfv-tech-discuss] REMINDER: OPNFV Summit CFP Closes March 27
>
>
>
> OPNFV Technical Community:
>
>
>
> This is a reminder that the CFP for the OPNFV Summit
> 
>  (June
> 12-15, Beijing, China) closes *Monday, March 27*. We encourage you to
> prepare and submit a proposal by the deadline. The six primary tracks are
> the following:
>
>- NFV Applications and Orchestration
>- Testing, Infrastructure, and DevOps
>- NFV Strategy and End User Stories
>- NFV Platform Requirements
>- Community and Upstream
>- Futures and Research
>
> *Access the CFP Here
> *
>
>
>
> We look forward to your submissions. If you have any questions, please
> email eve...@opnfv.org.
>
>
>
> Best,
>
>
>
> Brandon Wick
>
> OPNFV Head of Marketing, The Linux Foundation
>
> Mobile: +1.917.282.0960 <(917)%20282-0960>  Skype: wick.brandon
>
> Email / Google Talk: bw...@linuxfoundation.org
>
>
>
> *New Report! OPNFV Plugfest at UNH-IOL
> *
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Code Scan Tools Discussion

2017-03-23 Thread SULLIVAN, BRYAN L

Hi all,

I'm looking for the takeaways from the discussion 
https://wiki.opnfv.org/display/DEV/Licensing+and+External+repo%27s+discussion, 
specifically on the open questions. Should we have a specific followup item for 
this on the weekly technical call?

I'm also interested in other use cases for code scanning, beyond release-time 
scanning of all repos, such as in gerrit commit gates or in CI/CD. If we can 
ensure that the process impact is negligible, I think having an early 
indication of an issue (e.g. no license, incompatible dependency, etc) would be 
very helpful.

Thanks,
Bryan Sullivan | AT

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

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday March 23

2017-03-23 Thread HU, BIN

Hello community,



We had a very good discussion on Thursday March 23rd. Thank you all for 
participation and contribution.



Today, we primarily discussed Scenario 
Descriptor<http://artifacts.opnfv.org/octopus/review/28443/scenario-lifecycle/index.html>
 in Scenario 
Consolidation<https://wiki.opnfv.org/display/INF/Scenario+Consolidation>, and 
discussed details of the SDF template in patch 
https://gerrit.opnfv.org/gerrit/#/c/30677 (template YAML).



For details, please refer to the meeting minutes page [1], which includes 
attendees list and IRC log [2].



Next week on March 30th, we will focus on MANO WG's Build and Test.



Thanks

Bin



[1] https://wiki.opnfv.org/display/PROJ/tc+minutes+20170323

[2] 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-13.00.html



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

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

2017-03-23 Thread Dave Neary

Hi,

I also updated the test requirements to integrate suggestions, and moved
things around to make it clear what we have agreed and what are
suggestions. I also added our feedback to suggestions from last week.

Thanks,
Dave.

On 03/20/2017 07:10 PM, Wenjing Chu wrote:
>  
> 
> I took an action item last Friday to draft a worksheet (questionnaire)
> for the purpose of reviewing test areas/test cases. It can be found
> here: https://wiki.opnfv.org/pages/viewpage.action?pageId=10291560
> 
>  
> 
> Please you are invited to review and give feedbacks. We’ll try to review
> it this week.
> 
>  
> 
> Regards
> 
> Wenjing
> 
>  
> 
>  
> 
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of
> *Wenjing Chu
> *Sent:* Monday, March 20, 2017 1:44 PM
> *To:* 'TECH-DISCUSS OPNFV' 
> *Subject:* [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting minutes
> 
>  
> 
> Here is last week’s meeting minutes:
> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-17-13.00.log.html
> 
>  
> 
> We covered all the items in the agenda, except #5. And in addition, we
> also briefly touched upon the test strategy document draft 
> *http://artifacts.opnfv.org/dovetail/review/30811/testing_user_teststrategy/index.html*
> 
> Please provide feedback/comment.
> 
>  
> 
> The rest of the Dovetail plan for Danube (draft) is still here:
> https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan
> 
>  
> 
> Regards
> 
> Wenjing
> 
>  
> 
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org
> 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of
> *Wenjing Chu
> *Sent:* Wednesday, March 15, 2017 5:33 PM
> *To:* Christopher Price  >; Jose Lausuch
> >; Gaoliang
> (kubi) >;
> morgan.richo...@orange.com ; Tomofumi
> Hayashi >; Ulrich
> Kleber >;
> SULLIVAN, BRYAN L >; Dave Neary
> >; Lijun (Matthew)
> >;
> 'TECH-DISCUSS OPNFV'  >
> *Subject:* [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda
> 
>  
> 
>  
> 
> Here is a list of topics I propose we try to cover this Friday:
> 
>  
> 
> 1)  Test case requirement update (Dave Neary) – 20 min
> 
> 2)  Danube plan review – agreement on TSC report on 3/21 (Wenjing) –
> 20 min
> 
> 3)  Functest/yardstick/testWG dependencies update: result DB,
> refstack, interface, http/https – (Mathew/Jose/Chris P…) – 15 min
> 
> 4)  Dovetail test/qa/CI requirements (Uli/Leo) – 15 min
> 
> 5)  How to get started on test area/test case review (Bryan/Wenjing)
> – 15 min
> 
> 6)  AOB – 5 min
> 
>  
> 
> This is based on a 1.5 hour long meeting as we discussed last week. If
> you are to lead a topic, please come prepared so we can make max use of
> the meeting time. Thanks.
> 
>  
> 
> I also saw Hongbo’s meeting invite that reverts back to our original 7AM
> PDT spot (while rest of the world stays the same hour). I’m not sure if
> that slot is free from GTM bridge conflict for 7:00 – 8:30 period, or if
> something needs to be changed. Hongbo, can you help sort the bridge
> problem out? I’m unable to login to verify one way or the other. It says
> I have no permission.
> 
>  
> 
> Also, Does anyone in US have problem with the new time?
> 
>  
> 
> Regards
> 
> Wenjing
> 
>  
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [release][danube] Danube release status

2017-03-23 Thread David McBride

Thanks, Brady.  Sorry I missed your previous mail.

MS9 and 10 are offsets of the release, so if the release date is changed,
then MS9 and 10 will change, accordingly.

David


On Thu, Mar 23, 2017 at 2:11 AM, Brady Allen Johnson <
brady.allen.john...@ericsson.com> wrote:

>
> David,
>
> I asked in an email previous to this the following questions:
>
> Considering the Danube 1.0 release will be delayed by at least 1 week,
> what is the status of Milestones 9 and 10?
>
> Milestone 9 is due today, March 22 and requires us to have all the JIRAs
> closed and/or assigned to subsequent releases. Does this still make sense
> if we will still be working on fixing problems?
>
> Milestone 10 is due on Friday, March 24. This probably makes more sense to
> maintain, but then we might have MS10 before MS9.
>
>
> Brady
>
> -Original Message-
> *From*: David McBride  >
> *To*: TECH-DISCUSS OPNFV  >,
> opnfv-project-leads  >
> *Cc*: TSC OPNFV  >
> *Subject*: [opnfv-tech-discuss] [release][danube] Danube release status
> *Date*: Wed, 22 Mar 2017 11:27:25 -0700
>
> Team,
>
> As you may be aware, the TSC determined on Tuesday that they do not have
> enough information to vote on the Danube 1.0 release.  Therefore:
>
>- The vote on the release will be deferred to the next TSC meeting on
>Tues, March 28
>- This means that we are no longer planning to release on Mon, March
>27, as originally planned.
>- A revised schedule for release will be developed based on input from
>scenario owners and test framework PTLs.
>- The Release Manager will poll the scenario owners and test framework
>PTLs to assess the confidence level for releasing with different schedule
>offsets.
>
> I will update this thread as I gather additional data and decisions are
> made.  In the mean time, please continue to work hard toward the release,
> as I know you are.
>
> Let me know if you have questions or concerns.
>
> 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 
> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*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] REMINDER: OPNFV Summit CFP Closes March 27

2017-03-23 Thread SULLIVAN, BRYAN L

Brandon,

Some feedback on the CFP tool:

-  We should use the LF CFP tool (not sure why we are using a different 
one this time). It’s much more efficient to use a consistent tool with the 
history of proposals we have made to earlier summits.

-  The tool requires you to enter all fields each time (a real pain), 
i.e. does not save them as a profile

-  We should have the ability to edit proposals, rather than consulting 
“technical support”.

-  A google search for “opnfv summit cfp” take you to 
http://events.linuxfoundation.org/events/opnfv-summit/program/cfp which says 
“The Call For Participation (CFP) will be announced soon. Please check back.”

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Brandon Wick
Sent: Friday, March 10, 2017 3:45 PM
To: opnfv-tech-dis. 
Subject: [opnfv-tech-discuss] REMINDER: OPNFV Summit CFP Closes March 27

OPNFV Technical Community:

This is a reminder that the CFP for the OPNFV 
Summit
 (June 12-15, Beijing, China) closes Monday, March 27. We encourage you to 
prepare and submit a proposal by the deadline. The six primary tracks are the 
following:

  *   NFV Applications and Orchestration
  *   Testing, Infrastructure, and DevOps
  *   NFV Strategy and End User Stories
  *   NFV Platform Requirements
  *   Community and Upstream
  *   Futures and Research
Access the CFP 
Here

We look forward to your submissions. If you have any questions, please email 
eve...@opnfv.org.

Best,

Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org

New Report! OPNFV Plugfest at 
UNH-IOL
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] SDF (Scenario Descriptor File) Documentation

2017-03-23 Thread Dan Radez

Uli I thought of another question.

What about documentation?
Currently the install projects also house the documentation for the
scenario files.
Will that also become the responsibility of the scenario owners?
Will it be distributed independently from the installation project;s
documentation?

Thanks,
Radez

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

[opnfv-tech-discuss] Test Working Group Weekly Meeting

2017-03-23 Thread Cooper, Trevor

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:•   IRC channel: #opnfv-testperf @ Freenod
 e\n\nPhone numbers: 
 https://global.gotomeeting.com/305553637/numbersdisplay.html\n
 --\n•   Meeting time is based on UTC\n•\n
 •   Usual time (this timeslot): Every Thursday 15:00-16:00 UTC / 8:0
 0-9:00 PDT\nThursday GTM: https://global.gotomeeting.com/join/305553637\nA
 ccess Code: 305-553-637\n\nAPAC time: 2nd Wednesday of the month 8:00-9:00
  UTC replaces usual slot that week\nAPAC time: Wednesday GTM https://globa
 l.gotomeeting.com/join/778783733\nAccess Code: 778-783-733\n\n
 ---\n\nTest Working Group meeting AGENDA https://w
 iki.opnfv.org/display/meetings/TestPerf\n\nTest working group WIKI https:/
 /wiki.opnfv.org/display/testing\n•   Etherpad: https://etherpad.opnf
 v.org/p/testperf\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TH;WKST=SU
SUMMARY;LANGUAGE=en-US:[opnfv-tech-discuss] Test Working Group Weekly Meeti
 ng 
DTSTART;TZID=Pacific Standard Time:20170323T08
DTEND;TZID=Pacific Standard Time:20170323T09
UID:04008200E00074C5B7101A82E00890187A89A4A3D201000
 010008004170A0615C74DBDCE6619D7F7EB08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170323T141611Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1365821471
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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

[opnfv-tech-discuss] Cancelled: Test Working Group Weekly Meeting

2017-03-23 Thread Cooper, Trevor

BEGIN:VCALENDAR
PRODID://Yahoo//Calendar//EN
VERSION:2.0
METHOD:CANCEL
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Test Working Group Weekly Meeting
DESCRIPTION:?   IRC channel: #opnfv-testperf @ Freenode\n\nPhone numbers: https://global.go
 tomeeting.com/305553637/numbersdisplay.html\n-
 -\n?   Usual time (this timeslot): Every Thursday 15:00-16:00 
 UTC / 7:00-8:00 PST\nThursday GTM: https://global.gotomeeting.com/join/305
 553637\nAccess Code: 305-553-637\n\n--
 -\n?   APAC time: 2nd Wednesday of the month 8:00-9:00 UTC replaces us
 ual slot that week\nAPAC time: Wednesday GTM https://global.gotomeeting.co
 m/join/778783733\nAccess Code: 778-783-733\n\n
 ---\n\nTest Working Group meeting AGENDA https://wiki.opnfv.org/di
 splay/meetings/TestPerf\n\nTest working group WIKI https://wiki.opnfv.org/
 display/testing\n?   Etherpad: https://etherpad.opnfv.org/p/testperf\n
 \nTrevor Cooper\n+1 503-696-2096 (office) | +1 503-593-5249 (mobile) | tre
 vor.coo...@intel.com\n\n\n
CLASS:PUBLIC
DTSTART;TZID=Europe/London:20161103T14
DTEND;TZID=Europe/London:20161103T15
LOCATION:GTM and #opnfv-testperf @ Freenode
PRIORITY:0
SEQUENCE:2
STATUS:CONFIRMED
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
DTSTAMP:20161116T075849Z
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=opnfv-tech-discuss@lists.opnfv.org;ROLE=R
 EQ_PARTICIPANT;RSVP=FALSE:mailto:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Mario Torrecillas Rodriguez;ROLE=REQ_PART
 ICIPANT;RSVP=FALSE:mailto:mario.rodrig...@arm.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Andrew Veitch;ROLE=REQ_PARTICIPANT;RSVP=F
 ALSE:mailto:andrew.vei...@netcracker.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=morgan.richo...@orange.com;ROLE=REQ_PARTI
 CIPANT;RSVP=FALSE:mailto:morgan.richo...@orange.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Fatemeh Abdollahei;ROLE=REQ_PARTICIPANT;R
 SVP=TRUE:mailto:f.abdolla...@yahoo.com
ORGANIZER;CN="Cooper, Trevor":mailto:trevor.coo...@intel.com
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=1;BYDAY=TH
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-YAHOO-YID:yahoo.calendar.acl.writer
TRANSP:OPAQUE
STATUS:TENTATIVE
X-YAHOO-USER-STATUS:TENTATIVE
X-YAHOO-EVENT-STATUS:BUSY
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/London
TZURL:http://tzurl.org/zoneinfo/Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19810329T01
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19961027T02
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:-000115
TZOFFSETTO:+
TZNAME:GMT
DTSTART:18471201T00
RDATE:18471201T00
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19160521T02
RDATE:19160521T02
RDATE:19170408T02
RDATE:19180324T02
RDATE:19190330T02
RDATE:19200328T02
RDATE:19210403T02
RDATE:19220326T02
RDATE:19230422T02
RDATE:19240413T02
RDATE:19250419T02
RDATE:19260418T02
RDATE:19270410T02
RDATE:19280422T02
RDATE:19290421T02
RDATE:19300413T02
RDATE:19310419T02
RDATE:19320417T02
RDATE:19330409T02
RDATE:19340422T02
RDATE:19350414T02
RDATE:19360419T02
RDATE:19370418T02
RDATE:19380410T02
RDATE:19390416T02
RDATE:19400225T02
RDATE:19460414T02
RDATE:19470316T02
RDATE:19480314T02
RDATE:19490403T02
RDATE:19500416T02
RDATE:19510415T02
RDATE:19520420T02
RDATE:19530419T02
RDATE:19540411T02
RDATE:19550417T02
RDATE:19560422T02
RDATE:19570414T02
RDATE:19580420T02
RDATE:19590419T02
RDATE:19600410T02
RDATE:19610326T02
RDATE:19620325T02
RDATE:19630331T02
RDATE:19640322T02
RDATE:19650321T02
RDATE:19660320T02
RDATE:19670319T02
RDATE:19680218T02
RDATE:19720319T02
RDATE:19730318T02
RDATE:19740317T02
RDATE:19750316T02
RDATE:19760321T02
RDATE:19770320T02
RDATE:19780319T02
RDATE:19790318T02
RDATE:19800316T02
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19161001T03
RDATE:19161001T03
RDATE:19170917T03
RDATE:19180930T03
RDATE:19190929T03
RDATE:19201025T03
RDATE:19211003T03
RDATE:19221008T03
RDATE:19230916T03
RDATE:19240921T03
RDATE:19251004T03
RDATE:19261003T03
RDATE:19271002T03
RDATE:19281007T03

[opnfv-tech-discuss] Cancelled: Test Working Group Weekly Meeting

2017-03-23 Thread Cooper, Trevor

BEGIN:VCALENDAR
PRODID://Yahoo//Calendar//EN
VERSION:2.0
METHOD:CANCEL
BEGIN:VEVENT
SUMMARY:[opnfv-tech-discuss] Test Working Group Weekly Meeting
DESCRIPTION:?   IRC channel: #opnfv-testperf @ Freenode\n\nPhone numbers: https://global.go
 tomeeting.com/305553637/numbersdisplay.html\n-
 -\n?   Usual time (this timeslot): Every Thursday 15:00-16:00 
 UTC / 7:00-8:00 PST\nThursday GTM: https://global.gotomeeting.com/join/305
 553637\nAccess Code: 305-553-637\n\n--
 -\n?   APAC time: 2nd Wednesday of the month 8:00-9:00 UTC replaces us
 ual slot that week\nAPAC time: Wednesday GTM https://global.gotomeeting.co
 m/join/778783733\nAccess Code: 778-783-733\n\n
 ---\n\nTest Working Group meeting AGENDA https://wiki.opnfv.org/di
 splay/meetings/TestPerf\n\nTest working group WIKI https://wiki.opnfv.org/
 display/testing\n?   Etherpad: https://etherpad.opnfv.org/p/testperf\n
 \nTrevor Cooper\n+1 503-696-2096 (office) | +1 503-593-5249 (mobile) | tre
 vor.coo...@intel.com\n\n\n
CLASS:PUBLIC
DTSTART;TZID=Europe/London:20161103T14
DTEND;TZID=Europe/London:20161103T15
LOCATION:GTM and #opnfv-testperf @ Freenode
PRIORITY:0
SEQUENCE:2
STATUS:CONFIRMED
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
DTSTAMP:20161116T075849Z
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=opnfv-tech-discuss@lists.opnfv.org;ROLE=R
 EQ_PARTICIPANT;RSVP=FALSE:mailto:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Mario Torrecillas Rodriguez;ROLE=REQ_PART
 ICIPANT;RSVP=FALSE:mailto:mario.rodrig...@arm.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Andrew Veitch;ROLE=REQ_PARTICIPANT;RSVP=F
 ALSE:mailto:andrew.vei...@netcracker.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=morgan.richo...@orange.com;ROLE=REQ_PARTI
 CIPANT;RSVP=FALSE:mailto:morgan.richo...@orange.com
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=wonstonx;ROLE=REQ_PARTICIPANT;RSVP=TRUE:m
 ailto:wonst...@yahoo.com
ORGANIZER;CN="Cooper, Trevor":mailto:trevor.coo...@intel.com
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=1;BYDAY=TH
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
X-YAHOO-YID:yahoo.calendar.acl.writer
TRANSP:OPAQUE
STATUS:TENTATIVE
X-YAHOO-USER-STATUS:TENTATIVE
X-YAHOO-EVENT-STATUS:BUSY
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/London
TZURL:http://tzurl.org/zoneinfo/Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19810329T01
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19961027T02
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:-000115
TZOFFSETTO:+
TZNAME:GMT
DTSTART:18471201T00
RDATE:18471201T00
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19160521T02
RDATE:19160521T02
RDATE:19170408T02
RDATE:19180324T02
RDATE:19190330T02
RDATE:19200328T02
RDATE:19210403T02
RDATE:19220326T02
RDATE:19230422T02
RDATE:19240413T02
RDATE:19250419T02
RDATE:19260418T02
RDATE:19270410T02
RDATE:19280422T02
RDATE:19290421T02
RDATE:19300413T02
RDATE:19310419T02
RDATE:19320417T02
RDATE:19330409T02
RDATE:19340422T02
RDATE:19350414T02
RDATE:19360419T02
RDATE:19370418T02
RDATE:19380410T02
RDATE:19390416T02
RDATE:19400225T02
RDATE:19460414T02
RDATE:19470316T02
RDATE:19480314T02
RDATE:19490403T02
RDATE:19500416T02
RDATE:19510415T02
RDATE:19520420T02
RDATE:19530419T02
RDATE:19540411T02
RDATE:19550417T02
RDATE:19560422T02
RDATE:19570414T02
RDATE:19580420T02
RDATE:19590419T02
RDATE:19600410T02
RDATE:19610326T02
RDATE:19620325T02
RDATE:19630331T02
RDATE:19640322T02
RDATE:19650321T02
RDATE:19660320T02
RDATE:19670319T02
RDATE:19680218T02
RDATE:19720319T02
RDATE:19730318T02
RDATE:19740317T02
RDATE:19750316T02
RDATE:19760321T02
RDATE:19770320T02
RDATE:19780319T02
RDATE:19790318T02
RDATE:19800316T02
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19161001T03
RDATE:19161001T03
RDATE:19170917T03
RDATE:19180930T03
RDATE:19190929T03
RDATE:19201025T03
RDATE:19211003T03
RDATE:19221008T03
RDATE:19230916T03
RDATE:19240921T03
RDATE:19251004T03
RDATE:19261003T03
RDATE:19271002T03
RDATE:19281007T03
RDATE:19291006T03

[opnfv-tech-discuss] Canceled: Test Working Group Weekly Meeting

2017-03-23 Thread Cooper, Trevor

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='morgan.r
 icho...@orange.com':MAILTO:morgan.richo...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mingjian
 g Li':MAILTO:rexlee8...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Klozik, M
 artinX":MAILTO:martinx.klo...@intel.com
DESCRIPTION;LANGUAGE=en-US:Time is based on UTC so shifts with daylight sav
 ing … 15:00-16:00 UTC (8:00-9:00 PDT)\n\n
SUMMARY;LANGUAGE=en-US:Canceled: [opnfv-tech-discuss] Test Working Group We
 ekly Meeting 
DTSTART;TZID=Pacific Standard Time:20170323T07
DTEND;TZID=Pacific Standard Time:20170323T08
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
RECURRENCE-ID;TZID=Pacific Standard Time:20170323T07
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170323T141431Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:4
LOCATION;LANGUAGE=en-US:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: Test Working Group Weekly Meeting

2017-03-23 Thread Cooper, Trevor

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='morgan.r
 icho...@orange.com':MAILTO:morgan.richo...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mingjian
 g Li':MAILTO:rexlee8...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Klozik, M
 artinX":MAILTO:martinx.klo...@intel.com
DESCRIPTION;LANGUAGE=en-US:Time is based on UTC so shifts with daylight sav
 ing … 15:00-16:00 UTC (8:00-9:00 PDT)\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TH;WKST=SU
SUMMARY;LANGUAGE=en-US:Canceled: [opnfv-tech-discuss] Test Working Group We
 ekly Meeting 
DTSTART;TZID=Pacific Standard Time:20161103T07
DTEND;TZID=Pacific Standard Time:20161103T08
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170323T141429Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-US:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: [opnfv-tech-discuss] Test Working Group Weekly Meeting 
DTSTART;TZID=Pacific Standard Time:20161201T07
DTEND;TZID=Pacific Standard Time:20161201T08
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
RECURRENCE-ID;TZID=Pacific Standard Time:20161201T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170323T141429Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:3
LOCATION:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: [opnfv-tech-discuss] Test Working Group Weekly Meeting 
DTSTART;TZID=Pacific Standard Time:20170216T07
DTEND;TZID=Pacific Standard Time:20170216T08
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
RECURRENCE-ID;TZID=Pacific Standard Time:20170216T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170323T141429Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:3
LOCATION:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: [opnfv-tech-discuss] Test Working Group Weekly Meeting 
DTSTART;TZID=Pacific Standard Time:20170323T07
DTEND;TZID=Pacific Standard Time:20170323T08
UID:04008200E00074C5B7101A82E008C09E108F2530D201000
 01000247EC834F9ADE942A122892E9292F393
RECURRENCE-ID;TZID=Pacific Standard Time:20170323T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170323T141429Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:3
LOCATION:GTM and #opnfv-testperf @ Freenode
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:1461430240
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-23 Thread joehuang

Hi Valentin,

The networking topology is very clear from the picture.

If we want to make vIMS clearwater as close as to the production deployment in 
OpenStack multisite environment, what's the better networking proposal, for 
example, how many interfaces for one VM, i.e, how many network planes, how to 
process the north-south traffic, is SNAT/FIP needed?

Would like to check whether Tricircle networking automation can fulfill the 
demands for vIMS clearwater multi-site deployment.

Tricircle already supports several typical networking topology in 
https://docs.openstack.org/developer/tricircle/networking-guide.html#networking-scenario
 ( please note that VxLAN based bridge network between routers, VxLAN based 
cross OpenStack L2 network will be released in pike-1 by the end of next week )

And one more typical topology is expected to be released in pike-2: L3 
networking to support multiple north-south with east-west enabled: 
https://review.openstack.org/#/c/448359/

Best Regards
Chaoyi Huang (joehuang)

From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 23 March 2017 0:03
To: joehuang; Soni, Anand Kumar via opnfv-tech-discuss; Morales, Victor; Meimei
Subject: RE:答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hello, Chaoyi,

Oh ok, no problem.

 ~12 VMs with 2 Go and 1 VM with 4 Go per site

VNF networking:

  *   Only one network interface on each VM
  *   Communication between each local site network must be allowed without any 
NAT/PAT or floating ip.
  *   So, Each local VM must be able to communicate with the remote VM with his 
local ip.
  *   For the moment we use a openvpn tunnel to do that and the openvpn vms 
acts as router between local and remote networks (see the picture in 
attachment).

The goal is to replace openvpn tunnel with a better solution like bgp-mpls or 
other thing.

BR,
Valentin


De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 14:17
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across 
VIM

Hello, Valentin,

Very pleased to know the practice,
and very keen to discuss about it in more detail f2f.
But unfortuntealy I am not able to attend the
plugfest in Paris, could you please provide
reference material especial VNF's networking
topology, and then find a way for more detail disucssion.

BR
Chaoyi Huang(joehuang)

Sent from HUAWEI AnyOffice
发件人：valentin.bouc...@orange.com
收件人：黄朝意,Soni, Anand Kumar via opnfv-tech-discuss,Morales, Victor,梅玫
时间：2017-03-16 19:04:22
主题:RE:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

Last summer, In Orange Labs, we implemented vIMS ClearWater on a multi-site 
environment. We used  the single site implementation with Cloudify orchestrator 
and updated this to support multi-site environment. As presented by 
Metaswitch,
 vIMS Clearwater can support currently 2 sites deployment.

However, our implementation only works on 2 separate OpenStack platforms 
because we had no multisite platform at hand. So, the network between those 
sites is based on a OpenVPN tunnel. The multisite mechanism works but It would 
be nice to be able to integrate this on a real multisite platform.

Since OPNFV/Brahmaputra release, the deployment of this vIMS was included in 
functest project but for the moment, it only support one site.

I would attend the next OPNFV/Plugfest in Paris and it could be a great 
opportunity to improve this test-case using your multi-site solution.

Best Regards,
Valentin Boucher



De : opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de joehuang 
[joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 03:44
À : opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Objet : [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane for session/or other data

Re: [opnfv-tech-discuss] [multisite] weekly meeting of Mar.23

2017-03-23 Thread joehuang

Hello, Gerald,

Thank you for the mail. Will discuss this in next weekly meeting whether we can 
help.

Before rewriting the multisite part, can the old one still be put in place? The 
update can be done gradually. Someone already complains the missing of this 
guide.

Best Regards
Chaoyi Huang (joehuang)

From: Kunzmann, Gerald [kunzm...@docomolab-euro.com]
Sent: 22 March 2017 23:54
To: joehuang; opnfv-tech-discuss
Cc: openstack-operat...@lists.openstack.org; Heidi Joy Tretheway
Subject: RE: [multisite] weekly meeting of Mar.23

Dear multisite-Team,

FYI, the arch guide [1] in OpenStack is being rewritten, and the multi-site 
docs that were there are no longer there (see archived manuals in [2])
So there are currently no official docs on multi-site/region in OpenStack. In 
the Telco/NFV meeting it was suggested they could use some help writing those.

[1] https://docs.openstack.org/arch-design/
[2] 
https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/arch-design-to-archive/source

It seems the plan is to rewrite the arch guide piece by piece and they just 
haven't gotten to the multisite part yet, and could probably use some help. 
There is also potentially a NFV section to it.

Is there someone from multi-site team interested to work on this? Maybe you 
could discuss this in your meeting tomorrow.

I am not sure who would be the right person to contact, maybe Heidi from 
OpenStack heidi...@openstack.org?

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of joehuang
Sent: Mittwoch, 22. März 2017 06:04
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.23


Hello, team,



HA PTL FuQiao was invited to talk about multi-site requirements in this weekly 
meeting



Mar.23 2017 Agenda:

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion


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

Other topics are also welcome in the weekly meeting, please reply in this mail.


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

Re: [opnfv-tech-discuss] [release][danube] K8 scenario testing on Joid

2017-03-23 Thread Jose Lausuch

Hi,

Agreed. “Releasing” something that has not been –properly– tested is not a good 
practice. By “properly” I mean following the same procedures we use to verify 
all the other scenarios.

We need to emphasize that manual testing or “I run my own tests and it works” 
is not sufficient. Testing results must be shown and verified on CI following 
the OPNFV test mechanisms in order to consider it as a release candidate. Maybe 
we are too late to apply this to the k8 scenario which could be released as 
“Experimental”, as you suggest.

Regards,
Jose


From: Heather Kirksey [mailto:hkirk...@linuxfoundation.org]
Sent: Thursday, March 23, 2017 06:40 AM
To: Jose Lausuch
Cc: David McBride; Narinder Gupta; Fatih Degirmenci; TECH-DISCUSS OPNFV; Tapio 
Tallgren; Morgan Richomme (morgan.richo...@orange.com); Gaoliang (kubi); 
Raymond Paik
Subject: Re: [release][danube] K8 scenario testing on Joid

Hi all --

So first of all kudos to the JOID team for introducing this new technology -- 
it's an important step forward.

Secondly, obviously it doesn't make sense to run OpenStack tests against 
something that doesn't implement OpenStack.

I'm really worried, however, about "releasing" something that hasn't been 
tested at all. I know that often we document upstream bugs when tests aren't 
passing, etc., but not testing at all doesn't seem to be meeting a basic bar we 
should probably hold ourselves to for scenarios. Perhaps we can call this 
scenario something like "Experimental" or really point out that it's early 
days. Or we can continue to work this and put it out in Euphrates. I'd love to 
talk about this to the media, obviously, but I also want to feel comfortable 
that we're on solid footing and not overselling.

For my own edification, and apologies if this is a naive question, but how does 
this relate to the OpenRetriever project, which if I understood correctly, is 
the OPNFV project approved to focus on K8S and container requirements?

Cheers,
Heather





On Wed, Mar 22, 2017 at 6:14 AM, Jose Lausuch 
> wrote:
Hi,

I tend to agree about running the same set of test cases to all scenarios. But 
if the test frameworks are not prepared for a certain technology (like in this 
case K8), it doesn’t make sense to execute them. It’s a waste of time and we 
know beforehand that it will fail systematically.

We probably need to treat this case as an isolated scenario and define a 
different release criteria for it.

For Euphrates, we can think of adding support in Functest/Yardstick for 
containers (VIM abstraction layer or similar) but today we don’t have it.

Regards,
Jose



From: David McBride 
[mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, March 21, 2017 19:59 PM
To: Narinder Gupta; Fatih Degirmenci
Cc: TECH-DISCUSS OPNFV; Heather Kirksey; Tapio Tallgren; Morgan Richomme 
(morgan.richo...@orange.com); Gaoliang 
(kubi); Jose Lausuch; Raymond Paik
Subject: [release][danube] K8 scenario testing on Joid

This is a follow-up to a conversation on IRC (opnfv-release) earlier today.

When asked about disabling Functest and Yardstick for the new K8 scenarios on 
Joid, I agreed.  My reasoning was that I didn't want to delay release of new 
and potentially interesting scenarios.  I also know that functest and yardstick 
testing is not always applicable to every feature or configuration.  In 
addition, I was aware that the K8 scenarios had project-specific testing.

My initial thought was that the disabled tests would be documented in the 
release notes and that the project would be required to contribute tests to 
functest and yardstick for the following release.

Subsequently, after some discussion, I realized that I had made a mistake and 
that this is something that the test working group should weigh in on, at a 
minimum.

Therefore, please disregard my earlier direction about disabling the tests.  
The tests are still required for all scenarios until the test working group 
and/or the TSC indicate otherwise.

Let me know if you have any questions. Sorry for the confusion.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride



--
Heather Kirksey
Director, OPNFV
Mobile: +1.512.917.7938
Email/Google Talk: 
hkirk...@linuxfoundation.org
Skype: HeatherReneeKirksey
IRC: HKirksey

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

[opnfv-tech-discuss] [multisite]weekly meeting minutes of Mar.23

2017-03-23 Thread joehuang

Hello, team,

Weekly meeting minutes is as follows:

  *   Agenda

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion

  *   Minutes

  *
 *   CMCC multi-site 
requirements(joehuang,
 08:03:28)
*   3 layer NFV deployment architecture 
(joehuang,
 08:05:28)
functest 
issue(joehuang,
 08:52:07)
*   functest pass locally 
(joehuang,
 08:55:24)

  *   Link
 *   
Minutes:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.txt
 *   
Log:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html

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

Re: [opnfv-tech-discuss] [release][danube] Danube release status

2017-03-23 Thread Brady Allen Johnson


David,

I asked in an email previous to this the following questions:

Considering the Danube 1.0 release will be delayed by at least 1 week, what is 
the status of Milestones 9 and 10?

Milestone 9 is due today, March 22 and requires us to have all the JIRAs closed 
and/or assigned to subsequent releases. Does this still make sense if we will 
still be working on fixing problems?

Milestone 10 is due on Friday, March 24. This probably makes more sense to 
maintain, but then we might have MS10 before MS9.


Brady

-Original Message-
From: David McBride 
>
To: TECH-DISCUSS OPNFV 
>,
 opnfv-project-leads 
>
Cc: TSC OPNFV 
>
Subject: [opnfv-tech-discuss] [release][danube] Danube release status
Date: Wed, 22 Mar 2017 11:27:25 -0700

Team,

As you may be aware, the TSC determined on Tuesday that they do not have enough 
information to vote on the Danube 1.0 release.  Therefore:

  *   The vote on the release will be deferred to the next TSC meeting on Tues, 
March 28
  *   This means that we are no longer planning to release on Mon, March 27, as 
originally planned.
  *   A revised schedule for release will be developed based on input from 
scenario owners and test framework PTLs.
  *   The Release Manager will poll the scenario owners and test framework PTLs 
to assess the confidence level for releasing with different schedule offsets.

I will update this thread as I gather additional data and decisions are made.  
In the mean time, please continue to work hard toward the release, as I know 
you are.

Let me know if you have questions or concerns.

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

Re: [opnfv-tech-discuss] [VSPERF] Query regarding VSPERF trafficgen module

2017-03-23 Thread Klozik, MartinX

Hello Kritshekhar,

it seems to me, that you're using an outdated version of vsperf. This issue has 
been fixed on 10th of November 2016. Could you please update your repository 
(git pull) and switch to the recent version of master or stable/danube branch 
and test it again?

In case that your issue will persist, then please sent me following details for 
further debugging:

1)  exact vsperf version, i.e. git commit id

2)  your custom vsperf configuration; In case that you've modified any 
files inside conf/ directory, then please send me all the changes, you have 
performed as a diff against original versions; In case that you've modified 
also vsperf code, then please include also these changes, i.e. the full repo 
diff; e.g. git diff master..HEAD > debug.patch

3)  the full list of  vsperf options used for its execution and full vsperf 
output, e.g. ./vsperf -m trafficgen --trafficgen IxNet | tee debug.log

Thank you,
Martin


From: Cooper, Trevor
Sent: Wednesday, March 22, 2017 7:13 PM
To: Kritshekhar Jha ; opnfv-tech-discuss@lists.opnfv.org; 
test...@lists.opnfv.org; Klozik, MartinX 
Cc: Suvendu Mozumdar ; Mrinmoy Das 2 
Subject: RE: Query regarding VSPERF trafficgen module

Hi Kritshekhar

I am heads down with D-release but bringing this to attention of the VSPERF 
team and we will get back shortly.

/Trevor


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kritshekhar 
Jha
Sent: Wednesday, March 22, 2017 3:27 AM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
test...@lists.opnfv.org
Cc: Suvendu Mozumdar >; 
Mrinmoy Das 2 >
Subject: [opnfv-tech-discuss] Query regarding VSPERF trafficgen module

Hello OPNFV community members,

Thanks to the community for bringing this opportunity into the market.
Before coming to the issues, I would like to state the use case we trying to 
deploy and test.


*   We have a CENTOS7 system as a DUT deployed over a ESXI Hypervisor

*   We have cloned vswitchperf code over this and created the vsperf 
environment with the available script.

*   Currently we are using Ixia as the traffic gen, and we are progressing 
over that.

*   But if we use the 'trafficgen' mode and run it as ./vsperf -m 
trafficgen we are getting an error

AttributeError:  object has no attribute 'TOOLS'


On further debugging we have concluded that somehow TOOLS 
dictionary is not getting populated.

*   On the other hand if I run the test in normal mode TOOLS dictionary are 
getting populated and hence the control succeeded the conditional check where 
the trafficgen mode failed
[cid:image001.jpg@01D2A3A9.E75E1970]

*   Can you please guide what could the possible mistake here .

Thanks and Regards,
Kritshekhar Jha

--
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

[opnfv-tech-discuss] [qtip] Agenda for Weekly Meeting 2017-03-27

Re: [opnfv-tech-discuss] REMINDER: OPNFV Summit CFP Closes March 27

[opnfv-tech-discuss] Code Scan Tools Discussion

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday March 23

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

Re: [opnfv-tech-discuss] [release][danube] Danube release status

Re: [opnfv-tech-discuss] REMINDER: OPNFV Summit CFP Closes March 27

[opnfv-tech-discuss] SDF (Scenario Descriptor File) Documentation

[opnfv-tech-discuss] Test Working Group Weekly Meeting

[opnfv-tech-discuss] Cancelled: Test Working Group Weekly Meeting

[opnfv-tech-discuss] Cancelled: Test Working Group Weekly Meeting

[opnfv-tech-discuss] Canceled: Test Working Group Weekly Meeting

[opnfv-tech-discuss] Canceled: Test Working Group Weekly Meeting

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

Re: [opnfv-tech-discuss] [multisite] weekly meeting of Mar.23

Re: [opnfv-tech-discuss] [release][danube] K8 scenario testing on Joid

[opnfv-tech-discuss] [multisite]weekly meeting minutes of Mar.23

Re: [opnfv-tech-discuss] [release][danube] Danube release status

Re: [opnfv-tech-discuss] [VSPERF] Query regarding VSPERF trafficgen module

19 matches

Site Navigation

Mail list logo

Footer information