Domino Release D Planning 10/03/2016 Domino Release D Planning

Domino Core in Release C Step 1: Extract policy labels and policy targets Step 2: Find which nodes require which policy labels Step 3: Identify which nodes can be hosted by which domain based on label subscriptions TOSCA VNF or Network Service Descriptor NS/VNF Topology Policy Rules Label format: <policytype>:properties:<key:value> Example: tosca.policies.Placement.Geolocation:properties:region:us-west-1 Rule-1 Node-1 Label X Label Y Node-2 Rule-2 Label Z Label A targets properties Draw the graph view of service description and splitting Node-K Rule-N Label B Label G Nodes can be VNF, VDU, Connection Point, Virtual Link, Forwarding Path, VNFFG

Domino Core in Release C VNF1 CP2 VL1 VL3 CP1 CP5 VL2 VNF2 CP6 CP3 CP4 VNF3 VNF4 Domain 1 Domain 2 VNF1 CP2 VL1 Draw the graph view of service description and splitting VL1 CP1 VL3 VL2 CP5 VNF2 CP3 CP4 CP6 VNF3 VNF4

Release D Planning Installer Integration Open-O GSO project as upstream Label-based capability discovery and requirements matching for NFV-O and SDN-O Heat and Tacker based VNF onboarding Multi-domain NS onboarding Workflow generation Boundary definition, insertion, augmented templates Installer Integration Release-C test case performs post-installs At least work with JOID to install Domino Page 4

Release D – Open-O as Upstream Service Composer GSO DOMINO Services Service Decompositon Domain Specific Template Creation Capability Discovery Domino Agent Domino Agent Domino Agent Domino Agent Example of boundary condition definition SDN-O SDN-O NFV-O NFV-O

Release D – Integration Project DOMINO VNFD VNFD Heat Orch. Template Domino Agent Domino Agent Domino Agent NFV-O Tacker Heat OPENSTACK BARCELONA SUMMIT TARGET

Release D – Multi Domain Network Service ??? VNF1 CP2 VL1 VL3 CP1 CP5 VL2 VNF2 CP6 CP3 CP4 VNF3 VNF4 Send to Domain-1 Send to Domain-0 How do we split the template over multiple domains without breaking the connectivity? Insert an L2 or L3VPN service?