ONAP Beijing Release Developer Forum

This 2-hour session is both presentations followed by panel discussion on how models can be used to specify platform policy. For ONAP to be truly self-service and to support adaptive model drive management and control, any Dev Operations team must be able to easily specify and validate platform level policy providing the foundation for service and resource related policies. Every company has Dev Ops requirements that share common needs, but differ in current infrastructure requirements. Having a flexible, simple information and data model that captures platform policy is necessary to support all the possible scenarios. In addition, platform-level policies must be able to integrate well and work efficiently with the service and resource level policies that evolve over their lifecycle. How can we define models that can meet the dynamic and changing needs of a policy-enabled ONAP without the time and expense of modifying software code? How can operation teams use ONAP policies to automatically respond to events and conditions, in order to reduce the time required to react while increasing overall network and service availability thereby reducing the labor and effort required to manage the complex infrastructure and services? To support self-service, how does a model-driven Policy Platform support the capabilities to administer policies and monitor policy execution, including: policy creation and editing, policy translation, policy harmonization (conflict detection/resolution), policy validation, policy activation and tracking, policy monitoring, and policy reporting? How can the ONAP community bring together the Policy Information and Data Models, the Use-Cases, Common Reference Points and exchange mechanisms that are essential to enabling a policy-based model-driven ONAP? How do Policies that were defined during on-boarding of a VNF evolve when they are consumed as part of the on-boarding and instantiation of service-level policies?