Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Thadeu Lima de Souza Cascardo]

On Tue, Jul 26, 2016 at 02:24:19PM -0700, Jesse Gross wrote:
> On Sun, Jul 24, 2016 at 10:53 AM, Ben Pfaff  wrote:
> > On Sun, Jul 24, 2016 at 08:39:31AM -0300, Thadeu Lima de Souza Cascardo 
> > wrote:
> >> On Sat, Jul 23, 2016 at 08:59:35AM -0700, Ben Pfaff wrote:
> >> > The proposed Open vSwitch release schedule calls for branching 2.6 from
> >> > master on Aug. 1, followed by a period of bug fixes and stabilization,
> >> > with release on Sep. 15.  The proposed release schedule is posted here
> >> > for review:
> >> > https://patchwork.ozlabs.org/patch/650319/
> >> >
> >> > I don't yet know of a reason to modify this schedule.
> >> >
> >> > If you know of reasons to change it, now is an appropriate time to bring
> >> > it up for discussion.  In addition, if you have features planned for 2.6
> >> > that risk hitting master somewhat late for the branch, it is also a good
> >> > time to bring these up for discussion, so that we can plan to backport
> >> > them to the branch early on, or to delay the branch by a few days.
> >>
> >> I would like to see the rtnetlink patchset included. One of things
> >> that needs to happen before that is taking those decisions about
> >> netdev_open and the existence of conflicting port types with the same
> >> name. For example, a system interface and an interface in the database
> >> with the same name but a different type.
> >>
> >> I will post some comments on the discussion we already have opened for
> >> that.
> >>
> >> Just wanted to take the opportunity to mention this expectation of
> >> getting those into 2.6.
> >
> > For that feature, I need to defer to Jesse (added to the thread).
> 
> I think since there isn't yet a patch for this yet that is about ready
> to be applied, we'll need to make a call at the time the code is
> applied to master. If it's one day after we branch, sure that's fine;
> one day before release, obviously not; anything in the middle we'll
> need to decide.
> 
> However, based on the code that has been sent out previously, I think
> this is mostly infrastructure at this point rather than user-visible
> changes. It would allow other features to be built on top of it but
> that would be a follow on change. If that's the case, is there any
> particular reason to try to get this in 2.6?

Hi, Jesse.

Considering that it's very unlikely that other follow-up patches would go in, I
agree that this could wait.

Thanks for considering.

Cascardo.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Jesse Gross]

On Sun, Jul 24, 2016 at 10:53 AM, Ben Pfaff  wrote:
> On Sun, Jul 24, 2016 at 08:39:31AM -0300, Thadeu Lima de Souza Cascardo wrote:
>> On Sat, Jul 23, 2016 at 08:59:35AM -0700, Ben Pfaff wrote:
>> > The proposed Open vSwitch release schedule calls for branching 2.6 from
>> > master on Aug. 1, followed by a period of bug fixes and stabilization,
>> > with release on Sep. 15.  The proposed release schedule is posted here
>> > for review:
>> > https://patchwork.ozlabs.org/patch/650319/
>> >
>> > I don't yet know of a reason to modify this schedule.
>> >
>> > If you know of reasons to change it, now is an appropriate time to bring
>> > it up for discussion.  In addition, if you have features planned for 2.6
>> > that risk hitting master somewhat late for the branch, it is also a good
>> > time to bring these up for discussion, so that we can plan to backport
>> > them to the branch early on, or to delay the branch by a few days.
>>
>> I would like to see the rtnetlink patchset included. One of things
>> that needs to happen before that is taking those decisions about
>> netdev_open and the existence of conflicting port types with the same
>> name. For example, a system interface and an interface in the database
>> with the same name but a different type.
>>
>> I will post some comments on the discussion we already have opened for
>> that.
>>
>> Just wanted to take the opportunity to mention this expectation of
>> getting those into 2.6.
>
> For that feature, I need to defer to Jesse (added to the thread).

I think since there isn't yet a patch for this yet that is about ready
to be applied, we'll need to make a call at the time the code is
applied to master. If it's one day after we branch, sure that's fine;
one day before release, obviously not; anything in the middle we'll
need to decide.

However, based on the code that has been sent out previously, I think
this is mostly infrastructure at this point rather than user-visible
changes. It would allow other features to be built on top of it but
that would be a follow on change. If that's the case, is there any
particular reason to try to get this in 2.6?
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Gray, Mark D]

> -Original Message-
> From: Daniele Di Proietto [mailto:diproiet...@vmware.com]
> Sent: Monday, July 25, 2016 6:07 PM
> To: Ben Pfaff <b...@ovn.org>; Gray, Mark D <mark.d.g...@intel.com>;
> Pravin Shelar <pshe...@vmware.com>
> Cc: dev@openvswitch.org
> Subject: Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
> 
> 
> 
> 
> 
> 
> On 25/07/2016 09:16, "Ben Pfaff" <b...@ovn.org> wrote:
> 
> >On Mon, Jul 25, 2016 at 03:44:01PM +, Gray, Mark D wrote:
> >>
> >>
> >> > -Original Message-
> >> > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben
> >> > Pfaff
> >> > Sent: Saturday, July 23, 2016 5:00 PM
> >> > To: dev@openvswitch.org
> >> > Subject: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
> >> >
> >> > The proposed Open vSwitch release schedule calls for branching 2.6
> >> > from master on Aug. 1, followed by a period of bug fixes and
> >> > stabilization, with release on Sep. 15.  The proposed release
> >> > schedule is posted here for
> >> > review:
> >> > https://patchwork.ozlabs.org/patch/650319/
> >> >
> >> > I don't yet know of a reason to modify this schedule.
> >> >
> >> > If you know of reasons to change it, now is an appropriate time to
> >> > bring it up for discussion.  In addition, if you have features
> >> > planned for 2.6 that risk hitting master somewhat late for the
> >> > branch, it is also a good time to bring these up for discussion, so
> >> > that we can plan to backport them to the branch early on, or to delay
> the branch by a few days.
> >>
> >> DPDK 16.07 should be released by early next week. Ciara has a patch
> >> to enable it, could this be backported to the branch?
> >
> >I think that Daniele and Pravin should weigh in on that since they
> >understand DPDK and its relationship to OVS much better.
> 
> I think we should use DPDK 16.07 for branch-2.6.  I hope to merge the patch
> before we branch, otherwise we can always backport it.

Thanks Daniele

> 
> Thanks,
> 
> Daniele
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Daniele Di Proietto]

On 25/07/2016 09:16, "Ben Pfaff"  wrote:

>On Mon, Jul 25, 2016 at 03:44:01PM +, Gray, Mark D wrote:
>> 
>> 
>> > -Original Message-
>> > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff
>> > Sent: Saturday, July 23, 2016 5:00 PM
>> > To: dev@openvswitch.org
>> > Subject: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
>> > 
>> > The proposed Open vSwitch release schedule calls for branching 2.6 from
>> > master on Aug. 1, followed by a period of bug fixes and stabilization, with
>> > release on Sep. 15.  The proposed release schedule is posted here for
>> > review:
>> > https://patchwork.ozlabs.org/patch/650319/
>> > 
>> > I don't yet know of a reason to modify this schedule.
>> > 
>> > If you know of reasons to change it, now is an appropriate time to bring 
>> > it up
>> > for discussion.  In addition, if you have features planned for 2.6 that 
>> > risk
>> > hitting master somewhat late for the branch, it is also a good time to 
>> > bring
>> > these up for discussion, so that we can plan to backport them to the branch
>> > early on, or to delay the branch by a few days.
>> 
>> DPDK 16.07 should be released by early next week. Ciara has a patch to
>> enable it, could this be backported to the branch?
>
>I think that Daniele and Pravin should weigh in on that since they
>understand DPDK and its relationship to OVS much better.

I think we should use DPDK 16.07 for branch-2.6.  I hope to merge the patch
before we branch, otherwise we can always backport it.

Thanks,

Daniele
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Ben Pfaff]

On Mon, Jul 25, 2016 at 03:44:01PM +, Gray, Mark D wrote:
> 
> 
> > -Original Message-
> > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff
> > Sent: Saturday, July 23, 2016 5:00 PM
> > To: dev@openvswitch.org
> > Subject: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
> > 
> > The proposed Open vSwitch release schedule calls for branching 2.6 from
> > master on Aug. 1, followed by a period of bug fixes and stabilization, with
> > release on Sep. 15.  The proposed release schedule is posted here for
> > review:
> > https://patchwork.ozlabs.org/patch/650319/
> > 
> > I don't yet know of a reason to modify this schedule.
> > 
> > If you know of reasons to change it, now is an appropriate time to bring it 
> > up
> > for discussion.  In addition, if you have features planned for 2.6 that risk
> > hitting master somewhat late for the branch, it is also a good time to bring
> > these up for discussion, so that we can plan to backport them to the branch
> > early on, or to delay the branch by a few days.
> 
> DPDK 16.07 should be released by early next week. Ciara has a patch to
> enable it, could this be backported to the branch?

I think that Daniele and Pravin should weigh in on that since they
understand DPDK and its relationship to OVS much better.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Gray, Mark D]

> -Original Message-
> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff
> Sent: Saturday, July 23, 2016 5:00 PM
> To: dev@openvswitch.org
> Subject: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
> 
> The proposed Open vSwitch release schedule calls for branching 2.6 from
> master on Aug. 1, followed by a period of bug fixes and stabilization, with
> release on Sep. 15.  The proposed release schedule is posted here for
> review:
> https://patchwork.ozlabs.org/patch/650319/
> 
> I don't yet know of a reason to modify this schedule.
> 
> If you know of reasons to change it, now is an appropriate time to bring it up
> for discussion.  In addition, if you have features planned for 2.6 that risk
> hitting master somewhat late for the branch, it is also a good time to bring
> these up for discussion, so that we can plan to backport them to the branch
> early on, or to delay the branch by a few days.
> 

Hi Ben, 

DPDK 16.07 should be released by early next week. Ciara has a patch to enable 
it,
could this be backported to the branch?

Thanks,
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Ben Pfaff]

On Sun, Jul 24, 2016 at 08:39:31AM -0300, Thadeu Lima de Souza Cascardo wrote:
> On Sat, Jul 23, 2016 at 08:59:35AM -0700, Ben Pfaff wrote:
> > The proposed Open vSwitch release schedule calls for branching 2.6 from
> > master on Aug. 1, followed by a period of bug fixes and stabilization,
> > with release on Sep. 15.  The proposed release schedule is posted here
> > for review:
> > https://patchwork.ozlabs.org/patch/650319/
> > 
> > I don't yet know of a reason to modify this schedule.
> > 
> > If you know of reasons to change it, now is an appropriate time to bring
> > it up for discussion.  In addition, if you have features planned for 2.6
> > that risk hitting master somewhat late for the branch, it is also a good
> > time to bring these up for discussion, so that we can plan to backport
> > them to the branch early on, or to delay the branch by a few days.
>
> I would like to see the rtnetlink patchset included. One of things
> that needs to happen before that is taking those decisions about
> netdev_open and the existence of conflicting port types with the same
> name. For example, a system interface and an interface in the database
> with the same name but a different type.
> 
> I will post some comments on the discussion we already have opened for
> that.
> 
> Just wanted to take the opportunity to mention this expectation of
> getting those into 2.6.

For that feature, I need to defer to Jesse (added to the thread).
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Thadeu Lima de Souza Cascardo]

On Sat, Jul 23, 2016 at 08:59:35AM -0700, Ben Pfaff wrote:
> The proposed Open vSwitch release schedule calls for branching 2.6 from
> master on Aug. 1, followed by a period of bug fixes and stabilization,
> with release on Sep. 15.  The proposed release schedule is posted here
> for review:
> https://patchwork.ozlabs.org/patch/650319/
> 
> I don't yet know of a reason to modify this schedule.
> 
> If you know of reasons to change it, now is an appropriate time to bring
> it up for discussion.  In addition, if you have features planned for 2.6
> that risk hitting master somewhat late for the branch, it is also a good
> time to bring these up for discussion, so that we can plan to backport
> them to the branch early on, or to delay the branch by a few days.
> 
> Thanks,
> 
> Ben.
> ___
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev

I would like to see the rtnetlink patchset included. One of things that needs to
happen before that is taking those decisions about netdev_open and the existence
of conflicting port types with the same name. For example, a system interface
and an interface in the database with the same name but a different type.

I will post some comments on the discussion we already have opened for that.

Just wanted to take the opportunity to mention this expectation of getting those
into 2.6.

Thanks.
Cascardo.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Ryan Moats]

Ben Pfaff <b...@ovn.org> wrote on 07/23/2016 11:45:18 AM:

> From: Ben Pfaff <b...@ovn.org>
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: dev@openvswitch.org
> Date: 07/23/2016 11:45 AM
> Subject: Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15
>
> On Sat, Jul 23, 2016 at 11:31:54AM -0500, Ryan Moats wrote:
> >
> >
> > "dev" <dev-boun...@openvswitch.org> wrote on 07/23/2016 10:59:35 AM:
> > > The proposed Open vSwitch release schedule calls for branching 2.6
from
> > > master on Aug. 1, followed by a period of bug fixes and
stabilization,
> > > with release on Sep. 15.  The proposed release schedule is posted
here
> > > for review:
> > > https://patchwork.ozlabs.org/patch/650319/
> > >
> > > I don't yet know of a reason to modify this schedule.
> > >
> > > If you know of reasons to change it, now is an appropriate time to
bring
> > > it up for discussion.  In addition, if you have features planned for
2.6
> > > that risk hitting master somewhat late for the branch, it is also a
good
> > > time to bring these up for discussion, so that we can plan to
backport
> > > them to the branch early on, or to delay the branch by a few days.
> >
> > Apologies for the potential double notice on this, but email to the
> > list is being difficult again, so I'm not going to risk it:
> >
> > I just submitted http://patchwork.ozlabs.org/patch/651978/ to produce
> > an ovn-controller-vtep debian package. Our architecture plans call for
> > being able to assign TOR communication to specific nodes, so we'd like
> > to see this or its equivalent to land as part of the 2.6.0 feature set.
> > If it merges before the branch, great - if not, consider this an ask
> > for inclusion before the final release.
>
> I don't think that's a problem.  It's submitted well before the branch
> point and unless there's something surprising about it (I haven't looked
> yet) it should be low risk.  Really this is about patches or (more
> likely) series that might be a tough call in terms of size, risk, or
> timing.  But I'm glad that you're bringing it up because to date we
> haven't done a good job of making the process transparent and we need to
> properly set norms.

Glad to help...
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] releasing 2.6: branch Aug 1, release Sep 15

[Ben Pfaff]

On Sat, Jul 23, 2016 at 11:31:54AM -0500, Ryan Moats wrote:
> 
> 
> "dev"  wrote on 07/23/2016 10:59:35 AM:
> > The proposed Open vSwitch release schedule calls for branching 2.6 from
> > master on Aug. 1, followed by a period of bug fixes and stabilization,
> > with release on Sep. 15.  The proposed release schedule is posted here
> > for review:
> > https://patchwork.ozlabs.org/patch/650319/
> >
> > I don't yet know of a reason to modify this schedule.
> >
> > If you know of reasons to change it, now is an appropriate time to bring
> > it up for discussion.  In addition, if you have features planned for 2.6
> > that risk hitting master somewhat late for the branch, it is also a good
> > time to bring these up for discussion, so that we can plan to backport
> > them to the branch early on, or to delay the branch by a few days.
> 
> Apologies for the potential double notice on this, but email to the
> list is being difficult again, so I'm not going to risk it:
> 
> I just submitted http://patchwork.ozlabs.org/patch/651978/ to produce
> an ovn-controller-vtep debian package. Our architecture plans call for
> being able to assign TOR communication to specific nodes, so we'd like
> to see this or its equivalent to land as part of the 2.6.0 feature set.
> If it merges before the branch, great - if not, consider this an ask
> for inclusion before the final release.

I don't think that's a problem.  It's submitted well before the branch
point and unless there's something surprising about it (I haven't looked
yet) it should be low risk.  Really this is about patches or (more
likely) series that might be a tough call in terms of size, risk, or
timing.  But I'm glad that you're bringing it up because to date we
haven't done a good job of making the process transparent and we need to
properly set norms.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev