Jay Kay – HP
During the Jay Kay Systems event, we had opportunities to meet in small groups with each manufacturer. These are my notes from the various sessions.
Hewlett Packard (HP)
Software Defined Networks (SDN)
Problem with Networks today:
Industry hasn’t kept up.
Continue to have problems with security, robustness, manageability
CAPEX has not been reduced and OPEX grows due to complexity
Network operators find it difficult to introduce new revenue generating services on their infrastructures.
Open Networking foundation on SDN
…In the SDN architecture, the control and data planes are decoupled, network intelligence and state are logically centralized and the underlying network infrastructure is abstracted from the applications…
Network Architectures are currently very proprietary -> But the industry is starting to look at standard interfaces and control protocols.
What is OpenFlow?
Protocol for direct access to switch forwarding plane
- Controller or control software uses OpenFlow protocol to provide programmable interface to switches & routers
HP has been involved in OpenFlow since 2007 (started with project called Ethane)
Goal is to have 100% of switches supporting OpenFlow by the end of 2013.
Todd’s note: All of our switches support OpenFlow
HP wants to delivery SDN to achieve agility
Separate control pane
HP now has a Virtual Application Networks SDN Controller – can get it as a stand-alone controller, or a virtual controller.
Also Virtual Cloud Network Application
Automates network provisioning enabling self-service cloude
Limits provisioning actions to low risk infrastructure elements
Sentinel Security Application
CERN: Distributed Load Balancing Application
Debunking some SDN myths
Application Layer – Only deliver network a function in software on a VM or only creating an overlay network
Control Layer – only offering proprietary programming interfaces to network devices & management
Infrastructure Layer – The end of hardware innovation