“The king is dead, long live the king!”
Management and Orchestration (MANO) is one of the key components of ETSI’s NFV specifications. Some believe it and other cloud management approaches will spell the death of OSS as we know it (although NFV topology diagrams show the NFV Orchestrator connecting to higher-order B/OSS).
After all, it will likely revolutionise the management and orchestration of “cloud” resources of such as compute, networking, storage and security as well as the virtual machines (VMs) upon which they reside.
But I can’t help but thinking that a lot of OSS DNA will still propagate into the management frameworks of the future. For example, if we go back to FCAPS – we’ll still need to monitor and manage faults, performance, inventory, security, etc and in each case we may wish to aggregate that management from multiple different platforms, especially if we still have legacy networks / tools in our estate.
Then looking further northbound, we may have service catalogues implemented for virtualised environments, but they’ll still need processes / workflows that are adapted for each customer’s way of doing business (eg approvals, hand-offs, decision points, business unit responsibilities, equipment life-cycle management, etc).
And each service change will hopefully have a higher level of automation than current management systems, but to fulfil a service there will still be some work orders / activities that can’t be automated. These include activities such as building customer lead-in cables, network / capacity upgrades, gaining permits to work, cross domain interconnect, cross jurisdiction interconnect and more.
The pundits may be right and we may no longer refer to OSS in the future, but a lot of its DNA will propagate forth into generations to come.Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email