Automatically triggers DAA device & service testing for each proposed change, provisions test network and tracks change reviews and approvals.
Test Orchestration module interacting with Continuous Integration framework, Source of Truth, and R-PHY Test Suite. The Test Suite interacts with network services (DHCP, ToD, PTP) as well as vCMTS and R-PHY devices.
Accelerate network configuration testing and change approval
Ensures DAA device configuration quality, compliance and security for every change
Automatically documents proposed network changes to improve transparency
Orchestrates every test procedure that needs to be executed once a DAA device or service configuration change is ready for review – such as static code analysis, security policy analysis, unit tests, integration tests and end-to-end system tests. Individual tests can be composed as part of a pipeline that connects into – and is triggered by – a continuous integration framework, which can be either hosted in a public cloud and maintained by a third party or hosted entirely within the MSO’s environment.
Test procedures that require interactions with physical network devices (in a lab) can leverage the ephemeral environments module to automate device provisioning and connectivity, take snapshots of the network state before, during and after testing, and clean up the environment (rollback).
Device access credentials are automatically pulled from a secure repository allowing for stronger passwords, keys & certificates to be used consistently and maintain test device integrity. Furthermore, the network devices and services under test can leverage current or prior production network configurations from a Source of Truth to better match the conditions in the production network.
Once tests commence, their process can be easily monitored in real-time, and upon completion, (PDF) reports can be generated, shared and archived along with the configuration parameters for future recall and comparison.
Completed test procedures and reviewed results can be cryptographically signed to improve traceability, and the final configurations can be tagged to reflect release information, target devices, services & regions, and to inform future deployment procedures.