Re: [openstack-dev] TripleO NeutronNetworkVLANRanges

[Numan Siddique]

On Thu, Jun 14, 2018 at 12:50 AM, Remo Mattei  wrote:

> Hello guys, just want to double check and make sure that this option can
> be ignored if using vxlan.
>
> NeutronNetworkVLANRanges (used in the network isolation template)
>
>
Hi Remo, this parameter maps to the neutron config 'network_vlan_range'
defined here -
https://github.com/openstack/neutron/blob/master/neutron/conf/plugins/ml2/drivers/driver_type.py#L71

You probably need it if your provider network is VLAN.

Thanks
Numan



> Thanks,
> Remo
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] [OVN] L3 traffic

[Numan Siddique]

On Wed, Feb 14, 2018 at 4:19 AM, Assaf Muller  wrote:

> I'm not aware of plans for OVN to supported distributed SNAT, therefor
> a networking node will still be required for the foreseeable future.
>
> On Mon, Jan 15, 2018 at 2:18 AM, wenran xiao  wrote:
> > Hey all,
> > I have found Network OVN will support to distributed floating ip
> > (https://docs.openstack.org/releasenotes/networking-ovn/unreleased.html
> ),
> > how about the snat in the future? Still need network node or not?
> > Any suggestions are welcomed.
>

OVN can select any node (or nodes if HA is enabled) to schedule a router as
long as the node has ovn-controller service running in it and
ovn-bridge-mappings configured properly.
So, If you have external connectivity in your compute nodes and you are
fine with any of these compute nodes doing the centralized snat, you don't
need to have a network node.

Thanks
Numan

>
> >
> > Best regards
> > Ran
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovn] [tripleo] enable open ptcp communication to NB and SB databases

[Numan Siddique]

On Thu, Dec 14, 2017 at 2:31 PM, pranab boruah 
wrote:

> Thanks Numan for the reply.
>
> >tripleo takes care of that and there should be no need to run those
> >commands manually. Which release of tripleo you are using ?
> We are using Pike. My bad, I was looking for the aforementioned
> commands and didn't check the code properly for the alternate way to
> use open tcp based communication.
>
> I have couple of follow-up questions:
>
> 1. Is the open TCP(no SSL) based mechanism enabled by default in
> TripleO ? Or we have to set a config parameter for using open TCP ?
>

I think tripleo supports SSL  for all the service endpoints. You need to
include certain environment files.
I am not very clear whether your question is for tripleo in general or for
the communication between neutron server and OVN db servers.

For the communication between neutron-server/ovn-controller/ovn-northd and
OVN db servers, OVN tripleo heat temaplates/puppet modules doesn't support
SSL yet.
We need to enhance these to support this use case.


2. In actual production deployments, is open TCP used instead of SSL?
>

If your queston is for tripleo deployment in original, I am afraid I am not
right person.  May be Tripleo folks can answer this question.

Thanks
Numan


> Thanks,
> Pranab
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovn] [tripleo] enable open ptcp communication to NB and SB databases

[Numan Siddique]

On Wed, Dec 13, 2017 at 5:22 PM, pranab boruah 
wrote:

> Hi folks,
> The following commit[0] added support for SSL connections to NB and SB
> databases. Now for enabling open ptcp communication to NB and SB dbs,
> we need to do this:
>
> # ovn-sbctl set-connection ptcp:6642
> # ovn-nbctl set-connection ptcp:6641
>
> For an OpenStack cloud deployment(TripleO), if open ptcp communication
> is preferred, the above commands should run automatically instead of
> running them manually(on all the controller nodes).
>
> Do such an option exists today? Maybe, though the OVN TripleO HEAT
> templates.
>
> Will be happy to contribute if required.
>
> [0] https://github.com/openvswitch/ovs/commit/84d0ca5d00fe01b291
>
> Thanks,
> Pranab
>
>
Hi Pranab,

tripleo takes care of that and there should be no need to run those
commands manually. Which release of tripleo you are using ?

If you enable non-HA OVN db profile it would be done here [1] and for HA
(using pacemaker) it would be done here [2]. Also have a look
at [3].


[1] -
https://github.com/openstack/puppet-ovn/blob/master/manifests/northd.pp#L17
[2] -
https://github.com/openvswitch/ovs/blob/master/ovn/utilities/ovndb-servers.ocf#L308
[3] -
https://github.com/openvswitch/ovs/blob/master/ovn/utilities/ovn-ctl#L120


Thanks
Numan

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][ovn] networking-ovn core team update

[Numan Siddique]

Congratulations Daniel. Welcome :)

Thanks
Numan


On Fri, Dec 1, 2017 at 10:27 PM, Anil Venkata 
wrote:

> Congrats Daniel
>
> On 01-Dec-2017 10:22 PM, "Jakub Libosvar"  wrote:
>
>> Congratulations! Very well deserved! :)
>>
>> On 01/12/2017 17:45, Lucas Alvares Gomes wrote:
>> > Hi all,
>> >
>> > I would like to welcome Daniel Alvarez to the networking-ovn core team!
>> >
>> > Daniel has been contributing with the project for a good time already
>> > and helping *a lot* with reviews and code.
>> >
>> > Welcome onboard man!
>> >
>> > Cheers,
>> > Lucas
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [octavia] Proposing Nir Magnezi as Octavia core reviewer

[Numan Siddique]

Congratulations Nir

On Oct 12, 2017 5:19 AM, "Tong Liu"  wrote:

> Congratulations Nir!
>
> On Tue, Oct 10, 2017 at 1:36 PM, Nir Magnezi  wrote:
>
>> Thanks everyone for your votes :-)
>> I'm really happy to become a member of this great team!
>>
>> Nir
>>
>> On Tue, Oct 10, 2017 at 1:28 AM, Michael Johnson 
>> wrote:
>>
>>> Ok, that is quorum.
>>>
>>> Congratulations Nir!
>>>
>>> Michael
>>>
>>>
>>> On Mon, Oct 9, 2017 at 3:18 PM, Adam Harwell 
>>> wrote:
>>> > +1
>>> >
>>> >
>>> > On Thu, Oct 5, 2017, 05:48 Daniel Mellado 
>>> > wrote:
>>> >>
>>> >> +1
>>> >>
>>> >> Go, Nir, Go!
>>> >>
>>> >> congrats!
>>> >>
>>> >> On 10/05/2017 03:51 AM, German Eichberger wrote:
>>> >> > +1
>>> >> >
>>> >> > Welcome Nir, well earned.
>>> >> >
>>> >> > German
>>> >> >
>>> >> > On 10/4/17, 4:28 PM, "Michael Johnson"  wrote:
>>> >> >
>>> >> > Hello OpenStack folks,
>>> >> >
>>> >> > I would like to propose Nir Magnezi as a core reviewer on the
>>> >> > Octavia project.
>>> >> >
>>> >> > He has been an active contributor to the Octavia projects for a
>>> few
>>> >> > releases and has been providing solid patch review comments. His
>>> >> > review stats are also in line with other core reviewers.
>>> >> >
>>> >> > Octavia cores, please reply to this e-mail with your
>>> >> > agreement/disagreement to this proposal.
>>> >> >
>>> >> > Michael
>>> >> >
>>> >> >
>>> >> > 
>>> __
>>> >> > OpenStack Development Mailing List (not for usage questions)
>>> >> > Unsubscribe:
>>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
>>> ck-dev
>>> >> >
>>> >> >
>>> >> >
>>> >> > 
>>> __
>>> >> > OpenStack Development Mailing List (not for usage questions)
>>> >> > Unsubscribe:
>>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >> >
>>> >>
>>> >>
>>> >> 
>>> __
>>> >> OpenStack Development Mailing List (not for usage questions)
>>> >> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>> >
>>> > 
>>> __
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][ovn] networking-ovn-core updates

[Numan Siddique]

Awesome.

Welcome   Miguel and Yamamoto!

Thanks
Numan


On Tue, Oct 10, 2017 at 7:46 PM, Miguel Angel Ajo Pelayo <
majop...@redhat.com> wrote:

> Thank you very much :-)
>
> On Tue, Oct 10, 2017 at 4:09 PM, Lucas Alvares Gomes Martins <
> lmart...@redhat.com> wrote:
>
>> Hi,
>>
>> On Tue, Oct 10, 2017 at 2:25 PM, Russell Bryant 
>> wrote:
>> > Hello, everyone.  I'd like to welcome two new members to the
>> > networking-ovn-core team: Miguel Angel Ajo and Yamamoto Takashi.
>> >
>>
>> Great additions, welcome on board Miguel and Yamamoto!
>>
>> Cheers,
>> Lucas
>>
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Networking-OVN] Unable to run OVN functional tests

[Numan Siddique]

On Wed, Aug 23, 2017 at 10:41 AM, Trinath Somanchi <trinath.soman...@nxp.com
> wrote:

> I’m not running functional tests as root.
>
>
>
> Also, from [1] , The following errors fails most for the cases.
>
>
>
> Captured pythonlogging:
>
> ~~~
>
>ERROR [neutron.agent.linux.utils] Exit code: 1; Stdin: ; Stdout: ;
> Stderr: 2017-08-19T19:16:26Z|1|unixctl|WARN|failed to connect to
> /tmp/tmpNpVzUM/tmpxaCA5
>
> ovs-appctl: cannot connect to "/tmp/tmpNpVzUM/tmpxaCA5m/ovnnb_db.ctl"
> (No such file or directory)
>
>
>
>ERROR [neutron.agent.linux.utils] Exit code: 1; Stdin: ; Stdout: ;
> Stderr: 2017-08-19T19:16:26Z|1|unixctl|WARN|failed to connect to
> /tmp/tmpNpVzUM/tmpxaCA5
>
> ovs-appctl: cannot connect to "/tmp/tmpNpVzUM/tmpxaCA5m/ovnsb_db.ctl"
> (No such file or directory)
>
>
>
> why the test case is searching ovnnb_db.ctl at some other location?
>
>
You see these error logs when the test calls the "stop" function here [1].
"stop" is called because of [2] as part of cleanup.

The real issue is "utils.create_process(ovsdb_server_cmd)" called here [3]
is failing and you probably need to debug why.

Did you get the chance to try to the commands which I suggested in my
previous email ?


Thanks


[1] -
https://github.com/openstack/networking-ovn/blob/master/networking_ovn/tests/functional/resources/process.py#L125
[2] -
https://github.com/openstack/networking-ovn/blob/master/networking_ovn/tests/functional/resources/process.py#L66
[3] -
https://github.com/openstack/networking-ovn/blob/master/networking_ovn/tests/functional/resources/process.py#L108


>
>
> [1] http://paste.openstack.org/show/618837/
>
>
>
> Best Regards,
>
> Trinath Somanchi | *NXP* | *HSDC*, *INDIA*
>
>
>
> *From:* Numan Siddique [mailto:nusid...@redhat.com]
> *Sent:* Wednesday, August 23, 2017 10:25 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Networking-OVN] Unable to run OVN
> functional tests
>
>
>
>
>
>
>
> On Wed, Aug 23, 2017 at 12:03 AM, Assaf Muller <as...@redhat.com> wrote:
>
>
>
>
>
> On Sat, Aug 19, 2017 at 3:02 PM, Trinath Somanchi <
> trinath.soman...@nxp.com> wrote:
>
> Hi-
>
>
>
> Using [1] I have enabled devstack setup.
>
>
>
> Now that when I try dvsm-functional tests, I get all tests failed.
>
>
>
> Please find the error log [2]  help me resolve this issue.
>
>
>
> Looking into the logs, I am pretty sure there is some problem in finding
>  'ovsdb-server' binary in the path.
>
> May be you need to verify if you have installed the ovs properly in your
> system. I would suggest you clone ovs repository, compile it and run "sudo
> make install".
>
>
>
> Since you have mentioned that you have deployed devstack, devstack ovn
> script should have compiled ovs and installed.
>
> What I suggest you to do is verify again if you have installed ovs
> properly. Run "which ovsdb-server" and see if it returns
> "/usr/local/sbin/ovsdb-server".
>
>
>
> If you see the code here - https://github.com/
> openstack/networking-ovn/blob/master/networking_ovn/tests/
> functional/resources/process.py#L91, it uses 
> spawn.find_executable('ovsdb-server').
> May be you can run "spawn.find_executable('ovsdb-server') this out in a
> python shell.
>
>
>
> I hope you are not running functional tests as "sudo". When you run as
> sudo it may be possible that /usr/local/bin or /usr/local/sbin might not be
> in the PATH environment.
>
>
>
> Thanks
>
> Numan
>
>
>
>
>
> Also, were there any tempests tests possible for OVN?
>
>
>
> The networking-ovn repo doesn't add new Tempest tests, but the Tempest
> networking tests, as well as the Tempest tests in the Neutron tree can be
> run against a cloud using OVN.
>
>
>
>
>
> [1] https://docs.openstack.org/networking-ovn/latest/
> contributor/testing.html
>
> [2] http://paste.openstack.org/show/618837/
>
>
>
>
>
> Best Regards,
>
> */ Trinath Somanchi.*
>
> [image: cid:image001.png@01D28854.B7934C80]
>
> *Trinath Somanchi.*
>
> Hyderabad Software Development Center (HSDC), GSD , DN,
>
> NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
>
> Hyderabad, Telangana, 500032, India
>
>
>
> Email: *trinath.soman...@nxp.com <trinath.soman...@nxp.com>*  | Mobile: +91
> 9866235130 <+91%2098662%2035130> | Off: +91 4033504051
> <+91%2040%203

Re: [openstack-dev] [Networking-OVN] Unable to run OVN functional tests

[Numan Siddique]

On Wed, Aug 23, 2017 at 12:03 AM, Assaf Muller  wrote:

>
>
> On Sat, Aug 19, 2017 at 3:02 PM, Trinath Somanchi <
> trinath.soman...@nxp.com> wrote:
>
>> Hi-
>>
>>
>>
>> Using [1] I have enabled devstack setup.
>>
>>
>>
>> Now that when I try dvsm-functional tests, I get all tests failed.
>>
>>
>>
>> Please find the error log [2]  help me resolve this issue.
>>
>
Looking into the logs, I am pretty sure there is some problem in finding
 'ovsdb-server' binary in the path.
May be you need to verify if you have installed the ovs properly in your
system. I would suggest you clone ovs repository, compile it and run "sudo
make install".

Since you have mentioned that you have deployed devstack, devstack ovn
script should have compiled ovs and installed.
What I suggest you to do is verify again if you have installed ovs
properly. Run "which ovsdb-server" and see if it returns
"/usr/local/sbin/ovsdb-server".

If you see the code here -
https://github.com/openstack/networking-ovn/blob/master/networking_ovn/tests/functional/resources/process.py#L91,
it uses spawn.find_executable('ovsdb-server'). May be you can run
"spawn.find_executable('ovsdb-server') this out in a python shell.

I hope you are not running functional tests as "sudo". When you run as sudo
it may be possible that /usr/local/bin or /usr/local/sbin might not be in
the PATH environment.

Thanks
Numan


>>
>> Also, were there any tempests tests possible for OVN?
>>
>
> The networking-ovn repo doesn't add new Tempest tests, but the Tempest
> networking tests, as well as the Tempest tests in the Neutron tree can be
> run against a cloud using OVN.
>
>
>>
>>
>> [1] https://docs.openstack.org/networking-ovn/latest/contributor
>> /testing.html
>>
>> [2] http://paste.openstack.org/show/618837/
>>
>>
>>
>>
>>
>> Best Regards,
>>
>> */ Trinath Somanchi.*
>>
>> [image: cid:image001.png@01D28854.B7934C80]
>>
>> *Trinath Somanchi.*
>>
>> Hyderabad Software Development Center (HSDC), GSD , DN,
>>
>> NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
>>
>> Hyderabad, Telangana, 500032, India
>>
>>
>>
>> Email: *trinath.soman...@nxp.com *  | Mobile: +91
>> 9866235130 <+91%2098662%2035130> | Off: +91 4033504051
>> <+91%2040%203350%204051>
>>
>> [image: cid:image002.png@01D28854.B7934C80]
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] FFE for OVN container support

[Numan Siddique]

On Wed, Aug 9, 2017 at 8:41 AM, Emilien Macchi <emil...@redhat.com> wrote:

> On Tue, Aug 8, 2017 at 7:05 AM, Numan Siddique <nusid...@redhat.com>
> wrote:
> > I would like to request FFE exception for OVN containerized support. OVN
> is
> > an optional feature and should be a low risk.
> >
> > The patches can be found here -
> > https://review.openstack.org/#/q/topic:bug/1699085
>
> I checked all the patches and indeed they aren't intrusive enough to
> break anything. I think this is fine.
> Give us a bonus and bring-up scenario007 working on containers (
> https://review.openstack.org/#/c/490622 ) - it would be *awesome* :-)
>
>
Thank you Emilien, that's the goal :)



> Anyway, +1 on my side for this code to land in Pike. Any feedback from
> the team is welcome though.
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] FFE for OVN container support

[Numan Siddique]

Hello,

I would like to request FFE exception for OVN containerized support. OVN is
an optional feature and should be a low risk.

The patches can be found here -
https://review.openstack.org/#/q/topic:bug/1699085

Thanks
Numan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Request to add neutron-server-[ovn/odl] to the tripleoupstream docker hub

[Numan Siddique]

Hello,

When we build the kolla images using the command [1], it builds
neutron-server-ovn and neutron-server-odl which are not in tripleoupstream
docker hub.

Is it possible to upload them ? I am not sure if it is done manually or a
script does it.
neutron-server-ovn image is required  to have a CI job for OVN docker
services The patches for OVN docker services are still under review and can
be found here [2].

[1] - kolla-build --base centos --type binary --namespace tripleoupstream
--registry 192.168.24.1:8787 --tag latest --template-override
/usr/share/tripleo-common/container-images/tripleo_kolla_template_overrides.j2
--push


[2] - https://review.openstack.org/#/c/468860/
   https://review.openstack.org/#/c/484376/


Thanks
Numan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

[Numan Siddique]

On Wed, Jul 19, 2017 at 11:37 PM, Ben Nemec <openst...@nemebean.com> wrote:

>
>
> On 07/18/2017 08:18 AM, Numan Siddique wrote:
>
>>
>>
>> On Thu, Jul 13, 2017 at 3:02 PM, Saravanan KR <skram...@redhat.com
>> <mailto:skram...@redhat.com>> wrote:
>>
>> On Tue, Jul 11, 2017 at 11:40 PM, Ben Nemec <openst...@nemebean.com
>> <mailto:openst...@nemebean.com>> wrote:
>> >
>> >
>> > On 07/11/2017 10:17 AM, Numan Siddique wrote:
>> >>
>> >> Hello Tripleo team,
>> >>
>> >> I have few questios regarding migration from neutron ML2OVS to
>> OVN. Below
>> >> are some of the requirements
>> >>
>> >>   - We want to migrate an existing depoyment from Neutroon default
>> ML2OVS
>> >> to OVN
>> >>   - We are targetting this for tripleo Queen's release.
>> >>   - The plan is to first upgrade the tripleo deployment from Pike
>> to
>> >> Queens with no changes to neutron. i.e with neutron ML2OVS. Once
>> the upgrade
>> >> is done, we want to migrate to OVN.
>> >>   - The migration process will stop all the neutron agents,
>> configure
>> >> neutron server to load OVN mechanism driver and start OVN services
>> (with no
>> >> or very limited datapath downtime).
>> >>   - The migration would be handled by an ansible script. We have a
>> PoC
>> >> ansible script which can be found here [1]
>> >>
>> >> And the questions are
>> >> -  (A broad question) - What is the right way to migrate and
>> switch the
>> >> neutron plugin ? Can the stack upgrade handle the migration as
>> well ?
>> This is going to be a broader problem as it is also require to migrate
>> ML2OvS to ODL for NFV deployments, pretty much at the same timeline.
>> If i understand correctly, this migration involves stopping services
>> of ML2OVS (like neutron-ovs-agent) and starting the corresponding new
>> ML2 (OVN or ODL), along with few parameter additions and removals.
>>
>> >> - The migration procedure should be part of tripleo ? or can it be
>> a
>> >> standalone ansible script ? (I presume it should be former).
>> Each service has upgrade steps which can be associated via ansible
>> steps. But this is not a service upgrade. It disables an existing
>> service and enables a new service. So I think, it would need an
>> explicit disabled service [1], stop the required service. And enabled
>> the new service.
>>
>> >> - If it should be part of the tripleo then what would be the
>> command to do
>> >> it ? A update stack command with appropriate environment files for
>> OVN ?
>> >> - In case the migration can be done  as a standalone script, how
>> to handle
>> >> later updates/upgrades since tripleo wouldn't be aware of the
>> migration ?
>> >
>> I would also discourage doing it standalone.
>>
>> Another area which needs to be looked is that, should it be associated
>> with containers upgrade? May be OVN and ODL can be migrated as
>> containers only instead of baremetal by default (just a thought, could
>> have implications to be worked/discussed out).
>>
>> Regards,
>> Saravanan KR
>>
>> [1]
>> https://github.com/openstack/tripleo-heat-templates/tree/mas
>> ter/puppet/services/disabled
>> <https://github.com/openstack/tripleo-heat-templates/tree/ma
>> ster/puppet/services/disabled>
>>
>>  >
>>  > This last point seems like the crux of the discussion here.
>>  Sure, you can
>>  > do all kinds of things to your cloud using standalone bits, but
>> if any of
>>  > them affect things tripleo manages (which this would) then you're
>> going to
>>  > break on the next stack update.
>>  >
>>  > If there are things about the migration that a stack-update can't
>> handle,
>>  > then the migration process would need to be twofold: 1) Run the
>> standalone
>>  > bits to do the migration 2) Update the tripleo configuration to
>> match the
>>  > migrated config so stack-updates work.
>>  >
>>  > This is obviously a complex and error-prone process, so I'd
>> stron

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

[Numan Siddique]

On Thu, Jul 13, 2017 at 3:02 PM, Saravanan KR <skram...@redhat.com> wrote:

> On Tue, Jul 11, 2017 at 11:40 PM, Ben Nemec <openst...@nemebean.com>
> wrote:
> >
> >
> > On 07/11/2017 10:17 AM, Numan Siddique wrote:
> >>
> >> Hello Tripleo team,
> >>
> >> I have few questios regarding migration from neutron ML2OVS to OVN.
> Below
> >> are some of the requirements
> >>
> >>   - We want to migrate an existing depoyment from Neutroon default
> ML2OVS
> >> to OVN
> >>   - We are targetting this for tripleo Queen's release.
> >>   - The plan is to first upgrade the tripleo deployment from Pike to
> >> Queens with no changes to neutron. i.e with neutron ML2OVS. Once the
> upgrade
> >> is done, we want to migrate to OVN.
> >>   - The migration process will stop all the neutron agents, configure
> >> neutron server to load OVN mechanism driver and start OVN services
> (with no
> >> or very limited datapath downtime).
> >>   - The migration would be handled by an ansible script. We have a PoC
> >> ansible script which can be found here [1]
> >>
> >> And the questions are
> >> -  (A broad question) - What is the right way to migrate and switch the
> >> neutron plugin ? Can the stack upgrade handle the migration as well ?
> This is going to be a broader problem as it is also require to migrate
> ML2OvS to ODL for NFV deployments, pretty much at the same timeline.
> If i understand correctly, this migration involves stopping services
> of ML2OVS (like neutron-ovs-agent) and starting the corresponding new
> ML2 (OVN or ODL), along with few parameter additions and removals.
>
> >> - The migration procedure should be part of tripleo ? or can it be a
> >> standalone ansible script ? (I presume it should be former).
> Each service has upgrade steps which can be associated via ansible
> steps. But this is not a service upgrade. It disables an existing
> service and enables a new service. So I think, it would need an
> explicit disabled service [1], stop the required service. And enabled
> the new service.
>
> >> - If it should be part of the tripleo then what would be the command to
> do
> >> it ? A update stack command with appropriate environment files for OVN ?
> >> - In case the migration can be done  as a standalone script, how to
> handle
> >> later updates/upgrades since tripleo wouldn't be aware of the migration
> ?
> >
> I would also discourage doing it standalone.
>
> Another area which needs to be looked is that, should it be associated
> with containers upgrade? May be OVN and ODL can be migrated as
> containers only instead of baremetal by default (just a thought, could
> have implications to be worked/discussed out).
>
> Regards,
> Saravanan KR
>
> [1] https://github.com/openstack/tripleo-heat-templates/tree/
> master/puppet/services/disabled
>
> >
> > This last point seems like the crux of the discussion here.  Sure, you
> can
> > do all kinds of things to your cloud using standalone bits, but if any of
> > them affect things tripleo manages (which this would) then you're going
> to
> > break on the next stack update.
> >
> > If there are things about the migration that a stack-update can't handle,
> > then the migration process would need to be twofold: 1) Run the
> standalone
> > bits to do the migration 2) Update the tripleo configuration to match the
> > migrated config so stack-updates work.
> >
> > This is obviously a complex and error-prone process, so I'd strongly
> > encourage doing it in a tripleo-native fashion instead if at all
> possible.
> >
>


Thanks Ben and Saravanan for your comments.

I did some testing. I first deployed an overcloud with the command [1] and
then I ran the command [2] which enables the OVN services. After the
completion of [2], all the neutron agents were stopped and all the OVN
services were up.

The question is is this the right way to disable some services and enable
some ? or "openstack overcloud update stack" is the right command ?


[1] - openstack overcloud deploy \
--templates /usr/share/openstack-tripleo-heat-templates \
--libvirt-type qemu --control-flavor oooq_control --compute-flavor
oooq_compute --ceph-storage-flavor oooq_ceph --block-storage-flavor
oooq_blockstorage --swift-storage-flavor oooq_objectstorage --timeout 90 -e
/home/stack/cloud-names.yaml-e
/usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml
-e
/usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml
-e /home/stack/network-environment.yaml -e
/u

[openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

[Numan Siddique]

Hello Tripleo team,

I have few questios regarding migration from neutron ML2OVS to OVN. Below
are some of the requirements

 - We want to migrate an existing depoyment from Neutroon default ML2OVS to
OVN
 - We are targetting this for tripleo Queen's release.
 - The plan is to first upgrade the tripleo deployment from Pike to Queens
with no changes to neutron. i.e with neutron ML2OVS. Once the upgrade is
done, we want to migrate to OVN.
 - The migration process will stop all the neutron agents, configure
neutron server to load OVN mechanism driver and start OVN services (with no
or very limited datapath downtime).
 - The migration would be handled by an ansible script. We have a PoC
ansible script which can be found here [1]

And the questions are
-  (A broad question) - What is the right way to migrate and switch the
neutron plugin ? Can the stack upgrade handle the migration as well ?
- The migration procedure should be part of tripleo ? or can it be a
standalone ansible script ? (I presume it should be former).
- If it should be part of the tripleo then what would be the command to do
it ? A update stack command with appropriate environment files for OVN ?
- In case the migration can be done  as a standalone script, how to handle
later updates/upgrades since tripleo wouldn't be aware of the migration ?


Request to provide your comments so that we can move in the right direction.

[1] - https://github.com/openstack/networking-ovn/tree/master/migration

Thanks
Numan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] OpenStack and OVN integration is failing on multi-node physical machines.(probably a bug)

[Numan Siddique]

Hi Pranab,

Request to not drop the mailing list

Please see below for comments.



On Sat, May 27, 2017 at 11:30 AM, pranab boruah <pranabjyotibor...@gmail.com
> wrote:

> Thanks Numan for the reply. I modified the system service script of
> neutron server and made sure that it starts only after ovn-northd service
> is up and running.
>
> Able to launch VMs now.
> But the VMs doesn't get any dhcp ip. Is there any logs relevant to ovn
> native dhcp server that I can look for?
>

Since you are using Newton, you probably need to set ovn_native_dhcp=True
in /etc/neutron/plugin.ini or /etc/neutron/plugins/ml2/ml2_conf.ini.
Otherwise you are expected to use dhcp agent.



>
> I have another question:
> There are two ways to include the OVN specific configurations. One way is
> to add a new [ovn] section in /etc/neutron/plugin.ini file. Second way is
> to modify the /etc/neutron/plugins/networking-ovn/networking-ovn.ini
> file. Which is the right file that we should modify and if I had included
> the ovn configurations in both files, which one takes precedence?
>

Better to use  etc/neutron/plugin.ini or
/etc/neutron/plugins/ml2/ml2_conf.ini. I think the last included config
file overrides the values.


> After all this issues with the setup, we are planning to build a Triple-O
> setup.  I remember Russell Bryant mentioning that there is a Heat template
> for OVN. We are planning to use that. Any caveats/guides you would like to
> recommend for triple-O OVN integration? It would be really useful.
>
>
You need to include
/usr/share/openstack-triple-heat-templates/environments/neutron-ml2-ovn.yaml
[1] in the environment templates when calling openstack overcloud deploy
and it should work.
I would suggest using Ocata or master and OVS 2.7 in order to have a
successful deployment.
You can virt-customize your overcloud image and update ovs if you like.
There is a small script here [2] which does that. You can have a look into
it if you want.


Thanks
Numan



[1] -
https://github.com/openstack/tripleo-heat-templates/blob/master/environments/neutron-ml2-ovn.yaml

[2] -
https://github.com/numansiddique/overcloud_image_for_ovn/blob/master/build_ovn_oc_image.sh



> Thanks
> Pranab
>
>
> On May 24, 2017 23:38, "Numan Siddique" <nusid...@redhat.com> wrote:
>
>
>
> On Tue, May 23, 2017 at 6:48 PM, pranab boruah <
> pranabjyotibor...@gmail.com> wrote:
>
>> Hi,
>> We are building a multi-node physical set-up of OpenStack Newton. The
>> goal is to finally integrate the set-up with OVN.
>> Lab details:
>> 1 Controller, 2 computes
>>
>> CentOS-7.3, OpenStack Newton, separate network for mgmt and tunnel
>> OVS version: 2.6.1
>>
>> I followed the following guide to deploy OpenStack Newton using the
>> PackStack utility:
>>
>> http://networkop.co.uk/blog/2016/11/27/ovn-part1/
>>
>> Before I started integrating with OVN, I made sure that the set-up(ML2
>> and OVS) was working by launching VMs. VMs on cross compute node were
>> able to ping each other.
>>
>> Now, I followed the official guide for OVN integration:
>>
>> http://docs.openstack.org/developer/networking-ovn/install.html
>>
>> Error details :
>> Neutron Server log shows :
>>
>>  ERROR networking_ovn.ovsdb.impl_idl_ovn [-] OVS database connection
>> to OVN_Northbound failed with error: '{u'error': u'unknown database',
>> u'details': u'get_schema request specifies unknown database
>> OVN_Northbound', u'syntax': u'["OVN_Northbound"]'}'. Verify that the
>> OVS and OVN services are available and that the 'ovn_nb_connection'
>> and 'ovn_sb_connection' configuration options are correct.
>>
>> The issue is ovsdb-server on the controller binds with the port
>> 6641.instead of 6640.
>>
>>
>
> Hi Pranab,
> Normally I have seen this happening when neutron-server (i.e the
> networking-ovn ML2 driver) tries to connect to the OVN northbound
> ovsdb-server (on port 6641) and fails (mainly because the OVN NB db
> ovsdb-server) is not running. In such case the code here [1] runs
> "ovs-vsctl add-connection ptcp:6640:.. which causes the main ovsdb-server
> (for conf.db) to listen on port 6641.
>
> Can you make sure that ovsdb-server's for OVN are running before the
> neutron-server is started.
>
> May be to see if it works you can run "ovs-vsctl del-manager" and then run
> netsat -putna | grep 6641 and verify that OVN NB db ovsdb-server listens on
> 6641.
>
> [1] - https://github.com/openstack/neutron/blob/stable/newton/
> neutron/agent/ovsdb/native/connection.py#L82
>   https://github.com/openstack/neutron/blob/stable/newton/
> neutron/agent/ovsdb/native/helpers.py

Re: [openstack-dev] [ovs-discuss] OpenStack and OVN integration is failing on multi-node physical machines.(probably a bug)

[Numan Siddique]

On Tue, May 23, 2017 at 6:48 PM, pranab boruah 
wrote:

> Hi,
> We are building a multi-node physical set-up of OpenStack Newton. The
> goal is to finally integrate the set-up with OVN.
> Lab details:
> 1 Controller, 2 computes
>
> CentOS-7.3, OpenStack Newton, separate network for mgmt and tunnel
> OVS version: 2.6.1
>
> I followed the following guide to deploy OpenStack Newton using the
> PackStack utility:
>
> http://networkop.co.uk/blog/2016/11/27/ovn-part1/
>
> Before I started integrating with OVN, I made sure that the set-up(ML2
> and OVS) was working by launching VMs. VMs on cross compute node were
> able to ping each other.
>
> Now, I followed the official guide for OVN integration:
>
> http://docs.openstack.org/developer/networking-ovn/install.html
>
> Error details :
> Neutron Server log shows :
>
>  ERROR networking_ovn.ovsdb.impl_idl_ovn [-] OVS database connection
> to OVN_Northbound failed with error: '{u'error': u'unknown database',
> u'details': u'get_schema request specifies unknown database
> OVN_Northbound', u'syntax': u'["OVN_Northbound"]'}'. Verify that the
> OVS and OVN services are available and that the 'ovn_nb_connection'
> and 'ovn_sb_connection' configuration options are correct.
>
> The issue is ovsdb-server on the controller binds with the port
> 6641.instead of 6640.
>
>

Hi Pranab,
Normally I have seen this happening when neutron-server (i.e the
networking-ovn ML2 driver) tries to connect to the OVN northbound
ovsdb-server (on port 6641) and fails (mainly because the OVN NB db
ovsdb-server) is not running. In such case the code here [1] runs
"ovs-vsctl add-connection ptcp:6640:.. which causes the main ovsdb-server
(for conf.db) to listen on port 6641.

Can you make sure that ovsdb-server's for OVN are running before the
neutron-server is started.

May be to see if it works you can run "ovs-vsctl del-manager" and then run
netsat -putna | grep 6641 and verify that OVN NB db ovsdb-server listens on
6641.

[1] -
https://github.com/openstack/neutron/blob/stable/newton/neutron/agent/ovsdb/native/connection.py#L82

https://github.com/openstack/neutron/blob/stable/newton/neutron/agent/ovsdb/native/helpers.py#L41

Thanks
Numan

#  netstat -putna | grep 6641
>
> tcp0  0 192.168.10.10:6641  0.0.0.0:*
> LISTEN  809/ovsdb-server
>
> # netstat -putna | grep 6640 (shows no output)
>
> Now, OVN NB DB tries to listen on port 6641, but since it is used by
> the ovsdb-server, it's unable to. PID of ovsdb-server is 809, while
> the pid of OVN NB DB is 4217.
>
> OVN NB DB logs shows this:
>
> 2017-05-23T12:58:09.444Z|01421|ovsdb_jsonrpc_server|ERR|ptcp:6641:0.0.0.0:
> listen failed: Address already in use
> 2017-05-23T12:58:11.946Z|01422|socket_util|ERR|6641:0.0.0.0: bind:
> Address already in use
> 2017-05-23T12:58:14.448Z|01423|socket_util|ERR|6641:0.0.0.0: bind:
> Address already in use
>
> Solutions I tried:
> 1) Completely fresh installing everything.
> 2) Tried with OVS 2.6.0 and 2.7, same issue on all.
> 3) Checked  and verified : SB and NB configuration options in
> plugin.ini are exactly correct.
>
> Please help. Let me know. if additional details are required.
>
> Thanks,
> Pranab
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[Numan Siddique]

On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah <pranabjyotibor...@gmail.com>
wrote:

> Numan,
> Sorry for making this thread too long.
> Kind of deadlock scenario here:
> The process listening on port 6641 is ovsdb-server(not NB db).
>

​This is strange. The default port should be 6640 I suppose if not
specified.

​


> Details:
> Start OVS:
> # /usr/share/openvswitch/scripts/ovs-ctl start  --system-id="random"
> # netstat -putna | grep 6641
> tcp0  0 192.168.10.10:6641  0.0.0.0:*
> LISTEN  5118/ovsdb-server
> # ps -afx | grep ovsdb
>  5118 ?S< 0:00  \_ ovsdb-server /etc/openvswitch/conf.db
> -vconsole:emer -vsyslog:err -vfile:info 
> --remote=punix:/var/run/openvswitch/db.sock
> --private-key=db:Open_vSwitch,SSL,private_key
> --certificate=db:Open_vSwitch,SSL,certificate 
> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert
> --no-chdir --log-file=/var/log/openvswitch/ovsdb-server.log
> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>
> Start NB db
> # /usr/share/openvswitch/scripts/ovn-ctl restart_northd
> --db-sb-create-insecure-remote=yes --db-nb-create-insecure-remote=yes
>
> # netstat -putna | grep 6641
> tcp0  0 192.168.10.10:6641  0.0.0.0:*
> LISTEN  5118/ovsdb-server
>
> # ps -afx | grep ovsdb
>  5118 ?S< 0:00  \_ ovsdb-server /etc/openvswitch/conf.db
> -vconsole:emer -vsyslog:err -vfile:info 
> --remote=punix:/var/run/openvswitch/db.sock
> --private-key=db:Open_vSwitch,SSL,private_key
> --certificate=db:Open_vSwitch,SSL,certificate 
> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert
> --no-chdir --log-file=/var/log/openvswitch/ovsdb-server.log
> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>
>  5215 ?S  0:00  \_ ovsdb-server --detach --monitor
> -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-nb.log
> --remote=punix:/var/run/openvswitch/ovnnb_db.sock 
> --pidfile=/var/run/openvswitch/ovnnb_db.pid
> --remote=db:OVN_Northbound,NB_Global,connections --unixctl=ovnnb_db.ctl
> --private-key=db:OVN_Northbound,SSL,private_key 
> --certificate=db:OVN_Northbound,SSL,certificate
> --ca-cert=db:OVN_Northbound,SSL,ca_cert --remote=ptcp:6641:192.168.10.10
> /etc/openvswitch/ovnnb_db.db
>
>  5223 ?S  0:00  \_ ovsdb-server --detach --monitor
> -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-sb.log
> --remote=punix:/var/run/openvswitch/ovnsb_db.sock 
> --pidfile=/var/run/openvswitch/ovnsb_db.pid
> --remote=db:OVN_Southbound,SB_Global,connections --unixctl=ovnsb_db.ctl
> --private-key=db:OVN_Southbound,SSL,private_key 
> --certificate=db:OVN_Southbound,SSL,certificate
> --ca-cert=db:OVN_Southbound,SSL,ca_cert --remote=ptcp:6642:192.168.10.10
> /etc/openvswitch/ovnsb_db.db
>
> Northbound DB logs show the same error.
>
> Well I am not supposed to kill the ovsdb-server process. Am I ?
>
> Also when I kill the ovsdb-server process, the error goes away. But my
> doubt is we need the ovsdb-server process on the Controller node. Right?
>

​OVN as such doesn't expect ovs-vswitchd (and ovsdb-server for ovs db) ​

​ running in controller node. May be you can stop the ovs-vswitchd service
if you don't need it in the controller.
Also you can configure the NB and SB db ports to some other values if you
wish so and update the new values in appropriate locations.
​Glad that you figured out the issue.

Numan
​


> Thanks for your patience.
>
> Pranab
>
>
>
>
> On 2 February 2017 at 17:45, Numan Siddique <nusid...@redhat.com> wrote:
>
>> In the ovsdb logs I see
>>
>> 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind:
>> Address already in use
>> 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind:
>> Address already in use
>> 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10: bind:
>> Address already in use
>> 2017-02-02T11:07:16.183Z|00023|socket_util|ERR|6641:192.168.10.10: bind:
>> Address already in use
>>
>> Probably you can use netstat and see which processes are listening on
>> port 6641, kill those processes and restart ovn-northd service and see if
>> it works.
>>
>> Thanks
>> Numan
>>
>>
>> On Thu, Feb 2, 2017 at 5:26 PM, pranab boruah <
>> pranabjyotibor...@gmail.com> wrote:
>>
>>> NB db is not listening on the port 6641:
>>>  # ovn-nbctl --db=tcp:192.168.10.10:6641 show
>>> 2017-02-02T11:35:10Z|1|ovsdb_idl|ERR|tcp:192.168.10.10:6641:
>>> requested schema not found
>>> ovn-nbctl: tcp:192.168.10.10:6641: database connection failed (No such
>>> file or director

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[Numan Siddique]

In the ovsdb logs I see

2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind:
Address already in use
2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind:
Address already in use
2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10: bind:
Address already in use
2017-02-02T11:07:16.183Z|00023|socket_util|ERR|6641:192.168.10.10: bind:
Address already in use

Probably you can use netstat and see which processes are listening on port
6641, kill those processes and restart ovn-northd service and see if it
works.

Thanks
Numan


On Thu, Feb 2, 2017 at 5:26 PM, pranab boruah <pranabjyotibor...@gmail.com>
wrote:

> NB db is not listening on the port 6641:
>  # ovn-nbctl --db=tcp:192.168.10.10:6641 show
> 2017-02-02T11:35:10Z|1|ovsdb_idl|ERR|tcp:192.168.10.10:6641:
> requested schema not found
> ovn-nbctl: tcp:192.168.10.10:6641: database connection failed (No such
> file or directory)
>
> # ovn-sbctl --db=tcp:192.168.10.10:6642 show
> Chassis "e8968c35-11db-4b3b-ab24-c20866ac3dc8"
> hostname: "compute-447"
> Encap geneve
> ip: "172.16.10.11"
> options: {csum="true"}
> Encap vxlan
> ip: "172.16.10.11"
> options: {csum="true"}
> Chassis "9f20e7bd-5e16-4273-8ce8-96d0e0a12047"
> hostname: "compute-397"
> Encap geneve
> ip: "172.16.10.12"
> options: {csum="true"}
> Encap vxlan
> ip: "172.16.10.12"
> options: {csum="true"}
>
> # ovsdb-client dump unix:/var/run/openvswitch/ovnnb_db.sock Connection
> Connection table
> _uuidexternal_ids inactivity_probe
> is_connected max_backoff other_config status
> target
>   
>  ---  ---
> -
> c110-5ba2-4125-8a51-3c3db583f267 {}   []
> false[]  {}   {state=BACKOFF} "ptcp:
> 192.168.10.10:6641"
>
> # ovsdb-client dump unix:/var/run/openvswitch/ovnsb_db.sock Connection
> Connection table
> _uuidexternal_ids inactivity_probe
> is_connected max_backoff other_config read_only status
> target
>   
>  ---  - ---
> -
> 1beb9cba-cc01-4981-8a67-a8b265326df9 {}   []
> false[]  {}   false     {state=BACKOFF} "ptcp:
> 192.168.10.10:6642"
>
> No change after restarting Controller node and restating Northd as
> mentioned here:
> https://github.com/openvswitch/ovs/commit/84d0ca5d00fe01b29163236d48fa0f
> 9105687149
>
> Pranab
>
>
>
>
>
> On 2 February 2017 at 17:00, Numan Siddique <nusid...@redhat.com> wrote:
>
>>
>>
>> On Thu, Feb 2, 2017 at 4:44 PM, pranab boruah <
>> pranabjyotibor...@gmail.com> wrote:
>>
>>> Numan,
>>>
>>> Thanks, but, the above commands didn't changed anything. Checked the
>>> logs and found this:
>>>
>>>
>> ​
>> Could you run the below two commands and see how it goes
>>
>>  - "ovn-nbctl --db=tcp:192.168.10.10:6641 show" -> See if this command
>> is successful or not. If not then ovsdb-server is either not listening on
>> this port or it may be possible that you need to add iptables rule to allow
>> this port.
>>
>>  -
>> "ovn-
>> ​s​
>> bctl --db=tcp:192.168.10.10:664
>> ​2​
>> show"
>>  -​
>>
>>
>> ​On the controller node where you are running the ovsdb-server's run
>>  - "sudo ovsdb-client dump unix:/var/run/openvswitch/ovnnb_db.sock
>> Connection"
>> - "sudo ovsdb-client dump unix:/var/run/openvswitch/ovnsb_db.sock
>> Connection"
>> ​
>> If the Connection table is empty, it means ovsdb-server is not listening
>> on the tcp ports.
>>
>> Thanks
>> Numan
>>
>>
>> LOG of NB database:
>>>
>>> 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2017-02-02T11:07:16.183Z|00023|socket_util|ERR|6641:192.168.10.10:
>>> bind: Address already in use
>>> 2

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[Numan Siddique]

On Thu, Feb 2, 2017 at 4:44 PM, pranab boruah <pranabjyotibor...@gmail.com>
wrote:

> Numan,
>
> Thanks, but, the above commands didn't changed anything. Checked the logs
> and found this:
>
>
​
Could you run the below two commands and see how it goes

 - "ovn-nbctl --db=tcp:192.168.10.10:6641 show" -> See if this command is
successful or not. If not then ovsdb-server is either not listening on this
port or it may be possible that you need to add iptables rule to allow this
port.

 -
"ovn-
​s​
bctl --db=tcp:192.168.10.10:664
​2​
show"
 -​


​On the controller node where you are running the ovsdb-server's run
 - "sudo ovsdb-client dump unix:/var/run/openvswitch/ovnnb_db.sock
Connection"
- "sudo ovsdb-client dump unix:/var/run/openvswitch/ovnsb_db.sock
Connection"
​
If the Connection table is empty, it means ovsdb-server is not listening on
the tcp ports.

Thanks
Numan


LOG of NB database:
>
> 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:07:16.183Z|00023|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:07:16.184Z|00024|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:09:55.403Z|00025|ovsdb_jsonrpc_server|INFO|ptcp:6642:
> 192.168.10.10: remote deconfigured
> 2017-02-02T11:09:55.403Z|00026|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:09:55.403Z|00027|ovsdb_jsonrpc_server|ERR|Dropped 10 log
> messages in last 176 seconds (most recently, 159 seconds ago) due to
> excessive rate
> 2017-02-02T11:09:55.403Z|00028|ovsdb_jsonrpc_server|ERR|ptcp:6641:
> 192.168.10.10: listen failed: Address already in use
> 2017-02-02T11:09:55.403Z|00029|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:09:55.403Z|00030|ovsdb_jsonrpc_server|ERR|ptcp:6641:
> 192.168.10.10: listen failed: Address already in use
> 2017-02-02T11:09:57.460Z|00031|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:09:57.460Z|00032|ovsdb_jsonrpc_server|ERR|ptcp:6641:
> 192.168.10.10: listen failed: Address already in use
> 2017-02-02T11:09:57.460Z|00033|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:09:59.961Z|00034|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:02.464Z|00035|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:04.967Z|00036|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:07.469Z|00037|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:09.972Z|00038|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:12.475Z|00039|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:14.978Z|00040|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
> 2017-02-02T11:10:17.481Z|00041|socket_util|ERR|6641:192.168.10.10: bind:
> Address already in use
>
> -Pranab
>
>
> On 2 February 2017 at 16:36, Numan Siddique <nusid...@redhat.com> wrote:
>
>>
>>
>> On Thu, Feb 2, 2017 at 4:00 PM, pranab boruah <
>> pranabjyotibor...@gmail.com> wrote:
>>
>>> Numan,
>>> Details as requested:
>>>
>>> ___
>>> ml2_conf.ini:|
>>> ```
>>> ovn_nb_connection = tcp:192.168.10.10:6641
>>> ovn_sb_connection = tcp:192.168.10.10:6642
>>> ovn_l3_mode = True
>>> ovn_l3_scheduler = chance
>>> ovn_l3_admin_net_cidr = 169.254.128.0/30
>>> ovn_native_dhcp = True
>>>
>>> Note: 192.168.10.10 is the management ip of controller. Firewall,
>>> NetworkManager and SElinux are disabled on all nodes.
>>> 
>>> output of "ps -aef | grep ovsdb" :  |
>>> `
>>> root 21220 21219  0 Feb01 ?00:00:44 ovsdb-server
>>> /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info
>>> --remote=punix:/var/run/openvswitch/db.sock
>>> --private-key=db:Open_vSwitch,SSL,private_key
>>> --certificate=db:Open_vSwitch,SSL,certificate
>>> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --no-chdir
>>> --log-file=/var/log/openvswitch/ovsdb-server.log
>>> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[Numan Siddique]

On Thu, Feb 2, 2017 at 4:00 PM, pranab boruah <pranabjyotibor...@gmail.com>
wrote:

> Numan,
> Details as requested:
>
> ___
> ml2_conf.ini:|
> ```
> ovn_nb_connection = tcp:192.168.10.10:6641
> ovn_sb_connection = tcp:192.168.10.10:6642
> ovn_l3_mode = True
> ovn_l3_scheduler = chance
> ovn_l3_admin_net_cidr = 169.254.128.0/30
> ovn_native_dhcp = True
>
> Note: 192.168.10.10 is the management ip of controller. Firewall,
> NetworkManager and SElinux are disabled on all nodes.
> 
> output of "ps -aef | grep ovsdb" :  |
> `
> root 21220 21219  0 Feb01 ?00:00:44 ovsdb-server
> /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info
> --remote=punix:/var/run/openvswitch/db.sock 
> --private-key=db:Open_vSwitch,SSL,private_key
> --certificate=db:Open_vSwitch,SSL,certificate
> --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --no-chdir
> --log-file=/var/log/openvswitch/ovsdb-server.log
> --pidfile=/var/run/openvswitch/ovsdb-server.pid --detach --monitor
>
> root 21324 21323  0 Feb01 ?00:00:03 ovsdb-server --detach
> --monitor -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-nb.log
> --remote=punix:/var/run/openvswitch/ovnnb_db.sock
> --pidfile=/var/run/openvswitch/ovnnb_db.pid 
> --remote=db:OVN_Northbound,NB_Global,connections
> --unixctl=ovnnb_db.ctl --private-key=db:OVN_Northbound,SSL,private_key
> --certificate=db:OVN_Northbound,SSL,certificate
> --ca-cert=db:OVN_Northbound,SSL,ca_cert /etc/openvswitch/ovnnb_db.db
>
> root 21332 21331  0 Feb01 ?00:00:03 ovsdb-server --detach
> --monitor -vconsole:off --log-file=/var/log/openvswitch/ovsdb-server-sb.log
> --remote=punix:/var/run/openvswitch/ovnsb_db.sock
> --pidfile=/var/run/openvswitch/ovnsb_db.pid 
> --remote=db:OVN_Southbound,SB_Global,connections
> --unixctl=ovnsb_db.ctl --private-key=db:OVN_Southbound,SSL,private_key
> --certificate=db:OVN_Southbound,SSL,certificate
> --ca-cert=db:OVN_Southbound,SSL,ca_cert /etc/openvswitch/ovnsb_db.db
>
> Note: NB and SB databases are supposed to be listening on a tcp socket.
> But it isn't.
>
>
​Running the below commands should solve your problem
  - ovn-nbctl set-connection ptcp:6641:192.168.10.10

- ovn-
​s​
bctl set-connection ptcp:664
​2​
:192.168.10.10

L
​et me know if you still face problems.

The reason for this is this commit -
https://github.com/openvswitch/ovs/commit/84d0ca5d00fe01b29163236d48fa0f9105687149

P
​lease have a look at it.

Thanks
Numan
​
​

> _
> output of logs   |
> ```
> Neutron server log :
>  - http://paste.openstack.org/show/597320/
> ovs-nothd log:
>  - http://paste.openstack.org/show/597322/
> ovs-vswitchd log on Controller:
>   - http://paste.openstack.org/show/597324/
> _
> # ovn-nbctl and ovn-sbctl show no output.   |
> ```
> 
> OVN RPMS installation and download details:   |
> ``
> On controller:
> # git clone https://github.com/openvswitch/ovs.git
> # ./boot.sh
> # ./configure
> # make rpm-fedora RPMBUILD_OPT="--without check"
> # make rpm-fedora-kmod
>
> ALL nodes:
>
> # rpm -i openvswitch-kmod-2.6.90-1.el7.centos.x86_64.rpm#  rpm -U 
> openvswitch-2.6.90-1.el7.centos.x86_64.rpm
>
> Only Controller:
>
> # rpm -i openvswitch-ovn-common-*.x86_64.rpm# rpm -i 
> openvswitch-ovn-central-*.x86_64.rpm
>
> Only Compute:
>
> # rpm -i openvswitch-ovn-common-*.x86_64.rpm# rpm -i 
> openvswitch-ovn-host-*.x86_64.rpm
>
> # lsmod | grep open
>  - shows all the required modules
>
> Let me know if you need anything else.
>
> Thanks.
> pjb
>
>
>
>
>
>
>
>
>
> On 2 February 2017 at 15:23, Numan Siddique <nusid...@redhat.com> wrote:
>
>> Adding openstack-dev ML with [networking-ovn] tag.
>>
>> Please see comments inline
>>
>>
>> On Thu, Feb 2, 2017 at 3:01 PM, pranab boruah <
>> pranabjyotibor...@gmail.com> wrote:
>>
>>> Hi guys,
>>> We have a OpenStack multi-node lab. Everything was working, until I
>>> tried integrating with OVN.
>>> Followed the official guide for integration:
>>>
>>> http://docs.openstack.org/developer/networking-ovn/install.html
>>>
>>> Lab details:
>>> 1 Controller, 2 computes
>>>
>>> CentOS-7.3, OpenStack Newton, separ

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

[Numan Siddique]

Adding openstack-dev ML with [networking-ovn] tag.

Please see comments inline


On Thu, Feb 2, 2017 at 3:01 PM, pranab boruah 
wrote:

> Hi guys,
> We have a OpenStack multi-node lab. Everything was working, until I tried
> integrating with OVN.
> Followed the official guide for integration:
>
> http://docs.openstack.org/developer/networking-ovn/install.html
>
> Lab details:
> 1 Controller, 2 computes
>
> CentOS-7.3, OpenStack Newton, separate network for mgmt and tunnel.
>
> Error details :
> Neutron Server log shows :
>
>  ERROR networking_ovn.ovsdb.impl_idl_ovn [-] OVS database connection to
> OVN_Northbound failed with error: '{u'error': u'unknown database',
> u'details': u'get_schema request specifies unknown database
> OVN_Northbound', u'syntax': u'["OVN_Northbound"]'}'. Verify that the OVS
> and OVN services are available and that the 'ovn_nb_connection' and
> 'ovn_sb_connection' configuration options are correct.
>
> Stuck in this for more than 2 week. Starting to hate my life. Please help.
> Before I tried installing in physical machines, followed the same guide and
> installed in VMs. Everything was working then.
>
> Solutions I tried:
> 1) Completely fresh installing everything.
> 2) Rebuilding ovs
> 3) Check SB and NB configuration options in plugin.ini are exactly correct.
>
>
>
​
Could you please share
 - the values of ovn_nb_connection and ovn_sb_connection defined in
ml2_conf.ini.
 - the output of "ps -aef | grep ovsdb" on the node where you are running
the ovn-northd server.
 - If you could share the output of neutron-server logs in some paste link,
it would be helpful.

Are you able to run "ovn-nbctl show" ? I presume you have installed the
appropriate ovn RPMS ? If not so, please let me know how you have installed
it.

Thanks
Numan

​


> Let me know if additional details are required.
>
>
> -pjb
>
>
>
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ovs-discuss] [Neutron][networking-ovn] OVN + Openstack Issues

[Numan Siddique]

Adding openstack-dev mailing list as it is more relevant.

Please see inline for some comments.
​​

On Sat, Jan 21, 2017 at 9:12 PM, Martin Mailand  wrote:

> Hi,
>
> I tried to use OVN with Openstack, but I ran into an Issue.
>
> I use the OVN packages from the Canonical Cloud archive:
>
> On the controller node:
> ii  ovn-central  2.6.0-0ubuntu2~cloud0
>amd64OVN central components
> ii  ovn-common   2.6.0-0ubuntu2~cloud0
>amd64OVN common components
> ii  ovn-host 2.6.0-0ubuntu2~cloud0
>amd64OVN host components
> ii  python-networking-ovn1.0.1.dev4.201610261100.xenial-0ubuntu1
> all  OpenStack virtual network service - OVN driver
>
> On the compute node:
>
> ii  ovn-common   2.6.0-0ubuntu2~cloud0
>   amd64OVN common components
> ii  ovn-host 2.6.0-0ubuntu2~cloud0
>   amd64OVN host components
>
> If I create a network in Openstack I can see it in the norhd.
>
> ovn-nbctl show
> switch 5cd02e8c-aa16-4246-932e-c1455958daa6
> (neutron-83a25bd6-494b-4d9d-ba74-e824a8efb826)
>
> And I can see my compute nodes
>
> ovn-sbctl show
> Chassis "4a191104-a3b6-4bde-82ee-1a09ea1b9f17"
> hostname: "compute03"
> Encap vxlan
> ip: "172.16.44.130"
> options: {csum="true"}
> Encap geneve
> ip: "172.16.44.130"
> options: {csum="true"}
> Chassis "b0623e67-a2cf-4802-9343-807383e3eb94"
> hostname: "compute01"
> Encap geneve
> ip: "172.16.44.17"
> options: {csum="true"}
> Encap vxlan
> ip: "172.16.44.17"
> options: {csum="true“}
>
>
> But if I try to start a VM I get an error in the neutron-server log, could
> you please advise me
> where my mistake is?
>
> Best regards,
> martin
>
> log:
>
> 2017-01-21 15:33:42.239 10877 ERROR neutron.agent.ovsdb.impl_idl
> [req-fee0a2c8-b205-4e1e-8756-026880fe84cd 44ea98f941ce412d999b3c3dd7fe1dad
> afc5c0f383314e74bdd6bf1e3afbf509 - - -] Traceback (most recent call last):
>   File 
> "/usr/lib/python2.7/dist-packages/neutron/agent/ovsdb/native/connection.py",
> line 115, in run
> txn.results.put(txn.do_commit())
>   File "/usr/lib/python2.7/dist-packages/neutron/agent/ovsdb/impl_idl.py",
> line 105, in do_commit
> ctx.reraise = False
>   File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line
> 220, in __exit__
> self.force_reraise()
>   File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line
> 196, in force_reraise
> six.reraise(self.type_, self.value, self.tb)
>   File "/usr/lib/python2.7/dist-packages/neutron/agent/ovsdb/impl_idl.py",
> line 100, in do_commit
> command.run_idl(txn)
>   File "/usr/lib/python2.7/dist-packages/networking_ovn/ovsdb/commands.py",
> line 712, in run_idl
> raise RuntimeError(msg)
> RuntimeError: Address set as_ip4_c67f0b5b_ce6f_4a82_aa48_803f00b15300
> does not exist. Can't update addresses
>
>
​Looks like the Northbound db is not in sync with neutron db.
Can you run the command "ovn-nbctl list Address_Set" and see if there is a
row for the each of the security groups ?

If you see the ovn northbound db is not in sync, you can sync it by either
running the neutron-ovn-db-sync util or by restarting the neutron-server
after setting ovn-sync-mode=repair in /etc/neutron/plugins/ml2/ml2_conf.ini

Do you see the same issue with devstack ?

Thanks
Numan


​


> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers
> [req-fee0a2c8-b205-4e1e-8756-026880fe84cd 44ea98f941ce412d999b3c3dd7fe1dad
> afc5c0f383314e74bdd6bf1e3afbf509 - - -] Mechanism driver 'ovn' failed in
> create_port_postcommit
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers Traceback
> (most recent call last):
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers   File
> "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line
> 433, in _call_on_drivers
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers
>  getattr(driver.obj, method_name)(context)
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers   File
> "/usr/lib/python2.7/dist-packages/networking_ovn/ml2/mech_driver.py",
> line 556, in create_port_postcommit
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers
>  self.create_port_in_ovn(port, ovn_port_info)
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers   File
> "/usr/lib/python2.7/dist-packages/networking_ovn/ml2/mech_driver.py",
> line 657, in create_port_in_ovn
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers
>  if_exists=False))
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers   File
> "/usr/lib/python2.7/dist-packages/neutron/agent/ovsdb/api.py", line 76,
> in __exit__
> 2017-01-21 15:33:42.240 10877 ERROR neutron.plugins.ml2.managers
>  self.result = self.commit()
> 

Re: [openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

[Numan Siddique]

Thanks for the comments Amitabha.
Please see comments inline

On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas <azbis...@gmail.com> wrote:

> Hi Numan,
>
> Thanks for the proposal. We have also been thinking about this use-case.
>
> If I’m reading this accurately (and I may not be), it seems that the
> proposal is to not have any OVN NB (CUD) operations (R operations outside
> the scope) done by the api_worker threads but rather by a new journal
> thread.
>
>
Correct.
​


> If this is indeed the case, I’d like to consider the scenario when there
> any N neutron nodes, each node with M worker threads. The journal thread at
> the each node contain list of pending operations. Could there be (sequence)
> dependency in the pending operations amongst each the journal threads in
> the nodes that prevents them from getting applied (for e.g.
> Logical_Router_Port and Logical_Switch_Port inter-dependency), because we
> are returning success on neutron operations that have still not been
> committed to the NB DB.
>
>
I
​ts a valid scenario and should be designed properly to handle such
scenarios in case we take this approach.

​

> Couple of clarifications and thoughts below.
>
> Thanks
> Amitabha <abis...@us.ibm.com>
>
> On Jul 13, 2016, at 1:20 AM, Numan Siddique <nusid...@redhat.com> wrote:
>
> Adding the proper tags in subject
>
> On Wed, Jul 13, 2016 at 1:22 PM, Numan Siddique <nusid...@redhat.com>
> wrote:
>
>> Hi Neutrinos,
>>
>> Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and
>> OVN DB
>>  - At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN
>> DB if sync mode is set to repair.
>>  - Admin can run the "neutron-ovn-db-sync-util" to sync the DBs.
>>
>> Recently, in the v2 of networking-odl ML2 driver (Please see (1) below
>> which has more details). (ODL folks please correct me if I am wrong here)
>>
>>   - a journal thread is created which does the CRUD operations of neutron
>> resources asynchronously (i.e it sends the REST APIs to the ODL controller).
>>
>
> Would this be the equivalent of making OVSDB transactions to the OVN NB DB?
>

​Correct.
​


>
>   - a maintenance thread is created which does some cleanup periodically
>> and at startup does full sync if it detects ODL controller cold reboot.
>>
>>
>> Few question I have
>>  - can OVN ML2 driver take same or similar approach. Are there any
>> advantages in taking this approach ? One advantage is neutron resources can
>> be created/updated/deleted even if the OVN ML2 driver has lost connection
>> to the ovsdb-server. The journal thread would eventually sync these
>> resources in the OVN DB. I would like to know the communities thoughts on
>> this.
>>
>
> If we can make it work, it would indeed be a huge plus for system wide
> upgrades and some corner cases in the code (ACL specifically), where the
> post_commit relies on all transactions to be successful and doesn’t revert
> the neutron db if something fails.
>




>
>
>>  - Are there are other ML2 drivers which might have to handle the DB
>> sync's (cases where the other controllers also maintain their own DBs) and
>> how they are handling it ?
>>
>>  - Can a common approach be taken to sync the neutron DB and controller
>> DBs ?
>>
>>
>>
>> ---
>>
>> (1)
>> Sync threads created by networking-odl ML2 driver
>> --
>> ODL ML2 driver creates 2 threads (threading.Thread module) at init
>>  - Journal thread
>>  - Maintenance thread
>>
>> Journal thread
>> 
>> The journal module creates a new journal table by name
>> “opendaylightjournal”  -
>> https://github.com/openstack/networking-odl/blob/master/networking_odl/db/models.py#L23
>>
>> Journal thread will be in loop waiting for the sync event from the ODL
>> ML2 driver.
>>
>>  - ODL ML2 driver resource (network, subnet, port) precommit functions
>> when called by the ML2 plugin adds an entry in the “opendaylightjournal”
>> table with the resource data and sets the journal operation state for this
>> entry to “PENDING”.
>>  - The corresponding resource postcommit function of the ODL ML2 plugin
>> when called, sets the sync event flag.
>>  - A timer is also created which sets the sync event flag when it expires
>> (the default value is 10 seconds).
>>  - Journal thread wake

[openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

[Numan Siddique]

Adding the proper tags in subject

On Wed, Jul 13, 2016 at 1:22 PM, Numan Siddique <nusid...@redhat.com> wrote:

> Hi Neutrinos,
>
> Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and OVN
> DB
>  - At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN
> DB if sync mode is set to repair.
>  - Admin can run the "neutron-ovn-db-sync-util" to sync the DBs.
>
> Recently, in the v2 of networking-odl ML2 driver (Please see (1) below
> which has more details). (ODL folks please correct me if I am wrong here)
>
>   - a journal thread is created which does the CRUD operations of neutron
> resources asynchronously (i.e it sends the REST APIs to the ODL controller).
>   - a maintenance thread is created which does some cleanup periodically
> and at startup does full sync if it detects ODL controller cold reboot.
>
>
> Few question I have
>  - can OVN ML2 driver take same or similar approach. Are there any
> advantages in taking this approach ? One advantage is neutron resources can
> be created/updated/deleted even if the OVN ML2 driver has lost connection
> to the ovsdb-server. The journal thread would eventually sync these
> resources in the OVN DB. I would like to know the communities thoughts on
> this.
>
>  - Are there are other ML2 drivers which might have to handle the DB
> sync's (cases where the other controllers also maintain their own DBs) and
> how they are handling it ?
>
>  - Can a common approach be taken to sync the neutron DB and controller
> DBs ?
>
>
>
> ---
>
> (1)
> Sync threads created by networking-odl ML2 driver
> --
> ODL ML2 driver creates 2 threads (threading.Thread module) at init
>  - Journal thread
>  - Maintenance thread
>
> Journal thread
> 
> The journal module creates a new journal table by name
> “opendaylightjournal”  -
> https://github.com/openstack/networking-odl/blob/master/networking_odl/db/models.py#L23
>
> Journal thread will be in loop waiting for the sync event from the ODL ML2
> driver.
>
>  - ODL ML2 driver resource (network, subnet, port) precommit functions
> when called by the ML2 plugin adds an entry in the “opendaylightjournal”
> table with the resource data and sets the journal operation state for this
> entry to “PENDING”.
>  - The corresponding resource postcommit function of the ODL ML2 plugin
> when called, sets the sync event flag.
>  - A timer is also created which sets the sync event flag when it expires
> (the default value is 10 seconds).
>  - Journal thread wakes up, looks into the “opendaylightjournal” table
> with the entries with state “pending” and runs the CRUD operation on those
> resources in the ODL DB. Once done, it sets the state to “completed”.
>
> Maintenance thread
> --
> Maintenance thread does 3 operations
>  - JournalCleanup - Delete completed rows from journal table
> “opendaylightjournal”.
>  - CleanupProcessing - Mark orphaned processing rows to pending.
>  - Full sync - Re-sync when detecting an ODL "cold reboot”.
>
>
>
> Thanks
> Numan
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

[Numan Siddique]

Hi Neutrinos,

Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and OVN
DB
 - At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN
DB if sync mode is set to repair.
 - Admin can run the "neutron-ovn-db-sync-util" to sync the DBs.

Recently, in the v2 of networking-odl ML2 driver (Please see (1) below
which has more details). (ODL folks please correct me if I am wrong here)

  - a journal thread is created which does the CRUD operations of neutron
resources asynchronously (i.e it sends the REST APIs to the ODL controller).
  - a maintenance thread is created which does some cleanup periodically
and at startup does full sync if it detects ODL controller cold reboot.


Few question I have
 - can OVN ML2 driver take same or similar approach. Are there any
advantages in taking this approach ? One advantage is neutron resources can
be created/updated/deleted even if the OVN ML2 driver has lost connection
to the ovsdb-server. The journal thread would eventually sync these
resources in the OVN DB. I would like to know the communities thoughts on
this.

 - Are there are other ML2 drivers which might have to handle the DB sync's
(cases where the other controllers also maintain their own DBs) and how
they are handling it ?

 - Can a common approach be taken to sync the neutron DB and controller DBs
?


---

(1)
Sync threads created by networking-odl ML2 driver
--
ODL ML2 driver creates 2 threads (threading.Thread module) at init
 - Journal thread
 - Maintenance thread

Journal thread

The journal module creates a new journal table by name
“opendaylightjournal”  -
https://github.com/openstack/networking-odl/blob/master/networking_odl/db/models.py#L23

Journal thread will be in loop waiting for the sync event from the ODL ML2
driver.

 - ODL ML2 driver resource (network, subnet, port) precommit functions when
called by the ML2 plugin adds an entry in the “opendaylightjournal” table
with the resource data and sets the journal operation state for this entry
to “PENDING”.
 - The corresponding resource postcommit function of the ODL ML2 plugin
when called, sets the sync event flag.
 - A timer is also created which sets the sync event flag when it expires
(the default value is 10 seconds).
 - Journal thread wakes up, looks into the “opendaylightjournal” table with
the entries with state “pending” and runs the CRUD operation on those
resources in the ODL DB. Once done, it sets the state to “completed”.

Maintenance thread
--
Maintenance thread does 3 operations
 - JournalCleanup - Delete completed rows from journal table
“opendaylightjournal”.
 - CleanupProcessing - Mark orphaned processing rows to pending.
 - Full sync - Re-sync when detecting an ODL "cold reboot”.



Thanks
Numan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

[Numan Siddique]

Hi Vikram,

Sorry to hear the sad news. My prayers are with you. May you and your family 
have the patience to cope with this event.

Thanks
Numan

On 11/10/2015 08:48 AM, Vikram Choudhary wrote:
> Hi Team,
>
> I won't be able to work for couple of weeks as my mother passed away
> yesterday.
>
> Hope the team will understand and support in this difficult time.
>
> Thanks
> Vikram
> On 10-Nov-2015 2:00 am, "Ihar Hrachyshka"  wrote:
>
>> GMT time zone is available by following the official instructions:
>>
>> https://support.google.com/calendar/answer/37064?hl=en
>>
>> "See other time zones in your calendar” section.
>>
>> Ihar
>>
>> Russell Bryant  wrote:
>>
>> Where do you find this?  I've been using Iceland, but this sounds more
>>> explicit.  For me it makes me pick a country and then a TZ, so I'm not
>>> seeing the "GMT (no daylight saving)" option anywhere.
>>>
>>> --
>>> Russell
>>>
>>> On 11/09/2015 02:39 PM, Ihar Hrachyshka wrote:
>>>
 There is also 'GMT (no daylight saving)’ TZ available in Google Calendar
 that is identical to UTC for all practical matters.

 Ihar

 Carl Baldwin  wrote:

 I've been using Iceland's TZ for this.  Seems to work well and handle
> the TZ changes nicely.
>
> Carl
>
> On Sat, Nov 7, 2015 at 7:24 AM, Sean M. Collins 
> wrote:
>
>> Learn from my mistake, check your calendar for the timezone if you've
>> created an event for the weekly meetings. Google makes it a hassle to
>> set things in UTC time, so I was caught by surprise by the FwaaS
>> meeting
>> due to the DST change in the US of A.
>>
>> --
>> Sean M. Collins
>>
>>
>> __
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Question on functional tests

[Numan Siddique]

Yes. That's right.

Also there is a unit test here [1] which mocks ip netns exec.

[1] - 
https://review.openstack.org/#/c/145005/5/neutron_vpnaas/tests/unit/services/vpn/device_drivers/test_ipsec.py


Thanks
Numan

On 01/21/2015 02:22 PM, Kevin Benton wrote:
So the test wouldn't make much sense then without the creation of the 
namespace, right? If that's the case, it sounds like it is a very low 
level functional test making sure that routes can be installed into 
namespaces.


On Wed, Jan 21, 2015 at 12:19 AM, Numan Siddique 
numan.siddi...@enovance.com mailto:numan.siddi...@enovance.com wrote:


It is asserting the return value of ip netns exec ns ip route
get ip_address.


Thanks
Numan


On 01/21/2015 12:34 PM, Kevin Benton wrote:

Is the test asserting things about interactions with the system,
or does it just happen to use a system call as a side effect of
one of the setups?

On Tue, Jan 20, 2015 at 1:24 PM, Paul Michali p...@michali.net
mailto:p...@michali.net wrote:

My question is whether the tests proposed should be unit
tests or functional tests. They only test one method, and
it's not a complete piece of functionality - like creating a
VPN connection.

If that one system call is mocked, these could all be treated
as unit tests. So I'm wondering if there is an advantage in
actually testing the system call (getaddrinfo), as part of
this work?


Thoughts?

PCM (Paul Michali)

IRC pc_m (irc.freenode.com http://irc.freenode.com)
Twitter... @pmichali


On Tue, Jan 20, 2015 at 3:02 PM, Kevin Benton
blak...@gmail.com mailto:blak...@gmail.com wrote:

I don't believe we have any unit tests that create
namespaces or veth pairs. This sounds like it belongs
with functional tests.

On Tue, Jan 20, 2015 at 10:20 AM, Numan Siddique
numan.siddi...@enovance.com
mailto:numan.siddi...@enovance.com wrote:

Hello,

I am working on a bug [1] on neutron vpnaas and
submitted the patch here [2].

The test code to test the fix does the following
- creates a namespace
- creates a veth pair and add one interface into
the namespace
- configures the interface with an ip address and
- adds a default gateway
- and of course tests the code.

This test code only tests a specific function
(OpenSwanProcess._get_nexthop())

Reviewers of this patch are not clear if this should
be part of functional tests or unit tests.
Can unit tests create linux namespaces, interfaces
etc or it falls under functional tests?

Please let me know your thoughts on this.

[1] - https://bugs.launchpad.net/neutron/+bug/1405413
[2] - https://review.openstack.org/#/c/145005/5


Regards
Numan



__
OpenStack Development Mailing List (not for usage
questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Kevin Benton



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Kevin Benton



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe  
mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Question on functional tests

[Numan Siddique]

It is asserting the return value of ip netns exec ns ip route get 
ip_address.



Thanks
Numan


On 01/21/2015 12:34 PM, Kevin Benton wrote:
Is the test asserting things about interactions with the system, or 
does it just happen to use a system call as a side effect of one of 
the setups?


On Tue, Jan 20, 2015 at 1:24 PM, Paul Michali p...@michali.net 
mailto:p...@michali.net wrote:


My question is whether the tests proposed should be unit tests or
functional tests. They only test one method, and it's not a
complete piece of functionality - like creating a VPN connection.

If that one system call is mocked, these could all be treated as
unit tests. So I'm wondering if there is an advantage in actually
testing the system call (getaddrinfo), as part of this work?


Thoughts?

PCM (Paul Michali)

IRC pc_m (irc.freenode.com http://irc.freenode.com)
Twitter... @pmichali


On Tue, Jan 20, 2015 at 3:02 PM, Kevin Benton blak...@gmail.com
mailto:blak...@gmail.com wrote:

I don't believe we have any unit tests that create namespaces
or veth pairs. This sounds like it belongs with functional tests.

On Tue, Jan 20, 2015 at 10:20 AM, Numan Siddique
numan.siddi...@enovance.com
mailto:numan.siddi...@enovance.com wrote:

Hello,

I am working on a bug [1] on neutron vpnaas and submitted
the patch here [2].

The test code to test the fix does the following
- creates a namespace
- creates a veth pair and add one interface into the
namespace
- configures the interface with an ip address and
- adds a default gateway
- and of course tests the code.

This test code only tests a specific function
(OpenSwanProcess._get_nexthop())

Reviewers of this patch are not clear if this should be
part of functional tests or unit tests.
Can unit tests create linux namespaces, interfaces etc or
it falls under functional tests?

Please let me know your thoughts on this.

[1] - https://bugs.launchpad.net/neutron/+bug/1405413
[2] - https://review.openstack.org/#/c/145005/5


Regards
Numan



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Kevin Benton



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Kevin Benton


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] Question on functional tests

[Numan Siddique]

Hello,

I am working on a bug [1] on neutron vpnaas and submitted the patch here 
[2].


The test code to test the fix does the following
- creates a namespace
- creates a veth pair and add one interface into the namespace
- configures the interface with an ip address and
- adds a default gateway
- and of course tests the code.

This test code only tests a specific function 
(OpenSwanProcess._get_nexthop())


Reviewers of this patch are not clear if this should be part of 
functional tests or unit tests.
Can unit tests create linux namespaces, interfaces etc or it falls under 
functional tests?


Please let me know your thoughts on this.

[1] - https://bugs.launchpad.net/neutron/+bug/1405413
[2] - https://review.openstack.org/#/c/145005/5


Regards
Numan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev