wiki:tc_minutes_20151203
Differences
This shows you the differences between two versions of the page.
|
wiki:tc_minutes_20151203 [2015/12/04 03:05] Bin Hu created |
wiki:tc_minutes_20151203 [2015/12/04 03:19] (current) Bin Hu |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| Regarding ovn4nfv and ovsnfv, Vikram indicated that ovsnfv focuses on enhancement of the OPNFV build by including a deployment option for the software-accelerated userspace Open vSwitch build. This work will significantly improve the performance of the NFVI for network I/O. Thus Vikram concluded that ovsnfv is orthogonal to ovn4nfv project's goal, which is to enable Open Virtual Networks (OVN) as another option for network control in OPNFV. ovn4nfv could leverage the work done by ovsnfv by using accelerated data path. | Regarding ovn4nfv and ovsnfv, Vikram indicated that ovsnfv focuses on enhancement of the OPNFV build by including a deployment option for the software-accelerated userspace Open vSwitch build. This work will significantly improve the performance of the NFVI for network I/O. Thus Vikram concluded that ovsnfv is orthogonal to ovn4nfv project's goal, which is to enable Open Virtual Networks (OVN) as another option for network control in OPNFV. ovn4nfv could leverage the work done by ovsnfv by using accelerated data path. | ||
| - | Mark (Intel) indicated that there is still a little bit overlap, because they will work on the same repo and code base. How do you plan to address this overlap? Vikram responded that there are code in ovn4nfv project for contribution to upstream. Bryan indicated that as long as there is fork, it should be fine. The goal is to have a single OPNFV. | + | Mark (Intel) indicated that there is still a little bit overlap, because they will work on the same repo and code base. How do you plan to address this overlap? Vikram responded that there are code in ovn4nfv project for contribution to upstream. Bryan indicated that as long as there is no fork, it should be fine. The goal is to have a single OPNFV. |
| Bin asked Mark if he can share his experience and methodology used in ovsnfv project to avoid fork, even no temporary repo and fork. Mark shared that they discussed several options during OPNFV summit. And the final conclusion is to work on upstream repo and code base, i.e. dependent on upstream community, even if there may be inevitable delays. This will reduce the complexity of managing forks. So there will be only one OPNFV build by referring the appropriate label in upstream, and recognizing that the desired feature may not be in that upstream label, and some delays are expected. | Bin asked Mark if he can share his experience and methodology used in ovsnfv project to avoid fork, even no temporary repo and fork. Mark shared that they discussed several options during OPNFV summit. And the final conclusion is to work on upstream repo and code base, i.e. dependent on upstream community, even if there may be inevitable delays. This will reduce the complexity of managing forks. So there will be only one OPNFV build by referring the appropriate label in upstream, and recognizing that the desired feature may not be in that upstream label, and some delays are expected. | ||
wiki/tc_minutes_20151203.1449198306.txt.gz ยท Last modified: 2015/12/04 03:05 by Bin Hu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
