overture carrier classorchestration_sd_nandnfv_ctopraysonpate_10-2013
DESCRIPTION
Use SDN and NDV for Carrier-class orchestration. SDN and NFV will be used to build carrier services across the network, but orchestration must reflect additional requirements. It's not enough to think of it as the same as traditional orchestration focused on the data center.TRANSCRIPT
OVERTURENETWORKS.COM
Carrier Class Orchestration for SDN & NFV Prayson PateChief TechnologistOverture Networks
2 Carrier Class Orchestration for SDN & NFV
Carrier Orchestration is Different!Traditional orchestration (e.g. AWS CloudFormation) is focused on the data center.
Carrier SDN and NFV will be used to build carrier services across the network; orchestration must reflect additional requirements.
3 Carrier Class Orchestration for SDN & NFV
Resource Acquisition, Assignment & Span• In a data center, resources are all equivalent.• In an NFV network location matters• Span extends beyond data center to MEN and WAN
CustomerSite
Central OfficeMini-Datacenter
Metro Datacenter
MetroNetwork
All the sameThese resourcesare scarce, but lower latency
Not justin here
But also here
4 Carrier Class Orchestration for SDN & NFV
Lifecycle and Work Flow• Critical to tie into
higher-level systems• Could be OSS/BSS
systems• Could be network
applications• Programmable and
transactional behavior on service activation
• Reliability and status monitoring
5 Carrier Class Orchestration for SDN & NFV
Service Elasticity and Orchestrator Scalability
• Services built using NFV must have VNF components that are elastic / horizontally scalable
• Can’t be simple conversions of software to run on a server instead of an appliance
6 Carrier Class Orchestration for SDN & NFV
Orchestrator Multi-Tenancy• Wikipedia: “Multi-tenancy refers to a principle in
software architecture where a single instance of the software runs on a server, serving multiple client-organizations (tenants)”
• Different from “virtualization where components are abstracted enabling each customer application to appear to run on a separate physical machine.”
• Orchestrator multi-tenancy simplifies system design and integration into higher level systems.
7 Carrier Class Orchestration for SDN & NFV
Summary of Carrier Class OrchestrationAspect Data Center Carrier ClassResource Acquisition and Assignment
All resources are equivalent
Location, latency and bandwidth matter
Span of Control Within data center Across metro areaLifecycle and Work Flow
Controlled directly by user
Tied into higher level systems
Service Assurance and Resilience
Coarse status monitoring
Transactional behavior and fine status monitoring
Elasticity, Scalability and Multi-tenancy
Current resources are elastic
VNFs must be elastic and orchestrator multi-tenant
