Re: [opnfv-tech-discuss] [tech-discuss][fuel]

[Ash Young]

Next time I see you, beer is on me. You rock!!!

Sent from my iPhone

> On Jan 27, 2017, at 16:48, Heather Kirksey  
> wrote:
> 
> Let me echo Chris here. You bore much of the burden of our early releases on 
> your back and we wouldn't be where we are today without your dedication and 
> leadership. I hope that your new role in Ericsson is rewarding. You're also 
> always welcome at our parties.  :)
> 
> Heather
> 
>> On Fri, Jan 27, 2017 at 2:56 AM, Christopher Price 
>>  wrote:
>> Jonas,
>> 
>>  
>> 
>> I’m know for a fact that I am not alone in thinking of you as one of our 
>> critical early leaders who’s efforts helped shape and build much of the 
>> success in how OPNFV operates and collaborates.  Your overall concern and 
>> care for our community and selfless/sleepless nights carrying us through our 
>> first sequence of releases will not soon be forgotten.
>> 
>>  
>> 
>> Wishing you all the best in your new activities and hoping to see you in and 
>> around the community as your role allows.
>> 
>>  
>> 
>> Cheers,
>> 
>> Chris
>> 
>>  
>> 
>> From: Jonas Bjurel 
>> Date: Friday, 27 January 2017 at 00:57
>> To: TECH-DISCUSS OPNFV 
>> Cc: Gregory Elkinbard , Aric Gardner 
>> , Michal Skalski , 
>> Szilard Cserey 
>> Subject: [tech-discuss][fuel]
>> 
>>  
>> 
>> Hi Fuel@OPNFV- and OPNFV colleagues!
>> 
>>  
>> 
>> As I have been assigned a new position within my company, I have decided
>> to step down as a committer in the OPNFV@Fuel project.
>> 
>> The OPNFV journey to where we stand now has been really thrilling to me, and
>> 
>> I have experienced a lot of great and innovative time with all of you OPNFV
>> community contributors.
>> 
>>  
>> 
>> In a sense this concludes one of my best working experiences so far!
>> 
>>  
>> 
>> In my new position I will not be that distant to OPNFV- and upstream 
>> community work – so I’m likely to be around going forward.
>> 
>>  
>> 
>> I which the best luck to the Fuel@OPNFV project going forward,
>> and see you around!
>> 
>>  
>> 
>> BR/Jonas
>> 
>>  
>> 
>> 
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>> 
> 
> 
> 
> -- 
> Heather Kirksey
> Director, OPNFV
> Mobile: +1.512.917.7938
> Email/Google Talk: hkirk...@linuxfoundation.org
> Skype: HeatherReneeKirksey
> IRC: HKirksey
>   
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes 1/27

[Tianhongbo]

Hi all:

Here is the minutes for the dovetail weekly meeting 1/27

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-27-14.00.log.html

best regards

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

Re: [opnfv-tech-discuss] [tech-discuss][fuel]

[Heather Kirksey]

Let me echo Chris here. You bore much of the burden of our early releases
on your back and we wouldn't be where we are today without your dedication
and leadership. I hope that your new role in Ericsson is rewarding. You're
also always welcome at our parties.  :)

Heather

On Fri, Jan 27, 2017 at 2:56 AM, Christopher Price <
christopher.pr...@ericsson.com> wrote:

> Jonas,
>
>
>
> I’m know for a fact that I am not alone in thinking of you as one of our
> critical early leaders who’s efforts helped shape and build much of the
> success in how OPNFV operates and collaborates.  Your overall concern and
> care for our community and selfless/sleepless nights carrying us through
> our first sequence of releases will not soon be forgotten.
>
>
>
> Wishing you all the best in your new activities and hoping to see you in
> and around the community as your role allows.
>
>
>
> Cheers,
>
> Chris
>
>
>
> *From: *Jonas Bjurel 
> *Date: *Friday, 27 January 2017 at 00:57
> *To: *TECH-DISCUSS OPNFV 
> *Cc: *Gregory Elkinbard , Aric Gardner <
> agard...@linuxfoundation.org>, Michal Skalski ,
> Szilard Cserey 
> *Subject: *[tech-discuss][fuel]
>
>
>
> Hi Fuel@OPNFV- and OPNFV colleagues!
>
>
>
> As I have been assigned a new position within my company, I have decided
> to step down as a committer in the OPNFV@Fuel project.
>
> The OPNFV journey to where we stand now has been really thrilling to me,
> and
>
> I have experienced a lot of great and innovative time with all of you OPNFV
> community contributors.
>
>
>
> In a sense this concludes one of my best working experiences so far!
>
>
>
> In my new position I will not be that distant to OPNFV- and upstream
> community work – so I’m likely to be around going forward.
>
>
>
> I which the best luck to the Fuel@OPNFV project going forward,
> and see you around!
>
>
>
> BR/Jonas
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*Heather Kirksey*
Director, OPNFV
Mobile: +1.512.917.7938
Email/Google Talk: hkirk...@linuxfoundation.org
Skype: HeatherReneeKirksey
IRC: HKirksey

[image: OPNFV_RGB.png]
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Infra] Infra WG Meeting Minutes - Jan 25th

[Jack Morgan]

  
  
January 25th
Agenda:

  MS4 for Danube

  revisit topic from last week (slides available here)

  
  Common Configuration File

  review status of POD Description file

  
  Hardware Resources

  Copper, Models and VES projects need hardware resources - Bryan Sullivan
  Joid is looking for hardware resources in US or Europe - Narinder Gupta

  
  Infra Alignment Presentations from fd.io, ODL and Open-O

  Infra
  Collaboration#CommunityPresentationSchedule

  
  Action Item Review
  AoB

Minutes: (link)

  MS4 danube

  Jose mentions that this idea of a
  milestone is good but sometimes lab changes are up to
  companies
  David summarize the MS4 danube
  discussion topic
  Jack suggestions reviewing hardware
  resources at multiple points - MS4, Feature freeze, etc
  David suggets that MS4 would be a point
  that we delare hardware resources fixed for the release that we would avoid making major changes to
  infrastructure etc
  David revists his slides from the
  hackfest 
  issue #1 - how to identify project
  requirements
  what questions should be asked by
  release manager?
  some discussion included asking
  projects - baremetal/virtual, HA/No-HA, other, and
  quantity
  It is important to have checkpoints on
  the way to identify changes in project needs 

  
  Common Configuration Files - POD Config
  File

  Jack is working on common POD Config
  files and will contact people

  
  Hardware Resources for Copper/Models/VES

  Bryan mentions he is looking for vPOD
  and Jose will be able to host it 
  Fatihmentions that next meeting will be
  extended next week for infra alignment 
  Link - https://wiki.opnfv.org/display/INF/Infra+Collaboration#InfraCollaboration-CommunityPresentationSchedule

  
  Action Items Review

  Ray has followed up with Biteria and
  moving forward with effort (link - https://gerrit.opnfv.org/gerrit/#/c/22723/2/UPSTREAM)

  Q1 will start on development work
  by Biteria and Q2 will be deployment (jmorgan1,
  16:53:26)

  
  Covered remaining action items and not
  other business (jmorgan1,
  16:58:15)

  

Action Items:
  

  Follow up how the upstream
  contributions can be tracked with/for different upstream/OPNFV
  projects Ray Paik
  Infra PTLs to come up with summary
regarding how OPNFV Infra can be improved to present to TSC Fatih Degirmenci, Jack Morgan, Ulrich Kleber 
  Check latest status regarding UCS
support/education tracked via INFRA-11 - LF Lab: UCS Support with LF POD3 IN PROGRESS  assign
now to Rudy Grigar III

  Add links in the table for all the
static checking tools Jingbo Hao
  Contact installer teams for final
agreement on POD descriptor file template Jack Morgan
  Provide an example for POD
descriptor file from ZTE labs julien zhang

Ongoing Items:

  Document scenario to POD
mapping via the Scenario Infrastructure page Jack Morgan
  Document how to control commit gating in
  CI evolution Fatih Degirmenci
  Document
  how to build an OPNFV Pharos lab Jack Morgan  



-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

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

[opnfv-tech-discuss] Agenda for the February OPNFV Board meeting

[Raymond Paik]

All,

Please find below agenda for the Board meeting on February 2nd.

   - 2016 recap and the year ahead
   - Compliance/Verification Program discussion
   - Strategic plan topics
   - TSC update

Thanks,

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

Re: [opnfv-tech-discuss] [Fuel] Tacker Plugin MIssing From Danube Nightly ISO

[Serg Melikyan]

Aimee,

thank you! Do you need more information from me to proceed with adding
support for Tacker?

On Thu, Jan 26, 2017 at 7:24 AM, Aimee Ukasick 
wrote:

> Serg - I would be happy to help test Tacker whichever release it goes
> into. Same with Congress.
>
> aimee
>
>
> On 01/25/2017 06:43 PM, Serg Melikyan wrote:
> > Hi Aimee,
> >
> > indeed tacker is not included in Fuel Danube right now, building and
> > including this plugin was disabled
> >  9f8aff6636e0d86834178b461802f3e7cb95189d>
> > during uplifting to Fuel 10.
> >
> > Are you planning to include the tacker plugin in Danube?
> >
> >
> > Unfortunately this plugin was never tested with Fuel 10 and we are
> > awfully close to the Feature Freeze, any chance you are able and want
> > to help with this before Feature Freeze? George (in cc) was original
> > committer who added this plugin to the Fuel Colorado and might be
> > interested in adding to Danube.
> >
> > George?
> >
> > Otherwise I would say that Tacker will not be available as built-in
> > plugin for Danube.
> >
> > On Wed, Jan 25, 2017 at 9:26 AM, Aimee Ukasick
> > >
> wrote:
> >
> > Greetings Fuel team - Quick question -- the Colorado 3.0 Fuel ISO
> > has a
> > tacker plugin (tacker-0.2-0.2.0-1.noarch.rpm) but that plugin is
> > missing
> > from the Fuel nightly build I downloaded on 24 January (
> > artifacts.opnfv.org/fuel/opnfv-2017-01-25_00-00-11.iso
> > ).
> > Are you
> > planning to include the tacker plugin in Danube?
> >
> > Also I noticed the congress plugin is included in the nightly
> > Danube iso
> > - thanks loads!
> >
> > --
> >
> > Aimee Ukasick, AT Open Source
> >
> >
> > ___
> > opnfv-tech-discuss mailing list
> > opnfv-tech-discuss@lists.opnfv.org
> > 
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> > 
> >
> >
> >
> >
> > --
> > Serg Melikyan, Development Manager at Mirantis, Inc.
> > http://mirantis.com  | smelik...@mirantis.com
> >  | +1 (650) 440-8979
>
> --
> Aimee Ukasick, AT Open Source
>
>


-- 
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Wenjing Chu]

On source code link, take a look if these (as examples) will serve the purpose 
for now.

https://gerrit.opnfv.org/gerrit/#/c/27225/ ,
https://gerrit.opnfv.org/gerrit/#/c/27221/ ,
https://gerrit.opnfv.org/gerrit/#/c/27227/ ,
https://gerrit.opnfv.org/gerrit/#/c/27231/ ,
https://gerrit.opnfv.org/gerrit/#/c/27223/

Wenjing


From: Wenjing Chu
Sent: Friday, January 27, 2017 9:49 AM
To: 'SULLIVAN, BRYAN L' ; Pierre Lynch ; 
Jose Lausuch 
Cc: TECH-DISCUSS OPNFV 
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

I agree more information is better, however it is not obvious where that 
information will come from.


-Test case run result history
Do we keep records of old runs in Colorado for functest & yardsticks? If we do, 
let’s link them up.
If not, we can always re-run these tests on the frozen Colorado release and 
produce these results. Are we regularly running them now?
Also note, the Colorado release is frozen, test cases are frozen, so this spot 
info may not be as relevant as it appears. However I agree it’ll become more 
informational and valuable with longer history.


-Source code of test cases
Do we have a link to source code repos in openstack, ODL/ONOS, etc upstreams?
Can someone involved in CI/CD pitch in?

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Friday, January 27, 2017 6:20 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

More inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Thursday, January 26, 2017 12:30 PM
To: SULLIVAN, BRYAN L >; Pierre Lynch 
>; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Hi Bryan

Hope my inline responses are still readable …
Thanks.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Thursday, January 26, 2017 8:29 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

More comments inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Wednesday, January 25, 2017 3:00 PM
To: SULLIVAN, BRYAN L >; Pierre Lynch 
>; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Thanks Bryan. See my response inline below.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Wednesday, January 25, 2017 11:32 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

I posted some comments in gerrit. Here are the main points I think we need 
alignment on:

1)  All proposed dovetail included tests will be added one-by-one, in a 
separate commit.

Please follow the gerrit tickets below and see if you can follow through. Test 
cases are organized into two levels for convenience: test areas and test cases. 
There will be one commit for each test case, and one commit for each test area 
(which includes a lot of test cases that are related to a function area). The 
test case commit says we are good on how that test case is implemented. The 
test area commit says we agree the test case ought to be included. Clear enough?
[bryan] A test reference should not be added to a test area until the test has 
been approved (e.g. verified by more than one committer/reviewer). I see one 
commit with about 40 tests referenced. Have all these been verified?

[wenjing] the act of “adding a test case to a test area” is reflected as adding 
a single line in the compliance_set.yml file. Using your example, I 

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

[Wenjing Chu]

I agree more information is better, however it is not obvious where that 
information will come from.


-Test case run result history
Do we keep records of old runs in Colorado for functest & yardsticks? If we do, 
let’s link them up.
If not, we can always re-run these tests on the frozen Colorado release and 
produce these results. Are we regularly running them now?
Also note, the Colorado release is frozen, test cases are frozen, so this spot 
info may not be as relevant as it appears. However I agree it’ll become more 
informational and valuable with longer history.


-Source code of test cases
Do we have a link to source code repos in openstack, ODL/ONOS, etc upstreams?
Can someone involved in CI/CD pitch in?

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Friday, January 27, 2017 6:20 AM
To: Wenjing Chu ; Pierre Lynch ; 
Jose Lausuch 
Cc: TECH-DISCUSS OPNFV 
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

More inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Thursday, January 26, 2017 12:30 PM
To: SULLIVAN, BRYAN L >; Pierre Lynch 
>; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Hi Bryan

Hope my inline responses are still readable …
Thanks.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Thursday, January 26, 2017 8:29 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

More comments inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Wednesday, January 25, 2017 3:00 PM
To: SULLIVAN, BRYAN L >; Pierre Lynch 
>; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Thanks Bryan. See my response inline below.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Wednesday, January 25, 2017 11:32 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

I posted some comments in gerrit. Here are the main points I think we need 
alignment on:

1)  All proposed dovetail included tests will be added one-by-one, in a 
separate commit.

Please follow the gerrit tickets below and see if you can follow through. Test 
cases are organized into two levels for convenience: test areas and test cases. 
There will be one commit for each test case, and one commit for each test area 
(which includes a lot of test cases that are related to a function area). The 
test case commit says we are good on how that test case is implemented. The 
test area commit says we agree the test case ought to be included. Clear enough?
[bryan] A test reference should not be added to a test area until the test has 
been approved (e.g. verified by more than one committer/reviewer). I see one 
commit with about 40 tests referenced. Have all these been verified?

[wenjing] the act of “adding a test case to a test area” is reflected as adding 
a single line in the compliance_set.yml file. Using your example, I can add 40 
tests in a patch, meaning, I “propose” (based on the wiki discussion in the 
past) that these 40 cases be included. The submitter is sending this proposal 
out for review. If you have opinion about any of these, or simply want more 
explanation/clarification, please comment on the gerrit patch. Based on those 
comments, the submitter can modify the patch to reflect updated view and 
resubmit, until we are good and approve with +1 (or disapprove with -1). Hope 
that is clear. These are patch reviews, to be approved. Not yet.

I’m not sure what you mean by “verified”. If you mean if the software is 
tested, I think the answer is yes. If you mean if the test case has been 
approved, no, a patch email is precisely asking you to review.

[bryan] It 

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

[Michael Polenchuk]

Hi George,

The private network is created by default, you just need to assign it to an
interface on each of the node.
Please look at the following docs:
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/map-logical-to-physical-nic.html
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/network-settings.html
http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/sysreq/sysreq_network_requirements.html

Also if DPDK ain't requirement, please turn it off for now.

On Fri, Jan 27, 2017 at 7:54 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:

> Hi Michael,
>
>
>
> I think I found a possible cause for this issue
>
>
>
> From the dashboard I see that we don’t have a Private network.
>
> In the code I see:
>
>   roles['neutron/private'] = 'br-aux' if orig_roles.key?('neutron/
> private')
>
>
>
> Perhaps this is the root cause that br-aux is missing? Can you guide me
> how to create a private network?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 5:39 PM
> *To:* Michael Polenchuk 
>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli 
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Ok I’ll wait a bit for a Fuel 10 patch.
>
>
>
> Thanks for your help,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:34 PM
> *To:* Paraskevopoulos Georgios 
> *Cc:* Manuel Buil ; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> This commit is intended only for 9.0 branch of odl plugin
>
> (i.e. for Fuel 9/mitaka).
>
>
>
> On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> There is only one file, astute.yaml
>
> Here are the contents: http://pastebin.com/pKXtCnDX
>
>
>
> I’m using master + I cherry-picked your commit:
>
> Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV
>
>
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:06 PM
> *To:* Paraskevopoulos Georgios 
> *Cc:* Manuel Buil ; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> Thanks for testing it.
>
> Could you please share content of /etc/hiera.
>
> Which version of the odl plugin do you use?
>
> I believe this patch doesn't cause the error above with duplicate
> declaration.
>
>
>
> On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk ; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli 
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> ]
> *Sent:* Friday, January 27, 2017 12:55 PM
> *To:* Manuel Buil 
> *Cc:* brady.allen.john...@ericsson.com; Paraskevopoulos Georgios <
> geo...@intracom-telecom.com>; opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org; Veena Lingadahalli 
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Manuel,
>
> Is dpdk the requirement for SFC?
>
> I've successful deployment with 

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

[Paraskevopoulos Georgios]

Hi Michael,



I think I found a possible cause for this issue



>From the dashboard I see that we don’t have a Private network.

In the code I see:

  roles['neutron/private'] = 'br-aux' if orig_roles.key?('neutron/private')



Perhaps this is the root cause that br-aux is missing? Can you guide me how to 
create a private network?



Thanks,

George



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



Ok I’ll wait a bit for a Fuel 10 patch.



Thanks for your help,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 5:34 PM
To: Paraskevopoulos Georgios 
Cc: Manuel Buil ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli 

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



Hi George,

This commit is intended only for 9.0 branch of odl plugin

(i.e. for Fuel 9/mitaka).



On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios 
 > wrote:

Hi Michael,



There is only one file, astute.yaml

Here are the contents: http://pastebin.com/pKXtCnDX



I’m using master + I cherry-picked your commit:

Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV





From: Michael Polenchuk [mailto:mpolenc...@mirantis.com 
 ]
Sent: Friday, January 27, 2017 5:06 PM
To: Paraskevopoulos Georgios  >
Cc: Manuel Buil  >; 
opnfv-us...@lists.opnfv.org  ; 
opnfv-tech-discuss@lists.opnfv.org  
; Veena Lingadahalli  >


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



Hi George,

Thanks for testing it.

Could you please share content of /etc/hiera.

Which version of the odl plugin do you use?

I believe this patch doesn't cause the error above with duplicate declaration.



On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios 
 > wrote:

Hi Michael,



I tested your patch. Now it fails with a different error

2017-01-27 14:13:19ERRDuplicate declaration: 
L3_clear_route[default] is already declared; cannot redeclare at 
/etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on node 
node-3.domain.tld



Can you look into it?



Thanks,

George



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
  
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
 ] On Behalf Of 
Paraskevopoulos Georgios
Sent: Friday, January 27, 2017 2:15 PM
To: Michael Polenchuk  
>; Manuel Buil  >
Cc: opnfv-us...@lists.opnfv.org  ; 
opnfv-tech-discuss@lists.opnfv.org  
; Veena Lingadahalli  >


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



Hi Michael,



DPDK is not a requirement for SFC. NSH is. I can help you with the debugging.

I’ll try your patch now to see if it will resolve the issue and get back to you.



BR,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 12:55 PM
To: Manuel Buil  >
Cc: brady.allen.john...@ericsson.com  
; Paraskevopoulos Georgios  >; opnfv-tech-discuss@lists.opnfv.org 
 ; opnfv-us...@lists.opnfv.org 
 ; Veena Lingadahalli 
 >
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Manuel,

Is dpdk the requirement for SFC?

I've successful deployment with https://review.openstack.org/421907, but for 
now ... vms don't want to receive ip from dhcp server.
("dpdkvhostuser" interface is being added to br-int, opendaylight controller 
looks fine & etc.)
I'm definitely stuck a bit 

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

[Paraskevopoulos Georgios]

Ok I’ll wait a bit for a Fuel 10 patch.



Thanks for your help,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 5:34 PM
To: Paraskevopoulos Georgios 
Cc: Manuel Buil ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli 

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



Hi George,

This commit is intended only for 9.0 branch of odl plugin

(i.e. for Fuel 9/mitaka).



On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios 
 > wrote:

Hi Michael,



There is only one file, astute.yaml

Here are the contents: http://pastebin.com/pKXtCnDX



I’m using master + I cherry-picked your commit:

Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV





From: Michael Polenchuk [mailto:mpolenc...@mirantis.com 
 ]
Sent: Friday, January 27, 2017 5:06 PM
To: Paraskevopoulos Georgios  >
Cc: Manuel Buil  >; 
opnfv-us...@lists.opnfv.org  ; 
opnfv-tech-discuss@lists.opnfv.org  
; Veena Lingadahalli  >


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



Hi George,

Thanks for testing it.

Could you please share content of /etc/hiera.

Which version of the odl plugin do you use?

I believe this patch doesn't cause the error above with duplicate declaration.



On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios 
 > wrote:

Hi Michael,



I tested your patch. Now it fails with a different error

2017-01-27 14:13:19ERRDuplicate declaration: 
L3_clear_route[default] is already declared; cannot redeclare at 
/etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on node 
node-3.domain.tld



Can you look into it?



Thanks,

George



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
  
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
 ] On Behalf Of 
Paraskevopoulos Georgios
Sent: Friday, January 27, 2017 2:15 PM
To: Michael Polenchuk  
>; Manuel Buil  >
Cc: opnfv-us...@lists.opnfv.org  ; 
opnfv-tech-discuss@lists.opnfv.org  
; Veena Lingadahalli  >


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



Hi Michael,



DPDK is not a requirement for SFC. NSH is. I can help you with the debugging.

I’ll try your patch now to see if it will resolve the issue and get back to you.



BR,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 12:55 PM
To: Manuel Buil  >
Cc: brady.allen.john...@ericsson.com  
; Paraskevopoulos Georgios  >; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-us...@lists.opnfv.org  ; Veena 
Lingadahalli  >
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Manuel,

Is dpdk the requirement for SFC?

I've successful deployment with https://review.openstack.org/421907, but for 
now ... vms don't want to receive ip from dhcp server.
("dpdkvhostuser" interface is being added to br-int, opendaylight controller 
looks fine & etc.)
I'm definitely stuck a bit with it and have no much time to research an issue.

It would be great if you could help me to debug it to get that I'm missing.



On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  > wrote:

Hi Michael,

How is the progress going? We are hitting today M5 in OPNFV and we cannot 
report if our SFC tests work due to this bug. Can we help somehow to accelerate 
this?

Thanks,
Manuel





>>> Michael Polenchuk  
>>> > 01/24/17 3:09 PM >>>

Hi George,

We're working on this now for Fuel9 support and will make the same for Fuel10 
afterwards.



On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios 
 > wrote:

Hi all,



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

[opnfv-tech-discuss] [OPNFV] Danube community priorities

[morgan.richomme]

Hi

please find attached the pdf discussed on community priorities for
Danube by the TSC: https://wiki.opnfv.org/display/SWREL/Danube+priorities

In the first part we tried to indicate the main achievements of the
first OPNFV versions and indicate some metrics.

In the second part we tried to identify some problems and tasks/Commons
needed by the "community" to support the sustainable growth of the
scenarios/installers/projects.

A "community" priority is neither a project priority nor a ranking of
expected features.

It is just some work impacting several projects, not always well
identified, because at the interface of several projects but valuable to
give consistency especially for end users or use our resources more
efficiently.

That is why you will not find the future killing features of Danube here
:)...it is more probably in the projects...

These priorities are informative and there is no associated commitments
for Danube.

Finally we started this discussion after the Openstack Summit in
Barcelona, which was too late regarding the Danube version.

For the E release, we would like to start earlier, in order to finalize
this document on first release milestones (not on MS5)

As inputs we already have the EUAG pain points.
A wiki page has been initiated
https://wiki.opnfv.org/pages/viewpage.action?pageId=8688472
An etherpad is also available to collect community views:
https://etherpad.opnfv.org/p/E-Release_Community_priorities

Doing the exercise earlier could motivate the creation of projects on
priorities that would be uncovered or poorly covered by the existing
projects.

/Morgan


_

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.



TSC_Danube_Community_priorities.pdf
Description: Adobe PDF document
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Michael Polenchuk]

Hi George,

This commit is intended only for 9.0 branch of odl plugin
(i.e. for Fuel 9/mitaka).

On Fri, Jan 27, 2017 at 7:23 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:

> Hi Michael,
>
>
>
> There is only one file, astute.yaml
>
> Here are the contents: http://pastebin.com/pKXtCnDX
>
>
>
> I’m using master + I cherry-picked your commit:
>
> Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV
>
>
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com]
> *Sent:* Friday, January 27, 2017 5:06 PM
> *To:* Paraskevopoulos Georgios 
> *Cc:* Manuel Buil ; opnfv-us...@lists.opnfv.org;
> opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli <
> vlingadaha...@mvista.com>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi George,
>
> Thanks for testing it.
>
> Could you please share content of /etc/hiera.
>
> Which version of the odl plugin do you use?
>
> I believe this patch doesn't cause the error above with duplicate
> declaration.
>
>
>
> On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk ; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli 
>
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> ]
> *Sent:* Friday, January 27, 2017 12:55 PM
> *To:* Manuel Buil 
> *Cc:* brady.allen.john...@ericsson.com; Paraskevopoulos Georgios <
> geo...@intracom-telecom.com>; opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org; Veena Lingadahalli 
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Manuel,
>
> Is dpdk the requirement for SFC?
>
> I've successful deployment with https://review.openstack.org/421907, but
> for now ... vms don't want to receive ip from dhcp server.
> ("dpdkvhostuser" interface is being added to br-int, opendaylight
> controller looks fine & etc.)
> I'm definitely stuck a bit with it and have no much time to research an
> issue.
>
> It would be great if you could help me to debug it to get that I'm missing.
>
>
>
> On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  wrote:
>
> Hi Michael,
>
> How is the progress going? We are hitting today M5 in OPNFV and we cannot
> report if our SFC tests work due to this bug. Can we help somehow to
> accelerate this?
>
> Thanks,
> Manuel
>
>
>
>
>
> >>> Michael Polenchuk  01/24/17 3:09 PM >>>
>
> Hi George,
>
> We're working on this now for Fuel9 support and will make the same for
> Fuel10 afterwards.
>
>
>
> On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi all,
>
>
>
> I am encountering the same problem in Fuel 10. Do we have any news on this?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Michael
> Polenchuk
> *Sent:* Monday, January 16, 2017 9:25 PM
> *To:* Veena Lingadahalli 
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi,
>
> This bug/feature could be tracked by
> https://bugs.launchpad.net/fuel-plugin-opendaylight/+bug/1656924
>
> We're going to get a support of ODL with DPDK usecase soon.
>
>
>
> On Tue, Jan 10, 2017 at 2:18 PM, Michael Polenchuk <
> mpolenc...@mirantis.com> wrote:
>
> Hi Veena,
>
> In case of DPDK enabled the br-aux bridge ain't created on compute nodes
> since physical(dpdk) interface is being connected directly to br-prv ovs
> bridge.
>
> I guess this case (ODL + OVS/DPDK) ain't supported yet.
>
> Please turn off "install dpdk" option and try it out.
>
>
>
> On Mon, Jan 9, 2017 at 8:18 

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

[Paraskevopoulos Georgios]

Hi Michael,



There is only one file, astute.yaml

Here are the contents: http://pastebin.com/pKXtCnDX



I’m using master + I cherry-picked your commit:

Here are the top 3 commits in git log: http://pastebin.com/UzFf0wNV





From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 5:06 PM
To: Paraskevopoulos Georgios 
Cc: Manuel Buil ; opnfv-us...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; Veena Lingadahalli 

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



Hi George,

Thanks for testing it.

Could you please share content of /etc/hiera.

Which version of the odl plugin do you use?

I believe this patch doesn't cause the error above with duplicate declaration.



On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios 
 > wrote:

Hi Michael,



I tested your patch. Now it fails with a different error

2017-01-27 14:13:19ERRDuplicate declaration: 
L3_clear_route[default] is already declared; cannot redeclare at 
/etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on node 
node-3.domain.tld



Can you look into it?



Thanks,

George



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
  
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
 ] On Behalf Of 
Paraskevopoulos Georgios
Sent: Friday, January 27, 2017 2:15 PM
To: Michael Polenchuk  
>; Manuel Buil  >
Cc: opnfv-us...@lists.opnfv.org  ; 
opnfv-tech-discuss@lists.opnfv.org  
; Veena Lingadahalli  >


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



Hi Michael,



DPDK is not a requirement for SFC. NSH is. I can help you with the debugging.

I’ll try your patch now to see if it will resolve the issue and get back to you.



BR,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 12:55 PM
To: Manuel Buil  >
Cc: brady.allen.john...@ericsson.com  
; Paraskevopoulos Georgios  >; opnfv-tech-discuss@lists.opnfv.org 
 ; opnfv-us...@lists.opnfv.org 
 ; Veena Lingadahalli 
 >
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Manuel,

Is dpdk the requirement for SFC?

I've successful deployment with https://review.openstack.org/421907, but for 
now ... vms don't want to receive ip from dhcp server.
("dpdkvhostuser" interface is being added to br-int, opendaylight controller 
looks fine & etc.)
I'm definitely stuck a bit with it and have no much time to research an issue.

It would be great if you could help me to debug it to get that I'm missing.



On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  > wrote:

Hi Michael,

How is the progress going? We are hitting today M5 in OPNFV and we cannot 
report if our SFC tests work due to this bug. Can we help somehow to accelerate 
this?

Thanks,
Manuel





>>> Michael Polenchuk  
>>> > 01/24/17 3:09 PM >>>

Hi George,

We're working on this now for Fuel9 support and will make the same for Fuel10 
afterwards.



On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios 
 > wrote:

Hi all,



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



Thanks,

George



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



Hi,

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

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



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

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

[Michael Polenchuk]

Hi George,

Thanks for testing it.
Could you please share content of /etc/hiera.
Which version of the odl plugin do you use?
I believe this patch doesn't cause the error above with duplicate
declaration.

On Fri, Jan 27, 2017 at 6:51 PM, Paraskevopoulos Georgios <
geo...@intracom-telecom.com> wrote:

> Hi Michael,
>
>
>
> I tested your patch. Now it fails with a different error
>
> 2017-01-27 14:13:19ERRDuplicate declaration:
> L3_clear_route[default] is already declared; cannot redeclare at
> /etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on
> node node-3.domain.tld
>
>
>
> Can you look into it?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Paraskevopoulos
> Georgios
> *Sent:* Friday, January 27, 2017 2:15 PM
> *To:* Michael Polenchuk ; Manuel Buil <
> mb...@suse.com>
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org;
> Veena Lingadahalli 
>
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Michael,
>
>
>
> DPDK is not a requirement for SFC. NSH is. I can help you with the
> debugging.
>
> I’ll try your patch now to see if it will resolve the issue and get back
> to you.
>
>
>
> BR,
>
> George
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> ]
> *Sent:* Friday, January 27, 2017 12:55 PM
> *To:* Manuel Buil 
> *Cc:* brady.allen.john...@ericsson.com; Paraskevopoulos Georgios <
> geo...@intracom-telecom.com>; opnfv-tech-discuss@lists.opnfv.org;
> opnfv-us...@lists.opnfv.org; Veena Lingadahalli 
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi Manuel,
>
> Is dpdk the requirement for SFC?
>
> I've successful deployment with https://review.openstack.org/421907, but
> for now ... vms don't want to receive ip from dhcp server.
> ("dpdkvhostuser" interface is being added to br-int, opendaylight
> controller looks fine & etc.)
> I'm definitely stuck a bit with it and have no much time to research an
> issue.
>
> It would be great if you could help me to debug it to get that I'm missing.
>
>
>
> On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  wrote:
>
> Hi Michael,
>
> How is the progress going? We are hitting today M5 in OPNFV and we cannot
> report if our SFC tests work due to this bug. Can we help somehow to
> accelerate this?
>
> Thanks,
> Manuel
>
>
>
>
>
> >>> Michael Polenchuk  01/24/17 3:09 PM >>>
>
> Hi George,
>
> We're working on this now for Fuel9 support and will make the same for
> Fuel10 afterwards.
>
>
>
> On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios <
> geo...@intracom-telecom.com> wrote:
>
> Hi all,
>
>
>
> I am encountering the same problem in Fuel 10. Do we have any news on this?
>
>
>
> Thanks,
>
> George
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Michael
> Polenchuk
> *Sent:* Monday, January 16, 2017 9:25 PM
> *To:* Veena Lingadahalli 
> *Cc:* opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment
> failing with br-aux not found
>
>
>
> Hi,
>
> This bug/feature could be tracked by
> https://bugs.launchpad.net/fuel-plugin-opendaylight/+bug/1656924
>
> We're going to get a support of ODL with DPDK usecase soon.
>
>
>
> On Tue, Jan 10, 2017 at 2:18 PM, Michael Polenchuk <
> mpolenc...@mirantis.com> wrote:
>
> Hi Veena,
>
> In case of DPDK enabled the br-aux bridge ain't created on compute nodes
> since physical(dpdk) interface is being connected directly to br-prv ovs
> bridge.
>
> I guess this case (ODL + OVS/DPDK) ain't supported yet.
>
> Please turn off "install dpdk" option and try it out.
>
>
>
> On Mon, Jan 9, 2017 at 8:18 PM, Veena Lingadahalli <
> vlingadaha...@mvista.com> wrote:
>
> Hi,
>
> I'm using opnfv fuel 9.0 to deploy openstack with ODL-SFC(netvirt) +
> OVS(DPDK+NSH). I have used all default plugins which are staged with the
> fuel iso.
> I have made the necessary configurations related to neutron VLAN IDs, DPDK
> enabled interface and Hugepage configuration in compute node. Network
> verification is also successful. The deployment is failing with the below
> error.
>
>
> generate_network_config(): Endpoint 'br-aux' not found in interfaces or
> transformations result. at 
> /etc/fuel/plugins/opendaylight-0.9/puppet/manifests/odl-netconfig.pp:25
> on node node-1.domain.tld
>
> I'm unable to check where this bridge is being created. Never faced this
> issue before when neutron with tunneling is used. Am I missing any
> configuration related to vlan? Attached the complete puppet log and
> network_scheme. 

[opnfv-tech-discuss] [armband] Danube MS5 report for Armband

[Bob Monkman]

David, et al,
Here are the scenarios we are currently running in Armband at 
this time:

[1] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-nosdn-nofeature-ha-armband-baremetal-daily-master/
[2] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l2-bgpvpn-ha-armband-baremetal-daily-master/
[3] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l2-nofeature-ha-armband-baremetal-daily-master/
[4] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l2-nofeature-noha-armband-baremetal-daily-master/
[5] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l2-sfc-ha-armband-baremetal-daily-master/
[6] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l2-sfc-noha-armband-baremetal-daily-master/
[7] 
https://build.opnfv.org/ci/view/armband/job/fuel-os-odl_l3-nofeature-ha-armband-baremetal-daily-master/

Regards,
Bob
PTL for Armband

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Paraskevopoulos Georgios]

Hi Michael,



I tested your patch. Now it fails with a different error



2017-01-27 14:13:19ERRDuplicate declaration: 
L3_clear_route[default] is already declared; cannot redeclare at 
/etc/puppet/modules/osnailyfacter/manifests/netconfig/netconfig.pp:27 on node 
node-3.domain.tld



Can you look into it?



Thanks,

George



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
Paraskevopoulos Georgios
Sent: Friday, January 27, 2017 2:15 PM
To: Michael Polenchuk ; Manuel Buil 
Cc: opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Veena 
Lingadahalli 
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Michael,



DPDK is not a requirement for SFC. NSH is. I can help you with the debugging.

I’ll try your patch now to see if it will resolve the issue and get back to you.



BR,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 12:55 PM
To: Manuel Buil  >
Cc: brady.allen.john...@ericsson.com  
; Paraskevopoulos Georgios  >; opnfv-tech-discuss@lists.opnfv.org 
 ; opnfv-us...@lists.opnfv.org 
 ; Veena Lingadahalli 
 >
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Manuel,

Is dpdk the requirement for SFC?

I've successful deployment with https://review.openstack.org/421907, but for 
now ... vms don't want to receive ip from dhcp server.
("dpdkvhostuser" interface is being added to br-int, opendaylight controller 
looks fine & etc.)
I'm definitely stuck a bit with it and have no much time to research an issue.

It would be great if you could help me to debug it to get that I'm missing.



On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  > wrote:

Hi Michael,

How is the progress going? We are hitting today M5 in OPNFV and we cannot 
report if our SFC tests work due to this bug. Can we help somehow to accelerate 
this?

Thanks,
Manuel





>>> Michael Polenchuk  
>>> > 01/24/17 3:09 PM >>>

Hi George,

We're working on this now for Fuel9 support and will make the same for Fuel10 
afterwards.



On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios 
 > wrote:

Hi all,



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



Thanks,

George



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



Hi,

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

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



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

Hi Veena,

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

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

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



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

Hi,

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


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

I'm unable to check where this bridge is being created. Never faced this issue 
before when neutron with tunneling is used. Am I missing any configuration 
related to vlan? Attached the complete puppet log and 

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

[SULLIVAN, BRYAN L]

More inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Thursday, January 26, 2017 12:30 PM
To: SULLIVAN, BRYAN L ; Pierre Lynch ; Jose 
Lausuch 
Cc: TECH-DISCUSS OPNFV 
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Hi Bryan

Hope my inline responses are still readable …
Thanks.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Thursday, January 26, 2017 8:29 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

More comments inline.

Thanks,
Bryan Sullivan | AT

From: Wenjing Chu [mailto:wenjing@huawei.com]
Sent: Wednesday, January 25, 2017 3:00 PM
To: SULLIVAN, BRYAN L >; Pierre Lynch 
>; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

Thanks Bryan. See my response inline below.

Wenjing

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Wednesday, January 25, 2017 11:32 AM
To: Wenjing Chu >; Pierre 
Lynch >; Jose Lausuch 
>
Cc: TECH-DISCUSS OPNFV 
>
Subject: RE: [opnfv-tech-discuss] [dovetail]L3VPN for dovetail area

I posted some comments in gerrit. Here are the main points I think we need 
alignment on:

1)  All proposed dovetail included tests will be added one-by-one, in a 
separate commit.

Please follow the gerrit tickets below and see if you can follow through. Test 
cases are organized into two levels for convenience: test areas and test cases. 
There will be one commit for each test case, and one commit for each test area 
(which includes a lot of test cases that are related to a function area). The 
test case commit says we are good on how that test case is implemented. The 
test area commit says we agree the test case ought to be included. Clear enough?
[bryan] A test reference should not be added to a test area until the test has 
been approved (e.g. verified by more than one committer/reviewer). I see one 
commit with about 40 tests referenced. Have all these been verified?

[wenjing] the act of “adding a test case to a test area” is reflected as adding 
a single line in the compliance_set.yml file. Using your example, I can add 40 
tests in a patch, meaning, I “propose” (based on the wiki discussion in the 
past) that these 40 cases be included. The submitter is sending this proposal 
out for review. If you have opinion about any of these, or simply want more 
explanation/clarification, please comment on the gerrit patch. Based on those 
comments, the submitter can modify the patch to reflect updated view and 
resubmit, until we are good and approve with +1 (or disapprove with -1). Hope 
that is clear. These are patch reviews, to be approved. Not yet.

I’m not sure what you mean by “verified”. If you mean if the software is 
tested, I think the answer is yes. If you mean if the test case has been 
approved, no, a patch email is precisely asking you to review.

[bryan] It will be much more complicated to approve a block of tests for 
inclusion, rather than test-by-test, unless it is clarified that as a group 
they have been passing (e.g by reference to Jenkins jobs where the tests have 
been successfully running as a group). A single large commit with a bunch of 
text strings with no explanation as to what they are, where they have been 
tested, etc, is not the way we should manage the dovetail testcase list.


2)  The commit will include a link to the details of the test case (script 
or otherwise what I would use to run the test for myself)

You can trace down to the source step by step, e.g. from test area to test 
case, then to functest or yardstick, and/or to openstack or other upstream 
eventually the source code in that upstream project.

To test run it, you would need a test environment/pod. I would think that 
running dovetail tool, specifying the individual test cases you’d want to run, 
and examining the results probably a good way to go. Maybe good to write down a 
“how-to” cheat-sheet for this?
[bryan] Not sure how that answered the comment. Rather than having to search 
for something that relates to the test case reference, it would be good for 

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

[Paraskevopoulos Georgios]

Hi Michael,



DPDK is not a requirement for SFC. NSH is. I can help you with the debugging.

I’ll try your patch now to see if it will resolve the issue and get back to you.



BR,

George



From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, January 27, 2017 12:55 PM
To: Manuel Buil 
Cc: brady.allen.john...@ericsson.com; Paraskevopoulos Georgios 
; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-us...@lists.opnfv.org; Veena Lingadahalli 
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found



Hi Manuel,

Is dpdk the requirement for SFC?

I've successful deployment with https://review.openstack.org/421907, but for 
now ... vms don't want to receive ip from dhcp server.
("dpdkvhostuser" interface is being added to br-int, opendaylight controller 
looks fine & etc.)
I'm definitely stuck a bit with it and have no much time to research an issue.

It would be great if you could help me to debug it to get that I'm missing.



On Fri, Jan 27, 2017 at 1:22 PM, Manuel Buil  > wrote:

Hi Michael,

How is the progress going? We are hitting today M5 in OPNFV and we cannot 
report if our SFC tests work due to this bug. Can we help somehow to accelerate 
this?

Thanks,
Manuel





>>> Michael Polenchuk  
>>> > 01/24/17 3:09 PM >>>

Hi George,

We're working on this now for Fuel9 support and will make the same for Fuel10 
afterwards.



On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios 
 > wrote:

Hi all,



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



Thanks,

George



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



Hi,

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

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



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

Hi Veena,

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

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

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



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

Hi,

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


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

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



Thanks,

-Veena



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




--

  Michael Polenchuk
  Private Cloud / Mirantis Inc.




--

  Michael Polenchuk
  Private Cloud / Mirantis Inc.




--

  Michael Polenchuk
  Private Cloud / Mirantis Inc.




--

  Michael Polenchuk
  Private Cloud / Mirantis Inc.



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

Re: [opnfv-tech-discuss] [tech-discuss][fuel]

[Christopher Price]

Jonas,

I’m know for a fact that I am not alone in thinking of you as one of our 
critical early leaders who’s efforts helped shape and build much of the success 
in how OPNFV operates and collaborates.  Your overall concern and care for our 
community and selfless/sleepless nights carrying us through our first sequence 
of releases will not soon be forgotten.

Wishing you all the best in your new activities and hoping to see you in and 
around the community as your role allows.

Cheers,
Chris

From: Jonas Bjurel 
Date: Friday, 27 January 2017 at 00:57
To: TECH-DISCUSS OPNFV 
Cc: Gregory Elkinbard , Aric Gardner 
, Michal Skalski , Szilard 
Cserey 
Subject: [tech-discuss][fuel]

Hi Fuel@OPNFV- and OPNFV colleagues!

As I have been assigned a new position within my company, I have decided
to step down as a committer in the OPNFV@Fuel project.
The OPNFV journey to where we stand now has been really thrilling to me, and
I have experienced a lot of great and innovative time with all of you OPNFV
community contributors.

In a sense this concludes one of my best working experiences so far!

In my new position I will not be that distant to OPNFV- and upstream
community work – so I’m likely to be around going forward.

I which the best luck to the Fuel@OPNFV project going forward,
and see you around!

BR/Jonas

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

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

[Manuel Buil]

Hi Michael,

How is the progress going? We are hitting today M5 in OPNFV and we cannot 
report if our SFC tests work due to this bug. Can we help somehow to accelerate 
this?

Thanks,
Manuel




>>> Michael Polenchuk  01/24/17 3:09 PM >>>
Hi George,


We're working on this now for Fuel9 support and will make the same for Fuel10 
afterwards.


On Tue, Jan 24, 2017 at 6:00 PM, Paraskevopoulos Georgios 
 wrote:
 Hi all,
 
I am encountering the same problem in Fuel 10. Do we have any news on this?
 
Thanks,
George
 
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Michael 
Polenchuk
Sent: Monday, January 16, 2017 9:25 PM
To: Veena Lingadahalli 
Cc: opnfv-us...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel9.0][vlan] Fuel9.0 deployment failing 
with br-aux not found
 
Hi,

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

We're going to get a support of ODL with DPDK usecase soon.
 
On Tue, Jan 10, 2017 at 2:18 PM, Michael Polenchuk  
wrote:
Hi Veena,

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

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

Please turn off "install dpdk" option and try it out.
 
On Mon, Jan 9, 2017 at 8:18 PM, Veena Lingadahalli  
wrote:


Hi,

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

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

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

 

Thanks,

-Veena

 


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




-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.












-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.







 



-- 
  Michael Polenchuk
  Private Cloud / Mirantis Inc.



 



 

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

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

[Ryota Mibu via RT]

Hi Gerald and Aric,


Actually, this is miss-configuration of merge jobs. So, other merge jobs could 
have the same issue. We need to use 'git-scm' for merge jobs instead of 
'git-scm-gerrit' which is for verify jobs.


Best,
Ryota

> -Original Message-
> From: Kunzmann, Gerald via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Friday, January 27, 2017 5:14 PM
> Cc: opnfv-tech-discuss@lists.opnfv.org; Mibu Ryota(壬生 亮太) 
> 
> Subject: RE: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] 
> [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with
> Git/Gerrit/Jenkins
> 
> Hi Aric,
> 
> Thanks for your investigations! I'll do the fix as you have proposed.
> 
> If I understand your reply correctly, this issue is limited to opnfvdocs?
> 
> Best regards,
> Gerald
> 
> -Original Message-
> From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Donnerstag, 26. Januar 2017 20:54
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] 
> [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with
> Git/Gerrit/Jenkins
> 
> Hi,
> 
> Looks like the merge job is doing the wrong thing.
> 
> its checking out the patchset, rather than what is in master.
> since the patchset is from Dec 28, and does not touch 
> ./docs/requirements/05-implementation.rst (which has been updated
> since then) git does not see a conflict with merging this code.
> 
> If you look at the console output for the merge job 
> https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
> its doing this. > git fetch --tags --progress 
> ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
> timeout=15
> and it should be just doing a straight clone of whats in master (after
> 24365 is merged)
> 
> For now you can just submit a small change to doctor/docs/whatever and then 
> merge it, this will get the latest version
> of all rst files into artifacts.
> 
> I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this confusing 
> behavior in the future.
> 
> Regards,
> Aric
> 
> 
> 
> On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT 
>  wrote:
> > Dear all,
> >
> > Sorry for another email on this issue:
> >
> > Today the situation is even more strange:
> >
> > There is the old alarm table in generated artifacts file:
> > http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> > But the git tree still contains the new table:
> > https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.
> > rst
> >
> > What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/
> > after Ryota had merged the patch, jenkins-ci has just sent the document 
> > links, but there was no specific build started.
> Is this normal/okay?
> >
> > Best regards,
> > Gerald
> >
> > -Original Message-
> > From: Kunzmann, Gerald
> > Sent: Donnerstag, 26. Januar 2017 13:40
> > To: 'opnfv-helpd...@rt.linuxfoundation.org'
> > ; 'Fatih Degirmenci'
> > 
> > Cc: 'opnfv-tech-discuss@lists.opnfv.org'
> > ; 'r-m...@cq.jp.nec.com'
> > 
> > Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re:
> > [opnfv-tech-discuss] [releng][helpdesk] Problem with
> > Git/Gerrit/Jenkins
> >
> > Dear all,
> >
> > So this issue is easily reproducible. It had again happened today with 
> > another patch being merged
> >
> > https://gerrit.opnfv.org/gerrit/24365
> >
> > We are now back to the old table again :(
> >
> > We have to find a solution to this problem!!!
> >
> > Best regards,
> > Gerald
> >
> > -Original Message-
> > From: Kunzmann, Gerald
> > Sent: Mittwoch, 25. Januar 2017 13:56
> > To: 'opnfv-helpd...@rt.linuxfoundation.org'
> > 
> > Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> > Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re:
> > [opnfv-tech-discuss] [releng][helpdesk] Problem with
> > Git/Gerrit/Jenkins
> >
> > HI Fatih,
> >
> > Thanks for your quick check. The remerged had helped to bring back the 
> > table...
> >
> > Let's see docs team's reply on it.
> >
> > I agree gerrit was fine not raising conflict as the changed line in the 
> > "editorial" patch was not conflicting with the
> other patch.
> > Still, shouldn't gerrit have just changed that one line instead of also 
> > other parts of the file and/or shouldn't gerrit
> have raised some warning it was changing more than just the one line?
> >
> > When looking at the diff in gerrit for the "editorial" patch, it does not 
> > compare against the latest master, otherwise
> it would have shown more changes than just this one line. This might have 
> caused the issue?!?
> >
> > Best regards,
> > Gerald
> >
> > 

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

[Ryota Mibu]

Hi Gerald and Aric,


Actually, this is miss-configuration of merge jobs. So, other merge jobs could 
have the same issue. We need to use 'git-scm' for merge jobs instead of 
'git-scm-gerrit' which is for verify jobs.


Best,
Ryota

> -Original Message-
> From: Kunzmann, Gerald via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Friday, January 27, 2017 5:14 PM
> Cc: opnfv-tech-discuss@lists.opnfv.org; Mibu Ryota(壬生 亮太) 
> 
> Subject: RE: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] 
> [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with
> Git/Gerrit/Jenkins
> 
> Hi Aric,
> 
> Thanks for your investigations! I'll do the fix as you have proposed.
> 
> If I understand your reply correctly, this issue is limited to opnfvdocs?
> 
> Best regards,
> Gerald
> 
> -Original Message-
> From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Donnerstag, 26. Januar 2017 20:54
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] 
> [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with
> Git/Gerrit/Jenkins
> 
> Hi,
> 
> Looks like the merge job is doing the wrong thing.
> 
> its checking out the patchset, rather than what is in master.
> since the patchset is from Dec 28, and does not touch 
> ./docs/requirements/05-implementation.rst (which has been updated
> since then) git does not see a conflict with merging this code.
> 
> If you look at the console output for the merge job 
> https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
> its doing this. > git fetch --tags --progress 
> ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
> timeout=15
> and it should be just doing a straight clone of whats in master (after
> 24365 is merged)
> 
> For now you can just submit a small change to doctor/docs/whatever and then 
> merge it, this will get the latest version
> of all rst files into artifacts.
> 
> I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this confusing 
> behavior in the future.
> 
> Regards,
> Aric
> 
> 
> 
> On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT 
>  wrote:
> > Dear all,
> >
> > Sorry for another email on this issue:
> >
> > Today the situation is even more strange:
> >
> > There is the old alarm table in generated artifacts file:
> > http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> > But the git tree still contains the new table:
> > https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.
> > rst
> >
> > What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/
> > after Ryota had merged the patch, jenkins-ci has just sent the document 
> > links, but there was no specific build started.
> Is this normal/okay?
> >
> > Best regards,
> > Gerald
> >
> > -Original Message-
> > From: Kunzmann, Gerald
> > Sent: Donnerstag, 26. Januar 2017 13:40
> > To: 'opnfv-helpd...@rt.linuxfoundation.org'
> > ; 'Fatih Degirmenci'
> > 
> > Cc: 'opnfv-tech-discuss@lists.opnfv.org'
> > ; 'r-m...@cq.jp.nec.com'
> > 
> > Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re:
> > [opnfv-tech-discuss] [releng][helpdesk] Problem with
> > Git/Gerrit/Jenkins
> >
> > Dear all,
> >
> > So this issue is easily reproducible. It had again happened today with 
> > another patch being merged
> >
> > https://gerrit.opnfv.org/gerrit/24365
> >
> > We are now back to the old table again :(
> >
> > We have to find a solution to this problem!!!
> >
> > Best regards,
> > Gerald
> >
> > -Original Message-
> > From: Kunzmann, Gerald
> > Sent: Mittwoch, 25. Januar 2017 13:56
> > To: 'opnfv-helpd...@rt.linuxfoundation.org'
> > 
> > Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> > Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re:
> > [opnfv-tech-discuss] [releng][helpdesk] Problem with
> > Git/Gerrit/Jenkins
> >
> > HI Fatih,
> >
> > Thanks for your quick check. The remerged had helped to bring back the 
> > table...
> >
> > Let's see docs team's reply on it.
> >
> > I agree gerrit was fine not raising conflict as the changed line in the 
> > "editorial" patch was not conflicting with the
> other patch.
> > Still, shouldn't gerrit have just changed that one line instead of also 
> > other parts of the file and/or shouldn't gerrit
> have raised some warning it was changing more than just the one line?
> >
> > When looking at the diff in gerrit for the "editorial" patch, it does not 
> > compare against the latest master, otherwise
> it would have shown more changes than just this one line. This might have 
> caused the issue?!?
> >
> > Best regards,
> > Gerald
> >
> > 

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

[Kunzmann, Gerald]

Hi Aric,

Thanks for your investigations! I'll do the fix as you have proposed.

If I understand your reply correctly, this issue is limited to opnfvdocs?

Best regards,
Gerald

-Original Message-
From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Donnerstag, 26. Januar 2017 20:54
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org 
#35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

Hi,

Looks like the merge job is doing the wrong thing.

its checking out the patchset, rather than what is in master.
since the patchset is from Dec 28, and does not touch
./docs/requirements/05-implementation.rst (which has been updated
since then)
git does not see a conflict with merging this code.

If you look at the console output for the merge job
https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
its doing this. > git fetch --tags --progress
ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
timeout=15
and it should be just doing a straight clone of whats in master (after
24365 is merged)

For now you can just submit a small change to doctor/docs/whatever and
then merge it, this will get the latest version of all rst files into
artifacts.

I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this
confusing behavior in the future.

Regards,
Aric



On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT
 wrote:
> Dear all,
>
> Sorry for another email on this issue:
>
> Today the situation is even more strange:
>
> There is the old alarm table in generated artifacts file: 
> http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> But the git tree still contains the new table: 
> https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst
>
> What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
> Ryota had merged the patch,
> jenkins-ci has just sent the document links, but there was no specific build 
> started. Is this normal/okay?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Donnerstag, 26. Januar 2017 13:40
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> ; 'Fatih Degirmenci' 
> 
> Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
> ; 'r-m...@cq.jp.nec.com' 
> 
> Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Dear all,
>
> So this issue is easily reproducible. It had again happened today with 
> another patch being merged
>
> https://gerrit.opnfv.org/gerrit/24365
>
> We are now back to the old table again :(
>
> We have to find a solution to this problem!!!
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Mittwoch, 25. Januar 2017 13:56
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> HI Fatih,
>
> Thanks for your quick check. The remerged had helped to bring back the 
> table...
>
> Let's see docs team's reply on it.
>
> I agree gerrit was fine not raising conflict as the changed line in the 
> "editorial" patch was not conflicting with the other patch.
> Still, shouldn't gerrit have just changed that one line instead of also other 
> parts of the file and/or shouldn't gerrit have raised some warning it was 
> changing more than just the one line?
>
> When looking at the diff in gerrit for the "editorial" patch, it does not 
> compare against the latest master, otherwise it would have shown more changes 
> than just this one line. This might have caused the issue?!?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: fatih.degirme...@ericsson.com via RT 
> [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Mittwoch, 25. Januar 2017 13:38
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Hi,
>
> I had a quick look at this and diffed the commits and I see no conflict so 
> Gerrit was fine not raising conflict. (the changed line in 
> 05-implementation.rst in most recent patch is not a conflicting change)
>
> I then tried regenerating the documents by putting remerge as comment to 
> check the doc generation script/job output for possible errors which I didn't 
> see any. But the generated document is correct now. If you don't 

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

[Kunzmann, Gerald via RT]

Hi Aric,

Thanks for your investigations! I'll do the fix as you have proposed.

If I understand your reply correctly, this issue is limited to opnfvdocs?

Best regards,
Gerald

-Original Message-
From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Donnerstag, 26. Januar 2017 20:54
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org 
#35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

Hi,

Looks like the merge job is doing the wrong thing.

its checking out the patchset, rather than what is in master.
since the patchset is from Dec 28, and does not touch
./docs/requirements/05-implementation.rst (which has been updated
since then)
git does not see a conflict with merging this code.

If you look at the console output for the merge job
https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
its doing this. > git fetch --tags --progress
ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
timeout=15
and it should be just doing a straight clone of whats in master (after
24365 is merged)

For now you can just submit a small change to doctor/docs/whatever and
then merge it, this will get the latest version of all rst files into
artifacts.

I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this
confusing behavior in the future.

Regards,
Aric



On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT
 wrote:
> Dear all,
>
> Sorry for another email on this issue:
>
> Today the situation is even more strange:
>
> There is the old alarm table in generated artifacts file: 
> http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> But the git tree still contains the new table: 
> https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst
>
> What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
> Ryota had merged the patch,
> jenkins-ci has just sent the document links, but there was no specific build 
> started. Is this normal/okay?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Donnerstag, 26. Januar 2017 13:40
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> ; 'Fatih Degirmenci' 
> 
> Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
> ; 'r-m...@cq.jp.nec.com' 
> 
> Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Dear all,
>
> So this issue is easily reproducible. It had again happened today with 
> another patch being merged
>
> https://gerrit.opnfv.org/gerrit/24365
>
> We are now back to the old table again :(
>
> We have to find a solution to this problem!!!
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Mittwoch, 25. Januar 2017 13:56
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> HI Fatih,
>
> Thanks for your quick check. The remerged had helped to bring back the 
> table...
>
> Let's see docs team's reply on it.
>
> I agree gerrit was fine not raising conflict as the changed line in the 
> "editorial" patch was not conflicting with the other patch.
> Still, shouldn't gerrit have just changed that one line instead of also other 
> parts of the file and/or shouldn't gerrit have raised some warning it was 
> changing more than just the one line?
>
> When looking at the diff in gerrit for the "editorial" patch, it does not 
> compare against the latest master, otherwise it would have shown more changes 
> than just this one line. This might have caused the issue?!?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: fatih.degirme...@ericsson.com via RT 
> [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Mittwoch, 25. Januar 2017 13:38
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Hi,
>
> I had a quick look at this and diffed the commits and I see no conflict so 
> Gerrit was fine not raising conflict. (the changed line in 
> 05-implementation.rst in most recent patch is not a conflicting change)
>
> I then tried regenerating the documents by putting remerge as comment to 
> check the doc generation script/job output for possible errors which I didn't 
> see any. But the generated document is correct now. If you don't