[opnfv-tech-discuss] [Functest] Features test cases status

[Suse]

Hi,

This mail is addressed mainly to PTLs from Feature projects that are 
integrating tests in Functest. 

If you take a look at [1], you will see a summary of the current status of the 
tests cases from feature projects. Please take a look and let us know if there 
is something wrong or not up to date.

Although most of the tests are running in CI with the new Alpine containers, 
many of them are still failing. We are still in the bugfix phase, but if the 
failure persists until the release date, the reasons should be documented in 
the release notes.

Thank you,
Jose
 
[1] 
https://wiki.opnfv.org/display/functest/Functest+feature+integration+status#Functestfeatureintegrationstatus-Features
 
___
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] Poll for 2018 OPNFV release names

[Raymond Paik]

A quick reminder for people who have not participated in the poll for
release names.

Please cast your votes at https://www.surveymonkey.com/r/VT3T37S

Thanks,

Ray

On Sun, Sep 17, 2017 at 10:03 PM, Raymond Paik 
wrote:

> All,
>
> Thanks for your ideas for F & G release names.  I locked the wiki page
>  and
> removed a couple of candidates.  First, I removed Fenhe (in China) so that
> we don't repeat an Asian river after Euphrates.  For the G-release, I
> removed Guarapo (in Brazil) in case a South American river is chosen for
> the F-release.
>
> So this leaves us with 13 candidate for the F-release and 4 candidates for
> the G-release.  To take the poll for 2018 release names, please go to
> https://www.surveymonkey.com/r/VT3T37S
>
> The poll will remain open until 5pm Pacific Time on September 24th
> (Sunday).
>
> Cheers,
>
> 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] [infra] [pharos] Splitting up the Pharos Repo

[Jack Morgan]

  
  
Trevor,
Go ahead with Pharos repo slit per the following structure.
thanks
 pharos
    - INFO
    - config
    - pdf/pod1.yaml
    - installers
  - utils 
  
pharos-tools
  - lass-fog
  - dashboard
  - validator


On 09/21/2017 01:09 AM, Julien wrote:


  
  +1, PDF is better than template.


in the future, this file will be evolved into a pdf yaml
  schema file. It can be directly used to verify the content in
  PDF.


  
  
  
Jack Morgan 于2017年9月20日周三
  下午9:17写道：


  
Thanks Julien for feedback. I made one small
suggestions below, what do you think? thanks

  
   
On
  09/19/2017 10:52 PM, Julien wrote:


  Hi Trevor,


Thanks for following these changes in pharos.
Agree to merge LaaS and PDF changes.


some comments:


 pharos
    - INFO
    - config
      - pod1.yaml    
      ==> /template/pod1.yaml

  

  
   can we use pdf instead
of template? config/pdf/pod1.yaml
  

  
    - installers
      - utils
  
   pharos-tools
    - lass-fog        
         ==> laas
    - pharos-dashboard
==> dashboard
    - pharos-validator 
    ==> validator



BR/Julien
  
  
  
Trevor Bramwell 于2017年9月20日周三
  上午6:37写道：

Hi
  All,
  
  Yesterday in the Infra-WG we discussed[1] splitting up
  the Pharos
  repository due to it's growing size. Jack and I
  discussed further how
  he'd like the repo split up and I wanted to share with
  you our plans,
  most of which will start tomorrow:
  
   * Merging Peter's[2] patchsets for LaaS
  
   * Merging Alex patchsets to move the PDF generator[3]
  work out of
      securedlab and add pharos as a submodule of
  securedlab[4].
  
   * Splitting out the pharos tools directory into it's
  own repo
      pharos-tools using git-filter-branch:
  
        git filter-branch -d pharos --tag-name-filter
  cat --subdirectory-filter tools -- --all
  
   * Updating the pharos git repository to remove the
  tools directory and
      gitobjects created by those commits.
  
   * Updating any related Jenkins jobs.
  
  The new structure of the repos would look like this:
  
   pharos
    - INFO
    - config
      - pod1.yaml
      - installers
      - utils
  
   pharos-tools
    - lass-fog
    - pharos-dashboard
    - pharos-validator
  
  
  If anything doesn't line up with what we talked about
  Jack, please
  correct me!
  
  Regards,
  Trevor bramwell
  
  [1] http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-18-15.02.html
  [2] https://gerrit.opnfv.org/gerrit/#/q/owner:%22Parker+Berberian%22+status:open
  [3] https://gerrit.opnfv.org/gerrit/#/q/status:open+project:pharos+branch:master+topic:copy-pdf-from-securedlab
  [4] https://gerrit.opnfv.org/gerrit/#/q/status:open+project:securedlab+branch:master+topic:use-pharos-pdf
  ___

  

  

  


-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

[opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday September 21

[HU, BIN]

Hello community,



Thank you all for attending the technical discussion today.



Today, we continued the discussion of the CD-Friendly Release Model based on 
XCI<https://wiki.opnfv.org/download/attachments/12390139/OPNFV_ReleaseModelProposal.pdf?version=2modificationDate=150485449api=v2>
 driven by Fatih Degirmenci<https://wiki.opnfv.org/display/~fdegir>. Group 
agreed that XCI is the right way to go, and benefits the whole OPNFV community 
by bringing it to TSC for approval. So group agreed to the plan that Fatih 
presented, i.e. TSC approval on Oct 10 and kick off the  effort on Oct 10. 
Fatih will have another discussion with test teams on Thursday next week, and 
will come back with the revised proposal if any, which will be the final 
version to TSC, in a couple of weeks if needed.



We also discussed Graduation Review of Doctor 
Project<https://wiki.opnfv.org/download/attachments/2925877/OPNFV%20Doctor%20graduation%20proposal.pdf?version=1=1505994198784=v2>
 by Ryota Mibu<https://wiki.opnfv.org/display/~r-mibu>. There was one comment 
regarding future plan, and Ryota will add one more slide on the future plan. We 
will continue the discussion on mailing list, and hopefully to bring it to TSC 
directly.



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



Thanks

Bin



[1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20170921

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

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

[opnfv-tech-discuss] [dovetail] Project weekly meeting agenda 9/22

[Wenjing Chu]

Hi Dovetailers

With TSC's approval of the test scope and cvp process, our focus for the
next week or so should be meeting the beta start milestone, plus review of
branching scheme.

- Review of status: revision 0.7.0, web portal, remaining doc related tasks
(xudan/leo)
- Doc publication (Georg)
- Beta process and logistics of organizing and supporting beta tests
- Review dovetail branching scheme, support-ability

We'll probably not able to cover any more topics, but jira ticket cleanup
is still in the backlog.
Thanks.

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

[opnfv-tech-discuss] [barometer] Update

[Tahhan, Maryam]

Hi folks

[barometer] Update 



Actions:

* Maryam or team to create a wiki on the collectd VES application

* Maryam to review/help out with Al's definitions.

* Al to look at LLC definition --> Done but clarification needed on 
whether it is Kilobytes/Kibibytes.  ACTION Maryam to follow up



Dev updates: 
https://wiki.opnfv.org/display/fastpath/Barometer+Development+Updates



Functest update:

* issues since move to new model of split containers in functest.

* some JIRA bugs have been filed with functest.

* Emma has posted some patches to fix the long term testing issues encountered 
with Gnocchi



IFA027:

* Network Functions Virtualization (NFV) Release 2; Management and 
Orchestration; Performance Measurements Specification Perf. Measurements Spec

* Specify the performance measurements (i.e. performance metrics, performance 
values) and use cases for descriptors and interfaces, including Or-Vnfm 
reference point, Ve-Vnfm reference point, Vi-Vnfm reference point, Or-Vi 
reference point, and Os-Ma-nfvo reference point, based on the performance 
metrics collected from NFVI.

* References TST008

* 
https://docbox.etsi.org/isg/nfv/open/drafts/IFA027_Perf_Measurements_Spec/NFV-IFA027v050.zip

* Not looking at adding new metrics that go beyond the scope of past standard.

* Need to add a clarification note to TST008 about memory used as it's directly 
referenced by this doc.





Runtime analysis: 
https://wiki.opnfv.org/display/fastpath/Runtime+analysis+of+the+monitoring+agents+methodology





Please let me know if you have any questions or comments.

BR
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] Opening the nomination period for the TSC Chair election

[Tapio Tallgren]

I would like to nominate myself as a candidate in the OPNFV TSC Chair election.

I started as the TSC Chair in Fall 2016. Since then, OPNFV has gotten
both wider and deeper: wider since it now includes a storage project and
an ONAP integration project. Deeper since the testing projects have
increased their coverage, the C program is starting a beta test, and
OPNFV is testing OpenStack on a continuous basis. These are of course
just examples of the great work that the community has done.

Going forward, the biggest tasks ahead of OPNFV that the TSC has to
work on include the conclusion of the C technical work, improving the
usability of the OPNFV installers, and working together especially the
ONAP community. We need to make OPNFV easy to use for newcomers and
experienced users. This requires e.g improving the pod and scenario
description documents, better documentation, and perhaps enabling virtual
deployments. Personally, I have started working in the XCI project and
it is great fun to see a little OPNFV cluster running in virtual
machines on a single server. This is an experience I would like more
people to share.


___
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] [pharos] Splitting up the Pharos Repo

[Julien]

+1, PDF is better than template.

in the future, this file will be evolved into a pdf yaml schema file. It
can be directly used to verify the content in PDF.


Jack Morgan 于2017年9月20日周三 下午9:17写道：

> Thanks Julien for feedback. I made one small suggestions below, what do
> you think? thanks
>
> On 09/19/2017 10:52 PM, Julien wrote:
>
> Hi Trevor,
>
> Thanks for following these changes in pharos.
> Agree to merge LaaS and PDF changes.
>
> some comments:
>
>  pharos
>   - INFO
>   - config
> - pod1.yaml   ==> /template/pod1.yaml
>
> can we use pdf instead of template? config/pdf/pod1.yaml
>
> - installers
> - utils
>
>  pharos-tools
>   - lass-fog  ==> laas
>   - pharos-dashboard ==> dashboard
>   - pharos-validator==> validator
>
> BR/Julien
>
> Trevor Bramwell 于2017年9月20日周三 上午6:37写道：
>
>> Hi All,
>>
>> Yesterday in the Infra-WG we discussed[1] splitting up the Pharos
>> repository due to it's growing size. Jack and I discussed further how
>> he'd like the repo split up and I wanted to share with you our plans,
>> most of which will start tomorrow:
>>
>>  * Merging Peter's[2] patchsets for LaaS
>>
>>  * Merging Alex patchsets to move the PDF generator[3] work out of
>> securedlab and add pharos as a submodule of securedlab[4].
>>
>>  * Splitting out the pharos tools directory into it's own repo
>> pharos-tools using git-filter-branch:
>>
>>   git filter-branch -d pharos --tag-name-filter cat
>> --subdirectory-filter tools -- --all
>>
>>  * Updating the pharos git repository to remove the tools directory and
>> gitobjects created by those commits.
>>
>>  * Updating any related Jenkins jobs.
>>
>> The new structure of the repos would look like this:
>>
>>  pharos
>>   - INFO
>>   - config
>> - pod1.yaml
>> - installers
>> - utils
>>
>>  pharos-tools
>>   - lass-fog
>>   - pharos-dashboard
>>   - pharos-validator
>>
>>
>> If anything doesn't line up with what we talked about Jack, please
>> correct me!
>>
>> Regards,
>> Trevor bramwell
>>
>> [1]
>> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-18-15.02.html
>> [2]
>> https://gerrit.opnfv.org/gerrit/#/q/owner:%22Parker+Berberian%22+status:open
>> [3]
>> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:pharos+branch:master+topic:copy-pdf-from-securedlab
>> [4]
>> https://gerrit.opnfv.org/gerrit/#/q/status:open+project:securedlab+branch:master+topic:use-pharos-pdf
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
>
>
> ___
> opnfv-tech-discuss mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
> --
> 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
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] XCI Meeting Minutes - September 20th

[Fatih Degirmenci]

Hi,

Meeting minutes are available on 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-09-20-13.00.txt
 
/Fatih

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