several main areas - 1) some level of automation/orchestration, 2) focus on common data movement/management tools between on/off-premises, 3) tools for visibility into all environments
for #2 there are notable developments in the last 6 months even...while data has weight, there are more options around handling it between public/private clouds
Look toward the shift in OpenStack. There's no single pane of glass for Hybrid Cloud. It's understanding the unique challenges between the two environments. The focus needs to be on monitoring and ops technologies that integrate vs orchestration.
Your favorite topic! 😀 I think today they are silos. But they play a factor in containerizing operations so that you can manage your IT regardless of platform.
are seeing the very beginnings of #multicloud with some of our customers...enabled by data sync/management that can handle multiple clouds. If don't have that, the operational overhead is too high.
@CTOAdvisor Hopefully we get the point of multiple robust API's...so API's are a unifying approach but not a single API per se. At that point external engines can drive everything at least...
The recommendation for multi-cloud is coming from the need to leverage specialized clouds with generic cloud providers, e.g. AWS or Azure front-end for GE Predix
100% yes. Refer back to the ROI math on 1PB of data in AWS NFS vs doing it on-premise. The first time a client gets a $250K storage bill they start rethinking things. Tons of use cases for on-premise storage and infrastructure still
major changes in storage usage take time. Would be great to end the burden of storage migration (Wikibon estimates > 1/3 of TCO). Storage is becoming less of an emphasis - all about data
Yes - more or less. There will be orgs that go all cloud. If you are 100% x86/virtualized, there's a strong argument for all public cloud. However if you have a complex business and need for legacy platforms it's not as simple.
There's also the factor of control. Even born in the cloud companies moved to back to all private cloud. Just as data center strategies are revisited every 5 years or so, public vs. private should be revisited as business dictates.
If you have world class operations for a mission critical app, what's the value prop to moving it to the cloud? Save a couple $MM on depreciation but lose a core competence? Not an easy answer.
@steve_pao absolutely lower cost at scale...but for any new customer they won't get to that scale quickly. For existing customers a new application or environment could be incrementally less expensive if forklift upgrades are required to handle.
All of they above. Archive data has elements of all the data types. However, I see companies focused on parts of the distributed application. Look at ML/AI. You'd never do it in the DC. What type of data is ML & AI in the cloud?
Getting past "checkbox" regulation compliance...with tapes after 5 years who knows if can really restore much less move to new tape media (new LTO formats!).
If I decide to deploy HANA in AWS based on elastic compute then it will be structured data. If I want to use cheap and deep storage for AI/ML then it may be unstructured. It gets to the value prop of public cloud for your hybrid cloud use case.
@dinisco we've had cloud file gateways around for a while but adoption still seems to be mixed...people get nervous about the potential lack of performance predictability for "stubbed data"
@andriven with using cloud for archive it's still "on disk" and if done right both can keep a catalog plus selectively restore (not pull back a 100 GB vmdk when just need a 100 KB file)
there's hope that using cloud for certain data types will avoid "data migration" due to changing underlying physical media types (new LTO versions, storage array upgrades)
The hard question - Do you need an hybrid cloud data strategy or better yet a global hybrid cloud file system. @dfloyer talk about this concept a lot. I tend to side with him that enterprise need to think through the distributed hybrid FS.
often cost avoidance...storage is still a big line item but gets more scrutiny every budget cycle due to its size. You have to have options if get pressed harder than last year's budget cycle.