|
Edward Warnicke
Sam,
Question... in the scope... what constitutes 'network virtualization' in your mind? (trying to wrap my head around the scope :) ).
Ed
On Thu, Mar 24, 2016 at 8:45 AM, Sam Hague <shague@...> wrote: Hello,
we would like to submit the follow proposal [1] to split NetVirt from OVSDB. All committers have +1'd the proposal. Since the split of NetVirt from the OVSDB project has already been
discussed and recommended by the TSC, and was a qualification on the
recent scope revision approval [0], we request that the 2-week waiting
period be waived and this proposal be voted on as soon as the TSC
schedule allows. This would allow the project to minimize disruptions while transitioning to the new project. Thanks, Sam
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
|
|
|
Andre Fredette <afredette@...>
Hello Ed, The following looks like a reasonable definition: https://www.sdxcentral.com/resources/network-virtualization/whats-network-virtualization/For example, the NetVirt component of the existing OVSDB NetVirt project is a network virtualization solution for OpenStack. This will form the basis of the new project. We intend to define the scope in such a way that we can continue to extend our support for Openstack, but that we can do it in such a way that it is useful for other applications as well. Andre
|
|
|
It may well be that I am dense.
I have looked at the definition you pointed to.
I have looked at the project proposal page.
I cannot tell what the netvirt project would actually do. I can’t even guess what would be in or out of scope.
Yours,
Joel
From: project-proposals-bounces@... [mailto:project-proposals-bounces@...]
On Behalf Of Andre Fredette
Sent: Friday, April 01, 2016 7:52 AM
To: Edward Warnicke
Cc: project-proposals@...; <ovsdb-dev@...>
Subject: Re: [Project-proposals] [ovsdb-dev] Ovsdb Netvirt Project Split Proposal
Hello Ed,
The following looks like a reasonable definition:
https://www.sdxcentral.com/resources/network-virtualization/whats-network-virtualization/
For example, the NetVirt component of the existing OVSDB NetVirt project is a network virtualization solution for OpenStack. This will form the basis of the new project. We intend to define the scope in such a way that we can continue to extend our support
for Openstack, but that we can do it in such a way that it is useful for other applications as well.
Andre
toggle quoted messageShow quoted text
On Thu, Mar 31, 2016 at 12:07 PM, Edward Warnicke < hagbard@...> wrote:
Sam,
Question... in the scope... what constitutes 'network virtualization' in your mind? (trying to wrap my head around the scope :) ).
On Thu, Mar 24, 2016 at 8:45 AM, Sam Hague <shague@...> wrote:
we would like to submit the follow proposal [1] to split NetVirt from OVSDB. All committers have +1'd the proposal.
Since the split of NetVirt from the OVSDB project has already been discussed and recommended by the TSC, and was a qualification on the recent scope revision approval [0], we request that the 2-week waiting period be waived and this proposal be voted on as
soon as the TSC schedule allows. This would allow the project to minimize disruptions while transitioning to the new project.
Thanks, Sam
_______________________________________________
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
|
|
|
Andre Fredette <afredette@...>
Joel,
Based on my experience with you, I am sure you are not dense. This proposal is a spin out of the existing NetVirt functionality from the existing OVSDB Project. As such, we did not believe that an extensive description of the functionality was required. Also, the scope in this proposal is similar in language to the scope for the NetVirt parts in the existing approved OVSDB NetVirt Project Proposal [1]. [1] https://wiki.opendaylight.org/view/Project_Proposals:OVSDB_NetVirtThis proposal is scheduled to be reviewed by the TSC next week. We appreciate the early comments/questions to the list rather than waiting until the review. If the current scope will not be acceptable to the TSC, it would be good to hear that earlier rather than later.
Thanks,
On Fri, Apr 1, 2016 at 11:08 AM, Joel Halpern <joel.halpern@...> wrote:
It may well be that I am dense.
I have looked at the definition you pointed to.
I have looked at the project proposal page.
I cannot tell what the netvirt project would actually do. I can’t even guess what would be in or out of scope.
Yours,
Joel
From: project-proposals-bounces@... [mailto:project-proposals-bounces@...]
On Behalf Of Andre Fredette
Sent: Friday, April 01, 2016 7:52 AM
To: Edward Warnicke
Cc: project-proposals@...; <ovsdb-dev@...>
Subject: Re: [Project-proposals] [ovsdb-dev] Ovsdb Netvirt Project Split Proposal
Hello Ed,
The following looks like a reasonable definition:
https://www.sdxcentral.com/resources/network-virtualization/whats-network-virtualization/
For example, the NetVirt component of the existing OVSDB NetVirt project is a network virtualization solution for OpenStack. This will form the basis of the new project. We intend to define the scope in such a way that we can continue to extend our support
for Openstack, but that we can do it in such a way that it is useful for other applications as well.
Andre
On Thu, Mar 31, 2016 at 12:07 PM, Edward Warnicke <hagbard@...> wrote:
Sam,
Question... in the scope... what constitutes 'network virtualization' in your mind? (trying to wrap my head around the scope :) ).
On Thu, Mar 24, 2016 at 8:45 AM, Sam Hague <shague@...> wrote:
we would like to submit the follow proposal [1] to split NetVirt from OVSDB. All committers have +1'd the proposal.
Since the split of NetVirt from the OVSDB project has already been discussed and recommended by the TSC, and was a qualification on the recent scope revision approval [0], we request that the 2-week waiting period be waived and this proposal be voted on as
soon as the TSC schedule allows. This would allow the project to minimize disruptions while transitioning to the new project.
Thanks, Sam
_______________________________________________
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
|
|
|
Without treading too far into waters that we should discuss on the TSC call this week, the project mentions Neutron (although admittedly not in the scope), as an example of a northbound API for network virtualization, so that at the very least provides a pretty reasonable set of things that would be in-scope including creating virtual networks, subnets, tracking virtual nicks in those, floating IPs and the like.
There's a (potentially valid) discussion about whether we want to become more strict about how we describe scopes, but that seems like it should be orthogonal to this creation review.
Cheers,
--Colin
On Fri, Apr 1, 2016 at 5:44 PM, Andre Fredette <afredette@...> wrote: Joel,
Based on my experience with you, I am sure you are not dense. This proposal is a spin out of the existing NetVirt functionality from the existing OVSDB Project. As such, we did not believe that an extensive description of the functionality was required. Also, the scope in this proposal is similar in language to the scope for the NetVirt parts in the existing approved OVSDB NetVirt Project Proposal [1]. [1] https://wiki.opendaylight.org/view/Project_Proposals:OVSDB_NetVirtThis proposal is scheduled to be reviewed by the TSC next week. We appreciate the early comments/questions to the list rather than waiting until the review. If the current scope will not be acceptable to the TSC, it would be good to hear that earlier rather than later.
Thanks,
_______________________________________________
project-proposals mailing list
project-proposals@...
https://lists.opendaylight.org/mailman/listinfo/project-proposals
|
|
|
