Hi Ben and other OVS maintainers,
As I have asked on this listed before, our comany is planning to
open source our OpenFlow hardware switch
implementation based on OVS, and we hope that our implementation can
be contributed to OVS, and serves
as a reference to other vendors, and wish this can enrich the
ecosystem of OpenFlow.
Our implementation can be divided to 3 parts mainly, and I will list
the 3 parts here and describe how we sug-
gest to contribute, we are sincerely want to hear the voice from the
maintainers and the list.
Part 1: an ofproto/netdev provider
The two provider is developed by our engineer according to the OVS
porting guide, we hope to open source
this part. This part depends on our adpater layer and some
libraries, it can't be compiled directly, we never
want to break any parts of OVS, so we suggest that this part can be
merged to some folder named 'contrib' in
OVS as other open source software does.
Part 2: an adapter layer
This part is used as a hardware abstraction layer to support our
ofproto/netdev provider, and is based on
top of our ASIC SDK, we'd like to open source this layer too, and
suggest that it may be merged to the same
directory with our provider.
Part 3: ASIC SDK
The ASIC sdk is bound to our ASIC chipsets that support OpenFlow,
because this SDK is not solely written
for OpenFlow(though our colleagues are trying to tweak it to an
OpenFlow version), it's quite large and may
need more communication with our management team to cover the
copyright issues, so we do not have clear
view on how to open source and contribute it to OVS, we'd like to
listen to the advice from the community to
make further decision.
We are keen to hear the voice from you and other OVS maintainers and
do further work to make this thing
happens.
Thanks a lot.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
