>>Live from San Diego, California at the cue covering to clock in cloud native con brought to you by red hat, the cloud native computing foundation and its ecosystem Marsh. >>Welcome back to the cube here in San Diego for cube con cloud native con 2019. It's our fourth year of doing the cube here. I'm Stu Miniman. It's my fourth time I've done this show. Joining me is Justin Warren. He's actually been to more of the coupons than the cube has, I think at least in North America. And welcome into the program to two veterans of these events from pure storage. Uh, sitting to my right is she'll be uh, Shrivastava who's a director of product marketing and sitting to her right is Anthony lay Ferrario who's a senior product manager, uh, both of you with pure storage. Thank you so much for joining us. Thanks for having us. All right, so, so we, we were kind of joking about veterans here because we know that things are moving faster and faster. You both work for storage companies. Storage is not known to be the fastest moving industry. Um, it's been fascinating for me to watch kind of things picking up the pace of change, especially when you talk about, uh, you know, how developers and you know, software and a multicloud environment, a fit-out. So she'll be maybe, you know, give us a frame for, you know, you, you know, you're in a Cooper ladies tee shirt here pures at the show. How should we be thinking about pure in this ecosystem? >>Sure. Yeah. So, uh, you're, as, you know, we, we side off as all flash on brand storage company, uh, 10 years ago and, uh, we've kept pace with constantly innovating and making sure we're meeting our customer's needs. One of the areas of course that we see a lot of enterprises moving today is two words, microservices, two words, containerized applications. And our goal that you're really is to help customers modernize, modernize their applications while still keeping that store it's seamless and keeping that, uh, invisible to the application developers. >> I think it actually lines up really well if you're do just a pure sort of steam across time has been performance with simplicity. Right? And I think the simplicity argument starts to mean something different over time, but it's a place that we still want to really focus as our customers started to use, uh, try to containerize our applications. >>There are couple of challenges. We saw continued environments, of course, they're known for their, uh, agility, uh, how portable they are. They're lightweight and they're fast. And when they're fast, storage can sometimes be a bottleneck because your storage might not necessarily scale as fast. It might not be able to provision storage volumes as fast, your container environment. And that's the challenge that we at pure why to solve with our Cuban eighties integrations. Anthony, you mentioned simplicity there. So I'm going to challenge you a bit on that because Kubernetes is generally not perceived as being particularly simple and the storage interfaces as well, like stateful sets is kind of only really stabilized over the last 18 months. So how >>is pure actually helping to make the Cuban Eddie's experience simpler for developers? Yeah, and you know, you're totally right. I don't think I was necessarily saying that someone looking for the simplest thing that could ever find would adopt Kubernetes and expect to find that. But what I really meant was, you know, on one hand you have, you know, your more traditional enterprise infrastructure type folks who are trying to build out the underlying private cloud that you're going to deploy, you know, your infrastructure on. And on the other hand, you have your developers, you have your Kubernetes, you have your cloud native applications, right? And really the interface between those is where I'm looking at that simplicity argument because traditionally pure has focused on that simple interface to the end user. But the end user, as we were talking about before, the show has shifted from a person to being a machine, right? >>And the objective for pure and what we're building on the cognitive side is how do we take that simple sort of as a service consumption experience and present that on top of what looks like a traditional infrastructure platform. So I can get more into the, the details of that if you'd like, but really that that layer is where we're focused on the simplicity and really just asking the, the, uh, the end user as few questions as we can. Right. I just want to ask you, what do you need? I don't want to ask you, well, tell me about the, you know, IQN and blah, blah. They don't want that, right? That's the simplicity I'm talking about. Yeah. Well, you run developers generally, I mean, the idea of dev ops and I challenge people whenever they mentioned dev ops, and I'm hearing a pretty consistent message that developers really don't care about infrastructure and don't want to have anything to do with it at all. >>So if you can just bake it into the system and somehow make it easier to operate it, that kind of SRE level, that infrastructure level that, that Kubernetes as a platform. So once that's solved, then as a developer, I can just get on with, with writing some code. We definitely want stories to be invisible. Yeah. So if you want, but if they want stories to be invisible, that's not so great for your brand because you actually want them to know and care about having a particular storage platform. So how do you, how do you balance that idea that we want to show you that we can have to have innovative products that you care about the storage, but you also don't need to care about the storage at all because we'll make it invisible. How does that work? >>So Coupa storage for container environments has been a challenge. And what we are trying to educate the platform level users is that with the right kind of storage, it can actually be easy stores. For QA, these can be easy. And, uh, the way we make it simple or invisible is through the automation that we provide. So pure service orchestrator is our, uh, automation for storage delivery into the containerized environments. And so it's delivered to a CSI plugin, but we tried to do a little more than just develop a plugin into your Cubanetis environments. We tried to make your scalability seamless, so it's super easy to add new storage. And, um, so yeah, I think because a container environments were initially developed for States, less applications when became to staple applications, they still think about, Oh, why should I care about storage? But people are slowly realizing that we need care about it because we don't want to ultimately be bothered by it. Right. >>And if I can make, if I can make a point to just tag on to that I, the conversations I've had at the show this week, I've even helped me sort of crystallize the way I like to explain this to people, which is at first, you know, a lot of people will say, Oh, I don't, I don't do stateful application. I'm doing stateless applications and competitors. And my response is, okay, I understand that you've decided to externalize the state of your system from your Kubernetes deployment. But at some point you have to deal with state. Now, whether that's an Oracle database, you happen to be calling out to outside of your community's cluster, whether that's a service from a public cloud like S3 or whether that's deciding to internalize that state into Coobernetti's and manage it through the same management plane you have to have state. >>Now when we talk about, you know, what we're doing in PSO and why that's valuable and why, you know, to your point about the brand, I don't necessarily worry is because when we can give a seamless experience at the developer layer and we can give the SRE or the cluster manager layer a way where they can have a trusted high performance, high availability storage platform that their developers consume without knowing or worrying about it. And then as we look into the future, how do we handle cross cluster and multi-cloud stateful workloads, we can really add value there. >>Well, yeah, and I'm glad you brought up the multi-cloud piece of it because one of the more interesting things I saw from pure this year is how pure is putting in software cloud native. Um, so when I saw that one of the questions like, okay, when I come to a show like this, how does Kubernetes and containers fit into that old discussion? So how help us connect the dots as to what was announced and everything else that's happening. >>You've heard about cloud block store, which is our software running on the AWS cloud today. And uh, that's basically what we've done is we've people have loved flash array all these years for the simplicity it provides for the automation and performance. You want to give you something similar and something enterprise grade in the public cloud. The cloud, Luxor is basically, you can think of it as a virtual flash array and on the AWS cloud. So with that, you now have D duplication, 10 provisioning capabilities in the cloud. You can, um, be brought an active cluster, which is active, active, synchronous replication between availability zones. So really making your AWS environments ready for mission critical applications. Plus with our, you know, PSO just works the same way on prem as in the cloud. So it's just great for hybrid application mobility. You have the same APIs. >>Yeah, it's actually very cool. Right? One of the, one of the, you know, fun things for me as a software developer at pure, at a software side guy at pure, um, is that the API's that our arrays have are the same API. It's actually the same underlying software version even though it's a totally different hardware, hardware back end implementation. When we run in a cloud native form factor versus when we run in a physical appliance form factor, the replication engines work between the two snapshots, clones. Um, our ability to do instant, um, restores like everything that we do and that has brought value from our, our storage software stack, we still get access to in a cloud native environment and the transports as well. I guess trying to understand, is there Kubernetes involved here or is this just natively in AWS? And then then on premises itself is a, >> is a compute orchestration layer component. So when I look at Kubernetes, I'd say Kubernetes sits above both sides, right? Or potentially above and across both sides, um, depending on how you decide to structure your environment. But the nice part is if you've developed a cloud native application, right, and that's running on Kubernetes, the ability to support that with the same storage interfaces, the same SLS, move it efficiently, copy it efficiently and do that on whatever cloud you care to do. That's where it gets really cool. >>So we developed this really cool demo where you have a container application running on PSO, on flash array, on prem. We migrated that to cloud block store and on AWS and it just runs, you use the same yanno scripts in both places. There is no need to, you know, do a massive rearchitecture anything. Your application just runs when you move it. And we take care of all the data mobility with our asynchronous replications, you can take a snapshot on prem, you can snap it out into AWS, restore it back into cloud block store. So it really opens up a lot of new use cases and make them simple for customers >>that that idea of write once run anywhere. I said I'm, I'm old enough to remember when Java was a brand new thing and that was the promise. And it never quite got there because it turns out it's really, really hard to do that. Um, but we are seeing for from pure and from a lot of vendors here at the show that there's a lot of work and effort being put in into that difficult problem so that other people don't have to care about it. So you're building that abstraction in and, and working on how this particular, how the details of this work. And, uh, I was fortunate enough to get a deep dive into the end of the architecture of cloud Brock's door, just a recent accelerate conference and the way you've actually used cloud resources as if they were kind of infrastructure components and then built the abstraction on top of it, but in the same way that it runs on site, it, that's what gives you that ability to, to keep everything the same and make it simple, is doing a lot of hard work and hard engineering underneath so that no one has to care anymore. >>Yeah. And the way we've architected CloudLock store is that, you know, be as use the highest performance performing, uh, AWS infrastructure. And the highest durability it this infrastructure. So you're actually now able to buy performance and, and durability in one through one single virtual appliance as you would. >>Yeah. How's the adoption of the products going? I know it was, it was very early when it was announced just a few months ago. So what's the feedback from customers been so far about? >>It's been really positive and actually, you know, the one use case that I want to highlight really most is actually dev ops use cases, right? This, the value add of being able to have the same deployment for that application for a test or dev infrastructure in one cloud versus a production to point them in another cloud has been very exciting for folks. So, you know, when you think about that use case in particular, right? The ability to say, okay, I'm coming up to a major quarterly release or whatever I have for my product, I need to establish a bunch more test environments. I don't necessarily want to have bought that and we're not necessarily talking about, you know, bursting over the wire anymore. Right. We're talking about local, uh, local storage under the same interfaces in the cloud that you choose to spin up all of those test environments. So cases like that are pretty interesting for folks. >>Yeah. I think that's how people have started to realize that it's that operation side of things. It's not even day to day 90 and day 147 where I want to be operating this in the same place in the same way no matter where it is because it just saves me so much heartache and time of not having to re implement differently and I don't have to retrain my resources because it all looks the same. So, uh, yeah, Def does definitely have a big use case migration through verbose. That's another use case that we are seeing a lot of customers interested in and uh, disaster recovery, using it as a disaster recovery. How do you, so you can efficiently store backups on Amazon S three, but how do you do an easy fast restore to actually run your applications there? So with CloudLock store, it is now possible to do that, to do a fast, easy restore. Also a couple of weeks ago actually, we started taking registrations for a beta program for cloud Glocks or for Azure as well. Uh, yup. Customers are going multi-cloud. We are going multi-cloud with them. >>Great. I want to give you both a final word, uh, takeaways for a pure storage participation here at the show. >>I think the biggest thing that I, that I want people to understand, and I actually gave this talk at the cloud native storage day on day zero is that cloud native storage is an approach to storage. There's not a location for storage. And I think pure storage that really defines to me the way we're going about this, we're trying to be cloud native storage wherever you need it. So that's, that's really the takeaway I'd like people to have about pure >>and cute and storage for Cuban. It is, doesn't have to be hard. We are here all day today as well. So, um, I mean this is a challenge the industry seeing today and uh, we have a solution to solve that for you. >>All right, well that's a, that's a bold statement, uh, to help end us as Shilpi. Anthony, thank you so much for joining us for Justin Warren. I'm Stu Miniman back with more coverage here from cube con cloud native con 2019 stay classy, San Diego. And thanks for watching the queue.