 Today when we have conversations with any vendor or any partner, we make sure that their product supports OpenStack because if it doesn't, it doesn't fit our strategy. If there's an external provider that we want to work with, as long as they're running OpenStack, we know that we can use them. Even if they weren't initially part of the movement, they all seem to come into the movement. We're always expecting when we talk to a new vendor or an existing vendor, we're expecting them to participate equally in OpenStack and then contribute their interfaces and make their software work within the pluggable architecture of OpenStack. It helps solidify maybe the partner approach where it's not just a vendor and a customer, but when both parties are involved in making the same thing better, I think it opens it up to some stronger relationships and some better conversations. One of the primary reasons we did that, made that move, was so that we could leverage all of the tools and capabilities of all of the third-party software, open-source software that operates in that ecosystem and I can use all those tools for my internal complaints. I can leverage all this stuff. I don't have to build it myself. I don't have to go to a specific vendor. That, you know, Cloud is bigger than anyone given vendor. Therefore, it takes a platform that's open, like OpenStack, to be bigger than that because it needs to reach a cross. In the past, when an interface had been written with a specific vendor or a specific vendor's code was so integrated into our systems, it was hard to change to others, but given the pluggable architecture of OpenStack, we are now able to bring in more vendors.