Site icon IT World Canada

Software-defined Systems and Services

OpenStack logo

We appear to be moving into an era where ICT is “software-defined” and typically offered “as a Service.”  This is especially true for enterprise networks although the concept can be extended to computing, storage and transmission as well.

The first page of a Google search for “software-defined” includes the following:

The Open Networking Foundation (ONF) defines SDN as:

The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.”

In fact, this could be generalized to:  The physical/virtual separation of the control subsystem from the functional (processing/storage/networking/device) subsystems, and where the control subsystem controls several functional subsystems.

One of the key messages of a recent symposium hosted by the University of Toronto and sponsored by HP is that software has become the facilitator for a new generation of highly flexible, agile networks.  This is leading to innovative new products and a more standard, simplified infrastructure.

What makes being software-defined so important?  Some of the “-ility” characteristics for SDN (based on the ONF description) are:

The essence of the SDN architecture is to divide the network into three subsystems (usually called layers):

Software-driven networks and management systems are not really new – separation of the control plane has been used in older telco networks and almost all network hardware includes some form of software (e.g., microcode or firmware).  SDN’s, however, add a new level of automation that spans vendors and devices and facilitates service automation and dynamic management.  This allows managers to re-focus from managing bytes and packets to managing the overall “quality of experience.”  It can also support the rapid service delivery and elastic capacity required for cloud environments.

Mobility is also one of the driving forces for software-defined networking.  Some of the network requirements for mobility are:

The U of T Symposium referred to earlier covered various SDN and mobility topics from both the research and planning viewpoints.  Presentations included:

Some of my personal conclusions from the Symposium, after having listened to the various speakers, were:

Exit mobile version