Re: [opnfv-tech-discuss] Security PTL

[SULLIVAN, BRYAN L (BRYAN L)]

Luke,

I would like to thank you for your work as security project lead. I've tried to 
follow your lead in a similar role for the Acumos project, and I think the 
project (and other LF projects) are better for the focus you put on project 
objectives, tools, and CI/CD support for security/quality assurance. You know 
well how hard it us to build project momentum and maintain it for such a focus, 
but also that's it's a critical role to fill for any open source project.

I think Anteater still fills a gap in the tools that projects use for 
security/quality assurance, and despite challenges in adopting it, I appreciate 
the work and recommend that others take a second look.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss@lists.opnfv.org [opnfv-tech-discuss@lists.opnfv.org] 
on behalf of Luke Hinds [lhi...@redhat.com]
Sent: Friday, June 28, 2019 2:03 AM
To: TSC OPNFV; opnfv-tech-discuss; opnfv-security
Subject: [opnfv-tech-discuss] Security PTL

Hello,

I would like to notify the TSC that I wish to step down as Security PTL.

I have not been active in the role for a long time now, so this very much makes 
sense as the right thing to do.

I have also changed responsibilities with Red Hat that mean I would not have 
the time needed, should the role start to demand attention again in the future.

It's been a pleasure working with you all and I would happily mentor anyone 
interested in the position of security manager. All aspects of the role are 
very well documented too.

I am not familiar with the current off-boarding process, but the main tasks I 
see are removing my name from some of the confluence pages / wiki we have.

There is also the anteater project, which we can depreciate should you like or 
keep using. I guess the former, as I made a release a while ago, but it was 
never pulled into the opnfv jobs.

Best Regards,

Luke Hinds

--
Luke Hinds  | CTO Office | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | t: +44 
12 52 36 2483
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23312): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23312
Mute This Topic: https://lists.opnfv.org/mt/32281622/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [releng] Anteater maintenance

[SULLIVAN, BRYAN L (BRYAN L)]

You could try Thahn Ha (LF) on  lf-rel...@lists.linuxfoundation.org
I'm not sure the new compliance project is running yet but that would be 
another contact.

Thanks,
Bryan Sullivan | AT

From: Luke Hinds [lhi...@redhat.com]
Sent: Wednesday, January 09, 2019 1:56 AM
To: SULLIVAN, BRYAN L (BRYAN L)
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] [releng] Anteater maintenance

Thanks Bryan,

Any recommendations on who I could contact at LF to see if they want to use the 
tool.

You're of course welcome to do anything you please with anteater in acumos.

Cheers,

Luke

On Tue, Jan 8, 2019 at 6:37 PM SULLIVAN, BRYAN L (BRYAN L) 
mailto:bryan.sulli...@research.att.com>> wrote:
Hi Luke,

Thanks for continuing to develop this on github. Did you know that the LF 
recently launched a new compliance toolset project? 
https://www.linuxfoundation.org/press-release/2018/12/the-linux-foundation-to-launch-new-tooling-project-to-improve-open-source-compliance/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linuxfoundation.org_press-2Drelease_2018_12_the-2Dlinux-2Dfoundation-2Dto-2Dlaunch-2Dnew-2Dtooling-2Dproject-2Dto-2Dimprove-2Dopen-2Dsource-2Dcompliance_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=8bi4DXHJNQhsLOyPWzogWK6a9l4ICDvYsYG9YTQIH7o=VnhMaopqeV8vEnmFR19BikMzz2-GZkcyiSb3wvvAqs8=>

Your work might be useful to them.

I'm currently working in a related area for the Acumos project, leading the TSC 
Security Committee 
(https://wiki.acumos.org/display/SEC<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.acumos.org_display_SEC=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=8bi4DXHJNQhsLOyPWzogWK6a9l4ICDvYsYG9YTQIH7o=jwIDvp1U9xelr2inGyo9YdzKgRqJrNfih2K8fjq757s=>)
 and lead of the security-verification component of the Acumos platform (in 
development). Trust in the project code is one of the items in scope for the 
Security Committee, so it's good to see you are still working in that area. 
I'll look into the latest version.

On the notices, I also still get them though haven't done anything on them for 
a while.
I agree, if OPNFV is not minding that store, they should consider turning it 
down.

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 
[opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>] 
on behalf of Luke Hinds [lhi...@redhat.com<mailto:lhi...@redhat.com>]
Sent: Friday, January 04, 2019 12:32 AM
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [releng] Anteater maintenance

Hi RelEng Folks,

I am not as involved in OPNFV any longer. I still get a few emails around 
anteater information at gate.

Would someone else like to take over managing the issues at gate or should we 
decommission the project (in opnfv)?

Also it's running an old version now, there is a later version which is much 
improved and can be found below. We did talk about implementing this, but it 
never happened in the end.

https://github.com/anteater/anteater<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_anteater_anteater=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=eAjgBbuNlHCiHt6jSQC7qJa3JsbM6CvmpTl-3-JwTpY=ACeM_qM28hmlnnLp9_P1P1Zp93swhBR-mxxVOy2GEJo=>

Regards,

Luke


--
Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
e: lhi...@redhat.com<mailto:lhi...@redhat.com> | irc: lhinds @freenode | t: +44 
12 52 36 2483
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22628): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22628
Mute This Topic: https://lists.opnfv.org/mt/28970529/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [releng] Anteater maintenance

[SULLIVAN, BRYAN L (BRYAN L)]

Hi Luke,

Thanks for continuing to develop this on github. Did you know that the LF 
recently launched a new compliance toolset project? 
https://www.linuxfoundation.org/press-release/2018/12/the-linux-foundation-to-launch-new-tooling-project-to-improve-open-source-compliance/

Your work might be useful to them.

I'm currently working in a related area for the Acumos project, leading the TSC 
Security Committee (https://wiki.acumos.org/display/SEC) and lead of the 
security-verification component of the Acumos platform (in development). Trust 
in the project code is one of the items in scope for the Security Committee, so 
it's good to see you are still working in that area. I'll look into the latest 
version.

On the notices, I also still get them though haven't done anything on them for 
a while.
I agree, if OPNFV is not minding that store, they should consider turning it 
down.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss@lists.opnfv.org [opnfv-tech-discuss@lists.opnfv.org] 
on behalf of Luke Hinds [lhi...@redhat.com]
Sent: Friday, January 04, 2019 12:32 AM
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [releng] Anteater maintenance

Hi RelEng Folks,

I am not as involved in OPNFV any longer. I still get a few emails around 
anteater information at gate.

Would someone else like to take over managing the issues at gate or should we 
decommission the project (in opnfv)?

Also it's running an old version now, there is a later version which is much 
improved and can be found below. We did talk about implementing this, but it 
never happened in the end.

https://github.com/anteater/anteater

Regards,

Luke
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22609): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22609
Mute This Topic: https://lists.opnfv.org/mt/28970529/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [opnfv-project-leads] VOLUNTEERS NEEDED for booth duty at KubeCon! #volunteer #kubecon #booth

[SULLIVAN, BRYAN L (BRYAN L)]

Hi David,

Just got a pass to the event and planned my schedule. I signed up for the booth 
whenever I could.
Happy to bring anyone up to speed on the LFDL and Acumos during the time also.

Thanks,
Bryan Sullivan | AT

From: opnfv-project-le...@lists.opnfv.org [opnfv-project-le...@lists.opnfv.org] 
on behalf of David McBride [dmcbr...@linuxfoundation.org]
Sent: Friday, December 07, 2018 11:52 AM
To: TECH-DISCUSS OPNFV; TSC OPNFV; opnfv-project-leads
Cc: Brandon Wick; Heather Kirksey
Subject: Re: [opnfv-project-leads] VOLUNTEERS NEEDED for booth duty at KubeCon! 
#volunteer #kubecon #booth

+TSC OPNFV 
+opnfv-project-leads

On Fri, Dec 7, 2018 at 11:51 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Come on, folks!  Please sign up for booth duty if you are attending KubeCon 
next week.  We still have lots of open slots.  Surely you can find 1 or 2 hours 
to staff the booth next week!

Thanks.

David

On Wed, Dec 5, 2018 at 2:39 PM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Team,

For those of you attending KubeCon, please sign up for booth duty at the LFN 
booth.
  If you're able, please sign up for more than one session, but if you're 
limited to just one, that's fine too.

While you are staffing the LFN booth, please keep in mind that our goal for 
KubeCon is to build bridges and make connections between the LFN and CNCF 
communities… so please take an active role in that, introduce yourself to 
folks, and try exploring the areas where cloud native meets networking.

Let me or Brandon 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


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

Links:

You receive all messages sent to this group.

View/Reply Online 
(#1291)
 | Reply To 
Sender
 | Reply To 
Group
 | Mute This 
Topic
 | New 
Topic
Mute 
#volunteer
 | Mute 
#kubecon
 | Mute 
#booth
Your 

Re: [opnfv-tech-discuss] [announce][election] Opening nominations for OPNFV Technical Steering Committee (TSC)

[SULLIVAN, BRYAN L (BRYAN L)]

Yes


From: David McBride [dmcbr...@linuxfoundation.org]
Sent: Thursday, September 06, 2018 10:24 AM
To: HU, BIN; SULLIVAN, BRYAN L (BRYAN L)
Cc: TSC OPNFV; TECH-DISCUSS OPNFV; tim.irn...@ericsson.com; Heather Kirksey
Subject: Re: [opnfv-tech-discuss] [announce][election] Opening nominations for 
OPNFV Technical Steering Committee (TSC)

Bryan - do you accept the nomination?

On Thu, Sep 6, 2018 at 6:51 AM HU, BIN mailto:bh5...@att.com>> 
wrote:
Dear Community,

I would like to nominate Bryan Sullivan from AT for the new TSC.

Bryan was a founding member of OPNFV, and served in the TSC since then. He was 
part of the core team of OPNFV that led the community to achieve the success of 
the releases and other important milestones. He contributed to numerous 
projects at different stages of OPNFV, and is PTL of Copper, Models and VES 
projects.
He also actively promoted OPNFV in many industry events and summits, and worked 
with other upstream communities collaboratively.

Thank you for consideration

Bin

From: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 
mailto:opnfv-tech-discuss@lists.opnfv.org>> 
On Behalf Of David McBride
Sent: Friday, August 24, 2018 10:48 AM
To: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>; 
TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: tim.irn...@ericsson.com<mailto:tim.irn...@ericsson.com>; Heather Kirksey 
mailto:hkirk...@linuxfoundation.org>>
Subject: [opnfv-tech-discuss] [announce][election] Opening nominations for 
OPNFV Technical Steering Committee (TSC)

Team,

Today, we begin nominations for a new TSC, consisting of 15 members, in 
accordance with the Community Election 
Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_DEV_Community-2BElection-2BProcedure=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=LuF4PQga0L8C6dvOcU8uVc-a2v8pS8OX-DFOUc3qJw4=e__We9i2CKTRhuAj3skev-cdlYkbGKQl3GWtQzXbRJ8=>.
  Individuals who are eligible to both vote and run for a TSC position are 
those with 20 or more contributions on this list of active 
contributors<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_DEV_2018-2BConsolidated-2BContributions=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=LuF4PQga0L8C6dvOcU8uVc-a2v8pS8OX-DFOUc3qJw4=l2ejDspf3vS04vmVVBLKkXiP_9ZF0D4FF05vkbpqwr8=>.
  Before nominating someone, please consult the list and verify that the 
individual has 20 or more contributions.  You may find a schedule of election 
activities 
here<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_DEV_2018-2BTSC-2Band-2BTSC-2BChair-2BElection-2BSchedule-2Bof-2BActivities=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=LuF4PQga0L8C6dvOcU8uVc-a2v8pS8OX-DFOUc3qJw4=skqCxx2AROkjcgtaaz1n8v1pXz74xTvdmjhgwyv66zc=>.

PTL Input to the Active Contributor List
Note that the election procedures have a provision for adding and individual to 
the active contributor list, who has less than 20 contributions, yet who has 
make significant contributions to the OPNFV community.  Per the election 
procedure:

PTLs have an input on the "active contributor list" compiled over a 2-week 
review period (with a view that this step primarily targets at making sure 
qualified people that haven't been identified via the metric get added to the 
list)
I am working with the TSC to define a specific process for this situation.  In 
the mean time, if you are a PTL, and you would like to add someone to the 
active contributor list, please contact me directly with the name and a brief 
statement about why they should be included on the list.  Note that this action 
simply adds them to the active contributor list, they still must be nominated, 
separately.  Also, note that the 2-week review period for the active 
contributor list, cited in the election procedure, ends on Aug 31.

Nomination procedure

  1.  You may nominate yourself, or someone else.

 *   Remember that both you and the person nominated must be on the active 
contributor 
list<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_DEV_2018-2BConsolidated-2BContributions=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=LuF4PQga0L8C6dvOcU8uVc-a2v8pS8OX-DFOUc3qJw4=l2ejDspf3vS04vmVVBLKkXiP_9ZF0D4FF05vkbpqwr8=>
 with 20 or more contributions.
 *   If you nominate someone else, I will confirm with that person that 
they accept the nomination.

  1.  Announce the nomination with a "reply all" to this email prior to 5 p.m. 
(PT), Sept 7.
  2.  Please include the following information:

 *   Name of the nominee
 *   The nominee's organization
 *   A brief statement about the nominees qualifications and contributions 
to the OPNFV community.

  1.  Nominations close at 5 p.m. (PT) on Sept 7.  See the entire election 
schedule 
here<https://urldefense.pr

Re: [opnfv-tech-discuss] Following-up on groups.io discussion

[SULLIVAN, BRYAN L (BRYAN L)]

Ray,

I think the issue on attachments was limited to meeting invites, which didn't 
work reliably for some reason.  Just a heads up for people to ensure they are 
getting invites via the lists.


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Raymond Paik 
[rp...@linuxfoundation.org]
Sent: Thursday, May 24, 2018 12:23 PM
To: opnfv-tech-discuss; TSC OPNFV
Subject: [opnfv-tech-discuss] Following-up on groups.io discussion

All,

Please see this link for the help page on 
groups.io:
 
https://groups.io/static/help

Under FAQ (on the lefthand side of the page), you'll see various topics 
including passwords.  If there are topics that are not addressed on the page, 
please let me know prior to the TSC meeting next week.

I think Bryan brought up attachments, but if you look at this email I sent to 
the TAC mailing list on 
groups.io
 
(https://lists.lfnetworking.org/g/TAC/message/238),
 you'll find the attachment the same way as when you receive the original email.

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] Models and VES pull out of Fraser

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Just FYI although there was very substantial progress this time around for 
Models and VES, the Acumos project has consumed my time and thus I was not able 
to jump thru the final hoops to get the updates released. So these two projects 
will not participate further in the Fraser release.

Nonetheless development will continue and meet my main goal for these projects 
- simply that they break new ground and create reusable artifacts for future 
work.

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] [releng][security][infra] Anteater Improvements

[SULLIVAN, BRYAN L (BRYAN L)]

Can you add to that regexp:

  *   Retrieving an object or calling an API via wget/curl to any private subnet
  *   calling an API via wget/curl on any private subnet
  *   Retrieving an object or calling an API via wget/curl to any unregistered 
domain (i.e. a local hostname, one that is resolved by a local DNS only, or 
through a hosts file)

Solve those and you will be on your way to avoiding this being an onerous 
overhead.

But I still think an external malicious address (IP, subnet, domain name) 
checking resource would be more effective. The more one creates blanket rules 
such as the above, the more attack surface is hidden. So this regexp approach 
in the end creates a cover for attack. The alternative sadly is to require 
dozens (at least) of regexp rules. This is not an overhead projects (IMO) are 
ready to take on.

Thanks,
Bryan Sullivan | AT

From: Luke Hinds [mailto:lhi...@redhat.com]
Sent: Friday, March 09, 2018 1:52 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: Aric Gardner <agard...@linuxfoundation.org>; Fatih Degirmenci 
<fatih.degirme...@ericsson.com>; opnfv-tech-discuss 
<opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Sorry for spamming you folks, but the last one was broken:

https://regexr.com/3lv46<https://urldefense.proofpoint.com/v2/url?u=https-3A__regexr.com_3lv46=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=5KnnpogOSM_I2AxFww9_8Mgc-UOQW4-M1iwJkBTYF40=6tCZIqr3sisqZzb7RdDQJi6vJ5DjdXXMPkjUgalyb8Y=>

On Fri, Mar 9, 2018 at 9:36 AM, Luke Hinds 
<lhi...@redhat.com<mailto:lhi...@redhat.com>> wrote:
Another example with domain based urls:

https://regexr.com/3lv1o<https://urldefense.proofpoint.com/v2/url?u=https-3A__regexr.com_3lv1o=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=5KnnpogOSM_I2AxFww9_8Mgc-UOQW4-M1iwJkBTYF40=GmA-ipZszs01o584M3k4cvi-LtK1NwnOB74rs84Nak4=>
All we need do then is make an entry in anteater as follows

curl_http:
  regex: 
"wget.*|curl.*https?:\/\/(www\.)?[-a-zA-Z0-9@:%._\+~#=]{2,256}\.[a-z]{2,6}\b([-a-zA-Z0-9@:%_\+.~#?&//=]*)"
  desc: "Object retrieval from non authorised site."
And then domains would be white listed with a simple entry in the ignore list:

file_audits:
  file_contents:
- ^#
- \.onap\.org\/
The above would allow all file downloads, but if we wanted to be more specific, 
we could:

file_audits:
  file_contents:
- ^#
- \.onap\.org\/files\/.*\/*\.iso|img|yaml|tar
Hopefully its possible to see how flexible the tool is now.


On Fri, Mar 9, 2018 at 9:24 AM, Luke Hinds 
<lhi...@redhat.com<mailto:lhi...@redhat.com>> wrote:
A simple way to solve this is using regex. You can really build up multiple 
conditions, for example the following link will match anyone using curl /wget 
against an IP address, but things such as 'yum install curl' will not get 
picked up.

https://regexr.com/3lv1o<https://urldefense.proofpoint.com/v2/url?u=https-3A__regexr.com_3lv1o=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=5KnnpogOSM_I2AxFww9_8Mgc-UOQW4-M1iwJkBTYF40=GmA-ipZszs01o584M3k4cvi-LtK1NwnOB74rs84Nak4=>
 # Play around with the text section
When used in this way, the tool really becomes quite powerful. I use it myself 
for non security context stuff such as blocking depreciated functions, release 
names etc.


On Thu, Mar 8, 2018 at 3:31 PM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Aric,

To clarify my intent - it was that the blocking of wget/curl/etc tool use 
except as allowed by regex rules, is the onerous part since there are many 
different uses and it will be difficult to create/maintain the regexp rules.

I actually would *prefer* use of an external service such as VirusTotal that 
could flag risky content sources however they do it (FQDN, IP, etc though they 
are not a perfect solution either), since at least any private-subnet targets 
for wget/curl would pass that test.

Of course, one could argue that if a DNS is hacked then even curl for Keystone 
APIs can result in a vulnerability... but we have limits in what we can 
achieve. And such hacks would threaten use of the same resources even via 
python libraries e.g. for OpenStack clients, so it's not just curl/wget that 
would be at risk.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of Aric Gardner
Sent: Thursday, March 08, 2018 7:21 AM
To: Fatih Degirmenci 
<fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>>
Cc: opnfv-tech-discuss 
<opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

[SULLIVAN, BRYAN L (BRYAN L)]

Aric,

To clarify my intent - it was that the blocking of wget/curl/etc tool use 
except as allowed by regex rules, is the onerous part since there are many 
different uses and it will be difficult to create/maintain the regexp rules. 

I actually would *prefer* use of an external service such as VirusTotal that 
could flag risky content sources however they do it (FQDN, IP, etc though they 
are not a perfect solution either), since at least any private-subnet targets 
for wget/curl would pass that test.

Of course, one could argue that if a DNS is hacked then even curl for Keystone 
APIs can result in a vulnerability... but we have limits in what we can 
achieve. And such hacks would threaten use of the same resources even via 
python libraries e.g. for OpenStack clients, so it's not just curl/wget that 
would be at risk.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Thursday, March 08, 2018 7:21 AM
To: Fatih Degirmenci 
Cc: opnfv-tech-discuss 
Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Hi Faith,

Regarding your comments on reproducibility and traceability.

If we are not blocking ips, which I agree with Bryan is heavy handed
from a practical perspective. Perhaps ant eater could create a report
of external sources per repository, and then exit 0.

The developers could then be alerted to our concerns.

Gerrit Comment or email to ptl:

"Hi $project developer" Here are external ips connected to your build.
{list goes here}
If any of these sources should go offline, your builds will no longer
be reproducible or traceable.
Please consider this carefully. If you need a file hosted, contact
helpdesk and they will be happy to put in on artifacts.opnfv.org

Or something like that..


-Aric


On Thu, Mar 8, 2018 at 9:11 AM, Fatih Degirmenci
 wrote:
> Hi Luke,
>
>
>
> I have few comments and followup questions regarding this:
>
> “This in turn means we won't raise alarms over curl, git clone and wget and
> will instead check the IP addresses or URLS that those commands query. This
> should make anteater a lot less chatty at gate.”
>
>
>
> You might remember that one of the reasons we have checks for curl/wget is
> to find out if projects pull artifacts from unknown IPs during
> build/deployment/testing.
>
> These are not malicious but we have seen that few of the IPs where the
> projects fetch the artifacts belong to non-production/personal devices that
> tend to disappear over time.
>
> As you know, this is an important issue from reproducibility and
> traceability perspectives.
>
>
>
> Now the questions are;
>
> Assuming the IPs are not explicitly added to exception list for the
> corresponding project, do you mean that we will stop flagging changes/files
> that contain wget/curl against unknown IPs if they are not marked as
> malicious on VirusTotal?
>
> We also had plans to make anteater checks voting/blocking. Will we discard
> this plan since wget/curl against IPs are not even planned to be flagged?
>
>
>
> /Fatih
>
> From:  on behalf of Luke Hinds
> 
> Date: Thursday, 8 March 2018 at 14:02
> To: "opnfv-tech-discuss@lists.opnfv.org"
> 
> Subject: [opnfv-tech-discuss] [releng][security][infra] Anteater
> Improvements
>
>
>
> Hello,
>
> I have some changes to improve the reporting ability and hopefully tone down
> the false positives.
>
> Aneater will now interface with the VirusTotal public API:
>
> 1. If anteater finds a public IP address, the DNS history will be quiered to
> see if the IP has past or present associations with malicious domains.
>
>
>
> 2. If a URL is found, it is checked against the VirusTotal API to see if its
> marked as malicous.
>
> 3. Binaries will be sent to VirusTotal for a scan by the aggregation of
> scanners hosted there.
>
> For anyone wanting a demo, please see the following:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__asciinema.org_a_JfzUPWpBGm0wDKPCN3KlK2DK0=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=6EsJ-DUgsI7-DkbjEXxGjzptgs4TvKq5mEEloPNPaPs=dzAbMw0YSraSqGU7H20vdxbFs2N_XOGvATnqWbreIac=
>  
>
> I will work with various people to get this rigged into CI.
>
> This in turn means we won't raise alarms over curl, git clone and wget and
> will instead check the IP addresses or URLS that those commands query. This
> should make anteater a lot less chatty at gate.
>
> Cheers,
>
> Luke
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> 

Re: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

[SULLIVAN, BRYAN L (BRYAN L)]

Fatih,

I think the problem is that it’s very difficult to differentiate between use of 
wget/curl etc for:

  *   Pulling in components/data from external sources, as part of a deploy or 
test process, or even by design of the component being developed (e.g. a config 
file is pulled from some repo/place and used in component configuration)
  *   Use of APIs exposed by the NFV platform or applications running under it

Requiring all the latter uses to be allowed through regexp rules would be the 
onerous part.

Thanks,
Bryan Sullivan | AT

From: Fatih Degirmenci [mailto:fatih.degirme...@ericsson.com]
Sent: Thursday, March 08, 2018 7:01 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Luke Hinds 
<lhi...@redhat.com>; opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Hi Brian,

My comment wasn’t about the tools themselves but what they are used for and to 
be honest the suggestion is nothing sort of heavy-handed approach.

If someone includes something in an artifact that is consumed by someone else 
for different purposes, we have responsibility to them that we will always be 
able to recreate that artifact for different purposes such as troubleshooting.
If people hook their own machines to store artifacts that go into final OPNFV 
release and if these machines disappear, we will have no possibility to 
recreate what we released.
Apart from that, if people want to rebuild something for some reason, they will 
be unable to do that since the dependencies will not be available anymore.
These concerns are based on what we found while looking at our earlier releases 
so I’m not talking about something that’s possible to happen but a real issue 
that happened and we had to intervene.

If projects guarantee the long term availability of the artifacts on the 
original location (ie until the EOL of that specific release) and they ask for 
exception, there will be no blocking.

As you said, you are free to the promote tools and approaches like how I am 
doing here since I believe they are important to be shared.

/Fatih

From: "SULLIVAN, BRYAN L (BRYAN L)" 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Date: Thursday, 8 March 2018 at 15:31
To: Fatih Degirmenci 
<fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>>, Luke 
Hinds <lhi...@redhat.com<mailto:lhi...@redhat.com>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

I do recommend that we rely upon tools that can focus on the trust of specific 
sources, and not the use of platform capabilities such as curl, wget, etc. 
These (curl, wget, etc) are tools that can be used for many purposes inside an 
application like an OPNFV platform, or its deployment/testing tools. The 
flagging/blocking of patches just because the code contains use of 
wget/curl/etc is an onerous and heavy-handed approach to the goal. Having to 
create regexp rules for each valid use of wget/curl is a non-starter for me and 
likely many others in this project. Thus I support Luke’s plan, and intend to 
promote these same tools and approaches for use in the Acumos and other LFN 
projects.

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Fatih 
Degirmenci
Sent: Thursday, March 08, 2018 6:12 AM
To: Luke Hinds <lhi...@redhat.com<mailto:lhi...@redhat.com>>; 
opnfv-tech-discuss 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Hi Luke,

I have few comments and followup questions regarding this:
“This in turn means we won't raise alarms over curl, git clone and wget and 
will instead check the IP addresses or URLS that those commands query. This 
should make anteater a lot less chatty at gate.”

You might remember that one of the reasons we have checks for curl/wget is to 
find out if projects pull artifacts from unknown IPs during 
build/deployment/testing.
These are not malicious but we have seen that few of the IPs where the projects 
fetch the artifacts belong to non-production/personal devices that tend to 
disappear over time.
As you know, this is an important issue from reproducibility and traceability 
perspectives.

Now the questions are;
Assuming the IPs are not explicitly added to exception list for the 
corresponding project, do you mean that we will stop flagging changes/files 
that contain wget/curl against unknown IPs if they are not marked as malicious 
on Vir

Re: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

[SULLIVAN, BRYAN L (BRYAN L)]

I do recommend that we rely upon tools that can focus on the trust of specific 
sources, and not the use of platform capabilities such as curl, wget, etc. 
These (curl, wget, etc) are tools that can be used for many purposes inside an 
application like an OPNFV platform, or its deployment/testing tools. The 
flagging/blocking of patches just because the code contains use of 
wget/curl/etc is an onerous and heavy-handed approach to the goal. Having to 
create regexp rules for each valid use of wget/curl is a non-starter for me and 
likely many others in this project. Thus I support Luke’s plan, and intend to 
promote these same tools and approaches for use in the Acumos and other LFN 
projects.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Fatih 
Degirmenci
Sent: Thursday, March 08, 2018 6:12 AM
To: Luke Hinds ; opnfv-tech-discuss 

Subject: Re: [opnfv-tech-discuss] [releng][security][infra] Anteater 
Improvements

Hi Luke,

I have few comments and followup questions regarding this:
“This in turn means we won't raise alarms over curl, git clone and wget and 
will instead check the IP addresses or URLS that those commands query. This 
should make anteater a lot less chatty at gate.”

You might remember that one of the reasons we have checks for curl/wget is to 
find out if projects pull artifacts from unknown IPs during 
build/deployment/testing.
These are not malicious but we have seen that few of the IPs where the projects 
fetch the artifacts belong to non-production/personal devices that tend to 
disappear over time.
As you know, this is an important issue from reproducibility and traceability 
perspectives.

Now the questions are;
Assuming the IPs are not explicitly added to exception list for the 
corresponding project, do you mean that we will stop flagging changes/files 
that contain wget/curl against unknown IPs if they are not marked as malicious 
on VirusTotal?
We also had plans to make anteater checks voting/blocking. Will we discard this 
plan since wget/curl against IPs are not even planned to be flagged?

/Fatih

From: 
>
 on behalf of Luke Hinds >
Date: Thursday, 8 March 2018 at 14:02
To: 
"opnfv-tech-discuss@lists.opnfv.org" 
>
Subject: [opnfv-tech-discuss] [releng][security][infra] Anteater Improvements

Hello,
I have some changes to improve the reporting ability and hopefully tone down 
the false positives.
Aneater will now interface with the VirusTotal public API:
1. If anteater finds a public IP address, the DNS history will be quiered to 
see if the IP has past or present associations with malicious domains.

2. If a URL is found, it is checked against the VirusTotal API to see if its 
marked as malicous.
3. Binaries will be sent to VirusTotal for a scan by the aggregation of 
scanners hosted there.
For anyone wanting a demo, please see the following:

https://asciinema.org/a/JfzUPWpBGm0wDKPCN3KlK2DK0
I will work with various people to get this rigged into CI.
This in turn means we won't raise alarms over curl, git clone and wget and will 
instead check the IP addresses or URLS that those commands query. This should 
make anteater a lot less chatty at gate.
Cheers,
Luke
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and Arm pod at UNH

[SULLIVAN, BRYAN L (BRYAN L)]

Sofia,

If there’s anything I’ve done in the Models project work referenced below that 
may be useful to you, let me know and I can provide any support you need. Helm 
is deployed as part of this stack, and used to deploy other stack components 
including:

  *   Ceph-docker as SDS backend: 
ceph-helm.sh<https://github.com/opnfv/models/blob/master/tools/kubernetes/ceph-helm.sh>
 *   Currently using Helm as I investigate other options e.g. Cloudify
  *   Various demo Apps to verify k8s + PVC (via Ceph) operation
  *   The VES components are also deployable via Helm, since the Cloudify 
blueprints<https://github.com/opnfv/ves/tree/master/tools/cloudify> just wrap 
k8s charts in a TOSCA blueprint with a small amount of Cloudify-specific 
attributes.

The Helm install and demo use scripts are in 
helm-tools.sh<https://github.com/opnfv/models/blob/master/tools/kubernetes/helm-tools.sh>.
 This script is called in 
demo_deploy.sh<https://github.com/opnfv/models/blob/master/tools/kubernetes/demo_deploy.sh>
 after the base cluster (k8s-master+CNI+k8s-workers) is deployed.

The advantage of using Cloudify (or the ONAP OOM project, which is where this 
work is heading) for deploying stack components is that we don’t need to use 
Helm directly (e.g. via invocation over SSH) on the k8s cluster, rather can 
invoke chart operations via the Cloudify API. This meets one design goal which 
is to minimize any operations that must be performed over SSH, for 
security/reliability reasons, e.g. operations over APIs have inherently smaller 
attack surfaces. It also means that unless there is a specific stack deployment 
need for Helm, it doesn’t have to be installed, further improving 
security/reliability (any untested/unused code should not be deployed).

Thanks,
Bryan Sullivan | AT

From: Sofia Enriquez [mailto:lsofia.enriq...@gmail.com]
Sent: Friday, February 16, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: gerard.d...@wipro.com; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and 
Arm pod at UNH

Maybe this may interest you. It's not specific to ARM, but CONTAINER4NFV 
project is working on a Clearwater implementation with K8s[0] and Helm[1]. Helm 
deployment will be Istio compatible. I wrote some documentation about it [2].

Best Regards,
Sofia

[0]: 
https://gerrit.opnfv.org/gerrit/#/c/50467/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_-23_c_50467_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=uP_eo00sb1hRiLC3GV7bmnqaEyou9gD0ECr4JqsoCe0=Gn7t4dJIpuzLWGoOUFHylxpBNfa4a33oWu-dgvswnFM=>
[1]: 
https://gerrit.opnfv.org/gerrit/#/c/51603/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_-23_c_51603_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=uP_eo00sb1hRiLC3GV7bmnqaEyou9gD0ECr4JqsoCe0=Qd7skbw8UWlwAM-euzJQNzJxiOxJMuTcCRg8YtcGL-Y=>
[2]: 
https://github.com/opnfv/container4nfv/blob/master/docs/release/userguide/clearwater-project.rst<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_container4nfv_blob_master_docs_release_userguide_clearwater-2Dproject.rst=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=uP_eo00sb1hRiLC3GV7bmnqaEyou9gD0ECr4JqsoCe0=Fb-oHngCywm9v0NjLbh-Eb9OpjW0U0-zD4T1MLBM9Ek=>

2018-02-16 17:36 GMT-03:00 SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>:
Not specific to ARM, but I have implemented clearwater-docker as part of the 
Models kubernetes demo deploy, which includes a full-stack k8s cluster 
deployment, ending with clearwater-docker deployment and test. See 
https://github.com/opnfv/models/tree/master/tools/kubernetes<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_models_tree_master_tools_kubernetes=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=uP_eo00sb1hRiLC3GV7bmnqaEyou9gD0ECr4JqsoCe0=zv6gXfjUtgACaMm2WRK0XNBiUVtYPgo92BbP87xckgQ=>
 for an overview of the process. The clearwater-docker deployment script is at 
k8s-cloudify-clearwater.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_models_blob_master_tests_k8s-2Dcloudify-2Dclearwater.sh=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=uP_eo00sb1hRiLC3GV7bmnqaEyou9gD0ECr4JqsoCe0=yHk0whL7zCYlHStQ4pgx7EQh3PqCmo2Ce4uE4rYASxk=>
 (note this currently uses kubectl to deploy… I am working on wrapping the 
charts in TOSCA so I can use cloudify-kubernetes to deploy it, over the 
cloudify-manager API).

Note that the models scripts use clearwater-docker containers built for this 
test. It may be possible to build them for ARM platforms, after which the rest 
of the deploy process should work as scripted. The build scripts are 
clearwater-docker.sh<https://urldefense.proofpoint.

Re: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and Arm pod at UNH

[SULLIVAN, BRYAN L (BRYAN L)]

Not specific to ARM, but I have implemented clearwater-docker as part of the 
Models kubernetes demo deploy, which includes a full-stack k8s cluster 
deployment, ending with clearwater-docker deployment and test. See 
https://github.com/opnfv/models/tree/master/tools/kubernetes for an overview of 
the process. The clearwater-docker deployment script is at 
k8s-cloudify-clearwater.sh
 (note this currently uses kubectl to deploy... I am working on wrapping the 
charts in TOSCA so I can use cloudify-kubernetes to deploy it, over the 
cloudify-manager API).

Note that the models scripts use clearwater-docker containers built for this 
test. It may be possible to build them for ARM platforms, after which the rest 
of the deploy process should work as scripted. The build scripts are 
clearwater-docker.sh
 and 
clearwater-live-test.sh.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
gerard.d...@wipro.com
Sent: Friday, February 16, 2018 12:08 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and Arm 
pod at UNH

Hello,

Does anyone have pointers to open-source (containerized) VNFs for Kubernetes ?
(something like this: 
http://dougbtv.com/nfvpe/2017/05/30/vnf-asterisk-kubernetes/,
 thanks Joe Kidder for sharing the link!)

Even more specifically, Arm-compatible VNFs ?

And which would be a recommended ONAP install setup (i.e. successfully tried at 
least once) to manage and use them ?
(among those listed at 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes).

The target for that installation is the Auto Arm pod at UNH IOL.

Best regards,
Gerard Damm


The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. 
www.wipro.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] [opnfv-tsc] For the TSC composition discussion on Tuesday

[SULLIVAN, BRYAN L (BRYAN L)]

Re “As for the mailing list/IRC contributions, the difficulty comes with 
identity mapping.  Trying to map IRC NICs/or email addresses with IDs used for 
the other tools is very challenging and will involve a lot of manual process.”

Anyone that wants their identity to be mapped (e.g. to strengthen their 
potential role in the election) should be aware of this discussion and should 
support your effort there. Generally though IMO our identities should not be 
that hard to map – most of us may use a couple of email addresses and probably 
one IRC handle. Further, email addresses associated with an LF identity should 
be obvious for any contributor/committer, as part of the gerrit record.

If you want help coordinating such a call for identity mapping, let me know. I 
think it’s important not to leave out email and IRC to the calculations.

But overall my main two points remain: we need to keep the bar low, and setup a 
process for concerns to be raised and addressed by the TSC. That will help 
ensure the process is equitable, for anyone who really cares.

Thanks,
Bryan Sullivan | AT

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Friday, February 16, 2018 10:57 AM
To: opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-...@lists.opnfv.org
Cc: Dave Neary <dne...@redhat.com>; SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com>
Subject: Re: [opnfv-tsc] [opnfv-tech-discuss] For the TSC composition 
discussion on Tuesday

As promised, here's a new spreadsheet with updated wiki contributor data.  Now 
the data should show beyond top 50 contributors and list anyone who contributed 
to the wiki in 2017.  Bitergia also fixed a bug they had as there were some 
undercounting of "page edits".

Thanks,

Ray


On Wed, Feb 14, 2018 at 8:55 AM, Raymond Paik 
<rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>> wrote:
A couple of clarifications.

When we say a "union of contributions" across all tools, we're setting a bar 
for total contributions across Git, Gerrit, Jira, and wiki.  So for example, if 
you had done 50 reviews + 2 merged patches + 30 Jira activities + 20 wiki 
edits, you have a 102 total contributions (and you'd clear the hurdle for 
either 50 or 100 contributions).  The discussion was that this maybe simpler 
than setting a different bar/hurdle for each tool.

As for the mailing list/IRC contributions, the difficulty comes with identity 
mapping.  Trying to map IRC NICs/or email addresses with IDs used for the other 
tools is very challenging and will involve a lot of manual process.

Hope this helps.

Thanks,

Ray

On Wed, Feb 14, 2018 at 6:28 AM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
I echo Dave's recommendation to be inclusive. The main reason not to be 
exclusive AIUI is to prevent gaming of the voting process. There are two ways 
to address that, while remaining inclusive:

1) set a reasonably low bar for participation

IMO anyone that is a regular attendee in OPNFV TSC or technical community 
calls, has made any level of peer-reviewed commit (outside their own company) 
over the last year, etc should be included. There are a core of people that 
should be obvious to us all, as involved, and they should certainly not be 
excluded. These include all current TSC members, PTLs, active committers, 
anyone active in any form of discussion, anyone contributing content in any 
form (code, tests, docs, wiki, ...), ...

2) provide a means for process concerns to be raised and addressed by the TSC

Dave's concern is an example. We need to be open to any such concern as a sign 
the process needs to be improved or an exception needs to be made (which really 
means the process needs to be improved, but for some reason we are not able to 
at this time...). Other types of concern may be raised by analytics on the 
voting process, which should be shared with the community (every voter should 
be associated with a member company, or identified as independent, so we can 
ensure reasonable equity in the voting process). There should be a place on the 
wiki etc for raising these concerns so they can be tracked and the thread of 
addressing them is recorded.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: 
opnfv-tsc-boun...@lists.opnfv.org<mailto:opnfv-tsc-boun...@lists.opnfv.org> 
[mailto:opnfv-tsc-boun...@lists.opnfv.org<mailto:opnfv-tsc-boun...@lists.opnfv.org>]
 On Behalf Of Dave Neary
Sent: Wednesday, February 14, 2018 5:49 AM
To: Raymond Paik <rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>>; 
opnfv-tech-discuss 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>;
 opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Subject: Re: [opnfv-tsc] [opnfv-tech-discuss] For the TSC composition 
discussion on Tuesday

[Note post TSC call: this

[opnfv-tech-discuss] {releng-anteater] project_scan.py check for top-level license needs enhancements

[SULLIVAN, BRYAN L (BRYAN L)]

I'm not sure how/where to raise this as a bug, so I created a JIRA issue: 
https://jira.opnfv.org/browse/RELENG-346

Anteater needs to verify that the project top-level license file is correctly 
formatted ("Licence string present"), and accept any variation of file name 
"LICENSE*" (e.g. LICENSE.txt) as a valid present license file.

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] [opnfv-tsc] For the TSC composition discussion on Tuesday

[SULLIVAN, BRYAN L (BRYAN L)]

I echo Dave's recommendation to be inclusive. The main reason not to be 
exclusive AIUI is to prevent gaming of the voting process. There are two ways 
to address that, while remaining inclusive:

1) set a reasonably low bar for participation

IMO anyone that is a regular attendee in OPNFV TSC or technical community 
calls, has made any level of peer-reviewed commit (outside their own company) 
over the last year, etc should be included. There are a core of people that 
should be obvious to us all, as involved, and they should certainly not be 
excluded. These include all current TSC members, PTLs, active committers, 
anyone active in any form of discussion, anyone contributing content in any 
form (code, tests, docs, wiki, ...), ...

2) provide a means for process concerns to be raised and addressed by the TSC

Dave's concern is an example. We need to be open to any such concern as a sign 
the process needs to be improved or an exception needs to be made (which really 
means the process needs to be improved, but for some reason we are not able to 
at this time...). Other types of concern may be raised by analytics on the 
voting process, which should be shared with the community (every voter should 
be associated with a member company, or identified as independent, so we can 
ensure reasonable equity in the voting process). There should be a place on the 
wiki etc for raising these concerns so they can be tracked and the thread of 
addressing them is recorded.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Wednesday, February 14, 2018 5:49 AM
To: Raymond Paik ; opnfv-tech-discuss 
; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tsc] [opnfv-tech-discuss] For the TSC composition 
discussion on Tuesday

[Note post TSC call: this is the email I had written and found in my
Drafts folder after the TSC call - so I had not sent it - DN]

Thank you for putting this together, Ray!

A few comments: Your wiki stats look off - I would expect to see many
more people in the list (of course the first thing I did out of vanity
was look for myself, and I have definitely made a number of wiki edits
and comments, but I am not in the list).

We have so far discussed erring on the side of inclusion, so I am
curious about your setting a bar at 50 or 100 contributions. It might
make sense to have a minimum number for some of the lower impact
activities like Gerrit reviews, but for others like patch submission, a
lower bound of 1 might make more sense. For wiki edits 5 or 10 seems
reasonable. If using a composite metric, I would lean towards a lower
number (say, 20) rather than higher, to be more inclusive.

Have you considered being active on the mailing list as a potential
market of activity? Again the question of whether people who are active
on the list, but inactive elsewhere, can be considered active
contributors (I think they could) - there, perhaps 30 emails during the
year is a good level.

I would also be interested to hear if there are people who previously
had a vote as committers, who would not have a vote under this scheme,
or whether there is a big difference in the size of the
community/electorate with your proposed levels.

What do you think?

Thanks,
Dave.

On 02/12/2018 01:12 AM, Raymond Paik wrote:
> All, 
> 
> This is for the TSC composition discussion on Tuesday.  
> 
> As was discussed previously
>   >,
> there was a consensus to look at a "union of contributions" across
> various tools in OPNFV including Git, Gerrit, JIRA, and Confluence.  For
> example, we talked about people making a total of 50 or 100
> contributions across all tools over a 12 month period as the constituent
> for the TSC election.
> 
> In the attached, you'll see the data point across the 4 tools in 2017. 
> In the last tab, you'll also find a comparison of "top 50 contributors"
> across the tools.  Although there are some exceptions, you'll see that
> active contributors are active across all 4 tools.  One of the concerns
> was that we want to be inclusive to recognize non-code contributions and
> you'll see a high number of non-code contributors in both Gerrit and Jira.
> 
> In terms of a threshold, 100 annual contributions seems like a good
> starting point.  As a point of reference, the following shows the number
> of people that made 100 or more contributions in each tool.  (Based on
> this, we'll have a minimum of 112 people eligible for the TSC election
> as we have 112 people that made 100 or more contributions to Gerrit alone)
> 
>   * 

Re: [opnfv-tech-discuss] Anteater status and link issue

[SULLIVAN, BRYAN L (BRYAN L)]

Comments etc inline

Thanks,
Bryan Sullivan | AT

From: Luke Hinds [mailto:lhi...@redhat.com]
Sent: Monday, February 12, 2018 9:04 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org; degirmenci, fatih 
<fatih.degirme...@ericsson.com>; Raymond Paik <rp...@linuxfoundation.org>
Subject: Re: [opnfv-tech-discuss] Anteater status and link issue



On Tue, Feb 6, 2018 at 2:32 PM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi all,
I’m wondering where the Anteater program is – and want to note a broken link: 
build jobs with Anteater violations reference “Please visit: 
https://wiki.opnfv.org/x/5oey<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_x_5oey=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=s4zQHMsxrgVhlTs-Sw4-uGIsKYDMsnIQuvx0TehUoSk=>”,
 which is the wiki page 
https://wiki.opnfv.org/pages/viewpage.action?pageId=11700198<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D11700198=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=burTDZjfgUSG9lAKW4MjRDZULxleQEsKGknHvhdqzbA=>,
 which says “Project specific exceptions can be added for file_name, 
file_contents and binaries, by using the name of the repository within the 
anteater/exceptions/ directory of the 
releng-anteater<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_gerrit.opnfv.org-3A29418_releng-2Danteater.git=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=LrWykp0HOa_RUbxOEJDo7sojbPgNgsVsrlV6jmwMVx4=>
 repository.” – but that link 
(releng-anteater<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_gerrit.opnfv.org-3A29418_releng-2Danteater.git=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=LrWykp0HOa_RUbxOEJDo7sojbPgNgsVsrlV6jmwMVx4=>)
 is broken.
I want to start adding the exceptions for Models etc as an example for the LF 
IT team that is setting up the Acumos project gerrit/CI/CD process, and in 
general to help optimize the Anteater overhead for projects. I think we need to 
get some analysis of the types of exceptions that are typical, and establish a 
process for vetting those exceptions that goes beyond a simple review by a 
releng committer.
Further, we need to bring in other scan tools (e.g. security vulnerability, 
virus, or malicious code scans) into the Anteater process. This is in response 
to concerns about the security of the governance process for open source (e.g. 
upstream, but also direct contribution in projects) that is used to build 
production-oriented systems. We need to demonstrate that OPNFV and other LF 
projects are addressing these concerns through their infra toolsets.

Sorry Bryan, I missed a few of these emails thanks (or rather no thanks) to a 
bad mail filter rule.
I am working on the following now which we will see soon:
Much better documentation: 
http://anteater.readthedocs.io/en/latest/<https://urldefense.proofpoint.com/v2/url?u=http-3A__anteater.readthedocs.io_en_latest_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=AdeEyIqajKWRGD1zz3MXcKrWoAWYR6mXmQDgVVzp1Zo=>
[bryan] Are you going to start hosting these docs at docs.opnfv.org?
Virus total integration:
   * Any binaries will be scanned using the virus total API, unless a sha256 
waiver is already present e.g. 
https://github.com/opnfv/releng-anteater/blob/master/exceptions/calipso.yaml#L9<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_releng-2Danteater_blob_master_exceptions_calipso.yaml-23L9=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=rxS4DJ0v-VW97BzYjY1_yRCmM1znHlxObcXiTIP6RBI=WNetEYMktH0pxwVzSJXZyDFVnJr6lIDBhM6laGBrbjs=>
   * Any IP addresses / domain name / URL will be scanned (again using the 
Virus Total API) for known malware and other nastiness.
[bryan] VirusTotal looks like a useful service. Are there any stats for its 
effectiveness at detecting threats, including new threats and delay in 
supporting them?
I also have a load of new strings to add to dig out and report anything of a 
more recent finding (for example a javascript based bitcoin miner).
[bryan] I would like to see how we can improve the contextual effectiveness of 
the pattern matching approach. Any bar (or port in a storm) may seem to be 
better than none, and can at least catch newbie mistakes and anti-patterns, but 
most of the strings I’ve included in 
https://github.com/opnfv/models/blob/master/tools/anteater-exceptions.yaml 
relate to IMO innocuous (if admittedly sometimes cheap or anti-

[opnfv-tech-discuss] [Infra] Latest docs for connecting to Jenkins

[SULLIVAN, BRYAN L (BRYAN L)]

Is the document 
http://docs.opnfv.org/en/latest/submodules/octopus/docs/octopus_docs/opnfv-jenkins-slave-connection.html
 still valid?
I see very little info in the docs e.g. 
http://docs.opnfv.org/en/latest/infrastructure/ci.html, and need to know what 
is the current process for connecting to Jenkins, so I can first implement this 
internally, test it out, and then when ready connect to the OPNFV Jenkins.

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] FW: [OPNFV Helpdesk #52339] AutoReply: Wiki appears somewhat broken

[SULLIVAN, BRYAN L (BRYAN L)]

FYI you may have seen some strange rendering etc on the wiki as below. FYI I 
filed a helpdesk ticket on this.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: OPNFV Helpdesk via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Monday, February 12, 2018 1:16 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Subject: [OPNFV Helpdesk #52339] AutoReply: Wiki appears somewhat broken

Greetings,

Your support ticket regarding:
"Wiki appears somewhat broken",
has been entered in our ticket tracker.  A summary of your ticket appears below.

If you have any follow-up related to this issue, please reply to this email.

You may also follow up on your open tickets by visiting 
https://urldefense.proofpoint.com/v2/url?u=https-3A__rt.linuxfoundation.org_=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=vmy-99xIqnwxpcONrq_mwZxXeF83IM8ZQp8trrBoVDE=HPWf61WqgfOx8nUAe9j8zwDXahitzhu9O3DTJFybAp8=
  -- if you have not logged into RT before, you will need to follow the "Forgot 
your password" link to set an RT password.

-- 
The Linux Foundation Support Team


-
Something has happened to the wiki:

  *   It required login and when that was completed, it threw an error 
indicating a Java version check failed
  *   The rendering is different, e.g. the base font has changed, the menu 
buttons at the top now wrap (and have no border), ...

Looks like some upgrade/config had some unintended side-effect.

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] Issues with Anteater pretest process

[SULLIVAN, BRYAN L (BRYAN L)]

Julien,

I figured out how to get it working and developed a script for it. I’ll work on 
making it generic so it can be used by any OPNFV project. I’m working on using 
the tool to scan the code for other projects as well. I did find a bug – the 
project name cannot have a “-“ otherwise the tool throws a python exception. I 
found this when running the tool against non-OPNFV projects. I had to figure 
out how to add them to the master-list.yaml but once that was done, I was able 
to run the tool against any arbitrary git repo.

The script is at https://github.com/opnfv/models/blob/master/tools/anteater.sh

I do think the Anteater tool needs a good bit of work, as evidenced by the long 
list of exceptions I had to create for Models: 
https://github.com/opnfv/models/blob/master/tools/anteater-exceptions.yaml
Most of these are due to the tool’s assumption that certain strings are 
problematic, without considering the context of where those strings appear.

I think other more robust and vulnerability-specific tools may also be needed 
in OPNFV, e.g. OpenSCAP and Fossology as I recommended when the security 
scanning project was first proposed. And we need to support iterative license 
scanning for tightly integrated code, e.g. imported modules, to ensure that 
OPNFV code is compatible with the license of all tightly integrated code. Note 
“tightly integrated” means it becomes part of the application, thus rules 
related to GPL license for example apply. This in comparison to loosely 
integrated code e.g. through APIs, or running as separate processes and 
providing some system service.

Thanks,
Bryan Sullivan | AT

From: Julien [mailto:julien...@gmail.com]
Sent: Tuesday, February 06, 2018 10:20 PM
To: Fatih Degirmenci <fatih.degirme...@ericsson.com>
Cc: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; 
opnfv-tech-discuss@lists.opnfv.org; Luke Hinds <lhi...@redhat.com>
Subject: Re: [opnfv-tech-discuss] Issues with Anteater pretest process

Hi Bryan,

I have happened to work together with Luke on this project for some time. It's 
really cool.
Thanks for your interests.

For the anteater container is already there in the docker hub, you can directly 
use it without building from the very beginning.
Luke, you can help to verify the steps.

Several steps,
1. docker pull opnfv/releng-anteater
2. take Pharos project for example
3. docker run -it opnfv/releng-anteater -v 
/Users/julien/Documents/git/opnfv/pharos:/home/opnfv/anteater/pharos
   I only map Pharos repo into the container to /home/opnfv/anteater/pharos.
   any target path is OK.
4. /home/opnfv/venv/bin/anteater -p pharos --path pharos/

You can get some helpful info through:

/home/opnfv/venv/bin/anteater -h
Anteater - CI Gate Checks.

Usage:
  anteater (-p |--project)  [(-ps |--patchset) ]
  anteater (-p |--project)  [--path ]
  anteater (-h | --help)
  anteater --version

Options:
  -h --help Show this screen.
  --version Show version.

The only thing I want to mention is that project_path is a  mandatory argument 
when you want to scan for the whole project.
-p project: to indicate which project to scan for we have some exceptions name 
with this project name.

5. You can get the report log in .reports sub-directory besides terminal
[opnfv@c96175c845be anteater]$ ll .reports/
total 76
-rw-rw-r-- 1 opnfv opnfv 48546 Feb  7 06:14 anteater.log
-rw-rw-r-- 1 opnfv opnfv  9444 Feb  7 06:14 binaries-pharos.log
-rw-rw-r-- 1 opnfv opnfv  8630 Feb  7 06:14 contents-pharos.log
-rw-rw-r-- 1 opnfv opnfv  1030 Feb  7 06:14 licence-pharos.log

Regards,
Julien

Fatih Degirmenci 
<fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>>于2018年2月7日周三
 上午3:38写道：
Hi Bryan,

Anteater is used for gating patches coming to OPNFV projects. See the Jenkins 
job configuration to see patches of which projects are gated.

https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/ci_gate_security/opnfv-ci-gate-security.yml<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_gitweb-3Fp-3Dreleng.git-3Ba-3Dblob-3Bf-3Djjb_ci-5Fgate-5Fsecurity_opnfv-2Dci-2Dgate-2Dsecurity.yml=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=29tOLifHP4ypkHyoj-0ME63HMvkxwFChpECoenBhUbc=uvfiqxpMlCi8liP2QlYw-LYV3xHmlphuK--TLQN5gLk=>

And see the script that is executed by Jenkins job.

https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/ci_gate_security/anteater-security-audit.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_gitweb-3Fp-3Dreleng.git-3Ba-3Dblob-3Bf-3Djjb_ci-5Fgate-5Fsecurity_anteater-2Dsecurity-2Daudit.sh=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=29tOLifHP4ypkHyoj-0ME63HMvkxwFChpECoenBhUbc=terU3K4ZCHsx1Vl6jH6coKwOjQ5gRohxDDFRkiNb9Oc=>

Adding Luke who is maintaining Anteater.

/Fatih

From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv

Re: [opnfv-tech-discuss] Issues with Anteater pretest process

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Is anyone using this toolset for a project? I am trying to follow the 
instructions as below (I did figure out that you have to clone anteater 
first... that needs to be updated on the wiki).

But the rest of the instructions just don't work. It's not clear how to run the 
anteater process once in the container. "anteater" is not in the path, and 
running "pip install ." on the root folder seems to build something, but it's 
still not in the path and it's not clear how to invoke the tool.

Anyone supporting this tool - please respond asap so I can get an impression if 
I should continue down this path.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, February 06, 2018 6:43 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: Issues with Anteater pretest process

Hi all,

I'm starting to look at the pretest process for Anteater patches as described 
under "How can I test my entire project or pretest a patch?" at 
https://wiki.opnfv.org/pages/viewpage.action?pageId=11700198. The first 
instruction is not working:

if you would like to perform a full retrospective check of your project, you 
can do so on any machine capable of running Docker. Follow these steps..
Pull the anteater Docker image and build.
docker build -t anteater .


That command (docker build) is for building a container based upon a 
Dockerfile. It seems there's a missing step - clone the Anteater repo and cd to 
the folder that contains the Anteater Dockerfile. Is that what was intended?

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] Issues with Anteater pretest process

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

I'm starting to look at the pretest process for Anteater patches as described 
under "How can I test my entire project or pretest a patch?" at 
https://wiki.opnfv.org/pages/viewpage.action?pageId=11700198. The first 
instruction is not working:

if you would like to perform a full retrospective check of your project, you 
can do so on any machine capable of running Docker. Follow these steps..
Pull the anteater Docker image and build.
docker build -t anteater .


That command (docker build) is for building a container based upon a 
Dockerfile. It seems there's a missing step - clone the Anteater repo and cd to 
the folder that contains the Anteater Dockerfile. Is that what was intended?

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] Test Results Dashboard

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

I see that the design of http://testresults.opnfv.org has evolved. Quick 
suggestions/questions.

  *   Is it possible to reduce the size of the tiles in the UI? I don't see how 
the tiles so large add a lot of value.
  *   The info for past releases seems to be missing/broken
  *   For master, the data is there (e.g. 
http://testresults.opnfv.org/master/functest/status-apex.html) but only for Apex
  *   It takes a lot of clicks to get to the details. The presentation ala 
http://testresults.opnfv.org/master/functest/status-apex.html is really what we 
need to see, so is there a way to simply have the main page  
http://testresults.opnfv.org just present an outline view of the subpages for 
master (first), then the previous releases in reverse order? This would make 
the site easier to use.


FYI I am looking to bring the basic test results dashboard concept (status 
meter, trend graph, score, iterations, ...) to the Acumos project's CI/CD team. 
This is a valuable approach to tracking project status and the trend of 
build/tests, and it would be good to share the OPNFV expertise in this at the 
right time (at ONS would be great).

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] Could ways of working with testing frameworks be improved when working with master?

[SULLIVAN, BRYAN L (BRYAN L)]

Manuel,

Apart from the basic issue you are facing being dependency on test frameworks 
(which can be a convenient tool, until they change out from under you without 
notice), the basic problem OPNFV faces here is that it needs to, and easily 
can, provide such notice automatically. For example, when there is a patch that 
will cause dependencies to break, the easiest case being that some function no 
longer exists, it should be straightforward to run a scan of all OPNFV repos to 
check for references to that function. Other cases, e.g. where a function 
changes in definition/input etc may be harder, but there should also be notice 
somehow, supported by a similar scan for references to that function.

In Models, VES, and Copper, I solve the basic problem you are facing by not 
depending upon any of the test frameworks/utils, and to the extent possible on 
none of the installer frameworks/utils either. But in your case I agree the 
community should support effective notice that something is likely to break.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Manuel Buil
Sent: Friday, February 02, 2018 4:00 AM
To: OPNFV-TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] Could ways of working with testing frameworks be 
improved when working with master?

Hi,

As you know, the SFC project is currently testing openstack master, that means 
we need to use functest master in order to consume the lastest patches in the 
projects we use. Unfortunately, in the last weeks, we wasted quite some time 
trying to understand why suddenly the tests were not able to run and the cause 
was a change in the master branch of functest. For example, we are using the 
function "timethis" from functest_utils, which was removed by this patch: 
https://github.com/opnfv/functest/commit/c6092cb676363d89f366dc9a416ba6c53eeea33f#diff-b5f06ecfb223c80624f432ef33cf1fdd
 and suddenly our tests are not working and we don't know whether there is an 
alternative.

Functest is the framework we use for our tests and ideally, we (SFC project) 
would like to get some heads up before that change is done, so that we are 
warned and we don't have to waste time investigating what changed. I guess the 
same could be applied to other core testing frameworks like Yardstick. However, 
this is complicated and I am not sure if there is a good solution to achieve 
that level of communication without impacting the efficiency of 
funcatest/yardstick/... development. I have some ideas:

A) Functest/Yarstick leave the old functionality for a week adding a log saying 
"This is going to be deprecated, please check this patch: "

B) Add gates in functest/yardstick projects which run tests of their customer 
projects (as in, SFC is a customer of functest). This way, projects could be 
warned on time

C) Do nothing. Sorry, this is the consequence of consuming functest/yardstick 
master

D) ??

From what I heard in the TSC, Apex is going to join the XCI philosophy and 
allow working with the tip of master, so it seems to me that more functest and 
potentially yardstick users are going to hit this problem, that's why I believe 
it could be a good time to discuss possible solutions.

Please don't get me wrong, I am not trying to blame functest (or yardstick), I 
just want to share the problems we are having with the current ways of working 
and try to find a solution :)

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

Re: [opnfv-tech-discuss] Seeking demo ideas for LFN booth at ONS

[SULLIVAN, BRYAN L (BRYAN L)]

Brandon,

I’ll be there and can provide a demo from the Models/VES projects of 
closed-loop lifecycle management for VNFs on cloud-native stacks. I’ll be using 
Clearwater-docker as the VNF, with the stack (Kubernetes, Cloudify (as VNFM), 
VES, and if possible ONAP etc) as described at 
https://github.com/opnfv/models/tree/master/tools/kubernetes.

I’m organizing the booth demos etc for the Acumos project at the same event, so 
we can further have a chance to discuss use cases for network efficiency and 
service optimization through AI/ML models developed in the Acumos project. If I 
can work up a policy microservice using a simple ML model based upon VES data 
in the meantime, I’ll add that to the demo.

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: Tuesday, January 30, 2018 11:06 PM
To: Tim Irnich 
Cc: opnfv-tech-dis. 
Subject: Re: [opnfv-tech-discuss] Seeking demo ideas for LFN booth at ONS

Thanks for the thought starters Tim and thanks to all that have submitted demo 
ideas. If you have an idea, but haven't submitted directly to me yet, please do 
so by EOD tomorrow (1/31). Note: The notification date is being pushed out to 
Feb 7.


Brandon Wick
Senior Integrated Marketing Manager, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org


On Fri, Jan 26, 2018 at 1:41 AM, Tim Irnich 
> wrote:
Hi Brandon, all,

thanks for highlighting this opportunity.

Off the top of my head, a couple of ideas what OPNFV might be able to show:

  *   LaaS: explain the idea, demo resource booking via the dashboard, show how 
a pre-deployed OPNFV scenario gets spun up & handed over to the user.
  *   New test dashboards: Explain the OPNFV test ecosystem, show how we use 
the dashboards to visualize quality improvements and capability gains over a 
development cycle
  *   Use of XCI for upstream patchset verification/gating using another LFN 
project as example (ODL?)

Just a starting point of course, and although I am aware that we basically need 
to submit ideas today, I’d assume putting together a rough proposal should 
still be possible. Any volunteers to drive one of the above topics or any other 
ideas?

Should there be any other OPNFV-related proposals underway, I’d be grateful if 
those could be shared in this thread for community visibility.

Let’s make sure OPNFV gets the visibility it deserves!

Regards, Tim

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Brandon Wick
Sent: Friday, January 19, 2018 08:19
To: opnfv-tech-dis. 
>
Subject: [opnfv-tech-discuss] Seeking demo ideas for LFN booth at ONS

OPNFV Tech Community:

We wanted to reach out and let you know that there will be space for a few 
demos in the LF Networking (LFN) Booth at ONS. We've received a couple good 
ideas already and are looking for a few more to consider. Our goal is to show 
compelling uses of LFN networking project technology to solve real world 
industry challenges. Demos that show cross-project elements (e.g. between ODL, 
ONAP, OPNFV, FD,io), that map to a specific industry use case, and that are 
endorsed by a service provider are preferred. That said, we have some room for 
demos that highlight the innovative work and value-add from projects that don't 
necessarily meet these criteria.

Please submit your demo ideas by January 26 by sending an email to 
bw...@linuxfoundation.org. LFN staff 
leadership will then review the options make the final determination which 
demos can be accommodated. Idea submitters will be notified by February 2.

In your email describing your demo idea and requirements, please indicate who 
the demo manager(s) will be. A demo manager is required as part of each demo 
proposal and will be responsible for the following:
•  Define the scope and storyline of the demo
•  Respond promptly to requests for additional information
•  Meet all requested deadlines
•  Setup and test the demo pre-show
•  Staff the demo during the expo hours (along with some other designated team 
members to help share the load)
•  Be willing to participate in media activities, e.g. video
•  Take down the demo post event
ONS sponsors are of course welcome to host demos in their booths on the show 
floor. Check with your sponsorship managers to explore these opportunities.

Please let me know if you have any questions and we look forward to hearing 
your ideas.

Best,

Brandon Wick
Senior Integrated Marketing Manager, The Linux Foundation

Re: [opnfv-tech-discuss] Issues building clearwater-live-test

[SULLIVAN, BRYAN L (BRYAN L)]

An update - I have found that the homestead service is not showing up in kube 
dns so the sprout checks on the Register request (which is getting there) is 
failing, thus the Forbidden response. So my issue seems to be related to how 
the clearwater-docker images are being deployed in k8s (all of the other 
services do show up in kube dns... just this one doesn't).

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Friday, January 26, 2018 6:20 AM
To: Valentin Boucher <valentin.bouc...@kontron.com>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Issues building clearwater-live-test

Thanks, I'll try it out. I did find in the interim a pre-built pjsua container 
(https://hub.docker.com/r/andrius/pjsua/) after also failing to build that 
client from the docs (what is it with docs?), and have been using it to attempt 
registration with the deployment. I can get the Bono pod to respond to 
registration requests but it always rejects them as "forbidden". I'm not sure 
what combination of these issues I'm facing but any advice is appreciated. It 
may be:

  *   I don't have the deployment configured correctly: I have made no 
changes/config settings for the pods - I just built the clearwater-docker 
images and deployed them in the same k8s namespace. So they should all be able 
to find each other by their default ports within the cluster. I know at least 
that part is working.
  *   Homestead and homestead-prov keep going through crashloops. So far this 
only seems to affect the user portal (sometimes Ellis can't display the 
dashboard settings for a user)
  *   I'm not using the correct values for the various fields in the register 
command... it's been 10 years since I led work in OMA on SIP/IMS PUSH... some 
complete examples that work with clearwater, mapped to the default deployment 
settings for clearwater would be *great*. Here's are a couple of examples: in 
these cases the password is the value shown (one time) by Ellis after I created 
the account. It's unclear whether I should use that in the register command, or 
the password that the user created when signing up at the portal (I assume it's 
the former, but it's not helping).



pjsua --app-log-level=4 --log-level=6 --realm=example.com 
--username=j...@example.com<mailto:--username=j...@example.com> 
--id=sip:j...@example.com --password=vgDeqmE5V --null-audio 
--registrar=sip:example.com --use-ims



pjsua --app-log-level=4 --log-level=6 --realm=default.svc.cluster.local 
--username=b...@default.svc.cluster.local<mailto:--username=b...@default.svc.cluster.local>
 --id=sip:b...@default.svc.cluster.local --password=jSv9QmERE --null-audio 
--registrar=sip:default.svc.cluster.local --use-ims

Are there docs that can help me with these questions above, somewhere? Sorry to 
ask for all this help and if you're too busy I understand. I'll keep looking 
and put whatever I find that works on the wiki.

Thanks,
Bryan Sullivan | AT

From: Valentin Boucher [mailto:valentin.bouc...@kontron.com]
Sent: Friday, January 26, 2018 5:41 AM
To: SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE:Issues building clearwater-live-test

Bryan,

The doc is not really up to date 

I write a new docker file [1] only for clearwater-live-test base on the vnf 
functest Dockerfile.
I test it, and it's work.
So, After your docker build you can run this commands:

  *   docker run -it  sh #you can add the --dns arg if you want to 
specify the dns ip of the clearwater deployment
  *   cd /src/vims-test
  *   rake test['<your_sip_domain'>] SIGNUP_CODE=''



Valentin



[1] The docker file:



FROM alpine:3.7

ARG VIMS_TAG=stable

RUN apk --no-cache add --update \
ruby ruby-bundler ruby-irb ruby-rdoc dnsmasq \
procps libxslt libxml2 zlib libffi git && \
apk --no-cache add --virtual .build-deps --update \
ruby-dev g++ make libxslt-dev libxml2-dev zlib-dev libffi-dev && \
git clone --depth 1 -b $VIMS_TAG 
https://github.com/boucherv-orange/clearwater-live-test<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_boucherv-2Dorange_clearwater-2Dlive-2Dtest=DwQF-g=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=7ISkxR4ctGen7_SdupsCan6p1oRX4XC1d4twQFb489Q=_dfsRJ-BQn2P5FX1O0wVUZr2R2XB2Qj3smU24KFckRg=>
 /src/vims-test && \
(cd /src/vims-test && bundle config build.nokogiri --use-system-libraries 
&& bundle install --system) && \
apk del .build-deps




De : SULLIVAN, BRYAN L (BRYAN L) [bryan.sulli...@research.att.com]
Envoyé : jeudi 25 janvier 2018 15:55
À : Valentin Boucher; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Objet : RE: Issues building clearwater-live-test
Valentin,

Re: [opnfv-tech-discuss] Issues building clearwater-live-test

[SULLIVAN, BRYAN L (BRYAN L)]

Thanks, I'll try it out. I did find in the interim a pre-built pjsua container 
(https://hub.docker.com/r/andrius/pjsua/) after also failing to build that 
client from the docs (what is it with docs?), and have been using it to attempt 
registration with the deployment. I can get the Bono pod to respond to 
registration requests but it always rejects them as "forbidden". I'm not sure 
what combination of these issues I'm facing but any advice is appreciated. It 
may be:

  *   I don't have the deployment configured correctly: I have made no 
changes/config settings for the pods - I just built the clearwater-docker 
images and deployed them in the same k8s namespace. So they should all be able 
to find each other by their default ports within the cluster. I know at least 
that part is working.
  *   Homestead and homestead-prov keep going through crashloops. So far this 
only seems to affect the user portal (sometimes Ellis can't display the 
dashboard settings for a user)
  *   I'm not using the correct values for the various fields in the register 
command... it's been 10 years since I led work in OMA on SIP/IMS PUSH... some 
complete examples that work with clearwater, mapped to the default deployment 
settings for clearwater would be *great*. Here's are a couple of examples: in 
these cases the password is the value shown (one time) by Ellis after I created 
the account. It's unclear whether I should use that in the register command, or 
the password that the user created when signing up at the portal (I assume it's 
the former, but it's not helping).



pjsua --app-log-level=4 --log-level=6 --realm=example.com 
--username=j...@example.com --id=sip:j...@example.com --password=vgDeqmE5V 
--null-audio --registrar=sip:example.com --use-ims



pjsua --app-log-level=4 --log-level=6 --realm=default.svc.cluster.local 
--username=b...@default.svc.cluster.local 
--id=sip:b...@default.svc.cluster.local --password=jSv9QmERE --null-audio 
--registrar=sip:default.svc.cluster.local --use-ims

Are there docs that can help me with these questions above, somewhere? Sorry to 
ask for all this help and if you're too busy I understand. I'll keep looking 
and put whatever I find that works on the wiki.

Thanks,
Bryan Sullivan | AT

From: Valentin Boucher [mailto:valentin.bouc...@kontron.com]
Sent: Friday, January 26, 2018 5:41 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE:Issues building clearwater-live-test

Bryan,

The doc is not really up to date 

I write a new docker file [1] only for clearwater-live-test base on the vnf 
functest Dockerfile.
I test it, and it's work.
So, After your docker build you can run this commands:

  *   docker run -it  sh #you can add the --dns arg if you want to 
specify the dns ip of the clearwater deployment
  *   cd /src/vims-test
  *   rake test['<your_sip_domain'>] SIGNUP_CODE=''



Valentin



[1] The docker file:



FROM alpine:3.7

ARG VIMS_TAG=stable

RUN apk --no-cache add --update \
ruby ruby-bundler ruby-irb ruby-rdoc dnsmasq \
procps libxslt libxml2 zlib libffi git && \
apk --no-cache add --virtual .build-deps --update \
ruby-dev g++ make libxslt-dev libxml2-dev zlib-dev libffi-dev && \
git clone --depth 1 -b $VIMS_TAG 
https://github.com/boucherv-orange/clearwater-live-test<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_boucherv-2Dorange_clearwater-2Dlive-2Dtest=DwQF-g=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=7ISkxR4ctGen7_SdupsCan6p1oRX4XC1d4twQFb489Q=_dfsRJ-BQn2P5FX1O0wVUZr2R2XB2Qj3smU24KFckRg=>
 /src/vims-test && \
(cd /src/vims-test && bundle config build.nokogiri --use-system-libraries 
&& bundle install --system) && \
apk del .build-deps




De : SULLIVAN, BRYAN L (BRYAN L) [bryan.sulli...@research.att.com]
Envoyé : jeudi 25 janvier 2018 15:55
À : Valentin Boucher; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Objet : RE: Issues building clearwater-live-test
Valentin,

Thanks for the advice. Some more notes and questions:

Your repo does not include a Dockerfile. So I created one with the instructions 
in the readme. I had to make the following updates to your instructions:

  *   Using a xenial base, start with "apt-get update" (otherwise 
build-essential etc did not install - "unable to locate package")
  *   I had to add "curl gnupg2" to the apt-get list
  *   Various other tweaks to get the instructions to run as via the dockerfile 
(e.g. as root), mostly related to getting rvm to install

However, once the container is deployed, it seems the sequence of install steps 
did not complete somehow as I get:
root@clearwater-live-test:/# rake
/usr/local/bin/rake:23:in `load': cannot load such file -- 
/usr/share/rubygems-integration/all/gem

Re: [opnfv-tech-discuss] Issues building clearwater-live-test

[SULLIVAN, BRYAN L (BRYAN L)]

Valentin,

Thanks for the advice. Some more notes and questions:

Your repo does not include a Dockerfile. So I created one with the instructions 
in the readme. I had to make the following updates to your instructions:

  *   Using a xenial base, start with "apt-get update" (otherwise 
build-essential etc did not install - "unable to locate package")
  *   I had to add "curl gnupg2" to the apt-get list
  *   Various other tweaks to get the instructions to run as via the dockerfile 
(e.g. as root), mostly related to getting rvm to install

However, once the container is deployed, it seems the sequence of install steps 
did not complete somehow as I get:
root@clearwater-live-test:/# rake
/usr/local/bin/rake:23:in `load': cannot load such file -- 
/usr/share/rubygems-integration/all/gems/rake-10.5.0/bin/rake (LoadError)
from /usr/local/bin/rake:23:in `'

Also, once I get past that... it's not clear from the readme what needs to be 
done, next. Are there examples somewhere of the  IMS tests that need to be 
referenced in the rake command? Or is there a way to use the shell for 
something simpler?

Here's the dockerfile I am using. One quick question on this: is xenial OK or 
is there some other ubuntu version I need to use?

FROM ubuntu:xenial

MAINTAINER Bryan Sullivan

RUN apt-get update && apt-get install -y build-essential bundler git curl gnupg2
RUN gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
RUN curl -L 
https://raw.githubusercontent.com/rvm/rvm/master/binscripts/rvm-installer -o 
~/rvm-installer

# This is not a user-based install, use --ignore-dotfiles
RUN /bin/bash -c "source ~/rvm-installer --ignore-dotfiles stable"
RUN /bin/bash -c "source /usr/local/rvm/scripts/rvm"
# Set the path to the rvm binary
RUN /bin/bash -c "export PATH=$PATH:/usr/local/rvm/bin; rvm autolibs enable; 
rvm autolibs enable; rvm install 1.9.3; rvm use 1.9.3; ruby --version"
# should indicate that ruby 1.9.3 is in use

RUN git clone https://github.com/Metaswitch/clearwater-live-test.git
RUN cd clearwater-live-test && bundle install


Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Valentin 
Boucher
Sent: Thursday, January 25, 2018 8:47 AM
To: Bryan Sullivan ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Issues building clearwater-live-test

Hi bryan,

In functest cloudify_ims testcase we use a fork of this clearwater live test 
repository.
By default the clearwater live test only print the results on the terminal .. 
So I update that code to have a json result file in order to put that in the 
opnfv test result api!

The build of functest docker vnf (including this test suite) work well and the 
version of quaff is 0.7.2
-> 
https://github.com/boucherv-orange/clearwater-live-test/blob/stable/Gemfile.lock#L47

Armband team, also update one dependency to support this container on arm64 
server!

Valentin

De : 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de Bryan Sullivan 
[bls...@hotmail.com]
Envoyé : jeudi 25 janvier 2018 11:35
À : 
opnfv-tech-discuss@lists.opnfv.org
Objet : [opnfv-tech-discuss] Issues building clearwater-live-test
Does anyone have contacts at Metaswitch that could help with this issue? I have 
tried joining their mail list but am getting no response.

When I build the docker container as described 
(https://github.com/Metaswitch/clearwater-live-test
 : "Simply run docker build -t clearwater/live-test . from within the 
clearwater-live-test/ directory. ") I get the following error. Same error with 
their stable branch.
Step 7/7 : RUN bundle install
 ---> Running in 81dc14cd34d7
Fetching gem metadata from 
https://rubygems.org/.
Fetching 

[opnfv-tech-discuss] Article on Containers with GPL and non-GPL Code

[SULLIVAN, BRYAN L (BRYAN L)]

In case anyone was wondering about this, see this article which addresses 
questions about incorporation of non-copyleft (e.g. Apache 2.0) code into 
copyleft-license based images in containers: 
https://opensource.com/article/18/1/containers-gpl-and-copyleft

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] Looking for a scriptable IMS client that will run in docker

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Looking for any guidance on the following. I need an IMS test client that can 
be dockerized, to drive the clearwater-docker deployment that I am putting into 
the Models project (I have clearwater-docker now running and will commit the 
build/run scripts soon, but need a test client to complete the test scenario 
that I will use for VNF lifecycle management tests in the Models, VES, and Auto 
projects).

Do you have or know of any open source clients that are:

  1.  will run under docker: I will run it in a k8s cluster were the IMS core 
runs, since I have not yet figured out how to expose the Bono service outside 
the cluster.
  2.  simple: I don't need a complex test client but if it's easy to get 
deployed, I call that simple.
 *   I am currently looking into how to build/use 
sipp, pjsua, but 
I'd really like to use a pre-built container for them; unfortunately I have not 
found one that works, or how to build it myself.
 *   I have checked out a really simple script 
(callSip.sh) but it doesn't appear to 
have the IMS layer.
 *   I do see a reference to clearwater-live-test in the functest VNF 
Dockerfile,
 but it's not clear what exactly in there is specific to clearwater-live-test, 
a dependency, or how to use it once it's built... by default I guess I could 
just hack this dockerfile and build my own to see.

Any help is appreciated. The docker image once created will likely be useful 
for other projects.

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] [Auto] "Auto Test Framework"

[SULLIVAN, BRYAN L (BRYAN L)]

I added some notes to the page at 
https://wiki.opnfv.org/display/AUTO/Auto+Test+Framework.
Hope this helps.

Thanks,
Bryan Sullivan | AT

From: Tina Tsou (OPNFV Confluence) [mailto:conflue...@opnfv.org]
Sent: Monday, January 22, 2018 6:51 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Subject: [OPNFV confluence] Tina Tsou mentioned you on "Auto Test Framework"

[cid:image001.png@01D39359.CA5F4510]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_-7Etinatsou-3Fsrc-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=uJCEIqbo1OOu6JoynJQzJKDabW4JXO27YZUefnxIeKw=>

Tina Tsou mentioned you on a page




[mention 
icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3Fsrc-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=k9Yy2iyUWhy6H3g3E3XUlW5nCcdg8FeHWAIw6uDT6BQ=>


Auto Test 
Framework<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3Fsrc-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=k9Yy2iyUWhy6H3g3E3XUlW5nCcdg8FeHWAIw6uDT6BQ=>



···


[View page 
Icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3Fsrc-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=k9Yy2iyUWhy6H3g3E3XUlW5nCcdg8FeHWAIw6uDT6BQ=>

View 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3Fsrc-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=k9Yy2iyUWhy6H3g3E3XUlW5nCcdg8FeHWAIw6uDT6BQ=>

•


[Add comment 
Icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3FshowComments-3Dtrue-26showCommentArea-3Dtrue-26src-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dcomment-23addcomment=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=VtBsqFY0nJ7mOVCjqy9wP8BFYF8VtnPOqPY1genXkmI=>

Add 
comment<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_AUTO_Auto-2BTest-2BFramework-3FshowComments-3Dtrue-26showCommentArea-3Dtrue-26src-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dcomment-23addcomment=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=WILYj0Gg76SkXbxv0mbvsDRTkZNr1Bk_02_VvOakzqA=VtBsqFY0nJ7mOVCjqy9wP8BFYF8VtnPOqPY1genXkmI=>

•

[Like 
Icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_plugins_likes_like.action-3FcontentId-3D13211036-26src-3Dmail-26src.mail.timestamp-3D1516632680224-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dlike-26jwt-3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ4c3JmOjJjOWU0OGQ1NTIxZGMwOTMwMTUyM2RiZGY4OGYwMDA0IiwicXNoIjoiZDY3MGRkMjEwYWFiYjAwZmU0OTRkYzFlZWNmZDY0NTZhOGRhZDkyZDU0MWZhZGRlZDA5MzVmYmE3ZGJkMzA1ZCIsImlzcyI6ImNvbmZsdWVuY2Vfbm90aWZpY2F0aW9uc0I5WVItMUFFRy0zRE1TLVBCNU4iLCJleHAiOjE1MTcyMzc0ODAsImlhdCI6MTUxNjYzMjY4MH0.AzDV96RaJpsu

Re: [opnfv-tech-discuss] New Adventures

[SULLIVAN, BRYAN L (BRYAN L)]

Dan,

Thanks for all your help and patience with us in OPNFV. You guys really set the 
bar for collaborative support, and I wish you the best in your new project.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dan Radez
Sent: Wednesday, January 17, 2018 11:56 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] New Adventures

With a new year I have been assigned to a new primary project.

I've enjoyed my time with OPNFV and want to say thank you to the
community and leadership for the past three years of working together.
It's been a pleasure to work along side of you all.

I'll be around less but not inaccessible. I'll be working to hand off my
tasks over the next couple weeks so they can be carried forward. Please
be in contact with me if I'm not already in discussion with you about
certain tasks.

Happy New Year!

Dan Radez
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=zd33VaS2QiwxmBbxmuQ4bLPOD85aUOZXIRqHkQfjSTk=PtkwCXBJNfRVuOUF1jRxVI32-jHaXPKIUAo64hd62Ow=
 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Auto Project Meeting 01/15/2018 - Auto - OPNFV Wiki

[SULLIVAN, BRYAN L (BRYAN L)]

No, I was not able to find the info to start the meeting. Sorry.

Thanks,
Bryan Sullivan | AT

From: Tina Tsou [mailto:tina.t...@arm.com]
Sent: Monday, January 15, 2018 8:06 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Auto Project Meeting 01/15/2018 - Auto - 
OPNFV Wiki

Dear Bryan et al,

“You need to use the login credential as listed at 
https://wiki.opnfv.org/display/meetings/Go-To-Meeting+info<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_meetings_Go-2DTo-2DMeeting-2Binfo=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=gKWWSv52mz3Xp-Ua3EpeMyH9vv7nMQk-dCM3JbB5AXs=3kvG3Juv_8prESL8QZ_4ZJ5ZyKjs8Pn0kZf6zjz_lxQ=>


This page is only accessible to PTLs.” from Ray.


Did the meeting happen?


Thank you,
Tina

On Jan 15, 2018, at 10:07 PM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
If someone has the credentials for the GTM bridge, please start the meeting and 
I will chair it. I can't find the current credentials.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tina Tsou
Sent: Friday, January 12, 2018 12:53 PM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] Auto Project Meeting 01/15/2018 - Auto - OPNFV 
Wiki

Dear all,

Auto weekly meeting agenda on Monday 6am PT 01/15 is posted.

https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D13210610=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=bW9YZfaBdUO1Xab4Ihvhuj7T4ljqVy8tYJAeTMteYG4=V9lrv8QwewQc9VOwPEoFJluHbN5wK-dfmGf1UK7brE4=

Bryan Sullivan from AT kindly agreed to chair the meeting, as I will be in an 
air plane at that time.

Have a good one. Happy weekend and MLK Day!


Thank you,
Tina
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<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=bW9YZfaBdUO1Xab4Ihvhuj7T4ljqVy8tYJAeTMteYG4=7cOGtRLiaXSPHc4i74zcNLSt_T135HxKxJh4FX66ATk=
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

Re: [opnfv-tech-discuss] Auto Project Meeting 01/15/2018 - Auto - OPNFV Wiki

[SULLIVAN, BRYAN L (BRYAN L)]

If someone has the credentials for the GTM bridge, please start the meeting and 
I will chair it. I can't find the current credentials.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tina Tsou
Sent: Friday, January 12, 2018 12:53 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Auto Project Meeting 01/15/2018 - Auto - OPNFV 
Wiki

Dear all,

Auto weekly meeting agenda on Monday 6am PT 01/15 is posted.

https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D13210610=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=bW9YZfaBdUO1Xab4Ihvhuj7T4ljqVy8tYJAeTMteYG4=V9lrv8QwewQc9VOwPEoFJluHbN5wK-dfmGf1UK7brE4=
 

Bryan Sullivan from AT kindly agreed to chair the meeting, as I will be in an 
air plane at that time.

Have a good one. Happy weekend and MLK Day!


Thank you,
Tina
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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=bW9YZfaBdUO1Xab4Ihvhuj7T4ljqVy8tYJAeTMteYG4=7cOGtRLiaXSPHc4i74zcNLSt_T135HxKxJh4FX66ATk=
 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Collecting questions for the Biterg Dashboard Training //RE: Issues/Needs/requirements for Biterg dashboard

[SULLIVAN, BRYAN L (BRYAN L)]

If it results in some gaps being better socialized and prioritized, it's a good 
idea to meet. E.g. I sent a request back in Nov and got no response... it was:

I’d like the ability to view/download the full set of data for a particular 
query, e.g. as you have from stackalytics (setting for “Show  entries”).

Thanks,
Bryan Sullivan | AT

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Thursday, January 11, 2018 6:50 AM
To: Yuyang (Gabriel) ; 
'opnfv-tech-discuss@lists.opnfv.org' ; 
test...@lists.opnfv.org
Cc: Alberto Pérez García-Plaza ; Alvaro del Castillo 
; Jesus M. Gonzalez-Barahona 
Subject: Re: [opnfv-tech-discuss] Collecting questions for the Biterg Dashboard 
Training //RE: Issues/Needs/requirements for Biterg dashboard

Hi,

Is the goal to get a better idea of how we can use the dashboard ("How
can I tell how many companies were active in a project between date 1
and date 2, excluding LF employees? What data sources are available for
query?" type questions), or is it to identify qualitative questions we
would like to answer with data ("Are we keeping participants over time?
Are there projects for which timely  patch review/acknowledgement of
issues is a challenge?") - understanding the goal of the tutorial would
help with identifying the right questions to ask.

Thanks,
Dave.

On 01/11/2018 04:40 AM, Yuyang (Gabriel) wrote:
> Hi Community,
> 
>  
> 
> As discussed, Biterg will arrange a training session of OPNFV statistics
> dashboard for the community in test working group meeting.
> 
> Basically, it will last about 1 hour as the usual first training
> covering the needs of navigating through panels, filtering the relevant
> results, sharing and exporting capabilities, etc.
> 
> Before this wonderful thing could happen, it would better if you look at
> the dashboard first and feedback questions regarding the operations,
> visualizations,  settings, statistics results and etc. as input for the
> training.
> 
> So that the training session could meet your needs in more efficient manner.
> 
>  
> 
> During last Testperf meeting, we have already discussed some needs and
> questions which are listed below. Please post your questions/needs behind.
> 
> 1.   How the commit number is calculated? What are involved in this
> metric? Including review?
> 
> 2.   When searching commit number for a specific person, there will
> be other persons involved in the results page. Are these persons for the
> calculation of reviews?
> 
> 3.   How should I search for the statistics results (commits, code
> line, patchsets, etc., ) of a project with aggregation results of
> companies, persons involved in this project
> 
> 4.   Needs for comprehensive introduction of the dashboard including
> every operations, filtering relevant information, where the dashboard
> retrieve datas, etc.?
> 
>  
> 
> Thanks,
> 
> Gabriel
> 
>  
> 
> *From:*Yuyang (Gabriel)
> *Sent:* Thursday, January 04, 2018 9:43 AM
> *To:* 'Alberto Pérez García-Plaza' 
> *Cc:* 'Alvaro del Castillo' ; 'Raymond Paik'
> ; 'mark.bei...@emc.com'
> ; 'Brandon Wick' ;
> 'jalaus...@suse.com' ; 'Rao, Sridhar'
> ; 'Jesus M. Gonzalez-Barahona'
> ; 'cedric.olliv...@orange.com'
> ; 'Brattain, Ross B'
> ; 'Cooper, Trevor' ;
> 'test...@lists.opnfv.org' ;
> 'opnfv-tech-discuss@lists.opnfv.org' 
> *Subject:* RE: Issues/Needs/requirements for Biterg dashboard
> 
>  
> 
> Hi Alberto,
> 
>  
> 
> Do not know if you are back from holiday yet. Just want to check-in for
> the proposal and training session.
> 
> Do you have some basic ideas now?
> 
>  
> 
> Thanks,
> 
> Gabriel
> 
>  
> 
> *From:*Yuyang (Gabriel)
> *Sent:* Thursday, December 14, 2017 11:33 AM
> *To:* 'Alberto Pérez García-Plaza'  >
> *Cc:* Alvaro del Castillo >;
> Raymond Paik  >; mark.bei...@emc.com
> ; Brandon Wick  >; jalaus...@suse.com
> ; Rao, Sridhar  >; Jesus M. Gonzalez-Barahona
> >; cedric.olliv...@orange.com
> ; 'Brattain, Ross B'
> >; Cooper,
> Trevor 

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[SULLIVAN, BRYAN L (BRYAN L)]

A couple of notes:

  1.  There should not be multiple endpoints with the same name defined in 
OpenStack. It's likely that one is a remainder from some earlier test. You may 
need to use "openstack endpoint delete ..." to remove one of the endpoints. 
Being related to keystone in this case, it's not something that was setup by 
this test script. It may also be some quirk in the way that MOS sets up the 
endpoints, that I have not encountered so far.
 *   Send me the result of "openstack endpoints list" and "openstack 
endpoint show " for each endpoint. I will see if 
I can mod the script to handle it, if it's not some error in the Fuel setup.
  2.  "OS_CACERT=/etc/ssl/certs/mcp_os_cacert" looks like some Fuel-specific 
cert file. I'm not sure what the effects related to that might be. You will 
probably need Fuel team support. It could indicate that for Fuel, there needs 
to be some additional file installed on the Tacker client... I have not 
encountered such an error on Apex or JOID.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 9:05 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Tina Tsou 
<tina.t...@arm.com>; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com>; Joe Kidder <joe.kid...@5thlayer.com>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan and Joe,

I could create an image for tacker on ARM Pod using tacker.sh. I had to change 
start.sh in /tmp/models/ to account for a change in "endpoint create" API 
syntax and also to  account for multiple endpoints with the same name in 
openstack. The Tacker container is now started but still encounters an error 
for "tacker vim-register" as below. I also encountered some auth failure for 
this command on last Friday (for auth_url: 
http://172.16.10.10:35357/v3<https://urldefense.proofpoint.com/v2/url?u=http-3A__172.16.10.10-3A35357_v3=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw=Dqvdqx1SEDw9iIydILAy9Xx3TKFem1c-xvfDGYMzvyc=>
 and OS_PROJECT_DOMAIN_ID=Default). I was also wondering about the non-existent 
file for OS_CACERT=/etc/ssl/certs/mcp_os_cacert being used in env. Complete 
session logs are attached.

main:203 (Wed Jan 10 03:39:11 UTC 2018) Register default VIM
SSL exception connecting to 
https://10.10.50.103:5000/v2.0:<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.10.50.103-3A5000_v2.0-3A=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw=PBLuYji938qnVhsaxYC7LmQvnjmWEE6ZesHAaX0kxOo=>
 None: Max retries exceeded with url: /v2.0 (Caused by None)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource return 
method(*args, **kwargs)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource   File 
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
 line 203, in register_vim
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource ks_client = 
self.authenticate_vim(vim_obj)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource   File 
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
 line 120, in authenticate_vim
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource keystone_version 
= self._validate_auth_url(auth_url)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource   File 
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
 line 158, in _validate_auth_url
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource raise 
nfvo.VimConnectionException(message=str(e))
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource 
VimConnectionException: SSL exception connecting to 
https://10.10.50.103:5000/v2.0:<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.10.50.103-3A5000_v2.0-3A=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw=PBLuYji938qnVhsaxYC7LmQvnjmWEE6ZesHAaX0kxOo=>
 None: Max retries exceeded with url: /v2.0 (Caused by None)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource
2018-01-10 03:39:38.036 INFO tacker.wsgi 
[req-69c4ec56-0faf-4de2-9f13-4d2c43176720 admin admin] 172.17.0.2 - - 
[10/Jan/2018 03:39:38] "POST /v1.0/vims.json HTTP/1.1" 500 417 1.900016

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 5:50 PM
To: Pramod Sudrik (Product Engineering Service) 
<pramod.sud...@wipro.com<mailto:pramod.sud...@wipro.com>>; Tina Tsou 
<tina.t...@arm.com<mailto:tina.t...@arm.com>>; Eric DMaye (Product Engineerin

Re: [opnfv-tech-discuss] Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

[SULLIVAN, BRYAN L (BRYAN L)]

Also - any particular reason this thread is not on the tech-discuss and TSC 
list? This goes to my point about transparency. We have to always remember we 
are an open community and any proposals that affect the community need to be 
openly shared on the lists. Especially ones that address organizational issues.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: SULLIVAN, BRYAN L (BRYAN L) 
Sent: Tuesday, January 09, 2018 7:12 PM
To: 'Christopher Donley (Chris)' <christopher.don...@huawei.com>; Dave Neary 
<dne...@redhat.com>; Christopher Price <christopher.pr...@ericsson.com>; 
m...@linuxfoundation.org; hkirk...@linuxfoundation.org; Lincoln Lavoie 
<lylav...@iol.unh.edu>; fzdar...@redhat.com; denglin...@chinamobile.com; 
fbroc...@cisco.com; ljlam...@vmware.com; Scott Nicholas 
<snicho...@linuxfoundation.org>; trevor.coo...@intel.com; Wenjing Chu 
<wenjing@huawei.com>; glenn.sei...@windriver.com; Tianhongbo 
<hongbo.tianhon...@huawei.com>; dmcbr...@linuxfoundation.org; 
fuq...@chinamobile.com; Raymond Paik <rp...@linuxfoundation.org>; 
t.nakam...@cablelabs.com; juha.oravai...@nokia.com; tapio.tallg...@nokia.com; 
morgan.richo...@orange.com; Tim Irnich <tim.irn...@ericsson.com>; 
feng.xiao...@zte.com.cn; Edward Abou Arrage (Eddie Arrage, Silicon Valley NFV 
Competency Center) <eddie.arr...@huawei.com>
Subject: RE: Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 
11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

Note also that any member of any LFN project is (or can easily become) a member 
of all LFN projects - at least there is no financial obligation beyond LFN 
membership. So if Amdocs wants to participate in OPNFV, nothing is stopping 
them.

Infra synergy is clearly an opportunity with the LFN but we should ensure that 
any discussion on that (beyond selling proactivity toward it) is kept at a 
cross-community basis in the technical community, and not at the Board or Board 
committee level. The TAC may provide a venue for finalizing cross-community 
infra strategy but all the detailed discussion on it (including the CVP) should 
be at the level of inter-TSC dialog. We can setup cross-community focus groups 
as needed to facilitate that cross-community dialog, but it needs to remain 
open to community-level participation, and transparent.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: Christopher Donley (Chris) [mailto:christopher.don...@huawei.com] 
Sent: Tuesday, January 09, 2018 11:08 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Dave Neary 
<dne...@redhat.com>; Christopher Price <christopher.pr...@ericsson.com>; 
m...@linuxfoundation.org; hkirk...@linuxfoundation.org; Lincoln Lavoie 
<lylav...@iol.unh.edu>; fzdar...@redhat.com; denglin...@chinamobile.com; 
fbroc...@cisco.com; ljlam...@vmware.com; Scott Nicholas 
<snicho...@linuxfoundation.org>; trevor.coo...@intel.com; Wenjing Chu 
<wenjing@huawei.com>; glenn.sei...@windriver.com; Tianhongbo 
<hongbo.tianhon...@huawei.com>; dmcbr...@linuxfoundation.org; 
fuq...@chinamobile.com; Raymond Paik <rp...@linuxfoundation.org>; 
t.nakam...@cablelabs.com; juha.oravai...@nokia.com; tapio.tallg...@nokia.com; 
morgan.richo...@orange.com; Tim Irnich <tim.irn...@ericsson.com>; 
feng.xiao...@zte.com.cn; Edward Abou Arrage (Eddie Arrage, Silicon Valley NFV 
Competency Center) <eddie.arr...@huawei.com>
Subject: RE: Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 
11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

In the short term, my understanding is the main impact of having C under the 
LFN Board is that it opens us up for further participation (for example, from 
Amdocs, who is an LFN member but not an OPNFV member) and allows greater 
transparency.  It also encourages more cross-project discussion (you're right 
that it will take some time to work out any such details - this would just 
provide a vehicle). For OVP, I think we proceed as planned as soon as we have 
the C rechartered (which has to happen, regardless of where we put it, since 
we were originally chartered as a Board committee).

Longer-term, we'll have to work out logistical issues with how we work inside 
LFN.  As you mention, questions of scope and passing criteria would go to the 
TSC through Dovetail and/or other OPNFV testing projects.  Likewise, I think 
tests/requirements generated by other communities should be governed by their 
TSC and branding/marketing handled in the respective communities, as well (the 
top-level LFN may need to weigh in if there's a gray area between llcs).  From 
the work we've done so far, I think a lot could be reused in a combined 
environment, including the governance document, committee structure, 
operational practices, Dovetail testing framework,  and back-end 
infrastructure.  

For OPNFV, I don't anticipate a change in scope 

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[SULLIVAN, BRYAN L (BRYAN L)]

Re ARM arch, good point. I don't have ARM hw and did not build this for ARM. 
You can try to build it using the script (tacker.sh) in the models build 
folder. If it works, you will need to push the container to docker hub and 
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it 
as a local container image.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Tina Tsou 
<tina.t...@arm.com>; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com>; Joe Kidder <joe.kid...@5thlayer.com>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows "standard_init_linux.go:178: exec user 
process caused "exec format error"". The "sudo docker image inspect 
blsaws/models-tacker" shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) 
<pramod.sud...@wipro.com<mailto:pramod.sud...@wipro.com>>; Tina Tsou 
<tina.t...@arm.com<mailto:tina.t...@arm.com>>; Eric DMaye (Product Engineering 
Service) <eric.dm...@wipro.com<mailto:eric.dm...@wipro.com>>; UKASICK, AIMEE L 
(AIMEE L) <aim...@research.att.com<mailto:aim...@research.att.com>>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates


** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_Hrc5FkwpOuR8oAokrxZxTcfkcUrwV51dApwrhglEbQU-3D-3Fd-3DRUYeklrPVwVzZE5eiA5cg3dR4EYyLEGe2F-5F8lh-5F2kzeC5uCLQj9r7PM10v7jkOTnDcm6ECMCqMeWqJ1RQrrGBFi51-2D-5FdJeN0nn1K01wo6IXxU1MwTcJzgrZKLKSe9-2Dw6m471SIQlS0JwMYX18HBJaKwUBKDT41N7aEaD-2D2GWzOiMGohQIfgWJ-5FZcMdpUPDzbW-2DpJYpJJdKt7RTLJWGQ-2DC9UjdF03zvxqPmDOh8t0ZcYy9EeQ-2DOIdhFQg-5FWFKMqz0-5FO54TYg4-2DVxZVycFnxKLnbx70svqhg-5FWcIGsN1Ih1Lg7LOrVFT4A5ehNSWBmx6kz9sQRCpJ-5F-2DhwYhARmU6kW8Rkqp3nlg5DfnJWsZ4jEajEVQX8qVMYAPbqC9odOgnO6gidOuoWuJhPW00lcHu-5FyBP7hviQNUjqLbwf7MxV8llE12XUZqqj3WFBgEJXS-26u-3Dhttps-253A-252F-252Fgit.opnfv.org-252Fmodels-252Ftree-252Fbuild-252Ftacker-252Fstart.sh=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s=uaesfvInkRWLGR6yrtUmC5rrHURq8TfHA6viCcH98KA=>
  2.  start.sh already discovers the region name via the API so I'm not sure 
what's going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' 
<pramod.sud...@wipro.com<mailto:pramod.sud...@wipro.com>>; Tina Tsou 
<tina.t...@arm.com<mailto:tina.t...@arm.com>>; 
eric.dm...@wipro.com<mailto:eric.dm...@wipro.com>; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com<mailto:aim...@research.att.com>>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_SVYSmBwMT4BKSWX8bLMlbbG9P18CUTaQ-5FXNbDME-2DSNA-3D-3Fd-3DRUYeklrPVwVzZE5eiA5cg3dR4EYyLEGe2F-5F8lh-5F2kzeC5uCLQj9r7PM10v7jkOTnDcm6ECMCqMeWqJ1RQrrGBFi51-2D-5FdJeN0nn1K01wo6IXxU1MwTcJzgrZKLKSe9-2Dw6m471SIQlS0JwMYX18HBJaKwUBKDT41N7aEaD-2D2GWzOiMGohQIfgWJ-5FZcMdpUPDzbW-2DpJYpJJdKt7RTLJWGQ-2DC9UjdF03zvxqPmDOh8t0ZcYy9EeQ-2DOIdhFQg-5FWFKMqz0-5FO54TYg4-2DVxZVycFnxKLnbx70svqhg-5FWcIGsN1Ih1Lg7LOrVFT4A5ehNSWBmx6kz9

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[SULLIVAN, BRYAN L (BRYAN L)]

Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I'm not sure 
what's going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' <pramod.sud...@wipro.com>; Tina Tsou 
<tina.t...@arm.com>; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55<https://git.opnfv.org/models/tree/build/tacker/start.sh%20line%2055>.
  3.  Note that you can dump the tacker container log with "sudo docker logs 
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you 
will likely see the issue that led to the endpoint not being created. If the 
container is running, you can use "sudo docker exec -it /bin/bash" to poke 
around in the container, e.g. to debug using the openstack CLI etc from within 
the container.
  4.  I have no idea where "fatal: /home/ubuntu/auto/keystonercv3: 
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks 
like something Fuel is complaining about.
  5.  "internal endpoint for nfv-orchestration service in RegionOne region not 
found" is a bug, but one due to a persistent problem with OPNFV ... in that the 
different distros use inconsistent naming for key common attributes such as the 
region name. In Apex, this is "regionOne" and the case difference matters. But 
I will try to find a way for the test to be more intelligent, i.e. discover the 
actual value and use it. I've done this in the past, I just need to recall 
where and how.

For reference, For Apex the whole test process including the following is 
posted at https://etherpad.opnfv.org/p/bryan-models:

  *   Test setup
  *   Tacker container logs
  *   Test start
  *   Output of CLI calls for openstack user, endpoint, and service
  *   Test stop
  *   Test clean
  *   Output of CLI calls for openstack user, endpoint, and service (verifying 
cleanup)

Note you will still see some reports of "Neutron CLI is deprecated" Since 
it's taking time to convert all the CLI calls to use the openstack client. But 
they work.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com<mailto:pramod.sud...@wipro.com> 
[mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 12:43 PM
To: SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>; Tina 
Tsou <tina.t...@arm.com<mailto:tina.t...@arm.com>>; 
eric.dm...@wipro.com<mailto:eric.dm...@wipro.com>; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com<mailto:aim...@research.att.com>>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Thanks Bryan for the changes.

I tried the latest Models Project in ARM Pod (with OPNFV) and found that the 
setup for vHello_Tacker.sh indicates that it succeeded, but the session logs 
(as attached) show some issues. I did not see the logic to create an endpoint 
nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution 
fails to find this endpoint during "tacker vnf-create" processing. Is this 
endpoint not needed anymore with this change ? The logs are given below.
The docker status also shows as exited.
(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -a
CONTAINER IDIMAGE COMMAND  
CREATED STATUS PORTS   NAMES
982486b7290cblsaws/models-tacker:latest   "/bin/bash /opt/ta..."   
About an hour ago   Exited (1) About an hour ago   tacker

~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3
setup:165 (Tue Jan  9 18:28:11 UTC 2018) run tacker-setup.sh
...snip...
create_container:99 (Tue Jan  9 18:28:23 UTC 2018) Start ta

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[SULLIVAN, BRYAN L (BRYAN L)]

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55<https://git.opnfv.org/models/tree/build/tacker/start.sh%20line%2055>.
  3.  Note that you can dump the tacker container log with "sudo docker logs 
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you 
will likely see the issue that led to the endpoint not being created. If the 
container is running, you can use "sudo docker exec -it /bin/bash" to poke 
around in the container, e.g. to debug using the openstack CLI etc from within 
the container.
  4.  I have no idea where "fatal: /home/ubuntu/auto/keystonercv3: 
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks 
like something Fuel is complaining about.
  5.  "internal endpoint for nfv-orchestration service in RegionOne region not 
found" is a bug, but one due to a persistent problem with OPNFV ... in that the 
different distros use inconsistent naming for key common attributes such as the 
region name. In Apex, this is "regionOne" and the case difference matters. But 
I will try to find a way for the test to be more intelligent, i.e. discover the 
actual value and use it. I've done this in the past, I just need to recall 
where and how.

For reference, For Apex the whole test process including the following is 
posted at https://etherpad.opnfv.org/p/bryan-models:

  *   Test setup
  *   Tacker container logs
  *   Test start
  *   Output of CLI calls for openstack user, endpoint, and service
  *   Test stop
  *   Test clean
  *   Output of CLI calls for openstack user, endpoint, and service (verifying 
cleanup)

Note you will still see some reports of "Neutron CLI is deprecated" Since 
it's taking time to convert all the CLI calls to use the openstack client. But 
they work.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 12:43 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Tina Tsou 
<tina.t...@arm.com>; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
<aim...@research.att.com>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Thanks Bryan for the changes.

I tried the latest Models Project in ARM Pod (with OPNFV) and found that the 
setup for vHello_Tacker.sh indicates that it succeeded, but the session logs 
(as attached) show some issues. I did not see the logic to create an endpoint 
nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution 
fails to find this endpoint during "tacker vnf-create" processing. Is this 
endpoint not needed anymore with this change ? The logs are given below.
The docker status also shows as exited.
(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -a
CONTAINER IDIMAGE COMMAND  
CREATED STATUS PORTS   NAMES
982486b7290cblsaws/models-tacker:latest   "/bin/bash /opt/ta..."   
About an hour ago   Exited (1) About an hour ago   tacker

~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3
setup:165 (Tue Jan  9 18:28:11 UTC 2018) run tacker-setup.sh
...snip...
create_container:99 (Tue Jan  9 18:28:23 UTC 2018) Start tacker container with 
image blsaws/models-tacker:latest
Missing parameter(s):
Set a username with --os-username, OS_USERNAME, or auth.username
Set an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_url
Set a scope, such as a project or domain, set a project scope with 
--os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope 
with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name
982486b7290c9338979d216dbb8b285431f275028754e75605dbef160501a21e
pass:40 (Tue Jan  9 18:28:26 UTC 2018) Hooray!
...snip...
Create virtualenv
New python executable in /home/ubuntu/venv/bin/python
..snip...
fatal: /home/ubuntu/auto/keystonercv3: '/home/ubuntu/auto/keystonercv3' is 
outside repository
...snip..
setup:232 (Tue Jan  9 18:32:25 UTC 2018) Add router interface for vnf_private 
network
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
Added interface f2a6a8b3-bb70-4587-958b-3903629973b9 to router 
vnf_private_router.
pass:100 (Tue Jan  9 18:32:38 

[opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[SULLIVAN, BRYAN L (BRYAN L)]

Pramod,

Bringing this offline discussion to the list...

The Models vHello_Tacker test is now updated/merged and working for Euphrates 
(verified for Apex virtual install). There were a variety of API/CLI and other 
changes in OpenStack Ocata, and I took the opportunity to refactor the test. It 
now uses a docker container for Tacker, that is pre-built and downloaded from 
docker hub (https://hub.docker.com/r/blsaws/models-tacker/). The test overall 
runs much faster. The comments at the start of the script describe the updated 
process. The main difference is that the OpenStack commands require activation 
of a virtual env that is installed in the setup step.

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] Licenses for OPNFV docker images

[SULLIVAN, BRYAN L (BRYAN L)]

I have a proposed text, included in the containers I have published at 
https://hub.docker.com/u/blsaws/. Here is an example for 
https://hub.docker.com/r/blsaws/ves-agent/
This container provides the "VES Agent" function of the OPNFV VNF Event Stream 
(VES) project. The container is built via the "ves-agent.sh" script in the VES 
repo folder https://github.com/opnfv/ves/tree/master/build. For more 
information, see https://wiki.opnfv.org/display/ves/VES+Home.
The container includes code developed under the OPNFV project and distributed 
under the license below (# LICENSE #), and other code installed as part of the 
container build process, separately licensed per the source of that code.
LICENSE
Copyright 2017-2018 AT Intellectual Property, Inc
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0


Thanks,
Bryan Sullivan | AT

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Tuesday, January 09, 2018 8:55 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Licenses for OPNFV docker images

Hi Bryan,

So you're looking for a license text for OPNFV users to use the contents in 
OPNFV docker hub?  Let me know if I'm mistaken.  I can check with the legal 
team on this...

Thanks,

Ray

On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi all,

Should we be adding license descriptions to the 
https://hub.docker.com/u/opnfv<https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_opnfv=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=Vhsg_dHEzZCJSAlC9Rqj7XNCdUiysW9SBM-_Bwp4S4M=>
 images? I have seen a recommendation that the license be included in the repo 
description field. Just wondering, since otherwise per the docker hub TOS 
(https://www.docker.com/docker-terms-service<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.docker.com_docker-2Dterms-2Dservice=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=YRdES2lVRMwnqTDaC93eWXqDR-Z-VTorQmNkEirqyVM=>):

6.4 The Service allows you to specify or upload the terms under which other 
users of the Service will be licensed to use your User Content. If you do not 
specify or upload such license terms with respect to any User Content, you 
hereby grant to any other users of the Service, a non-exclusive license to 
access, download, use, modify or otherwise exploit such part of your User 
Content for any personal or business purposes.

Thanks,
Bryan Sullivan | AT


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=w8PKfRUudxG9-IcIX1J-Z0822Ry3Te8yDvoqQAYZyX0=>

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

[opnfv-tech-discuss] Licenses for OPNFV docker images

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Should we be adding license descriptions to the https://hub.docker.com/u/opnfv 
images? I have seen a recommendation that the license be included in the repo 
description field. Just wondering, since otherwise per the docker hub TOS 
(https://www.docker.com/docker-terms-service):

6.4 The Service allows you to specify or upload the terms under which other 
users of the Service will be licensed to use your User Content. If you do not 
specify or upload such license terms with respect to any User Content, you 
hereby grant to any other users of the Service, a non-exclusive license to 
access, download, use, modify or otherwise exploit such part of your User 
Content for any personal or business purposes.

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] [barometer] Demo of VES-Barometer deployment and takeaways

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

As noted on the Barometer call here is a quick overview of the status of 
VES-Barometer integration, and some takeaways, in advance of a 30-min demo on 
some upcoming Barometer call. For reference, see the current VES deployment 
approach for OPFNV testing and ONAP integration at the VES home 
page, and how the scripts below 
are used in a complete stack deployment ala 
demo_deploy.sh
 for the models 
kubernetes stack.

First as you can see in 
ves-setup.sh I'm 
now using the Barometer container out of the box. Thanks a lot for implementing 
this... it's really simplified the VES deployment.

In ves-setup.sh 
you can also see that I now deploy zookeeper as its own container using the 
default zookeeper image. For kafka, I had to create a container image that 
included some environment parameters that are needed, per the code snippet 
below:
log "setup kafka server"
source ~/k8s_env.sh
sudo docker run -it -d -p 2181:2181 --name zookeeper zookeeper
sudo docker run -it -d -p 9092:9092 --name ves-kafka \
  -e zookeeper_host=$k8s_master_host \
  -e zookeeper=$k8s_master \
  -e kafka_hostname=$ves_kafka_hostname \
  blsaws/ves-kafka:latest

It would be good if the build process for this container (see 
ves-kafka.sh) 
could be picked up by Barometer, and an "official" OPNFV kafka image generated, 
that VES could then use. This would help reduce the ants that anteater 
complains about (I assume you know what anteater is...).

The ves-agent.sh 
and 
ves-collector.sh
 build the containers that run those components. The ves-agent build script 
could migrate to Barometer since it's based upon the ves_app.py code, but 
that's an option. At the least we can review the dockerfiles/scripts to see 
what any Barometer docs or code can incorporate.

Right now those containers are simply started using docker in a shell script 
over SSH, on the node that the user (of 
demo_deploy.sh) 
chooses as the "master" node. I plan to evolve that soon to a more robust 
approach including:

  *   Deploying/managing the containers using kubernetes, with k8s chart labels 
for service placement and restart policies for resiliency
  *   Assess other ways to enhance the resiliency/HA nature of the services, 
e.g. running multiple k8s pods for a service; this will include assessing how 
well k8s restores a service deployed as a single pod, and how that affects the 
reliability of the VES framework.
  *   Deploy the containers onto k8s clusters (managing the local cloud/NFV 
platform) using Helm and/or Cloudify, with the goal of aligning with the ONAP 
OOM project in the current/next release.

I'd also like to have a deep-dive on the VES schema and how the ves_app.py code 
maps the collectd events. I'll try to collect some specific issues re that in 
advance of some later session, and get Alok's team to support the discussion.

Other goals for this year include aligning the ONAP VES code with OPNFV, 
driving VES/DCAE/CLAMP integration in OPNFV thru the Auto project, and 
leveraging the above for development of VES-compliance tests for NFV platforms 
and VNFs, as well as within the broader goals of Auto for closed-loop control 
tests.

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] [barometer] weekly meeting

[SULLIVAN, BRYAN L (BRYAN L)]

Sure. Today might be tricky though, I will be away during the Barometer call.
I’m using Prometheus since it’s in scope for control plane monitoring as part 
of the OpenStack Helm based platform we are building as the next version of the 
AIC: see 
https://www.openstack.org/assets/edge/slides/Kandan-AT-T-Edge-Talk-Opendev.pdf

I’m not using it in any specific way yet, except to get familiar with it as 
part of the toolchain. We may want to work on Prometheus as a VES data source 
though at some point.

I’m using InfluxDB as a simple and low-overhead way to build a local TSDB for 
VES data, so we can start writing tests that analyze VNF/platform aspects and 
execute closed-loop control ala ONAP DCAE. It may fit better than Hadoop (e.g. 
in weight at least) for a TSDB local to an edge cloud, for local closed-loop 
control.

BTW I am now using the Barometer container and really appreciate not having to 
build it. It also fits with the goal that every component in the VES framework 
that can be containerized, will be, and will be managed through kubernetes as 
services that are assigned to nodes through labels, and managed by kubernetes 
for resiliency. This is all a work in progress.

Thanks,
Bryan Sullivan | AT

From: Aaron Smith [mailto:aasm...@redhat.com]
Sent: Tuesday, December 12, 2017 5:28 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [barometer] weekly meeting

Bryan,
 Could you elaborate on your use of Prometheus + InfluxDB?  Do you use InfluxDB 
as long-term storage of Prometheus data?
We would love to see a demo during the Barometer meeting when it's running.

Thx,
  Aaron

On Mon, Nov 27, 2017 at 10:14 AM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes 
stack<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_models_tree_master_tools=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=RdGkOtIc9WO_eOK3fErP3H538ybynBMTBgTOPxFNTaI=efA7IVXizf1rYUwRZd4MlUPjax98-AlVjcqFpeGK5q8=>.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/<https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_blsaws_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=RdGkOtIc9WO_eOK3fErP3H538ybynBMTBgTOPxFNTaI=q2ZjsxL0k-8bv4RDyjlztcbjyJjf6_U-lg5-dYFs6hk=>

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_ves_tree_master_build=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=RdGkOtIc9WO_eOK3fErP3H538ybynBMTBgTOPxFNTaI=CEBR5cdLpGzj3YQ_9tbfu0i5K3vY64T3LAn-uXISUe4=>

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

--

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat

<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=KGNFH2ulYHexpHiZBjrMVlElF-irXzw2lkDJENvu6vE=zj6bdbP1GMP77eq5qEdnycizsMUhuBpf3SMTte6T6B4=>

314 Littleton Rd, Westford, MA 
01886<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D314-2BLittleton-2BRd-2C-2BWestford-2C-2BMA-2B01886-26entry-3Dgmail-26source-3Dg=DwMFaQ=LFY

Re: [opnfv-tech-discuss] Service VM

[SULLIVAN, BRYAN L (BRYAN L)]

Gokul,

I created a JIRA ticket for this: https://jira.opnfv.org/browse/INFRA-197
I think Infra team will help us route it where it can be handled.
Infra team - if we need to do something else please let us know.

The VES project requests a (v)pod with the following minimum configuration:

  *   3 nodes, either Centos 7 or Ubuntu Xenial
  *   64 GB RAM minimum (128 preferred) per server
We will use them to further develop the Barometer VES plugin code (ves_app.py) 
and test integration with the VES Collector etc as developed in OPNFV and ONAP.
We will install the OpenStack or other cloud control plane as needed, so we 
only need access to the nodes/VMs.


Thanks,
Bryan Sullivan | AT

From: SINGARAJU, GOKUL [mailto:gs2...@att.com]
Sent: Friday, December 01, 2017 8:34 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; GUPTA, ALOK 
<ag1...@att.com>
Subject: Service VM

Hi,
   Need a Single node VM to work on Barometer and VES Project.
   What is the process to obtain one.
Thanks
Gokul

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

Re: [opnfv-tech-discuss] [barometer] weekly meeting

[SULLIVAN, BRYAN L (BRYAN L)]

If it helps, I have some logs from the:

  *   VES Agent (ves_app.log)
  *   VES Collector (monitor.log and collector.log)
  *   collectd-kafka traffic (stdout from the test kafka consumer)

These could be used to correlate what is sent when, and trace back the lineage 
of values and timestamps as suggested. But I recommend first we get the 
Barometer team to describe how that lineage is intended to work – and we can 
then verify it.

Thanks,
Bryan Sullivan | AT

From: MORTON, ALFRED C (AL)
Sent: Monday, November 27, 2017 6:19 PM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Aaron Smith 
<aasm...@redhat.com>; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [barometer] weekly meeting

Hi Aaron, Bryan, and all,

I’d like to add a brief discussion to the agenda tomorrow,
related to the thread that many project members participated
in last week, the subject was:
“ves_app.py exception when collecting from multiple collectd clients”

In short, I’m interested in the steps that measured results
follow to arrive at any VIM, and what information accompanies
the results.

One of our barometer wiki pages gives the collectd 101,
https://wiki.opnfv.org/display/fastpath/Collectd+101
gives the contents of a value list for collectd statistics.
The most important ones to this discussion are:
•  Values
•  Value length: the number of values in the data set.
•  Time: timestamp at which the value was collected.
•  Interval: interval at which to expect a new value.
•  Host: used to identify the host.

As I have mentioned before, TST008 requires that
measured values be accompanied by the time they are measured.
I now wonder if the collectd Time: when the value was “collected”
is close enough to the actual time when the hypervisor reads
the meter or gauge and passes the value to libvirtd API & virt plugin
to ignore the difference (time error). It could simplify
life on earth if the error is small.

Please give this a little thought before we meet, thanks!
Al


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L (BRYAN L)
Sent: Monday, November 27, 2017 10:15 AM
To: Aaron Smith; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [barometer] weekly meeting

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes 
stack<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_models_tree_master_tools=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=OfsSu8kTIltVyD1oL72cBw=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20=VFHdVR23prpLP3WM8l6ddGc2dOP8lgNoudF8ZV61kF8=>.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/<https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_blsaws_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=OfsSu8kTIltVyD1oL72cBw=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20=VIjaf26ZIEFu4jxa8RH4UynLZvr2yv5ZSSUkZ_dngEE=>

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_ves_tree_master_build=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=OfsSu8kTIltVyD1oL72cBw=9PvLnmbuYxVL8K1S_AO83wjzC7fo0AZBGYdEs3zRm20=saUZH-BOBsoF5Fx4aFz8dao1WQzO2Y4rehaVMBvbsSs=>

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for to

Re: [opnfv-tech-discuss] [barometer] weekly meeting

[SULLIVAN, BRYAN L (BRYAN L)]

FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes stack.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

--

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat



314 Littleton Rd, Westford, MA 01886

aasm...@redhat.comM: 
617.877.4814
[https://www.redhat.com/files/brand/email/sig-redhat.png]


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

Re: [opnfv-tech-discuss] [barometer] ves_app.py exception when collecting from multiple collectd clients

[SULLIVAN, BRYAN L (BRYAN L)]

Thanks for the additional info. The detailed questions I had were on how to 
build the domain (VM) XML configuration file outside of an OpenStack 
environment. While VES will support OpenStack environments and be tested with 
them, for non-OpenStack environments (e.g. Kubernetes) is there any dependence 
on the virt plugin for collectd? Our main focus going forward (beyond 
supporting our current OpenStack-based platform, AIC) is on cloud-native stacks 
that do not include OpenStack or deploy apps/VNFs in VMs.

For OpenStack environments, the info you provided helps, but I will need to 
test it. The issue I was having was that though I followed all the steps except 
for creating the domain (VM) XML configuration file, the virt plugin was not 
installed and thus collectd failed to find it and exited. If you're saying that 
just because OpenStack compute code will have been installed prior (for 
OpenStack hosts), the virt plugin will be installed (or the "make install" 
process for collectd will find the present OpenStack domain (VM) XML 
configuration files, and complete the job of installing the virt plugin...), 
then OK and I will verify that.

Thanks,
Bryan Sullivan | AT

From: Mytnyk, VolodymyrX [mailto:volodymyrx.myt...@intel.com]
Sent: Tuesday, November 21, 2017 7:22 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Tahhan, 
Maryam <maryam.tah...@intel.com>
Cc: Mcmahon, Tony B <tony.b.mcma...@intel.com>; Power, Damien 
<damien.po...@intel.com>; GUPTA, ALOK <ag1...@att.com>; SINGARAJU, GOKUL 
<gs2...@att.com>; 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

Hi Bryan,

To make collectd virt plugin work on a host, the libvirt library needs to be 
installed on the system/host (virt 
plugin<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.opnfv.org_en_latest_submodules_barometer_docs_release_userguide_feature.userguide.html-23virt-2Dplugin=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=3QaIPLABF1J5bS7ZdYVUJE8lzTFK6CtloDvgmhuKd84=2HmUI80GTO-P-98xNvo_veQ3wEk3m2oCFz4TLHkg7bY=>,
 ` Dependencies: `). If the collectd is running in the OpenStack environment 
(e.g. on compute), the dependencies for libvirtd should be installed 
automatically during OpenStack installation. It means no other dependencies 
needs to be installed for collectd virt plugin. Only install 
collectd<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.opnfv.org_en_latest_submodules_barometer_docs_release_userguide_collectd.ves.userguide.html-23install-2Dcollectd=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=3QaIPLABF1J5bS7ZdYVUJE8lzTFK6CtloDvgmhuKd84=Vcp88USCgBSGIMg5tP3gBe0OehWksYdDNv_E-_3P9G0=>
 steps needs to be performed to install collectd on a host for the VES 
purposes. The following commands can be used on a host to make sure that 
libvirt dependencies have been installed by OpenStack:
$ sudo dpkg -l | grep virt
...
ii  libvirt-dev:amd64  2.5.0-3ubuntu5.5~cloud0  
  amd64development files for the libvirt library
...
If the collectd is running in non OpenStack environment, the libvirt should be 
installed manually (via `sudo apt-get install libvirt-dev`) or from sources 
(see virt 
plugin<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.opnfv.org_en_latest_submodules_barometer_docs_release_userguide_feature.userguide.html-23virt-2Dplugin=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=3QaIPLABF1J5bS7ZdYVUJE8lzTFK6CtloDvgmhuKd84=2HmUI80GTO-P-98xNvo_veQ3wEk3m2oCFz4TLHkg7bY=>
 `Install libvirt` & ` install the dependencies: ` for more details how to 
build from sources). It depends on what features/extended statistics you want 
to receive via libvirt (see Extended statistics 
requirements<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.opnfv.org_en_latest_submodules_barometer_docs_release_userguide_feature.userguide.html-23id9=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=3QaIPLABF1J5bS7ZdYVUJE8lzTFK6CtloDvgmhuKd84=NRfkRsR7WyxlPs9ysUo4zFJfMb0u7Wf041eSEMAA4XA=>
 section for more details). The extended statistics (if libvirt version 
supports them) are mapped  into `additionMeasurenmets` filed of the VES 
message. From the VES app perspective, it shouldn't  be difference what 
statistics are exposed by libvirt & virt plugin (e.g. what version of libvirt 
is installed and used).

Regarding the `virsh tool`. This tool is used to create and manage VM manually 
via libvirt and CLI. As I understand, you are running collectd in OpenStack 
environment, so you don't need to use this method. The OpenStack environment 
should be used instead to create/manage VMs (OpenStack uses libvirt to manage 
VMs).

If you receive collectd err

Re: [opnfv-tech-discuss] [barometer] VES Heartbeats

[SULLIVAN, BRYAN L (BRYAN L)]

OK, here are some thoughts then to consider.

  *   Collectd (or other monitoring frontend) on each host will probably be 
sending measurements at least every minute or more often (VNFs may have longer 
cycles but for bare metal hosts I imagine we would want measurements at least 
every minute). Those would make an easy trigger for proxied host heartbeats 
from the VES Agent.
  *   No report from collectd means the host may be down.
  *   To avoid collectd itself from causing a false positive heartbeat failure, 
it should be run in a container that is managed by a framework like Kubernetes, 
so that if/when it fails it is automatically respawned on the same host.
  *   For heartbeats from VNFs, this should be integrated into the VNF code, 
such that if the VNF is dead or a zombie, the heartbeat fails. It should not be 
issued by a separate process on the  VNF host (VM or container) since that may 
result in a false negative.

If that makes sense maybe Gokul can work with Intel to update the ves_app.py 
Agent to proxy the heartbeats for all the hosts it gets reports from. I'll work 
on options for deploying the collectd containers using e.g. Kubernetes+Helm and 
creating a demo/dummy VNF that issues heartbeats via the ONAP Agent libraries 
(Gokul is welcome to help there as well...).

Thanks,
Bryan Sullivan | AT

From: GUPTA, ALOK
Sent: Monday, November 20, 2017 6:19 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [barometer] VES Heartbeats

Bryan:

Interesting question. It is similar to getting VNF events from an EMS or OAM 
vm. The reason and rationale for heartbeat event was to avoid sending 
pings/queries to the devices but having DCAE analytics capable of analyzing 
heartbeat and metrics to determine health status of the device (compared to 
currently done via heath-check query to VNF). We had discussed earlier if the 
events coming in can assume if VNF is ok, instead of heartbeat and team felt 
otherwise. Fault and syslog event frequency can vary (you may not receive event 
for hours. If VNF is running smoothly). With Metrics the interval can be long 
(5  mins...15mins)...thus a need for Heartbeat event.
The heartbeat is not from agent but for devices for which data is being send. 
In some cases the entity forwarding the data could determine the health and it 
can create and send a HB event. You said this very well in your email for the 
infrastructure scenario, we may need to proxy the heartbeats for hosts not 
running the agent.

Hope this helps.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com<mailto:ag1...@att.com>

From: SULLIVAN, BRYAN L
Sent: Monday, November 20, 2017 8:55 AM
To: GUPTA, ALOK <ag1...@att.com<mailto:ag1...@att.com>>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [barometer] VES Heartbeats

Alok,

Thinking about the shared Agent (ves_app.py from Barometer) design, in which we 
don't need an agent running on each node, but can use a single agent running on 
the local cloud which aggregates VES events from the Kafka bus, it brings up 
the question of how heartbeats are supposed to work (and what we use them for) 
in the VES design.

Beyond the VNF (presumably by integration of the ONAP VES library into the 
VNF), have you been assuming that the heartbeats represent the health of:

  *   The VES agent
  *   A host (real or virtual, whether running a VES agent or not) from which 
VES events are received

If the latter, we need to consider how the agent can proxy the heartbeats for 
hosts on which there is no agent running, e.g. the agent can keep a host-based 
flag that is set whenever a collectd event is picked up on the Kafka bus during 
the heartbeat period, and send a Heartbeat report for each host at the end of 
the period. But really in that case couldn't DCAE derive that information 
anyway from what it had received? So it calls into question the purpose of the 
heartbeat beyond the VNF itself (the obvious use case) - I just need to clarify 
it.

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] [barometer] ves_app.py exception when collecting from multiple collectd clients

[SULLIVAN, BRYAN L (BRYAN L)]

OK, trying to use the node.yaml and collectd virt plugin as noted on the wiki, 
still having errors with collectd (collectd fails as the virt plugin is not 
found). I think this is probably due to some of the steps in the guide not 
being completed. Honestly 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/feature.userguide.html#virt-plugin
 could be a bit clearer... it says e.g. "Create domain (VM) XML configuration 
file. For more information on domain XML format and examples, please see: 
https://libvirt.org/formatdomain.html; but that's a reference to a long guide 
to libvirt XML files... something more specific (e.g. a working example and 
more clarifications as below) would be really helpful to people that aren't 
libvirt SMEs, e.g.

  *   What's typical or workable for libvirt as used by OpenStack
  *   What should be the "DOMAIN_NAME" in "virsh start DOMAIN_NAME" (maybe the 
name matters?)
  *   Re "Check list of available Performance monitoring events and their 
settings:" what would we be checking for and what settings are important to 
check? E.g. which events map to measurements in the VES data model or are 
mappable via the node.yaml file by the ves_app (presumably we should not worry 
for now about those that can't be mapped).
  *   Re "Clone and install the collectd virt plugin:" is the cloning and 
build/install of the collectd repo at this point redundant with the earlier 
build (see 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/collectd.ves.userguide.html#install-collectd
 ... at that point the goal was to "Build collectd with Kafka support" - but do 
we have to build twice to get the virt plugin setup?)

Thanks,
Bryan Sullivan | AT

From: Mytnyk, VolodymyrX [mailto:volodymyrx.myt...@intel.com]
Sent: Monday, November 20, 2017 9:05 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>; Tahhan, 
Maryam <maryam.tah...@intel.com>
Cc: Mcmahon, Tony B <tony.b.mcma...@intel.com>; Power, Damien 
<damien.po...@intel.com>; GUPTA, ALOK <ag1...@att.com>; SINGARAJU, GOKUL 
<gs2...@att.com>; 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

Hi Bryan,

See my  comments inline.

* "How do I (as noted in the patch) get ves_app to generate 
messages for the guest, hypervisor, and node separately? Do I need to run 3 
instances of the ves_app?"
You need to run only one instance of the ves_app (patched one) 
somewhere where ves_app will have an access to the Kafka server (e.g. on the 
host).

* "Should I use the yaml files in the repo or the one (merged) that 
you provided Friday? I assume I should use the ones in the repo."
You have to use new node.yaml from gerrit review (provided on 
Friday, 
https://gerrit.opnfv.org/gerrit/#/c/47427/1/3rd_party/collectd-ves-app/ves_app/node.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_-23_c_47427_1_3rd-5Fparty_collectd-2Dves-2Dapp_ves-5Fapp_node.yaml=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=tAQbjXoKuI6-8IbLIJ1IFnPHe8rikjRZnuL2wqaDfmY=xDaI7ASpSIt1nc0vNxBrztdn8jTSJ4aq3FoVAlfb9-Y=>
 )


  *   Also, you have to use collectd configuration files provided on Friday.
 *   For collectd that is running on each guest machine VM, you have to use 
collectd-guest.conf (please make sure IP address of Kafka server is correct)
 *   For collectd that is running on the host machine, you have to use 
collectd-host.conf (please make sure IP address of Kafka server is correct)
 *   `csv` and `logfile` plugins are enabled in the configuration files and 
used for debug purposes.

The usage example of the `node.yaml` configuration:

[cid:image004.png@01D36215.E28DDEA0]

Thanks and Regards,
Volodymyr

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Monday, November 20, 2017 6:33 PM
To: Mytnyk, VolodymyrX 
<volodymyrx.myt...@intel.com<mailto:volodymyrx.myt...@intel.com>>; Tahhan, 
Maryam <maryam.tah...@intel.com<mailto:maryam.tah...@intel.com>>
Cc: Mcmahon, Tony B 
<tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>>; Power, Damien 
<damien.po...@intel.com<mailto:damien.po...@intel.com>>; GUPTA, ALOK 
<ag1...@att.com<mailto:ag1...@att.com>>; SINGARAJU, GOKUL 
<gs2...@att.com<mailto:gs2...@att.com>>; 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

Bringing it back to the list, and cc'ing Alok and Gokul as some of this relates 

Re: [opnfv-tech-discuss] [barometer] ves_app.py exception when collecting from multiple collectd clients

[SULLIVAN, BRYAN L (BRYAN L)]

Bringing it back to the list, and cc'ing Alok and Gokul as some of this relates 
to the overall VES design.

OK, ready to work on testing your patch. I can locally edit the ves-setup 
script to pull the patch when I clone barometer in the VES Agent (ves_app) 
container.

Quick questions first though:

  *   How do I (as noted in the patch) get ves_app to generate messages for the 
guest, hypervisor, and node separately? Do I need to run 3 instances of the 
ves_app?
  *   Should I use the yaml files in the repo or the one (merged) that you 
provided Friday? I assume I should use the ones in the repo.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Monday, November 20, 2017 5:36 AM
To: 'Mytnyk, VolodymyrX' <volodymyrx.myt...@intel.com>; Tahhan, Maryam 
<maryam.tah...@intel.com>
Cc: Mcmahon, Tony B <tony.b.mcma...@intel.com>; Power, Damien 
<damien.po...@intel.com>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

I'm using Barometer master and guest mode based upon the discussions we had 
(not the merged yaml). Trying to keep it simple on my end so I can get the 
basic single node deployment completed. That's done now as of 
https://gerrit.opnfv.org/gerrit/#/c/47475/ so I can start looking at your 
recent changes. Deploying patches from other repos gets a little complicated as 
I clone Barometer in the scripts, and have to edit the script to include 
checkout of your patch. So I usually wait until changes from other repos have 
merged to test. But I'll see what I can do in the meantime.

Thanks,
Bryan Sullivan | AT

From: Mytnyk, VolodymyrX [mailto:volodymyrx.myt...@intel.com]
Sent: Monday, November 20, 2017 5:18 AM
To: SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>; 
Tahhan, Maryam <maryam.tah...@intel.com<mailto:maryam.tah...@intel.com>>
Cc: Mcmahon, Tony B 
<tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>>; Power, Damien 
<damien.po...@intel.com<mailto:damien.po...@intel.com>>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

Hi Bryan,

Based on the logs you provided

AssertionError: Wrong SELECT condition, selected 4 metrics

looks like the latest changes of VES app is not used. E.g. the 
https://gerrit.opnfv.org/gerrit/#/c/47427/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_-23_c_47427_=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=wvfRnqnK1lxmd6iX8-opA5DLkTYOTy2WAtC-81JI7qc=lsPEgr9kC5dQSvNnVsMfzKNuVv4E3ZmbaqThVx6NXYc=>
 patch is not applied.


  1.  Are you sure that this patch is applied and node.yaml configuration is 
used by VES application?
  2.  Are you using collectd configuration files ( guests/hosts) provided by me 
on Friday?

Thanks and Regards,
Volodymyr

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Monday, November 20, 2017 3:09 PM
To: Tahhan, Maryam <maryam.tah...@intel.com<mailto:maryam.tah...@intel.com>>
Cc: Mytnyk, VolodymyrX 
<volodymyrx.myt...@intel.com<mailto:volodymyrx.myt...@intel.com>>; Mcmahon, 
Tony B <tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>>; Power, 
Damien <damien.po...@intel.com<mailto:damien.po...@intel.com>>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

If there's a better way to report issues, e.g. thru the github mirror, let me 
know. I do have a number of things to followup on from the testing.

Thanks,
Bryan Sullivan | AT

From: Tahhan, Maryam [mailto:maryam.tah...@intel.com]
Sent: Monday, November 20, 2017 5:06 AM
To: SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Cc: Mytnyk, VolodymyrX 
<volodymyrx.myt...@intel.com<mailto:volodymyrx.myt...@intel.com>>; Mcmahon, 
Tony B <tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>>; Power, 
Damien <damien.po...@intel.com<mailto:damien.po...@intel.com>>
Subject: RE: [opnfv-tech-discuss] [barometer] ves_app.py exception when 
collecting from multiple collectd clients

Hey Bryan
Thanks for the bug report. I've pinged Volodymyr on this, not sure if he 
follows the mailing list.

BR
Maryam

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L (BRYAN L)
Sent: Monday, November 20, 2017 4:39 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [barometer] ves_app.py exception when collecting 
from multiple collectd clients

Hi Barometer te

[opnfv-tech-discuss] [Auto] Test entry into the database via swagger

[SULLIVAN, BRYAN L (BRYAN L)]

All,

As we discussed today if you need access or help to enter tests into the 
swagger UI for the test database reach out to me. We can setup an adhoc call to 
help you get started.

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] [barometer] VES Heartbeats

[SULLIVAN, BRYAN L (BRYAN L)]

Alok,

Thinking about the shared Agent (ves_app.py from Barometer) design, in which we 
don't need an agent running on each node, but can use a single agent running on 
the local cloud which aggregates VES events from the Kafka bus, it brings up 
the question of how heartbeats are supposed to work (and what we use them for) 
in the VES design.

Beyond the VNF (presumably by integration of the ONAP VES library into the 
VNF), have you been assuming that the heartbeats represent the health of:

  *   The VES agent
  *   A host (real or virtual, whether running a VES agent or not) from which 
VES events are received

If the latter, we need to consider how the agent can proxy the heartbeats for 
hosts on which there is no agent running, e.g. the agent can keep a host-based 
flag that is set whenever a collectd event is picked up on the Kafka bus during 
the heartbeat period, and send a Heartbeat report for each host at the end of 
the period. But really in that case couldn't DCAE derive that information 
anyway from what it had received? So it calls into question the purpose of the 
heartbeat beyond the VNF itself (the obvious use case) - I just need to clarify 
it.

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] [barometer] ves_app.py exception when collecting from multiple collectd clients

[SULLIVAN, BRYAN L (BRYAN L)]

Hi Barometer team,

The exception below came up when the ves_app began getting events from multiple 
collectd clients (one on each compute node). This occurs when there is a shared 
kafka server and a single ves_app instance which is getting the events from the 
multiple collectd clients. The exceptions started happening as soon as I 
activated the 2nd collectd client. The exception info "AssertionError: Wrong 
SELECT condition, selected 4 metrics" changed from "2 metrics" to "4 metrics" 
as I added the 2nd thru 4th collectd client, so I'm pretty sure the issue is 
related to there being more than one collectd client.

Let me know if you need more info.

Exception in thread Thread-130:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 1073, in run
self.function(*self.args, **self.kwargs)
  File "/opt/ves/barometer/3rd_party/collectd-ves-app/ves_app/normalizer.py", 
line 561, in on_timer
self.process_measurements()
  File "/opt/ves/barometer/3rd_party/collectd-ves-app/ves_app/normalizer.py", 
line 583, in process_measurements
measurements = loader.get_data()
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 33, 
in get_data
return self.construct_document(self.get_node())
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 48, 
in construct_document
for dummy in generator:
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 398, 
in construct_yaml_map
value = self.construct_mapping(node)
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 208, 
in construct_mapping
return BaseConstructor.construct_mapping(self, node, deep=deep)
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 133, 
in construct_mapping
value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 88, 
in construct_object
data = constructor(self, node)
  File "/opt/ves/barometer/3rd_party/collectd-ves-app/ves_app/normalizer.py", 
line 411, in from_yaml
items.append(loader.construct_mapping(item))
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 208, 
in construct_mapping
return BaseConstructor.construct_mapping(self, node, deep=deep)
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 133, 
in construct_mapping
value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python2.7/dist-packages/yaml/constructor.py", line 88, 
in construct_object
data = constructor(self, node)
  File "/opt/ves/barometer/3rd_party/collectd-ves-app/ves_app/normalizer.py", 
line 350, in from_yaml
'Wrong SELECT condition, selected {} metrics'.format(len(metrics))
AssertionError: Wrong SELECT condition, selected 4 metrics


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] Agenda Items for Technical Discussion This Week Nov 16

[SULLIVAN, BRYAN L (BRYAN L)]

Maybe we can have PTLs discuss some Fraser release goals, e.g. as I noted in 
the email [opnfv-tech-discuss] Euphrates retrospective input 

 ?

I would welcome for example the opportunity to get feedback on the points I 
raised in that email wrt the Fraser release goals. Probably other PTLs would 
like the chance to outline their goals for the release as well and get feedback 
and support for their plans in this release.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of HU, BIN
Sent: Tuesday, November 14, 2017 10:08 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Agenda Items for Technical Discussion This Week 
Nov 16

Hello community,

Please let me know if there is any topic you want to discuss this Thursday.

Thanks
Bin


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

[opnfv-tech-discuss] Euphrates retrospective input

[SULLIVAN, BRYAN L (BRYAN L)]

On the release call today I mentioned several takeaways from the OPNFV 
Euphrates release that might be good to capture as part of the retrospective. 
Thanks to the release call participants to allow me to take the final 10 
minutes for these thoughts!

This release allowed us a pause on project goals that in part at least have 
shifted to ONAP, and to establish a new/modified strategy for how OPNFV can add 
value to ONAP and create more synergy in the new networking umbrella structure. 
The projects include primarily VES and Models, which have rejoined the release 
program with these goals for Fraser:

  *   VES: Test tools and 
tests for certification of OPNFV reference platform distributions and VNFs as 
compliant with the VES schema and interoperable with ONAP for lifecycle 
management based upon VES events.
 *   Supporting that goal is the ongoing work of deploying the Barometer 
VES agents and the new work of integrating them with ONAP components that will 
drive lifecycle management (DCAE and microservices that implement closed loop 
control functions).
 *   The test suite that verifies VES functionality for open source NFV 
platforms (e.g. the cloud-native platform WIP in Models) and VNFs (WIP in 
Models) will thus be directly usable by vendors/projects that develop NFV 
platforms and VNFs, and potentially form part of the Dovetail suite.
 *   This work will enable the Auto project to fulfill some of its goals 
for platform/VNF assessments under ONAP automation, e.g. per goals for ONAP's 
role in measuring/managing platform/VNF efficiency, performance, and resilience.
 *   ONAP projects related to VES are more able to focus on the data model 
and architecture for closed-loop control, and work with OPNFV on the broader 
goals of promoting VES support in diverse NFV platforms and VNFs
  *   Models: Use case 
tests for certification of VIM platforms (cloud-native primarily, but also as 
time permits OpenStack-based VIM platforms) and VNFs as compatible with VNF 
orchestration via ONAP for lifecycle management based upon TOSCA-based VNF 
blueprints.
 *   ONAP has taken over most of the meta-goals of Models e.g. driving 
collaboration across SDOs and open source projects for modeled VNF support. 
OPNFV can retain however a key role in developing tools that apply those 
modeled VNF concepts to a diversity of NFV platforms and VNFs.
 *   Since the overall goal for modeling VNFs is that a single blueprint 
can be deployed on (and across) diverse NFV platforms, expanding Models focus 
to cloud-native and hybrid-cloud deployment further fits with the goal of 
supporting ONAP-managed VNF lifecycle in the true diversity of NFV environments 
that will be required. This will also be used to support the goals of the Auto 
project.
 *   Similar with VES, ONAP projects can thus focus on cloud/application 
orchestration, and benefit from OPNFV's driving the readiness of 
multi-cloud-compatible orchestration tools (e.g. Cloudify/Aria) for use in the 
ONAP Multi-VIM project, as applied to diverse NFV platforms. In some cases, 
e.g. for cloud-native, this work will accelerate ONAP's readiness to expand 
into hybrid cloud environments in subsequent releases.

The other takeaways from Euphrates reflected a shift in strategy for our focus 
in OPNFV:

  *   Away from (or at least expanding focus beyond) OpenStack-based cloud 
platforms as the core of OPNFV-inspired NFV platforms. This was partly due to 
the complexity of the OpenStack platform and the ongoing difficulty in getting 
OPNFV distros based upon it reliably deployed, but also its insufficiency to 
meet the goals of evolving beyond first-generation, large-datacenter focused 
deployments of legacy network functions as VM-based VNFs. Thus the refocus on 
cloud-native and hybrid-cloud in Models and VES.
 *   Models in particular will produce a variety of cloud-native stacks 
(Kubernetes, Docker-ce/Moby, Rancher) as test tools, including common 
subsystems such as SDS (e.g. 
ceph-docker),
 monitoring (Prometheus, VES), orchestration (Cloudify).
  *   Related to the above, the insufficiency of OpenStack as currently 
deployed in OPNFV installers to meet the efficiency and resiliency goals of 
edge-focused NFV platforms.
 *   We had proposed the OpenStack-Helm (OSH) based 
Armada project earlier to address 
the latter goal (since kubernetes will enable much more resilient management of 
the OpenStack control plane), but that has not taken off yet. Nonetheless the 
OSH project is proceeding and getting pushed toward production-readiness by 
service providers (such as 
AT), and I fully expect 
there will be renewed opportunity for OPNFV to kick off a project 

Re: [opnfv-tech-discuss] [barometer] Issues in VES Guide

[SULLIVAN, BRYAN L (BRYAN L)]

Sure, that works too. If there’s anyone available to talk today over IRC, I’m 
bryan_att and will be working on this today.

Thanks,
Bryan Sullivan | AT

From: Aaron Smith [mailto:aasm...@redhat.com]
Sent: Monday, November 13, 2017 6:34 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [barometer] Issues in VES Guide

Hi Bryan,
 Can we talk about this during the second part of the Weekly meeting tomorrow?

Aaron

On Sun, Nov 12, 2017 at 9:41 PM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi Barometer team,

I’d like to have a call asap this week, or an IRC chat, to discuss the issues 
I’ve found in scripting the VES install, and other questions on how this is 
intended to (or can) work.

My WIP patch for VES is at 
https://gerrit.opnfv.org/gerrit/#/c/47101/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.opnfv.org_gerrit_-23_c_47101_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ntavL3wyrZN_YIKkGikYots9sUMdeopLU2VpPJISxps=NTctm40IWucZulZXFazZQHtEXJlu_sY_gt8xnT7SMN0=>.
 Once this is working, you can refer to it in the guide as an example of how to 
automate the process. This will be much less painful than following the manual 
step-by-step process (which anyway will be documented in the script), and will 
be used in CI for VES.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Sunday, November 12, 2017 9:45 AM
To: 
'opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [barometer] Issues in VES Guide

Hi Barometer team,

Getting beyond the issues noted below (which still need to be addressed in the 
user guide):

  *   Setting the hostname in /etc/hosts prevented the kafka server from exiting

Here are a couple of other issues that need to be addressed as well:

  *   The “producer – consumer” test shown only works when you are installing 
interactively, as the “consumer” part does not automatically return control 
back to the shell or script. So when scripting this either we have to just 
assume that the kafka server is running properly, or we need a method of 
testing it that works in a script.
  *   At “Install development tools:” the guide only references how to do this 
for Centos. It should also clarify for Ubuntu (there is no “group” operation in 
apt-get).

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Friday, November 10, 2017 10:40 AM
To: 
'opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [barometer] Issues in VES Guide

Hi Barometer team,

Any help below is appreciated. I am scripting the setup for the new version of 
the VES plugin per 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/collectd.ves.userguide.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.opnfv.org_en_latest_submodules_barometer_docs_release_userguide_collectd.ves.userguide.html=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ntavL3wyrZN_YIKkGikYots9sUMdeopLU2VpPJISxps=TvzMfuMYJ8pEENUkkURnOgAWfQ7_tVWVMnzXOJ90DoA=>

I have found a couple of issues as below. Here are the steps I am using per the 
guide (note the additional step needed below, in bold):
# TODO: Guide should reference use of “apt-get” vs “apt”, per Ubuntu advice on 
which works better in scripts
sudo apt-get install -y default-jre
sudo apt-get install -y zookeeperd
sudo apt-get install -y python-pip
sudo pip install kafka-python
wget 
"http://www-eu.apache.org/dist/kafka/0.11.0.0/kafka_2.11-0.11.0.0.tgz<https://urldefense.proofpoint.com/v2/url?u=http-3A__www-2Deu.apache.org_dist_kafka_0.11.0.0_kafka-5F2.11-2D0.11.0.0.tgz=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ntavL3wyrZN_YIKkGikYots9sUMdeopLU2VpPJISxps=JFi0Nr3iliKP33GvGYAHn8eFHL9aMrZq3GxRqhdrxOw=>"
tar -xvzf kafka_2.11-0.11.0.0.tgz
sed -i -- 's/#delete.topic.enable=true/delete.topic.enable=true/' 
kafka_2.11-0.11.0.0/config/server.properties<https://urldefense.proofpoint.com/v2/url?u=http-3A__server.properties=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ntavL3wyrZN_YIKkGikYots9sUMdeopLU2VpPJISxps=wvW57XCN7UDakxBC6kKQtyF3oDE2zEVj-jLctOO7qsY=>
sudo nohup 
kafka_2.11-0.11.0.0/bin/kafka-server-start.sh<https://urldefense.proofpoint.com/v2/url?u=http-3A__server-2Dstart.sh=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ntavL3wyrZN_YIKkGikYots9sUMdeopLU2VpPJISxps=WO9G4qyDm87PISQA88ng009ZdB9aHsdNIzHF5dhSBzM=>
 \
  
kafka_2.11-0.11.0.0/config/server.properties<https://urldefense.proofpoint.com/v2/url?

Re: [opnfv-tech-discuss] [barometer] Issues in VES Guide

[SULLIVAN, BRYAN L (BRYAN L)]

Hi Barometer team,

I'd like to have a call asap this week, or an IRC chat, to discuss the issues 
I've found in scripting the VES install, and other questions on how this is 
intended to (or can) work.

My WIP patch for VES is at https://gerrit.opnfv.org/gerrit/#/c/47101/. Once 
this is working, you can refer to it in the guide as an example of how to 
automate the process. This will be much less painful than following the manual 
step-by-step process (which anyway will be documented in the script), and will 
be used in CI for VES.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Sunday, November 12, 2017 9:45 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [barometer] Issues in VES Guide

Hi Barometer team,

Getting beyond the issues noted below (which still need to be addressed in the 
user guide):

  *   Setting the hostname in /etc/hosts prevented the kafka server from exiting

Here are a couple of other issues that need to be addressed as well:

  *   The "producer - consumer" test shown only works when you are installing 
interactively, as the "consumer" part does not automatically return control 
back to the shell or script. So when scripting this either we have to just 
assume that the kafka server is running properly, or we need a method of 
testing it that works in a script.
  *   At "Install development tools:" the guide only references how to do this 
for Centos. It should also clarify for Ubuntu (there is no "group" operation in 
apt-get).

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Friday, November 10, 2017 10:40 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [barometer] Issues in VES Guide

Hi Barometer team,

Any help below is appreciated. I am scripting the setup for the new version of 
the VES plugin per 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/collectd.ves.userguide.html

I have found a couple of issues as below. Here are the steps I am using per the 
guide (note the additional step needed below, in bold):
# TODO: Guide should reference use of "apt-get" vs "apt", per Ubuntu advice on 
which works better in scripts
sudo apt-get install -y default-jre
sudo apt-get install -y zookeeperd
sudo apt-get install -y python-pip
sudo pip install kafka-python
wget "http://www-eu.apache.org/dist/kafka/0.11.0.0/kafka_2.11-0.11.0.0.tgz;
tar -xvzf kafka_2.11-0.11.0.0.tgz
sed -i -- 's/#delete.topic.enable=true/delete.topic.enable=true/' 
kafka_2.11-0.11.0.0/config/server.properties
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
# TODO: missing step in guide: hostname must be in /etc/hosts
echo "$(ip route get 8.8.8.8 | awk '{print $NF; exit}') $HOSTNAME" | sudo tee 
-a /etc/hosts
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper   localhost:2181 
--topic TopicTest --from-beginning

When I run the server, it exits. I saw the note about the exit when I ran the 
"Producer" test per the guide, which complained that there was no Broker 
available (I guess due to the exit). After that I ran the "Consumer" test (I 
did not see the note about the server exit yet), which has hanged, and I can't 
quit that command. Any ideas for:

  *   what I do now, to get my terminal prompt back (other than wipe the server 
and start again)
  *   what may have caused the server to exit

ubuntu@opnfv01:~$ sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
>   kafka_2.11-0.11.0.0/config/server.properties > 
> kafka_2.11-0.11.0.0/kafka.log 2>&1 &
[1] 6797
ubuntu@opnfv01:~$
ubuntu@opnfv01:~$ echo "Hello, World" | 
kafka_2.11-0.11.0.0/bin/kafka-console-producer.sh \
[1]+  Exit 1  sudo nohup 
kafka_2.11-0.11.0.0/bin/kafka-server-start.sh 
kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1
>   --broker-list localhost:9092 --topic TopicTest > /dev/null
[2017-11-10 18:22:18,189] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-11-10 18:22:18,241] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
...

ubuntu@opnfv01:~$ kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper 
  localhost:2181 --topic TopicTest --from-beginning
Using the ConsoleConsumer with old consumer is deprecated and will be removed 
in a future major release. Consider using the new consumer

Re: [opnfv-tech-discuss] [barometer] Issues in VES Guide

[SULLIVAN, BRYAN L (BRYAN L)]

Hi Barometer team,

Getting beyond the issues noted below (which still need to be addressed in the 
user guide):

  *   Setting the hostname in /etc/hosts prevented the kafka server from exiting

Here are a couple of other issues that need to be addressed as well:

  *   The "producer - consumer" test shown only works when you are installing 
interactively, as the "consumer" part does not automatically return control 
back to the shell or script. So when scripting this either we have to just 
assume that the kafka server is running properly, or we need a method of 
testing it that works in a script.
  *   At "Install development tools:" the guide only references how to do this 
for Centos. It should also clarify for Ubuntu (there is no "group" operation in 
apt-get).

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Friday, November 10, 2017 10:40 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Subject: [barometer] Issues in VES Guide

Hi Barometer team,

Any help below is appreciated. I am scripting the setup for the new version of 
the VES plugin per 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/collectd.ves.userguide.html

I have found a couple of issues as below. Here are the steps I am using per the 
guide (note the additional step needed below, in bold):
# TODO: Guide should reference use of "apt-get" vs "apt", per Ubuntu advice on 
which works better in scripts
sudo apt-get install -y default-jre
sudo apt-get install -y zookeeperd
sudo apt-get install -y python-pip
sudo pip install kafka-python
wget "http://www-eu.apache.org/dist/kafka/0.11.0.0/kafka_2.11-0.11.0.0.tgz;
tar -xvzf kafka_2.11-0.11.0.0.tgz
sed -i -- 's/#delete.topic.enable=true/delete.topic.enable=true/' 
kafka_2.11-0.11.0.0/config/server.properties
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
# TODO: missing step in guide: hostname must be in /etc/hosts
echo "$(ip route get 8.8.8.8 | awk '{print $NF; exit}') $HOSTNAME" | sudo tee 
-a /etc/hosts
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper   localhost:2181 
--topic TopicTest --from-beginning

When I run the server, it exits. I saw the note about the exit when I ran the 
"Producer" test per the guide, which complained that there was no Broker 
available (I guess due to the exit). After that I ran the "Consumer" test (I 
did not see the note about the server exit yet), which has hanged, and I can't 
quit that command. Any ideas for:

  *   what I do now, to get my terminal prompt back (other than wipe the server 
and start again)
  *   what may have caused the server to exit

ubuntu@opnfv01:~$ sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
>   kafka_2.11-0.11.0.0/config/server.properties > 
> kafka_2.11-0.11.0.0/kafka.log 2>&1 &
[1] 6797
ubuntu@opnfv01:~$
ubuntu@opnfv01:~$ echo "Hello, World" | 
kafka_2.11-0.11.0.0/bin/kafka-console-producer.sh \
[1]+  Exit 1  sudo nohup 
kafka_2.11-0.11.0.0/bin/kafka-server-start.sh 
kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1
>   --broker-list localhost:9092 --topic TopicTest > /dev/null
[2017-11-10 18:22:18,189] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-11-10 18:22:18,241] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
...

ubuntu@opnfv01:~$ kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper 
  localhost:2181 --topic TopicTest --from-beginning
Using the ConsoleConsumer with old consumer is deprecated and will be removed 
in a future major release. Consider using the new consumer by passing 
[bootstrap-server] instead of [zookeeper].
[2017-11-10 18:25:34,303] WARN 
[console-consumer-18617_opnfv01-1510338334002-e1877230], no brokers found when 
trying to rebalance. (kafka.consumer.ZookeeperConsumerConnector)
^C

^C^C^C^C^C^C^C^C^C


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] [barometer] Issues in VES Guide

[SULLIVAN, BRYAN L (BRYAN L)]

Hi Barometer team,

Any help below is appreciated. I am scripting the setup for the new version of 
the VES plugin per 
http://docs.opnfv.org/en/latest/submodules/barometer/docs/release/userguide/collectd.ves.userguide.html

I have found a couple of issues as below. Here are the steps I am using per the 
guide (note the additional step needed below, in bold):
# TODO: Guide should reference use of "apt-get" vs "apt", per Ubuntu advice on 
which works better in scripts
sudo apt-get install -y default-jre
sudo apt-get install -y zookeeperd
sudo apt-get install -y python-pip
sudo pip install kafka-python
wget "http://www-eu.apache.org/dist/kafka/0.11.0.0/kafka_2.11-0.11.0.0.tgz;
tar -xvzf kafka_2.11-0.11.0.0.tgz
sed -i -- 's/#delete.topic.enable=true/delete.topic.enable=true/' 
kafka_2.11-0.11.0.0/config/server.properties
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
# TODO: missing step in guide: hostname must be in /etc/hosts
echo "$(ip route get 8.8.8.8 | awk '{print $NF; exit}') $HOSTNAME" | sudo tee 
-a /etc/hosts
sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
  kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1 &
kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper   localhost:2181 
--topic TopicTest --from-beginning

When I run the server, it exits. I saw the note about the exit when I ran the 
"Producer" test per the guide, which complained that there was no Broker 
available (I guess due to the exit). After that I ran the "Consumer" test (I 
did not see the note about the server exit yet), which has hanged, and I can't 
quit that command. Any ideas for:

  *   what I do now, to get my terminal prompt back (other than wipe the server 
and start again)
  *   what may have caused the server to exit

ubuntu@opnfv01:~$ sudo nohup kafka_2.11-0.11.0.0/bin/kafka-server-start.sh \
>   kafka_2.11-0.11.0.0/config/server.properties > 
> kafka_2.11-0.11.0.0/kafka.log 2>&1 &
[1] 6797
ubuntu@opnfv01:~$
ubuntu@opnfv01:~$ echo "Hello, World" | 
kafka_2.11-0.11.0.0/bin/kafka-console-producer.sh \
[1]+  Exit 1  sudo nohup 
kafka_2.11-0.11.0.0/bin/kafka-server-start.sh 
kafka_2.11-0.11.0.0/config/server.properties > kafka_2.11-0.11.0.0/kafka.log 
2>&1
>   --broker-list localhost:9092 --topic TopicTest > /dev/null
[2017-11-10 18:22:18,189] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2017-11-10 18:22:18,241] WARN Connection to node -1 could not be established. 
Broker may not be available. (org.apache.kafka.clients.NetworkClient)
...

ubuntu@opnfv01:~$ kafka_2.11-0.11.0.0/bin/kafka-console-consumer.sh --zookeeper 
  localhost:2181 --topic TopicTest --from-beginning
Using the ConsoleConsumer with old consumer is deprecated and will be removed 
in a future major release. Consider using the new consumer by passing 
[bootstrap-server] instead of [zookeeper].
[2017-11-10 18:25:34,303] WARN 
[console-consumer-18617_opnfv01-1510338334002-e1877230], no brokers found when 
trying to rebalance. (kafka.consumer.ZookeeperConsumerConnector)
^C

^C^C^C^C^C^C^C^C^C


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] Anyone working with Clearwater-docker ?

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

This goes out to anyone who is experimenting with Metaswitch clearwater-docker, 
or who might have an idea what's going on with an error I am having when trying 
to build it. I'm doing this as part of the Models project development of 
cloud-native stacks (https://github.com/opnfv/models/tree/master/tools) and 
will be using Cloudify with the k8s plugin. See 
https://github.com/opnfv/models/tree/master/tools/kubernetes for the working 
scripts that I use to deploy the stack 
(k8s+Helm+ceph-docker+Prometheus+Cloudify)
 and a hello world demo app. Other than trying to expand to deployment of real 
VNFs, I'm also working on VES integration using the latest Barometer VES plugin.

The issue I am having is with building the Ellis image, and is the same as 
https://github.com/Metaswitch/clearwater-docker/issues/74. You can see my 
environment in the note I added to that issue thread.

Any advice is appreciated.

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] Hybrid Cloud goals for VES, Models, Auto in Fraser

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

I edited the Auto wiki use case 
page to capture what I 
mentioned on today’s call. See below. I can provide a walk-thru of progress 
toward the cloud-native stack described below next week, and the roadmap for 
integrating ONAP subsystems as described. I welcome any expressions of interest 
in or support of this work in the Models and VES projects. It’s also part of 
our broader effort to develop stacks that support edge cloud use cases, with 
integration of key ONAP subsystems as needed for semi-autonomous local cloud 
operation (related to what was, and still is ;-) proposed for the 
Edge and 
Armada projects, proceeding for 
cloud-native under the Models and VES projects in the meantime).

Hybrid Cloud for R1 ONAP Deployment and Hybrid VNF Use Cases

The diagram below (see 
link) illustrates two local 
cloud stacks (OpenStack, and cloud-native) which when used in combination 
represent one type of "hybrid cloud" environment. Hybrid clouds may be 
necessary to deploy VNFs that are partially cloud-native, i.e. include some 
VNFCs that are deployed in VMs under cloud control planes such as OpenStack. 
Work on a k8s-based cloud-native stack as illustrated below (the k8s nodes) is 
underway in the Models 
project, as part of a broader work on cloud-native stack options (see the 
tools folder in the Models 
repo). That k8s-based stack will be used as the local cloud control plane into 
which three key ONAP subsystems will be integrated: monitoring (VES), 
closed-loop control (DCAE, Policy), and orchestration (Multi-VIM, initially 
represented by Cloudify in standalone mode). See the VES Project 
Plan for info on how this 
relates to the Fraser release goals for VES. The other stack shown below is 
based on OpenStack Helm but could be any OpenStack-based OPNFV distribution. An 
OpenStack Helm based stack is expected to be ready to test with Auto early in 
2018 (WIP in OpenStack), and the hybrid cloud use cases thus sometime after 
that. In the meantime, we can make progress with the cloud-native stack and 
establish the basic ONAP subsystem integration and test approaches described 
above.

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] Request for AOB Item in next TSC Call: OPNFV Should Take a Lead Role in Open Source NFV Platform Security Scanning

[SULLIVAN, BRYAN L (BRYAN L)]

Already done.

Thanks,
Bryan Sullivan | AT

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Tuesday, October 10, 2017 5:56 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Request for AOB Item in next TSC Call: OPNFV 
Should Take a Lead Role in Open Source NFV Platform Security Scanning

Bryan,

In case we don't have time for this today, you can also discuss this in the 
Infra WG call on Mondays that now also includes the Security team

Thanks,

Ray

On Mon, Oct 9, 2017 at 5:55 PM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi all,

You may follow the security space and already be aware of the open source 
vulnerability that led to the recent Equifax breach. I want the TSC to 
seriously consider seeking budget to incorporate detailed security scanning for 
any open source software included in OPNFV platform builds. By crowd-sourcing 
the effort for this, OPNFV can make a very strong contribution to the 
reliability of platforms it releases, as well as benefit its members who may 
already be scanning code internally – essentially upstreaming that effort, or a 
large part of it.

If there’s time tomorrow on the TSC call, I would like 5-10 mins to further 
describe the proposal if needed.

For more info see e.g.:
https://blog.blackducksoftware.com/equifax-apache-struts-cve-2017-5638-vulnerability<https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.blackducksoftware.com_equifax-2Dapache-2Dstruts-2Dcve-2D2017-2D5638-2Dvulnerability=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=2HIzuP0ExN7vZAbgIr95v-ARAypMpJtPLFqf6PDL19Y=Mqzjc7n36kM_7POO21gbXwsucWJDjRGzixXHVz8jF1U=>
https://blog.blackducksoftware.com/threat-check-for-struts-released-equifax-breach-dominates-news<https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.blackducksoftware.com_threat-2Dcheck-2Dfor-2Dstruts-2Dreleased-2Dequifax-2Dbreach-2Ddominates-2Dnews=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=2HIzuP0ExN7vZAbgIr95v-ARAypMpJtPLFqf6PDL19Y=VJ0bG3CMzVsvE1ML-OLRCoxclNV5DwKMaWKB3Ag04n4=>

Thanks,
Bryan Sullivan | AT


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=2HIzuP0ExN7vZAbgIr95v-ARAypMpJtPLFqf6PDL19Y=mGyAGnuP4uKMXR-dh7xs1B3q1tjl75AIx5A64s4aiGk=>

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

[opnfv-tech-discuss] Request for AOB Item in next TSC Call: OPNFV Should Take a Lead Role in Open Source NFV Platform Security Scanning

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

You may follow the security space and already be aware of the open source 
vulnerability that led to the recent Equifax breach. I want the TSC to 
seriously consider seeking budget to incorporate detailed security scanning for 
any open source software included in OPNFV platform builds. By crowd-sourcing 
the effort for this, OPNFV can make a very strong contribution to the 
reliability of platforms it releases, as well as benefit its members who may 
already be scanning code internally - essentially upstreaming that effort, or a 
large part of it.

If there's time tomorrow on the TSC call, I would like 5-10 mins to further 
describe the proposal if needed.

For more info see e.g.:
https://blog.blackducksoftware.com/equifax-apache-struts-cve-2017-5638-vulnerability
https://blog.blackducksoftware.com/threat-check-for-struts-released-equifax-breach-dominates-news

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] [Infra] Infra WG Weekly Meeting Minutes - Oct. 9th

[SULLIVAN, BRYAN L (BRYAN L)]

I submitted a commit for the securedlab project with an alternate proposal for 
the IDF as I mentioned today. At the least I recommend that we discuss/define 
the schema for these proposals in more detail, as I have included in the 
commit: https://gerrit.opnfv.org/gerrit/#/c/44603/

Here is the commit message:
Alternate proposal for IDF, adding more schema node types and schema 
description. This is intended as an actual IDF for the AT pod. The goal of 
this proposal is to pull out any PDF aspects that are variable in their 
intended use, e.g. anything other than physical devices with fixed 
configuration. It also assumed here that some pre-installation may have been 
completed based upon the static information in the PDF, e.g. host OS install 
and configuration, based upon the ability of the installer to assign 
PDF-declared devices with specific roles/configuration. That assumption is 
intended to keep this file to a useful minimum of choices that the pod owner 
wants to apply to the pod, for all installers.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jack Morgan
Sent: Monday, October 09, 2017 9:38 AM
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting Minutes - Oct. 9th

October 9th

Agenda:
1. Status update on PDF
·complete discussion from last week as this is a deliverable for 
Euphrates release
2. LaaS and Dashboard integration Lincoln 
Lavoie
3. Infra documentation on RTD - patch 
40329
 merged, what else?
a. Discussion of Infra documentation
4. Zuul v3, Fatih 
Degirmenci
 .   possibility to start a prototype?
5. Follow up on security audit job logs  
[https://jira.opnfv.org/secure/viewavatar?size=xsmall=10303=issuetype]
 
RELENG-272
 - Ericsson Build 3 not reporting failures to comments IN PROGRESS
6. F Release participation
7. Review actions items

Minutes 
(link)
1. Status update on PDF
·David_Orange reports that IDF is mostly complete and haven't heard any 
feedback during the last week on his patch below
·work in progress patch  
https://gerrit.opnfv.org/gerrit/#/c/42233/5/labs/orange/idf-pod1.yaml
·current SDF patch 
https://gerrit.opnfv.org/gerrit/#/c/36977/
2. LaaS and Dashboard integration
·lylavoie is working on LF hosting issues with bramwelt but will focus 
on it after the release
·requirements gathering and plan is being tracked via Dashboard 
Roadmap
3. Infra documentation on RTD
·initial patch 

[opnfv-tech-discuss] {Auto] Auto Project Meeting 10/09/2017

[SULLIVAN, BRYAN L (BRYAN L)]

I added a diagram to https://wiki.opnfv.org/display/AUTO/Auto+Use+Cases.
Also update to the lab requirements at 
https://wiki.opnfv.org/display/AUTO/Auto+Lab+Requirements.

Thanks,
Bryan Sullivan | AT

From: Michael O'Brien (OPNFV Confluence) [mailto:conflue...@opnfv.org]
Sent: Monday, October 09, 2017 7:15 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Subject: [OPNFV confluence] Michael O'Brien mentioned you on "Auto Project 
Meeting 10/09/2017"

[cid:image002.jpg@01D340D2.A9F0D980]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_-7Emichaelobrien-3Fsrc-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=Fv-2OpW5jE7mpjjSoo-C3oEJAWeBDFeHOgktuLT_KOw=>

Michael O'Brien mentioned you on a page




[mention 
icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D12392005-26src-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=ExjMv6GZWJBRykQw5E-36HCHJy3wa1TvLKPEoEY5cR4=>


Auto Project Meeting 
10/09/2017<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D12392005-26src-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=ExjMv6GZWJBRykQw5E-36HCHJy3wa1TvLKPEoEY5cR4=>



···

DCAE 
(https://wiki.onap.org/display/DW/Meetings<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Meetings=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=FRPEJVuwKiNl65vfoZqq5x6hD56WDtKt8Z0zGcV47Jk=>)
 deployment (HEAT and K8S) talk scope discuss dcae status in heat (wrapper from 
oom) - provide more wiki instructions - @Michael 
O'Brien<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_-7Emichaelobrien=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=cCagHpy-PhXukWg1ElbRC0wO1wHmZW0-Jm0LrjQZ2og=>
 (K8S) @Bryan 
Sullivan<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_-7Eblsaws=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=xrHsCwMvv3F_8tN40mON-djaTSRi_HS4vFUwEc-3ITQ=>
 (MultiVIM)

···

UC edge cloud, resiliency testng - need resiliency/monitoring assistance from 
teams - @Bryan 
Sullivan<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_-7Eblsaws=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=xrHsCwMvv3F_8tN40mON-djaTSRi_HS4vFUwEc-3ITQ=>

···


[View page 
Icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D12392005-26src-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=ExjMv6GZWJBRykQw5E-36HCHJy3wa1TvLKPEoEY5cR4=>

View 
page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D12392005-26src-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dview=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=OrbtGCluczz9awEKz9Fv7g=toPF5BssPKhEPBl4W3H1LR9NYGOh5IxN1g2I8ds1ciQ=ExjMv6GZWJBRykQw5E-36HCHJy3wa1TvLKPEoEY5cR4=>

•


[Add comment 
Icon]<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_pages_viewpage.action-3FpageId-3D12392005-26showComments-3Dtrue-26showCommentArea-3Dtrue-26src-3Dmail-26src.mail.timestamp-3D1507558528682-26src.mail.notification-3Dcom.atlassian.confluence.plugins.confluence-2Dmentions-2Dplugin-253Amention-2Dcreated-2Dnotification-26src.mail.recipient-3D2c9e48d5521dc09301523dbdf88f0004-26src.mail.action-3Dcomment-23addcomment=DwMFaQ=LFYZ-o9_HUMeMTSQ

Re: [opnfv-tech-discuss] [announce] F-release name poll (part II)

[SULLIVAN, BRYAN L (BRYAN L)]

FYI – the translation of Feio is “ugly, bad, nasty”. We should check these 
things before proposing them.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Sunday, October 01, 2017 1:36 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [announce] F-release name poll (part II)

All,

Here's the new poll for the F-release name:
https://www.surveymonkey.com/r/Y2CFCKP

The poll will close at 5pm Pacific Time on October 6th (Friday). Happy voting 
(again) :-) .

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] Discussion Topics for Weekly Technical Discussion this Thursday 09/28

[SULLIVAN, BRYAN L (BRYAN L)]

The one-size nature of the Pharos specs has always been one of the key 
weaknesses of the OPNFV program IMO. It does not reflect the likely diversity 
of hardware infra that will be used in different deployment environments, e.g. 
datacenter, edge, customer premises (enterprise, consumer), including compute, 
storage, and networking components. Even so, it’s been difficult to nail down 
how a Pharos POD should be configured (aside from how it *could* be as 
described in the spec, in loose terms), and that unclarity is I think a key 
aspect of why it’s so hard to deploy OPNFV installer-based distros in labs. For 
example, there is nothing AFAICT about how switches should be configured (in 
detail, as needed), though this is a key aspect of getting the networking to 
work.

I think that OPNFV should focus on documenting Pharos lab configs that have 
been proven compatible (with PDF’s provided) with specific installers, so that 
it’s possible to replicate that. In the process we would likely see the true 
diversity of POD configs that are needed, being clarified, as lab owners apply 
their PODs to different deployment use cases.

This would be a more useful approach to this IMO. Re 32GB or 128GB, personally 
for a datacenter-focused lab server I would recommend no less than 256GB or 
even 512GB (which we use in production). For an end-focused deployment the RAM 
may be less, and for a CPE deployment maybe 128GB or less, depending upon the 
type of CPE. A key consideration in the memory footprint will be what is the 
nature of the control plane, e.g. OpenStack (heavyweight) or cloud-native 
(lightweight).

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jack Morgan
Sent: Monday, September 25, 2017 10:39 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Discussion Topics for Weekly Technical 
Discussion this Thursday 09/28


Bin,

I think it would be a good conversation to have around hardware requirements in 
OPNFV and how they evolving. This is particularly interesting when thinking 
about OPNFV and ONAP integration. For example, the pharos specification only 
has a minimum of 32Gb of memory on nodes but I've gotten a couple of requests 
recently for an OPNFV POD with 128Gb of memory as a minimum. I wonder how 
sustainable this is long term for lab owners. I also wonder what other hardware 
requirements need to be evaluated within OPNFV (besides memory) I think this 
would be an interesting discussion. Anyone else?

On 09/25/2017 09:56 PM, HU, BIN wrote:
Hello community,

Please let me know if you have any topics or issues that need to be discussed 
at our weekly technical discussion this Thursday 09/28.

If no issues or topics, we may cancel the discussion this week.



--

Jack Morgan

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

Re: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E release.

[SULLIVAN, BRYAN L (BRYAN L)]

And thanks to you, Maryam, for your excellent work as PTL. I'm sure over the 
last couple of releases the team picked up some great pointers from you on how 
to do this job right, so we should be in good hands.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 3:30 AM
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Aaron Smith 

Cc: Verrall, Timothy ; Power, Damien 
; Mcmahon, Tony B 
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

Re: [opnfv-tech-discuss] [opnfv-tsc] Commiters-at-Large TSC election

[SULLIVAN, BRYAN L (BRYAN L)]

I think someone else also reported this issue... but I received two notices for 
the BOD election and none for the TSC election.

On Sep 13, 2017, at 7:32 AM, Raymond Paik 
> wrote:

All,

Thanks to everyone who voted so far...

If you have not voted yet, this is a reminder that the Committers-at-Large TSC 
election closes at 5pm Pacific Time this Friday (Sep. 15th).

Cheers,

Ray

On Sun, Sep 10, 2017 at 9:44 PM, Raymond Paik 
> wrote:
All,

For eligible 
committers,
 you will be receiving an email from "Ray Paik (CIVS poll supervisor)" to cast 
your vote to elect 5 Committers-at-Large TSC members.  Please note that the 
email will not be coming from my Linux Foundation email address and if you 
can't find the email (incl. in your spam folders), please let me know.

You can find the complete list of nominees (listed alphabetically by first 
name) on this 
page.
  The poll will close at 5pm Pacific Time on September 15th (Friday).

Thanks,

Ray

___
opnfv-tsc mailing list
opnfv-...@lists.opnfv.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk=wC_VaikCJwbB4-jm2-Y3BsxlP8uFR_u2KGZbuz1zP-A=xjoSmGA4v-hDeUu8uowvQN1s4oRQlXasBGbIcPUkcxg=
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OpenContrail support in OPNFV

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let me 
know the status of that work, e.g. which scenarios are deployable, and what is 
the latest build that is deployable. We had not been actively testing with OCL 
but it is a key part of our AIC (AT Integrated Cloud) platform, and I need to 
be sure that it's included in OPNFV supported scenarios. So though we are not 
the technical experts that would develop the scenarios, we would like to work 
with whoever is, to test the scenarios and ensure that they are supported in 
Dovetail asap.

Looking forward to any advice on this.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[SULLIVAN, BRYAN L (BRYAN L)]

I would like to nominate Tina Tsou (Arm) as a member of Committers-at-Large TSC.



Tina serves as an Enterprise Architect with ARM, a technical leadership 
position on the Enterprise Open Source Enablement team. In this highly visible 
role, Tina analyzes, designs, and implements dynamic strategies to establish 
first tier status for ARM architecture within open source communities and 
projects. As a thought leader, Tina forges and maintains strong partnerships 
with open source communities in support of multiple architectures, while 
prioritizing requirements for open source enablement in collaboration with Arm 
key stakeholders and relevant ecosystem partners.



Tina previously excelled as the Digital Domain Expert for Connectivity at 
Philips Lighting, where she championed the company’s first NB-IoT solution. She 
was also employed by Huawei (both in China and the US) for over 16 years as a 
Technical Lead and Principal Engineer.



Tina is the Project Technical Lead (PTL) of OPNFV Auto Project, and ONAP VNFSDK 
Project Manager. She also served as the Chair of Open Source SDN Breckenridge 
Working Group. She earned the distinction of being the first woman from a 
Chinese business enterprise to chair an IETF working group. Tina’s community 
leadership and collaborative spirit will be a great asset to the TSC.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Tuesday, September 05, 2017 10:32 PM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [announce] Opening nominations for 
Committers-at-Large TSC & Committer Board elections

All,

I don't believe I saw any nomination for either Committers-at-Large TSC or 
Committer Board elections  Yesterday was a holiday in the US, but this is still 
somewhat surprising...

Could someone to get things started please?  :-)

Thanks,

Ray

On Mon, Sep 4, 2017 at 9:31 PM, Raymond Paik 
> wrote:
Re-sending with the eligible committers link (the first link below) fixed...

Thanks,

Ray


On Sun, Sep 3, 2017 at 10:42 AM, Raymond Paik 
> wrote:
All,

I'm kicking off the nomination process for Committers-at-Large TSC (electing 5 
members) plus the Committer Board (electing 1) elections.

The list of eligible committers who can run for & vote in both elections are 
posted 
here,
 and I want to encourage all eligible committers to nominate community members 
who can represent the OPNFV technical community in both the TSC and the Board.  
Self nominations are also welcome.   As I mentioned earlier in the week, I hope 
to see a diverse group of community members represented--in terms of geography, 
gender, projects,  service providers/vendors, etc.--in the nominations.

Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing lists by 
5pm Pacific Time on September 8th (Friday).  You are welcome to reply to this 
email or if you're sending out a separate note, please include phrases like 
"Committer Board nomination" or "Committer-at-Large TSC nomination" in email 
subjects.  In nomination statements, please list the following information:

  *   Which election (TSC vs. Board) the nomination is for
  *   Name of the nominee
  *   Organization
  *   A brief description of nominee's qualifications
As nominations are accepted, I will add them to this 
page.
  There will be separate Condorcet ballot for these two elections, and they 
will be sent out by September 11th.

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] [Auto] Telemetry in Auto-UC-01

[SULLIVAN, BRYAN L (BRYAN L)]

Here are some examples:
- the ability to make workload placement decisions (e.g. knowing that a VNF can 
be deployed in an edge cloud) requires a running view of key metrics for the 
NFVI e.g. compute, network, storage, and control plane capacity (if there's 
some limitation based on that). This is basic telemetry data that will come 
from Barometer/VES.
- similar to the above, for scaling decisions
- the ability to respond to stress (e.g. faults, threats) depends upon rapid 
notification of fault/threat start/end (or trending issues that can result in a 
fault/threat). We'll need to break this down into some typical use cases to 
focus on. Somewhere I hope we can find open data about what types of faults or 
failure modes are most common (the same for security threats)

On Sep 6, 2017, at 11:03 AM, Tina Tsou  wrote:

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

[opnfv-tech-discuss] [barometer] Updates to VES Plugin install guide

[SULLIVAN, BRYAN L (BRYAN L)]

Alan,

Per https://gerrit.opnfv.org/gerrit/#/c/39603/, what is the new/changed process 
for installing the VES plugin?
I checked out that patch and edited the new conf file, and removed the earlier 
collectd plugin conf (implied by "All collectd modules removed").
What do I need to change in the install process for this now to get it working?

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] weekly call agenda 8/11

[SULLIVAN, BRYAN L (BRYAN L)]

I added the table for beta participants.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Monday, August 14, 2017 10:44 PM
To: Dave Urschatz <dave.ursch...@cengn.ca>; Lincoln Lavoie 
<lylav...@iol.unh.edu>; SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Here is the Beta test page: 
https://wiki.opnfv.org/display/dovetail/Dovetail+Beta<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_dovetail_Dovetail-2BBeta=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=v9curOpTMUn7PlLbVHRqXlFJZJ275Ip0Q09llzCX4dI=0kagZLID-U737LKkt3XcjnqiEd5jSAxLtDcRofH-Yys=>
I think I summarized most of the comments I received so far. Please let me know 
if I missed anything. Additional comments welcome and we’ll discuss in this 
week’s call.
Again, thanks Bryan and Lincoln for your suggestions.

Dave,
On your first two points, please refer to the above wiki page.
For the third point, yes, current testing assumes Pharos pods for the system 
under test.

Wenjing

From: Wenjing Chu
Sent: Monday, August 14, 2017 4:47 PM
To: 'Dave Urschatz' <dave.ursch...@cengn.ca<mailto:dave.ursch...@cengn.ca>>; 
Lincoln Lavoie <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>; SULLIVAN, 
BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Just an ack that I’ll be populating a wiki page today incorporating discussions 
at last Friday’s call and some of comments in this thread.
Thanks for all the inputs.

Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Urschatz
Sent: Friday, August 11, 2017 10:39 AM
To: Lincoln Lavoie <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>; 
SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

I missed the call today also.

  *   What timeframe are we planning this for?
  *   How long would the trial be?
  *   Bare Metal Pharos PODs only?  (I think this is yes but want to confirm.)

Best Regards,
Dave

Dave Urschatz
Senior Technical Lead
[cid:image001.jpg@01D31678.61A55C70]<https://urldefense.proofpoint.com/v2/url?u=http-3A__cengn.ca_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=v9curOpTMUn7PlLbVHRqXlFJZJ275Ip0Q09llzCX4dI=0P_h6U9LBNif0kZMknVIfAog3vlWe-ytlJS1Tm3zbTA=>
555 Legget Drive| Tower A | Suite 600| Ottawa ON | K2K 2X3 | 613-963-1201


From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Lincon Lavoie <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>
Date: Friday, August 11, 2017 at 11:16 AM
To: "SULLIVAN, BRYAN L (BRYAN L)" 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

And 3rd party labs. :)

On Fri, Aug 11, 2017 at 11:14 AM, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
And before I forget, we should also allow end-users to participate in the beta 
program of course!

Thanks,
Bryan Sullivan | AT

-Original Message-
From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Friday, August 11, 2017 8:04 AM
To: 'Lincoln Lavoie' <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>; 
Christopher Price 
<christopher.pr...@ericsson.com<mailto:christopher.pr...@ericsson.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Wenjing is going to add a page where we can document the plans and results for 
the beta program. Here’s what I suggested:
• We freeze the CVP suite and Dovetail tools prior to start of the beta
• We offer all OPNFV vendor members who produce commercial platforms that are 
applicable the chance to run the tests against their product and produce 
results provided back to OPNFV (in the form that CVP result reviewers will be 
expected to assess)
• We get C to provide a team of result reviewers for the beta
• On the wiki we build a table of those vendors

Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

[SULLIVAN, BRYAN L (BRYAN L)]

I usually mean “ports” (distinct ethernet connections) when I say “NIC” so by I 
expect production-grade servers to typically come with 4 onboard ports, often 
configured as 2 10GB and 2 1GB.

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Wednesday, August 16, 2017 6:57 AM
To: Frank Brockners (fbrockne) ; Bryan Sullivan 
; Fatih Degirmenci ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware


Few comments:
•  Would it be possible to distinguish between NICs and ports? When I 
see “2 NICs” or “4 NICs” I suppose these are 10G ports?
•  I’d recommend using DPDK compliant NICs everywhere, best is to use 
NICs that are known to work well with DPDK (e.g. Intel X710 NIC has 4x10G ports)
•  What is the total ingress (or outgress) tenant bandwidth required 
for compute nodes? 10G or 20G? This will determine how many ports are required 
for tenant traffic
•  Is there a need to also support SRIOV? This will require extra ports
•  If possible, I’d recommend using 2 NICs per server – 1 on each NUMA 
socket for a total of 8x10G ports
•  How many top of rack switches are there per vPOD? 1 or 2 configured 
in HA?
•  Please also make sure the jump host for each vPOD has at least 2 x 
10G ports connected on the vPOD top of rack switch(es) and dedicated for tenant 
traffic – this is *very* important in order to run software traffic generator 
(e,g TRex) on the jumphost! Without this it will be very difficult to get any 
data plane performance using tools like NFVbench

Thanks

  Alec



From: 
>
 on behalf of "Frank Brockners (fbrockne)" 
>
Date: Wednesday, August 16, 2017 at 6:44 AM
To: Bryan Sullivan >, Fatih 
Degirmenci 
>, 
"opnfv-tech-discuss@lists.opnfv.org" 
>
Subject: Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

True. A 2port 10GE NIC is ~500 $US. I’ve already updated the wiki ☺

Thanks again, Frank

From: Bryan Sullivan [mailto:bls...@hotmail.com]
Sent: Mittwoch, 16. August 2017 15:36
To: Frank Brockners (fbrockne) >; 
Fatih Degirmenci 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [infra] Proposal for LaaS Hardware

Re budget I don't think 2 or 4 NICs will have much impact given the type of 
servers we are talking about here (datacenter, production-grade servers). Most 
I have seen come with 4 NICs onboard and often dedicated IPMI.

Thanks,
Bryan Sullivan

From: Frank Brockners (fbrockne) >
Sent: Wednesday, August 16, 2017 3:36 AM
To: Bryan Sullivan; Fatih Degirmenci; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [infra] Proposal for LaaS Hardware

Bryan,

Thanks for raising an important point. IMHO 2 NICs are the minimal setup. This 
allows for performance focused setups (i.e. traffic enters on one NIC and 
leaves on another NIC), and it also allows for setups where you use the NICs 
for different purposes (e.g. dedicate a NIC to the kernel, and another one to 
VPP).

We can of course handle all three “types” of networks (admin, public, 
tenant/private) using VLAN/VLAN-ranges – but for some deployments a physical 
decoupling might ease things.

Per your suggestion: In order to allow for better flexibility, let’s plan with 
3 NICs for now. We can always scale back in case there are budget constraints.

Lights-out-management is something that is often vendor specific – and it may, 
or may not require a dedicated port (IPMI 2.0 even runs over VLANs) – but as 
part of the requirements list, we should spell out that lights-out-management 
is something we absolutely require. I’ll update the wiki accordingly.

Thanks, Frank



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bryan Sullivan
Sent: Dienstag, 15. August 2017 22:58
To: Fatih Degirmenci 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [infra] Proposal for LaaS Hardware

Fatih,

Do "2 x 10 Gbps NICs" suffice for Pharos POD servers? I thought 

Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

[SULLIVAN, BRYAN L (BRYAN L)]

And before I forget, we should also allow end-users to participate in the beta 
program of course!

Thanks,
Bryan Sullivan | AT

-Original Message-
From: SULLIVAN, BRYAN L (BRYAN L) 
Sent: Friday, August 11, 2017 8:04 AM
To: 'Lincoln Lavoie' <lylav...@iol.unh.edu>; Christopher Price 
<christopher.pr...@ericsson.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Wenjing is going to add a page where we can document the plans and results for 
the beta program. Here’s what I suggested:
• We freeze the CVP suite and Dovetail tools prior to start of the beta
• We offer all OPNFV vendor members who produce commercial platforms that are 
applicable the chance to run the tests against their product and produce 
results provided back to OPNFV (in the form that CVP result reviewers will be 
expected to assess)
• We get C to provide a team of result reviewers for the beta
• On the wiki we build a table of those vendors who plan to do this, the 
results of the tests as assessed by the team, and any feedback of the vendor 
(sub-pages as needed depending upon the amount of feedback)
• We do not release until both Dovetail and C are satisfied with the beta 
results, e.g. for scope (# of vendors participating) and results (reliability 
of the test suite/tools, and rate of compliance success)

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Lincoln Lavoie
Sent: Friday, August 11, 2017 7:40 AM
To: Christopher Price <christopher.pr...@ericsson.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Hi Chris,

We talked about this at the very end of the call, and I think it's in 
alignment.  I think we just need to write down the "rules" for the beta trial 
period, and get people signed up to participate in that process.  In other 
groups, I've seen the "cookie" to get that is the beta users would be the first 
users listed as "certified" and the organization would provide some press / 
media coverage to promote that accomplishment.

Cheers,
Lincoln

On Fri, Aug 11, 2017 at 10:29 AM, Christopher Price 
<mailto:christopher.pr...@ericsson.com> wrote:
Sounds like a good approach Lincoln.  It would be nice to see how something 
like that fits into our current activities.  Sorry I couldn’t be on the call to 
discuss it today, finding myself a little over scheduled at the moment. 
 
/ Chris
 
From: Lincoln Lavoie <mailto:lylav...@iol.unh.edu>
Date: Friday, 11 August 2017 at 16:01
To: Christopher Price <mailto:christopher.pr...@ericsson.com>
Cc: Tianhongbo <mailto:hongbo.tianhon...@huawei.com>, TECH-DISCUSS OPNFV 
<mailto:opnfv-tech-discuss@lists.opnfv.org>

Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
 
Hi Chris, 
 
What I've seen other programs do for trials/launch is the following:
 
1. Freeze the development of new work
2. A group of companies or users would volunteer to be beta trial testers, 
submitting feedback / bugs
3. Only bug fixes from those beta "customers" are reviewed and accepted.
4. We need to decide the beta outcome requirements (i.e. all customers are 
passing, all tests run, etc).
5. Once that outcome mark is hit, that version would be considered the version 
submitted for approval.
 
Cheers,
Lincoln
 
On Fri, Aug 11, 2017 at 5:12 AM, Christopher Price 
<mailto:christopher.pr...@ericsson.com> wrote:
Hi Hongbo,
 
Thanks, I’ve seen the information on the wiki.
I guess the questions I have relates more to:  Once we have the tool in a ready 
state, do we have a plan to validate it against volunteer commercial systems 
prior to having the TSC vote and making it generally available?  I didn’t see 
that information on the wiki page, maybe I missed it?
 
/ Chris
 
From: Tianhongbo <mailto:hongbo.tianhon...@huawei.com>
Date: Friday, 11 August 2017 at 11:05
To: Christopher Price <mailto:christopher.pr...@ericsson.com>, TECH-DISCUSS 
OPNFV <mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [dovetail] weekly call agenda 8/11
 
Hi Chris:
 
Here is the page for recoding the history of this. We can discuss further.
 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_dovetail_Running-2Bhistory-2Bfor-2Bthe-2Bdovetail-2Btool=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI=G6rTJNQcAfoxUGn85uFP2BFvW7yxOA-a5DF7tkl_Ex0=
 
Best regards
 
hongbo
 
From: mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
Christopher Price
Sent: 2017年8月11日 16:55
To: mailto:opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
 
Hi Guys,
 
Do we have a time-plan for the remain

Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

[SULLIVAN, BRYAN L (BRYAN L)]

Wenjing is going to add a page where we can document the plans and results for 
the beta program. Here’s what I suggested:
• We freeze the CVP suite and Dovetail tools prior to start of the beta
• We offer all OPNFV vendor members who produce commercial platforms that are 
applicable the chance to run the tests against their product and produce 
results provided back to OPNFV (in the form that CVP result reviewers will be 
expected to assess)
• We get C to provide a team of result reviewers for the beta
• On the wiki we build a table of those vendors who plan to do this, the 
results of the tests as assessed by the team, and any feedback of the vendor 
(sub-pages as needed depending upon the amount of feedback)
• We do not release until both Dovetail and C are satisfied with the beta 
results, e.g. for scope (# of vendors participating) and results (reliability 
of the test suite/tools, and rate of compliance success)

Thanks,
Bryan Sullivan | AT

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Lincoln Lavoie
Sent: Friday, August 11, 2017 7:40 AM
To: Christopher Price 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11

Hi Chris,

We talked about this at the very end of the call, and I think it's in 
alignment.  I think we just need to write down the "rules" for the beta trial 
period, and get people signed up to participate in that process.  In other 
groups, I've seen the "cookie" to get that is the beta users would be the first 
users listed as "certified" and the organization would provide some press / 
media coverage to promote that accomplishment.

Cheers,
Lincoln

On Fri, Aug 11, 2017 at 10:29 AM, Christopher Price 
 wrote:
Sounds like a good approach Lincoln.  It would be nice to see how something 
like that fits into our current activities.  Sorry I couldn’t be on the call to 
discuss it today, finding myself a little over scheduled at the moment. 
 
/ Chris
 
From: Lincoln Lavoie 
Date: Friday, 11 August 2017 at 16:01
To: Christopher Price 
Cc: Tianhongbo , TECH-DISCUSS OPNFV 


Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
 
Hi Chris, 
 
What I've seen other programs do for trials/launch is the following:
 
1. Freeze the development of new work
2. A group of companies or users would volunteer to be beta trial testers, 
submitting feedback / bugs
3. Only bug fixes from those beta "customers" are reviewed and accepted.
4. We need to decide the beta outcome requirements (i.e. all customers are 
passing, all tests run, etc).
5. Once that outcome mark is hit, that version would be considered the version 
submitted for approval.
 
Cheers,
Lincoln
 
On Fri, Aug 11, 2017 at 5:12 AM, Christopher Price 
 wrote:
Hi Hongbo,
 
Thanks, I’ve seen the information on the wiki.
I guess the questions I have relates more to:  Once we have the tool in a ready 
state, do we have a plan to validate it against volunteer commercial systems 
prior to having the TSC vote and making it generally available?  I didn’t see 
that information on the wiki page, maybe I missed it?
 
/ Chris
 
From: Tianhongbo 
Date: Friday, 11 August 2017 at 11:05
To: Christopher Price , TECH-DISCUSS 
OPNFV 
Subject: RE: [dovetail] weekly call agenda 8/11
 
Hi Chris:
 
Here is the page for recoding the history of this. We can discuss further.
 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_dovetail_Running-2Bhistory-2Bfor-2Bthe-2Bdovetail-2Btool=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI=G6rTJNQcAfoxUGn85uFP2BFvW7yxOA-a5DF7tkl_Ex0=
 
Best regards
 
hongbo
 
From: mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
Christopher Price
Sent: 2017年8月11日 16:55
To: mailto:opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
 
Hi Guys,
 
Do we have a time-plan for the remaining work?  
 
I see we still have a lot of documentation work to do and the test cases are in 
flux, but we have other things to do as well.
-  Do we intend to test/validate the documentation in any way with 
community scenario’s prior to merging it?  
o   Do we have people, resources and time-plans for that?
-  Will we arrange to test the toolchain against volunteer commercial 
systems in labs prior to making it available for use?
o   Same as above; people, resources, time-plans?
 
I can also see the links are all pointing to 

Re: [opnfv-tech-discuss] [Edge] Call to discuss next steps for Edge project proposal

[SULLIVAN, BRYAN L (BRYAN L)]

Understood – I was invited to it early. But it seemed to me that all these 
discussions are in the context of OpenStack nonetheless – unless they are open 
to discussion of solutions that do not include Nova, Neutron, … but anyway I’m 
sure it will be a good discussion forum so I wish those who are attending a 
great time.

Thanks,
Bryan Sullivan | AT

From: Christopher Price [mailto:christopher.pr...@ericsson.com]
Sent: Wednesday, August 09, 2017 11:29 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: Pasi Vaananen <pvaan...@redhat.com>; Stephen Wong 
<stephen.wo...@huawei.com>; Joel Halpern <joel.halp...@ericsson.com>; Timon 
Sloane <ti...@opennetworking.org>; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [Edge] Call to discuss next steps for Edge project proposal

Hey Bryan,

It is organized by the foundation, but it is not intended to focus exclusively 
on OpenStack.  Topics such as SDN, Containers, Hardware and security are, among 
other things, part of the conference streams.

Cheers,
Chris

Sent from my iPhone

On Aug 9, 2017, at 19:47, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Well that event is solely focused on OpenStack. We will have representation 
there, but I think we need to set our sights wider. So I’ll be at the 
http://events.linuxfoundation.org/events/open-source-summit-north-america with 
focus on the docker/moby-based options for edge clouds with NFV use cases.

Thanks,
Bryan Sullivan | AT

From: Christopher Price [mailto:christopher.pr...@ericsson.com]
Sent: Wednesday, August 09, 2017 10:23 AM
To: SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>>
Cc: Pasi Vaananen <pvaan...@redhat.com<mailto:pvaan...@redhat.com>>; Stephen 
Wong <stephen.wo...@huawei.com<mailto:stephen.wo...@huawei.com>>; Joel Halpern 
<joel.halp...@ericsson.com<mailto:joel.halp...@ericsson.com>>; Timon Sloane 
<ti...@opennetworking.org<mailto:ti...@opennetworking.org>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [Edge] Call to discuss next steps for Edge project proposal

Hey Bryan,

Related to this there's an event in California next month addressing the edge.  
http://www.opendevconf.com/

I think this would be an excellent forum to help develop content and 
architecture for anyone interested in this area.

/ Chris
Sent from my iPhone

On Aug 9, 2017, at 17:18, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi all,

As those who expressed interest in the Edge project proposal 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge I’d like to get us 
together with anyone else with interest in the project, to start planning OPNFV 
F release participation (with TSC approval of the project first of course).

Poll for meeting times: https://beta.doodle.com/poll/imqnb8cbm6zan9ia

It was mentioned on the OPNFV Marketing call today that the Marketing team 
plans to re-use the Beijing VCO demo content for further marketing of the 
concept. I commented that since we have the Edge project proposal on the table, 
I would recommend that the OPNFV technical community have a central role in the 
planning for future demos, e.g. through the Edge project. So we can use this 
call also to talk about next demo plans, and other things e.g. could we have 
anything ready for the December plugfest.

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] [Edge] Call to discuss next steps for Edge project proposal

[SULLIVAN, BRYAN L (BRYAN L)]

Well that event is solely focused on OpenStack. We will have representation 
there, but I think we need to set our sights wider. So I’ll be at the 
http://events.linuxfoundation.org/events/open-source-summit-north-america with 
focus on the docker/moby-based options for edge clouds with NFV use cases.

Thanks,
Bryan Sullivan | AT

From: Christopher Price [mailto:christopher.pr...@ericsson.com]
Sent: Wednesday, August 09, 2017 10:23 AM
To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com>
Cc: Pasi Vaananen <pvaan...@redhat.com>; Stephen Wong 
<stephen.wo...@huawei.com>; Joel Halpern <joel.halp...@ericsson.com>; Timon 
Sloane <ti...@opennetworking.org>; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [Edge] Call to discuss next steps for Edge project proposal

Hey Bryan,

Related to this there's an event in California next month addressing the edge.  
http://www.opendevconf.com/

I think this would be an excellent forum to help develop content and 
architecture for anyone interested in this area.

/ Chris
Sent from my iPhone

On Aug 9, 2017, at 17:18, SULLIVAN, BRYAN L (BRYAN L) 
<bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote:
Hi all,

As those who expressed interest in the Edge project proposal 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge I’d like to get us 
together with anyone else with interest in the project, to start planning OPNFV 
F release participation (with TSC approval of the project first of course).

Poll for meeting times: https://beta.doodle.com/poll/imqnb8cbm6zan9ia

It was mentioned on the OPNFV Marketing call today that the Marketing team 
plans to re-use the Beijing VCO demo content for further marketing of the 
concept. I commented that since we have the Edge project proposal on the table, 
I would recommend that the OPNFV technical community have a central role in the 
planning for future demos, e.g. through the Edge project. So we can use this 
call also to talk about next demo plans, and other things e.g. could we have 
anything ready for the December plugfest.

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] [Edge] Call to discuss next steps for Edge project proposal

[SULLIVAN, BRYAN L (BRYAN L)]

Hi all,

As those who expressed interest in the Edge project proposal 
https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge I'd like to get us 
together with anyone else with interest in the project, to start planning OPNFV 
F release participation (with TSC approval of the project first of course).

Poll for meeting times: https://beta.doodle.com/poll/imqnb8cbm6zan9ia

It was mentioned on the OPNFV Marketing call today that the Marketing team 
plans to re-use the Beijing VCO demo content for further marketing of the 
concept. I commented that since we have the Edge project proposal on the table, 
I would recommend that the OPNFV technical community have a central role in the 
planning for future demos, e.g. through the Edge project. So we can use this 
call also to talk about next demo plans, and other things e.g. could we have 
anything ready for the December plugfest.

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] [Auto] Seeking input to the Auto project creation review

[SULLIVAN, BRYAN L (BRYAN L)]

FYI I added a summary of the points below to the Auto project proposal at 
https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216

The Auto project supporters would like to get started ASAP on the project’s 
goals. While in principle I think the consensus is that a combined project 
(Opera+Auto) has some potential advantages, we would need to address the 
questions as noted on the wiki, as:

  *   The Opera project may not get re-started with the necessary resources to 
complete the Open-O to ONAP transition, or at least soon enough. The Auto 
project supporters would thus like to proceed with minimal (as possible) 
dependency upon the evolved Opera project plans in the F release.
  *   We may find that the technical approach to ONAP integration (e.g. how are 
the components deployed and integrated into tests) varies, for the different 
purposes of (1) deploying ONAP as a platform component on OPNFV PODs (Opera 
project scope), and (2) verifying specific ONAP component interop with OPNFV 
generic or scenario-specific features.

If we can’t resolve the key question here soon enough (what are the Opera 
project’s plans for the F release, e.g. who Is committed to support that work 
and is that enough for success), we may just delay efforts to get organized 
around the Auto projects’ goals for the F release.

I expect this to be a topic on this week’s TSC call (part of the creation 
review), and I request that anyone with an opinion on this (especially those 
that intend to support Auto or Opera in the F release) to provide input via 
this thread ahead of the call.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, August 03, 2017 8:19 AM
To: 'Yunxia Chen' ; 'Tina Tsou' 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [OPNFV confluence] Ulrich Kleber mentioned you on "Tc Agenda 
20170803"

Helen,

We had a discussion today on the takeaways from the call yesterday, to try to 
come to a broader consensus on the plan for how to achieve the Auto project’s 
proposed scope and the Opera project’s scope for F (ONAP integration). Here are 
the key questions I recommended we discuss over email before the TSC meeting:

  1.  As noted by Uli there may be a dependency of Auto on Opera. What Opera 
project resources (developers) will be available in F to complete the ONAP 
integration (the “ONAP integration team” as I refer to them below)?
 *   In Auto we had not planned to necessarily deploy ONAP as a complete 
platform, but rather if possible to deploy the components that are needed to 
test the interop use cases in Auto’s scope.
 *   If we find that approach (partial ONAP install) is infeasible/unable 
to meet our goals, we will depend upon a complete ONAP platform install 
instead, either through Opera or as described for the LaaS proposal integrating 
ONAP and OPNFV into a multi-lab testbed 
environment. In this case, 
who from the Opera team would be available to work with us on one of those 
approaches?
  2.  My overall recommendation is to keep the project overhead low, progress 
agile, and the approach flexible. Given ability to meet those goals, I don’t 
care where the work is done. Here are some questions that will help us in the 
decision per those goals:
 *   Can a combined project be organized as multiple, potentially loosely 
connected tracks?

   i.  We need 
regular project meetings in order to make rapid progress. Would the ONAP 
integration team prefer to have their own meetings? Although we know there was 
a lot of work done on Open-O integration, we don’t see a lot of record of those 
meetings on the wiki etc. That’s OK, if the team (e.g. led by Harry) can 
deliver ONAP integration without a lot of involvement from the Auto project 
team (mostly US based). We want people to work the way they need to, to be 
successful. But given that we would still need calls for the progress on Auto 
scope, would you have any concerns that we have at least two tracks in the 
combined project?

 *   Here is how I view the three (at least) distinct focuses in the 
overall project. These will likely require different developers with different 
skill sets. Who will be available to support the first two?

   i.  ONAP 
integration per current Opera: OPNFV installer support (if needed), or 
post-deploy install process (preferred)

 ii.  VNF use 
case integration into Functest etc, ala vIMS, vCPE, etc

   iii.  detailed 
functional interop test cases per the Auto proposal, using the Opera-installed 
ONAP, or discrete ONAP component install tools, or the cross-lab LaaS as above

 *   There will be multiple (in detail) ways to (1) deploy 

[opnfv-tech-discuss] [Auto] Seeking input to the Auto project creation review

[SULLIVAN, BRYAN L (BRYAN L)]

FYI I added a summary of the points below to the Auto project proposal at 
https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216

The Auto project supporters would like to get started ASAP on the project’s 
goals. While in principle I think the consensus is that a combined project 
(Opera+Auto) has some potential advantages, we would need to address the 
questions as noted on the wiki, as:

  *   The Opera project may not get re-started with the necessary resources to 
complete the Open-O to ONAP transition, or at least soon enough. The Auto 
project supporters would thus like to proceed with minimal (as possible) 
dependency upon the evolved Opera project plans in the F release.
  *   We may find that the technical approach to ONAP integration (e.g. how are 
the components deployed and integrated into tests) varies, for the different 
purposes of (1) deploying ONAP as a platform component on OPNFV PODs (Opera 
project scope), and (2) verifying specific ONAP component interop with OPNFV 
generic or scenario-specific features.

If we can’t resolve the key question here soon enough (what are the Opera 
project’s plans for the F release, e.g. who Is committed to support that work 
and is that enough for success), we may just delay efforts to get organized 
around the Auto projects’ goals for the F release.

I expect this to be a topic on this week’s TSC call (part of the creation 
review), and I request that anyone with an opinion on this (especially those 
that intend to support Auto or Opera in the F release) to provide input via 
this thread ahead of the call.

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L
Sent: Thursday, August 03, 2017 8:19 AM
To: 'Yunxia Chen' >; 'Tina 
Tsou' >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [OPNFV confluence] Ulrich Kleber mentioned you on "Tc Agenda 
20170803"

Helen,

We had a discussion today on the takeaways from the call yesterday, to try to 
come to a broader consensus on the plan for how to achieve the Auto project’s 
proposed scope and the Opera project’s scope for F (ONAP integration). Here are 
the key questions I recommended we discuss over email before the TSC meeting:

  1.  As noted by Uli there may be a dependency of Auto on Opera. What Opera 
project resources (developers) will be available in F to complete the ONAP 
integration (the “ONAP integration team” as I refer to them below)?
 *   In Auto we had not planned to necessarily deploy ONAP as a complete 
platform, but rather if possible to deploy the components that are needed to 
test the interop use cases in Auto’s scope.
 *   If we find that approach (partial ONAP install) is infeasible/unable 
to meet our goals, we will depend upon a complete ONAP platform install 
instead, either through Opera or as described for the LaaS proposal integrating 
ONAP and OPNFV into a multi-lab testbed 
environment. In this case, 
who from the Opera team would be available to work with us on one of those 
approaches?
  2.  My overall recommendation is to keep the project overhead low, progress 
agile, and the approach flexible. Given ability to meet those goals, I don’t 
care where the work is done. Here are some questions that will help us in the 
decision per those goals:
 *   Can a combined project be organized as multiple, potentially loosely 
connected tracks?

   i.  We need 
regular project meetings in order to make rapid progress. Would the ONAP 
integration team prefer to have their own meetings? Although we know there was 
a lot of work done on Open-O integration, we don’t see a lot of record of those 
meetings on the wiki etc. That’s OK, if the team (e.g. led by Harry) can 
deliver ONAP integration without a lot of involvement from the Auto project 
team (mostly US based). We want people to work the way they need to, to be 
successful. But given that we would still need calls for the progress on Auto 
scope, would you have any concerns that we have at least two tracks in the 
combined project?

 *   Here is how I view the three (at least) distinct focuses in the 
overall project. These will likely require different developers with different 
skill sets. Who will be available to support the first two?

   i.  ONAP 
integration per current Opera: OPNFV installer support (if needed), or 
post-deploy install process (preferred)

 ii.  VNF use 
case integration into Functest etc, ala vIMS, vCPE, etc

   iii.  detailed 
functional interop test cases per the Auto proposal, using the Opera-installed 
ONAP, or discrete ONAP component install