30m Brief introduction about Telco-vendors collaboration pattern - DevIntOps, which would leads to faster delivery and better quality of NFV in production ENV.
Brief introduction about Telco-vendors collaboration pattern - DevIntOps, which would leads to faster delivery and better quality of NFV in production ENV.
As NFV technology decoupled different components, it also brings the complexity of integration and interoperation. In production NFV deployment, it always involves multiple vendors, hardware vendor, storage vendor, integration vendor etc, the deployment is “blackboxed”, the speed and quality could be uncertain and uncontrollable. In order to optimize the delivery, Telco operators need to get their hands dirty, go deep into the integration and deployment , to build a Telco-vendors collaboration pattern - DevIntOps.
DevIntOps: adding an integration stage between vendors "Development" stage and production "Operation" stage, "Integration" stage means continuously integrate and deploy NFV in Telco lab, continuously verify if products from different vendors can integrate and works good with others. By doing pre-integration, we would be able to detect issues or gaps before production deployment, and so their will be enough time for optimize the integration procedure or fix issues with patches.
Slides & Recording
Please indicate your session type in the blank space below and then remove this Info field.
- Demo / Informational (non-interactive)
- You may be asked to pre-record this session which will be made available on-demand.
- Live Interactive Session
LFN Staff may elect to publish some videos to YouTube. Please indicate here if you do not want your session to be published to YouTube.
1, Promoting more close collaboration between vendors and operator by continuous integration multiple vendor products, continuous testing, continuous optimizing.
2, Promoting Pre-integration and Pre-deployment before production deploy, will help improve the quality and save time.
1, Openstack deploy could be very complex, hard to fully automate deploy and upgrade
2, Not easy to define which vendor should be responsible for the defect, suggesting apply RC testing.