Operators pick their own MANO

We have suddenly too many opensource versions of the MANO “standard” : OSM (openMANO) , Open-O, etc. which includes cloudify, rift.io, juju, tacker, etc. At least these projects are promoted by actual telco customers. Let’s see if they become a defacto standard, before the actual ETSI documents are finished.

Axians UK Blog

There’s an old saying in IT that any standard is good enough as long as it is a standard, which loosely translates as ‘we don’t care what it is, only that everybody sticks to it’.

So the European Telecommunications Standards Institute (ETSI) must be at least a little nervous that certain carriers are busy building their own open source versions of the management and orchestration (MANO) tools they need to effectively provision and deliver virtualised cloud services to their enterprise customers – one of the key functions that the ETSI network function virtualisation industry specifications group (NFV ISG) was originally set up in 2013 to co-ordinate.

The in-house MANO tools we know about so far come from Open O from China Mobile (Open O), Tata Communications (TCS Telco Cloud), NTT (Gohan) and Telefónica (OpenMANO). But there could be many more from different carriers, service providers and operators lurking just beneath…

View original post 244 more words


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s