• elastic, mobility infrastructure
  • cloudlet
  • app to data

Thanks to SDN the data streams in network infrastructure can be reprogrammed. Network functions provided by fix network devices can be migrate to where clients are located. New mobility solutions go opposite direction to detecting and handing over clients to others access networks providing adjacent coverage areas. This requires complex interaction between client and the access network. When clients move, they are handled over and ongoing services are reestablished (how mobile ip did, this also require the same service capability at adjacent access network). Instead, with SDN, the service is migrated to new access network. Network, service applications are migrated to neu infrastructure location. Data flows are reconfigured and optimized. Client experience true mobile service as the service network virtually extendable to wherever the clients are.

• how SDN does that?
  • http://www.ericsson.com/news/140220-the-real-time-cloud_244099438_c

This is the enabler.

are you OVS expert?

• openflow?
• ovsdb?
• ovsdb protocol?

What it can

Why is it important

Network controller function

Why not Neutron?

Theoretically Neutron can be extended. It need more to be SDN controller. SNMP, Netconf, 3rd party protocols.

That's what ODL is.

Other SDN controller out there

• Opencontrail
• …

• Neutron northbound
• OVSDB southbound

• southbound
• northbound

Extend the tools to be both SDN and Openstack controller.

Integrated through AT&T’s Wide Area Network (WAN) and utilizing Network Function Virtualization (NFV) and Software Defined Networks (SDN), as well as modern architectural and operational approaches, AT&T plans to simplify and scale its network by:

a fully programmable fabric of networking and virtualized resources

NFV-centric orchestration falls short of the operator end-goal: a fully programmable fabric of networking and virtualized resources. I am confident that stitching services hop-by-hop through disparate networking systems, technologies and domains is not on an operator’s Christmas wish list.

For network operators, the combined orchestration of WAN and data center resources enables:

• Policy-based placement of VNFs across the entire pool of virtualized resources.
• End-to-End service chaining spanning both the physical network as well as the data center.
• Follow-the-sun (and follow-the-people) resource allocation models, coordinating network bandwidth and applications.
• Service-layer fault management, correlation and isolation across networking and data center resources.
• Unified management of the service-quality and user-experience.
• Data center interconnect virtualization allowing for efficient sharing of resources that span multiple domains.

Operators can only realize the complete potential of carrier SDN and NFV when they can manage all of their resources through a single-pane of glass. This enables them to dynamically design, assemble and deliver revenue-generating services across their infrastructure. In fact, it is worth mentioning that the single-pane of glass is very likely to be an M2M interface. Operators want automation; they want RESTful API-driven solutions and programmatic interfaces. The orchestrator must expose the network and data center resources as programmable entities, and allow operators to define services with commonly used object modeling languages (e.g. JSON, TOSCA, YANG). This is the future. To all the operators out there - we hear you loudly and clearly.

from page 16 to here: ieeexplore.ieee.org/search/searchresult.jsp?ranges%3D20122014pPublicationYear%26pageNumber%3D55%26queryText%3Dnetwork+virtualization&pageNumber=46

paper sdn nfv