& cplSiteName &
Threaded  |  Newest First  |  Oldest First        ADD A COMMENT
[email protected],
User Rank: Blogger
4/4/2019 | 4:48:12 PM
Update on investors in Nefeli Networks
The article has been updated to note that NEA is the lead investor in Nefeli, with Danhua Capital (DHVC) and The House Fund also contributing to its $9.2 million round. 
User Rank: Light Sabre
4/4/2019 | 5:34:43 PM
Why would it work this time?
If lean NFV is trying to solve a problem that NFV introduced, than perhaps no NFV is even better? It seems to me that NFV with less specifications will only increase integration complexity because it leaves more open to interpretation and variation. Few CSPs have the IT resources to build, integrate and operate VNFs at any scale, in any architecture. The CSPs that do will customize it to the point it's unusable by anybody else (if they would share their code, which they won't). Besides, even if there wasn't an integration cost, many NFs simply perform better and at a lower cost on a network appliance than on an x86 server.
User Rank: Blogger
4/5/2019 | 7:38:20 AM
Lean and mean
"The Lean NFV approach relies on two technically straightforward design decisions: using an open-source KV store for coordination within NFV solutions (management components and VNFs), and using a plug-in approach to integration with the existing infrastructure."

The key value store (also known as a hash table I think) could be a good solution to the problem of API integration between different vendors. But to ensure compatibility, as the paper says, vendors need to "agree on key semantics, or use separate keyspaces". How do we get vendors to agree on these key semantics or agree a common schema / keyspace?

The plug-in approach is about making the VIM (e.g. OpenStack, VMWare's vSphere) as simple as possible and keeping all the clever stuff (auto-scaling, etc.) in the NFV Manager (a combination of the NFVO and VNFM in the ETSI architecture). Given that OpenStack is a mature open source project and the NFVM field is fairly fragmented (with some operators struggling to get their hands around less mature open source projects like ONAP) I would have thought it made more sense to exploit the full potential of OpenStack rather than rely more heavily on the orchestration layer. It also seems an odd thing for a VIM vendor like VMWare to support.
Featured Video
Flash Poll
Upcoming Live Events
September 17-19, 2019, Dallas, Texas
October 1-2, 2019, New Orleans, Louisiana
October 10, 2019, New York, New York
October 22, 2019, Los Angeles, CA
November 5, 2019, London, England
November 7, 2019, London, UK
December 3, 2019, New York, New York
December 3-5, 2019, Vienna, Austria
March 16-18, 2020, Embassy Suites, Denver, Colorado
May 18-20, 2020, Irving Convention Center, Dallas, TX
All Upcoming Live Events