Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

[Joe Stringer]

On 9 June 2016 at 08:50, Terry Wilson  wrote:
> On Thu, Jun 9, 2016 at 3:07 AM, Russell Bryant  wrote:
>> The real solution to making this less awkward would be to split the Python
>> library out of the OVS git tree so that it can be released independently of
>> OVS itself.  That way a proper verison could be released that includes
>> Python 3 support.
>
> This would be very nice. There are some challenges to overcome. The
> testing infrastructure between the Python and C implementations is
> shared. Out of tree it becomes more a bit more difficult to make sure
> that they stay in sync both feature and compatibility-wise. My gut
> feeling is that it would still be worth the work, though. There's no
> good reason for releases of the Python library to be tied OVS
> releases.

Setting aside the python3 compatibility issues, the typical number of
commits to this library between releases is pretty small (<10). They
seem to be largely independent of other changes in the OVS tree, but
occasionally they are coupled to other changes.

Is the proposal really fixing an ongoing issue or just a one-off? It
seems like a lot of effort unless the pace of development on this
library significantly increases and users really need a more frequent
release cycle (for example, because they're releasing versions of
their software more regularly than the OVS and need the latest and
greatest python-ovs).

Bug#826780: [ovs-dev] Bug#826780: Please package OVS >= 2.6.0.dev1

[Joe Stringer]

On 8 June 2016 at 16:40, Ben Pfaff  wrote:
> On Thu, Jun 09, 2016 at 01:23:12AM +0200, Thomas Goirand wrote:
>> Source: openvswitch
>> Version: 2.3.0+git20140819-4
>> Severity: normal
>>
>> Hi,
>>
>> OpenStack Neutron currently has:
>>
>> ovs>=2.5.0;python_version=='2.7' # Apache-2.0
>> ovs>=2.6.0.dev1;python_version>='3.4' # Apache-2.0
>>
>> in its requirements.txt. Please package this at least to Debian Experimental,
>> so that I can package Neutron Newton Beta 1.
>
> I can package 2.5.x, though there are reports that there's one testsuite
> failure on big-endian architectures.
>
> OVS 2.6.0 doesn't exist yet, so it can't be packaged.  When Neutron asks
> for 2.6.0 what does it mean?

It would appear that someone has uploaded an OVS 2.5.90 development
version of the OVS python libraries to pypi as 2.6.0.dev1:
https://pypi.python.org/pypi/ovs/2.6.0.dev1

This probably has the latest python3 fixes that were applied since OVS
2.5, so is required if someone wants to run neutron under python3.

Russell, do you know much about this? I'd CC otherwiseguy, but I don't
know who that is off-hand.

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

[Joe Stringer]

On 23 December 2014 at 03:12, Fabio Fantoni fabio.fant...@m2r.biz wrote:
 For have it working I had to do service networking restart.
 I found probably final solution applying also this patch:
 http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
 Even if seems not good in some cases.
 I don't know if also Jessie have this problem but probably yes. If yes I
 think this bug is only partially solves with 2.3.0+git20140819-3.

FYI, the above URL points to an outdated git and may go away; OVS has
migrated to GitHub:
https://github.com/openvswitch/ovs/commit/9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af

If you accessed the above URL via the OVS website somehow, please get
in touch with me off-list so we can fix the links to point to the
correct location.


 I had also another start problem probably not related to this, after some
 hours xenbr0 stopped to working.
 I not found any useful errors about in logs, only some strange thing, in
 ifconfig xenbr0 was without the static ip, in syslog keep tried to acquire
 configuration with dhcp failing (dhcp server present and working in lan).
 After service networking restart was working again but I not understand
 was happen and why :(
 Someone have any idea about?

I see that Guru has suggested a possible fix; if that does not address
your issue, you could send your question to disc...@openvswitch.org or
open a fresh debian bug (or both!). It would be helpful to provide
related logs (ovs-vswitchd.log and/or syslog), OVS versions and OVS
configuration.

Thanks,
Joe


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly

[Joe Stringer]

On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
 One maintainer or debian developer can do a new build of ovs with the fix
 available in 2.3.1 please?

   * Version 2.3.0+git20140819-2 of openvswitch is marked for
 autoremoval from testing on 2015-01-15.
   * It is affected by RC bug #771863 https://bugs.debian.org/771863.


 Without this fix openvswitch will be removed from Jessie and I think this
 would be a bad thing.

 Thanks for any reply and sorry for my bad english.

Ben usually takes care of this sort of thing, but he is out on holiday
through to Christmas.

Simon, would you be able to take care of this?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771863: [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly, updating severity

[Joe Stringer]

On 15 December 2014 at 10:21, Gurucharan Shetty shet...@nicira.com wrote:
 On Sat, Dec 13, 2014 at 2:03 AM, Stig Sandbeck Mathisen s...@debian.org 
 wrote:
 I would like to clarify that 2.3.1 does get rid of the check on
 $RUNLEVEL which was the original bug description.

 That's great, thanks. :)

 I probably should treat this as a separate bug. Would you like me to
 file a new bug for it in the Debian BTS, in addition to submitting an
 upstream patch?

snip

I agree that this should be treated as a separate bug, yes please (I'm
just following up as it wasn't clear to me whether you're working on
this or not).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org