ms, performance, and logs typically trigger a human to perform a VM reboot. This information, combined with expert domain knowledge, can be transformed into policies that automate future reboot actions. 15.2.4.3 Increasing Software Complexity ONAP and virtualization together provide a meteoric shift to an increased reliance on software, with a corresponding reduction in our reliance on hardware. As the industry gains more experience with these technologies, we will learn whether this comes with a corresponding increase in the number and complexity of software bugs, and whether this creates a greater challenge in trouble- shooting. As we gain further experience, we expect that this will drive new understanding of the tooling required to support troubleshooting of these issues. TRANSFORMING THE OPERATIONS TEAM Despite the fact that traffic volumes continue to grow exponentially, revenue growth for service providers does not follow the same curves. Thus, operations teams typically cannot be significantly expanded, even in the face of a vast number of new, virtual network functions and control capabili- ties (ONAP) being deployed. It is also unlikely that the economics will make it attractive to imme- diately replace all of the legacy physical network elements-even as each given network function is being virtualized. Thus, service providers will likely take a "cap and grow" approach to initial VNF deployment; leaving physical network functions (PNFs) in place and adding new growth traffic onto virtualized functions. This is more capital efficient, but leaves operations teams having to support both physical and virtual versions of the same network function, thereby significantly increasing operations responsibilities. Thus, achieving this without expanding the operations team size will necessitate significant enhancements to legacy technologies (PNFs) automation, as well as taking advantage of the improved efficiencies promised through ONAP. The virtualization of network functions also changes the roles that operation