alability and active reassign- ment of idle capacity, which are not well understood. If applications are not structured to make use of these capabilities, they will be more costly and less efficient than the same application running on a dedicated infrastructure. Building services that are designed around a dedicated infrastructure concept and deploying them in a virtualized infrastructure fails to exploit the capabilities of the vir- tualized network. Furthermore, building a virtualized service that makes no use of SDN to provide flexible routing of messages between service components adds significantly to the complexity of the solution when compared to a dedicated application. Virtualization and SDN are well defined, but the key is to enable using virtualization and SDN together to simplify the design of virtualized services. Integration of virtualization and SDN technologies boils down to understanding how decomposition, orchestration, virtualization, and SDN can be used together to create, manage, and provide a finished service to a user. It enables services to be created from modular components described in recipes where automated creation, scaling, and management are provided by Open Network Automation Platform (ONAP), an open source software platform that powers AT&Ts SDN. ONAP enables Independent management of applications, networking, and physical infrastructure A service creation environment that is not limited by a fixed underlying network or com- pute infrastructure The automatic instantiation and scaling of components based on real-time usage The efficient reuse of modular application logic Automatic configuration of network connectivity via SDN User definable services The Need for Change ONAP will benefit service providers by driving down operations costs. It will also give providers and businesses greater control of their network services becoming much more "on demand." At the end of the day, customers are the ones who will benefit the most. The idea of creating a truly per- sonalized secure set of