 What's going on? What's going on? Karim Abdullah is here. He's an IT practitioner with Sprint. Karim and I first met down in New York City in April. Karim, welcome to the liveCube. Thanks, Dave. Good to be back. What brought SVC to Sprint originally? What was the motivation? What was the driver there? Strictly a cost and an end of life issue. We had an end of life approaching on all of our existing storage arrays. So over the last three, three and a half to four years, we've gotten rid of over a hundred storage arrays simply by installing a virtualization platform and then redeploying or deploying newer platforms behind the virtualization. And as we roll the virtualization platform up, we roll the end of life devices off. We're reducing operations costs, managing some capital expense in lieu of some long-term high overhead. And are you able to do that migration non-disruptively? Today we are. Today we are fully utilizing SVC at lower cost and at no cost, whereas comparatively it would have been a very expensive proposition years ago. In the early days of SVC, people would say, well, you're only going to put, you know, your sort of your crapplications behind the SVC. You're not going to put your tier one storage behind SVC, but you actually have a VMAX running behind your SVC. Is that correct? Yeah. Our SVC installation now have four tiers of storage from tier zero to tier three, and tier zero is the new flash system, whereas tier one is your traditional high-end DMX or VMAX. Tier two and three are your SATA and or your Clarion and or some XIV. So we've got four tiers of storage, and the whole SVC has reduced the number of interventions a person has to make to manage the storage, and that's what's making it unbelievably easy in terms of being able to allocate and provision and carve out storage based on performance needs, application needs and tiering needs. So for us, for us using flash system was really just dropping a block of storage as a new item or a new node within an SVC infrastructure. Now do you do charge backs at Sprint? We don't, but we're working on it. You are. Okay. Do you do any kind of showback? That's where we are now. We're trying to demonstrate where it is, a showback for certain deployments as part of a budgetary practice for costs of projects. So obviously different tiers have different costs associated with them. Do you see, we talked about this in New York, and I'm going to ask you again, because I think your answer caused you to rethink it. So do you see those tiers, those four tiers collapsing over time? Do you see them maintaining? Have you thought about that anymore? Maybe the four tiers reducing down to three from where we are today, but having flash system replaced tier one, I don't see it really occurring near term. It may over a period of time. And one of the reasons is the price point, right? So now we're looking at price point for iOS versus price point for Gig. I want to ask you about your SDN strategies before I do. So we talked to Eric Eiberg about the 100 microsecond overhead in the flash systems that SVC injects. And I mean, it's a virtualization layer. So obviously there's overhead. Was that a concern to you prior to going SVC? I mean, obviously you're all in on SVC, but I presume the benefits outweigh that. But can you talk about that a little bit? Yeah, the 100 millisecond was not such a big factor because we were going from an end of life comparison, right? You had one bit of comparison here that says you're extremely latent to something that was much more automatic and had the ability to grow and move faster. So the latency introduced by the overhead in the SVC was not such a challenge. When you can go to a flash system based on a 6-8 millisecond to a 200 microsecond, that's where you see real benefit of going Yang SVC. So for the most part, you ignore that 100 millisecond just from the SVC overhead.