Thank you to everyone who joined SDxCentral for its latest webinar featuring UBIqube and the Rayno Report on DevOps culture in the telecom industry. Attendees of the webinar were introduced to the foundations needed to streamline a DevOps culture in dynamic business environments. Next generation infrastructure, operations support system (OSS)/business support systems (BSS), and networks functions virtualization (NFV) technologies were discussed in the context of agile development. Market data on lifecycle service orchestration (LSO) from the Rayno Report was analyzed and UBIqube CEO Nabil Souli made the case for the necessity for a DevOps culture, especially in the telecommunication industry.
How quickly can you train DevOps engineers on your framework?
UBIqube: UBIqube delivers a three-day DevOps training session. During those days, engineers learn how to develop devices adaptors as well as service configuration objects. In addition, UBIqube organizes network DevOps hackathons free of charge. T&Es which are reserved for the DevOps community are not included. To learn more about the next network DevOps hackathlon, please contact us.
What kind of tools do you provide to create objects with CLI or web interface?
UBIqube: The MSActivator web portal features a service designer interface. The graphical object editor embedded in the service designer interface drastically eases the creation of the services configuration objects. This editor features more than just creation, design, update, delete and import capabilities. It also streamlines the management of service parameters in a WISIWIG mode.
UBIqube: More than 20 different device adaptors are supported. In addition to the devices’ plugins, the MSActivator features default service objects libraries. Moreover, the MSActivator empowers service providers and partners with DevOps capabilities. The community of UBIqube certified engineers can therefore develop their own devices adaptors and design on the fly services configuration objects.
Do you have a feature to deploy new configurations on a lot of different devices and to do a rollback in case of error on any device?
UBIqube: While the embedded Object Based Management Framework (OBMF) engine provides the abstraction layer needed to handle multivendor networks, the MSActivator service mashup interface allows the creation of service workflows. OBMF eases the definition of those workflows allowing order recomposition. Service designers can define the state of any machine and send orders to the objects of multiple devices across the network. Error handling and rollback are part of the workflow themselves.
What is the typical integration time to onboard a new vendor?
UBIqube: The MSActivator already features devices adaptors for CLI, Netconf, XML, REST, and SOAP based APIs. Consequently, the integration of a new vendor can be done in days.
Who have you seen customize the technology in DevOps mode?
UBIqube: Each customer or partner is different and depending of the skill sets they have, the level of adoption of this new DevOps approach to kill the integration costs is different. There is an opportunity for system integrators to help service providers that have not yet enabled the transitions to DevOps.
Has the MSAcivator been used in a hybrid network service scenario yet?
UBIqube: The MSActiavtor is deployed in several SPs around the world managing both physical and virtual devices. The MSActivator framework is an agile by design service orchestration so it can spread across multiple domains from legacy to software-defined networking (SDN) and NFV. Hybrid support is a no brainer for real end-to-end service orchestration.
Where do you currently see the most activity and interest in building DevOps-style telecom platforms (geography, size of company, etc.)?
UBIqube: The need for DevOps is global. It is not unique to a certain part of the world. Telcos suffered in the past because changes in service industry led to costly acquisition of professional services from a quintuple of OSS vendors. With the virtualization storm hitting the SP back office, the need for DevOps is key no matter the size of a telecommunication company.
What do you think will happen if telecoms don’t adopt DevOps?
UBIqube: If telecoms don’t adopt DevOps, they will still have the option to pay for expensive professional services, but this approach cannot last for ever.