Fullscreen User Comments
Share on Twitter Share on Facebook Share on LInkedIn Share on GooglePlus

Loading…

Loading…

Loading…

Loading…

Loading…

Why they made NFV up as they went along and why that's a good thing

<iframe src="https://www.youtube.com/embed/7OqdH_DZo4s?modestbranding=1&rel=0" width="970" height="546" frameborder="0" scrolling="auto" allowfullscreen></iframe>

Prodip Sen, CTO Network Functions Virtualization (NFV), Hewlett Packard Enterprise

Prodip Sen looks back over the past five years of NFV development and describes a process that  participants made up as they went along - how could they do otherwise given NFV's scope and novelty? Therefore, he implies, it was impossible to say at any point how long it would take and even what the exact destination was. 

Even so, looking back now he identifies business change (rather than just technology change) as something that could and perhaps should have been given more attention earlier on. And he explains why, ideally, business and technology transformation should be viewed as joined at the hip.

Filmed at: SDN NFV World Congress 2017, The Hague, Netherlands

Join The Discussion

 
x By using this website you are consenting to the use of cookies. More information is available in our cookie policy. OK