Hybrid Infrastructure Complexity
Transcript
hybrid infrastructure has one meaning that is going to be a cloud plus conversation from now until the next delivery method of Enterprise it comes available we're going to have our labels Legacy Storage arrays most of us are multiple vendor data center designs are Cloud assets and we are going to move assets from the data center for workloads from the data center into the public Cloud we're going to run move workloads from the public Cloud into the data center as we optimize for both cost performance in
efficiency that means that the resorting operations model equates to complexity private data center doesn't operate in the same way that public Cloud operates public Cloud doesn't operate in the same way that private data center operates even if we took the 200 plus projects of the cncef cloud native cloud computing Foundation whittled it all down to a consistent offering we're not Cloud providers we can't mimic what they do however there are examples of companies looking to address some of this complexity it's moving slowly but interesting hpe
recently announced their let me get make sure I can get this name right there are Pub their private Cloud Business Edition or Green Lake private Cloud Business Edition why am I doing a video on this because I own hpe dhci system based on their uh liter Electra it's spelled elytra by the way hpe but they're Electro storage array system the electric 6000 in my case and talking to hpe I get this thing for free it's part of my licensing agreement for the next couple of years
and basically it is a control plane that allows me to present a cloud interface to my VMware vsphere environment and the CTO advisor hybrid infrastructure I haven't played around with it yet but as I'm thinking through how do I manage complexity do I want to get in the business of offering my data center assets up to developers as Cloud assets or do I want to think more as a platform team and this is a tool for more platform teams and it is a interface for developers
to consume I don't want to give developers yet another API the Green Lake API into the data center I want them to continue to use whether it's openshift kubernetes aws's control plane I want them to continue to use the API they're familiar with and for my platform team to make that invisible to them so my general question to you where is the battle for hiding the complexity from your developers and managing that complexity for it is that within the platform team is that within our Cloud
providers is that within our OEM hardware and isvs independent software vendors I'd love to know your feedback talk to you next CTO dose
