How cloud-native architecture affects traditional on-prem infrastructure | #KubeCon

stevewattproshot

As traditional, on-premise network infrastructure transitions to the cloud-native model, some are asking what role remains for legacy storage platforms and how will these platforms interface with cloud-based Platform as a Service architecture?

Stephen Watt, chief architect of Emerging Technologies at Red Hat Inc., spoke to John Furrier (@furrier), co-host of theCUBE*, from the SiliconANGLE Media team, during a special on the ground segment as part of the KubeCon 2016 event in Seattle, WA. The two talked about the role of traditional, on-premesis infrastructure as data centers move toward PaaS and cloud-native architecture.

Cloud-native is empowering developers

As traditional data centers transition to a cloud native model, software-defined storage is replacing legacy on-premise storage platforms, according to Watt. Furthermore, the role of developers and how storage space is assigned to their project is changing as well.

In the past, the developer would submit a workflow ticket requesting storage allocation, and an administrator would respond and fill the request. Now, with the cloud-native model, developers are able to create and assign their own storage through the platform, thereby saving time that can be put to better use, Watt explained.

“We want to empower the developer to get storage administrators out of the workflow,” said Watt. “So we want to give developers the ability to dynamically create their own storage.”

Cloud-native versus on-premise storage

In addition to these changes in workflow and developer reponsibility, possible issues with using newer cloud-native, software-defined storage and legacy on-premise storage systems as part of the same network may arise, Watt indicated. The in-house, traditional storage systems may not mesh with the newer cloud-native architecture, meaning both types of storage would need to be managed separately.

“How does that work with traditional on-premise storage platforms that maybe don’t have the APIs or the interfaces to support that?” asked Watt. “So the cloud-native model is not necessarily so conducive with the traditional model.”

*Disclosure: The Linux Foundation and other companies sponsor some KubeCon 2016 segments on SiliconANGLE Media’s theCUBE. Neither The Linux Foundation nor other sponsors have editorial control over content on theCUBE or SiliconANGLE.

Watch the complete video interview below, and be sure to check out more of SiliconANGLE and theCUBE’s coverage of KubeCon 2016.

Photo by SiliconANGLE