STRATOSS™ LIFECYCLE MANAGER 2.0 PRODUCT OVERVIEW
This shows the simplification of the operational lifecycle of cloud network services. Version 2.0 builds on the work of V1.0 but demonstrates even greater levels of automation.
- Intent Execution: A dynamic view of ongoing intent progress and tasks. View execution history of assembly instances.
- Designer: Graphical designer to design VNF, network services, and behaviour driven tests. Drag and drop to establish relationships and property sharing.
- Suite of tools for behaviour driven testing: Create test assemblies, create test scenarios, run test scenarios, show and send results to Kafka.
- Deployment location and resource managers: Add, edit and remove deployment locations and resource managers
- Role based access control: The ability to control access to specific functionality in the Lifecycle Manager based on LDAP
- CI/CD Hub: Set of tools and reference processes and examples on how to integrate to a CI/CD DevOps environment. The reference implementation uses Gitlab for source code versioning, Jenkins for continuous integration, LMCTL tool to create, push, pull, and test VNF and Network Services.
SDN NFV WORLD CONGRESS, 2018 – THE HAGUE
Brian Naughton, CTO, presenting on Applying DevOps to the Modern Service Factory.
How do we have a predictable cookie-cut way of delivering and maintaining services so that the costs are under control, but predictable?
“Intent based orchestration is similar to how a sat nav works. Rather than programming all of the lifecycles that bring the service into being, then programming the lifecycles that heal it, change it, optimise it, or move things around for cost and quality reasons, operators need an engine that removes that operational burden from Design and Engineering in order to scale. The intent engine means you can tell it what state you want a service in and it will automatically figure out how to get that service from A to B, taking into account whatever the state of the environment is.”
“Accanto’s focus are the operational NFV use cases. The complicated pieces that an operator would normally throw people at. How does an operator automate after they’ve turned on a service, not just a VNF? If something breaks, or we want to change the shape of that service normally an army of people would be thrown at it. We want to add a whole level of automation to that ‘service’ lifecycle.”
“Level 1 and level 2 people within an operator, who are looking at trouble ticketing or looking at an appliance state, will have to disappear due to the new complexity of a virtual network. In our world, support becomes something that is embedded in the engineering process. The lower cost operating model is required in order to bring NFV to market.”
“Given that NFV is either software programmable or delivered as a lump of software the level of automation that we should be able to achieve in this next version of the service factory, should be greater than anything we’ve been able to achieve in the past.”
SDN NFV WORLD CONGRESS, 2018 – THE HAGUE
Victor Donselaar, VP Sales, presenting on Lights Out Operations for NFV.
Lights out operations is about running your complex network services with close to 100% automation.
“ETSI state that a VNF typically has 13 different lifecycles. So, when an operator moves from a physical to a virtual world, they have to consider 13x more lifecycles. Basic lifecycles i.e. start, stop, etc are centred at the point of on-boarding and mapped to VNF specific device commands making them quite easy to program. However, the more advanced scale, heal, amend, upgrade commands etc, are more difficult to program because logic has to be applied to take into account multiple scenarios and policies. Then take into account the lifecycle of the service itself, which also has to be managed. Manual programming isn’t an option and traditional OSS tools won’t work.”
“Our focus has been on reducing the manual effort involved in launching and running services and we believe we can achieve a 30% reduction.”
“How will an operator scale when these multiple virtual services and all of the associated lifecycles kick in?”
“There are 3 steps to NFV operational automation. Number 1 is Intent driven orchestration, automating most of the lifecycles once the services are in production. Number 2 is reducing operational errors with Behaviour Driven Testing, testing all of the lifecycles before the service goes into production. The third step, having achieved a significant amount of automation with the first two steps, is with AI. Using artificial intelligence to apply diagnostics to uncover any problems that might not have been addressed previously.”
Tackling Network Operations Complexity and Resource Challenges with StratOSS™
Increasing network service complexity can place additional demand on scarce skill sets, breaking the business case. Watch ‘Engineer Jack’ and ‘Operations Jill’ demonstrate how StratOSS™ can solve the problem.
How can we scale to solve the complexity of the networks of tomorrow – today?
Customer demand for bandwidth has never been higher, and networks are struggling to cope.
From Mobile World Congress 2018, IBM and Accanto explore the changing landscape of Telecommunications today, focusing on the necessity of network reinvention and the opportunities and challenges that come with changing business models and the status quo.
Automating complex network operations. An overview of the StratOSS™ solution
View the story of how Accanto addresses the complete lifecycle of network automation, bridging the gap between Development and Operations.
SDN NFV World Congress, 2017 – The Hague
Brian Naughton, CTO, Accanto Systems presents, ‘How to achieve service factory levels of cloud network automation’.
Delivering Complex Network Operations with DevOps
Brian Naughton, CTO Accanto Systems, presents ‘Delivering NFV DevOps Through Continuous VNF Integration and Service Behaviour Driven Testing’.