odels used to define service and network data structures are compiled directly to java code to generate the REST APIs. It would be interesting to look at an API engine that could directly operate off the YANG models and bypass the steps for code generation. Dynamic binding of the REST RPCs and RESTCONF GET/PUT/POST/ DELETE operations against the http server based on the model would be another opportunity to take time and resources out of the feature development cycle. ACKNOWLEDGMENT The authors would like to acknowledge the contribution of Margaret Chiosi. Building the Network of the Future REFERENCES 1. YANG-A Data Modeling Language for the Network Configuration Protocol (NETCONF), IETF RFC6020, https://tools.ietf.org/html/rfc6020. 2. S. Agrawal, V. Narasayya, B. Yang, Integrating vertical and horizontal partitioning into automated physical database design, Proceedings of the 2004 ACM SIGMOD International Conference on Management of Data, June 13-18, 2004, Paris, France. 3. Node-RED-http://www.nodered.org/ 4. PCEP-Path Computation Element (PCE) Communication Protocol (PCEP) RFC5440, https://tools. ietf.org/html/rfc5440. 5. ODL-http://www.opendaylight.org/ 6. OpenContrail-http://www.opencontrail.org/ 7. ONOS-http://onosproject.org/ The Network Operating System VNF Automation Platform Chris Rice and Andre Fuetsch CONTENTS ONAP: Logical Technical Architecture 7.1.1 Open Network Automation Platform 7.1.2 ONAP Component Roles 7.1.3 European Telecommunications Standards Institute: NFV Management and Orchestration and ONAP Alignment Master Services Orchestrator SDC Environment 7.3.1 Metadata-Driven Design Time and Runtime Execution 7.3.2 Data Repositories 7.3.3 Certification Studio 7.3.4 Distribution Studio Software-Defined Controllers 7.4.1 Application, Network, and Infrastructure Controller Orchestration 7.4.2 Infrastructure Controller Orchestration 7.4.3 Network Controller Orchestration 7.4.4 Application Controller Orchestration Portal, Reporting, GUI, and Dashboard Functions Data Collection Analytics and Events 7.6