Re: [opnfv-tech-discuss] For the TSC composition discussion on Tuesday

[Raymond Paik]

Following-up on this as we didn't have sufficient time for discussion
during this week's TSC and we wanted to continue the conversation over
email.

For additional context, please look at notes that several community members
contributed to on this topic at
https://wiki.opnfv.org/display/DEV/TSC+composition+discussion

There was a strong consensus to move away from committers as constituents
for both nominations & voting in TSC elections.  That's how we arrived at
looking at several tools to identify "active contributors" (of code &
non-code) in OPNFV.  As I mentioned on the call, the proposal is for PTLs
to have an input on the active contributors list that is generated in case
people fall through the cracks.  No matter which metrics we chose, it's not
going to be perfect

Thanks,

Ray

On Sun, Feb 11, 2018 at 10:12 PM, 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)
>
>- Gerrit: 112
>- Git: 30
>- JIRA: 36
>- Wiki: 4
>
> If we go to 50 annual contributions, I don't necessarily think there'll be
> a significant increase in the pool and following is the breakdown.
>
>- Gerrit: 137
>- Git: 51
>- JIRA: 62
>- Wiki: 8
>
> Please feel free to reply with any thoughts or feedback.  This will be
> discussed further during the TSC call.
>
> 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] [vsperf] Agenda for VSPERF weekly meeting - 14 Feb 2018 (ww56)

[Rao, Sridhar]

Agenda


  1.  Development Update.
  2.  VSPERF architecture diagram review.
  3.  Review of past discussions
  4.  Next round of discussions proposal.

Meeting minutes

  *   WW55 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-02-07-15.59.html
  *   WW54 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-01-31-16.02.html
  *   WW53 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-01-24-16.00.html



Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (UTC/GMT -8)

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings


Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064





Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [onap-discuss] [integration] demo E2E testing & reporting follow-up

[Tina Tsou]

Dear all,

What’s the Zoom information?

6am PT Wednesday 02/14 right?

Happy Valentine’s!


Thank you,
Tina

On Feb 13, 2018, at 9:36 AM, 
"morgan.richo...@orange.com" 
> wrote:

Hi

I uploaded the slidedeck used for the demo
I added some screenshots 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_chain.pdf

I got the action point to organize a follow-up on this topic through another 
meeting

I am not sure I have the rights to book a zoom for an ad-hoc session (my 
personnal account allows only 40 minutes sessions)
I tried to ask the question on the IRC chan but it is not very active and I did 
not find any guideline on the wiki (could make sense to add one page).
@Gildas could you help me to book such slot? I could suggest tomorrow or 
Thursday 2h30 UTC (same time than the integration meeting)

Some open questions need LF helpdesks view (see slide "next steps").
BTW I created a ticket to ONAP heldesk on the 5th of February but did not get 
any feedback so far 
(https://rt.linuxfoundation.org/SelfService/Display.html?id=52001)
Did I miss something on the procedure regarding ONAP helpdesk?
Meanwhile I wondered if it would be possible to mutualize things if OPNFV 
community agrees (+Tim, Gabriel, Ray, Heather and Aric in CC)
The testresults.opnfv.org machine could be shared 
(everything is already there DB, dockers, mechanism to backup the DB) and a 
testresults.onap.org subdomain could be easily 
created (hopefully) and configured
The VM would not suffer...
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda1   75G 29G   47G  38% /
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ free -m
  totalusedfree  shared  buff/cache   available
Mem:   74803118 320 36840403451


/Morgan






Le mardi 13 février 2018 à 16:10 +, Tina Tsou a écrit :
Dear Morgan,

This is Tina Tsou, PTL of Auto Project. I was in Integration Project meeting 
just now. We are interested at your option #1 for the test API: integration 
OPNFV - ONAP.

Would you send the meeting invitation to opnfv-tech-discussion too? So Auto 
participants can join and learn from you.


Thank you,
Tina

On Feb 13, 2018, at 6:38 AM, Roger Maitland 
> wrote:

One clarification on OOM – it’s not a just a deployment tool, it manages the 
entire lifecycle of ONAP as shown in our logo.

Cheers,
Roger



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Tuesday, February 13, 2018 2:41 AM
To: bryan.sulli...@research.att.com; 
opnfv-tech-discuss@lists.opnfv.org
Cc: feng.xiao...@zte.com.cn; 
onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] [Auto] RE: [opnfv-tech-discuss] [integration] demo 
E2E testing & reporting next Tuesday?

Hi Bryan,

we can discuss it after the demo or offline
As far as I understand Auto is the equivalent of OOM, i.e. a deployment of ONAP 
based on kubernetes (but Auto is on OPNFV side) - do not hesitate to correct me 
if I am wrong
it would be possible to indicate Auto as 1 of the ONAP installer and collect 
the results of the tests
that is one of the interests to use the test API/Test DB independently from 
jenkins. Several CI chains can push results to provide an aggregate view of E2E 
Functional and later performance testing on ONAP.

and depending on the installer it is possible to customize the test list. For 
example if you have additional test cases through VES or Model projects.
/Morgan

Le vendredi 09 février 2018 à 16:54 +, SULLIVAN, BRYAN L (BRYAN L) a écrit :
Auto team,

FYI in case you have not seen this. Some of you may be collaborating with 
Morgan on the ONAP lab deployment, if not then perhaps there are some 
deployment tools you can leverage, or other ways that Orange can help the Auto 
project get off the ground with ONAP deployment for Auto use case 
development/testing.

For those cc’d who may not yet be aware of the Auto project: 
https://wiki.opnfv.org/pages/viewpage.action?pageId=12389095
Other OPNFV project focused on functional capability / use case testing which 
will support and leverage the OPNFV-ONAP integration through the Auto project 
include VES (https://wiki.opnfv.org/display/ves/VES+Home) and Models 
(https://wiki.opnfv.org/display/models/Models+Home).

Progress toward ONAP-OPNFV integration 

[opnfv-tech-discuss] [Doctor] Fraser issues

[Juvonen, Tomi (Nokia - FI/Espoo)]

OPNFV Fraser / OpenStack Pike-1 has problem with unstable nova migrations. 
After struggling this to get Doctor ONS demo working it came down to this bug:
https://bugs.launchpad.net/nova/+bug/1742827
So OPNFV Fraser / OpenStack Pike-1 can be fixed with this:
https://review.openstack.org/#/c/539005/1

Doctor APEX had problem that some sub process is hanging. There is now dirty 
fix just to get test cases passing:
https://gerrit.opnfv.org/gerrit/#/c/52075/1

Thanks,
Tomi

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

[opnfv-tech-discuss] [onap-discuss] [integration] demo E2E testing & reporting follow-up

[morgan.richomme]

Hi

I uploaded the slidedeck used for the demo
I added some screenshots 
https://wiki.onap.org/pages/viewpage.action?pageId=6593670=/6593670/25433913/integration_demo_E2E_chain.pdf

I got the action point to organize a follow-up on this topic through another 
meeting

I am not sure I have the rights to book a zoom for an ad-hoc session (my 
personnal account allows only 40 minutes sessions)
I tried to ask the question on the IRC chan but it is not very active and I did 
not find any guideline on the wiki (could make sense to add one page).
@Gildas could you help me to book such slot? I could suggest tomorrow or 
Thursday 2h30 UTC (same time than the integration meeting)

Some open questions need LF helpdesks view (see slide "next steps").
BTW I created a ticket to ONAP heldesk on the 5th of February but did not get 
any feedback so far 
(https://rt.linuxfoundation.org/SelfService/Display.html?id=52001)
Did I miss something on the procedure regarding ONAP helpdesk?
Meanwhile I wondered if it would be possible to mutualize things if OPNFV 
community agrees (+Tim, Gabriel, Ray, Heather and Aric in CC)
The testresults.opnfv.org machine could be shared (everything is already there 
DB, dockers, mechanism to backup the DB) and a testresults.onap.org subdomain 
could be easily created (hopefully) and configured
The VM would not suffer...
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda1   75G 29G   47G  38% /
[morgan@gce-opnfv-sandbox-fbrockners
 ~]$ free -m
  totalusedfree  shared  buff/cache   available
Mem:   74803118 320 36840403451


/Morgan






Le mardi 13 février 2018 à 16:10 +, Tina Tsou a écrit :
Dear Morgan,

This is Tina Tsou, PTL of Auto Project. I was in Integration Project meeting 
just now. We are interested at your option #1 for the test API: integration 
OPNFV - ONAP.

Would you send the meeting invitation to opnfv-tech-discussion too? So Auto 
participants can join and learn from you.


Thank you,
Tina

On Feb 13, 2018, at 6:38 AM, Roger Maitland 
> wrote:

One clarification on OOM – it’s not a just a deployment tool, it manages the 
entire lifecycle of ONAP as shown in our logo.

Cheers,
Roger



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Tuesday, February 13, 2018 2:41 AM
To: bryan.sulli...@research.att.com; 
opnfv-tech-discuss@lists.opnfv.org
Cc: feng.xiao...@zte.com.cn; 
onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] [Auto] RE: [opnfv-tech-discuss] [integration] demo 
E2E testing & reporting next Tuesday?

Hi Bryan,

we can discuss it after the demo or offline
As far as I understand Auto is the equivalent of OOM, i.e. a deployment of ONAP 
based on kubernetes (but Auto is on OPNFV side) - do not hesitate to correct me 
if I am wrong
it would be possible to indicate Auto as 1 of the ONAP installer and collect 
the results of the tests
that is one of the interests to use the test API/Test DB independently from 
jenkins. Several CI chains can push results to provide an aggregate view of E2E 
Functional and later performance testing on ONAP.

and depending on the installer it is possible to customize the test list. For 
example if you have additional test cases through VES or Model projects.
/Morgan

Le vendredi 09 février 2018 à 16:54 +, SULLIVAN, BRYAN L (BRYAN L) a écrit :
Auto team,

FYI in case you have not seen this. Some of you may be collaborating with 
Morgan on the ONAP lab deployment, if not then perhaps there are some 
deployment tools you can leverage, or other ways that Orange can help the Auto 
project get off the ground with ONAP deployment for Auto use case 
development/testing.

For those cc’d who may not yet be aware of the Auto project: 
https://wiki.opnfv.org/pages/viewpage.action?pageId=12389095
Other OPNFV project focused on functional capability / use case testing which 
will support and leverage the OPNFV-ONAP integration through the Auto project 
include VES (https://wiki.opnfv.org/display/ves/VES+Home) and Models 
(https://wiki.opnfv.org/display/models/Models+Home).

Progress toward ONAP-OPNFV integration will also support the OPNFV Lab As A 
Service (LaaS) use cases shown at 
https://wiki.opnfv.org/display/INF/Lab+as+a+Service, which will enable ONAP 
developers to access OPNFV deployed VIM/NFVI environments (and vice versa). 
This and other work in the Models project above will help setup a diverse 
VIM/NFVI environment for supporting 

[opnfv-tech-discuss] Update for Weekly Technical Discussion this Thursday Feb 15

[HU, BIN]

Hello community,

Because of the Chinese New Year in a couple of days, our folks in China will be 
on holidays for 2 weeks. Thus our original agenda item this week "Status Update 
of PDF/IDF Maturity (Julien and 
Alexandru Avadanii)" needs 
to be pushed back to March 1st.

Thus the only potential agenda item is the "Lightning Talk" this week. However, 
I didn't see any project signedup yet.

If your project is interested in giving a lightning talk, please sign up, and 
the time slots are quite open this week Feb 15.

If there is no signups of lightning talk or other agenda item, we will have to 
cancel it this week.

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

[opnfv-tech-discuss] [Auto] Re: ONAP integration with OPNFV progress

[Tina Tsou]

Thanks for the pointers, Song.


Thank you,
Tina

On Feb 13, 2018, at 3:15 AM, Song Zhu 
> wrote:

Hi Gerard,

Below document (not merged yet) describes K8s deployment on Arm with Compass 
installer. Note that it deploys container on VM. The deployment of containers 
on Bare metal is similar but the document is not ready yet.

https://gerrit.opnfv.org/gerrit/#/c/49717/2/docs/release/installation/k8s-deploy-arm.rst

To clarification, we didn’t bring up a containerized version of ONAP on K8S. We 
have been focusing on bring up K8s NFV infrastructure with data plane 
acceleration (DPDK, VPP) as described below. We haven’t done any work on ONAP 
before.
http://artifacts.opnfv.org/container4nfv/review/46463/arm/index.html

Thank you,
Song

From: Tina Tsou
Sent: Tuesday, February 13, 2018 2:24 PM
To: gerard.d...@wipro.com
Cc: Song Zhu >; 
eric.dm...@wipro.com
Subject: Re: ONAP integration with OPNFV progress

Dear Gerard,

Thanks for catching it.

Better to have meeting before Harry goes for Chinese New Year long vacation. 
Sooner than later...

Thank you,
Tina

On Feb 12, 2018, at 9:25 PM, 
"gerard.d...@wipro.com" 
> wrote:


Hi all,

Quick notes, please add/modify as needed:

- overview of test framework analysis, with transversal organization proposal 
(specialize in use case definition independently of implementation, and 
specialize in use case implementation); this should increase the team's output;

- overview of data structure (as defined in Resilience Improvements Use Case), 
with cross pointers to manager/VNF/cloud/resources

(check 2 slide decks at https://wiki.opnfv.org/display/AUTO/Auto+Test+Framework)

- identified a need to unify/align tools used to implement use cases. Gerard to 
organize a meeting between Harry, Mohan, Eric and Gerard, to select a similar 
environment (e.g., Pramod was using Python with PyCharm (from JetBrains), 
leveraging Django); most of the environment should be the same; the only 
difference is the APIs (should be polymorphic: "stop compute resource" would be 
the logic in the main body, and would call a different implementation for 
OpenStack and for K8S; i.e., don't hard-code API calls in test body).

 - keep doing simultaneously the top-down work (specify use cases, detail them 
logically, then implement scripts) and the bottom-up (bring up environments, 
install ONAP on OpenStack and K8S, at least ONAP/OS on ARM pod and ONAP/K8S on 
x86, but ideally also ONAP/K8S on ARM and ONAP/OS on x86 pod (so, 4 cases of 
ONAP//).

- for installations, make sure the steps/process are documented, as 
installation scripts (for repeatability)

- use MCP and Compass for installations (MCP can't support K8S for now)

- there is a ARM team in Shanghai that has brought up a containerized version 
of ONAP on K8S: maybe they can support Auto (contact via Song)

- next-step VNFs and Use Cases: to be discussed; might be vIMS (ClearWater), 
but preference for more Edge Cloud use cases, and more vCPEs. Look into SNORT 
(open-source IDS/IPS). OpenWRT is too residential-oriented, not really for 
Enterprise use cases.


BR,
Gerard





From: Tina Tsou
Sent: Monday, February 12, 2018 1:20 PM
To: Tina Tsou; Song Zhu; Eric DMaye (Product Engineering Service); Gerard Damm 
(Product Engineering Service)
Subject: ONAP integration with OPNFV progress
When: Monday, February 12, 2018 7:30 PM-8:00 PM.
Where: WebEx


** This mail has been sent from an external source. Treat hyperlinks and 
attachments in this email with caution**

-- Do not delete or change any of the following text. --


Join WebEx 
meeting
Meeting number (access code): 806 240 531
Meeting password: kpGsMiFb


Join by phone
1-408-792-6300 Call-in toll number (US/Canada)
1-877-668-4490 Call-in toll-free number (US/Canada)
Global call-in 
numbers
 | Toll-free calling 
restrictions

Can't join the meeting?

If you are a host, go 
here
 to view host information.

IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
information sent during the session to be recorded, which may be discoverable 
in a legal matter. By joining this session, you automatically consent to such 
recordings. If you do not consent to being recorded, discuss your concerns with 
the host or do not join the session.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended 

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

[Luke Hinds]

Top post with an example using the Virus Total API:

> anteater --bincheck --project testproject --path
/home/luke/repos/personal/anteater/tests/testproject

2018-02-13 14:49:18,349 - anteater.src.get_lists - INFO - Loaded
testproject specific file_audits entries
2018-02-13 14:49:18,352 - anteater.src.get_lists - INFO - Loaded
testproject specific file_contents entries
2018-02-13 14:49:18,375 - anteater.src.project_scan - INFO - Non
Whitelisted Binary file:
/home/luke/repos/personal/anteater/tests/testproject/images/pal.png
2018-02-13 14:49:18,376 - anteater.src.project_scan - INFO - Performing
Scan: /home/luke/repos/personal/anteater/tests/testproject/images/pal.png
2018-02-13 14:49:18,824 - anteater.src.project_scan - INFO - File last
scanned and shown as clean on:, 2018-02-13 13:44:11
2018-02-13 14:49:18,825 - anteater.src.project_scan - INFO - Full report
here:
https://www.virustotal.com/file/a71e13ebeb2500ed20781ab3ae8a9b306cf69a6c8be9a31e96d4e04f1657b4d8/analysis/1518529451

2018-02-13 14:49:18,825 - anteater.src.project_scan - INFO - The following
sha256 hash can be used in your testproject.yaml file:
a71e13ebeb2500ed20781ab3ae8a9b306cf69a6c8be9a31e96d4e04f1657b4d8

Should have the URL / Domain / IP stuff working later in the week.


On Tue, Feb 13, 2018 at 9:41 AM, Luke Hinds  wrote:

>
>
> On Tue, Feb 13, 2018 at 12:17 AM, SULLIVAN, BRYAN L (BRYAN L) <
> bryan.sulli...@research.att.com> wrote:
>
>> 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) 
>> *Cc:* opnfv-tech-discuss@lists.opnfv.org; degirmenci, fatih <
>> fatih.degirme...@ericsson.com>; Raymond Paik 
>> *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> 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
>> 
>> ”, which is the wiki page https://wiki.opnfv.org/pages/v
>> iewpage.action?pageId=11700198
>> ,
>> 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
>> 
>>  repository.” – but that link (releng-anteater
>> )
>> 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/
>> 

Re: [opnfv-tech-discuss] [Auto] URL to access ONAP portal

[Joe Kidder]

Thanks Harry!
I ran across a mention (at 
https://wiki.onap.org/display/DW/Tutorial%3A+Accessing+the+ONAP+Portal) of 
adding these names to /etc/hosts this morning just before opening your email.

Joe
> On Feb 12, 2018, at 11:25 PM, huangxiangyu  wrote:
> 
> Joe
>  
> Containers have their internal IPs. In the /etc/hosts there are some name 
> resolving to let you find the internal addresses of domains like 
> portal.api.simpledemo.onap.org .
>  
> Regards
> Harry
>  
> 发件人: Joe Kidder [mailto:joe.kid...@5thlayer.com] 
> 发送时间: 2018年2月13日 10:21
> 收件人: huangxiangyu 
> 抄送: Tina Tsou ; opnfv-tech-discuss@lists.opnfv.org
> 主题: Re: [opnfv-tech-discuss] [Auto] URL to access ONAP portal
>  
> Thanks, Harry.
>  
> I’m confused, however.  This browser page points to 
> http://portal.api.simpledemo.onap.org:8989 
> .
> Shouldn’t I be connecting to a local IP address of the ONAP portal running on 
> 10.10.30.157?
>  
> Thanks,
> Joe
> On Feb 12, 2018, at 9:03 PM, huangxiangyu  > wrote:
>  
> Hi Joe
>  
> Here‘s the link to access ONAP portal built in pod1 of UNH Laas lab:
> http://10.10.30.157:30211 
> You will see a noVNC login page, password is “password”, then you will see a 
> desktop and I already opened the browser so you should find the main page of 
> ONAP portal just there.
>  
> This ONAP on Kubernetes is not connected to an OpenStack yet so I think most 
> likely we have to tear down this ONAP and redeploy it when there is a VIM 
> ready to be connected.
> Sorry Gokul, I didn’t get your email address. Joe or Tina, can you help to 
> add Gokul to this loop? thanks.
> I will be on Chinese new year vacation during 2.14 to 2.22 but I will check 
> the mail time to time, we can keep discussion on this thread.
>  
> Regards
> Harry

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

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

[Luke Hinds]

On Tue, Feb 13, 2018 at 12:17 AM, SULLIVAN, BRYAN L (BRYAN L) <
bryan.sulli...@research.att.com> wrote:

> 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) 
> *Cc:* opnfv-tech-discuss@lists.opnfv.org; degirmenci, fatih <
> fatih.degirme...@ericsson.com>; Raymond Paik 
> *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> 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
> 
> ”, which is the wiki page https://wiki.opnfv.org/pages/v
> iewpage.action?pageId=11700198
> ,
> 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
> 
>  repository.” – but that link (releng-anteater
> )
> 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/
> 
>
> [bryan] Are you going to start hosting these docs at docs.opnfv.org?
>
We can do yes, although I guess it make sense to have the main body of the
documentation around the tool upstream (once the github re-homing happens),
and then have everything OPNFV developers need to know about how anteater
is used in OPNFV at docs.opnfv.org - this way there won't be materials in
docs.opnfv.org around using Travis CI (which would confuse people).

> 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/relen
> g-anteater/blob/master/exceptions/calipso.yaml#L9
> 
>
>* 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?
>
Its pretty much the epicentre of community 

[opnfv-tech-discuss] [Compass] meeting arrange during Chinese New Year

[Chigang (Justin)]

Hi guys,

Chinese New year is nearly coming, so I want to cancel the Compass weekly 
meeting in next weeks(Feb 14, Feb 21),
Regarding to Compass integration discussion meeting,  it is canceled in Feb 15. 
Because I am still on vacation in Feb 22, Yifei Xue will chair the meeting at 
Feb 22.
It is an important period for Fraser delivery in next couple weeks, so if there 
is something critical, please mail me or ping me in #opnfv-compass4nfv, I will 
check mail and irc for each day.

Thanks Yifei for chairing the next discussion meeting.
Happy new year for Chinese guys! Enjoy your vacations.

Regards
Justin

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