Re: [opnfv-tech-discuss] [opnfv-tsc] TSC Meeting Artifacts

[Manuel Buil]

Hello,

If we move to IRC-only meetings we will not able able to present slides or 
share documents and talk about them, right?. Would there be a way to fill this 
gap?

If we post the recording, does that mean that there will not be any MoMs 
anymore (in written format)?

Regards,
Manuel

From: opnfv-...@lists.opnfv.org  on behalf of Mark 
Beierl via Lists.Opnfv.Org 
Sent: Wednesday, October 9, 2019 2:26 PM
To: opnfv-tech-discuss@lists.opnfv.org 
Cc: opnfv-...@lists.opnfv.org 
Subject: Re: [opnfv-tsc] TSC Meeting Artifacts


Expanding to include the broader community.



We are seeking feedback on what level of information capture the TSC should 
provide.  This has been a discussion that has been going on for a while now, so 
please give this your prompt attention.



Regards,

Mark



From:  on behalf of "Mark Beierl via 
Lists.Opnfv.Org" 
Reply-To: Mark Beierl 
Date: Wednesday, October 2, 2019 at 10:35
To: "opnfv-...@lists.opnfv.org" 
Cc: "opnfv-...@lists.opnfv.org" 
Subject: [opnfv-tsc] TSC Meeting Artifacts



Hello, all.



There has been some discussion about improving the accuracy of how we capture 
discussions in the TSC meeting.  Right now the only official record is the IRC 
meetbot logs, which requires that there is a note taker who can effectively 
transcribe all that discussions from the audio portion of the Zoom bridge into 
IRC.  In addition to that, any presentations must also be posted via #link, and 
if they are not yet available, that information might be lost.



I think now is a time to open the discussion about how we as a community want 
to share the full content of our TSC meetings.  Some options are listed below:



  *   Record the Zoom meeting and post the recording as part of the official 
record
  *   Remove the Zoom portion and move to a pure IRC only meeting



There are advantages as disadvantages to both, so please reply with your 
comments.



Also, should this discussion be expanded to include the whole community to 
ensure we are meeting their requests for transparency?



Regards,

Mark Beierl
Telco Innovation Staff Solution Architect

mbei...@vmware.com

[VMware]


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

View/Reply Online (#23631): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23631
Mute This Topic: https://lists.opnfv.org/mt/34462569/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] Process Overview - How to Bring a Project into OPNFV

[Manuel Buil]

Hi TSC,

First of all, thanks Bin for the description. I personally did not know how 
this meeting got created.

I think we can all agree that currently the only way for new projects to get 
the stamp "you have community consensus" is through the decision of the weekly 
technical discussion. Therefore, projects must go to the weekly technical 
discussion and get the approval from it to reach the next level, the TSC. I see 
some potential improvements in this process because there are some problems 
that I personally see:

  *   We have a geographically widespread community. The time for this meeting 
is never good for everyone and most of the times not even half of the TSC 
participates, thus I don't think this meeting is a good way to measure the 
"community consensus" because we are indirectly excluding TSC members and other 
community members and we would like to hear their opinions too, right?
  *   Even if the project has been up for review in the wiki for 2 weeks, most 
of the opinions, feedback, reviews are first time raised in that meeting and 
not in the comments of the wiki. Therefore, most of the times, there is not 
time to confront the points raised thus delaying everything
  *   Things can only move once a week, when this meeting takes place. This 
adds an extra delay which could be avoided, or?. Let alone holidays, etc.
  *   Non native speakers might have difficulties to respond to feedback, 
especially when comments are not raised before the meeting
  *   How the meeting decides if a project gets the approval is not clearly 
settled. Currently, we don't vote and if there are no further questions, the 
moderator of the meeting decides that the project is good to go to the TSC.

I'd like to suggest a new way for this which I think servers better the purpose 
of "foster community review and fulfill the metric of “Proposal has been 
socialized with potentially interested or affected projects and/or parties”".

Actually I have two similar alternatives, just the tool changes:

## Alternative 1 ## (preferred)

Upload the proposal to github (or gerrit or gitlab) and then allow TSC members 
to comment on this and do the reviews online. Same procedure that CNTT is 
following for its documents and a very common procedure in other open source 
communities. We give 2 weeks and during that time TSC members must write their 
concerns, questions, feedback, etc in the comments. Our PM or the person 
proposing the project should actively take care of reminding it to the TSC 
members, this way we will hopefully get reviews from the whole TSC. Things 
could be of course delayed in case of need, e.g. a TSC person is on vacation, 
comments were not addressed, etc... but in general, after 2 weeks, the project 
is voted in the TSC and everyone had a chance to review it and raise concerns.

## Alternative 2 ##

Same as alternative 1 but uploading it to the wiki instead of github and review 
the proposal in the comments.

The benefits I see:

  *   Everyone in the TSC can participate in the review 24h a day, 7 days a week
  *   We get opinions and comments from most of the TSC thus reaching what we 
want: "community consensus"
  *   The person proposing the project will have space to think about the 
concerns and reviews that were raised
  *   This eases a lot the participation of non-native speakers
  *   The project could still go and present in the weekly technical discussion 
and of course clarify comments that were raised.  However, the decision that it 
has community consensus will be made by checking that TSC members reviewed it 
and are fine with it
  *   From process perspective, I think this is clearer and it scales better

What you guys think? Any feedback is welcome!

Regards,
Manuel


From: opnfv-...@lists.opnfv.org  on behalf of HU, 
BIN 
Sent: Sunday, August 25, 2019 6:54 AM
To: opnfv-tech-discuss@lists.opnfv.org ; 
opnfv-...@lists.opnfv.org 
Subject: [opnfv-tsc] Process Overview - How to Bring a Project into OPNFV


Hello community,



Fresh blood is joining us. New project proposals are coming. I want to take 
this opportunity to give an overview of the process of bringing a project to 
OPNFV.



  1.  History of Process



General Project Lifecycle is documented in [1]. Project promotion, and 
demotion, across states can only be done by TSC review and voting. During the 
reviews, the candidate projects are evaluated based on predefined metrics and 
KPIs. The target numbers may vary for the different levels. In order for 
creation review in TSC, proposals need to be emailed to TSC mailing list, and 
posted for two weeks. Various review criteria are available in [1].



In practice, after OPNFV was founded, we started to discuss new project 
proposals in TSC meeting on 10/21/2014 [1]. TSC spent 2 hours to discuss 
several projects. None could be agreed. TSC realized that a separate community 
discussion was needed to discuss project proposals, help proposals get 

Re: [opnfv-tech-discuss] [opnfv-tsc] Can installers use CircleCI?

[Manuel Buil]

Hello Trevor,

Cool! Thanks.

If you want we work together to try to understand why it fails for XCI. That 
way we will probably find gaps.

Note that you are doing a "virtual" deployment, where controller and computes 
are in VMs. When you were reading the documentation, did you find a way to 
deploy baremetal?

Thanks,
Manuel


From: opnfv-...@lists.opnfv.org  on behalf of Trevor 
Bramwell 
Sent: Tuesday, July 30, 2019 12:10 AM
To: Manuel Buil 
Cc: ahot...@cisco.com ; opnfv-tech-discuss@lists.opnfv.org 
; opnfv-...@lists.opnfv.org 

Subject: Re: [opnfv-tsc] Can installers use CircleCI?

Hi Manuel, Alec, et al.

I finished up a guide[1] for setting up repos on CircleCI, Gitlab-CI,
and Azure Pipelines for testing these proof-of-concepts (PoCs).

Hopefully this will help anyone who has the cycles to dig into these
platforms and find if they'll meet our needs.

It was pretty easy to get a machine from LaaS connected up the Gitlab-CI
and attempt to run XCI[2] (though I've yet to successfully deploy it),
and I don't think I'll have any issues trying to connect it to Azure
Pipelines. From what I know of CircleCI it will take a bit more work
though as it can only SSH out, and that would require first setting up
the VPN connection.

Regards,
Trevor Bramwell

[1] https://wiki.opnfv.org/display/INF/PoC+Setup
[2] https://gitlab.com/bramweltci/releng-xci/pipelines

On Tue, Jul 09, 2019 at 04:49:42PM +0000, Manuel Buil wrote:
> Thanks for sharing the details Alec. It sounds like an interesting PoC and 
> will give us a lot of insights .
>
> I also think those baremetal features will be hard to get but that needs to 
> be investigated. By your information, I am also realizing that multi-distro 
> is not supported and we are tight to the images they offer, which are not 
> that many, just ubuntu-1604. For example, by looking at Airship's CI, they 
> use ubuntu-1804 for OpenStack Stein or later, so we would not be able to 
> deploy it in CircleCI. Not sure how much influence we could have over 
> CircleCI to get multi-distro support .
>
>
> Regards,
> Manuel
> 
> From: opnfv-...@lists.opnfv.org  on behalf of Alec 
> via Lists.Opnfv.Org 
> Sent: Tuesday, July 9, 2019 5:53 PM
> To: Manuel Buil
> Cc: opnfv-...@lists.opnfv.org
> Subject: Re: [opnfv-tsc] Can installers use CircleCI?
>
>
> Hi Manuel,
>
>
>
> I doubt circleci can do any of the features you describe below other than 
> perhaps nested virtualization (VM in VM).
>
> Circle ci is great to build software and do unit testing of it, what you need 
> for the below is a bare metal cloud such as packet.net or OPNFV LaaS.
>
> You can chose between a few flavors of VMs or docker containers to run your 
> workload (https://circleci.com/docs/2.0/configuration-reference/#machine)
>
> I don’t see how they can provide anything closer to bare metal.
>
>
>
> I am planning to test circleci to do the following with nfvbench:
>
>   *   Build VM images and push them to a VM image repo
>   *   Build docker containers and push them to docker hub
>
> Unit testing that does not require any HW dependencies
>
> Nothing really extraordinary…
>
> My project is a good example of tool that is highly dependent on NIC hardware 
> and kernel settings. If I can’t control those by API I’m pretty much limited 
> to SW unit testing.
>
>
>
> The only way to test an installer is to run it on a set of “friendly” bare 
> metal servers where you can
>
>   *   Select the NIC to use (or be sure you’re landing on a server that has 
> proper NIC)
>   *   control by API the bare metal SW setup (linux boot)
>   *   control by API the switch where your server is wired
>
>
>
> The devil is in the detail especially when it comes to mapping openstack to 
> the underlying networking layer.
>
> You can get away with nested virtualization but that is hardly comparable to 
> the real installation process in production 
>
> The level of details required for production deployers of openstack is 
> excruciatingly difficult.
>
>
>
> HTH
>
>
>
>   Alec
>
>
>
>
>
> From:  on behalf of Manuel Buil 
> Date: Tuesday, July 9, 2019 at 8:09 AM
> To: TSC OPNFV 
> Subject: [opnfv-tsc] Can installers use CircleCI?
>
>
>
> Hey guys,
>
>
>
> Unfortunately, we ran out of time so I could not ask. I think we all agree by 
> saying that installers are key projects in OPNFV and they are the biggest 
> consumers of our current jenkins CI, so we should probably try one of those 
> in the PoC. In fact, the usual way of deploying a scenario is through an 
> installer, right? So most projects depend on them.
>
>
>
> There are some installer requirements 

Re: [opnfv-tech-discuss] Results of 2019 OPNFV TSC Election #election #announce

[Manuel Buil]

Congratulations to the new TSC!

@David: I think you meant August instead of October, right? 

July 24 - Aug 7 TSC chair nomination
Aug 8 - Aug 22  TSC chair election

Regards,
Manuel

From: opnfv-tech-discuss@lists.opnfv.org  
on behalf of David McBride 
Sent: Thursday, July 25, 2019 9:37 PM
To: TECH-DISCUSS OPNFV ; TSC OPNFV 

Cc: Bin Hu ; Heather Kirksey ; 
James Baker 
Subject: [opnfv-tech-discuss] Results of 2019 OPNFV TSC Election #election 
#announce

Team,

I'm pleased to announce the results of the TSC election.

  *   Al Morton
  *   Bin Hu
  *   Cedric Ollivier
  *   Cristina Pauna
  *   Dan Xu
  *   Frank Brockners
  *   Georg Kunz
  *   Manuel Buil
  *   Mark Beierl
  *   Panagiotis Karalis
  *   Parker Berberian
  *   Qiao Fu
  *   Sridhar Rao
  *   Sunku Ranganath
  *   Trevor Cooper

The new TSC members will assume their roles as soon as the TSC chair election 
is completed near the end of October.

Election Stats:

  *   17 nominees
  *   116 eligible voters
  *   51 votes cast

Thanks to all of the nominators and nominees, as well as those who cast votes.

Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23391): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23391
Mute This Topic: https://lists.opnfv.org/mt/32602427/21656
Mute #election: https://lists.opnfv.org/mk?hashtag=election=2783016
Mute #announce: https://lists.opnfv.org/mk?hashtag=announce=2783016
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] [XCI] Failed to deploy XCI

[Manuel Buil]

Hey,

I can't reproduce that problem. Can you confirm that you followed the steps: 
https://opnfv-releng-xci.readthedocs.io/en/latest/xci-user-guide.html#how-to-use?

Did you perhaps forget to generate the SSH key?

Regards,
Manuel


From: opnfv-tech-discuss@lists.opnfv.org  
on behalf of xudan 
Sent: Tuesday, July 16, 2019 12:49 PM
To: Parker Berberian; opnfv-tech-discuss@lists.opnfv.org
Cc: fatih.degirme...@est.tech
Subject: Re: [opnfv-tech-discuss] [XCI] Failed to deploy XCI


Hi Parker,



Thanks a lot for your reply. I have tried to add the deployment user to these 
groups but it still failed with the same error.

Then I tried to change the Ansible script to force it to use sudo to do the 
command and it works.



For script [1], change it to be like this:

- name: Configure SSH key for local user

  become: yes

  become_method: sudo

  user:

  …

  …



Regagrds,

Dan



[1] 
https://github.com/opnfv/releng-xci/blob/master/xci/playbooks/configure-localhost.yml#L83





From: Parker Berberian [mailto:pberber...@iol.unh.edu]
Sent: Friday, July 12, 2019 8:57 PM
To: xudan (N) 
Cc: opnfv-tech-discuss@lists.opnfv.org; fatih.degirme...@est.tech
Subject: Re: [opnfv-tech-discuss] [XCI] Failed to deploy XCI



Hi Dan Xu,



This seems like a bug if XCI is not using `sudo` to change group settings. 
However, you should be able to work around this by adding the groups to your 
user manually.



In my XCI deploy, the deployment user has these groups: "root, wheel, kvm, 
qemu, docker, libvirt". I'm not sure which are required by xci, but there is no 
harm to adding them all to your user.



If you manually add these groups to your xd user with `sudo usermod -aG 
 xd` then XCI should skip the step that is giving you trouble.



Best,

Parker Berberian

Lead Developer

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

pberber...@iol.unh.edu

www.iol.unh.edu





On Fri, Jul 12, 2019 at 3:42 AM xudan 
mailto:xuda...@huawei.com>> wrote:

Hi all,



I tried to deploy with XCI master but failed with error “usermod: Permission 
denied.\nusermod: cannot lock /etc/passwd;”. The detailed error message and 
required ENV can be found in the attachment.

I used user ‘xd’ and have added ‘xd ALL=(ALL) NOPASSWD:ALL’ to sudoers.

Also SSH key are generated before the deploy.

xd@ubuntu:~$ ll ~/.ssh/

total 20

drwxrwxr-x 2 xd xd 4096 Jul 11 15:17 ./

drwxr-xr-x 7 xd xd 4096 Jul 11 15:05 ../

-rw--- 1 xd xd 1675 Jul 11 14:59 id_rsa

-rw-r--r-- 1 xd xd  391 Jul 11 14:59 id_rsa.pub

-rw-r--r-- 1 xd xd  222 Jul 11 15:17 known_hosts



Also I can successfully use command “sudo usermod –d /home/abc abc” to change 
user ‘abc’’s home with user ‘xd’.



Did anyone meet the same problem before? Or do anyone know how to solve this?



BR,

Dan Xu

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

View/Reply Online (#23360): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23360
Mute This Topic: https://lists.opnfv.org/mt/32439749/1217375
Group Owner: 
opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[pberber...@iol.unh.edu]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] Nomination for TSC - Georg Kunz

[Manuel Buil]

Hi,

I would like to nominate Georg Kunz from Ericsson

Georg has been an active and valuable contributor in OPNFV since the beginning. 
For example, lately, he has helped Dovetail progress to a point where we have a 
great certification tool for OPNFV. As part of the TSC, Georg always provides 
great and thoughtful opinions that help steer the discussions into the correct 
direction. Besides, due to his experience, he can be a great asset to have when 
discussions regarding OVP pop up, and we know they will as LFN expects us to 
succeed with it.

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] TSC Nomination: Cristina Pauna

[Manuel Buil]

I would like to nominate Cristina Pauna of ENEA to the TSC.

Nomination Statement:

Cristina has been working in OPNFV for several years contributing to FUEL and 
providing help and support to anyone who required it. She has been a great 
community player! During last TSC mandate, she was one of the few who tried to 
change things and had the courage to lead a difficult task of improving, among 
other things, our best practices. I think her perseverance and her willingness 
to improve OPNFV is really valuable for us and that's why I think she should 
continue in the OPNFV TSC.

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23326): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23326
Mute This Topic: https://lists.opnfv.org/mt/32310601/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-tsc] [opnfv-tech-discuss] TSC Nomination: Manuel Buil

[Manuel Buil]

Thanks Mark. I accept the nomination.

Regards,
Manuel

From: opnfv-...@lists.opnfv.org  on behalf of David 
McBride 
Sent: Tuesday, July 2, 2019 6:35 PM
To: TSC OPNFV; mbei...@vmware.com
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tsc] [opnfv-tech-discuss] TSC Nomination: Manuel Buil

+OPNFV-TSC

On Tue, Jul 2, 2019 at 8:27 AM Mark Beierl via 
Lists.Opnfv.Org<http://Lists.Opnfv.Org> 
mailto:vmware@lists.opnfv.org>> wrote:

I would like to nominate Manuel Build of SUSE to the TSC.



Nomination Statement:



Manuel has been an active member of OPNFV for over three years, having served 
one term already on the TSC.  His contributions include being the PTL for 
Service Function Chaining as well as being involved in the edge and Airship 
projects, and XCI.  With his breadth of experience in different aspects of 
OPNFV, I believe Manuel will be of great value to the TSC for a second term.



Regards,

Mark Beierl
Telco Innovation Staff Solution Architect

mbei...@vmware.com<mailto:mbei...@vmware.com%0b>

[VMware]<http://www.vmware.com/>



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

View/Reply Online (#23310): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23310
Mute This Topic: https://lists.opnfv.org/mt/32287294/766177
Group Owner: 
opnfv-tech-discuss+ow...@lists.opnfv.org<mailto:opnfv-tech-discuss%2bow...@lists.opnfv.org>
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
-=-=-=-=-=-=-=-=-=-=-=-
--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23314): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23314
Mute This Topic: https://lists.opnfv.org/mt/32289409/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: [XCI INSTALLING] [opnfv-tech-discuss] [opnfv-tech-discuss+help]

[Manuel Buil]

On Wed, 2019-05-15 at 14:28 +0300, NAZAN CENGIZ wrote:
> Hi all,
> We are installing successfull scenario:os-odl-sfc. XCI installing
> config on below;
> 
> export INSTALLER_TYPE=osa
> export DEPLOY_SCENARIO=os-odl-sfc
> export XCI_FLAVOR=ha
> export XCI_DISTRO=ubuntu
> ./xci-deploy.sh
> 
> Mister Fatih said as :"Please start with a small virtual deployment
> of the scenario you want to try and avoid setting
> OPENSTACK_OSA_VERSION while doing that." so we didn't any setting
> OPENSTACK_OSA_VERSION.
> Question 1:Now, what is be Openstack ansible variable on XCI? We want
> OPENSTACK_OSA_VERSION=stable/queens but maybe it's be problems
> setting osa_version. 

This is the openstack version ==> https://github.com/opnfv/releng-xci/b
lob/master/xci/config/pinned-versions#L38-L39
What probably Fatih meant was to start with XCI_FLAVOR=mini. You
started with ha which complicates things
> Question 2:Which XCI include OPNFV projects? For this, I looked at
> the setup-infrastructure log file on the opnfv machine, but in
> general I found that the necessary adjustments were made for
> Openstack projects.

These are the supported scenarios (+ SFC) ==> https://github.com/opnfv/
releng-xci-scenarios/tree/master/scenarios
> Question 3:What is password for stack user on Controller machines?
> Question 3 for Explanation:
> Openstack running on opnfv,controller00,controller01,controller02
> machines.Openstack running ago on Opnfv machine we must run "source
> openrc" config this machine.
> While We are logging as ssh root@192.168.122.3,ssh root@192.168.122.6
> ,ssh root@192.168.122.7 on controller machines when we run "ls -la"
> command not find source file these
> machine(controller00,controller01,controller02).
> We run "su - stack" command on these controller machine but it is
> want password as below;
> (root@controller00:~# su - stack
> No passwd entry for user 'stack')
> 
> But when XCI install "ssh-keygen -t rsa" command Enter passphrase
> (empty for no passphrase): no passkey.So what is stack user password?

That's weird, does that happeng with 192.168.122.2, 192.168.122.4 and
192.168.122.5 too?

> Best Regards,
> Nazan.
> 
> 
> This e-mail and any attached files are confidential and may be
> legally privileged. If you are not the addressee, any disclosure,
> reproduction, copying, distribution, or other dissemination or use of
> this communication is strictly prohibited. If you have received this
> transmission in error please notify the sender immediately and then
> delete this mail.
> E-mail transmission cannot be guaranteed to be secure or error free
> as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore
> does not accept liability for any errors or omissions in the contents
> of this message which arise as a result of e-mail transmission or
> changes to transmitted date not specifically approved by the sender.
> If this e-mail or attached files contain information which do not
> relate to our professional activity we do not accept liability for
> such information.
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#23140): https://lists.opnfv.org/g/opnfv-tech-disc
> uss/message/23140
> Mute This Topic: https://lists.opnfv.org/mt/31628579/675458
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsubb  [mb
> u...@suse.com]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] Stepping down from PTL

[Manuel Buil]

Hi,

Now that Hunter is out, as I already announced in our last SFC meeting,
I will step down from my PTL role in the OPNFV-SFC project. Due to
recent changes in my focus, I don't have enough time to continue as
PTL. I would like to thanks everyone who helped me during these 4
releases, it was a great honor to be PTL.

Unfortunately, I haven't heard from anyone interested in taking the PTL
role. Nevertheless, I would like to call for nominations for the new
PTL. Please respond to this email with nominations.

Thanks,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23133): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23133
Mute This Topic: https://lists.opnfv.org/mt/31616222/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] ONS Un-conference topic - Leverage OPNFV Test Frameworks

[Manuel Buil]

I agree with Mark. Also be aware that functest documentation needs an
update. For example the devguide is still describing Euphrates release:
https://opnfv-functest.readthedocs.io/en/stable-
gambia/testing/developer/devguide/index.html#functest-util-classes and
there are commands which don't work anymore in the user guide: https://
opnfv-functest.readthedocs.io/en/stable-
gambia/testing/user/userguide/runfunctest.html (e.g. functest testcase
list). Probably a section about Xtesting would help there and also
covering developer use cases: several weeks ago I had trouble to
activate the SFC testcases as it was not described that I had to modify
the yaml config file.
Besides, we are an open source community and as our community code of
conduct says, we should have 100% transparency. Pointing to our
weaknesses in public or ask questions is not bad, on the contrary:
No one should be afraid of asking questions or making mistakes.  Some
may not know how to express themselves or may feel intimidated, and
community members should encourage people to simply participate the
best they can and people will not be judged.  
Regards,Manuel
On Mon, 2019-04-01 at 13:30 +, Mark Beierl wrote:
> With all due respect, I would not call David’s message damaging.
>  
> In the software/releases Wiki space,, there is only one passing
> reference to Xtesting put in place by you starting around April 9,
> 2018.  Note: David is a release manager, and as such closely follows
> the releases.  If Xtesting is not releases,
>  then it is perfectly understandable that he is not aware of it.
>  
> When I search for Xtesting in the wiki, I get references to pages
> that refer to “collivier” in sources.  I would definitely not have
> considered those to be part of OPNFV, so if Xtesting is supposed to
> be official, then please do make it
>  so and host it via LFN.
>  
> 
> Regards,
> Mark
>  
> Mark Beierl
> SW System Sr Principal Developer
> Dell EMC |
>  Cloud & Communication Service Provider Solution
> 
> mark.bei...@dell.com
>  
> 
> From:  on behalf of Cedric
> OLLIVIER 
> 
> Date: Saturday, March 30, 2019 at 13:12
> 
> To: "HU, BIN" , "Cooper, Trevor"  .com>, "opnfv-tech-discuss@lists.opnfv.org"  .opnfv.org>, "test...@lists.opnfv.org" 
> 
> Cc: "dmcbr...@linuxfoundation.org" ,
> Pierre Lynch , "Limingjiang (Rex)"  ji...@huawei.com>, Heather Kirksey , "c
> edric.olliv...@orange.com" 
> 
> Subject: Re: [opnfv-tech-discuss] ONS Un-conference topic - Leverage
> OPNFV Test Frameworks
> 
> 
>  
> 
> 
> [EXTERNAL EMAIL] 
> 
> 
> Hello,
> 
> 
>  
> 
> 
> Who is the target audience here? internal or external?
> 
> 
> At firth glance, I would have considered internal discussions to
> prevent from next damaging public messages like the next 2 email sent
> to ONAP TSC and OPNFV TSC.
> 
> 
> https://lists.onap.org/g/onap-tsc/message/4804
> 
> 
> https://lists.opnfv.org/g/opnfv-tsc/message/5050?p=,,,20,0,0,0::Creat
> ed,,Lack+of+developers,20,2,0,29775334
> 
> 
>  
> 
> 
> We have given lots of speechs in the last ONS summits about that
> topic and it seems we are still unsuccessfull in OPNFV (and our tools
> are already reused by LFN projects)
> 
> 
> https://sched.co/EF9Z
> 
> 
> https://www.sdxcentral.com/articles/news/opnfvs-6th-release-brings-te
> sting-capabilities-that-orange-is-already-using/2018/05/
> 
> 
> https://sched.co/Fmsd
> 
> 
> https://sched.co/LKU3
> 
> 
>  
> 
> 
> + OPNFV Hackfest/Plugest
> 
> 
> http://testresults.opnfv.org/functest/gambia/
> 
> 
> http://testresults.opnfv.org/functest/functest2019/
> 
> 
> etc...
> 
> 
>  
> 
> 
> 
> Yes Xtesting is hosted by OPNFV (Functest).
> 
> 
> It's worth mentioning that Bitergia quickly highlights that more than
> 50% of the overall code contribution in OPNFV from the beginning of
> the year is about Functest and its subprojects.
> 
> 
> It should be even bigger if we take the other OPNFV test frameworks
> into account.
> 
> 
> https://opnfv.biterg.io/app/kibana
> 
> 
> 
>  
> 
> 
> Cédric
> 
> 
>  
> 
> 
> Le jeudi 28 mars 2019 à 18:54 +, HU, BIN a écrit :
> 
> > Great, Trevor, thank you for leading this effort.
> >  
> > Would you add this topic in 
> > https://wiki.opnfv.org/display/EVNT, where we collect OPNFV related
> > topics for ONS so that people will have an overall insight of all
> > OPNFV related activities in ONS?
> >  
> > Thank you
> > Bin
> >  
> > 
> > 
> > From: test...@lists.opnfv.org 
> > On Behalf Of Cooper, Trevor
> > 
> > Sent: Thursday, March 28, 2019 11:51 AM
> > 
> > To: opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
> > 
> > Cc: dmcbr...@linuxfoundation.org; Pierre Lynch  > ht.com>; Limingjiang (Rex) 
> > 
> > Subject: [test-wg] ONS Un-conference topic - Leverage OPNFV Test
> > Frameworks
> > 
> > 
> >  
> > Based on a discussion in the Test Working Group today I have added
> > this proposed un-conference topic on testing. We are looking for
> > volunteers to help lead the discussion, please consider adding your
> > name
> >  and creating 

Re: [opnfv-tech-discuss] How to activate tests in functest-features

[Manuel Buil]

Hi Cedric,
Now I can see SFC in master but I think something is wrong because the
module cannot be loaded:
https://hastebin.com/dipibupihu.bash
Is there anything else that I must activate?
Thanks,Manuel


On Thu, 2019-03-07 at 10:00 +0100, Manuel Buil wrote:
> Hello Cedric,
> 
> As you suggested, I started using the container "opnfv/functest-
> features:latest"; however, I don't see sfc project there. Is there
> anything wrong?  
> 
> Regards,
> Manuel
> 
> On Wed, 2019-03-06 at 19:00 +0100, Cedric OLLIVIER wrote:
> > SFC is now enabled in Functest master which could be the best
> > containers regarding your SUT (XCI).
> > https://gerrit.opnfv.org/gerrit/#/c/66811/
> > 
> > It had been disabled in Functest master when the SFC hunter branch
> > didn't exist (requirement synchronization). 
> > 
> > Cédric
> > 
> > Le mercredi 06 mars 2019 à 11:39 +0100, Manuel Buil a écrit :
> > > Thanks Cristina!
> > > 
> > > On Wed, 2019-03-06 at 09:10 +, Cristina Pauna wrote:
> > > > Hi Manuel,
> > > >  
> > > > When you start the Functest container, you need to pass
> > > > DEPLOY_SCENARIO variable, that needs to match the regex in the
> > > >  testcases file [1] 
> > > > In your case, it needs to match odl.*sfc [2]
> > > >  
> > > > Thanks,
> > > > Cristina
> > > >  
> > > >  
> > > > [1]
> > > > 
> > > > https://github.com/opnfv/functest/blob/master/functest/ci/testc
> > > > ases.yaml
> > > > [2]
> > > > 
> > > > https://github.com/opnfv/functest/blob/master/functest/ci/testc
> > > > ases.yaml#L492
> > > >  
> > > > 
> > > > 
> > > > From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-dis
> > > > c...@lists.opnfv.org]
> > > > On Behalf Of Manuel Buil
> > > > 
> > > > Sent: Wednesday, March 6, 2019 10:54 AM
> > > > 
> > > > To: OPNFV-tech 
> > > > 
> > > > Subject: Re: [opnfv-tech-discuss] How to activate tests in
> > > > functest-features
> > > > 
> > > > 
> > > >  
> > > > 
> > > > Hey,
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Nobody knows the answer? We are stuck in SFC...
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > We have also checked 
> > > > https://opnfv-functest.readthedocs.io/en/stable-gambia/testing/
> > > > user/userguide/runfunctest.html but we could not find anything
> > > > either.
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Any hint or pointer to docs would be great!
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Thanks,
> > > > 
> > > > 
> > > > Manuel
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > On Mon, 2019-03-04 at 15:31 +0100, Manuel Buil wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > When I run 'run_tests -t functest-odl-sfc' inside the
> > > > > functest-
> > > > > 
> > > > > 
> > > > > features:gambia or hunter version, the tests are skipped. I
> > > > > have been
> > > > > 
> > > > > 
> > > > > reading the wiki but I could not find how to make functest
> > > > > run the sfc
> > > > > 
> > > > > 
> > > > > tests:
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > https://wiki.opnfv.org/pages/viewpage.action?pageId=29098314
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > Any help or pointer to the correct doc will help!
> > > > > 
> > > > > 
> > > > >  
> > > > > 
> > > > > 
> > > > > Thanks,
> > > > > 
> > > > > 
> > > > > Manue

Re: [opnfv-tech-discuss] How to activate tests in functest-features

[Manuel Buil]

Hello Cedric,
As you suggested, I started using the container "opnfv/functest-
features:latest"; however, I don't see sfc project there. Is there
anything wrong?  
Regards,Manuel
On Wed, 2019-03-06 at 19:00 +0100, Cedric OLLIVIER wrote:
> SFC is now enabled in Functest master which could be the best
> containers regarding your SUT (XCI).
> https://gerrit.opnfv.org/gerrit/#/c/66811/
> 
> It had been disabled in Functest master when the SFC hunter branch
> didn't exist (requirement synchronization). 
> 
> Cédric
> 
> Le mercredi 06 mars 2019 à 11:39 +0100, Manuel Buil a écrit :
> > Thanks Cristina!
> > 
> > On Wed, 2019-03-06 at 09:10 +, Cristina Pauna wrote:
> > > Hi Manuel,
> > >  
> > > When you start the Functest container, you need to pass
> > > DEPLOY_SCENARIO variable, that needs to match the regex in the
> > >  testcases file [1] 
> > > In your case, it needs to match odl.*sfc [2]
> > >  
> > > Thanks,
> > > Cristina
> > >  
> > >  
> > > [1]
> > > 
> > > https://github.com/opnfv/functest/blob/master/functest/ci/testcas
> > > es.yaml
> > > [2]
> > > 
> > > https://github.com/opnfv/functest/blob/master/functest/ci/testcas
> > > es.yaml#L492
> > >  
> > > 
> > > 
> > > From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discu
> > > s...@lists.opnfv.org]
> > > On Behalf Of Manuel Buil
> > > 
> > > Sent: Wednesday, March 6, 2019 10:54 AM
> > > 
> > > To: OPNFV-tech 
> > > 
> > > Subject: Re: [opnfv-tech-discuss] How to activate tests in
> > > functest-features
> > > 
> > > 
> > >  
> > > 
> > > Hey,
> > > 
> > > 
> > >  
> > > 
> > > 
> > > Nobody knows the answer? We are stuck in SFC...
> > > 
> > > 
> > >  
> > > 
> > > 
> > > We have also checked 
> > > https://opnfv-functest.readthedocs.io/en/stable-gambia/testing/us
> > > er/userguide/runfunctest.html but we could not find anything
> > > either.
> > > 
> > > 
> > >  
> > > 
> > > 
> > > Any hint or pointer to docs would be great!
> > > 
> > > 
> > >  
> > > 
> > > 
> > > Thanks,
> > > 
> > > 
> > > Manuel
> > > 
> > > 
> > >  
> > > 
> > > 
> > > On Mon, 2019-03-04 at 15:31 +0100, Manuel Buil wrote:
> > > 
> > > > Hi,
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > When I run 'run_tests -t functest-odl-sfc' inside the functest-
> > > > 
> > > > 
> > > > features:gambia or hunter version, the tests are skipped. I
> > > > have been
> > > > 
> > > > 
> > > > reading the wiki but I could not find how to make functest run
> > > > the sfc
> > > > 
> > > > 
> > > > tests:
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > https://wiki.opnfv.org/pages/viewpage.action?pageId=29098314
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Any help or pointer to the correct doc will help!
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Thanks,
> > > > 
> > > > 
> > > > Manuel
> > > > 
> > > > 
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > 
> > > > 
> > > > Links: You receive all messages sent to this group.
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > View/Reply Online (#22879): 
> > > > https://lists.opnfv.org/g/opnfv-tech-discuss/message/22879
> > > > 
> > > > 
> > > > Mute This Topic: 
> > > > https://lists.opnfv.org/mt/30213915/675458
> > > > 
> > > > 
> > > > Group Owner: 
> > > > opnfv-tech-discuss+ow...@lists.opnfv.org
> > > > 
> > > > 
> > > > Unsubscribe: 
> > > > https://lists.opnfv.org/g/opnfv-tech-discuss/unsubbb  [mbuil@su
> > > > se.com]
> > > > 
> > > > 
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > &

Re: [opnfv-tech-discuss] How to activate tests in functest-features

[Manuel Buil]

Thanks Cristina!

On Wed, 2019-03-06 at 09:10 +, Cristina Pauna wrote:
> 
> 
> Hi Manuel,
>  
> When you start the Functest container, you need to pass
> DEPLOY_SCENARIO variable, that needs to match the regex in the
>  testcases file [1] 
> In your case, it needs to match odl.*sfc [2]
>  
> Thanks,
> Cristina
>  
>  
> [1]
> 
> https://github.com/opnfv/functest/blob/master/functest/ci/testcases.y
> aml
> [2]
> 
> https://github.com/opnfv/functest/blob/master/functest/ci/testcases.y
> aml#L492
>  
> 
> 
> From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@l
> ists.opnfv.org]
> On Behalf Of Manuel Buil
> 
> Sent: Wednesday, March 6, 2019 10:54 AM
> 
> To: OPNFV-tech 
> 
> Subject: Re: [opnfv-tech-discuss] How to activate tests in functest-
> features
> 
> 
>  
> 
> Hey,
> 
> 
>  
> 
> 
> Nobody knows the answer? We are stuck in SFC...
> 
> 
>  
> 
> 
> We have also checked 
> https://opnfv-functest.readthedocs.io/en/stable-gambia/testing/user/u
> serguide/runfunctest.html but we could not find anything either.
> 
> 
>  
> 
> 
> Any hint or pointer to docs would be great!
> 
> 
>  
> 
> 
> Thanks,
> 
> 
> Manuel
> 
> 
>  
> 
> 
> On Mon, 2019-03-04 at 15:31 +0100, Manuel Buil wrote:
> 
> > Hi,
> > 
> > 
> >  
> > 
> > 
> > When I run 'run_tests -t functest-odl-sfc' inside the functest-
> > 
> > 
> > features:gambia or hunter version, the tests are skipped. I have
> > been
> > 
> > 
> > reading the wiki but I could not find how to make functest run the
> > sfc
> > 
> > 
> > tests:
> > 
> > 
> >  
> > 
> > 
> > https://wiki.opnfv.org/pages/viewpage.action?pageId=29098314
> > 
> > 
> >  
> > 
> > 
> > Any help or pointer to the correct doc will help!
> > 
> > 
> >  
> > 
> > 
> > Thanks,
> > 
> > 
> > Manuel
> > 
> > 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > 
> > 
> > Links: You receive all messages sent to this group.
> > 
> > 
> >  
> > 
> > 
> > View/Reply Online (#22879): 
> > https://lists.opnfv.org/g/opnfv-tech-discuss/message/22879
> > 
> > 
> > Mute This Topic: 
> > https://lists.opnfv.org/mt/30213915/675458
> > 
> > 
> > Group Owner: 
> > opnfv-tech-discuss+ow...@lists.opnfv.org
> > 
> > 
> > Unsubscribe: 
> > https://lists.opnfv.org/g/opnfv-tech-discuss/unsubbb  [mbuil@suse.c
> > om]
> > 
> > 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > 
> 
> 
> 
> 
> This message, including attachments, is CONFIDENTIAL. It may also be
> privileged or otherwise protected by law. If you received this email
> by mistake please let us know by reply and then delete it from your
> system; you should not copy it or disclose its contents
>  to anyone. All messages sent to and from Enea may be monitored to
> ensure compliance with internal policies and to protect our business.
> Emails are not secure and cannot be guaranteed to be error free as
> they can be intercepted, a mended, lost or destroyed,
>  or contain viruses. The sender therefore does not accept liability
> for any errors or omissions in the contents of this message, which
> arise as a result of email transmission. Anyone who communicates with
> us by email accepts these risks.
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#22890): https://lists.opnfv.org/g/opnfv-tech-disc
> uss/message/22890
> Mute This Topic: https://lists.opnfv.org/mt/30213915/675458
> Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsubb  [mb
> u...@suse.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] How to activate tests in functest-features

[Manuel Buil]

Hi,

When I run 'run_tests -t functest-odl-sfc' inside the functest-
features:gambia or hunter version, the tests are skipped. I have been
reading the wiki but I could not find how to make functest run the sfc
tests:

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

Any help or pointer to the correct doc will help!

Thanks,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22879): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22879
Mute This Topic: https://lists.opnfv.org/mt/30213915/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] Code and Release improvements

[Manuel Buil]

Hello,
This is the last mail I got in this thread but perhaps it is not the
last one. For unknown reasons, this thread is being flagged as SPAM and
I am not sure if something got blocked in between (e.g. I never got
Alec's mail).
Ok, now I get your points, thanks Alec and Cedric. Unfortunately, I
still think it is bad if this is not enforced (with temporary
exceptions) because of what I said in my previous mail. I'd suggest to
ask around people working in other communities about this (kernel,
openstack, CNCF...). Last week I was on a business trip and had the
opportunity to ask open source people. Everyone I asked was surprised
and I agreed with a couple of them who said that they would never join
a project that allows this. If a project does not attract developers,
allowing to self-merge patches is not going to help, right the
opposite. 
It seems to me, and correct me if I am wrong, that you guys are fine if
OPNFV becomes a community for multiple projects with only one/two
committers (as long as those are niche projects (@Alec: what about
installers? what about yardstick/functest/dovetail?) or projects with
an ideally perfect CI). That is a vision I don't share and I thought
OPNFV in general did not share but I can just talk for myself, let's
hear some other opinions ;).
Regards,Manuel
On Mon, 2019-02-11 at 14:41 +, cedric.olliv...@orange.com wrote:
> Hello,
>  
> New development process enforcement for which developers?
> The proposal could maybe make sense in a very active community with
> lots of developers without any automated verification jobs.
> Both assumptions are false:
> 
> as bitergia statistics (https://opnfv.biterg.io) have been showing
> for several months, OPNFV is progressively becoming a community
> without developers.
> as a consequence we put in place lots of verification jobs which
> compensate the lack of reviews and which strongly improve the code
> quality.
> 
> 
> 
> Some of them are being adopted by Yardstick (I voted +1).
> Imposing new process rules from the top will clearly discourage the
> remaining contributors and increase the risk of fork out of the
> community.
> It is at least an option I can clearly foresee for my project.
>  
> Is adding process enforcements the top priority topic of OPNFV?
> Regarding the previous statement, is it really the top priority of
> OPNFV TSC to debate on new development processes which constraints
> the developers without any direct improvement regarding the project
> quality ?
> Is there no more critical decisions to take if we simply want to
> survive as a community?
> 
> As service provider I am still fully convinced of the interest of
> OPNFV.
> The creation of the LF Networking should be a catalyst to work with
> the other projects and disseminate the best practices that are
> already in place and have been demonstrated by the code.
> It is already the case with the discussions on Xtesting with ONAP and
> Akraino. Docker production, Alpine adoption, CI/CD best practices
> which have been initiated in OPNFV.
>  
> We certainly agree not to enable it in Functest.
> 
> 
> Cédric
>  
> 
> 
> De : opnfv-tech-discuss@lists.opnfv.org [opnfv-tech-disc...@lists.opn
> fv.org] de la part de Alec via Lists.Opnfv.Org [ahothan=cisco.com@lis
> ts.opnfv.org]
> 
> Envoyé : samedi 9 février 2019 04:08
> 
> À : Manuel Buil; Cristina Pauna; opnfv-tech-discuss@lists.opnfv.org
> 
> Cc : opnfv-tech-discuss@lists.opnfv.org
> 
> Objet : Re: [opnfv-tech-discuss] Code and Release improvements
> 
> 
> 
> 
> 
> 
> 
>  
>  
> I do not disagree on the general benefits of having multiple
> reviewers for every commit, no question about it. If you can afford
> it – go for it.
> However, I would like to point out that for most low-key or “niche”
> projects with few committers, a rule to enforce dual review and
> forbid self commit will quickly force any remaining participants to
> exit opnfv
>  and head out direct to gihtub ot bitbucket.
>  
> So I would vote to let the PTL decide on how to regulate the commits
> of his/her project. I think OPNFV PTL have generally been quite
> responsible in the past and I have not personally seen any of the
> behavior
>  listed below.
> I think many PTL are in the same situation, with projects that are
> not sufficiently attractive to afford the luxury of requesting
> multiple reviews. Most PTL would welcome any “reasonable” review but
> in  many
>  cases, it just happens that the code that is being managed in not
> that easy to understand, not because it is spaghetti code, but
> because of the nature of the beast. In my case, people with good
> understanding of networking performance, traffic generation and
>  TRex APIs are unfortunately very hard to come by. This

Re: [opnfv-tech-discuss] Code and Release improvements

[Manuel Buil]

Hi Cristina,
SFC has been doing this from the beginning and I think it is a great
idea which should be enforced. There are of course exceptions which
should be handled with a workaround, especially at the beginning, but
as you say, they should be limited on time. When a person merges his
own patches, there are some dangerous potential consequences which
jeopardize the values of community driven development, for example:
1 - Single Point of Failure. That person is the only one that knows
about some piece of the code. If that person stops working in the
project, can other people continue the development?2 - Coding hero/god
mentality which is very bad for the health of the community and will
frighten potential new committers or consumers of that project3 -
Quality of code becomes worse. Several eyes on the code is better than
just two. Jenkins tests will give +1 to spaghetti code4 - Knowledge
sharing is stopped. By code reviews, developers share knowledge and
ideas or can enforce good documentation5 - If I am PTL and I am able to
merge my own patches. Why would I want to add new committers?6 -
Company driven projects instead of community driven projects
Unfortunately, I was not able to join Tuesday's or Thursday's meeting
because of a business trip. Did you reach any agreement? By reading
your mail it seems there were people against it which suprises me
because I see this as common sense in open source communities but
perhaps I am missing the points of the people against it.
Regards,Manuel
On Wed, 2019-02-06 at 15:17 +, Cristina Pauna wrote:
> Hi all,
>  
> The first proposal from the
> Code and Release Quality (Improve project's info accuracy) has been
> approved by the TSC on 5th Feb
> (see TSC-14
> for details).  
>  
> The second proposal (Improve gerrit best practices), although
> generally well received, has raised some concerns and I would like to
> ask the community for more feedback on it.
> The proposal is to discourage self-merging patches by adding this
> into our wiki documentation and, in a reasonable timeline to enforce
> it through gerrit (current recommendation is Hunter 8.0 milestone)
>  
> The background for this proposal is good practices done in other open
> source communities, which value peer review. Some examples are:
> ·   
> OpenStack requires 2 committers to give a +2 for any patch:
> https://docs.openstack.org/infra/manual/developers.html#code-review
> ·   
> Akraino requires contributor diversity (the project demonstrates that
> it has a stable core team of contributors/committers
>  which are affiliated to a set of at least three different
> companies):
> https://wiki.akraino.org/display/AK/Akraino+Technical+Community+Docum
> ent#AkrainoTechnicalCommunityDocument-3.3.7.3CoreReview
> ·   
> Blog with gerrit best practices that promotes to not self-approve
> changes and to have at least 2 other people review the change:
> https://blog.simplypatrick.com/html/gerrit-best-practices.html
> ·   
> Some OPNFV projects already follow this good practice although is not
> enforced by gerrit
>  
>  
> Peer reviews are important because they make other members to better
> understand the changes that are happening in a project, give
> opportunity to have architectural discussions, make committers
>  more involved and responsible, and improve the overall quality of a
> project. 
> 
>  
> Understandably, there have been situations when a project had a
> single active committer, and those can be excepted from the rule for
> a limited period of time. On the long run this type of projects
>  have been proven  to be unsustainable anyway (most of them died on
> their own when the person sustaining the project pursues other
> interests). Exceptions can always be approved if there’s a good
> reason for them.
>  
> These are some concerns I got over this proposal:
> -   
> Code is automatically verified by Jenkins so a Verified +1 from
> Jenkins assures the new code is not breaking anything
> 
> o  
> Peer review is just as important as automatic verification of the
> patches, as it provides all the benefits listed above. One should not
> exclude the other
> -   
> Trivial patches don’t need peer review
> 
> o  
> What is trivial and not can be better decided by a second set of eyes
> (one line change can have major impact). Also, it should not matter
> if a change is trivial or not to have proper peer
>  review
> -   
> Low number of active developers in OPNFV
> 
> o  
> This is indeed a concern and a reason for which this practice has
> become so common. But unless a project has just 1 active committer,
> self-approved patches should not happen
>  
> I would like to know if your projects already has this practice
> informally, if you would like to have it as a hard requirement, and
> if you have any concerns. You can either use this thread or join
>  us on the Technical Discuss meeting this Thursday (https://wiki.opnf
> v.org/display/PROJ/Weekly+Technical+Discussion)
> 

Re: [opnfv-tsc] [opnfv-tech-discuss] [RESPONSE NEEDED] Community Interest in Co-located Developer Event at ONS #ONS

[Manuel Buil]

Hey David,
Unfortunately, that same week I will be in another conference that I
must attend and is far away from San Jose, so I won't be at ONS this
time. Nevertheless, for the ones who will be able to attend, I always
think this kind of events are very useful :)
Regards,Manuel
On Wed, 2019-01-23 at 08:12 -0800, David McBride wrote:
> +TECH-DISCUSS OPNFV +TSC OPNFV 
> 
> On Tue, Jan 22, 2019 at 10:54 AM David McBride  ion.org> wrote:
> > The TSC discussion of this topic has been pushed out to Jan 29 due
> > to the low number of responses.  Please respond to this thread and
> > let us know your interest in participating in this event if we're
> > able to arrange it.  Both pro and con positions are welcome. 
> > Thanks.
> > David
> > On Sun, Jan 20, 2019 at 7:01 AM MORTON, ALFRED C (AL)  > .att.com> wrote:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi David, (dropping-off the big lists)
> > >  
> > > I’m interested *and* would attend of course.
> > > I’d prefer to meet before ONS begins (like every
> > > other project, I’m sure).
> > >  
> > > Al
> > >  
> > > 
> > > 
> > > 
> > > From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discu
> > > s...@lists.opnfv.org]
> > > On Behalf Of David McBride
> > > 
> > > Sent: Thursday, January 17, 2019 3:59 PM
> > > 
> > > To: TECH-DISCUSS OPNFV ; TSC
> > > OPNFV 
> > > 
> > > Cc: HU, BIN ; Heather Kirksey  > > dation.org>; Brandon Wick 
> > > 
> > > Subject: [opnfv-tech-discuss] [RESPONSE NEEDED] Community
> > > Interest in Co-located Developer Event at ONS #ONS
> > > 
> > > 
> > >  
> > > 
> > > Team,
> > > 
> > >  
> > > 
> > > 
> > > During the TSC meeting on Jan 15, we discussed the possibility of
> > > having a developer event co-located with ONS NA (April 3 - 5). 
> > > We would like to get feedback from the community about the level
> > > of interest in such an activity before we
> > >  commit to finding a location, etc.
> > > 
> > > 
> > >  
> > > 
> > > 
> > > Please respond to this email and let me know if are interested
> > > and would attend the event.  We will also be discussing this
> > > during the next TSC meeting on Jan 22.
> > > 
> > > 
> > >  
> > > 
> > > 
> > > David
> > > 
> > > 
> > > 
> > >  
> > > 
> > > -- 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > David McBride
> > > 
> > > Release Manager, OPNFV
> > > 
> > > 
> > > Mobile: +1.805.276.8018
> > > 
> > > 
> > > Email/Google Talk: dmcbr...@linuxfoundation.org
> > > 
> > > 
> > > Skype: davidjmcbride1
> > > 
> > > 
> > > IRC: dmcbride
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > -- 
> > David McBrideRelease 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 (#4969): https://lists.opnfv.org/g/opnfv-tsc/messag
> e/4969
> Mute This Topic: https://lists.opnfv.org/mt/29434280/675458
> Mute #ons: https://lists.opnfv.org/mk?hashtag=ons=3267464
> Group Owner: opnfv-tsc+ow...@lists.opnfv.org
> Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsubb  [mbuil@suse.
> com]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2019/opnfv-sfc.
2019-01-23-14.59.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22688): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22688
Mute This Topic: https://lists.opnfv.org/mt/29433610/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-tsc] [opnfv-tech-discuss] [edge cloud] Time changed for this week's meeting

[Manuel Buil]

Hey Mark,
I think what the slides show is basically what was discussed (I joined
20 minutes late, so perhaps at the beginning something different was
discussed). I did not take any extra notes.
Regards,Manuel
On Wed, 2019-01-09 at 17:09 +, Mark Beierl wrote:
> Are there any minutes or notes taken from the XCI/StarlingX meeting? 
> I was not able to attend online.
>  
> 
> Regards,
> Mark
>  
> Mark Beierl
> SW System Sr Principal Developer
> Dell EMC |
>  Cloud & Communication Service Provider Solution
> 
> mark.bei...@dell.com
>  
> 
> From:  on behalf of Manuel Buil <
> mb...@suse.com>
> 
> Date: Wednesday, January 9, 2019 at 05:16
> 
> To: "Csatari, Gergely (Nokia - HU/Budapest)"  om>, "zhaoqi...@chinamobile.com" , fuqiao
> , "beth.cohen" ,
> "Peret, Adrian (Nokia - FI/Espoo)" ,
>  julienjut , haojingbo ,
> ildiko , "paul-andre.raymond"  n...@b-yond.com>, "trevor.cooper" ,
> "cristina.pauna" , "xiaohua.zhang"  zh...@windriver.com>,
>  "Bob.Monkman" , "deepak.s"  l.com>, asayeed , "Tina.Tsou" 
> , "klaus.mehler" , "periyasamy.palanisamy"
> , "hu.jie" ,
>  kliu , wanglu , pvaanane  vaan...@redhat.com>, fanyamei ,
> "glenn.seiler" , "huang.shuquan"  huq...@99cloud.net>, "adrien.lebre" ,
>  "pierre.lynch" , pj ,
> "valentin.boucher" , "kan.hong"  n...@99cloud.net>, claudio_serra , acm  search.att.com>, "Tikkanen, Viktor (Nokia - FI/Espoo)"
>  , simple_hlw ,
> "kailun.qin" , "Beierl, Mark"  com>
> 
> Cc: opnfv-tech-discuss , opnfv-
> tsc , edge-computing  .openstack.org>
> 
> Subject: Re: [opnfv-tech-discuss] [edge cloud] Time changed for this
> week's meeting
> 
> 
>  
> 
> 
> [EXTERNAL EMAIL] 
> 
> 
> Hi Qihui,
> 
> 
>  
> 
> 
> Regarding the StarlingX integration with XCI, have you started
> discussions? Is there any meeting where we could dicuss this? I could
> help.
> 
> 
>  
> 
> 
> Regards,
> 
> 
> Manuel
> 
> 
>  
> 
> 
> On Wed, 2019-01-09 at 09:13 +, Csatari, Gergely (Nokia -
> HU/Budapest) wrote:
> 
> > Hi, 
> >  
> > Thanks for the links. 
> >  
> > I still think, that we should keep the Edge Pharos Specs [1] and
> > the Edge Cloud Site definitions [2]
> >  in the whitepaper consistent. 
> >  
> > Br, 
> > Gerg0
> >  
> > [1]: https://wiki.opnfv.org/display/EC/Edge+cloud?preview=/20745277
> > /32015361/Edge%20Cloud_Pharos%20Spec_StarlingX.pdf
> > [2]: https://opnfv-edgecloud.readthedocs.io/en/stable-gambia/develo
> > pment/requirements/requirements.html#edge-sites-conditions-
> > deployment-scenarios
> >  
> > 
> > 
> > From: zhaoqi...@chinamobile.com 
> > 
> > 
> > Sent: Wednesday, January 9, 2019 10:07 AM
> > 
> > To: Csatari, Gergely (Nokia - HU/Budapest)  > om>; fuqiao ; beth.cohen  > n.com>; Peret, Adrian (Nokia - FI/Espoo) ;
> > julienjut ; haojingbo ;
> >  ildiko ; paul-andre.raymond  > o...@b-yond.com>; trevor.cooper ;
> > cristina.pauna ; xiaohua.zhang  > a...@windriver.com>; Bob.Monkman ; deepak.s  > epa...@linux.intel.com>;
> >  asayeed ; Tina.Tsou ;
> > klaus.mehler ; periyasamy.palanisamy  > riyasamy.palanis...@ericsson.com>; hu.jie ; kliu
> > ; wanglu ; pvaanane
> >  ; fanyamei ;
> > glenn.seiler ; huang.shuquan  > q...@99cloud.net>; adrien.lebre ;
> > pierre.lynch ; pj ;
> > valentin.boucher
> >  ; kan.hong ;
> > claudio_serra ; acm 
> > ; Tikkanen, Viktor (Nokia - FI/Espoo) ;
> > simple_hlw ; kailun.qin ;
> >  mark.beierl ; Manuel Buil 
> > 
> > Cc: opnfv-tech-discuss ; opnfv-
> > tsc ; edge-computing  > ts.openstack.org>
> > 
> > Subject: Re: RE: [opnfv-tech-discuss] [edge cloud] Time changed for
> > this week's meeting
> > 
> > 
> >  
> > 
> > Sure.
> > 
> > 
> >  
> > 
> > 
> > I have uploaded the slides onto our wiki home page:
> > https://wiki.opnfv.org/display/EC/Edge+cloud 
> > 
> > 
> > you can find them at the bottom of the page -> "Related discussion
> > links and slides" -> under "January 2019 Plugfest slides"
> > 
> > 
> >  
> > 
> > 
> > Best,
> > 
> > 
> > Qihui
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > China Mobile

[opnfv-tech-discuss] SFC Weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2019/opnfv-sfc.
2019-01-09-15.01.html

If you want to join our meetings come to #opnfv-sfc IRC channel on
Wednesday at 14h UTC (next meeting on the 23rd of January)

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22629): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22629
Mute This Topic: https://lists.opnfv.org/mt/28985212/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] [edge cloud] Time changed for this week's meeting

[Manuel Buil]

Hi Qihui,
Regarding the StarlingX integration with XCI, have you started
discussions? Is there any meeting where we could dicuss this? I could
help.
Regards,Manuel
On Wed, 2019-01-09 at 09:13 +, Csatari, Gergely (Nokia -
HU/Budapest) wrote:
> Hi, 
>  
> Thanks for the links.
> 
>  
> I still think, that we should keep the Edge Pharos Specs [1] and the
>  Edge Cloud Site definitions [2] in the whitepaper consistent.
> 
>  
> Br, 
> Gerg0
>  
> [1]: https://wiki.opnfv.org/display/EC/Edge+cloud?preview=/20745277/3
> 2015361/Edge%20Cloud_Pharos%20Spec_StarlingX.pdf
> [2]: https://opnfv-edgecloud.readthedocs.io/en/stable-gambia/developm
> ent/requirements/requirements.html#edge-sites-conditions-deployment-
> scenarios
>  
> 
> 
> From: zhaoqi...@chinamobile.com 
> 
> 
> Sent: Wednesday, January 9, 2019 10:07 AM
> 
> To: Csatari, Gergely (Nokia - HU/Budapest)  >; fuqiao ; beth.cohen  m>; Peret, Adrian (Nokia - FI/Espoo) ;
> julienjut ; haojingbo ;
>  ildiko ; paul-andre.raymond  d...@b-yond.com>; trevor.cooper ;
> cristina.pauna ; xiaohua.zhang  g...@windriver.com>; Bob.Monkman ; deepak.s  .s...@linux.intel.com>;
>  asayeed ; Tina.Tsou ;
> klaus.mehler ; periyasamy.palanisamy  yasamy.palanis...@ericsson.com>; hu.jie ; kliu  i...@cavium.com>; wanglu ; pvaanane
>  ; fanyamei ;
> glenn.seiler ; huang.shuquan  a...@99cloud.net>; adrien.lebre ; pierre.lynch <
> pierre.ly...@keysight.com>; pj ; valentin.boucher
>  ; kan.hong ;
> claudio_serra ; acm ;
> Tikkanen, Viktor (Nokia - FI/Espoo) ;
> simple_hlw ; kailun.qin ;
>  mark.beierl ; Manuel Buil 
> 
> Cc: opnfv-tech-discuss ; opnfv-
> tsc ; edge-computing  .openstack.org>
> 
> Subject: Re: RE: [opnfv-tech-discuss] [edge cloud] Time changed for
> this week's meeting
> 
> 
>  
> 
> Sure.
> 
> 
>  
> 
> 
> I have uploaded the slides onto our wiki home page:
> https://wiki.opnfv.org/display/EC/Edge+cloud 
> 
> 
> you can find them at the bottom of the page -> "Related discussion
> links and slides" -> under "January 2019 Plugfest slides"
> 
> 
>  
> 
> 
> Best,
> 
> 
> Qihui
> 
> 
> 
> 
> 
> 
> 
> China Mobile Research Institute
> 
> 
> (+86) 13810659120
> 
> 
> 
> >  
> > 
> > 
> > 
> > 
> > From: Csatari,
> >  Gergely (Nokia - HU/Budapest)
> > 
> > 
> > Date: 2019-01-09 16:40
> > 
> > 
> > To: zhaoqi...@chinamobile.com;
> > fuqiao; 
> > beth.cohen; Peret, Adrian (Nokia - FI/Espoo);
> > julienjut; 
> > haojingbo; ildiko; 
> > paul-andre.raymond; trevor.cooper;
> > cristina.pauna; 
> > xiaohua.zhang; Bob.Monkman; 
> > deepak.s; asayeed; 
> > Tina.Tsou; klaus.mehler; 
> > periyasamy.palanisamy; hu.jie; 
> > kliu; wanglu; 
> > pvaanane; fanyamei; 
> > glenn.seiler; huang.shuquan; 
> > adrien.lebre; pierre.lynch; 
> > pj; valentin.boucher; 
> > kan.hong; claudio_serra; 
> > acm; Tikkanen, Viktor (Nokia - FI/Espoo);
> > simple_hlw; 
> > kailun.qin; mark.beierl; 
> > Manuel Buil
> > 
> > 
> > CC: opnfv-tech-discuss;
> > opnfv-tsc; 
> > edge-computing
> > 
> > 
> > Subject: RE: Re: [opnfv-tech-discuss] [edge cloud]
> >  Time changed for this week's meeting
> > 
> > 
> > 
> > 
> > 
> > Hi, 
> > 
> >  
> > Is it possible to get the presented materials in some form?
> >  
> > Thanks,
> > 
> > Gerg0
> >  
> > 
> > 
> > From:
> > zhaoqi...@chinamobile.com 
> > 
> > 
> > Sent: Wednesday, January 9, 2019 2:29 AM
> > 
> > To: fuqiao ; beth.cohen  > .com>; Peret, Adrian (Nokia - FI/Espoo) ;
> >  julienjut ; haojingbo ;
> > Csatari, Gergely (Nokia - HU/Budapest) ;
> >  ildiko ; paul-andre.raymond  > o...@b-yond.com>; trevor.cooper ;
> >  cristina.pauna ; xiaohua.zhang  > h...@windriver.com>; Bob.Monkman ;
> >  deepak.s ; asayeed ;
> > Tina.Tsou ; klaus.mehler  > com>;
> >  periyasamy.palanisamy ; hu.jie
> > ; kliu ; wanglu  > bile.com>;
> >  pvaanane ; fanyamei  > >; glenn.seiler ; huang.shuquan
> >  ; adrien.lebre ;
> > pierre.lynch ; pj ;
> >  valentin.boucher ; kan.hong  > g...@99cloud.net>; claudio_serra ;
> >  acm ; Tikkanen, Viktor (Nokia - FI/Espoo)  > iktor.tikka...@nokia.com>; simple_hlw ;
> > kailun.qin
> >  ; mark.beierl ; Manuel
> > Buil 
> > 
> > Cc: opnfv-tech-discuss ; opnfv-
> > tsc ; edge-computing  > ts.openstack.

[opnfv-tech-discuss] OPNFV-SFC meeting

[Manuel Buil]

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:/freeassociation.sourceforge.net/Europe/Madrid
X-LIC-LOCATION:Europe/Madrid
BEGIN:STANDARD
TZNAME:CET
DTSTART:19701027T03
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:CEST
DTSTART:19700331T02
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:9c6791baeaef2ceb237d1ee6469082c6d6fcd747
DTSTAMP:20190108T120735Z
DTSTART;TZID=/freeassociation.sourceforge.net/Europe/Madrid:
 20190109T16
DTEND;TZID=/freeassociation.sourceforge.net/Europe/Madrid:
 20190109T163000
SEQUENCE:3
ORGANIZER;CN=Manuel Buil:MAILTO:mb...@suse.com
SUMMARY:OPNFV-SFC meeting
LOCATION:https://zoom.us/j/5014627785
TRANSP:OPAQUE
DESCRIPTION:This is the placeholder for our bi-weekly meeting to discuss 
 OPNFV-SFC project
CLASS:PUBLIC
CREATED:20190108T120650Z
LAST-MODIFIED:20190108T120727Z
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;CN=OPNFV-tech;LANGUAGE=en:opnfv-tech-discuss@lists.opnfv.org
RRULE:FREQ=WEEKLY;UNTIL=20190731T14;INTERVAL=2;BYDAY=WE
END:VEVENT
END:VCALENDAR

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

View/Reply Online (#22607): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22607
Mute This Topic: https://lists.opnfv.org/mt/28972854/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-tsc] Discussion of OPNFV Strategic Plan

[Manuel Buil]

Hi Bin,

Reading all your answers (thanks for that!), I think I was confused
because your slides contain much more content that what you really want
us to approve, right? If I understand correctly, basically tomorrow you
would like the TSC to *only* vote on your proposed "strategy (vision
and direction) based on potential addressable market and potential
customer needs, and our expertise and strength". 

That means, checking your slides, you want us to vote on slide 13. The
rest, is just information to corroborate your reasoning of why we need
a new strategy and why that strategy in particular (up until slide 13),
or just a peek into potential actions we could take once the strategy
is approved (after slide 13).

In conclusion, correct if I am wrong, the question you want us to vote
tomorrow would be something like: 

Do you think OPNFV strategy should be based on?: 

* Enabling and automating stakeholders’ business transformation into
DevOps organization
* Addressing key roadblock of other open source communities

Is my reasoning correct? or... how wrong am I? :) 

Thanks,
Manuel

On Mon, 2018-11-26 at 15:39 +, HU, BIN wrote:
> Tim,
> 
> Thank you for jumping in and offering your opinion. That's very
> helpful and valuable.
> 
> If I understand correctly, Point #1 and #3 are actually the same
> question, i.e. what will we do in the next step?
> - As I clarified in the email https://lists.opnfv.org/g/opnfv-tsc/mes
> sage/4844 and earlier in this thread https://lists.opnfv.org/g/opnfv-
> tsc/message/4845, this is our 1st milestone or Step #1 to have a
> strategic plan. This milestone triggers the action of Step #2 and
> other following steps. Those steps (or actions) are outlined on slide
> #16.
> - Once we agree on the strategic plan, the action is the Step #2,
> i.e. to define the details of the portfolio of what we can offer. The
> example of details was illustrated in https://lists.opnfv.org/g/opnfv
> -tsc/message/4845.
> - You can see the example of portfolio in https://lists.opnfv.org/g/o
> pnfv-tsc/message/4845 is getting the balance of equal importance of
> tools and reference stacks, and maximizes the value of what we can
> offer.
> - I changed the wording of 1st bullet point on slide #16 to reflect
> your point of #1 and #3. This is the Step #2, the immediate action
> point triggered by the strategic plan.
> - I also changed wording on other bullets on slide #16 to reflect
> some more details in my prior messages.
> - See attached deck v0.7.
> 
> Regarding your point #4, it is actually one of the following actions,
> i.e. to develop a marketing message to reflect our strategy. This is
> captured on the last bullet point on slide #16. Certainly, this is
> another action point we need to take after we agree on the strategy.
> 
> Regarding your point #2, yes, we need all TSC members to contribute
> to those actions, including:
> - defining the portfolio
> - defining the implementation and roadmap
> - working with MWG to define marketing message.
> 
> I also would expect that yourself will be able to help drive one of
> those actions, for example, working with MWG on marketing message to
> make sure that it gets known externally.
> 
> With those changes on slide #16 (in attached v0.7), hopefully it gets
> the level of clarity you expected, and we can move forward.
> 
> I am looking forward to your further contribution in executing this
> strategy, especially e.g. in working with MWG for our marketing
> message to get it known externally.
> 
> Thank you again
> Bin
> 
> -Original Message-
> From: Tim Irnich  
> Sent: Monday, November 26, 2018 6:37 AM
> To: HU, BIN ; AshYoung ; Georg Kunz
> ; Manuel Buil 
> Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
> Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan
> 
> Hi all,
> 
> having read the entire thread again this morning, I'd like to offer
> the following thoughts to hopefully help us make progress:
> 
> - We need to make sure the decision we take triggers action and
> change (since I think we all agree that we need to change something
> in OPNFV).
> To achieve this, we need to more clarity on the choices that are in
> front of us and their consequences. The current material does not do
> this clearly enough. It sort of says "we keep doing everything we
> already do and add a few things." IMHO it would be better is we
> described the change we want to achieve (i.e. in the form of "instead
> of [...] we want [...]").
> 
> - The fraction of TSC members that have actively participated in the
> discussion so far is way too low. I'd like to urge all TSC members to
> get engaged. Remember, we are elected by the OPNFV community, and
> this obl

Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan

[Manuel Buil]

Hey Bin,

Let me try to answer combining a bit both email threads. Thanks for
replying by the way!

In line with the ROI statement, as you were saying: "we are setting a
strategy based on potential addressable market and potential customer
needs, and our expertise and strength", I am afraid that the different
OPNFV product portfolio which you listed in the previous mail address
different markets and needs. This, in my opinion, will result in not
having a clear focus and thus still not increasing the ROI. I kind of
agree with Georg and Ash that so far we have probably been working on
too many areas (and maybe jumping onto the next new thing) and never
finished any completely. AFAIK, that's what our stakeholders claim,
right? Therefore, I am a bit afraid to jump onto the next new thing
with the devops line of work and that's why I was asking whether you
have some indications pointing to that market as an addressable one for
OPNFV (we definitely have skills in that area!).

My suggestion would be to focus on one thing which could result in 2 or
3 "products". After a few years, I wonder if our "original product" of
OPNFV (the reference patform) is still interesting for anyone
(specially stakeholders) and thus we should focus there. According to
Georg and Ash's mail, it seems they have some indications that it is
and we are not too late. Unfortunately, I can't really tell but I'll
try to investigate a bit :).

Regards,
Manuel

On Wed, 2018-11-21 at 21:34 +, HU, BIN wrote:
> Hi Georg and Ash,
>  
> Thank you very much for sharing your view and concern.
>  
> First of all, please refer to the message I sent earlier that tried
> to answer Manuel’s concerns. That message outlines the thought-
> process and my view to address Manuel’s 3 concerns.
>  
> Then back to your concern, i.e. integrated platform capability and
> compliance toolset that we are having now. I am really sorry that if
> there is a misunderstanding here. My view is that the offering (or
> the delivered product) will be defined in Step 2 in detail (as a
> Product Management function). My personal understanding is that what
> we can offer is a portfolio instead of a single product. Our OPNFV
> product portfolio may include:
> DevOps solution as outlined in User Story on slide #12.
> A packaged testing tool chain that can be offered standalone
> An Integrated Platform Capabilities grown from our DevOps pipeline
> (our original product)
> A conformance testing solution of the integrated platform (our CVP /
> Dovetail)
> A LaaS infrastructure solution
> Etc.
>  
> Just like a cloud provider has a portfolio of products and services,
> including fundamental IaaS, PaaS and SaaS solutions and services. So
> it is a portfolio.
>  
> Please note that I used the word “Product” to  illustrate what we can
> offer. It does not mean anything commercial.
>  
> Hopefully I clarified it. Of course, we cannot do it all at one time.
> so when we define product portfolio in Step 2, we also need to define
> the roadmap and timeline in long term view. Once we have the
> strategy, and then portfolio and roadmap, we will have a very good
> story to market it and attract investment and resources back, and of
> course the most important is to implement it with necessary
> resources.
>  
> Please let me know if you have more questions.
>  
> Thank you
> Bin
>  
> From: Georg Kunz  
> Sent: Wednesday, November 21, 2018 9:04 AM
> To: Ash Young ; HU, BIN 
> Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> Subject: RE: [opnfv-tsc] Discussion of OPNFV Strategic Plan
>  
> Hi Bin, Ash, all,
>  
> I’d like to pick up Manuel’s question about the value that our
> stakeholders would like to see and Ash’s point of building a
> reference platform: I believe that both aspects point towards the
> need for strengthening our compliance program – which is already
> based on a broad base of great test tools. OVP does not yet consume
> enough of the available tests for various reasons – having to admit
> this as a former Dovetail PTL. But I also think that we can still
> improve the capabilities of the OPNFV platform – by means of
> integration and closing gaps upstream. This is a requirement for
> adding additional tests covering NFV capabilities to the
> corresponding test tools and then eventually to OVP. Additional NFV
> capabilities we could think about include, for instance, L2GW, SR-
> IOV, LBaaS, FWaaS – in addition to emerging use cases like edge
> computing and cloud native computing, i.e., covering both OpenStack
> and K8s-based deployments.
>  
> So, in the context of the proposed DevOps approach, I am a little
> concerned that we lose track of enabling platform capabilities which
> are a requirement for the test tools and the compliance program. We
> need to make sure that this does not get out of focus too much (in my
> opinion). Specifically, if the main deliverable of OPNFV is an
> integration and CI framework, who do we consider performs the
> 

Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan

[Manuel Buil]

Hi Bin,
Here are some concerns I have, hopefully I am not the only one:
- By your slides I understand that you suggest to focus on doing work
which could be reused internally by the companies involved in OPNFV to
build their devops platform for NFV solutions. I wonder whether there
is a niche there and how the relevant internal departments of the
different companies (stakeholders in your slides) are currently doing
their NFV devops activities and whether they are happy or they are
looking for an alternative. Talking about open source communities, ODL
and Openstack are currently happy with their CI/CD solution and AFAIK,
not looking for something else (please correct me if I am wrong). Do we
have any sort of indication that this direction would be useful by
companies involved in OPNFV? Perhaps we all could talk internally to
check this and even gather some pain points with current tools and
desired features.
- I understand that the end goal of "the evolution of pharos lab" is
having a lab based on cloud services. I am a bit concerned about this
because to some extend we would lose control of our infrastructure and
will need to rely on what the providers give us (which most of the
times is abstracted) and perhaps we will lose geographical distribution
or the heterogeneity of it. Let alone having the possibility to connect
some exotic hardware to test edge use cases or IoT use cases (e.g.
having a pool of raspberries connected to our infra).
- Regarding the community growth, I think that attending developer-
oriented events will not be enough to gather new developers in OPNFV. I
am actually not sure how to address this problem which, in my opinion,
is getting acute. A big part of the people who stopped working in OPNFV
in the last months was not because they did not find OPNFV attractive
or cool but because their employers prioritized other communities (e.g.
ONAP) or some internal work over OPNFV. The best approach for me would
be to reach those employers (I guess they are the stakeholders in the
slides) and ask: what would you like to see in OPNFV in order to
increase the amount of resources you currently provide? or, what you
did not like in OPNFV which resulted in you decreasing the amount of
developers in OPNFV during the last months?. Perhaps the board could be
a good place to ask this?
It would be nice to know other poeple's opinion too! My view might be
completely wrong... :)
Regards,Manuel



On Tue, 2018-11-20 at 15:23 +, HU, BIN wrote:
> Hello community,
>  
> Thank you for the input and discussion of 
> OPNFV Strategy and Plan in the past 3 weeks, including in TSC
> discussion and Weekly Technical Discussions.
>  
> One critical role of TSC is to set up the direction and vision. So
> please continue your input and discussion in the mailing list in
> order to further mature the vision and strategy for the future. We
> target for TSC to approve the strategy
>  and vision next week Nov 27 as the 1st milestone, if we can mature
> the discussion. Then we can continue to work on next steps for
> details of deliverables that fit our resource availability and
> capability.
>  
> Thank you and I am looking forward to more inputs and discussions.
>  
> Bin
>  
> 
> 
> From: HU, BIN 
> 
> Sent: Tuesday, October 30, 2018 10:16 PM
> 
> To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> 
> Subject: Discussion of OPNFV Strategic Plan
> 
> 
>  
> Hello community,
>  
> At the 1st meeting of our new TSC today, we kicked off a discussion
> of
> OPNFV
>  Strategic Plan. The outline of the 
> OPNFV Strategic Plan includes:
> 
> First 3 agenda items outline the current status of OPNFV (slide #3-
> #8), which is a Problem Statement
> 
> Slide #7 is a summary of input from new TSC members.
> Then it talks about key objectives of evolving OPNFV (slide #10),
> focusing on
> 
> Stakeholder-oriented business opportunityTechnology
> excellenceCommunity growth
> Slide #11-#13 talks about stakeholder-oriented business opportunity,
> including
> 
> Why should we evolve to DevOps platformA user storyOPNFV new
> strategy, including addressing key roadblocks of other communities
> including ONAP, OpenStack and Acumos
> Slide #14 talks about technology excellence, such as cloud-native and
> microservices, edge, and a long-term vision of cloud-services based
> toolchainSlide #15 talks about community growthSlide #16 talks about
> the next step to develop a detailed work plan
>  
> We would like community involvement in discussing OPNFV strategic
> plan, and shaping OPNFV’s future. So we plan to discuss it in the
> Weekly Technical Discussion on Nov 8.
>  
> Meanwhile, please feel free to give any feedback via email so that
> the discussion on Nov. 8 will be more effective and productive.
>  
> Thank you and look forward to everyone’s involvement and feedback.
>  
> Bin
>  
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#4834): 

[opnfv-tech-discuss] No OPNFV-SFC meeting this week

[Manuel Buil]

Hey,

Due to the openstack summit, it is better if we cancel this week's SFC
meeting.

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-10-31-14.59.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hello,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-10-17-13.59.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Here they are:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2018/opnfv-p
haros.2018-10-03-13.01.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-09-19-13.59.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hello,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-09-12-14.02.html

Regards,
Manuel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22019): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22019
Mute This Topic: https://lists.opnfv.org/mt/25522002/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] [announce][election] Opening nominations for OPNFV Technical Steering Committee (TSC)

[Manuel Buil]

Hi,

I would like to nominate myself for the TSC of OPNFV.

** Name of the nominee: Manuel Buil
** The nominee's organization: SUSE
**A brief statement about the nominees qualifications and contributions
to the OPNFV community:
I have been involved in OPNFV since almost the start of it and I have
been the SFC PTL since Euphrates and commiter in releng-xci. 
My main focus has been in the successful integration and testing
between multiple open source components, so that basic and advanced
network functionality could be delivered in different installers 
I have participated quite actively in the community and giving multiple
talks in summits, being the mentor of interns and helping people of
other communities (e.g. ETSI or Openstack) understand the value of
OPNFV
I am also involved in other important open source communities as a
committer such as Openstack or ODL and will soon start working with OSM
Moving forward, I would like to bring new fresh ideas to OPNFV in order
to improve the current situation and make it a key community for other
open source communities which should see it as a cornerstone for devops
activities in NFV/SDN development

Regards,
Manuel
On Fri, 2018-08-31 at 09:57 -0700, David McBride wrote:
> Team,
> We've reached the halfway point for the nomination period. 
> Nominations will close in 1 week, on Sept 7 at 5 p.m. (PT).  So far,
> we have only 5 nominations.  Keep in mind that we need to elect 15
> people to the TSC, so keep those nominations coming!
> 
> David
> 
> On Wed, Aug 29, 2018 at 8:47 AM David McBride  on.org> wrote:
> > Team,
> > I'm surprised that nominations have been open for 5 days and I've
> > yet to see a single nomination.  Someone needs to break the ice and
> > get this started.  Nominations close Sept 7.  Thanks.
> > 
> > David
> > On Fri, Aug 24, 2018 at 10:47 AM David McBride  > ation.org> wrote:
> > > Team,
> > > Today, we begin nominations for a new TSC, consisting of 15
> > > members, in accordance with the Community Election Procedures. 
> > > 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.  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.
> > > 
> > > 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
> > > You may nominate yourself, or someone else.  Remember that both
> > > you and the person nominated must be on the active contributor
> > > list with 20 or more contributions.
> > > If you nominate someone else, I will confirm with that person
> > > that they accept the nomination.Announce the nomination with a
> > > "reply all" to this email prior to 5 p.m. (PT), Sept 7.  Please
> > > include the following information:Name of the nomineeThe
> > > nominee's organizationA brief statement about the nominees
> > > qualifications and contributions to the OPNFV
> > > community.Nominations close at 5 p.m. (PT) on Sept 7.  See the
> > > entire election schedule here.As nominees are accepted, I will
> > > post the nominee information on this page.
> > > 
> > > Thank you for your participation in this important activity for
> > > the OPNFV community.  Please let me know if you have

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-08-29-13.59.html

Regards,
Manuel

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

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-08-08-14.00.html

Regards,
Manuel

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

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week.
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-08-01-14.01.html id="-x-evo-selection-start-marker">

Regards,
Manuel

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

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-07-18-14.01.html

Regards,
Manuel

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

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-07-11-14.01.html

Regards,
Manuel

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

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs from this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-06-27-14.00.html

Regards,
Manuel

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

View/Reply Online (#21477): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/21477
Mute This Topic: https://lists.opnfv.org/mt/22723484/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] [announce] moving on....

[Manuel Buil]

ooh :(

It was great working with you and you should be proud of the work you
did in OPNFV! I really hope you are not going too far ;)

All the best!
Manuel

On Sun, 2018-06-17 at 12:31 -0700, Raymond Paik wrote:
> All, 
> > I shared this news with some of the community members over the past
several days, and I wanted to notify the rest of the community.
> 
> > > > > > I recently made a difficult decision to pursue a new opportunity
outside of the LF.  Having been involved in OPNFV since the formation
days, the thought of leaving the community isn't easy.  This is
especially the case since I just spent the entire week with many
community members at ETSI during the Plugfest.  I was again reminded
that I'm part of a wonderful & motivated community.
> 
> > > My last day at the Linux Foundation is on June 22nd, and I'm working
with both Phil & Heather on transition plans so that things don't get
dropped.  
> 
> > > > I sincerely hope that our paths will cross again.  I'm still going to
be involved in open source software, so I'm definitely not going too
far.  Wherever and whenever our paths cross, I hope we can share a
drink soon
> 
> Regards, 
> 
> Ray
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-06-13-14.00.html

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-05-23-14.01.html

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs from this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-05-16-14.00.txt

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-05-09-14.02.html

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-05-02-14.01.html

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

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

Hi,

Here are this week's MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-04-25-14.02.html

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-04-18-14.01.html

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

[opnfv-tech-discuss] SFC weekly meeting MoMs

[Manuel Buil]

Hello,

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-04-11-14.01.html

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-04-04-14.03.html

Regards,
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] [OPNFV Helpdesk #54009] [xci] Committer Promotions for releng-xci

[Manuel Buil via RT]

Hi,

I did not get the invitation either.

Thanks,
Manuel

On Sun, 2018-03-25 at 23:05 -0400, periyasamy.palanis...@ericsson.com
via RT wrote:
> Hi Aric,
> 
> Can you send me the invite again ?
> I have somehow lost the email.
> 
> Thanks,
> Periyasamy
> 
> -Original Message-
> From: Aric Gardner via RT [mailto:opnfv-helpdesk@rt.linuxfoundation.o
> rg] 
> Sent: Friday, March 23, 2018 7:56 AM
> To: Fatih Degirmenci <fatih.degirme...@ericsson.com>
> Cc: david.blaisonn...@orange.com; mb...@suse.com; opnfv-tech-discuss@
> lists.opnfv.org; opnfv-...@lists.opnfv.org; Periyasamy Palanisamy  riyasamy.palanis...@ericsson.com>; wutianw...@huawei.com
> Subject: [OPNFV Helpdesk #54009] [xci] Committer Promotions for
> releng-xci
> 
> Hi Fatih,
> 
> Invitations have been sent out.
> 
> Regards,
> Aric
> 
> 
> On Fri Mar 23 10:13:34 2018, fatih.degirme...@ericsson.com wrote:
> > 
> > Hi,
> > 
> > I would like to inform the TSC that Tianwei, Manuel, Periyasamy,
> > and 
> > David have been promoted as committers to XCI.
> > You can see the nomination statements and the voting on Gerrit.
> > 
> > https://gerrit.opnfv.org/gerrit/#/q/status:merged+project:releng-
> > xci+topic:xci-committer-promotion-skip-verify
> > 
> > I also want to take this opportunity to thank everyone for their 
> > contributions, support, and interest into XCI. Without them, XCI 
> > wouldn’t be where it is today.
> > Much more and even better things are coming so please stay tuned.
> > 
> > Helpdesk,
> > 
> > Please grant committer rights to new XCI committers on Gerrit
> > releng- 
> > xci project.
> > 
> > /Fatih
> > 
> > From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of
> > Fatih 
> > Degirmenci <fatih.degirme...@ericsson.com>
> > Date: Wednesday, 21 March 2018 at 09:01
> > To: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech- 
> > disc...@lists.opnfv.org>
> > Subject: [opnfv-tech-discuss] [xci] Committer Nominations for
> > releng- 
> > xci
> > 
> > Hi,
> > 
> > As approved by TSC on 2017-12-12 [1], it is my pleasure to
> > nominate 
> > the XCI contributors listed below as committers to releng-xci
> > Gerrit 
> > project.
> > XCI committers, please find the nomination statements on Gerrit 
> > changes linked below and cast your vote; +1/-1, directly on Gerrit.
> > 
> > Tianwei Wu: https://gerrit.opnfv.org/gerrit/#/c/53885/
> > Manuel Buil: https://gerrit.opnfv.org/gerrit/#/c/53887/
> > Periyasamy Palanisamy: https://gerrit.opnfv.org/gerrit/#/c/53889/
> > David Blaisonneau: https://gerrit.opnfv.org/gerrit/#/c/53891/
> > 
> > If the voting ends positively, I’ll inform the TSC regarding the 
> > promotions and ask helpdesk to grant committer rights in releng-
> > xci 
> > Gerrit project to them.
> > [1] http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-
> > meeting.2017-12-12-14.01.html
> > 
> > /Fatih
> 
> 
> 
> 
> 

___
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 Helpdesk #54009] [xci] Committer Promotions for releng-xci

[Manuel Buil]

Hi,

I did not get the invitation either.

Thanks,
Manuel

On Sun, 2018-03-25 at 23:05 -0400, periyasamy.palanis...@ericsson.com
via RT wrote:
> Hi Aric,
> 
> Can you send me the invite again ?
> I have somehow lost the email.
> 
> Thanks,
> Periyasamy
> 
> -Original Message-
> From: Aric Gardner via RT [mailto:opnfv-helpdesk@rt.linuxfoundation.o
> rg] 
> Sent: Friday, March 23, 2018 7:56 AM
> To: Fatih Degirmenci <fatih.degirme...@ericsson.com>
> Cc: david.blaisonn...@orange.com; mb...@suse.com; opnfv-tech-discuss@
> lists.opnfv.org; opnfv-...@lists.opnfv.org; Periyasamy Palanisamy  riyasamy.palanis...@ericsson.com>; wutianw...@huawei.com
> Subject: [OPNFV Helpdesk #54009] [xci] Committer Promotions for
> releng-xci
> 
> Hi Fatih,
> 
> Invitations have been sent out.
> 
> Regards,
> Aric
> 
> 
> On Fri Mar 23 10:13:34 2018, fatih.degirme...@ericsson.com wrote:
> > 
> > Hi,
> > 
> > I would like to inform the TSC that Tianwei, Manuel, Periyasamy,
> > and 
> > David have been promoted as committers to XCI.
> > You can see the nomination statements and the voting on Gerrit.
> > 
> > https://gerrit.opnfv.org/gerrit/#/q/status:merged+project:releng-
> > xci+topic:xci-committer-promotion-skip-verify
> > 
> > I also want to take this opportunity to thank everyone for their 
> > contributions, support, and interest into XCI. Without them, XCI 
> > wouldn’t be where it is today.
> > Much more and even better things are coming so please stay tuned.
> > 
> > Helpdesk,
> > 
> > Please grant committer rights to new XCI committers on Gerrit
> > releng- 
> > xci project.
> > 
> > /Fatih
> > 
> > From: <opnfv-tech-discuss-boun...@lists.opnfv.org> on behalf of
> > Fatih 
> > Degirmenci <fatih.degirme...@ericsson.com>
> > Date: Wednesday, 21 March 2018 at 09:01
> > To: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech- 
> > disc...@lists.opnfv.org>
> > Subject: [opnfv-tech-discuss] [xci] Committer Nominations for
> > releng- 
> > xci
> > 
> > Hi,
> > 
> > As approved by TSC on 2017-12-12 [1], it is my pleasure to
> > nominate 
> > the XCI contributors listed below as committers to releng-xci
> > Gerrit 
> > project.
> > XCI committers, please find the nomination statements on Gerrit 
> > changes linked below and cast your vote; +1/-1, directly on Gerrit.
> > 
> > Tianwei Wu: https://gerrit.opnfv.org/gerrit/#/c/53885/
> > Manuel Buil: https://gerrit.opnfv.org/gerrit/#/c/53887/
> > Periyasamy Palanisamy: https://gerrit.opnfv.org/gerrit/#/c/53889/
> > David Blaisonneau: https://gerrit.opnfv.org/gerrit/#/c/53891/
> > 
> > If the voting ends positively, I’ll inform the TSC regarding the 
> > promotions and ask helpdesk to grant committer rights in releng-
> > xci 
> > Gerrit project to them.
> > [1] http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-
> > meeting.2017-12-12-14.01.html
> > 
> > /Fatih
> 
> 
> 
> 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] SFC breakout session

[Manuel Buil]

Hi

For anyone interested in the OPNFV-SFC breakout session, we are in
Silver Laker A room

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

[opnfv-tech-discuss] SFC weekly MoMs

[Manuel Buil]

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-03-21-15.03.html

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

[opnfv-tech-discuss] SFC weely MoMs

[Manuel Buil]

Here are the MoMs for this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-02-28-15.02.html

Regards,
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] Problems with sfc - functest integration (mater branch)

[Manuel Buil]

Hello David,

Yes, it is fixed now. Functest guys are aware of the integration points sfc has 
with them and when the API changes in functest side, they are also creating a 
patch in the SFC repo.

-Manuel

On Wed, 2018-02-28 at 17:18 +0100, Cedric OLLIVIER wrote:
> Hello David,
> 
> > We have worked hard to clean the interfaces between Functest, SFC and
SDNVPN.
> > It remains from our side to add few remaining docstrings to complete
the API docs.
> 
> Cédric
> 
> > 2018-02-28 17:12 GMT+01:00 David McBride <dmcbr...@linuxfoundation.or
g>:
> > Manuel,
> > Did this resolve your issue?  Thanks.
> > 
> > David
> > 
> > 
> > > > > > On Wed, Feb 21, 2018 at 2:49 AM, Manuel Buil <mb...@suse.com>
wrote:
> > > 
> > > 
> > > 
> > > Hi Juha,
> > > 
> > > Thanks! We will try today :)
> > > 
> > > Regards,
> > > Manuel
> > > 
> > > > > > On Wed, 2018-02-21 at 10:35 +, Kosonen, Juha (Nokia -
FI/Espoo) wrote:
> > > > 
> > > > Hi Dimitris & Manuel
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > > > > > The name of credential file was changed few 
> > > > > > > > > > > > > > > > weeks back (https:/
/gerrit.opnfv.org/gerrit/#/c/51283/), the new name is
"env_file"
(https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751).
> > > > 
> > > > 
> > > > 
> > > > As a such CONST is still there but you need to change 
> > > > 
> > > > 
> > > > 
> > > > os_env_file=CONST.__getattribute__('openstack_creds')
> > > > 
> > > > 
> > > > 
> > > > to
> > > > 
> > > > 
> > > > 
> > > > os_env_file=getattr(CONST, 'env_file')
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Regards,
> > > >     JK
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > > > > > From: 
> > > > > > > > > > > > > > > > opnfv-tech-discuss-boun...@lists.opnfv.org 
> > > > > > > > > > > > > > > >  on behalf of Manuel Buil <mbuil@
suse.com>
> > > > 
> > > > Sent: Wednesday, February 21, 2018 11:43
> > > > 
> > > > To: OPNFV-TECH-DISCUSS OPNFV
> > > > 
> > > > > > > > Subject: [opnfv-tech-discuss] Problems with sfc - functest
integration (mater branch)
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hey functest guys,
> > > > 
> > > > 
> > > > 
> > > > > > > > We need again help with funcetst-sfc integration because there
is
> > > > 
> > > > > > > > something broken now related to the removal of the CONST module
from
> > > > 
> > > > your repo. This is our script:
> > > > 
> > > > 
> > > > 
> > > > > > > > https://github.com/opnfv/sfc/blob/master/sfc/lib/openstack_util
s.py
> > > > 
> > > > 
> > > > 
> > > > In that script, we used to fetch several things with
> > > > 
> > > > CONST.__getattribute__:
> > > > 
> > > > 
> > > > 
> > > > os_env_file=CONST.__getattribute__('openstack_creds'))
> > > > 
> > > > CONST.__getattribute__('EXTERNAL_NETWORK')
> > > > 
> > > > CONST.__getattribute__('OS_AUTH_URL')
> > > > 
> > > > CONST.__getattribute__('OS_PASSWORD')
> > > > 
> > > > 
> > > > 
> > > > We tried to "s/CONST.__getattribute__/env.get" but
> > > > 
> > > > env.get('openstack_creds') returns None.
> > > > 
> > > > 
> > > > 
> > > > We were checking your patch:
> > > > 
> > > > 
> > > > 
> > > > https://gerrit.opnfv.org/gerrit/#/c/52221/4
> > > > 
> > > > 
> > > > 
> > > > > > > > And we realized that some of those parameters are now gone, so
we
> &

[opnfv-tech-discuss] Confluence license expired

[Manuel Buil]

Hey,

I tried to edit the https://wiki.lfnetworking.org wiki and I got:

Your license has expired

This Confluence site is running under an evaluation license which has
expired. This means you will no longer be able to add or edit content
on the site. You will, however, continue to be able to browse existing
content.

If you have enjoyed using Confluence, please consider purchasing it
today.
Purchasing Confluence allows you to continue using the software
indefinitely, and also entitles you to a year of upgrades at no extra
cost.
If you need more time, you may extend your evaluation via your My
Atlassian account, or please contact us if you have any questions.

Is it only me?

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

[opnfv-tech-discuss] Problems with sfc - functest integration (mater branch)

[Manuel Buil]

Hey functest guys,

We need again help with funcetst-sfc integration because there is
something broken now related to the removal of the CONST module from
your repo. This is our script:

https://github.com/opnfv/sfc/blob/master/sfc/lib/openstack_utils.py

In that script, we used to fetch several things with
CONST.__getattribute__:

os_env_file=CONST.__getattribute__('openstack_creds'))
CONST.__getattribute__('EXTERNAL_NETWORK')
CONST.__getattribute__('OS_AUTH_URL')
CONST.__getattribute__('OS_PASSWORD')

We tried to "s/CONST.__getattribute__/env.get" but
env.get('openstack_creds') returns None.

We were checking your patch:

https://gerrit.opnfv.org/gerrit/#/c/52221/4

And we realized that some of those parameters are now gone, so we
wondered how should we do it now. We were checking your documented API:

http://functest.readthedocs.io/en/latest/apidoc/functest.html

However, we cannot see the functest.utils package there (CONST and env
belong to that), so we are a bit lost about what needs to be changed on
our side. We guess we must be using the functest API again in a
wrong/not-supported-anymore way :(. Any link or any explanation which
shows us how to do it properly will be appreciated.

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

[opnfv-tech-discuss] SFC Weekly MoMs

[Manuel Buil]

Hello,

Here are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-02-07-14.59.html

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

[Manuel Buil]

Hi Georg,

I think your proposal could be a good solution!! Having an API which
guarantees us some stability will surely solve the problems I
described. I am not sure if this will be too much effort for the
testing frameworks though and how the API model could be developed.

Regards,
Manuel

On Fri, 2018-02-02 at 14:42 +, Georg Kunz wrote:
> 
> 
> Hi all,
>  
> > > In the context of this discussion I am wondering if one of the
official goals of Functest is to provide common functionality to
support developers in OPNFV to write functional
> > >  tests? That was my understanding, but I might be wrong. In any case,
the Functest team along with the broader community should have a
clear common understanding of this.
>  
> > > Assuming this is the case, then the functionality which Functest
provides constitutes an API. Typically, APIs exhibit some kind of
stability along with some kind of deprecation
> >  process. It would in this case be beneficial for the broader
community if such processes are defined and known.
>  
> > > If Functest is not considered a framework providing common
functionality, well, then it is indeed a problem of SFC. However, I
do not consider this a valuable approach because
> > > >  it might just result in every project creating similar code for the
same tasks, e.g., measuring execution times as in Manuel’s case.
Moreover, Brian’s statement that he is trying to avoid using Functest
functionality in his projects doesn’t really feel right
>  from a community perspective…
>  
> Just my two cents as an observer.
>  
> Best regards
> Georg
>  
>  
> 
> 
> 
> > > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-d
iscuss-boun...@lists.opnfv.org]
> On Behalf Of cedric.olliv...@orange.com
> 
> Sent: Friday, February 02, 2018 3:25 PM
> 
> > > To: Manuel Buil <mb...@suse.com>; OPNFV-TECH-DISCUSS OPNFV 
> 
> > Subject: Re: [opnfv-tech-discuss] Could ways of working with testing
frameworks be improved when working with master?
> 
> 
> 
> 
>  
> Hello Manuel,
>  
> > In case of Functest, we are simply improving our code that why we are
removing uncovered obsolete (and unused internally) functions.
>  
> > As we take care of pylint output and coverage, we should stop
maintaining modules/functions which are out of our standards and
> unused by Functest.
> https://git.opnfv.org/functest/tree/tox.ini
>  
> > It’s well known that we are getting rid of openstack utils to
leverage on snaps and we are removing unused functest utils
> > We have worked on SDNVPN about that point before and we should apply
the same rules for SFC.
> I don’t understand why Functest should host functions needed by SFC.
> 
>  
> > > In fact this issue is on the client side (SFC) which still uses
obsolete Functest functions and your email seems asking to block
innovation.
> > I don’t think it’s an issue regarding APEX master or XCI for which
this global improvement initiated from E is very helpful.
>  
> > Be free to reuse this method in your tree as it could have belong to
instead.
>  
> Cédric
>  
> 
> 
> De :
> > opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss
-boun...@lists.opnfv.org]
> De la part de Manuel Buil
> 
> Envoyé : vendredi 2 février 2018 13:00
> 
> À : OPNFV-TECH-DISCUSS OPNFV
> 
> > Objet : [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/o
pnfv/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 achie

Re: [opnfv-tech-discuss] Could ways of working with testing frameworks be improved when working with master?

[Manuel Buil]

Hi Cedric,

I probably expressed myself wrongly since you understood that I intent
to block innovation and host SFC functions in functest but that is not
my intention. My objective with this mail is to check if there exists
(perhaps not), an efficient way for testing frameworks to communicate
in advance important changes which will break things in the projects
using those frameworks. I have a very good example: functest warned us
during the Euphrates cycle that openstack_utils was not going to be
maintained anymore and that we should stop using that and migrate to an
alternative during the Fraser development cycle. You guys even
suggested us an alternative (SNAPs). That was really helpful and we
were able to plan the task accordingly in our SFC backlog and right now
we are 100% compatible with SNAPs. Note that as far as I know, you
haven't removed the openstack_utils yet (or at least we were able to
use it while doing the migration).

However, during the last weeks, some functest changes broke our testing
(apart from that function I mentioned as an example):

* It seems like the openrc file changed the name in the functest
container and /home/opnfv/functest/conf/openstack.creds does not work
anymore
* TEST_DB_URL is now an environment variable and cannot be consumed
from the functest config file

To understand how to fix those, we had to go into the IRC channel and
ping you. If this is only SFC guys doing it, I guess we could continue
with option C, but if now more users start to work on master (XCI and
APEX), I suspect the number pings you will receive will increase. And I
guess the same will happen with yardstick, that's why I don't think
this is a SFC <--> Functest issue but a more general ways of working
issue.

Regards,
Manuel



On Fri, 2018-02-02 at 14:24 +, cedric.olliv...@orange.com wrote:
> 
> 
> Hello Manuel,
>  
> > In case of Functest, we are simply improving our code that why we are
removing uncovered obsolete (and unused internally) functions.
>  
> > As we take care of pylint output and coverage, we should stop
maintaining modules/functions which are out of our standards and
> unused by Functest.
> https://git.opnfv.org/functest/tree/tox.ini
>  
> > It’s well known that we are getting rid of openstack utils to
leverage on snaps and we are removing unused functest utils
> > We have worked on SDNVPN about that point before and we should apply
the same rules for SFC.
> I don’t understand why Functest should host functions needed by SFC.
> 
>  
> > > In fact this issue is on the client side (SFC) which still uses
obsolete Functest functions and your email seems asking to block
innovation.
> > I don’t think it’s an issue regarding APEX master or XCI for which
this global improvement initiated from E is very helpful.
>  
> > Be free to reuse this method in your tree as it could have belong to
instead.
>  
> Cédric
>  
> 
> 
> > > De : opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-di
scuss-boun...@lists.opnfv.org]
> De la part de Manuel Buil
> 
> Envoyé : vendredi 2 février 2018 13:00
> 
> À : OPNFV-TECH-DISCUSS OPNFV
> 
> > Objet : [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/c6092
cb676363d89f366dc9a416ba6c53eeea33f#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:
x

[opnfv-tech-discuss] Could ways of working with testing frameworks be improved when working with master?

[Manuel Buil]

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.co
m/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

[opnfv-tech-discuss] SFC weekly meeting MoMs

[Manuel Buil]

Hi,

Here are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-01-31-14.59.html

Regards,
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

[Manuel Buil]

Hello Tim,

The OPNFV-SFC project has already volunteered to be part of that booth
and our proposal seems aligned with your third idea. We would like to
explain our cross community CI strategy based on XCI and show a demo of
the first and second phase in that strategy, i.e. the integration of
our scenarios with XCI and its automatic deployment and testing through
Functest. All components in the deployment based on the master branch
of OpenStack, OPNFV and ODL. Note that our roadmap for 2018 includes
the integration with other LF projects such as fd.io (and perhaps ONAP
if they develop any SFC integration which is missing so far). Any
feedback on our proposal or help would be really appreciated!

Regards,
Manuel




On Fri, 2018-01-26 at 09:41 +, 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 cycleUse 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-d
iscuss-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
i...@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
> 
> Mobile: +1.917.282.0960  Skype: wick.brandon
> 
> 
> 
> Email / Google Talk: 
> bw...@linuxfoundation.org
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> 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

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

Hi,

Here is the link to the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-01-24-15.01.html

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

[opnfv-tech-discuss] SFC Weekly MoMs

[Manuel Buil]

Hello,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2018/opnfv-sfc.
2018-01-10-15.01.html

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

[opnfv-tech-discuss] MoMs SFC weekly

[Manuel Buil]

Hi,

Here are the MoMs of this week's meeting

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-12-20-15.01.html

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

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

HI,

Here are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-12-13-14.59.html

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

[opnfv-tech-discuss] MoMs SFC weekly meeting

[Manuel Buil]

Hi,

Not many updates this time:  http://ircbot.wl.linuxfoundation.org/meeti
ngs/opnfv-sfc/2017/opnfv-sfc.2017-11-29-14.58.html

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

[opnfv-tech-discuss] MoMs SFC weekly

[Manuel Buil]

Hi,

Here are the MoMs of this week's weekly:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-11-22-15.00.html

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

[opnfv-tech-discuss] SFC weekly meeting MoMs

[Manuel Buil]

Hi,

Here are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-11-15-15.01.html

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

[opnfv-tech-discuss] SFC MoMs weekly

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-11-08-14.59.html

Regards,
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] 回复： SFC

[Manuel Buil]

Good, Euphrates also brings a lot of new things and bug fixes, so I
think it makes sense to try the newest OPNFV.

If you use XCI as installer, note that it will create the controller,
jumphost and compute nodes as VMs using OpenStack Bifrost, so you will
not need virtualbox to do that as xci does it for you.

Regards,
Manuel

On Wed, 2017-11-08 at 14:57 +0800, 繁星 wrote:
> > > > Hi,I check the resources ,and they are enough.I use virtualbox to
install VM to build the environment, using three nodes, a control
node and two compute nodes, and the configuration of all VMs are 16G
RAM and 100G hard drive storage.
> > Now,I move to the newer OPNFV Euphrates release,and I hope the same
problem will not happen.
> Thank you for your advice!!!
> 
> 
> -- 原始邮件 --
> > 发件人: "Manuel Buil";<mb...@suse.com>;
> 发送时间: 2017年11月8日(星期三) 凌晨0:30
> > > 收件人: "繁星"<2846356...@qq.com>;"opnfv-tech-discuss"<opnfv-tech-discuss@
lists.opnfv.org>;
> 
> 主题: Re: [opnfv-tech-discuss] SFC
> 
> 
> Hi,
> 
> Could you check if you are running out of resources (e.g. memory)?
> 
> > Anyway, it would be easier for us if you move to the newer OPNFV
Euphrates release:
> 
> https://wiki.opnfv.org/display/sfc/Deploy+OPNFV+SFC+scenarios
> 
> Regards,
> Manuel
> 
> On Tue, 2017-11-07 at 15:52 +0800, 繁星 wrote:
> > > > Hello,When I installed and deployed the Danube 3.0 by using
Fuel,the following problems arose:
> > Deployment has failed. All nodes are finished. Failed tasks:
> > Task[odl_remove_hiera/9], 
> > Task[odl_remove_hiera/8],
> > Task[odl_remove_hiera/7] Stopping the deployment process!
> > 
> > I don't know the reasons,can you give me some advice?thank you!!! 
> > 
> > ___
> > opnfv-tech-discuss mailing list
> > opnfv-tech-discuss@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] SFC

[Manuel Buil]

Hi,

Could you check if you are running out of resources (e.g. memory)?

Anyway, it would be easier for us if you move to the newer OPNFV
Euphrates release:

https://wiki.opnfv.org/display/sfc/Deploy+OPNFV+SFC+scenarios

Regards,
Manuel

On Tue, 2017-11-07 at 15:52 +0800, 繁星 wrote:
> > Hello,When I installed and deployed the Danube 3.0 by using Fuel,the
following problems arose:
> Deployment has failed. All nodes are finished. Failed tasks:
> Task[odl_remove_hiera/9], 
> Task[odl_remove_hiera/8],
> Task[odl_remove_hiera/7] Stopping the deployment process!
> 
> I don't know the reasons,can you give me some advice?thank you!!! 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] No SFC weekly meeting this week

[Manuel Buil]

Hello,

I can't host today's weekly meeting, sorry :(. If there is a topic
which cannot wait, let's discuss it over the mailing list.

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

[opnfv-tech-discuss] MoMs from the SFC weekly meeting

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-10-18-14.02.html

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

[opnfv-tech-discuss] SFC weekly call cancelled

[Manuel Buil]

Hey,

I have an important meeting today at the same time, so I need to cancel
this week's meeting. I think there is not much to update since all of
us are working on fixing bugs for ODL, OVS or tacker. If there is
something which cannot wait until next week, let's try to discuss it
over the mailing list.

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

[opnfv-tech-discuss] Problems deploying xci

[Manuel Buil]

Hello,

I tried today to get familiar with the releng-xci master branch but I
was very unlucky because I tried two times and both failed.

First time I tried with flavor= aio and this is the result:

https://hastebin.com/suseyojepu.md

Then I tried with flavor = noha and it failed before:

https://hastebin.com/oyejesafos.sm

After this second try, I ran bifrost-provision.sh alone to see if I was
getting more information but I could not see anything extra

https://hastebin.com/amaqelafij.coffeescript

Any idea?

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

[opnfv-tech-discuss] MoMs SFC weekly meeting

[Manuel Buil]

Hi,

These are the MoMs of this week's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-10-04-14.00.html

Regards,
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] xci authentication problem

[Manuel Buil]

Hey Markos,

I am trying with noha

Regards,
Manuel

On Fri, 2017-09-29 at 16:33 +0100, Markos Chandras wrote:
> On 29/09/17 15:23, Manuel Buil wrote:
> > 
> > Hey guys,
> > 
> > After deploying xci, I have two different openrc files. One in the
> > opnfv vm:
> > 
> Hi Manuel,
> 
> What XCI flavor is this?
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] xci authentication problem

[Manuel Buil]

Hey guys,

After deploying xci, I have two different openrc files. One in the
opnfv vm:

https://hastebin.com/hizuvipiva.bash

and one in the utility container in the controller VM:

https://hastebin.com/ayafabevan.bash

The big difference is the OS_PASSWORD value. If I source the first one,
and do "openstack server list" the result is:

The request you have made requires authentication. (HTTP 401) (Request-
ID: req-3a8f9b3b-c1e7-4e7c-9fc3-528e81894dbd)

If I use that same openrc but change OS_PASSWORD to the value in the
second openrc, then it works, which means that the problem is the
password. I guess, my services are not using 'opnfv-secret-password' as
a password for their endpoints in keystone. Could you help me
understand what should I change so that my password uses the xci
generated one instead of the osa genereated one?

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

[opnfv-tech-discuss] SFC weeekly MoMs

[Manuel Buil]

Hi,

Here are the MoMs of today's weekly meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-09-27-14.00.html

Regards,
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] OPNFV Danube 3.0: Issue with two SFC's

[Manuel Buil]

Hey Srikanth,

You are not getting any classification rule because it can't find an
RSP, which means it was not able to create the chain. There is
something fishy going on and it should not be there if you do a
complete restart of ODL. To completely restart ODL, you must stop it,
remove the directories: snapshot, instances and journal. Then, you
should restart the OVSs (removing their conf.db database). If you are
using neutron v2, you must also restart neutron completely (database
included) because it keeps a journal and what breaks ODL, will again be
executed as soon as neutron detects that ODL is up.

Regards,
Manuel

On Fri, 2017-09-22 at 12:57 +, Srikanth Lingala wrote:
> 
> 
> Hi Manuel,
> > I started ODL cleanly. But, I observe the same issue. SFC Classifier
flows are adding, only when we have single Chain.
> > I wonder how functests are passing with the SFC usecase
‘sfc_two_chains_SSH_and_HTTP.py’ in different OPNFV labs.
>  
> > And also, now after cleaning up ODL, SFC flows are NOT adding with
table id 150 – 158. Those SFC flows are adding to table id 10.
> I observe no ERROR logs in ODL, but few WARNING logs.
>  
> Following are the ODL logs:
> While creating first chain ‘mychain1’: 
> tacker sfc-create --name mychain1 --chain testVNF1
> https://pastebin.com/JXDgitXD
>  
> While creating second chain ‘mychain2’: 
> tacker sfc-create --name mychain2 --chain testVNF2
> https://pastebin.com/CYaxYvtZ
>  
> While creating first classifier ‘myclass1’: 
> > tacker sfc-classifier-create --name myclass1 --chain mychain1 --match 
source_port=0,dest_port=80,protocol=6
> https://pastebin.com/Ly4Y2aSb
> Here, Classifier flow is NOT adding with tcp and dest_port=80.
>  
> While creating first classifier ‘myclass2’: 
> > tacker sfc-classifier-create --name myclass2 --chain mychain2 --match 
source_port=0,dest_port=22,protocol=6
> https://pastebin.com/iJJ2me1Y
> Here, Classifier flow is adding with tcp and dest_port=22.
>  
> Regards,
> Srikanth.
>  
> 
> 
> > From: Manuel Buil [mailto:mb...@suse.com] 
> 
> Sent: Friday, September 22, 2017 4:50 PM
> 
> > > > > To: Srikanth Lingala <srikanth.ling...@nxp.com>; sfc-dev@lists.openda
ylight.org; opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opn
fv.org
> 
> > Cc: Gorja Gorja <prasad.go...@nxp.com>
> 
> > Subject: Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two
SFC's
> 
> 
> 
> 
>  
> 
> > > Yes. You need to stop it, remove instances/ journal/ and snapshots/
and start it with bin/start clean. If I remember well, ODL Boron had
an issue when restarting it and
> >  connecting old OVS, so you might need to restart also the OVS
switches before starting ODL again.
> 
> 
> 
>  
> 
> 
> 
> Regards,
> 
> 
> 
> Manuel
> 
> 
> 
>  
> 
> 
> 
> On Fri, 2017-09-22 at 10:30 +, Srikanth Lingala wrote:
> 
> 
> 
> Hi Manuel,
> > So, If I restart the ODL and then add SFC and SFC Classifiers may fix
this issue?
>  
> Regards,
> Srikanth.
>  
> 
> 
> > From: Manuel Buil [mailto:mb...@suse.com]
> 
> 
> Sent: Friday, September 22, 2017 3:52 PM
> 
> > To: Srikanth Lingala <srikanth.ling...@nxp.com>;
> sfc-...@lists.opendaylight.org;
> opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org
> 
> > Subject: Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two
SFC's
> 
> 
> 
> 
>  
> 
> Hello Srikanth,
> 
> 
> 
>  
> 
> 
> 
> > > Danube is using ODL Boron which had some issues when removing the
classification rules. Unfortunately, those rules are not correctly
removed and that creates a small mess
> > >  which results in problems when creating new rules. You should not
see this problem if you have a clean ODL but if you have created
several classifiers and tried to remove them, you might see it.
> 
> 
> 
>  
> 
> 
> 
> Do you see any error in ODL logs when creating the classifier
> 
> 
> 
>  
> 
> 
> 
> Regards,
> 
> 
> 
> Manuel
> 
> 
> 
>  
> 
> 
> 
> On Fri, 2017-09-22 at 07:28 +, Srikanth Lingala wrote:
> 
> 
> 
> Hi,
> > I am using OPNFV Danube 3.0. I deployed one Openstack Controller with
ODL & Tacker and Openstack Compute through Fuel.
> I am trying to execute the usecase: sfc_two_chains_SSH_and_HTTP
> > When I create two chains, Classifier flow is missing in the compute
node.
> I executed below commands:
>  
> #> tacker vnfd-create --vnfd-file test-vnfd-1.yaml
> #> tacker vnfd-create --vnfd-file test-vnfd-2.yaml
> #> tacker vnf-create --name testVNF1 --vnfd-name test-vnfd-1
> #> tacker vnf-crea

Re: [opnfv-tech-discuss] VxLAN workaround for OPNFV Danube 3.0

[Manuel Buil]

Hi Srikanth,

It is still required.

Regards,
Manuel

On Sat, 2017-09-23 at 14:04 +, Srikanth Lingala wrote:
> 
> 
> Hi,
> > I am trying to implement SFC with Opendaylight is OPNFV Danube 3.0
release.
> > Is “VxLAN Workaround in Compute node” still required in OPNFV Danube
3.0 release also? Or ODL will take care of it.
> Anyone please confirm.
>  
> Regards,
> Srikanth.
> 
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two SFC's

[Manuel Buil]

Yes. You need to stop it, remove instances/ journal/ and snapshots/ and
start it with bin/start clean. If I remember well, ODL Boron had an
issue when restarting it and connecting old OVS, so you might need to
restart also the OVS switches before starting ODL again.

Regards,
Manuel

On Fri, 2017-09-22 at 10:30 +, Srikanth Lingala wrote:
> 
> 
> Hi Manuel,
> > So, If I restart the ODL and then add SFC and SFC Classifiers may fix
this issue?
>  
> Regards,
> Srikanth.
>  
> 
> 
> > From: Manuel Buil [mailto:mb...@suse.com] 
> 
> Sent: Friday, September 22, 2017 3:52 PM
> 
> > > > > To: Srikanth Lingala <srikanth.ling...@nxp.com>; sfc-dev@lists.openda
ylight.org; opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opn
fv.org
> 
> > Subject: Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two
SFC's
> 
> 
> 
> 
>  
> 
> Hello Srikanth,
> 
> 
> 
>  
> 
> 
> 
> > > Danube is using ODL Boron which had some issues when removing the
classification rules. Unfortunately, those rules are not correctly
removed and that creates a small mess
> > >  which results in problems when creating new rules. You should not
see this problem if you have a clean ODL but if you have created
several classifiers and tried to remove them, you might see it.
> 
> 
> 
>  
> 
> 
> 
> Do you see any error in ODL logs when creating the classifier
> 
> 
> 
>  
> 
> 
> 
> Regards,
> 
> 
> 
> Manuel
> 
> 
> 
>  
> 
> 
> 
> On Fri, 2017-09-22 at 07:28 +, Srikanth Lingala wrote:
> 
> 
> 
> Hi,
> > I am using OPNFV Danube 3.0. I deployed one Openstack Controller with
ODL & Tacker and Openstack Compute through Fuel.
> I am trying to execute the usecase: sfc_two_chains_SSH_and_HTTP
> > When I create two chains, Classifier flow is missing in the compute
node.
> I executed below commands:
>  
> #> tacker vnfd-create --vnfd-file test-vnfd-1.yaml
> #> tacker vnfd-create --vnfd-file test-vnfd-2.yaml
> #> tacker vnf-create --name testVNF1 --vnfd-name test-vnfd-1
> #> tacker vnf-create --name testVNF2 --vnfd-name test-vnfd-2
> #> tacker sfc-create --name mychain1 --chain testVNF1
> #> tacker sfc-create --name mychain2 --chain testVNF2
> > #> tacker sfc-classifier-create --name myclass1 --chain mychain1 --
match source_port=0,dest_port=80,protocol=6
>  
> > > When I execute the above command, I am not able to see classifier
flow in the compute node. The flow should be something similar to
below:
> # ovs-ofctl dump-flows br-int -O Openflow13 | grep tcp
> > > > > > cookie=0x1110010005970255, duration=121.077s, table=11, n_packets=0,
n_bytes=0, tcp,reg0=0x1,tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]-
>NXM_NX_NSH_C2[],push_nsh,load:0x1->NXM_NX_NSH_MDTYPE[],load:0x3-
>NXM_NX_NSH_NP[],load:0xc0a8001a->NXM_NX_NSH_C1[],load:0x255-
>NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI[],load:0x7b7b7b05-
>NXM_NX_TUN_IPV4_DST[],load:0x255->NXM_NX_TUN_ID[0..31],resubmit(,0)
>  
> > The above flow is not adding. But, when I tried the same with single
Chain, I am able to see the above flow.
>  
> Is there any issue with two chains?
>  
> Regards,
> Srikanth.
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 
> 
> 
> 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OPNFV Danube 3.0: Issue with two SFC's

[Manuel Buil]

Hello Srikanth,

Danube is using ODL Boron which had some issues when removing the
classification rules. Unfortunately, those rules are not correctly
removed and that creates a small mess which results in problems when
creating new rules. You should not see this problem if you have a clean
ODL but if you have created several classifiers and tried to remove
them, you might see it.

Do you see any error in ODL logs when creating the classifier

Regards,
Manuel

On Fri, 2017-09-22 at 07:28 +, Srikanth Lingala wrote:
> 
> 
> Hi,
> > I am using OPNFV Danube 3.0. I deployed one Openstack Controller with
ODL & Tacker and Openstack Compute through Fuel.
> I am trying to execute the usecase: sfc_two_chains_SSH_and_HTTP
> > When I create two chains, Classifier flow is missing in the compute
node.
> I executed below commands:
>  
> #> tacker vnfd-create --vnfd-file test-vnfd-1.yaml
> #> tacker vnfd-create --vnfd-file test-vnfd-2.yaml
> #> tacker vnf-create --name testVNF1 --vnfd-name test-vnfd-1
> #> tacker vnf-create --name testVNF2 --vnfd-name test-vnfd-2
> #> tacker sfc-create --name mychain1 --chain testVNF1
> #> tacker sfc-create --name mychain2 --chain testVNF2
> > #> tacker sfc-classifier-create --name myclass1 --chain mychain1 --
match source_port=0,dest_port=80,protocol=6
>  
> > > When I execute the above command, I am not able to see classifier
flow in the compute node. The flow should be something similar to
below:
> # ovs-ofctl dump-flows br-int -O Openflow13 | grep tcp
> > > > > > cookie=0x1110010005970255, duration=121.077s, table=11, n_packets=0,
n_bytes=0, tcp,reg0=0x1,tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]-
>NXM_NX_NSH_C2[],push_nsh,load:0x1->NXM_NX_NSH_MDTYPE[],load:0x3-
>NXM_NX_NSH_NP[],load:0xc0a8001a->NXM_NX_NSH_C1[],load:0x255-
>NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI[],load:0x7b7b7b05-
>NXM_NX_TUN_IPV4_DST[],load:0x255->NXM_NX_TUN_ID[0..31],resubmit(,0)
>  
> > The above flow is not adding. But, when I tried the same with single
Chain, I am able to see the above flow.
>  
> Is there any issue with two chains?
>  
> Regards,
> Srikanth.
> 
> 
> 
> 
> ___
> 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] OPNFV SFC MoMs week 38

[Manuel Buil]

Hello,

Here are the MoMs of this week:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-09-20-14.03.html

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

[opnfv-tech-discuss] SFC Weekly meeting MoMs

[Manuel Buil]

Hello,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-09-13-14.01.html

As promised, here are the rest of issues which we could not cover
during the call:

#info issue #2 The time window we use to check if VMs are up is a bit
small. We need to increase it
#info I created a patch for this ==> https://gerrit.opnfv.org/gerrit/#/
c/41853/

#info issue #3 We need to provide the neutron source port id to the
vnffgd 
#info I created a patch to fix that: https://gerrit.opnfv.org/gerrit/#/
c/41849/

#info issue #4 there is a bug fixed in Pike which does not allow to
have input_data in the vnffgd templates
#link https://bugs.launchpad.net/tacker/+bug/1675672
#info It is fixed for pike. We should backport it and test

#info issue #5 ==> The new alpine functest container is missing the
sshpass package. We need it to access the VMs created by the test
#info patch to fix it ==> https://gerrit.opnfv.org/gerrit/#/c/41857/

#info issue #6: it is not possible to set the insecure flag when
creating the vim in tacker, so we must have valid certificates when
contacting tacker

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

[opnfv-tech-discuss] MoMs SFC weekly (week 34)

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-08-23-14.00.html

Regards,
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] Delays due to Intel outage

[Manuel Buil]

Hello David, Mark,

Thanks for bringing this up Mark. SFC is also impacted by this outage
:(

Regards,
Manuel

On Tue, 2017-08-22 at 19:59 +, Beierl, Mark wrote:
> 
> Hello, David.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > > > I am sending this as a heads up.  There has been an outage in Intel
[1] since yesterday and it is causing a minor impact to StorPerf as
we have been without our primary development and CI pod since it
started.  Right now, I don't anticipate any problems with
>  the next milestone for StorPerf.
> 
> 
> 
> 
> 
> 
> 
> > If this lasts much longer, there may be other projects that are
impacted too.
> 
> 
> 
> 
> 
> 
> 
> [1] https://jira.opnfv.org/projects/INFRA/issues/INFRA-161
> 
> 
> 
> 
> 
> 
> 
> Regards,
> 
> 
> Mark
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Mark Beierl
> 
> SW System Sr Principal Engineer
> 
> 
> Dell EMC | Office of the CTO
> 
> 
> mobile +1 613 314 8106
> 
> 
> mark.bei...@dell.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] SFC weekly meeting MoMs week 33

[Manuel Buil]

Hi,

Here are the MoMs of today's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-
sfc.2017-08-16-14.00.html

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

[opnfv-tech-discuss] SFC weekly MoMs 9th August 2017

[Manuel Buil]

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-08-09-14.01.html
___
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] ODL target Release for Euphrates

[Manuel Buil]

Hello Morgan,

As far as I understood, the OPNFV release is only agreeing on the
openstack version. So I assume different projects can use different ODL
versions, or?

In SFC we are targetting ODL Nitrogen SR0. It will be officially
released on the 7th of September and we are currently using our OPNFV
tests to help them find bugs.

Regards,
Manuel

On Tue, 2017-08-08 at 15:29 +0800, jason wrote:
> > Hi Morgan,Daisy currently uses Carbon snapshot earlier than SR1 but
the target  is Carbon SR1.
> 
> 
> > On Aug 8, 2017 15:18,   wrote:
> >   
> > 
> > 
> >   
> >   
> > Hi,
> > 
> > 
> > 
> > I did not find the list of the target versions for the main
> > components integrated in Euphrates version.
> > 
> > > > it would make sense to explicitely reference them on one of the
wiki
> > pages dedicated to the release
> > https://wiki.opnfv.org/display/SWREL/Euphrates
> > 
> > 
> > 
> > In functest, we need to know it. 
> > 
> > Cedric consolidated Functest in order to manage properly the
> > upstream dependencies (including clients/tooling/lib needed for
> > > > testing relatively to upstream components) and introduced a
clean
> > packetization, which is key for an integration project.
> > 
> > 
> > 
> > At the moment, the only ODL version reference we found was
> > beryllium-sr4, which is pretty old.
> > 
> > 
> > 
> > According to
> > https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
> > 
> > scenario owners dealing with ODL are:
> > 
> > - Frank (Apex ∩ Fdio)
> > 
> > - Tim Inrich (Apex ∩ bgpvpn)
> > 
> > > > - Brady (not sure the page is up to date) / Manuel (Apex ∩
Sfc)
> > 
> > - Georg (not sure it is up to date) Apex ∩ gluon
> > 
> > - Tim Rozet (Other Apex scenarios)
> > 
> > - Ruan He (Compass ∩ moon)
> > 
> > - Justin (Other Compass scenarios)
> > 
> > - Zhiang (Daisy ∩ moon)
> > 
> > - Michael (Fuel/MCP)
> > 
> > 
> > 
> > could you confirm the target version for ODL?
> > 
> > 
> > 
> > 
> > 
> >   /Morgan
> > 
> > 
> > 
> > note: no scenario ODL with joid
> > referenced in the page.
> > 
> >   
> > 
> > 
> > 
> > > > > >  
___
__
> > 
> > > > Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
> > > > pas etre diffuses, exploites ou copies sans autorisation. Si vous
avez recu ce message par erreur, veuillez le signaler
> > > > a l'expediteur et le detruire ainsi que les pieces jointes. Les
messages electroniques etant susceptibles d'alteration,
> > > > Orange decline toute responsabilite si ce message a ete altere,
deforme ou falsifie. Merci.
> > 
> > > > This message and its attachments may contain confidential or
privileged information that may be protected by law;
> > > > they should not be distributed, used or copied without
authorisation.
> > > > If you have received this email in error, please notify the sender
and delete this message and its attachments.
> > > > As emails may be altered, Orange is not liable for messages that
have been modified, changed or falsified.
> > Thank you.
> > 
> > 
> > 
> > 
> > ___
> > 
> > opnfv-tech-discuss mailing list
> > 
> > opnfv-tech-discuss@lists.opnfv.org
> > 
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> > 
> > 
> 
> 
> ___
> 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] MoMs weekly meeting week 31

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-08-02-14.01.txt

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

[opnfv-tech-discuss] MoMs of the SFC meeting

[Manuel Buil]

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-07-26-14.00.html

Regards,
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] SFC Project

[Manuel Buil]

Is your ODL listening on: 192.168.0.9:8282?

Give me the output of:

curl -u admin:admin -H 'Content-type: application/json' -X GET http://1
92.168.0.9:8282/controller/nb/v2/neutron/networks

Regards,
Manuel


On Thu, 2017-07-20 at 14:06 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:
> Manuel,
> 
> I am deploying using fuel and ODL plug-in. You will find both files
> in  
> the attachement.
> 
> Regards,
> 
> Quoting "Manuel Buil" <mb...@suse.com>:
> 
> > 
> > Hi,
> > 
> > I just checked your logs. It seems the ml2_conf.ini file is wrong.
> > Are
> > you deploying openstack using fuel and ODL plug-in? Can you post:
> > 
> > /etc/neutron/neutron.conf
> > /etc/neutron/plugins/ml2/ml2_conf.ini
> > 
> > They are in the controller
> > 
> > Regards,
> > Manuel
> > 
> > On Thu, 2017-07-20 at 12:34 +0200,
> > andres.sanchez.ra...@estudiant.upc.edu wrote:
> > > 
> > > Good morning to both!
> > > 
> > > Manuel let me know if it is alright to post this issues on IRC
> > > channel  
> > > in case you are unable to help us! i am experiencing similar
> > > issues
> > > to  
> > > Pavan. I am doing the setup using just one controller-ODL-tacker
> > > and  
> > > one compute-Cinder. My compute has only 2 cpu cores and 8 GB
> > > memory  
> > > (maybe this is not enough to hold the scenario), i understand
> > > the  
> > > scenario consists of 2 SFs, 1 client and 1 server. I am only
> > > executing  
> > > sfc_two_chains_SSH_and_HTTP.py.
> > > 
> > > This is the relevant info of my sfc.log:
> > > 
> > > 2017-07-20 09:20:59,069 - ovs_logger - ERROR - list index out of
> > > range
> > > 2017-07-20 09:20:59,072 - sfc.lib.utils - INFO - This is the
> > > first_RSP:
> > > 2017-07-20 09:20:59,281 - ovs_logger - ERROR - list index out of
> > > range
> > > 2017-07-20 09:20:59,284 - sfc.lib.utils - INFO - This is the
> > > rsps:  
> > > [u'0x4e', u'0x4e']
> > > 2017-07-20 09:21:00,285 - sfc.lib.utils - INFO - classification
> > > rules
> > > updated
> > > 2017-07-20 09:21:00,286 - functest_utils - INFO -  
> > > wait_for_classification_rules(*( > >   
> > > object at 0x7f058c453750>,
> > > [<opnfv.utils.ssh_utils.ProxyHopClient  
> > > object at 0x7f059c25aed0>], 2), **{}) took: 1.40145111084 sec
> > > 2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Instance name
> > > and
> > > ip  
> > > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > > lgypmueg7aus:172.16.10.48
> > > 2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Waiting for
> > > instance  
> > > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > > lgypmueg7aus:172.16.10.48
> > > to  
> > > come up
> > > 2017-07-20 09:22:47,839 - sfc.lib.utils - INFO - Instance  
> > > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > > lgypmueg7aus:172.16.10.48  
> > > didn't come up
> > > 2017-07-20 09:22:47,840 - __main__ - ERROR - Exception when
> > > executing:  
> > > sfc_two_chains_SSH_and_HTTP
> > > 2017-07-20 09:22:47,840 - __main__ - ERROR - 'NoneType' object is
> > > not
> > > iterable
> > > .
> > > .
> > > .
> > > 2017-07-20 09:22:48,910 - __main__ - INFO - Results of test
> > > case  
> > > 'sfc_two_chains_SSH_and_HTTP - ODL-SFC tests':
> > > {'status': 'FAILED'}
> > > 
> > > 2017-07-20 09:22:49,308 - sfc.lib.cleanup - INFO - Removing sfc  
> > > classifier: 2c63594c-1266-4162-b159-cde4575d8fd7
> > > 2017-07-20 09:22:49,386 - sfc.lib.cleanup - INFO - Removing sfc  
> > > classifier: 873a693d-345f-4569-af73-4910b7a00b5d
> > > 2017-07-20 09:22:49,717 - sfc.lib.cleanup - INFO - Removing
> > > sfc:  
> > > 81debb08-a506-4ba9-bc13-4e3046f2b8e6
> > > 2017-07-20 09:22:49,783 - sfc.lib.cleanup - INFO - Removing
> > > sfc:  
> > > e5a2b2f1-e53c-4745-8e90-943cd1c16c2e
> > > 2017-07-20 09:22:50,147 - sfc.lib.cleanup - INFO - Removing
> > > vnf:  
> > > 4d837dae-d334-406f-8ce9-9c2997857838
> > > 2017-07-20 09:22:50,785 - sfc.lib.cleanup - INFO - Removing
> > > vnf:  
> > > d9ca5164-beb5-4ac6-89fc-c8feefec494a
> > > 2017-07-20 09:22:52,421 - sfc.lib.cleanup - INFO - Removing
> > > vnfd:  
> > > 33c9890a-4f22-4261-9351-be6376f41228
> > > 2017-07-20 09:22:52,467 - sfc.lib.clean

Re: [opnfv-tech-discuss] SFC Project

[Manuel Buil]

rt
> 2017-07-20 09:21:06.556 1011 ERROR
> networking_odl.ml2.network_topology  
>  _('Unable to find any valid segment in given context.'))
> 2017-07-20 09:21:06.556 1011 ERROR
> networking_odl.ml2.network_topology  
> ValueError: Unable to find any valid segment in given context.
> 2017-07-20 09:21:06.556 1011 ERROR
> networking_odl.ml2.network_topology
> 2017-07-20 09:21:06.561 1011 ERROR
> networking_odl.ml2.network_topology  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Unable to bind  
> port element for given host and valid VIF types:
>   hostname: node-25.domain.tld
>   valid VIF types: vhostuser, ovs
> 2017-07-20 09:21:06.562 1011 ERROR neutron.plugins.ml2.managers  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Failed to bind  
> port 826578fa-e3de-496e-8f4a-88bcd9b5288a on host node-
> 25.domain.tld  
> for vnic_type normal using segments [{'segmentation_id': None,  
> 'physical_network': u'physnet1', 'id':  
> u'c15cd96a-08c6-47ce-807f-91ced82ba3af', 'network_type': u'flat'}]
> 2017-07-20 09:21:06.563 1011 INFO neutron.plugins.ml2.plugin  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Attempt 2 to
> bind  
> port 826578fa-e3de-496e-8f4a-88bcd9b5288a.
> 
> Im attaching this log, take into account this test ran between
> 09:18  
> through 09:23 so maybe you can disregard the rest of the file.
> 
> Let me know what you think. Thanks in advance for your help.
> 
> Best regards,
> 
> Quoting "Manuel Buil" <mb...@suse.com>:
> 
> > 
> > Hi Pavan,
> > 
> > n_packets=0 means that no packets are matching the conditions. Is
> > this
> > the switch where the client that generates the traffic is connected
> > to?
> > 
> > Regards,
> > Manuel
> > 
> > On Thu, 2017-07-20 at 12:44 +0530, Pavan Gupta wrote:
> > > 
> > > Hi Manuel,Following is the output of the cvs-ofctl command. 
> > > 
> > > OFPST_FLOW reply (OF1.3) (xid=0x2):
> > >  cookie=0x1110010002420255, 
> > > duration=62656.965s, 
> > > table=11, 
> > > n_packets=0,
> > >  n_bytes=0, 
> > > tcp,
> > > reg0=0x1,
> > > tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],
> > > push_nsh,
> > > load:0x1->NXM_NX_NSH_MDTYPE[],
> > > load:0x3->NXM_NX_NSH_NP[],
> > > load:0xc0a80005->NXM_NX_NSH_C1[],
> > > load:0xf2->NXM_NX_NSP[0..23],
> > > load:0xff->NXM_NX_NSI[],
> > > load:0xb08->NXM_NX_TUN_IPV4_DST[],
> > > load:0xf2->NXM_NX_TUN_ID[0..31],
> > > resubmit(,0)
> > > > 
> > > > cookie=0x0, duration=67645.386s, table=11, n_packets=76029,
> > n_bytes=5979053, priority=0 actions=goto_table:21
> > > 
> > > 
> > > 
> > > Pavan
> > > > 
> > > > > 
> > > > > > 
> > > > > > On 19-Jul-2017, at 8:44 PM, Manuel Buil <mb...@suse.com>
> > > > > > wrote:
> > > > ovs-ofctl -O Openflow13 dump-flows br-int table=11
> > > 
> > > 
> > 
> 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] SFC Project

[Manuel Buil]

 _('Unable to find any valid segment in given context.'))
> 2017-07-20 09:21:06.556 1011 ERROR
> networking_odl.ml2.network_topology  
> ValueError: Unable to find any valid segment in given context.
> 2017-07-20 09:21:06.556 1011 ERROR
> networking_odl.ml2.network_topology
> 2017-07-20 09:21:06.561 1011 ERROR
> networking_odl.ml2.network_topology  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Unable to bind  
> port element for given host and valid VIF types:
>   hostname: node-25.domain.tld
>   valid VIF types: vhostuser, ovs
> 2017-07-20 09:21:06.562 1011 ERROR neutron.plugins.ml2.managers  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Failed to bind  
> port 826578fa-e3de-496e-8f4a-88bcd9b5288a on host node-
> 25.domain.tld  
> for vnic_type normal using segments [{'segmentation_id': None,  
> 'physical_network': u'physnet1', 'id':  
> u'c15cd96a-08c6-47ce-807f-91ced82ba3af', 'network_type': u'flat'}]
> 2017-07-20 09:21:06.563 1011 INFO neutron.plugins.ml2.plugin  
> [req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Attempt 2 to
> bind  
> port 826578fa-e3de-496e-8f4a-88bcd9b5288a.
> 
> Im attaching this log, take into account this test ran between
> 09:18  
> through 09:23 so maybe you can disregard the rest of the file.
> 
> Let me know what you think. Thanks in advance for your help.
> 
> Best regards,
> 
> Quoting "Manuel Buil" <mb...@suse.com>:
> 
> > 
> > Hi Pavan,
> > 
> > n_packets=0 means that no packets are matching the conditions. Is
> > this
> > the switch where the client that generates the traffic is connected
> > to?
> > 
> > Regards,
> > Manuel
> > 
> > On Thu, 2017-07-20 at 12:44 +0530, Pavan Gupta wrote:
> > > 
> > > Hi Manuel,Following is the output of the cvs-ofctl command. 
> > > 
> > > OFPST_FLOW reply (OF1.3) (xid=0x2):
> > >  cookie=0x1110010002420255, 
> > > duration=62656.965s, 
> > > table=11, 
> > > n_packets=0,
> > >  n_bytes=0, 
> > > tcp,
> > > reg0=0x1,
> > > tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],
> > > push_nsh,
> > > load:0x1->NXM_NX_NSH_MDTYPE[],
> > > load:0x3->NXM_NX_NSH_NP[],
> > > load:0xc0a80005->NXM_NX_NSH_C1[],
> > > load:0xf2->NXM_NX_NSP[0..23],
> > > load:0xff->NXM_NX_NSI[],
> > > load:0xb08->NXM_NX_TUN_IPV4_DST[],
> > > load:0xf2->NXM_NX_TUN_ID[0..31],
> > > resubmit(,0)
> > > > 
> > > > cookie=0x0, duration=67645.386s, table=11, n_packets=76029,
> > n_bytes=5979053, priority=0 actions=goto_table:21
> > > 
> > > 
> > > 
> > > Pavan
> > > > 
> > > > > 
> > > > > > 
> > > > > > On 19-Jul-2017, at 8:44 PM, Manuel Buil <mb...@suse.com>
> > > > > > wrote:
> > > > ovs-ofctl -O Openflow13 dump-flows br-int table=11
> > > 
> > > 
> > 
> 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] SFC Project

[Manuel Buil]

Hi Pavan,

n_packets=0 means that no packets are matching the conditions. Is this
the switch where the client that generates the traffic is connected to?

Regards,
Manuel

On Thu, 2017-07-20 at 12:44 +0530, Pavan Gupta wrote:
> Hi Manuel,Following is the output of the cvs-ofctl command. 
> 
> OFPST_FLOW reply (OF1.3) (xid=0x2):
>  cookie=0x1110010002420255, 
> duration=62656.965s, 
> table=11, 
> n_packets=0,
>  n_bytes=0, 
> tcp,
> reg0=0x1,
> tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],
> push_nsh,
> load:0x1->NXM_NX_NSH_MDTYPE[],
> load:0x3->NXM_NX_NSH_NP[],
> load:0xc0a80005->NXM_NX_NSH_C1[],
> load:0xf2->NXM_NX_NSP[0..23],
> load:0xff->NXM_NX_NSI[],
> load:0xb08->NXM_NX_TUN_IPV4_DST[],
> load:0xf2->NXM_NX_TUN_ID[0..31],
> resubmit(,0)
> > cookie=0x0, duration=67645.386s, table=11, n_packets=76029,
n_bytes=5979053, priority=0 actions=goto_table:21
> 
> 
> Pavan
> > > > On 19-Jul-2017, at 8:44 PM, Manuel Buil <mb...@suse.com> wrote:
> > ovs-ofctl -O Openflow13 dump-flows br-int table=11
> 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] SFC Project

[Manuel Buil]

 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I encountered a similar problem in my setting, it appears
that the problem is that the configuration file is not
updated with your installer IP address. So what i did was:
edit the file
"/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and
modify the installer IP address and cluster number. You can
get the cluster number by executing the command "fuel node
list" in your Fuel master machine.
> > > > > > 
> > > > > > I hope this helps you.
> > > > > > 
> > > > > > Best regards,
> > > > > > 
> > > > > > > > > > > > Quoting "Pavan Gupta" <pavan.gu...@calsoftinc.com>:
> > > > > > 
> > > > > > > HI Andres,
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I now hit 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > issue 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > related 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 10.20.0.2 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > IP 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > address. 
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Though
at time of starting the container I gave a different IP
address, I see there are several files that have
10.20.0.2 IP address. Shouldn’t that change? This is
where my script fails:
> > > > > > > > > > > > > > root@c8fc69ea9256:~# cat
/home/opnfv/functest/results/sfc.log
> > > > > > > 2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
> > > > > > > Traceback (most recent call last):
> > > > > > > File "./run_tests.py", line 189, in 
> > > > > > >   main(report=args.report)
> > > > > > > File "./run_tests.py", line 81, in main
> > > > > > >   installer_pwd=COMMON_CONFIG.installer_password)
> > > > > > > > > > > > > > > > > > > > > File
"/home/opnfv/repos/releng/modules/opnfv/deployment/factor
y.py", line 43, in get_handler
> > > > > > >   installer_pwd=installer_pwd)
> > > > > > > > > > > > > > > > > > > > > File
"/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/a
dapter.py", line 26, in __init__
> > > > > > >   pkey_file=None)
> > > > > > > > > > > > > > > > > > > > > File
"/home/opnfv/repos/releng/modules/opnfv/deployment/manage
r.py", line 332, in __init__
> > > > > > >   'Cannot establish connection to the installer node!')
> > > > > > > > > > > > > > Exception: Cannot establish connection to the 
> > > > > > > > > > > > > > installer
node!
> > > > > > > 
> > > > > > > Pavan
> > > > > > > 
> > > > > > > > > > > >

Re: [opnfv-tech-discuss] SFC Project

[Manuel Buil]

Ok. Check the first log you sent:







017-07-14
11:18:47,630 - __main__ - INFO - Restart heat-engine in 10.192.3.71

2017-07-14
11:18:47,630 - __main__ - INFO - Waiting for heat-engine to restart
in controllers

2017-07-14
11:18:57,641 - __main__ - INFO - tackerc file not found, fetching it
from controller

Tacker should have created a tackerc file in the controller when deployed

-Manuel

On Fri, 2017-07-14 at 19:12 +0530, Pavan Gupta wrote:
> > HI Manuel,Tacker was deployed in the beginning itself. Please check
the attached image.  Is there anything else I need to deploy Tacker?
> Pavan
> 
> 
> > > > On 14-Jul-2017, at 7:07 PM, Manuel Buil <mb...@suse.com> wrote:
> > Hello Pavan,
> > 
> > > > > > In the logs you sent previously, that step worked but it was not
able to fetch tackerc. Did you deploy your environment activating
tacker? It should be under settings > openstack services.
> > 
> > -Manuel
> > 
> > On Fri, 2017-07-14 at 18:36 +0530, Pavan Gupta wrote:
> > > HI Jose,
> > > This is sfc.log
> > > 
> > > 
> > > 
> > > 
> > > 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out
> > > 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out
> > > 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out
> > > 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out
> > > > > > 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch
/etc/heat/heat.conf from controller 10.192.3.70
> > > > > > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO -
Fetching /etc/heat/heat.conf from 10.192.3.70
> > > > > > > > > 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error
[get_file(ssh_conn, '/etc/heat/heat.conf', '/tmp/heat.conf']:
'NoneType' object has no attribute 'open_sftp'
> > > > > > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP
failed to retrieve the file.
> > > > > > 2017-07-14 13:00:13,407 - __main__ - INFO - Replace
/etc/heat/heat.conf with /tmp/heat.conf in controller 10.192.3.70
> > > 10.20.0.2
> > > root
> > > r00tme
> > > None
> > > --*-*
> > > > > > Installer Connection =  
> > > Traceback (most recent call last):
> > >   File "./run_tests.py", line 189, in 
> > >     main(report=args.report)
> > >   File "./run_tests.py", line 91, in main
> > >     disable_heat_resource_finder_cache(nodes)
> > > > > >   File "./run_tests.py", line 67, in
disable_heat_resource_finder_cache
> > >     controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
> > > > > > > > >   File
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py",
line 184, in run_cmd
> > >     _, stdout, stderr = (self.ssh_client.exec_command(cmd))
> > > AttributeError: 'NoneType' object has no attribute ‘exec_command'
> > > 
> > > 
> > > 
> > > 
> > > Pavan
> > > 
> > > 
> > > 
> > > 
> > > > > > > > On 14-Jul-2017, at 6:32 PM, Jose Lausuch <jose.lausuch@ericsson
.com> wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi,
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > > > > > Functest looks fine. Can you now attach sfc.log 
> > > > > > > > > > > > > > > > located in the
same directory? Maybe it’s a problem with the test case as such
while trying to access the deployment. Maybe Manuel has more
experience with it.
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > - Jose -
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > On 14 Jul 2017, at 14:47, Pavan Gupta 
> > > > > > > > > > <pavan.gupta@calsoftinc
.com> wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > HI Jose,
> > > > > 
> > > > > - I have attached the log file this time.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >