Date   

Re: Openstack-ODL integration - stacking issues with pbr

Anil Vishnoi
 

Eric,

Changing the required version can put you into some nasty cyclic package dependency issues, but as far as you are not seeing it right now you can continue. :)

So are you installing packages form yum repo or building it through devstack code? If you are using yum and if your VM has old devstack installation,, it gives these version issues and i have seen many time. I generally remove all the python packages from /opt/stack/ installed by devstack installation and then use pip to install the required version. That generally solve these kind of issues in my environment.

ANil

On Thu, Aug 6, 2015 at 10:48 PM, Multanen, Eric W <eric.w.multanen@...> wrote:

Thanks Sam and Anil.

 

Yes – the system (not a VM) has external network connectivity.

 

I worked around the pbr issue by editing out the “>=1.3” requirement for pbr in networking-odl/setup.py.

 

I know I’d tried flavio’s networking-odl the other day – I don’t think (or recall) that it helped with this issue.  The issue I was hoping Flavio’s would help with was setting the controller on br-int on the control node – it did not help with that either – so I’m setting that manually after stacking completes.

 

Thanks,

Eric

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, August 6, 2015 9:40 AM
To: Sam Hague
Cc: Multanen, Eric W; ovsdb-dev@...
Subject: Re: [ovsdb-dev] Openstack-ODL integration - stacking issues with pbr

 

Hi Eric,

 

is you VM has external network connectivity?

 

2015-08-05 14:59:53.160 | Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found!

 

Anil

 

On Thu, Aug 6, 2015 at 9:55 PM, Sam Hague <shague@...> wrote:

Eric,

could you point to flavio's networking-odl and see if that get's past the issue? pbr 1.3 was an issue so I added a patch to drop it back to an earlier version.

We have seen pbr issues and they are a pain to get around since so much is happening behind the scenes.

Thanks, Sam


----- Original Message -----
> From: "Eric W Multanen" <eric.w.multanen@...>
> To: ovsdb-dev@...
> Sent: Thursday, August 6, 2015 11:19:22 AM
> Subject: [ovsdb-dev]  Openstack-ODL integration - stacking issues with pbr
>
>
>
> Hi ODL Netvirt experts (Flavio, Sam, etc.),
>
>
>
> I’m trying to setup OVSDB Netvirt with Openstack stable/kilo 2015.1.1
>
> On Fedora 21 systems – not the vagrant/vm based examples.
>
>
>
> The problem appears to be around version requirements for a python pbr
> package.
>
>
>
> Are there any known resolutions or hints for this issue?
>
>
>
> I am using the 2015.1.1 tag for most of the openstack packages, or
> stable/kilo branch for the ones that don’t have that tag.
>
>
>
> Using the stable/kilo branch of the networking-odl driver, I get the
> following error when trying to stack (devstack):
>
>
>
> 2015-08-05 14:57:45.472 | Installing the Networking-ODL driver for
> OpenDaylight
>
> 2015-08-05 14:59:53.160 | Download error on
> https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out --
> Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/:
> [Errno 110] Connection timed out -- Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | No local packages or download links found for
> pbr>=1.3
>
> 2015-08-05 15:02:00.476 | Traceback (most recent call last):
>
> 2015-08-05 15:02:00.477 | File "setup.py", line 29, in <module>
>
> 2015-08-05 15:02:00.477 | pbr=True)
>
> 2015-08-05 15:02:00.477 | File "/usr/lib64/python2.7/distutils/core.py", line
> 111, in setup
>
> 2015-08-05 15:02:00.477 | _setup_distribution = dist = klass(attrs)
>
> 2015-08-05 15:02:00.477 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
>
> 2015-08-05 15:02:00.477 | self.fetch_build_eggs(attrs['setup_requires'])
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 313, in
> fetch_build_eggs
>
> 2015-08-05 15:02:00.478 | replace_conflicting=True,
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in
> resolve
>
> 2015-08-05 15:02:00.478 | dist = best[req.key] = env.best_match(req, ws,
> installer)
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in
> best_match
>
> 2015-08-05 15:02:00.479 | return self.obtain(req, installer)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in
> obtain
>
> 2015-08-05 15:02:00.479 | return installer(requirement)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 380, in
> fetch_build_egg
>
> 2015-08-05 15:02:00.479 | return cmd.easy_install(req)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line
> 623, in easy_install
>
> 2015-08-05 15:02:00.480 | raise DistutilsError(msg)
>
> 2015-08-05 15:02:00.480 | distutils.errors.DistutilsError: Could not find
> suitable distribution for Requirement.parse('pbr>=1.3')
>
> 2015-08-05 15:02:00.516 | Error on exit
>
>
>
>
>
> Thanks,
>
> Eric
>
>
>
>
>
>
>
>
>

> _______________________________________________
> ovsdb-dev mailing list
> ovsdb-dev@...
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



 

--

Thanks

Anil




--
Thanks
Anil


Re: Openstack-ODL integration - stacking issues with pbr

Multanen, Eric W
 

Thanks Sam and Anil.

 

Yes – the system (not a VM) has external network connectivity.

 

I worked around the pbr issue by editing out the “>=1.3” requirement for pbr in networking-odl/setup.py.

 

I know I’d tried flavio’s networking-odl the other day – I don’t think (or recall) that it helped with this issue.  The issue I was hoping Flavio’s would help with was setting the controller on br-int on the control node – it did not help with that either – so I’m setting that manually after stacking completes.

 

Thanks,

Eric

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, August 6, 2015 9:40 AM
To: Sam Hague
Cc: Multanen, Eric W; ovsdb-dev@...
Subject: Re: [ovsdb-dev] Openstack-ODL integration - stacking issues with pbr

 

Hi Eric,

 

is you VM has external network connectivity?

 

2015-08-05 14:59:53.160 | Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found!

 

Anil

 

On Thu, Aug 6, 2015 at 9:55 PM, Sam Hague <shague@...> wrote:

Eric,

could you point to flavio's networking-odl and see if that get's past the issue? pbr 1.3 was an issue so I added a patch to drop it back to an earlier version.

We have seen pbr issues and they are a pain to get around since so much is happening behind the scenes.

Thanks, Sam


----- Original Message -----
> From: "Eric W Multanen" <eric.w.multanen@...>
> To: ovsdb-dev@...
> Sent: Thursday, August 6, 2015 11:19:22 AM
> Subject: [ovsdb-dev]  Openstack-ODL integration - stacking issues with pbr
>
>
>
> Hi ODL Netvirt experts (Flavio, Sam, etc.),
>
>
>
> I’m trying to setup OVSDB Netvirt with Openstack stable/kilo 2015.1.1
>
> On Fedora 21 systems – not the vagrant/vm based examples.
>
>
>
> The problem appears to be around version requirements for a python pbr
> package.
>
>
>
> Are there any known resolutions or hints for this issue?
>
>
>
> I am using the 2015.1.1 tag for most of the openstack packages, or
> stable/kilo branch for the ones that don’t have that tag.
>
>
>
> Using the stable/kilo branch of the networking-odl driver, I get the
> following error when trying to stack (devstack):
>
>
>
> 2015-08-05 14:57:45.472 | Installing the Networking-ODL driver for
> OpenDaylight
>
> 2015-08-05 14:59:53.160 | Download error on
> https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out --
> Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/:
> [Errno 110] Connection timed out -- Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | No local packages or download links found for
> pbr>=1.3
>
> 2015-08-05 15:02:00.476 | Traceback (most recent call last):
>
> 2015-08-05 15:02:00.477 | File "setup.py", line 29, in <module>
>
> 2015-08-05 15:02:00.477 | pbr=True)
>
> 2015-08-05 15:02:00.477 | File "/usr/lib64/python2.7/distutils/core.py", line
> 111, in setup
>
> 2015-08-05 15:02:00.477 | _setup_distribution = dist = klass(attrs)
>
> 2015-08-05 15:02:00.477 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
>
> 2015-08-05 15:02:00.477 | self.fetch_build_eggs(attrs['setup_requires'])
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 313, in
> fetch_build_eggs
>
> 2015-08-05 15:02:00.478 | replace_conflicting=True,
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in
> resolve
>
> 2015-08-05 15:02:00.478 | dist = best[req.key] = env.best_match(req, ws,
> installer)
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in
> best_match
>
> 2015-08-05 15:02:00.479 | return self.obtain(req, installer)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in
> obtain
>
> 2015-08-05 15:02:00.479 | return installer(requirement)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 380, in
> fetch_build_egg
>
> 2015-08-05 15:02:00.479 | return cmd.easy_install(req)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line
> 623, in easy_install
>
> 2015-08-05 15:02:00.480 | raise DistutilsError(msg)
>
> 2015-08-05 15:02:00.480 | distutils.errors.DistutilsError: Could not find
> suitable distribution for Requirement.parse('pbr>=1.3')
>
> 2015-08-05 15:02:00.516 | Error on exit
>
>
>
>
>
> Thanks,
>
> Eric
>
>
>
>
>
>
>
>
>

> _______________________________________________
> ovsdb-dev mailing list
> ovsdb-dev@...
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



 

--

Thanks

Anil


Re: Openstack-ODL integration - stacking issues with pbr

Anil Vishnoi
 

Hi Eric,

is you VM has external network connectivity?

2015-08-05 14:59:53.160 | Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found!


Anil


On Thu, Aug 6, 2015 at 9:55 PM, Sam Hague <shague@...> wrote:
Eric,

could you point to flavio's networking-odl and see if that get's past the issue? pbr 1.3 was an issue so I added a patch to drop it back to an earlier version.

We have seen pbr issues and they are a pain to get around since so much is happening behind the scenes.

Thanks, Sam

----- Original Message -----
> From: "Eric W Multanen" <eric.w.multanen@...>
> To: ovsdb-dev@...
> Sent: Thursday, August 6, 2015 11:19:22 AM
> Subject: [ovsdb-dev]  Openstack-ODL integration - stacking issues with pbr
>
>
>
> Hi ODL Netvirt experts (Flavio, Sam, etc.),
>
>
>
> I’m trying to setup OVSDB Netvirt with Openstack stable/kilo 2015.1.1
>
> On Fedora 21 systems – not the vagrant/vm based examples.
>
>
>
> The problem appears to be around version requirements for a python pbr
> package.
>
>
>
> Are there any known resolutions or hints for this issue?
>
>
>
> I am using the 2015.1.1 tag for most of the openstack packages, or
> stable/kilo branch for the ones that don’t have that tag.
>
>
>
> Using the stable/kilo branch of the networking-odl driver, I get the
> following error when trying to stack (devstack):
>
>
>
> 2015-08-05 14:57:45.472 | Installing the Networking-ODL driver for
> OpenDaylight
>
> 2015-08-05 14:59:53.160 | Download error on
> https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out --
> Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/:
> [Errno 110] Connection timed out -- Some packages may not be found!
>
> 2015-08-05 15:02:00.392 | No local packages or download links found for
> pbr>=1.3
>
> 2015-08-05 15:02:00.476 | Traceback (most recent call last):
>
> 2015-08-05 15:02:00.477 | File "setup.py", line 29, in <module>
>
> 2015-08-05 15:02:00.477 | pbr=True)
>
> 2015-08-05 15:02:00.477 | File "/usr/lib64/python2.7/distutils/core.py", line
> 111, in setup
>
> 2015-08-05 15:02:00.477 | _setup_distribution = dist = klass(attrs)
>
> 2015-08-05 15:02:00.477 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__
>
> 2015-08-05 15:02:00.477 | self.fetch_build_eggs(attrs['setup_requires'])
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 313, in
> fetch_build_eggs
>
> 2015-08-05 15:02:00.478 | replace_conflicting=True,
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in
> resolve
>
> 2015-08-05 15:02:00.478 | dist = best[req.key] = env.best_match(req, ws,
> installer)
>
> 2015-08-05 15:02:00.478 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in
> best_match
>
> 2015-08-05 15:02:00.479 | return self.obtain(req, installer)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in
> obtain
>
> 2015-08-05 15:02:00.479 | return installer(requirement)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 380, in
> fetch_build_egg
>
> 2015-08-05 15:02:00.479 | return cmd.easy_install(req)
>
> 2015-08-05 15:02:00.479 | File
> "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line
> 623, in easy_install
>
> 2015-08-05 15:02:00.480 | raise DistutilsError(msg)
>
> 2015-08-05 15:02:00.480 | distutils.errors.DistutilsError: Could not find
> suitable distribution for Requirement.parse('pbr>=1.3')
>
> 2015-08-05 15:02:00.516 | Error on exit
>
>
>
>
>
> Thanks,
>
> Eric
>
>
>
>
>
>
>
>
>
> _______________________________________________
> ovsdb-dev mailing list
> ovsdb-dev@...
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



--
Thanks
Anil


Re: Openstack-ODL integration - stacking issues with pbr

Sam Hague
 

Eric,

could you point to flavio's networking-odl and see if that get's past the issue? pbr 1.3 was an issue so I added a patch to drop it back to an earlier version.

We have seen pbr issues and they are a pain to get around since so much is happening behind the scenes.

Thanks, Sam

----- Original Message -----
From: "Eric W Multanen" <eric.w.multanen@...>
To: ovsdb-dev@...
Sent: Thursday, August 6, 2015 11:19:22 AM
Subject: [ovsdb-dev] Openstack-ODL integration - stacking issues with pbr



Hi ODL Netvirt experts (Flavio, Sam, etc.),



I’m trying to setup OVSDB Netvirt with Openstack stable/kilo 2015.1.1

On Fedora 21 systems – not the vagrant/vm based examples.



The problem appears to be around version requirements for a python pbr
package.



Are there any known resolutions or hints for this issue?



I am using the 2015.1.1 tag for most of the openstack packages, or
stable/kilo branch for the ones that don’t have that tag.



Using the stable/kilo branch of the networking-odl driver, I get the
following error when trying to stack (devstack):



2015-08-05 14:57:45.472 | Installing the Networking-ODL driver for
OpenDaylight

2015-08-05 14:59:53.160 | Download error on
https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out --
Some packages may not be found!

2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/:
[Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | No local packages or download links found for
pbr>=1.3

2015-08-05 15:02:00.476 | Traceback (most recent call last):

2015-08-05 15:02:00.477 | File "setup.py", line 29, in <module>

2015-08-05 15:02:00.477 | pbr=True)

2015-08-05 15:02:00.477 | File "/usr/lib64/python2.7/distutils/core.py", line
111, in setup

2015-08-05 15:02:00.477 | _setup_distribution = dist = klass(attrs)

2015-08-05 15:02:00.477 | File
"/usr/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__

2015-08-05 15:02:00.477 | self.fetch_build_eggs(attrs['setup_requires'])

2015-08-05 15:02:00.478 | File
"/usr/lib/python2.7/site-packages/setuptools/dist.py", line 313, in
fetch_build_eggs

2015-08-05 15:02:00.478 | replace_conflicting=True,

2015-08-05 15:02:00.478 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in
resolve

2015-08-05 15:02:00.478 | dist = best[req.key] = env.best_match(req, ws,
installer)

2015-08-05 15:02:00.478 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in
best_match

2015-08-05 15:02:00.479 | return self.obtain(req, installer)

2015-08-05 15:02:00.479 | File
"/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in
obtain

2015-08-05 15:02:00.479 | return installer(requirement)

2015-08-05 15:02:00.479 | File
"/usr/lib/python2.7/site-packages/setuptools/dist.py", line 380, in
fetch_build_egg

2015-08-05 15:02:00.479 | return cmd.easy_install(req)

2015-08-05 15:02:00.479 | File
"/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line
623, in easy_install

2015-08-05 15:02:00.480 | raise DistutilsError(msg)

2015-08-05 15:02:00.480 | distutils.errors.DistutilsError: Could not find
suitable distribution for Requirement.parse('pbr>=1.3')

2015-08-05 15:02:00.516 | Error on exit





Thanks,

Eric









_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Openstack-ODL integration - stacking issues with pbr

Multanen, Eric W
 

Hi ODL Netvirt experts (Flavio, Sam, etc.),

 

I’m trying to setup OVSDB Netvirt with Openstack stable/kilo 2015.1.1

On Fedora 21 systems – not the vagrant/vm based examples.

 

The problem appears to be around version requirements for a python pbr package.

 

Are there any known resolutions or hints for this issue?

 

I am using the 2015.1.1 tag for most of the openstack packages, or stable/kilo branch for the ones that don’t have that tag.

 

Using the stable/kilo branch of the networking-odl driver, I get the following error when trying to stack (devstack):

 

2015-08-05 14:57:45.472 | Installing the Networking-ODL driver for OpenDaylight

2015-08-05 14:59:53.160 | Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | Download error on https://pypi.python.org/simple/: [Errno 110] Connection timed out -- Some packages may not be found!

2015-08-05 15:02:00.392 | No local packages or download links found for pbr>=1.3

2015-08-05 15:02:00.476 | Traceback (most recent call last):

2015-08-05 15:02:00.477 |   File "setup.py", line 29, in <module>

2015-08-05 15:02:00.477 |     pbr=True)

2015-08-05 15:02:00.477 |   File "/usr/lib64/python2.7/distutils/core.py", line 111, in setup

2015-08-05 15:02:00.477 |     _setup_distribution = dist = klass(attrs)

2015-08-05 15:02:00.477 |   File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 268, in __init__

2015-08-05 15:02:00.477 |     self.fetch_build_eggs(attrs['setup_requires'])

2015-08-05 15:02:00.478 |   File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs

2015-08-05 15:02:00.478 |     replace_conflicting=True,

2015-08-05 15:02:00.478 |   File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 836, in resolve

2015-08-05 15:02:00.478 |     dist = best[req.key] = env.best_match(req, ws, installer)

2015-08-05 15:02:00.478 |   File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1081, in best_match

2015-08-05 15:02:00.479 |     return self.obtain(req, installer)

2015-08-05 15:02:00.479 |   File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1093, in obtain

2015-08-05 15:02:00.479 |     return installer(requirement)

2015-08-05 15:02:00.479 |   File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg

2015-08-05 15:02:00.479 |     return cmd.easy_install(req)

2015-08-05 15:02:00.479 |   File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 623, in easy_install

2015-08-05 15:02:00.480 |     raise DistutilsError(msg)

2015-08-05 15:02:00.480 | distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=1.3')

2015-08-05 15:02:00.516 | Error on exit

 

 

Thanks,

Eric

 

 

 

 


ovsdb usage of custom.properties

Edward Warnicke <hagbard@...>
 

Guys,
   I was reviewing:


(which is a totally fine patch) and it occurred to me to make the suggestion that you guys
either use the config subsystem to configure these things or ConfigAdmin so that you can
get your config parameters out of custom.properties and into a place you manage yourselves
in ovsdb.

Please note: I'm not demanding you do this... I'm just politely suggesting that you might 
be happier if you did :)

Ed


Re: Be Test Contact

Williams, Marcus <marcus.williams@...>
 

I'm also interested in the Test Contact for Be role. Though happy to let
Alexis do it and help out.

Thanks,
Marcus

-----Original Message-----
From: ovsdb-dev-bounces@...
[mailto:ovsdb-dev-bounces@...] On Behalf Of Alexis de
Talhouet
Sent: Tuesday, August 4, 2015 7:50 AM
To: Sam Hague
Cc: ovsdb-dev
Subject: Re: [ovsdb-dev] Be Test Contact

Sam,

I'll be glad to be the be in charge of the test tasks for Be.

Thanks,
Alexis

On Aug 4, 2015, at 4:16 AM, Sam Hague <shague@...> wrote:

Hi all,

We are looking for a volunteer(s) for the Be test contact. Per [1] we need
to identify a test contact to coordinate the test tasks. Please let me know
if you would like to volunteer for the role.

The main responsibilities:

- Coordinate with the Integration Test team
- Coordinate with Release Planning for test requirements
- Coordinate communication for OVSDB test questions and concerns

Thanks, Sam

[1]
https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Rele
ase_Plan _______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


debugging ovsdb system tests

Jamo Luhrsen <jluhrsen@...>
 

Chaudhry (CC'd ovsdb and integration dev),

I've spent some time debugging your troubles [0] in the sandbox.  It looks
like the trouble is coming from something being done in either of your
vxlan test suites.  As soon as one of those suites is run, it's no
longer possible to ssh in to the mininet VMs.

You can toggle the order in which suites are run [1] (search for pybot) to
verify this if you want, but I wonder if you run this in your local environment
you might also have trouble.  Running a single vxlan suite seems to be
fine, but running any other suite after it fails.  even running the same
vxlan suite back to back will see the first one PASS and the second one
FAIL.

Let me know if you can see this in your own environment, and if not we'll
have to keep digging in the sandbox to find the root cause.

The final few steps of the vlxan suite are to:

-  stop mininet (requires logging in to VM and that works)
-  sending a DELETE to:
    /restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2F${MININET}:6634
    (that gives a 200 response)

then the next suite runs and it's first attempt to log in to the ${MININET} system
fails.  Could there be some networking issue on the linux level that gets
triggered by playing with vxlan and then deleting the node from restconf?
(thinking out loud)

Let me know what you figure out and I'll see what I can do to help
after that.

Thanks,
JamO

[0]  https://jenkins.opendaylight.org/releng/job/ovsdb-csit-verify-southbound-master/116/
[1]  https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-1node-cds-southbound-all-master/configure


OVSDB Team Interest List

Sam Hague
 

Hi all,

please add your name to the spreadsheet [1] below. This will help identify those of us with crazy handles and align interests.

Thanks, Sam

[1] https://docs.google.com/spreadsheets/d/16W8LOt5hWjJEezfYPK9t5Kf1wKgb8xwujfU8HT2fgas/edit#gid=0


Re: Migration of OVS ML2 to ODL ML2 for Neutron

Dave Neary <dneary@...>
 

Thanks Wojciech,

Ed told me that the flows would be cleared by the controller when it connected - is that not right?

Thanks,
Dave.

----- Wojciech Dec <wdec.ietf@...> wrote:

Hi Dave,

I believe that it will be necessary to clear all flows in OVS, before step
4.

-Wojciech.

On 1 August 2015 at 21:33, Dave Neary <dneary@...> wrote:

Hi,

I had conversations last week with a number of you about this topic, and
just wanted to strike while the iron was hot to get it on the Be
planning cycle (if any work needs doing).

When someone is deciding to use ODL for OpenStack Neutron, my
expectation would be that they're not starting from scratch - in all
probability, either they are currently using nova-network or they're
using the defail OVS ML2 plug-in.

Migrating from nova-network to Neutron is already a hairy topic, but
migrating an existing cloud from OVS to ODL easily would make it easier
to adopt ODL. My understanding before last week was that you didn't have
a choice - to migrate to ODL from OVSDB required deleting and
reinitialising the ovsdb database on all of the Nova compute nodes, as
documented here:
https://wiki.opendaylight.org/view/OpenStack_and_OpenDaylight

But in conversation last week, the following procedure was suggested. My
question is, can we document and test this, and verify that it works?

Migration procesure:

0. Install and start ODL
1. Stop neutron-service (doesn't affect dataplane for existing instances)
2. On each OVS instance: stop and disable neutron-openvswitch-agent
3. Update Neutron config to use ODL mechanism
4. On each OVS instance: set-manager to ODL

It'll be important for Neutron to be connected to ODL before setting ODL
as the manager for the vswitch, as once you do a set-manager, ODL will
write flows to the switches. The contention is, since the compute
instances are still connected to OVS, the set-manager will also kick off
ovsdb events which will lead to everything converging on a consistent
state - ODL will wipe any old flows from the switches, and will rewire
instances to the appropriate network IDs, and set all the flows, vlan
tags, etc as they should be.

Will this work? I'm going to try it out when I get home (in a few days),
but I wanted to get something written down & argued about ASAP.

Thanks,
Dave.

--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Re: Be Test Contact

Alexis de Talhouet <adetalhouet@...>
 

Sam,

I’ll be glad to be the be in charge of the test tasks for Be.

Thanks,
Alexis

On Aug 4, 2015, at 4:16 AM, Sam Hague <shague@...> wrote:

Hi all,

We are looking for a volunteer(s) for the Be test contact. Per [1] we need to identify a test contact to coordinate the test tasks. Please let me know if you would like to volunteer for the role.

The main responsibilities:

- Coordinate with the Integration Test team
- Coordinate with Release Planning for test requirements
- Coordinate communication for OVSDB test questions and concerns

Thanks, Sam

[1] https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Re: Migration of OVS ML2 to ODL ML2 for Neutron

Wojciech Dec <wdec.ietf@...>
 

Hi Dave,

I believe that it will be necessary to clear all flows in OVS, before step 4.

-Wojciech.

On 1 August 2015 at 21:33, Dave Neary <dneary@...> wrote:
Hi,

I had conversations last week with a number of you about this topic, and
just wanted to strike while the iron was hot to get it on the Be
planning cycle (if any work needs doing).

When someone is deciding to use ODL for OpenStack Neutron, my
expectation would be that they're not starting from scratch - in all
probability, either they are currently using nova-network or they're
using the defail OVS ML2 plug-in.

Migrating from nova-network to Neutron is already a hairy topic, but
migrating an existing cloud from OVS to ODL easily would make it easier
to adopt ODL. My understanding before last week was that you didn't have
a choice - to migrate to ODL from OVSDB required deleting and
reinitialising the ovsdb database on all of the Nova compute nodes, as
documented here:
https://wiki.opendaylight.org/view/OpenStack_and_OpenDaylight

But in conversation last week, the following procedure was suggested. My
question is, can we document and test this, and verify that it works?

Migration procesure:

0. Install and start ODL
1. Stop neutron-service (doesn't affect dataplane for existing instances)
2. On each OVS instance: stop and disable neutron-openvswitch-agent
3. Update Neutron config to use ODL mechanism
4. On each OVS instance: set-manager to ODL

It'll be important for Neutron to be connected to ODL before setting ODL
as the manager for the vswitch, as once you do a set-manager, ODL will
write flows to the switches. The contention is, since the compute
instances are still connected to OVS, the set-manager will also kick off
ovsdb events which will lead to everything converging on a consistent
state - ODL will wipe any old flows from the switches, and will rewire
instances to the appropriate network IDs, and set all the flows, vlan
tags, etc as they should be.

Will this work? I'm going to try it out when I get home (in a few days),
but I wanted to get something written down & argued about ASAP.

Thanks,
Dave.

--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Summit 2015 Slides for OVSDB Netvirt

Sam Hague
 

Hi all,

here are links to the slides that were presented at the summit:

[1] OVSDB Tutorial: Describes architecture, plans for Be and good tutorial on using ODL OVSDB NetVirt and OpenStack integration with a prebuilt vm.
[2] OVSDB Developer Forum: Details ideas for SFC integration, SNAT and Hardware VTEP YANG model

Thanks, Sam

[1] https://docs.google.com/presentation/d/1KIuNDuUJGGEV37Zk9yzx9OSnWExt4iD2Z7afycFLf_I/edit?usp=sharing
[2] https://docs.google.com/presentation/d/1EcKSl-lVOU7HBBku2KZEnaedG9lsNpAN3pd3WmYCoqo/edit?usp=sharing


Be Documentation Contact Volunteer

Sam Hague
 

Hi all,

We are looking for a volunteer(s) for the Be documentation contact. Per [1] we need to identify a documentation contact to coordinate the test tasks. Please let me know if you would like to volunteer for the role.

The main responsibilities:

- Coordinate with the documentation team
- Coordinate with Release Planning for documentation requirements
- Coordinate communication for OVSDB documentation questions and concerns

Thanks, Sam

[1] https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan


Be Test Contact

Sam Hague
 

Hi all,

We are looking for a volunteer(s) for the Be test contact. Per [1] we need to identify a test contact to coordinate the test tasks. Please let me know if you would like to volunteer for the role.

The main responsibilities:

- Coordinate with the Integration Test team
- Coordinate with Release Planning for test requirements
- Coordinate communication for OVSDB test questions and concerns

Thanks, Sam

[1] https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan


Re: [OpenDaylight Discuss] TWS - call for topics

Edward Warnicke <hagbard@...>
 

Actually... I found a bug in the archetype that is merged upstream and *won't* be able to show this today :(

Ed

On Sun, Aug 2, 2015 at 6:47 PM, Keith Burns <alagalah@...> wrote:

Done!

On Aug 2, 2015 9:22 AM, "Edward Warnicke" <hagbard@...> wrote:
I'd be happy to talk through the new IT stuff in the startup archetype :)

Ed

On Sun, Aug 2, 2015 at 8:56 AM, Jamie G. <jamie.goodyear@...> wrote:
Not sure if topic for TWS or TSC - there was some interest expressed
in developing a Monitoring & Alerting project for ODL based upon
Apache Karaf's Decanter project
https://karaf.apache.org/index/subprojects/decanter.html.

--J

On Sun, Aug 2, 2015 at 12:49 PM, alagalah <alagalah@...> wrote:
> We are sans agenda for the TWS.
>
> There were a lot of interesting topics at the Summit, so I would *think*
> there’d be a lot of follow on topics. I’ll try and add the relevant –dev
> lists to my suggestions, hoping it hits the right email filters.
>
> Suggested topics for Aug3 (doesn’t have to be polished, can bounce around
> between content, just looking to spark conversation).
>
> Overlay with LISP
>
> Overview of LISP components implemented, how they could be leveraged.
>
> OF Table Type Patterns (TTP) update
>
> where is the industry? Adoption?
>
> In-project documentation and format
>
> any readout from the session, overview from the session for those that
> missed it.
>
> Pipeline co-existance
>
> Recap of the issue
> Tentatively narrow scope to OVS?
>
> Clustering
>
> There were quite a few sessions, any concrete outcomes?
>
>
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss@...
> https://lists.opendaylight.org/mailman/listinfo/discuss
>
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss



Re: [OpenDaylight Discuss] TWS - call for topics

Keith Burns <alagalah@...>
 

Done!

On Aug 2, 2015 9:22 AM, "Edward Warnicke" <hagbard@...> wrote:

I'd be happy to talk through the new IT stuff in the startup archetype :)

Ed

On Sun, Aug 2, 2015 at 8:56 AM, Jamie G. <jamie.goodyear@...> wrote:
Not sure if topic for TWS or TSC - there was some interest expressed
in developing a Monitoring & Alerting project for ODL based upon
Apache Karaf's Decanter project
https://karaf.apache.org/index/subprojects/decanter.html.

--J

On Sun, Aug 2, 2015 at 12:49 PM, alagalah <alagalah@...> wrote:
> We are sans agenda for the TWS.
>
> There were a lot of interesting topics at the Summit, so I would *think*
> there’d be a lot of follow on topics. I’ll try and add the relevant –dev
> lists to my suggestions, hoping it hits the right email filters.
>
> Suggested topics for Aug3 (doesn’t have to be polished, can bounce around
> between content, just looking to spark conversation).
>
> Overlay with LISP
>
> Overview of LISP components implemented, how they could be leveraged.
>
> OF Table Type Patterns (TTP) update
>
> where is the industry? Adoption?
>
> In-project documentation and format
>
> any readout from the session, overview from the session for those that
> missed it.
>
> Pipeline co-existance
>
> Recap of the issue
> Tentatively narrow scope to OVS?
>
> Clustering
>
> There were quite a few sessions, any concrete outcomes?
>
>
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss@...
> https://lists.opendaylight.org/mailman/listinfo/discuss
>
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss


Re: [OpenDaylight Discuss] TWS - call for topics

Lori Jakab <lojakab@...>
 

Hi Keith,

On 8/2/15 8:19 AM, alagalah wrote:
We are sans agenda for the TWS.

There were a lot of interesting topics at the Summit, so I would
*think* there’d be a lot of follow on topics. I’ll try and add the
relevant –dev lists to my suggestions, hoping it hits the right email
filters.

Suggested topics for Aug3 (doesn’t have to be polished, can bounce
around between content, just looking to spark conversation).

* Overlay with LISP
o Overview of LISP components implemented, how they could be
leveraged.
Thanks for bringing this up. I'll be on a plane at the time of the Aug3
TWS though, so if you guys don't terribly mind, I'd love to see this
discussion (and possibly the pipeline co-existance) happen in a later TWS.

-Lori

* OF Table Type Patterns (TTP) update
o where is the industry? Adoption?
* In-project documentation and format
o any readout from the session, overview from the session for
those that missed it.
* Pipeline co-existance
o Recap of the issue
o Tentatively narrow scope to OVS?
* Clustering
o There were quite a few sessions, any concrete outcomes?






_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss


Re: [OpenDaylight Discuss] TWS - call for topics

Edward Warnicke <hagbard@...>
 

I'd be happy to talk through the new IT stuff in the startup archetype :)

Ed

On Sun, Aug 2, 2015 at 8:56 AM, Jamie G. <jamie.goodyear@...> wrote:
Not sure if topic for TWS or TSC - there was some interest expressed
in developing a Monitoring & Alerting project for ODL based upon
Apache Karaf's Decanter project
https://karaf.apache.org/index/subprojects/decanter.html.

--J

On Sun, Aug 2, 2015 at 12:49 PM, alagalah <alagalah@...> wrote:
> We are sans agenda for the TWS.
>
> There were a lot of interesting topics at the Summit, so I would *think*
> there’d be a lot of follow on topics. I’ll try and add the relevant –dev
> lists to my suggestions, hoping it hits the right email filters.
>
> Suggested topics for Aug3 (doesn’t have to be polished, can bounce around
> between content, just looking to spark conversation).
>
> Overlay with LISP
>
> Overview of LISP components implemented, how they could be leveraged.
>
> OF Table Type Patterns (TTP) update
>
> where is the industry? Adoption?
>
> In-project documentation and format
>
> any readout from the session, overview from the session for those that
> missed it.
>
> Pipeline co-existance
>
> Recap of the issue
> Tentatively narrow scope to OVS?
>
> Clustering
>
> There were quite a few sessions, any concrete outcomes?
>
>
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss@...
> https://lists.opendaylight.org/mailman/listinfo/discuss
>
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss


Re: [OpenDaylight Discuss] TWS - call for topics

Jamie G. <jamie.goodyear@...>
 

Not sure if topic for TWS or TSC - there was some interest expressed
in developing a Monitoring & Alerting project for ODL based upon
Apache Karaf's Decanter project
https://karaf.apache.org/index/subprojects/decanter.html.

--J

On Sun, Aug 2, 2015 at 12:49 PM, alagalah <alagalah@...> wrote:
We are sans agenda for the TWS.

There were a lot of interesting topics at the Summit, so I would *think*
there’d be a lot of follow on topics. I’ll try and add the relevant –dev
lists to my suggestions, hoping it hits the right email filters.

Suggested topics for Aug3 (doesn’t have to be polished, can bounce around
between content, just looking to spark conversation).

Overlay with LISP

Overview of LISP components implemented, how they could be leveraged.

OF Table Type Patterns (TTP) update

where is the industry? Adoption?

In-project documentation and format

any readout from the session, overview from the session for those that
missed it.

Pipeline co-existance

Recap of the issue
Tentatively narrow scope to OVS?

Clustering

There were quite a few sessions, any concrete outcomes?





_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss

3081 - 3100 of 4855