 Hi, I'm Kamran Yusa from Storage Made Easy. And here I'm going to give you a brief overview of what Storage Made Easy does, what features it has. And then I'm going to show you a demo where we did integration with Swift Stack, LDAP, and Storage Made Easy for a single sign-on. So what has Storage Made Easy? We provide an appliance that you can deploy in your own data center or any hypervisor or infrastructure as a service and connect multiple different storages. Those storages, they can be Amazon S3. It can be OpenStack, Swift. It can be Google Storage. And we provide you with a unified view. You can integrate with Active Directory or LDAP, where the users, they will be logging in using Active Directory or LDAP credentials. Users, you can create shared folders. You can give permissions. We can get permissions from LDAP. And the users, they can access their files from the desktop using our native clients, or they can access them from the mobile devices. And we support all the mobile devices, be it iOS, Android, BlackBerry, or Windows phone. Then we have value-added features, where every access is audited. You can download the audits who access to a file, who updated the file, who deleted the file, and all that kind of stuff. If you want to encrypt data, you can also encrypt data at rest. You can set a key phrase, so it never leaves your appliance. And it's encrypted using AES 256-bit at rest. When you are doing file sharing, you can set up permissions and policies that how many times a user can download the file. Is it password protected? Can it be accessed from just a certain IP address? And this is the list of all the providers that we support and more. So you will see that almost all the providers that are available are storages, be they cloud storages or your internal storages, like SIF, Sand, or NAS. You can all combine them together and give a unified view to the users. And the end user, that's the view he will be seeing. That's just a web browser, but he will be seeing the same view in his Windows Explorer as a drive or in Finder on OS. Or he can mount those folders on Linux also. So the users, they can access those files using multiple channels, so file manager, mobile tablets, and native desktop tools. We also integrate with Apache Solar. So all the content, if it's an open stack, it can be the content that can be indexed. And the users, they can do a search on those contents. Or they can also add meta tags that can also be searched. OK, so I've gone through that quickly. So now I'm going to move to the demo. Let's close this. So here, for open stack Swift, I am using Swift Stack. And the reason I'm using Swift Stack is that it's much easier to deploy. And it provides you with a few middlewares that you can use. It's just one click deployment. And two of the middlewares that I want to mention that we have integrated with is, one is that Swift Stack provides you with an LDAP, just like Keystone or SWR, it provides you with the middleware to do the authentication against LDAP. So here I have set up my LDAP server. I've given the search DN and all that kind of stuff. Now, another middleware that I want to mention is Swift Undelete. And we have tightly integrated with Swift Undelete also, the Swift Undelete middleware. Whenever a user deletes any file, that file will not be deleted on Swift. But it will be put into a separate container where only the admin, he can delete that file. So if you want to recover the file, you can recover that file. And it's pretty configurable. You can set up that, OK, after how much time the deleted file will stay in Swift. Now, I will move to Storage Made Easy. And in Storage Made Easy, just like Swift, you can also add multiple authentication systems. So here, I've added the same LDAP server, from which I can import different users, and they will be authenticated against LDAP. And also, we have done tighter integration with the Swift stack. So you can specify that, OK, whenever a user logs in, I want to do auto-provisioning rather than for the administrator to go to Swift, create an account for him, and he logs in. So here, what we are saying is that whenever a user logs into SME, that's the authentication URL. Go to that URL. I want to use native OpenStack versioning. So whenever a new file is uploaded, keep the old versions up to a certain point, which we manage. We are also saying that whenever a file is deleted, don't delete it, put it into a separate container, which is, again, managed by the undelete middleware. And also create a container and just some bookkeeping stuff, that what should be the container called, and what should be the user login. Now, I can go to the users, and I'll say that, OK, I want to import some users. I'll just do tools, Tokyo. And here, I'm querying, and I already created some users. So now I've queried LDAP, and I said, OK, I want to import some users. If I want to get the roles from LDAP, I can also do that, or I can do that automatically. Now, I'll just import one user, OK? So the user is imported. And everything I'm showing here, it can be done through the API. So if you want to automate the provisioning, you have a provisioning system. You can use the API and import the user using the APIs. So it's all automatic. You don't have to use the user interface. Now, the user I imported was OS Tokyo 1. So now if I sign in, it's waiting, OK? So now, if I go to the file manager, I should automatically see that a container is created for him, which is his home directory. And he can start using the system. So that's what we configured that home and call his home directory by his username. Now, I will log into the switch stack. They provide a nice user interface where you can see the containers for different users. Oh, yes. OK. So here, we have created the containers for him. And now through SME, I will just drop a file and a screenshot. So it's getting uploaded there. And we should see the same files here. Here we go. But this is more a dwell per friendly user interface. But with SME, now the user, he can create shared folders. He can do all his kind of anything he wants to do. But that's not the only access mechanism. Now here, if I go to Windows, again, the same user, Tokyo, and this is Windows, I can log in. So it's going to Active Directory or logging in the user. He can see all his files here. And now, if I go to Explorer, again, he can just work with open stack just like you're working with your shared or mounted drives. Then again, as I mentioned, we also provide for all the mobile devices, clients. That's Android, but I'm just running it in a simulator. Let me just refresh this. OK. Unfortunately, I have to refresh it just to get it quickly. So on Android also, you can access. So what we have done is, using SME as the gateway, we are using LDAP as a common authentication mechanism that storage mid-easy appliance storage mid-easy uses. And also, open stack uses, open stack Swift. We are passing the authentication to open stack Swift and then accessing the storage and doing automatic provisioning also. And you can also access from all the, for business users, they can do sharing. You can create shared folders, do the groups that will map to SME roles, give them permissions, read-write permissions. So we just make it more business-friendly and accessible through multiple channels. And also, make it easy to use with fully-ordered controls. So I think I'll finish quite quickly if anyone has any questions or anything. Any questions? All right, guys, thank you.