Glenn Dekheyser

because ingress is free in amazon so they got this inter-regional bill that was just totally unbudgeted the customer was not very happy with this

And I realized I was missing a dimension of architecture in this.

And this is like six years ago, seven years ago at this point.

Talking to other folks active in the NetApp community, I realized most people didn't think about this.

They said they would have run into the same problem because they just figured the customer guys has this figured out.

And I will say that if you're a storage guy and you're doing anything hybrid cloud and you expect your customer

to have optimized or understand even their hybrid cloud networking, you've made a big mistake.

Assume they don't.

And when they don't, obviously, your stuff is probably not going to work the way you think it's going to work.

Your customer may get a bill or they may not just get the performance they want.

Things just aren't going to come together.

You need to be able to put your customer in a position where they can succeed not just with this project, but with the future projects and keep them flexible.

I think the time is now for storage people to make sure they understand cloud private connectivity and things that have driven that reason to learn, especially now as the world, you'll see it more outside the US, but certainly you see it here as well in multinational corporations.

Sovereignty has become a huge topic.

Customers are really increasingly looking to get that data.

on equipment they control in locations they can access so that they can claim the sovereignty of it.

I'm not saying they're looking to extricate the clouds necessarily.

They are certainly looking to make sure that if they have to get out, it's easier than it has been in the past.

You start to see a greater interest from some of the public clouds

of interconnectivity between themselves so they can move.