>>Portability implies inoperability; I mean I can only run that workload wherever it is. Doesn't that mean that your choice of internal virtualization dictates which external services you can use? And also, you know, things like the Amazon machine image, which is format proprietary to Amazon, mapping that to something in the enterprise is obviously a challenge for portability. How does portability and inoperability and the choice of in-house virtualization technology affect your ability to go to market and interposing?
>>Yeah, simple, that's a perfect, it's a fabulous question and I knew you would like this. Well, I work with Steve Hurd's team at VM we're on a standard which has become this thing called OVF. It's a DMTF standard and it's a packagings format which allows you to package multiple tiers of an application, all the networks virtualization, all the configuration and allow localization , a bunch of other things and essentially make your workloads independent of a particular binding to a particular hypervisor, that has now become a standard of the DMTF. And it was through recognition, I believe, at VM Wear as well on our part, Microsoft now has adopted this, that virtualization is a mandate for everybody and that nobody is served by proprietary vertically integrated stacks and that we have to provide a mechanism for workloads to be portable. So OVF is becoming a big deal. It allows you to package a whole App with all its configuration and move its whole mass to some other place and have it correctly instantiated correctly and configured and correctly localized even. And OVF's in its, it's in a 1.1 state now and moving forward very well, so I think that that is, that concern around portability will be addressed, the vendors know that they've got to do this and nobody is served by vastians of non- portability.
>>For Randy, your job is to receive whatever people are porting to you, do you guys have to support lots of different environments to support your customers, or?
>>Randy: Yeah, it's something that comes up in, I mean I think people are afraid of lock-in and they're not interested in proprietaries, they want something more open. I don't know that when they move to the service provider that they ever necessarily will bring it back, but they just want to have the choice, so it's something that we do address in the pre-sales process and it's something that we work and the OVF standards is something that we will support and we want to make it, today its difficult, at some level, to move things seems seamlessly, but we're working, the technology's improving and they, it makes it more portable and I think we'll see a time in the probably in this calendar year where it's easy to move workloads from internal to external Clouds using software as the mechanism.
>>What takes the most; I mean you said it was difficult, what are the things that are the biggest pain to move something into your Cloud environment?
>>Randy: Well, in our particular instance, it's mainly around networking, right? Its changing of IP addresses, it's you know, so and registering and so I think those are some of the things that we've got to do when you move a workload, but the other thing that we, in our particular instance, we do have to manually move the workloads and I think there's technologies just around the corner that will make that a little bit more seamless.
>>In general, I think if you look at, his expertise in the audience which surpasses mine, but generally if you think about how you get an application up and running today, there's an extraordinary networks specific function that has to be present; IBS's, IPS's, load balances, firewalls, PCI compliance, just go. There's a ton of this stuff and in general I would say the first generation of infrastructures of service models have been weak. Specifically in the networking region, there are other issues in storage. So virtualized computing is easy. Inaudible to hypervise, there are a ton of them out there, that's no big, doing a good job of abstracting the network so that instead of just having a virtualized virtual private server model, I can have a virtual private data center, bend the virtual wires, plug them into virtual routers or whatever I want to have, is the next generation of technology evolution that the vendors have got to focus on.
==== Transcribed by Automatic Sync Technologies ====
