Open Sourcing Thrones
What if a reader changed Daenerys Targaryen’s wedding gift to chicken eggs?
I recently finished all 804 pages of the first book in the Games of Thrones series. The story was tightly written, as I followed the Starks, Lannisters and Targaryens set the stage for the rest of the series. But what if George R. R. Martin had published his book online, as an open source project? And what if someone had gone into Daenerys Targaryen’s wedding scene, and replaced the dragon eggs she received as a gift with chicken eggs? The Mother of Dragons would be much less frightening to her enemies if she walked around with three chickens instead of flying on the back of her fire-breathing dragons. The entire story would need to be rewritten. Which basically brings us to AT&T’s recently announced ECOMP.
Imagine a platform with millions of lines of code. The platform is open source; anyone can make changes to it. However, there needs to be a structure, and those changes need to be tracked, cataloged and communicated to others in the open-source ecosystem. The changes also need to be verified, to ensure that they don’t damage other sections of code. And without an integrator looking things over, those millions of lines of code risk corruption. Dan Bleming, Director of Ethernet Product Management, AT&T Mobile & Business Solutions mentioned in a conversation with Telecom TV’s Guy Daniels, "A key to success in large open source project like this is having an integrator."
ECOMP is bringing the industry closer to a fully virtualized network. But, as Bleming continued, "some companies don’t have the technical depth in order to make a transition like this, so being able for them to go to Amdocs and say can you help me with this is important. We want the entire industry to make this change with us."
This past March we saw live NFV demos at Mobile World Congress, and there is no shortage of use cases demonstrating the value that industry-wide virtualization will bring to the industry. And so, we’re proud of the role we are going to play in protecting the integrity of the ECOMP system. Because when we think about, we never want to see a black-haired Lannister, and we definitely don’t want to see corrupted virtualized systems.