>>Hello and welcome to the power of and where H P E Aruba and Pensando are changing the game the way customers scale at the cloud and what's next in the evolution in switching everyone. I'm john ferrier with the Cuban. I'm here with Shane Corbyn, Director of Technical Product management. Pensando Williams show vice president Product management, Aruba HP Gentlemen, thank you for coming on and doing a deep dive and and going into the big news. So the first question I want to ask you guys is um, what do you guys see from a market customer perspective that kicked this project off? Amazing results over the past year or so. Where did it all come from? >>It's a great question, John So when we were doing our homework, there were actually three very clear customer challenges. First, security threats were largely spawned with from within the perimeter. In fact, four star highlights that 80% of threats originate within the internal network. Secondly, workloads are largely distributed, creating a ton of east west traffic and then lastly, network services such as firewalls load balancers. VPN aggregators are expensive. They're centralized and then ultimately result in service changing complexity. So everyone, >>so go ahead. Change. >>Yeah. Additionally, when we spoke to our customers after launching initially the distributed services platform, these compliance challenges clearly became apparent to us and while they saw the architectural value of adopting what the largest public cloud providers have done by putting a smart making each compute note to provide these state full services. Enterprise customers were still were struggling with the need to upgrade fleets and Brownfield servers and the associated per node cost of adding a spark nick to every compute node. Typically the traffic volumes for on a personal basis within an enterprise data center are significantly lower than cloud. Thus we saw an opportunity here to in conjunction with Aruba developed a new category of switching product um, to share the crossing capabilities of our unique intellectual property around our DPU across a rack of servers that Net Net delivers the same set of services through a new category of platform, enabling a distributed services architecture and ultimately addressing the compliance and uh, TCO generating huge TCO and ri for customers. >>You know, one of the things that we've been reporting on with you guys as well as the cloud scale, this is the volume of data and just the performance and scale I think the timing of the, of this partnership and the product development is right on point. You got the edge right around the corner more, more distributed nature of cloud operations, huge, huge change in the marketplace. So great timing on the origination story there. Great stuff. Tell me more about the platform itself. The details what's under the hood, the hardware. Os, what are the specs? >>Yeah, so we started with a very familiar premise, Ruba customers are already leveraging C X with an edge to cloud, common operating model and deploying Leaf and spy networks. Plus we're excited to introduce the industry's first distributed services switch where the first configuration has 48 25 gig ports with 100 gig uplinks running Aruba C X cloud native operating system. Pensando A six and software inside enabling layer four through seven staple services you want to elaborate on. >>Let me elaborate on that a little further. Um, you know, as we spoke, existing platforms and how customers were seeking to address these challenges were inherently limited by the diocese and that thus limited their scale and performance and ability in traditional switching platforms to deliver truly stable functions in in a switching platform. This was, you know, architecturally from the ground up. When we developed our DPU 1st and 2nd generation, we delivered it or we we we built it with staples services in in mind from the Gecko. We we leverage to clean state designed with RP four program with GPU, we evolved to our seven nanometer based DPU right now, which is essentially enabling software and silicon and this has generated a new level of performance scale flexibility and capability in terms of services this serves as the foundation for or 200 gig card where we're taking the largest cloud providers into production for. And the DPU itself is designed inherently to process state track state connections and state will flow is a very, very large scale without impacting performance. And in fact, the two of these deep you component service, their services foundation of the C X 10-K And this is how we enable states of functions in a switching platform. Functions like stable network network fire walling, stable segmentation, enhance programmable telemetry. Which we believe will bring a whole lot of value to our customers. And this is a, a platform that's inherently programmable from the ground up. We can we can build and and leverages platform to build new use cases around encryption, enabling state for load balancing, stable nash to name a few. But the key message here is this is this is a platform with the next generation of architecture is in mind is programmed but at all levels of the stack and that's what makes it fundamentally different than anything else. >>I want to just double click on that if you don't mind before we get to the competitive question because I think you brought up the state thing, I think this is worth calling out if you guys don't mind commenting more on this state issue because this is big cloud. Native developers right now want speed, they're shifting left at the Ci cd pipeline with program ability. So going down and having the program ability and having state is a really big deal. Can you guys just expand on that a little bit more and why it's important and how hard it really is to pull off. >>I I can start I guess. Well um it's very hard to pull off because of the sheer amount of connections you need to track when you're developing something like a state, full firewall or state from load balancer. A key component of that is managing the connections at very, very large scale and understanding what's happening with those connections at scale without impacting application performance. And this is fundamentally different. A traditional switching platform regardless of how it's deployed today in a six don't typically process and manage state like this. Memory resources within the shape aren't sufficient. Um the policy scale that you can implement on a platform aren't sufficient to address and fundamentally enable deployable fire walling or load balancing or other state services. >>That's exactly right. So the other kind of key point here is that if you think about the sophistication of different security threats, it does really require you to be able to look at the entire packet and more so be able to look at the entire flow and be able to log that history so that you can get much better heuristics around different anomalies. Security threats that are emerging today. >>That's a great great point. Thanks for bringing that extra extra point out, I would just add to this, we're reporting this all the time when silicon angle in the cube is that you know, the you know, the the automation wave that's coming with around data, you know, it's the center of data now, not date as soon as we heard earlier on with the presentation data drives automation having that enabled with state is a real big deal. So I think that's really worth calling out now. I got to ask the competition question, how is this different? I mean this is an evolution, I would say it's a revolution you guys are being humble um but how is this different from what customers can deploy today >>architecturally, if you take a look at it? So we've, we've spoken about the technology and fundamentally in the platform, what's unique in the architecture but foundational e when customers deploy stable services, they're typically deployed leveraging traditional big box appliances for east west or workload based agents which seek to implement stable security for each East west architectural, what we're enabling is staples services like fire walling, segmentation can scale with the fabric and are delivered at the optimal point for east west which is through the Leaf for access their of the network and we do this for any type of workload. Being deployed on a virtualized compute node being deployed on a containerized, our worker node being deployed on bare metal agnostic of topology. It can be in the access layer of a three tier design and a data center. It can be in the leaf layer of the excellent VPN based fabric. But the goal is an all centrally managed to a single point of orchestration control which William we'll talk about shortly. The goal of this is to to drive down the TCO of your data center as a whole by allowing you to retire legacy appliances that are deployed in in east west role, not utilized host based agents and thus save a whole lot of money. And we've modeled on the order of 60 to 70% in terms of savings in terms of the traditional data center pod design of 1000 compute nodes which will be publishing and as as we go forward, additional services as we mentioned like encryption, this platform has the capability to terminate up to 800 gigs of line, right encryption, I P sec VPN per platform state will not load balancing and this is all functionality will be adding to this existing platform because it's programmable as we mentioned from the ground up. >>What are some of the use cases lead and one of the top use case. What's the low hanging fruit? And where does this go? Service providers enterprise, what are the types of customers you guys see implementing? >>Yeah, that's what's really exciting about the C X 10,000 we actually see customer interest from all types of different markets, whether it be higher education service providers to financial services, basically all enterprises verticals with private cloud or edge data centers for example, could be a hospital, a big box retailer or Coehlo. Such as an equity. It's so it's really the 6 10,000 that creates a new switching category enabling staple services in that leaf node, right at the workload, unifying network and security automation policy management. Second, the C X 10,000 greatly improved security posture and eliminates the need for hair pinning east west traffic all the way back to the centralized plants. Lastly, a Shane highlighted there's a 70% Tco savings by eliminating that appliance brawl and ultimately collapsing the network security operations. >>I love the category creation vibe here. Love it. And obviously the technical and the cloud line is great. But how do the customers manage all this? Okay. You got a new category. I just put the box in, throw away some other one. I mean how does this all get down? How does the customers manage all this? >>Yeah. So we're looking to build on top of the ribbon fabric composer. It's another familiar sight for our customers which already provides for compute storage and network automation with a broad ecosystem integrations such as being where the sphere be center as with Nutanix prison And so aligned with the c. x. 10,000 at G. A. now the aruba fabric composer unifies security and policy orchestration and management with the ability to find firewall policies efficiently and provide that telemetry to collectors such a slump. >>So the customer environments right now involve a lot of multi vendor and new frameworks cloud native. How does this fit into the customer's existing environment? The ecosystem. How do they get that get going here? >>Yeah, great question. Um our customers can get going is we we built a flexible platform that can be deployed in either Greenfield or brownfield. Obviously it's a best of breed architecture for distributed services were building in conjunction with the ruble but if customers want to gradually integrate this into their existing environments and they're using other vendors, spines or course this can be inserted seamlessly as a leaf or an access access to your switch to deliver the exact same set of services within that architecture. So it plugs seamlessly in because it supports all the standard control playing protocols, VX, Lenny, VPN and traditional attitude three tier designs easily. Now for any enterprise solution deployment, it's critical that you build a holistic ecosystem around it. It's clear that this will get customer deployments and the ecosystem being diverse and rich is very, very important and as part of our integrations with the controller, we're building a broad suite of integrations across threat detection application dependency mapping, Semen sore develops infrastructure as code tools like ants, Poland to answer the entire form. Um, it's clear if you look at these categories of integrations, you know XDR or threat detection requires full telemetry from within the data center. It's been hard to accomplish to date because you typically need agents on, on your compute nodes to give you the visibility into what's going on or firewalls for east west flaws. Now our platform can natively provide full visibility in dolphins, East west in the data center and this can become the source of telemetry truth that these Ml XT or engines required to work. The other aspects of ecosystem are around application dependency mapping the single core challenge with deploying segmentation. East West is understanding the rules to put in place right first, is how do you insert the service uh service device in such a way that it won't add more complexity. We don't add any complexity because we're in line natively. How do we understand that allow you to build the rules are necessary to do segmentation. We integrate with tools like guard corps, we provide our flow logs a source of data and they can provide rural recommendations and policy recommendations for customers around. We're building integrations around steve and soar with tools like Splunk and elastic elastic search that will allow net hops and sec ops teams to visualize, train and manage the services delivered by the C X 10-K. And the other aspect of ecosystem from a security standpoint is clearly how do I get policy from these traditional appliances and enforce them on this next generation architecture that you've built that can enable state health services. So we're building integrations with tools like toughen analgesic third party sources of policy that we can ingest and enforcing the infrastructure allowing you to gradually migrate to this new architecture over time >>it's really a cloud native switch, you solve people's problems pain points but yet positioned for growth. I mean it sounds that's my takeaway. But I gotta ask you guys both what's the takeaway for the customers because it's not that simple for that. We have a complicated >>Environment. I think, I think it's really simple every 10 years or so. We see major evolutions in the data center in the switching environment. We do believe we've created a new category with the distributed services, distributed services, switch, delivering cloud scale distribute services where the local where the workloads were side greatly simplifying network security provisions and operations with the Yoruba fabric composer while improving security posture and the TCO. But that's not all folks. It's a journey. Right. >>Yeah, it's absolutely a journey. And this is the first step in in a long journey with a great partner like Aruba, there's other platforms, 100 or four gig hardware platforms we're looking at and then there's additional services that we can enable over time allowing customers to drive even more Tco value out of the platform and the architectural services like encryption for securing the cloud on ramp services like state for load balancing to deploy east west in the data center and you know, holistically that's that's the goal, deliver value for customers and we believe we have an architecture and a platform and this is the first step in a long journey. It's >>a great way. I just ask one final final question for both of you. As product leaders, you've got to be excited having a category creation product here in this market, this big wave. What's what's your thoughts? >>Yeah, exactly. Right. It doesn't happen that often. And so we're all in, it's it's exciting to be able to work with a great team like Sandu and chain here. And so we're really excited about this launch. >>Yeah, it's awesome. The team is great. It's a great partnership between and santo and Aruba and you know, we we look forward to delivering value for john customers. >>Thank you both for sharing under the hood and more details on the product. Thanks for coming on. >>Thank you. Okay, >>the next evolution of switching, I'm john furrier here with the power of An HP, Aruba and Pensando, changing the game the way customers scale up in the cloud and networking. Thanks for watching. Mhm.

>>From the cube studios in Palo Alto, in Boston, connecting with thought leaders all around the world. This is a cute conversation. Hi, welcome back. I'm Stu middleman. And this is a cube conversation digging in with, talking about what they're doing to help people. Yeah. Really bringing some of the networking ideals to cloud native environment, both know in the cloud, in the data centers program, Krishna penny. He is the vice president of software. Thanks so much for joining us. Thank you so much for talking to me. Alright, so, so Krishna the pin Sandow team, uh, you know, very well known in the industry three, uh, you innovation. Yeah. Especially in the networking world. Give us a little bit about your background specifically, uh, how long you've been part of this team and, uh, you know, but, uh, you know, you and the team, you know? Yeah. >>And Sando. Yup. Um, so, uh, I'm VP of software in Sandow, um, before Penn Sarno, before founding concern, though, I worked in a few startups in CME networks, uh, newer systems and Greenfield networks, all those three startups have been acquired by Cisco. Um, um, my recent role before this, uh, uh, this, this company was a, it was VP of engineering and Cisco, uh, I was responsible for a product called ACA, which is course flagship SDN tonic. Mmm. So I mean, when, why did we find a phone, uh, Ben Sandoz? So when we were looking at the industry, uh, the last, uh, a few years, right? The few trends that are becoming clear. So obviously we have a lot of enterprise background. We were watching, you know, ECA being deployed in the enterprise data centers. One sore point for customers from operational point of view was installing service devices, network appliances, or storage appliances. >>So not only the operational complexity that this device is bringing, it's also, they don't give you the performance and bandwidth, uh, and PPS that you expect, but traffic, especially from East West. So that was one that was one major issue. And also, if you look at where the intelligence is going, has been, this has been the trend it's been going to the edge. The reason for that is the motors or switches or the devices in the middle. They cannot handle the scale. Yeah. I mean, the bandwidths are growing. The scale is growing. The stateful stuff is going in the network and the switches and the appliances not able to handle it. So you need something at the edge close to the application that can handle, uh, uh, this kind of, uh, services and bandwidth. And the third thing is obviously, you know, x86, okay. Even a few years back, you know, every two years, you know, you're getting more transistors. >>I mean, obviously the most lined it. And, uh, we know we know how that, that part is going. So the it's cycles are more valuable and we don't want to use them for this network services Mmm. Including SDN or firewalls or load balancer. So NBME, mutualization so looking at all these trends in the industry, you know, we thought there is a good, uh, good opportunity to do a domain specific processor for IO and build products around it. I mean, that's how we started Ben signed off. Yeah. So, so Krishna, it's always fascinating to watch. If you look at startups, they are often yeah. Okay. The time that they're in and the technologies that are available, you know, sometimes their ideas that, you know, cakes a few times and, you know, maturation of the technology and other times, you know, I'll hear teams and they're like, Oh, well we did this. >>And then, Oh, wow. There was this new innovation came out that I wish I had add that when I did this last time. So we do, a generation. Oh, wow. Talking about, you know, distributed architectures or, you know, well, over a decade spent a long time now, uh, in many ways I feel edge computing is just, you know, the latest discussion of this, but when it comes to, and you know, you've got software, uh, under, under your purview, um, what are some of the things that are available for that might not have been, you know, in your toolkit, you know, five years ago. Yeah. So the growth of open source software has been very helpful for us because we baked scale-out microservices. This controller, like the last time I don't, when we were building that, you know, we had to build our own consensus algorithm. >>We had to build our own dishwasher database for metrics and humans and logs. So right now, uh, we, I mean, we have, because of open source thing, we leverage CD elastic influx in all this open source technologies that you hear, uh, uh, since we want to leverage the Kubernetes ecosystem. No, that helped us a lot at the same time, if you think about it. Right. But even the software, which is not open source, close source thing, I'm maturing. Um, I mean, if you talk about SDN, you know, seven APS bank, it was like, you know, the end versions of doing off SDN, but now the industry standard is an ADPN, um, which is one of the core pieces of what we do we do as Dean solution with DVA. Um, so, you know, it's more of, you know, the industry's coming to a place where, you know, these are the standards and this is open source software that you could leverage and quickly innovate compared to building all of this from scratch, which will be a big effort for us stocked up, uh, to succeed and build it in time for your customer success. >>Yeah. And Krishna, I, you know, you talk about open forum, not only in the software, the hardware standards. Okay. Think about things, the open compute or the proliferation of, you know, GPS and, uh, everything along that, how was that impact? I did. So, I mean, it's a good thing you're talking about. For example, we were, we are looking in the future and OCP card, but I do know it's a good thing that SEP card goes into a HP server. It goes into a Dell software. Um, so pretty much, you know, we, we want to, I mean, see our goal is to enable this platform, uh, that what we built in, you know, all the use cases that customer could think of. Right. So in that way, hardware, standardization is a good thing for the industry. Um, and then same thing, if you go in how we program the AC, you know, we at about standards of this people, programming, it's an industry consortium led by a few people. >>Um, we want to make sure that, you know, we follow the standards for the customer who's coming in, uh, who wants to program it., it's good to have a standards based thing rather than doing something completely proprietary at the same time you're enabling innovations. And then those innovations here to push it back to the open source. That's what we trying to do with before. Yeah. Excellent. I've had some, some real good conversations about before. Um, and, and the way, uh, and Tondo is, is leveraging that, that may be a little bit differently. You know, you talk about standards and open source, oftentimes it's like, well, is there a differentiator there, there are certain parts of the ecosystem that you say, well, kind of been commodified. Mmm. Obviously you're taking a lot of different technologies, putting them together, uh, help, help share the uniqueness. Okay. And Tondo what differentiates, what you're doing from what was available in the market or that I couldn't just cobbled together, uh, you know, a bunch of open source hardware and software together. >>Yeah. I mean, if you look at a technologist, I think the networking that both of us are very familiar with that. If you want to build an SDN solution, or you can take a, well yes. Or you can use exhibit six and, you know, take some much in Silicon and cobble it together. But the problem is you will not get the performance and bandwidth that you're looking for. Okay. So let's say, you know, uh, if you want a high PPS solution or you want a high CPS solution, because the number of connections are going for your IOT use case or Fiji use case, right. If you, uh, to get that with an open source thing, without any assist, uh, from a domain specific processor, your performance will be low. So that is the, I mean, that's once an enterprise in the cloud use case state, as you know, you're trying to pack as many BMCs containers in one set of word, because, you know, you get charged. >>I mean, the customer, uh, the other customers make money based on that. Right? So you want to offload all of those things into a domain specific processor that what we've built, which we call the TSC, which will, um, which we'll, you know, do all the services at pretty much no cost to accept a six. I mean, it's to six, you'll be using zero cycles, a photo doing, you know, features like security groups or VPCs, or VPN, uh, or encryption or storage virtualization. Right. That's where that value comes in. I mean, if you count the TCO model using bunch of x86 codes or in a bunch of arm or AMD codes compared to what we do. Mmm. A TCO model works out great for our customers. I mean, that's why, you know, there's so much interest in a product. Excellent. I'm proud of you. Glad you brought up customers, Christina. >>One of the challenges I have seen over the years with networking is it tends to be, you know, a completely separate language that we speak there, you know, a lot of acronyms and protocols and, uh, you know, not necessarily passable to people outside of the silo of networking. I think back then, you know, SDN, uh, you know, people on the outside would be like, that stands for still does nothing, right? Like networking, uh, you know, mumbo jumbo there for people outside of networking. You know what I think about, you know, if I was going to the C suite of an enterprise customer, um, they don't necessarily care about those networking protocols. They care about the, you know, the business results and the product Liberty. How, how do you help explain what pen Sandow does to those that aren't, you know, steeped in the network, because the way I look at it, right? >>What is customer looking? But yeah, you're writing who doesn't need, what in cap you use customer is looking for is operational simplicity. And then he wants looking for security. They, it, you know, and if you look at it sometimes, you know, both like in orthogonal, if you make it very highly secure, but you make it like and does an operational procedure before you deploy a workload that doesn't work for the customer because in operational complexity increases tremendously. Right? So it, we are coming in, um, is that we want to simplify this for the customer. You know, this is a very simple way to deploy policies. There's a simple way to deploy your networking infrastructure. And in the way we do it is we don't care what your physical network is, uh, in some sense, right? So because we are close to the server, that's a very good advantage. >>We have, we have played the policies before, even the packet leaves the center, right? So in that way, he knows his fully secure environment and we, and you don't want to manage each one individually, we have this, okay, Rockwell PSM, which manages, you know, all this service from a central place. And it's easy to operationalize a fabric, whether you talk about upgrades or you talk about, you know, uh, deploying new services, it's all driven with rest API, and you can have a GUI, so you can do it a single place. And that's where, you know, a customer's value is rather than talking about, as you're talking about end caps or, you know, exactly the route to port. That is not the main thing that, I mean, they wake up every day, they wake up. Have you been thinking about it or do I have a security risk? >>And then how easy for me is to deploy new, uh, in a new services or bring up new data center. Right. Okay. Krishna, you're also spanning with your product, a few different worlds out. Yeah. You know, traditionally yeah. About, you know, an enterprise data center versus a hyperscale public cloud and ed sites, hi comes to mind very different skillset for management, you know, different types of okay. Appointments there. Mmm. You know, I understand right. You were going to, you know, play in all of those environments. So talk a little bit about that, please. How you do that and, you know, you know, where you sit in, in that overall discussion. Yes. So, I mean, a number one rule inside a company is we are driven by customers and obviously not customer success is our success. So, but given said that, right. What we try to do is that we try to build a platform that is kind of, you know, programmable obviously starting from, you know, before that we talked about earlier, but it's also from a software point of view, it's kind of plugable right. >>So when we build a software, for example, at cloud customers, and they use BSC, they use the same set of age KPI's or GSP CRS, TPS that DSC provides their controller. But when we ship the same, uh, platform, what enterprise customers, we built our own controller and we use the same DC APS. So the way we are trying to do is things is fully leverage yeah. In what we do for enterprise customers and cloud customers. Mmm. We don't try to reinvent the wheel. Uh, obviously at the same time, if you look at the highest level constructs from a network perspective, right. Uh, audience, for his perspective, what are you trying to do? You're trying to provide connectivity, but you're trying to avoid isolation and you're trying to provide security. Uh, so all these constructs we encapsulated in APA is a, which, you know, uh, in some, I, some, some mostly like cloud, like APS and those APIs are, are used, but cloud customers and enterprise customers, and the software is built in a way of it. >>Any layer is, can be removed on any layer. It can be hard, right? Because it's not interested. We don't want to be multiple different offers for different customers. Right. Then we will not scale. So the idea when we started the software architecture, is that how we make it pluggable and how will you make the program will that customer says, I don't want this piece of it. You can put them third party piece on it and still integrate, uh, at a, at a common layer with using. Yeah. Yeah. Well, you know, Krishna, you know, I have a little bit of appreciation where some of the hard work, what your team has been doing, you know, a couple of years in stealth, but, you know, really accelerating from, uh, you know, the announcement coming out of stealth, uh, at the end of 2019. Yeah. Just about half a year, your GA with a major OEM of HPE, definitely a lot of work that needs to be done. >>It brings us to, you know, what, what are you most proud about from the work that your team's doing? Uh, you know, we don't need to hear any, you know, major horror stories, but, you know, there always are some of them, you know, not holes or challenges that, uh, you know, often get hidden yeah. Behind the curtain. Okay. I mean, personally, I'm most proud of the team that we've made. Um, so, uh, you know, obviously, you know, uh, our executors have it good track record of disrupting the market multiple times, but I'm most proud of the team because the team is not just worried about that., uh, that, uh, even delegate is senior technologist and they're great leaders, but they're also worried about the customer problem, right? So it's always about, you know, getting the right mix, awfully not execution combined with technology is when you succeed, that is what I'm most proud of. >>You know, we have a team with, and Cletus running all these projects independently, um, and then releasing almost we have at least every week, if you look at all our customers, right. And then, you know, being a small company doing that is a, Hmm, it's pretty challenging in a way. But we did, we came up with methodologists where we fully believe in automation, everything is automated. And whenever we release software, we run through the full set of automation. So then we are confident that customer is getting good quality code. Uh, it's not like, you know, we cooked up something and that they should be ready and they need to upgrade to the software. That's I think that's the key part. If you want to succeed in this day and age, uh, developing the features at the velocity that you would want to develop and still support all these customers at the same time. >>Okay. Well, congratulations on that, Christian. All right. Final question. I have for you give us a little bit of guidance going forward, you know, often when we see a company out and we, you know, to try to say, Oh, well, this is what company does. You've got a very flexible architecture, lot of different types of solutions, what kind of markets or services might we be looking at a firm, uh, you know, download down the road a little ways. So I think we have a long journey. So we have a platform right now. We already, uh, I mean, we have a very baby, we are shipping. Mmm Mmm. The platforms are really shipping in a storage provider. Uh, we are integrating with the premier clouds, public clouds and, you know, enterprise market, you know, we already deployed a distributed firewall. Some of the customers divert is weird firewall. >>So, you know, uh, so if you take this platform, it can be extendable to add in all the services that you see in data centers on clubs, right. But primarily we are driven from a customer perspective and customer priority point of view. Mmm. So BMW will go is even try to add more ed services. We'll try to add more storage features. Mmm. And then we, we are also this initial interest in service provider market. What we can do for Fiji and IOT, uh, because we have the flexible platform. We have the, see, you know, how to apply this platform, this new application, that's where it probably will go into church. All right. Well, Krishna not a penny vice president of software with Ben Tondo. Thank you so much for joining us. Thank you, sir. It was great talking to you. All right. Be sure to check out the cube.net. You can find lots of interviews from Penn Sundo I'm Stu Miniman and thank you. We're watching the cute.

welcome back to vmworld live 2010 live at the cube in san francisco california Moscone Center at vmworld 2010 please welcome this morning's press conference with VM ware compelling technologies and their customers Heineken from the Netherlands speaking today our Todd is Todd Nielsen's chief operating officer of VMware Phil sore and CEO of Compellent technologies and from Heineken the Netherlands microbrews virtualization team lead lucien de konak project manager and now please welcome Todd Nielsen the chief operating officer of VMware it's a it's great to be here we'd like to welcome you to the Compellent vmware operands and i want to say a couple words about compelling technologies in our partnership with them as vmware they've been a great storage partner of ours have a number of customers together a number and we really like work with them to drive value to our overall customer the solution said the that we did announced yesterday at vmware at vm for every dollar of license revenue that vmware cells we are partners or our ecosystem is able to add on or to drag with that fifteen dollars of ecosystem revenue and the compellent folks are a great example of a partnership with vmware where our solutions work well together and we do some exciting things we're going to hear from for the president and CEO of compellent and one of their customers but before we do one of my favorites twist of this press conference is a differentiation of compellent is the fluid data architecture and I think it's somewhat ironic after last night's beer crawls at vmworld 2010 that Heineken happens to be the customer on stage so I'm sure there's a story there and I would like to introduce Phil Soren the president and CEO of compellent to tell us about the company and about the Heineken beer crawls great Todd thanks a lot we're just thrilled to be up here on stage with you being participated in the fantastic show you have in operation here at moscone in San Francisco and we're thrilled to have a joint announcement our customer heineken here and to have them for from the Netherlands to share the excitement with us but let me tell you a little about Compellent we're a data storage company with the fluid data architecture we've been really the innovator if you look at primary storage innovation over the last decade things like thin provisioning sub lund automated tiered storage tiering disk platters flexible volumes portable volumes then provision you look at all those types of innovations over the last decade that storages come out and compellent has been the leader in that whole space and I think we'd be able to get ahead of some of the incumbent vendors with our innovation and we're in really fast growing we grew about thirty eight percent year-over-year last year we're the one of the fastest growing sandbenders in the world and we're hoping to keep that growing about 2,100 customers in 34 countries Heineken being a good example in the Netherlands of those customers there they're running their mission-critical enterprise applications on us for their worldwide operations and I would say of the 2100 about 2090 of them are also running some form of VMware so this partnership with vmware is very very important to us and we're real excited about it talk a little bit about our patented technology we call it the fluid data architecture and we thought no better customer to do a joint press conference with on our fluid data architecture than Heineken so the ultimate fluid data architecture is the combination of heineken and compellent and our system is so easy to use that you can actually enjoy a Heineken while you're about storage administrator so we like that they're so Heineken Nell lenders are our customer we have microbrews in Lushan nakonec and we're real excited to hear about their story they're part of a global enterprise of customers we talked about we have customers in all industries verticals geographic areas we're announcing actually this week we're announcing our expansion of our Australian operations where we have dozens of customers already but we're now seeing the expanse of our Australian operations and now let's take it back to the Netherlands and let's hear a real customer story about how vmware Compellent can really cut the the total cost of ownership in a data center by more than fifty percent with the combination of our two efforts and also improve the operational efficiency of those data centers and let's hear Mike and Lucien to tell us a little bit about it okay thank you very much feel I guess I don't have to introduce any cancer company itself because we all know with the core business or for companies brewing beer not only the beer we grade to brew great beers and great brands and that makes us the number one brewer in Europe and the number three in volume in the complete worldwide we have over 200 regional and local beers and ciders in total and when we look at our breweries we have almost in every country we have a brewery or its Hank is deliverable when we look at the International Anakin international we're very large company almost in every country as I just said before and we have 130 140 breweries in more than 70 countries which is good for a group beer volume of 200 million hectoliters of beer a year as includes insiders when we look at the the Netherlands we have only three breweries that's where it all started we have 18 million hectoliters of total supply but we're not drinking at all ourselves the domestic market is only about five million hectoliters and the rest of the volume is going to USA so as all export for us and that's where all your beers coming from and I strategies that we've introduced a Heineken Light several years ago is especially made for the USA market because we don't drink it okay when we take a look at the virtualization roadmap for hanukkah we started about six years ago in 2004 VMware was the only real player in the market at the moment we introduced it when we were consolidating our data centers in our main location suit about we came from about 12 server rooms to one major data center which we used storage from HP at the moment and we used HP blades infrastructure and we decided to go for it with VMware for our DTI environments or the test and acceptance environment after several years it we grew outgrew our storage capacity and we needed to upgrade so we we change te va with a forklift upgrade some to another EPA and we also introduced a new version of vmware again we're later we thought everybody was ready to go to use protection so everyone used the dta and i was confident it should work on production also so we start with the bronze service that our servers are not mission critical for us those are great success and last year we start a new project to virtualize every gold and silver system we have that means every mission critical and priority system we use for brewing packaging and distribution just the latest news is that last weekend we migrated one of the last warehouse management systems there's also virtualized now and is running perfectly where are we going we are looking at the end of the year we're going to vsphere for of course the main thing and last year we decided to choose for another storage storage solution we chose component well this is something where elution comes in you can tell about the choice you ate and why we did it okay thank you well well tell you something about the project itself the migration and why we choose component in the first place well we really needed to look for other solutions because especially in the two main sites suta wild and divorce we had some serious problems especially the support costs because after three years you pay an enormous amount of money for support from HB also we had our capacity problems and also experienced severe performance issues in suit about us so that meant that we had to take action fast also we had we were stuck on the AEV a 5000 which didn't allow us to upgrade to a newer version of vmware and also we couldn't use windows server 2008 which was very high on us on our priority list furthermore business continuity is on a plan for early next year so we wanted to have a solution which could provide us that and also because heineken is as called a new but it's not really a project but Sequoia the hunt for cash within itn Anakin element meant that we we want to you reduce IT costs as much as possible so in another point problem was that we had a major issue with reporting from our currents and infrastructure why did you choose for component well it opera it operates with every operating system it is very very important it's one for the solution that fits really everything that's what we experience as well during the migration we could start with replication early next year that's also very important and we needed a high high performance solution but it eventually meant why we choose chose for a component that it's excellent value for money the fluid data concept we really was consecrated what we can can use and give us high flexibility and one of the major pros is that the accident reporting facilities is I've never seen a better reporting functionality inside a project such as propellant and what is also very important that we got 24 7 proactive support and that's something you will never get for free so okay well as a result we have at least certain sixty percent virtualized and actually like my except last week we went to 61 percent because we virtualize to more FM machines and the speed we are going now it it really looks that we are in 2012 we are going to for ninety percent and I think it's a really feasible the number of disks we significantly reduced which meant lowers I decided lower on the power lower on low on the rec space for example the evi 5000 cost us one and a half 19-inch rack and right now it's about 12 views so it's a real big difference the performance we see on all layers not only on the only windows servers also on ax systems we see an enormous improvement regarding performance with yet we did have to do some optimization but with the support of copilot in the in the last month we had a excellent result and we even have a much better performance that we ever had so and because yeah we are finally using solar state drives because we really needed that for a sequel a reporting server which is very business critical and indio on the old evi we reached performance for about twenty thirty five minutes for a report which needed to be ready before a certain time and now we even cut times under 20 minutes so you see how fast it really is so we are next week actually the final and virtual machine will be migrated from the OTV a two component and that will finalize our migration on both breweries and so far no disruption whatsoever so we're very pleased perfect so that's a that's our part of the presentation thank you somebody talks out of the sky now right any questions uh well the question the question was with all the savings he's gotten his data center can you lower the cost of heineken beer for everyone I knew a new kind of heineken light right yeah how we go do that let us not up to me we really want to thank you guys for sharing that story I mean it just hit all our bullets about you know the future built in performance flexibility fluid data VMware compellent working together and we're just really really excited and we appreciate you sharing your story with our viewers and our customers and our prospects out in the audience here okay thank you guys yeah okay