[opnfv-tech-discuss] Weekly Technical Discussion #82

[HU, BIN]

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="HU, BIN":MAILTO:bh5...@att.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=en-US:https://global.gotomeeting.com/join/819733085\n+
 1 (312) 757-3126 / Access Code: 819-733-085\n\n*Please note that UTC time 
 has changed to 13:00 after US changes to Daylight Savings Time*\n\nHello\,
 \n\nThis is our 82nd weekly technical discussion at 6am PDT / 9am EDT Thur
 sday March 16th\, 2017\, which is 13:00 UTC. We will discuss:\n-   A n
 ew Project Proposal - NextGen VIM Scheduler (NGVS) (Amar Kapadia)\n-   DevOps/Co
 ntinuous Delivery Release Model (Bryan Sullivan)\no
Scenario Descriptor in Scenario Consolidation (Ul
 rich Kleber)\no   Patch https://gerrit.opnfv.org/gerr
 it/#/c/28443\n\nYou can find your local time here ht
 tp://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-Technical-Dis
 cussion=20170316T13=1.\n\nPlease refer to https://wiki.opnfv.org/di
 splay/PROJ/Weekly+Technical+Discussion for details of dialing logistics an
 d tentative agenda.\n\nPlease let me know if you want to add anything to a
 genda for discussion in the community.\n\nFor your convenience:\n-   G
 oTo Meeting: https://global.gotomeeting.com/join/819733085\n-   You ca
 n also dial in using your phone:\no   United States (Long distance): +
 1 (312) 757-3126 / Access Code: 819-733-085\no   More phone numbers: h
 ttps://global.gotomeeting.com/819733085/numbersdisplay.html\n\nThanks\nBin
 \n\n\n
SUMMARY;LANGUAGE=en-US:Weekly Technical Discussion #82
DTSTART;TZID=Pacific Standard Time:20170316T06
DTEND;TZID=Pacific Standard Time:20170316T07
UID:04008200E00074C5B7101A82E008B0474929BE99D201000
 01000E7166A6B20986D48A0FA6F4727F0BB5B
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170311T005628Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-754305055
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

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

[Brandon Wick]

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] Summary of Weekly Technical Community Discussion Thursday March 09

[HU, BIN]

Hello community,



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



We primarily discussed a new project proposal 
SampleVNF. 
Through the discussion, group achieved consensus to recommend it for TSC 
creation review by addressing 4 issues:

1.   clarify feature-completeness v.s. production quality, and for testing 
purpose instead of commercial purpose;

2.   No conformance testing;

3.   No field deployment

4.   Apache 2 License will be used.



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



Next week on March 16th, we will discuss:

-  New Project Proposal - NextGen VIM Scheduler 
(NGVS) (Amar 
Kapadia)

-  DevOps/Continuous Delivery Release Model (Bryan 
Sullivan)

o   Scenario 
Descriptor
 in Scenario 
Consolidation 
(Ulrich Kleber)

o   Patch https://gerrit.opnfv.org/gerrit/#/c/28443

Thanks

Bin



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

[2] 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-14.01.html



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

[opnfv-tech-discuss] Agenda for the April OPNFV Board meeting

[Raymond Paik]

All,

Please find below agenda for the next Board meeting on April 7, 2017.

   - LF networking projects
   - EUAG update/discussions
   - CVP Update
   - TSC update/discussions
  - Danube release report
  - E-release planning
  - Cross community CI update
  - Devops model for OPNFV (Upstream Development on Master rather than
  Stable)
  - Projects health metrics
   - Board members only
  - Strategic planning topics
  - LF Networking projects harmonization
  - A Committee/budget review
  - Marketing committee update/discussions
  - AoB/Action items review

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] [FUNCTEST] [SNAPS-OO] Danube release

[morgan.richomme]

for Danube, it could somehow be considered as a part of Functest (it is
documented in Functest)
it fully make sense to branch it
if it would have been a cable labs external lib, we would have probably
used a git commit id to fix the version, keep it simple and branch...

for the next releases, other projects could use SNAPS as middleware,
then SNAPS_OO will have to follow release process (documentation,
meeting, ..)

/Morgan

Le 10/03/2017 à 21:13, David McBride a écrit :
> +Aric
>
> Let's branch to ensure functionality, but defer "official" inclusion
> of SNAPS-OO until the Euphrates release.  Thanks.
>
> David 
>
> On Fri, Mar 10, 2017 at 11:03 AM, Steven Pisarski
> > wrote:
>
> Hi Morgan and Jose,
>
>  
>
> As SNAPS-OO is not officially part of the Danube release but is
> pointed to by the Functest Dockerfile and the BRANCH variable. So
> my question to you and the overall community is whether or not
> SNAPS-OO should have a stable/danube branch cut or should FUNCTEST
> remove the $BRANCH from the git clone command? I believe a branch
> should be cut but wanted raise the potential issue before things
> start breaking.
>
>  
>
> Best,
>
> Steve
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> 
> https://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


-- 
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] [opnfv-project-leads] [release][danube] MS7 - stable branch window closes March 10

[David McBride]

Hi Brady,

See separate email for list.  SFC is planned for branching today.

David

On Fri, Mar 10, 2017 at 2:39 AM, Brady Allen Johnson <
brady.allen.john...@ericsson.com> wrote:

>
> Aric,
>
> Thanks for the info.
>
> Im assuming SFC is considered a "participating project". If not, can you
> still branch our project please?
>
> We're ready to go for MS7 and for the branching, so whenever you're ready,
> branch away from the latest commit :)
>
> Thanks,
>
> Brady
>
>
> -Original Message-
> *From*: David McBride  >
> *To*: Aric Gardner  >
> *Cc*: opnfv-project-leads  >,
> Raymond Paik  >,
> opnfv-tech-discuss@lists.opnfv.org  <%22opnfv-tech-disc...@lists.opnfv.org%22%20%3copnfv-tech-disc...@lists.opnfv.org%3e>>,
> Tapio Tallgren  >
> *Subject*: Re: [opnfv-project-leads] [release][danube] MS7 - stable
> branch window closes March 10
> *Date*: Fri, 3 Mar 2017 13:00:27 -0800
>
> Thanks, Aric.  Sorry for the confusion, Mark.
>
> David
>
> On Fri, Mar 3, 2017 at 9:02 AM, Aric Gardner  > wrote:
>
> Hi Mark, Yujun, David
>
> Only Gerrit admins can create branches. I will create the Danube
> branch from head of all participating projects on March 10th. If
> anything special needs to be done in this regard, (eg branching from a
> older ref) please contact me via irc or helpdesk
> And as a clarification, Mark you are correct, no tagging needs to be
> done for this milestone, tagging is for the final release.
>
> Regards,
> Aric
>
>
> On Fri, Mar 3, 2017 at 10:42 AM, Beierl, Mark 
> wrote:
> > Hello, David.
> >
> > The tagging instructions in the wiki [1] do not work, as it appears to
> > assume there is already a stable/danube branch created.  The instructions
> > appear to be for the release of Danube 1.0 after the work has been done
> in
> > stable/danube.
> >
> > Am I missing something?
> >
> > [1] https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instruction
> s+for+Danube
> >
> > Regards,
> > Mark
> >
> > Mark Beierl
> > Advisory Solutions Architect
> > Dell EMC | Office of the CTO
> > mobile +1 613 314 8106
> > mark.bei...@dell.com
> >
> > On Mar 2, 2017, at 14:28, David McBride 
> > wrote:
> >
> > PTLs,
> >
> > The stable branch window for Danube opened on February 17 (MS6).  The
> window
> > will close one week from Friday, on March 10 at 12 p.m. (PST).   Please
> plan
> > to branch your project by that date.
> >
> > Any projects not branched by the PTL by MS7 will be branched by LF
> (Aric).
> >
> > You may find tagging instructions here.
> >
> > Please contact me, or Aric, if you have any questions.  Thanks.
> >
> > David
> >
> > --
> > David McBride
> > Release Manager, OPNFV
> > Mobile: +1.805.276.8018
> > Email/Google Talk: dmcbr...@linuxfoundation.org
> > Skype: davidjmcbride1
> > IRC: dmcbride
> > ___
> > opnfv-project-leads mailing list
> > opnfv-project-le...@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
> >
> >
>
>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>
> ___
> opnfv-project-leads mailing 
> listopnfv-project-leads@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
>
>


-- 
*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] [FUNCTEST] [SNAPS-OO] Danube release

[David McBride]

+Aric

Let's branch to ensure functionality, but defer "official" inclusion of
SNAPS-OO until the Euphrates release.  Thanks.

David

On Fri, Mar 10, 2017 at 11:03 AM, Steven Pisarski 
wrote:

> Hi Morgan and Jose,
>
>
>
> As SNAPS-OO is not officially part of the Danube release but is pointed to
> by the Functest Dockerfile and the BRANCH variable. So my question to you
> and the overall community is whether or not SNAPS-OO should have a
> stable/danube branch cut or should FUNCTEST remove the $BRANCH from the git
> clone command? I believe a branch should be cut but wanted raise the
> potential issue before things start breaking.
>
>
>
> Best,
>
> Steve
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://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

[opnfv-tech-discuss] Dovetail planning and the weekly meeting minutes 3/10/2017

[Wenjing Chu]

Thanks for everyone in today’s dovetail call and esp. those who took action 
items. Thank you!

We reviewed the dovetail plan brainstorming inputs and started to summarize 
into agreements and action items 
https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan  in today’s weekly 
call. The minutes can be found here:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-10-14.00.html

As part of the action items, the test case requirement criteria will be updated 
based on inputs collected in the last few weeks on etherpad, wiki pages and 
mailing list. Dave Neary took this action item to summarize and make the 
updated wiki page ready for community review. The page is: 
https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Case+Requirements. Once 
updated and reviewed, these requirements will then be used as criteria when we 
start reviewing test cases for inclusion into the dovetail suite.

Openstack is a major component in opnfv’s stacks and they have developed 
defcore/refstack for interoperability testing. This part will be incorporated 
as a whole for dovetail, and this model of upstream collaboration could be 
extended in the future. Some technical questions are still open but developers 
are making good progress to close them.

A draft milestone time table is also in the plan page 
https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan. We are still 
working on validation of assumptions and resource assignments; you are welcome 
to review the milestones and give your inputs.

As a last note, we are to finalize the plan and present to TSC for review on 
March 21 call, so if you like to give input please engage now. Next week is the 
only time we have. Thanks!

Regards
Wenjing



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Wenjing Chu
Sent: Friday, March 03, 2017 11:08 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Dovetail planning and the weekly meeting minutes

Thanks for everyone in today's call.

In order to reach to broader audience, I did not use the [dovetail] filter in 
this email. As noted in the TSC call as well, dovetail planning should be of 
interest to many of you in the community. I like to also invite/encourage 
anyone interested joining the call or get on IRC or wiki as well.

Today's call was mostly focused on reaching on a high level plan for launching 
CVP based on Danube release. The etherpad 
https://etherpad.opnfv.org/p/Dovetail_Danube_Planning had been used for 
brainstorming. We have moved to the wiki for editing/tracking now. The new wiki 
page is: https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan. All 
information in the etherpad had been copied under the section "brainstorming". 
Please continue to contribute in the wiki page.

I enclose the meeting minutes here: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-03-14.00.html

A couple of things did not get captured in the minute. One is the https issue 
Tomofumi brought up. The action item is for him/dovetail/functest to come back 
with a solution proposal and JIRA tickets next week.

I also took an action item to merge the google doc milestone timetable to the 
wiki. That's now done and also in 
https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan. This table 
outlines overall project timeline.

The team also has a collection action item to clean up old/obsolete JIRA 
tickets and put JIRA in a clean starting point. We will continue on the review 
of the plan on the next call March 10. I expect we come to some conclusions 
that we can then summarize and refine.

Thanks again and please follow up on the action items.

Cheers
Wenjing


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

Re: [opnfv-tech-discuss] MS7 - stable branch TODAY at 12 p.m. (PST)

[David McBride]

Here's the list of projects that will be branched:

   1. apex
   2. armband
   3. availability
   4. barometer
   5. bottlenecks
   6. compass4nfv
   7. copper
   8. doctor
   9. domino
   10. fds
   11. fuel
   12. functest
   13. ipv6
   14. joid
   15. kvmfornfv
   16. models
   17. multisite
   18. netready
   19. opera
   20. opnfvdocs
   21. orchestra
   22. parser
   23. promise
   24. qtip
   25. sdnvpn
   26. securityscanning
   27. sfc
   28. storperf
   29. ves
   30. vswitchperf
   31. yardstick


On Fri, Mar 10, 2017 at 8:22 AM, David McBride  wrote:

> In about 3.5 hours, the stable branch window will be closed for Danube.
> Let me know if you have any questions.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



-- 
*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] [functest][dovetail] OpenStack HTTPS transport support in functest/dovetail

[Wenjing Chu]

+1

Does yardstick have the same issue? If it does, can we have a fix too in 
Danube. Thanks.

Wenjing

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Julien
Sent: Thursday, March 09, 2017 7:27 PM
To: yaohelan ; Tomofumi Hayashi ; 
trevor.coo...@intel.com; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS 
transport support in functest/dovetail

Hi all,

Maybe this will be a good guideline for all OPNFV projects when they consume or 
provide APIs.

Regards,
Julien



yaohelan >于2017年3月10日周五 
上午11:15写道：
Hi Tomofumi,

I am a committer of Functest. I will try to enable HTTPS for Functest.

There is a JIRA item tracking the status.
https://jira.opnfv.org/browse/FUNCTEST-757


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Tomofumi Hayashi
Sent: Thursday, March 02, 2017 9:14 PM

To: trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS transport 
support in functest/dovetail

Hi folks,

Let me clarify HTTPS support status and plan of functest/yardstick/dovetail.

I tried to run functest/dovetail against TripleO deployment and find that 
functest script, leveraged by dovetail, only works with HTTP (!= HTTPS) for 
OpenStack API (see verify_connectivity(): functest/ci/check_os.py). In 
addition, more modification is required certificate (such as self-signed one).

At that time, OPNFV testing project is mainly consumed by OPNFV platforms (e.g. 
Apex). But in the future, at least dovetail should be used for C (compliance 
and certification) in various OpenStack platform and some of them does not 
support HTTP transport for OpenStack API (mostly due to security reason). So I 
suppose we should support HTTPS OpenStack API in dovetail and functest.

What do you think about it?

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

[opnfv-tech-discuss] Weekly SNAPS-OO Technical Discussion

[Steven Pisarski]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Mountain Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Steven Pisarski:MAILTO:s.pisar...@cablelabs.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:Hello\,\n\n\n\nPlease join our weekly technical 
 discussion for the SNAPS-OO project.\n\n\n\nBest regards\,\n\nSteve Pisars
 ki\n\nArchitect\n\nCableLabs\n\n\n\nJoin from PC\, Mac\, Linux\, iOS or An
 droid: https://cablelabs.zoom.us/j/314610225\n\n\n\nOr iPhone one-tap (US 
 Toll):  +16465588656\,314610225# or +14086380968\,314610225#\n\n\n\nOr Tel
 ephone:\n\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll
 )\n\n+971 4 550 8389 (United Arab Emirates Toll)\n\n(010) 87833177
  (China Toll)\n\n+62 21 2188 9017 (Indonesia Toll)\n\n+91 22 62 19
 2 563 (India Toll)\n\n+91 22 71 279 163 (India Toll)\n\n+63 2395 3
 500 (Philippines Toll)\n\n+66 60 003 5790 (Thailand Toll)\n\n+886 
 277 417 473 (Taiwan Toll)\n\n+84 8 4458 2373 (Vietnam Toll)\n\n+1 
 855 880 1246 (US Toll Free)\n\n+1 877 369 0926 (US Toll Free)\n\nM
 eeting ID: 314 610 225\n\nInternational numbers available: https://cab
 lelabs.zoom.us/zoomconference?m=Tzbe-cSaiGiwP4ayLCpsevbFjE3dZ_xx\n\n\n\nOr
  an H.323/SIP room system:\n\nH.323:\n\n162.255.37.11 (US West
 )\n\n162.255.36.11 (US East)\n\n221.122.88.195 (China)\n\n
 115.114.131.7 (India)\n\n213.19.144.110 (EMEA)\n\nMeet
 ing ID: 314 610 225\n\n\n\nSIP: 314610...@zoomcrc.com\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
UID:A6B3D2AA-9A4E-4D79-B577-9AD2903332C2
SUMMARY;LANGUAGE=en-US:Weekly SNAPS-OO Technical Discussion
DTSTART;TZID=Mountain Standard Time:20170315T073000
DTEND;TZID=Mountain Standard Time:20170315T083000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170310T162554Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://cablelabs.zoom.us/j/314610225
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115194895
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
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
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] MS7 - stable branch TODAY at 12 p.m. (PST)

[David McBride]

In about 3.5 hours, the stable branch window will be closed for Danube.
Let me know if you have any questions.

David

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

Re: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS transport support in functest/dovetail

[yaohelan]

The patch about Functest being able to run on OpenStack through https is 
submitted
https://gerrit.opnfv.org/gerrit/#/c/30253

Your feedback is appreciated.

From: yaohelan
Sent: Friday, March 10, 2017 11:15 AM
To: 'Tomofumi Hayashi' ; trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS 
transport support in functest/dovetail

Hi Tomofumi,

I am a committer of Functest. I will try to enable HTTPS for Functest.

There is a JIRA item tracking the status.
https://jira.opnfv.org/browse/FUNCTEST-757


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tomofumi 
Hayashi
Sent: Thursday, March 02, 2017 9:14 PM
To: trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS transport 
support in functest/dovetail

Hi folks,

Let me clarify HTTPS support status and plan of functest/yardstick/dovetail.

I tried to run functest/dovetail against TripleO deployment and find that 
functest script, leveraged by dovetail, only works with HTTP (!= HTTPS) for 
OpenStack API (see verify_connectivity(): functest/ci/check_os.py). In 
addition, more modification is required certificate (such as self-signed one).

At that time, OPNFV testing project is mainly consumed by OPNFV platforms (e.g. 
Apex). But in the future, at least dovetail should be used for C (compliance 
and certification) in various OpenStack platform and some of them does not 
support HTTP transport for OpenStack API (mostly due to security reason). So I 
suppose we should support HTTPS OpenStack API in dovetail and functest.

What do you think about it?

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

[opnfv-tech-discuss] [armband] Weekly Meetings Established for ARMBand project

[Bob Monkman]

Hello Armbanders, just confirming that we will have our meeting today to go 
over where we are at in readiness for Danube release.

Talk to you shortly.

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] FW: OPNFV Barometer project

[Tahhan, Maryam]

Hi

Can you please remove committer rights for Christoph Meyer for the barometer 
project, please see the email below

BR
Maryam

From: Christoph Meyer [mailto:christoph.me...@ericsson.com]
Sent: Wednesday, March 8, 2017 3:44 PM
To: Tahhan, Maryam 
Subject: OPNFV Barometer project

Hi Maryam,

I just noticed that I am still listed as committer for the barometer project. 
Unfortunately my assignments do not include OPNFV work any more.

In consequence I would like to step down from this committer role in order to 
have this list reflect the reality.

Regards,
Christoph


[Ericsson]
CHRISTOPH MEYER Dr.
Expert Data Center Networking
PDU Cloud Solutions & Architecture

Ericsson
Ericsson-Allee 1
52134 Herzogenrath, Germany
Phone +49-2407-575-3323
Mobile +49-173-7079830
Office +49-173-7079830
christoph.me...@ericsson.com
www.ericsson.com


[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson GmbH, registered office in Dusseldorf, Germany, Trade 
Register: Amtsgericht Dusseldorf (HRB 33012). Managing Directors: Stefan Koetz 
(Chairman) and Bernd Mellinghaus. Supervisory Board: Jan Ögren (Chairman).  
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer

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

[opnfv-tech-discuss] [OPNFV] minutes weekly meeting 410/03

[morgan.richomme]

http://irc.opnfv.fr/opnfv-orange/2017/opnfv-orange.2017-03-10-10.01.html

- Note 1: etherpad available to collect ideas/sync proposals for the
Beijing Summit (deadline March 27th)
http://etherpad.rd.francetelecom.fr/p/CfpBeijing

@Eric I put your proposals here

@Ruan => your demo will be in the PoC area?
any other possible PoCs?

We planned a discussion next friday and last submits on the 24th
feel free to join Friday weekly meeting if you have any question

- Note 2: lots of people in copy this week (involved in the CFP
Beijing), if you want to receive the weekly meeting minutes and you are
note part of opnfv-tech, please tell me I will add you to the mailing list

_

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] [opnfv-project-leads] [release][danube] MS7 - stable branch window closes March 10

[Brady Allen Johnson]

Aric,

Thanks for the info.

Im assuming SFC is considered a "participating project". If not, can you still 
branch our project please?

We're ready to go for MS7 and for the branching, so whenever you're ready, 
branch away from the latest commit :)

Thanks,

Brady


-Original Message-
From: David McBride 
>
To: Aric Gardner 
>
Cc: opnfv-project-leads 
>,
 Raymond Paik 
>,
 opnfv-tech-discuss@lists.opnfv.org 
>,
 Tapio Tallgren 
>
Subject: Re: [opnfv-project-leads] [release][danube] MS7 - stable branch window 
closes March 10
Date: Fri, 3 Mar 2017 13:00:27 -0800

Thanks, Aric.  Sorry for the confusion, Mark.

David

On Fri, Mar 3, 2017 at 9:02 AM, Aric Gardner 
> wrote:
Hi Mark, Yujun, David

Only Gerrit admins can create branches. I will create the Danube
branch from head of all participating projects on March 10th. If
anything special needs to be done in this regard, (eg branching from a
older ref) please contact me via irc or helpdesk
And as a clarification, Mark you are correct, no tagging needs to be
done for this milestone, tagging is for the final release.

Regards,
Aric


On Fri, Mar 3, 2017 at 10:42 AM, Beierl, Mark 
> wrote:
> Hello, David.
>
> The tagging instructions in the wiki [1] do not work, as it appears to
> assume there is already a stable/danube branch created.  The instructions
> appear to be for the release of Danube 1.0 after the work has been done in
> stable/danube.
>
> Am I missing something?
>
> [1] https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Danube
>
> Regards,
> Mark
>
> Mark Beierl
> Advisory Solutions Architect
> Dell EMC | Office of the CTO
> mobile +1 613 314 8106
> mark.bei...@dell.com
>
> On Mar 2, 2017, at 14:28, David McBride 
> >
> wrote:
>
> PTLs,
>
> The stable branch window for Danube opened on February 17 (MS6).  The window
> will close one week from Friday, on March 10 at 12 p.m. (PST).   Please plan
> to branch your project by that date.
>
> Any projects not branched by the PTL by MS7 will be branched by LF (Aric).
>
> You may find tagging instructions here.
>
> Please contact me, or Aric, if you have any questions.  Thanks.
>
> David
>
> --
> David McBride
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: 
> dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
> ___
> opnfv-project-leads mailing list
> opnfv-project-le...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
>
>




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

___
opnfv-project-leads mailing list
opnfv-project-le...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads

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

Re: [opnfv-tech-discuss] [SFC] Creating the stable/danube branch today at 17:30 GMT+1

[Brady Allen Johnson]

Correction: Aric Gardner, the OPNFV sys admin, will create the branches for us 
today.

Regards,

Brady

-Original Message-
From: Brady Allen Johnson 
>
To: opnfv-tech-discuss@lists.opnfv.org 
>
Subject: [opnfv-tech-discuss] [SFC] Creating the stable/danube branch today at 
17:30 GMT+1
Date: Fri, 10 Mar 2017 09:29:13 +


I plan to create the stable/danube branch for OPNFV SFC today at 17:30 GMT+1. 
This is the final piece missing for us to complete Danube MS7.

If anyone has any objections with that, please let me know ASAP.

Regards,

Brady


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

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

[opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

[Julien]

Hi Sofia,

Currently there are two verify docs jobs in OPNFV:
1. opnfv-docs-verify-master
2. docs-verify-rtd-master


The first job existed earlier before the *opnfvdocs* project created, and
they works for the same purpose. Shall we merge them two?

The other issues existed :
1. The job 'docs-verify-rtd-master' uses submodule to fetch all the OPNFV
projects' docs triggered by any project, which makes the projects affected
by each other. Any issue in one project will affect others. It is not
necessary. This will also make the building process occupy more time. The
jobs 'opnfv-docs-verify-master' does well.
2. opnfv-docs-verify-master does not output the building result to the
artifactory, so we can not check the results.
3. the jobs of opnfvdoc fixed the Jenkins slave's label with lf-build1 or
lf-build2 .  Currently, the resources in lf-build are in short and the many
jobs are in the queue. Shall we set it to opnfv-build to all the jobs.
4. There are lots of warnings in logs of Job 'docs-verify-rtd-master'.

In next release I hope I can introduce sphinx docker to faster current
verify job.

Best Regards,
Julien



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

[opnfv-tech-discuss] [SFC] Creating the stable/danube branch today at 17:30 GMT+1

[Brady Allen Johnson]

I plan to create the stable/danube branch for OPNFV SFC today at 17:30 GMT+1. 
This is the final piece missing for us to complete Danube MS7.

If anyone has any objections with that, please let me know ASAP.

Regards,

Brady

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