[opnfv-tech-discuss] Announcing the next OPNFV Plugfest

[Raymond Paik]

All,

Happy to announce that the next Plugfest will be hosted by Orange near
Paris during the week of April 24th.  I will kick off the Plugfest planning
meeting in February and will also create the wiki page to start the
planning activities.

Looking forward to our first Plugfest outside of the US!

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] 答复: [dovetail]call for more dovetail contributors and committers for the PTL update

[Tianhongbo]

Hi zhihui：

Thanks for your interests, I will add you as the contributor now.

Best regards

hongbo

发件人: wu.zhih...@zte.com.cn [mailto:wu.zhih...@zte.com.cn]
发送时间: 2017年1月25日 10:15
收件人: Tianhongbo
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: 答复: [opnfv-tech-discuss] [dovetail]call for more dovetail contributors and 
committers for the PTL update


Hi hongbo,

  I would like to contribute dovetail.



Thanks!



吴之惠 wuzhihui



虚拟化开发七部/无线研究院/无线产品经营部 NIV Development Dept. VII/Wireless Product R＆D 
Institute/Wireless Product Operation


[cid:image001.gif@01D27713.F9919F80]

[cid:image002.gif@01D27713.F9919F80]
上海市浦东新区碧波路889号/上研D座2楼
R Building, Bibo Road 889, Zhangjiang Hi-tech Park,
New Pudong District, Shanghai, P..R.China, 518057
T: +86 021 68896831
M: +86 18121012137
E: wu.zhih...@zte.com.cn
www.zte.com.cn

原始邮件
发件人： ＜hongbo.tianhon...@huawei.com＞;
收件人： ＜opnfv-tech-discuss@lists.opnfv.org＞;
日 期 ：2017年01月25日 08:57
主 题 ：[opnfv-tech-discuss] [dovetail]call for more dovetail contributors and 
committers for the PTL update


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

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

[Goutham Pratapa]

Hi all, 

I have updated the document with the api structure and a trivial change in DB 
structure please go through the document 

and provide your comments.

https://docs.google.com/document/d/1fXvhUj1v16TLe72UsWi6CHZxwBmePWckam2_u9fr4Qk/edit


Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 01/16/2017 12:35AM
Cc: "caizhiyuan (A)" , opnfv-tech-discuss   
, "Dimitri Mazmanov" 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all, 

I have updated the document with the SYNC_JOB structure the table we are going 
to follow for the keypair sync job.

https://docs.google.com/document/d/1fXvhUj1v16TLe72UsWi6CHZxwBmePWckam2_u9fr4Qk/edit#

I have updated the document with ER diagram and brief description. We have to 
act fast to meet our deadline. 

So please provide your feedback and comments. Our target is to make the keypair 
syncing an async approach between client and engine.

at least we will give it a try to complete.

In the mean while i will try and convert all the tempest test cases with python 
clients.To help that it will be better if we can get this commit reviewed 
https://review.openstack.org/#/c/418412/

and close the commit soon to complete kingbird sdk as soon as possible. :)

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 01/13/2017 11:45AM
Cc: "caizhiyuan (A)" , opnfv-tech-discuss   
, "Dimitri Mazmanov" 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi Joe, 

I have created a new doc. 

https://docs.google.com/document/d/1fXvhUj1v16TLe72UsWi6CHZxwBmePWckam2_u9fr4Qk/edit#

and shared it with respective gmail id's please go through and provide your 
comments. 

Thanks
Goutham


-joehuang  wrote: -
To: Goutham Pratapa 
From: joehuang 
Date: 01/13/2017 09:35AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss  

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

  
 Hello, Goutham, 

  
Thank you for the update. But the documentation needs to clean, there are lots 
of comment, and inconsistency in several places. Don't know which updates are 
new one or old one.
 

 
 
 
Best Regards Chaoyi Huang (joehuang)   
  
From: Goutham Pratapa [goutham.prat...@tcs.com]
 Sent: 13 January 2017 1:12
 To: joehuang
 Cc: Ashish singh; caizhiyuan (A); opnfv-tech-discuss
 Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach
 
  
 
 
Hi all,  

  
I request you all to go through the document and provide comments.. 

  
I have made changes regarding api structure. 

  
Thanks 
 
Goutham
   
 
 -Goutham Pratapa/HYD/TCS wrote: - 
 
To: joehuang 
 From: Goutham Pratapa/HYD/TCS
 Date: 01/06/2017 05:40PM
 Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

 Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach
 
 Hi all, 
 
 I have changed the document. based on our discussion to remove User-id from 
Url Path.
 
 Thanks 
Goutham
  
 
 -Goutham Pratapa/HYD/TCS wrote: - 
 
To: joehuang 
 From: Goutham Pratapa/HYD/TCS
 Date: 12/09/2016 10:29AM
 Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

 Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach
 
 Hi all, 
 
 I changed the document following are the links 
 
 
https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A03Vdcc
 
 
https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A4VEf0U
 
 
https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A0y2I0c
 
 Changed the document and Please provide your feedback so that we can keep lock 
on the things to be implemented for now.
 
 and start implementation based upon the locked document.
 
 Thanks 
Goutham
  
 
 -joehuang  wrote: - 
 
To: Goutham Pratapa 
 From: joehuang 
 Date: 12/09/2016 07:51AM
 Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

 Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach
 
 
Hello, Goutham, 

  
For os-sync API, two suggestions: 

  
1. we need to use POST but not put for this action 
2. Even 

[opnfv-tech-discuss] [MANO] Meeting #17 Jan 25 UTC 15.00 / PST 7.00

[Prakash Ramchandran]

Please join us tomorrow for MANO WG Meeting 17

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Jan  25, Wednesday : 15.00 UTC /7.00 PST  Meeting 17

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

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

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)
https://global.gotomeeting.com/join/843517045
1.Agenda:
2.1.Agenda bashing
3.2.Review of last meeting (#15) and actions
a. a.Priority for D 
- completed
b.b. Review of VNF 
on-boarding - Is 
anyone Interested in monitoring Intern for VNF 
On-boarding
c. c. Code review for VNF 
testing - Completed  common testing 
for vIMS (Orchestra to use Orchestration and Opera to use Compass Installer for 
testing vIMS as VNF use case)
d.d. Scenario conclusion - Orchestra - (???) , 
Opera(os-onos-nofetaure-ha?), Domino (os-...), Model (None), , Parser(?), - Do 
we have a path to no scenario? Whats input from Installers on Scenario for MANO?
e.e.  Release E (Move left out D to E +??? for consistency?)
f. f. ABOT framewrok for BDD has impact beyond MANO and hence moved the 
discussions to Tech Meeting - Completed Transfer to Weekly Tech for Thursday.
4.3.Architecture 
comparison and LCM.
5.4.OSM & ETSI NFV updates - Refer [ RP ] in Meeting 15 -2016
6.5.Report from upstream (OpenBaton, Open-O, openECOMP, JuJu, Tacker, 
OSM/Plug-test) and its impact on MANO WG
7.6.MANO related tests for Dovetail beyond C for D based on what we have 
and who will volunteer to get this moving?
8.7.Continuing on Reviewing Best Practices for VNF On-boarding & LCM based 
on current community project status?
9.8.Actionable Items and Agreement summary recording



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

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks


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

Re: [opnfv-tech-discuss] New OPNFV Project Proposal - SNAPS-OO

[HU, BIN]

Great and thank you for new project proposal.

I will put it on the agenda of our weekly technical discussion next week (Feb 
2nd).

Thanks
Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Steven Pisarski
Sent: Tuesday, January 24, 2017 12:23 PM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Cc: Kevin Kershaw 
Subject: [opnfv-tech-discuss] New OPNFV Project Proposal - SNAPS-OO

Hello all,

We just completed our proposal for a new OPNFV Project named SNAPS-OO 
(https://wiki.opnfv.org/display/PROJ/SNAPS-OO). Please feel free to contact 
Randy, Kevin, or myself if you should have any questions.

Best regards,
Steve Pisarski
Architect
CableLabs
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Infra Working Group Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.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
DESCRIPTION;LANGUAGE=en-US:The "Infra Working Group" plans and tracks infra
 structure cross project initiatives. We report our efforts up to the TSC t
 o ensure the community is able to provide sufficient resources for develop
 ment and release infrastructure.\n\nTopics and meeting agenda at https://w
 iki.opnfv.org/display/INF/Infra+Working+Group\n\n•   Weekly on Wedne
 sday at 8:00 PST  or 16:00 UTC\n•   GTM Link https://global.gotomeet
 ing.com/join/819733085\n•   Minutes at Meetings#InfraWorkingGroupMee
 ting\n•   IRC #opn
 fv-meeting - freenode.net\n•   Chaired by Jack Morgan (meetings chai
 red by Infra PTLs on a 2-month basis)\n\nYou can also dial in using your p
 hone with Access Code: 819-733-085\n•   United States +1 (312) 757-3
 126\n•   Australia +61 2 8355 1040\n•   Austria +43 7 2088 003
 4\n•   Belgium +32 (0) 28 93 7018\n•   Canada +1 (647) 497-935
 0\n•   Denmark +45 69 91 88 64\n•   Finland +358 (0) 923 17 05
 68\n•   France +33 (0) 170 950 592\n•   Germany +49 (0) 692 57
 36 7211\n•   Ireland +353 (0) 15 360 728\n•   Italy +39 0 247 
 92 13 01\n•   Netherlands +31 (0) 208 080 219\n•   New Zealand
  +64 9 280 6302\n•   Norway +47 75 80 32 07\n•   Spain +34 911
  82 9906\n•   Sweden +46 (0) 853 527 836\n•   Switzerland +41 
 (0) 435 0167 13\n•   United Kingdom +44 (0) 330 221 0086\n\n
RRULE:FREQ=WEEKLY;UNTIL=20170222T16Z;INTERVAL=1;BYDAY=WE;WKST=SU
SUMMARY;LANGUAGE=en-US:Infra Working Group Meeting
DTSTART;TZID=Pacific Standard Time:20170111T08
DTEND;TZID=Pacific Standard Time:20170111T09
UID:04008200E00074C5B7101A82E00880B1D4E1646BD201000
 010005E212FD6F7EB6043B4F4B301B08B7E1F
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170125T024402Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:GTM and IRC #opnfv-meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1531582433
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] 答复: [dovetail]call for more dovetail contributors and committers for the PTL update

[wu.zhihui1]

Hi hongbo,

  I would like to contribute dovetail. 





Thanks!







吴之惠 wuzhihui






虚拟化开发七部/无线研究院/无线产品经营部 NIV Development Dept. VII/Wireless Product R＆D 
Institute/Wireless Product Operation









上海市浦东新区碧波路889号/上研D座2楼 
R Building, Bibo Road 889, Zhangjiang Hi-tech Park, 
New Pudong District, Shanghai, P..R.China, 518057 
T: +86 021 68896831
M: +86 18121012137
E: wu.zhih...@zte.com.cn 
www.zte.com.cn












原始邮件



发件人： ＜hongbo.tianhon...@huawei.com＞
收件人： ＜opnfv-tech-discuss@lists.opnfv.org＞
日 期 ：2017年01月25日 08:57
主 题 ：[opnfv-tech-discuss] [dovetail]call for more dovetail contributors and 
committers for the PTL update







Hi all:


 


The CVP is very import for the OPNFV community and has been approved by the 
board. So the dovetail moves more faster than before.


With the development of the dovetail, there are more and more work needed to be 
done and it needs more and more contributors and committers for the progress.


Here, the dovetail team calls for more contribution in the whole community to 
join dovetail.


With the contribution, there will be more committers selected.


Soon or later. As usually, the PTL will be update with the progress of project. 
I will step down the PTL. And the new PTL will be selected.


the dovetail will move more regularly. And more and more people will join the 
dovetail.


 


Best regards


 


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

[opnfv-tech-discuss] [dovetail]call for more dovetail contributors and committers for the PTL update

[Tianhongbo]

Hi all:

The CVP is very import for the OPNFV community and has been approved by the 
board. So the dovetail moves more faster than before.
With the development of the dovetail, there are more and more work needed to be 
done and it needs more and more contributors and committers for the progress.
Here, the dovetail team calls for more contribution in the whole community to 
join dovetail.
With the contribution, there will be more committers selected.
Soon or later. As usually, the PTL will be update with the progress of project. 
I will step down the PTL. And the new PTL will be selected.
the dovetail will move more regularly. And more and more people will join the 
dovetail.

Best regards

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

[opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

[Tianhongbo]

Hi Jose:

As you mentioned, there will be discussion about the more detail of the L3VPN 
with L3VPN team to check if the L3VPN can be included in the dovetail area now.

There are some requirements from the dovetail wiki page: 
https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Case+Requirements

Look forward to your reply.

Best regards

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

Re: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

[Yujun Zhang]

That would be an interesting topic.

We have already started something on inspector[1]. We may create one for
monitor as well.

[1]: https://jira.opnfv.org/browse/DOCTOR-73

On Wed, Jan 25, 2017 at 1:12 AM Aaron Smith  wrote:

> Hi,
>   Would there be interest in a separate meeting to discussion what an
> "ideal" monitoring framework might look like.
>
> Topics might include:
>   - Polling vs Event capture
>   - Platform independent monitor agent
> - Network Interfaces
> - Kernel events
> - VM / Container monitoring
> - Common bus for Events / Telemetry / Config
>   -  Common Object model
> - Agent configuration
> - Performance
>- <<50ms
>
> This would be an informal brainstorming activity with more emphasis on
> concepts than existing projects (unless necessary).
>
> Thoughts?
>
> Aaron
>
> --
> Aaron Smith | Senior Principal Software Engineer
> NFV Partner Engineering
> Red Hat
> aasm...@redhat.com
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> 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] FW: Checking in the the Policytest project in OPNFV.

[Raymond Paik]

Thanks Bryan...

People maybe able to see this in the email chain, but it also looks like 2
(out of the original 5) committers are no longer active in OPNFV.  With no
activity since formation, there shouldn't be any impact to existing OPNFV
projects.

Ray

On Tue, Jan 24, 2017 at 9:32 AM, SULLIVAN, BRYAN L  wrote:

> Hi all,
>
>
>
> If there are no objections, it’s proposed that the PolicyTest project be
> terminated, as there has been no activity since its formation.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org]
> *Sent:* Tuesday, January 24, 2017 9:28 AM
>
> *To:* SULLIVAN, BRYAN L 
> *Cc:* Keith Burns ; David McBride <
> dmcbr...@linuxfoundation.org>; Brady Allen Johnson <
> brady.allen.john...@ericsson.com>; Reinaldo Penno 
> *Subject:* Re: Checking in the the Policytest project in OPNFV.
>
>
>
> If there are no objections from other committers, Bryan do you mind
> starting the termination review process (https://www.opnfv.org/
> developers/technical-project-governance/project-lifecycle)?
>
>
>
> It's pretty straightforward.  Make an announcement on mailing lists and
> then after two weeks come back to the TSC for a vote...
>
>
>
> Thanks,
>
>
>
> Ray
>
>
>
> On Tue, Jan 24, 2017 at 7:46 AM, SULLIVAN, BRYAN L  wrote:
>
> Not that I know of.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org]
> *Sent:* Tuesday, January 24, 2017 6:42 AM
> *To:* SULLIVAN, BRYAN L 
> *Cc:* Keith Burns ; David McBride <
> dmcbr...@linuxfoundation.org>; Brady Allen Johnson <
> brady.allen.john...@ericsson.com>; Reinaldo Penno 
> *Subject:* Re: Checking in the the Policytest project in OPNFV.
>
>
>
> Thanks Bryan...
>
>
>
> So it sounds like this is a candidate for a termination review.  Is Keith
> still involved in OPNFV?  Email from Peter Bandzi bounced back.
>
>
>
> Thanks,
>
>
>
> Ray
>
>
>
> On Tue, Jan 24, 2017 at 6:18 AM, SULLIVAN, BRYAN L  wrote:
>
> As far as I know the project is defunct.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> *From:* Raymond Paik [mailto:rp...@linuxfoundation.org]
> *Sent:* Monday, January 23, 2017 8:50 PM
> *To:* Keith Burns 
> *Cc:* David McBride ; Brady Allen Johnson <
> brady.allen.john...@ericsson.com>; SULLIVAN, BRYAN L ;
> Reinaldo Penno ; Peter Bandzi -X (pbandzi - Pantheon
> Technologies SRO at Cisco) 
> *Subject:* Re: Checking in the the Policytest project in OPNFV.
>
>
>
> Keith:
>
>
>
> Following up on this again and adding other committers.  Can you let me
> know if you plan on continuing with the Policy Test project?
>
>
>
> Thanks,
>
>
>
> Ray
>
>
>
> On Fri, Jan 13, 2017 at 9:35 PM, Raymond Paik 
> wrote:
>
> Keith:
>
>
>
> You may have had a conversation with my colleague David McBride on this
> topic...
>
>
>
> I haven't seen any activities in your repo since project creation in
> August of 2015.  Do you intend to continue with the project?  If not, I'd
> recommend "archiving" the project.  The steps required for is outlined
> under "termination review" at https://www.opnfv.org/
> developers/technical-project-governance/project-lifecycle
>
>
>
> Thanks,
>
>
>
> Ray
>
>
>
>
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

[Tim Rozet]

Hi Mark,
I had a chance to go through the repo.  Much of it looks like it could be 
translated into TripleO heat/puppet for Apex and TripleO upstream.  The design 
of how Andrey is installing will need to change though.  What he is doing right 
now is using ExtraConfig to initiate calls to bash scripts which end up calling 
puppet to deploy scaleio.  The proper way is to add real ScaleIO services to 
OOO so that heat templates call the puppet directly to deploy scaleio, and not 
initiate bash scripts.

If you want to tackle adding this to TripleO I can help guide you.  We would 
need a blueprint and I can walk you through how it all works.  Otherwise if you 
want the Apex team to handle adding ScaleIO I think we will need to wait until 
after Danube as we are already overloaded with features right now.  Maybe 
Andrey would want to contribute as well? (cc'ed)

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Mark Beierl" 
To: "Tim Rozet" 
Cc: opnfv-tech-discuss@lists.opnfv.org
Sent: Monday, January 23, 2017 5:43:46 PM
Subject: Re: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules

Hey, Tim.

The original repo has been moving forward: 
https://github.com/codedellemc/puppet-scaleio

Not sure what changes you needed to make, or if they have been superseded by 
changes in the codedellemc repo.  It now claims to support CentOS 6/7, so maybe?

The other repo (https://github.com/cloudscaling/redhat-kvm) has a bunch of 
overcloud scripts that appear to pull in the correct puppet modules and 
configure them.  I wonder if anything from those scripts can be used directly 
in Apex?

Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

> On Jan 23, 2017, at 17:30, Tim Rozet  wrote:
> 
> Hi Mark,
> Back at the previous plugfest in Colorado I had modified scaleio puppet 
> module to work with Apex as a POC.  Not sure if they still work or not, but I 
> never had time to go back and integrate into Apex upstream:
> 
> https://github.com/trozet/puppet-scaleio/tree/rpm_support
> 
> Tim Rozet
> Red Hat SDN Team
> 
> - Original Message -
> From: "Mark Beierl" 
> To: opnfv-tech-discuss@lists.opnfv.org
> Sent: Monday, January 23, 2017 12:38:08 PM
> Subject: [opnfv-tech-discuss] [Apex] ScaleIO puppet modules
> 
> Hello, Apex team, but probably mainly Dan/Tim. 
> 
> At the plugfest, Dan and I chatted briefly about getting ScaleIO puppet 
> modules integrated with Apex. I have noticed that some work has been done by 
> the ScaleIO team in a side repo [1]. Does any of this look like it would be 
> reusable for Apex? 
> 
> [1] https://github.com/cloudscaling/redhat-kvm 
> 
> Regards, 
> Mark 
> 
> Mark Beierl 
> Advisory Solutions Architect 
> Dell EMC | Office of the CTO 
> mobile +1 613 314 8106 
> mark.bei...@dell.com 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[opnfv-tech-discuss] New OPNFV Project Proposal - SNAPS-OO

[Steven Pisarski]

Hello all,

We just completed our proposal for a new OPNFV Project named SNAPS-OO 
(https://wiki.opnfv.org/display/PROJ/SNAPS-OO). Please feel free to contact 
Randy, Kevin, or myself if you should have any questions.

Best regards,
Steve Pisarski
Architect
CableLabs
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Apex] POD needed for Apex testing

[Tim Rozet]

Hi Bryan,
We could lend you a server from pod7, but I think Jack mentioned that type of 
thing isn't allowed anymore.  Jack can you confirm?  Are there any other 
sandbox intel pods where Bryan could get a server for development?

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "BRYAN L SULLIVAN" 
To: "Tim Rozet (tro...@redhat.com)" , "Dan Radez 
(dra...@redhat.com)" 
Cc: opnfv-tech-discuss@lists.opnfv.org
Sent: Tuesday, January 24, 2017 9:24:49 AM
Subject: [Apex] POD needed for Apex testing

Tim and Dan,

Do you have any PODs or servers (as with the previous POD7 server) that the 
Copper, Models, and VES projects can use for testing with Apex? I've tried 
several times to get Centos 7 installed in my lab but it's always hanging on 
"yum update" (I've tried three times now, and there's no way to quit the yum 
update without hosing the OS). So unless I can invoke the Apex installer from a 
Xenial-based jumphost, I am blocked from using Apex in my lab.

Thanks,
Bryan Sullivan | AT

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

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Is there anyone on the FUEL team monitoring this list? Really, we cannot make 
progress in Danube on Fuel support unless we get some basic support on the 
issues we have with standing up a Fuel-based deploy for testing.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Thursday, January 19, 2017 2:44 PM
To: Michael Polenchuk 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Resending, as I have not yet see a clarification of the fields in the 
dea-pod-override.yaml and dha.yaml files. I need this in order to setup our 
PODs to test under Fuel for the Copper, Models, and VES project.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, January 12, 2017 6:13 AM
To: 'Michael Polenchuk' 
>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Michael,

We figured out that much after actually looking at the README file, but the 
details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how 
they should be setup for a specific POD, what are the options and values, 
what’s mandatory/optional, etc. In the repo, it looks like they refer to 
virtual envs, but after looking at the “secret” lab config versions it’s not 
much clearer. There are dozens of fields, subnet specs, etc and it’s unclear 
what they all related to. Where is the spec for all that?

Thanks,
Bryan Sullivan | AT

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 11:35 PM
To: SULLIVAN, BRYAN L >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?



On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L 
> wrote:
Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?


Hi Bryan,

"-b base-uri" parameter usually pointed to the config which resides in the 
repo, e.g.:
# git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel

In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config
-s option is for a scenario name which is available in the repo as well 
(.../opnfv-fuel/deploy/scenario).

--
  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] FW: Checking in the the Policytest project in OPNFV.

[SULLIVAN, BRYAN L]

Hi all,

If there are no objections, it’s proposed that the PolicyTest project be 
terminated, as there has been no activity since its formation.

Thanks,
Bryan Sullivan | AT

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Tuesday, January 24, 2017 9:28 AM
To: SULLIVAN, BRYAN L 
Cc: Keith Burns ; David McBride 
; Brady Allen Johnson 
; Reinaldo Penno 
Subject: Re: Checking in the the Policytest project in OPNFV.

If there are no objections from other committers, Bryan do you mind starting 
the termination review process 
(https://www.opnfv.org/developers/technical-project-governance/project-lifecycle)?

It's pretty straightforward.  Make an announcement on mailing lists and then 
after two weeks come back to the TSC for a vote...

Thanks,

Ray

On Tue, Jan 24, 2017 at 7:46 AM, SULLIVAN, BRYAN L 
> wrote:
Not that I know of.

Thanks,
Bryan Sullivan | AT

From: Raymond Paik 
[mailto:rp...@linuxfoundation.org]
Sent: Tuesday, January 24, 2017 6:42 AM
To: SULLIVAN, BRYAN L >
Cc: Keith Burns >; David McBride 
>; Brady 
Allen Johnson 
>; 
Reinaldo Penno >
Subject: Re: Checking in the the Policytest project in OPNFV.

Thanks Bryan...

So it sounds like this is a candidate for a termination review.  Is Keith still 
involved in OPNFV?  Email from Peter Bandzi bounced back.

Thanks,

Ray

On Tue, Jan 24, 2017 at 6:18 AM, SULLIVAN, BRYAN L 
> wrote:
As far as I know the project is defunct.

Thanks,
Bryan Sullivan | AT

From: Raymond Paik 
[mailto:rp...@linuxfoundation.org]
Sent: Monday, January 23, 2017 8:50 PM
To: Keith Burns >
Cc: David McBride 
>; Brady 
Allen Johnson 
>; 
SULLIVAN, BRYAN L >; Reinaldo Penno 
>; Peter Bandzi -X (pbandzi - 
Pantheon Technologies SRO at Cisco) 
>
Subject: Re: Checking in the the Policytest project in OPNFV.

Keith:

Following up on this again and adding other committers.  Can you let me know if 
you plan on continuing with the Policy Test project?

Thanks,

Ray

On Fri, Jan 13, 2017 at 9:35 PM, Raymond Paik 
> wrote:
Keith:

You may have had a conversation with my colleague David McBride on this topic...

I haven't seen any activities in your repo since project creation in August of 
2015.  Do you intend to continue with the project?  If not, I'd recommend 
"archiving" the project.  The steps required for is outlined under "termination 
review" at 
https://www.opnfv.org/developers/technical-project-governance/project-lifecycle

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] [barometer] Weekly Call Minutes

[Tahhan, Maryam]

 Hi folks

[barometer] Weekly Call Minutes 

* Dev update: 
https://wiki.opnfv.org/display/fastpath/Barometer+Danube+Development+Updates
  * Fuel update
* Testing plugin updates in virtual deployment. Mcelog, hugepages and 
ovs_events are passing.
* RDT bugfix https://github.com/collectd/collectd/pull/2147
  * Apex
* Discussions to make sure the plugins and configurations for D release 
plugins are in place.
* Manual testing/sanity check will be done - no functest as this was a 
stretch goal for release D

* VES update:
  * New spec is available in the test collector project - got this.
  * Adding a JIRA ticket to update the VES Agent to the backlog.
  * [ACTION] Maryam to push VES collectd agent code to barometer repo.

* Talk Proposals for ONS and OpenStack Boston
  * ONS abstract submitted
* Opportunity to collaborate with Doctor and barometer and a CFP.

* Testing update:
  * Place holder Wiki: 
https://wiki.opnfv.org/display/fastpath/Testing+with+Functest [Action Calin to 
fill in test details]
  * Working on fuel deployment on baremetal.
  * Issues with installing latest OPNFV env on baremetal behind a proxy. 
Testing on hold till there's a work around.

[ACTION]: Maryam to update 
https://wiki.opnfv.org/display/fastpath/Collectd+Metrics+and+Events to include 
Mcelog plugin stats --> Done
[ACTION]: Damien to add metrics that are in progress to the table. --> Done.
[ACTION]: Maryam to update 
https://wiki.opnfv.org/display/fastpath/Collectd+Metrics+and+Events to include 
events

BR
Maryam

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

[opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

[Aaron Smith]

Hi,
  Would there be interest in a separate meeting to discussion what an
"ideal" monitoring framework might look like.

Topics might include:
  - Polling vs Event capture
  - Platform independent monitor agent
- Network Interfaces
- Kernel events
- VM / Container monitoring
- Common bus for Events / Telemetry / Config
  -  Common Object model
- Agent configuration
- Performance
   - <<50ms

This would be an informal brainstorming activity with more emphasis on
concepts than existing projects (unless necessary).

Thoughts?

Aaron

-- 
Aaron Smith | Senior Principal Software Engineer
NFV Partner Engineering
Red Hat
aasm...@redhat.com

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Compass4nfv PTL nomination

[Iben Rodriguez]

+1 for Justin

> 
>> 在 2017/1/20 9:38, Weidong.Shao 写道:
>> Hi everyone,
>>  
>> I would like to use this email to express my appreciation to the community 
>> and inform everyone that I will step down as PTL for the Compass4nfv 
>> project. It’s been a privilege serving as PTL for Compass4nfv, one of the 
>> installer tools for OPNFV. I have learned a great deal from the community 
>> members by participating each and every OPNFV Summit as well as many OPNFV 
>> community meetings. Thanks for this amazing journey.
>>  
>> I would also like to nominate Justin Chi from Huawei as the next PTL for 
>> Compass4nfv. Justin has been the technical leader of the Huawei Compass4nfv 
>> open source team in Shanghai, China which consists of many original members 
>> of Compass4nfv. He has demonstrated excellent leadership skills as well as 
>> strong technical skills. Under Justin’s leadership, Compass4nfv has been 
>> extremely active and gained great recognition.
>>  
>> I will be in a fully supportive role to Justin and remain as a Committer to 
>> the Compass4nfv project in the near future.
>>  
>>  
>> We also welcome contributions  to Compass4nfv. 
>> https://wiki.opnfv.org/display/compass4nfv/Compass4nfv.
>>  
>> Compass4nfv project was originally derived from compass project. Official 
>> upstream Compass project had 3 repos, all hosted under openstack.
>> They are:https://github.com/openstack/compass-core
>> https://github.com/openstack/compass-web
>> https://github.com/openstack/compass-adapters
>>  
>> Also we have recently finished the development of containerized  
>>  Compass solution. If you are interested in contributing/knowing more on 
>> this. Contact me weidong.s...@huawei.com or xicheng.cha...@huawei.com
>>  
>> Thanks,
>> Weidong
>> 
>> 
>> ___
>> 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: Reply: [availability] Minutes for HA project weekly meeting on Jan. 18th

[Yin Tony]

Hi Fu Qiao,

All these ten test cases have been already merged in yardstick C release, 
corresponding to tc045~tc054. But it's a good suggestion to discuss on these 
test cases because some of these cases need to be refined as discussed last 
time.

-邮件原件-
发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年1月24日 9:39
收件人: 'Yin Tony'
抄送: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng Liu'
主题: 答复: Reply: [opnfv-tech-discuss] [availability] Minutes for HA project 
weekly meeting on Jan. 18th

Hi, Kanglin. Thank you.
I recall we had ten testcases discussed in the C release, but haven't got all 
of them merged in yardstick, right? We would also like to know your plan about 
these testcases.

-邮件原件-
发件人: Yin Tony [mailto:14_...@tongji.edu.cn] 
发送时间: 2017年1月23日 22:59
收件人: 'Fu Qiao'
抄送: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng Liu'
主题: Reply: [opnfv-tech-discuss] [availability] Minutes for HA project weekly 
meeting on Jan. 18th

Hi Fu Qiao, 

I have to apologize that we don't have any drafts yet for HA test cases in D 
release because recently we are taking efforts on framework improving. We asked 
for a discussion this time in order to know HA team's suggestions on HA test 
cases in D release and then decide what to test.
Before the discussion on test cases , I can share yardstick's current work and 
plan on HA in D release, including some improvements on HA testing and 
yardstick's UI --- grafana, through which we can see test results of yardstick.

-邮件原件-
发件人: Fu Qiao [mailto:fuq...@chinamobile.com] 
发送时间: 2017年1月20日 11:13
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: 答复: [opnfv-tech-discuss] [availability] Minutes for HA project weekly 
meeting on Jan. 18th

Hi, all. Below are the minutes for this week's HA project call. Thank you for 
everyone to join the discussion.
We will have our next meeting on Feb. 8th, after the Chinese Lunar New Year 
holidays. And will have Kanglin introduce about the HA test cases in D release.
@Kanglin, do we have drafts about the HA test cases for D release? If yes, 
please send out the link before the meeting so that we can review it at first. 
Thanks.

Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th Minutes Wanghui introduced the 
scope and plan for the Rescuer team. The rescuer team will focus on the date 
pretection issue, currently mainly in VIM. it will use karbor as its upstream 
project, and is intended to collect requirement and gap analysis from the OPNFV 
community. The team has close connection with the OpenStack Karbor project, so 
can be predicted to work closely with the upsteams. Hui also introduced more 
details about the Karbor project in OpenStack.
The plan for the D release is to work out requirement for data pretection. The 
HA team suggested Hui to look into the release doc of the HA project first, and 
see if they can get more clue for the requirement specificly on data 
pretection. The HA requirement doc and scenario analysis doc can help to 
identify requirement and scenarios for data pretection. And  the deployment 
framework doc can help to understand the HA deployment  context when talking 
about data pretection.
fuqiao will send out the release doc to hui after the meeting.

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年1月18日 10:34
收件人: 'stpierre, edgar'; 'Leon Wang'; 'wanghui71'; 'yuval.brik'; 
'opnfv-tech-discuss'; 'Ian.Jolliffe'; 'Stefan Arntzen'; 'greg.waines'; 
'14_ykl'; 'juan_qiu'; 'mathi.naickan'; 'jonas.arndt'; 'yuan.yue'; 'jniu'; 'Peng 
Liu'
主题: [opnfv-tech-discuss] [availability] Agenda for HA project weekly meeting on 
Jan. 18th

Hi, all. Below are the agenda for today's HA project meeting. Looking forward 
to talking to you all soon.

Next Meeting on 13:00-14:00 UTC, Wednesday, Jan. 18th HA project meeting Please 
join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/772448949   

You can also dial in using your phone.
United States (Long distance):
+1 (646) 749-3117
Access Code: 772-448-949
More phone numbers: https://global.gotomeeting.com/772448949/numbersdisplay.html
Agenda
1 Introduction of Rescuer – Hui Wang
2 Introduction of HA project progress – fuqiao
2 Discussion of co-working between HA and Rescuer




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

[opnfv-tech-discuss] [Apex] POD needed for Apex testing

[SULLIVAN, BRYAN L]

Tim and Dan,

Do you have any PODs or servers (as with the previous POD7 server) that the 
Copper, Models, and VES projects can use for testing with Apex? I've tried 
several times to get Centos 7 installed in my lab but it's always hanging on 
"yum update" (I've tried three times now, and there's no way to quit the yum 
update without hosing the OS). So unless I can invoke the Apex installer from a 
Xenial-based jumphost, I am blocked from using Apex in my lab.

Thanks,
Bryan Sullivan | AT

___
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]Thoughts on Report Authentication

[SULLIVAN, BRYAN L]

The solution you propose (sending direct to the database over a secure 
connection) is the best solution. It does require however these additional 
capabilities:

1)  For users that want to assess how their system stacks up without having 
the data published to the OPNFV DB (“dry run”), there needs to be an option to 
store the test results locally, so the user can see how they did.

2)  Results stored locally would not be considered valid test results for 
the CVP, and could not be submitted to OPNFV for that (only results sent 
directly from the test tool over a secure connection will be accepted).

3)  For users that somehow do not select the “dry run” option when they 
meant to, and thus their test results were sent to the OPNFV DB in error, we 
need a process for the user to request that their data be cleaned from the DB. 
We can minimize these cases with adequate warnings in the test tool, or making 
“dry run” the default (the user has to explicitly indicate they want the 
results pushed to OPNFV).

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Leo Wang
Sent: Tuesday, January 24, 2017 12:20 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [dovetail]Thoughts on Report Authentication

Hi

Last Friday on dovetail weekly meetings, dovetail faced a question about the 
security issue of results in container(functest/yardstick), how to make sure 
that these results are not modified

I’ve checked on docker’s documentation and googled some well-known 
websites(stackoverflow, serverfault, …) , it seems there is no way to prevent 
people from accessing the container



Here are things we can do:

1) the upstream project to do authentication on themselves

2) setup a database, and the database is dedicated for dovetail results, people 
with no permit can not access the database

3) use the REST API of FUNCTEST/YARDSTICK with SSL to make sure that these 
results are just existing in secured transportation and saved to db, and then 
no one can touch them.

This is a very primitive workaround, so welcome everyone to contribute your idea

BR

Leo Wang

[cid:image001.png@01D27609.0B84EE10]
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing with br-aux not found

[Paraskevopoulos Georgios]

Hi all,



I am encountering the same problem in Fuel 10. Do we have any news on this?



Thanks,

George



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Michael 
Polenchuk
Sent: Monday, January 16, 2017 9:25 PM
To: Veena Lingadahalli 
Cc: opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi,

This bug/feature could be tracked by
https://bugs.launchpad.net/fuel-plugin-opendaylight/+bug/1656924

We're going to get a support of ODL with DPDK usecase soon.



On Tue, Jan 10, 2017 at 2:18 PM, Michael Polenchuk  > wrote:

Hi Veena,

In case of DPDK enabled the br-aux bridge ain't created on compute nodes
since physical(dpdk) interface is being connected directly to br-prv ovs bridge.

I guess this case (ODL + OVS/DPDK) ain't supported yet.

Please turn off "install dpdk" option and try it out.



On Mon, Jan 9, 2017 at 8:18 PM, Veena Lingadahalli  > wrote:

Hi,

I'm using opnfv fuel 9.0 to deploy openstack with ODL-SFC(netvirt) + 
OVS(DPDK+NSH). I have used all default plugins which are staged with the fuel 
iso.
I have made the necessary configurations related to neutron VLAN IDs, DPDK 
enabled interface and Hugepage configuration in compute node. Network 
verification is also successful. The deployment is failing with the below error.


generate_network_config(): Endpoint 'br-aux' not found in interfaces or 
transformations result. at 
/etc/fuel/plugins/opendaylight-0.9/puppet/manifests/odl-netconfig.pp:25 on node 
node-1.domain.tld

I'm unable to check where this bridge is being created. Never faced this issue 
before when neutron with tunneling is used. Am I missing any configuration 
related to vlan? Attached the complete puppet log and network_scheme. Please 
let me know the cause for error and how to proceed about this.



Thanks,

-Veena



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




--

  Michael Polenchuk
  Private Cloud / Mirantis Inc.




--

  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] [joid] ubuntu version for jumphost?

[Ryota Mibu]

Hi joid team,


I know that you guys are working on MAAS 2.0 support [1] and Ubuntu 16.04 [2], 
but not sure which version of ubuntu can be used for jumphost now. Could you 
advise how we can build pod with latest joid? Should I use trusty + maas 2.0 
manual installation?

Note, I'm using '00-maasdeploy.sh' to build virtual pod with default config.

It seems the main brocker for [2] is maas-deployer package which only has 
trusty support. And, this seems blocked by python3 support [3].

Any idea?

[1] https://jira.opnfv.org/projects/JOID/issues/JOID-100
[2] https://jira.opnfv.org/projects/JOID/issues/JOID-99
[3] https://bugs.launchpad.net/maas-deployer/+bug/1571093


BR,
Ryota

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

Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

[Fatih Degirmenci]

Hi,

This is in our plans since last year. The idea is to come up with a common 
format to use in commit message which gets processed by the verify job, running 
the impacted scenario.

Please see the first step in below section.

https://wiki.opnfv.org/display/INF/CI+Evolution#CIEvolution-HowtheThingsFitTogether

We are currently working on aligning job structures (verify and daily) and 
scope of the patchset verification for all the installers since the current 
situation is not good, some do things properly some does nothing.

Here is who does what as part of patchset verification.

- apex: unit test, build, virtual deploy, functest smoke test
- compass: lint, virtual deploy, functest smoke test
- daisy: build, virtual deploy
- fuel: build
- joid: nothing

Apart from not reaching to this step to come up with a proposal for commit 
message, this depends on scenario consolidation/naming activity as well. We can 
hopefully start working with this after Danube.

/Fatih

From:  on behalf of Yujun Zhang 

Date: Tuesday, 24 January 2017 at 08:41
To: Chigang , "opnfv-tech-discuss@lists.opnfv.org" 

Subject: Re: [opnfv-tech-discuss] [Releng/Octopus] Patch verification suggestion

I think it is technically feasible.

We added an experimental trigger for doctor project not long ago[1]. The 
trigger is similar to your requirement.

[1]: https://gerrit.opnfv.org/gerrit/#/c/26839/4/jjb/global/releng-macros.yml


On Tue, Jan 24, 2017 at 12:31 PM Chigang (Justin) 
> wrote:
Hi,

The Command "recheck" is used to run default patch verification again in
Gerrit.

But there are so many scenarios to be vericated, I think default patch
verification is not enough.

Is it possible to add a "scenarios" parameters to improve additional
verification before patch merged in master?

such as :

"recheck odl" will trigged to odl related scenarios.

Thanks

Justin



___
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] [dovetail]Thoughts on Report Authentication

[Leo Wang]

Hi

Last Friday on dovetail weekly meetings, dovetail faced a question about the 
security issue of results in container(functest/yardstick), how to make sure 
that these results are not modified

I’ve checked on docker’s documentation and googled some well-known 
websites(stackoverflow, serverfault, …) , it seems there is no way to prevent 
people from accessing the container



Here are things we can do:

1) the upstream project to do authentication on themselves

2) setup a database, and the database is dedicated for dovetail results, people 
with no permit can not access the database

3) use the REST API of FUNCTEST/YARDSTICK with SSL to make sure that these 
results are just existing in secured transportation and saved to db, and then 
no one can touch them.

This is a very primitive workaround, so welcome everyone to contribute your idea

BR

Leo Wang

[cid:48590F6C-CAFE-41B2-B5CC-C94F575C4293]
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss