 because that's what I do. So first of all, welcome to all of you. I know we still have some people coming in. Can I just say I am really impressed that any of you are still awake at this point? Yes, let's give yourselves a hand. Yes, including them. I know that I am at point one completely wiped out. But we're going to talk about, we're going to talk about OpenStack and the internet of things because it's just something that we really can't ignore. I'm sure if IoT is your thing, you've probably been to other sessions this week. And it's, yeah, we've got to pay attention. So without further ado, let me introduce my esteemed panelists here who are not sitting in the order in which they are on this slide. So we'll just kind of work our way down. I'm going to ask them to introduce themselves and tell us who they are and what they do and for whom. And I'm Nick Jaysson, one of them. Hi, I'm Nick Yacosta with Disco, also a co-host of OSPod and OpenStack. OpenStack, and I am an OpenStack around OSPod. Thank you. Hi, I'm Aleksandar Adamov from Durantis. I'm a particular researcher, and I've been working for a while in antivirus industry. I'm from IBM, and I'm the first go for IBM Watson, IoT engineering. We are with that one. Kumutini Ratnam Singham, I work for Julipa Network, task software engineer. I am on the product side at the people marketing side. And I'm also an active member in OpenStack. Hi, my name is Sean Towns. I'm mostly working in UConn and QA project with an OpenStack. But I also do a lot of work with Chase, writing OpenStack guides, which is the architecture guide. Lots of guides. Lots of guides. We all know how many guides OpenStack needs. So we try and write as many of them as we can. All right, so let's talk a little bit about what we're going to talk about today. So as you can see here, we're going to talk about OpenStack and the Internet of Things and how they relate together and whether we're just piggybacking on a hot term spoiler alert. No, we're not. So we're going to talk about where we are and where we're going and why it's important. And before we worry about Skynet coming and Terminator destroying all of us, we have some more basic concepts. And then we'll look at, OK, so that's great. What do we already have? And what does the OpenStack community need to be thinking about and putting together in order for us to be able to make this a reality? So this here is a survey that I took off the Internet. I'm not really going to go through all this data. My whole point of this data is, boy, there's a lot of people talking about this. And there's really, really a good reason. So I'm going to hand off to our panelists here to talk about kind of where we are now and why this is all important. And I cheated and wrote down my stats because I'm not smart enough to remember them. I'm going to go ahead and blame the party the other night as well as all the barbecue I've consumed this week. So in 2008, there were already more things connected to the Internet than people, which is crazy. More things connected to the Internet than people. By 2019, companies are going to ship 1.9 billion connected home devices. And you're looking at just a tremendous market opportunity. By 2025, the global worth of IoT technology could be as much as $6.2 trillion. So if you hear big companies hopping on the IoT bandwagon, this is why. It's a tremendous market opportunity. And of course, all of these things need infrastructure to run on. And OpenStack, obviously, is a key technology in terms of cloud computing. And one that a lot of companies are looking at to power this sort of wave of digitization. Yeah, just to add what Nikki just shared, you said there's more devices connected than human beings. Exactly. We have 10 billion devices connected to the Internet today. And we expect that number go up to 30 billion by 2020. So really, Internet of Things is just a digital type, the physical world we are in. Wow. In my opinion, I think in about 20, 30 years from now, we are going to look back and look at our lives and say we were living inefficient life. IoT and OpenStack are going to bring a lot of efficiency to our lives and to our business models. A lot of from the data, the massive amount of data, we extract valuable information. From that, the businesses and even household lives, we are going to make a smart decision and make our life more efficient. That's why we need IoT. And for instance, in Juniper Networks, we are co-innovating with our customers and partners to build the right infrastructure to scale and to secure, automate the network with our partners so that we can provide high-performance scalable networks, which is agile. And also, we have advanced powerful analytics technologies and tools that we are partnering with our customers and partners so that our partners and customers can take full advantage of IoT or what is possible with IoT. Excellent. Thank you. Do we have any more comments on this? Okay. So let me just kind of hop back up here. Have I mentioned that this is the fourth day of the summit and I'm exhausted and didn't plug in my computer? So, yeah. So if you can see here, this is a shot that actually comes from Cisco. These are all the different... This is an example of the sort of different systems that have to be handled in a world where everything is, you know, internet-ified. Thank you very much. So let's talk about kind of some of these things that we should be worried about. I think the major concern is security. We've heard a lot of posts and notifications in media. When ethical hackers, white-haired guys, they investigated the security of Internet of Things. They hacked smart cities, smart homes, medical devices. Recently, my colleague passed from Kaspersky Lab. He posted research on how he hacked a hospital. So he managed to get access to a magnetically-announced imaging device, MRI, and he penetrated through the local Wi-Fi network and was able to access the storage where these funny pictures with brain and bones are stored. So that showed Internet of Things devices and the infrastructure are exposed to the threats, to the all-known threats like spoofing, tempering, denial of service, elevation of privileges, and repudiation. Let me just ask a question. So does that mean if I have my thermostat on the Internet that I should be worried about the rest of my stuff? Yeah, I should be worried that you can die of waiting. Or freeze, yes. I agree with Alex. Security is definitely what we see top, or number one, concerns our client have. So it is very important to have the basic security building in Internet of Things like authentication, authorization, access control. But I want to push that a little bit further. No matter how good your system is, there are still risks to be attacked. Let's just face it. So it is extremely important to have risk management. That means be able to detect the anomaly and send an alert for your client, give them the time to respond before damage is done. So in my opinion, I think the data that we collect, who owns the data? Let's say we have businesses and we collect the data. It goes to the data collection center to get analyzed and to extract valuable data information from that. But it has to pass different points, so it opens up hackers to hack in and take the information. So the main objective here is there could be, like if it's a household IoT devices, we may even see small, mini data centers, just like the way we have the solar panels on our roofs. We may even install small data centers to analyze our data. But when it comes to businesses, the security, obviously, who owns the data? Whom are we sending that information to? Who is going to get handled of the data? So in Juniper, we are coming up with a lot of innovative technologies and innovative algorithms to position ourselves so that we can help our customers to take full advantage of IoT. Excellent. So let's talk for a minute here. For those of you who are not familiar with the term, Alex, tell us what is attack surface and why is this relevant? The attack surface includes actually two parts. The first part is actually endpoint devices, so like sensors, this medical device is on. And the second area is cloud infrastructure where the data are collected and processed. So from my standpoint, I think the major concern is security should be addressed to cloud infrastructure. And today we had a talk from HP Architects and they suggested security architecture that provides protection of IoT infrastructure but mostly pointing to cloud infrastructure. So they suggested using a DNF virtual network function to introduce intrusion prevention system, intrusion detection system, antiviruses in the cloud. So cloud infrastructure for IoT needs the same protection as any other kind of information system. Probably a little bit more. Even more. And the interesting thing is that I just talked to one technical manager of IoT company and he showed the management interface how they can access the database of all customers. They actually can control all IoT devices that they sell and they support. And usually chipsets of Internet of Things devices, they contain some hard-coded SSH keys. So this is done to provide ability for manufacturer, for vendor to support, to provide services to the customer. See something goes wrong so they can connect to your device, for example, IoT router, and to check what is going wrong. And this is the major concern, a huge concern because once you hack this management interface, once you get access to this cloud infrastructure, you can get access to all IoT devices and you can do cyber-spionage, you can destroy, you can even kill people. Okay, there's... It's pessimistic. I wasn't expecting that. I don't know if anybody else here was expecting that. I was not. So don't be nervous. You just told me my thermostat can kill me. What do you mean, don't be nervous? No, no, no. This is what hacker may do, right? But a robust, I would say, commercial IoT platform. Have building device management that prevents this kind of risk and the security attack. That's definitely... They should be having it. That's what you're saying. Exactly, this is a top focus. Good. Okay, so other concerns, Sean or Nikki, do you want to talk about the other concerns that we should have? Yeah, I think, you know, it comes in things like self-driving cars, airplanes, transportation vehicles. It's literally a matter of life and death where a bad decision can create havoc for yourself or those around you or your family. This is definitely scary. I bought a Honda recently, I love my Hondas, and I got a newer model and it's connected now. I know it's connected because I'm supposed to get an oil change every 6,000 to 8,000 miles or something crazy. But now, when I'm getting close, as soon as that early warning light comes in, literally that day I get an email saying, hey, you're due for an oil change. Here's a coupon. And I'm like, man, what else do they know? I mean, they probably know where I'm driving. They probably know. I've got the nav in the dash. But it's really interesting to think about the companies that have this data and what they could potentially do with it or how valuable that could become. Knowing where I go, where I shop, how long I'm there. That's all interesting data that the companies need to protect as a carrier. So, setting aside the security piece for a second, let's just discuss the capacity part. Most of the world is still trying to adopt IPv6. And in order to talk to all of these devices in your customer's home, past the customer premise equipment, you need to start thinking about designing your apps around the correct networking model for the 21st century, which is IPv6. The other thing you'll have to consider is the fact that you will have so many devices, you will need to do capacity planning within your data center and start to discuss not necessarily the density of, so perhaps your hypervisors and the number of virtual machines that are running on each hypervisor, but also perhaps from the other side of the equation determining how many IoT devices you'll be establishing sessions with these virtual machines or whatever your control plane is. So, you'll almost be pressed up against two different types of concerns, which is the density of your hypervisor and then also the density of all the devices that are connected to that to ensure for disaster recovery purposes, the amount of bandwidth that you'll be consuming out of a single data center or even a single compute unit. That's those types of things. And then you also have to build your applications to also conserve the amount of data that is being transmitted among very large and expensive paths. This is why he writes guides because he thinks about the actual practical things. So, yes. Thank you. Thank you. Okay. So, let's talk about kind of where we are right now. We are going to save a bunch of time for questions, so don't worry about that. Well, Sean, tell us a little bit about where we are on IPv6 and then we'll kind of move on from there. Sure. So, within OpenStack in the neutron community, there was a team that was built from a diverse number of companies which has prepared OpenStack to be IPv6 enabled. That work was done a couple years ago, so we find ourselves in a nice position here that as the interest from the application developers and the device manufacturers get ready for the IoT paradigm, we're in a good position where we've already done the majority of the legwork for that to then occur. The orchestration piece as well within the OpenStack community and all the tools that we have floating around to do application development, such as the first application guide. I'm always on message. And then I'm going to hand it off to somebody to discuss more of the big data piece. Yeah, sure. So, we talk about there are lots of devices in the magnitude of billions of devices. Think about all the data could come from those devices. They are both structured data, unstructured data. It's going to be huge amount of data lake. It's one thing you might want to consider. Another thing, you may not want to push every single piece of device data to the cloud. In some cases, the device is a low-power device. Cannot afford to do that from the capacity perspective. In other cases, maybe in a shipyard, it's very poor internet access. You just cannot. So, one thing to keep in mind to consider when we design all those solutions, applications for internet of things is fully leverage the analytic power on the edge or gateway. So, you don't have to, and you don't want to push every single piece of data to the cloud. Excellent. Thank you. All right. So, now let's talk about what we still need. Okay, who wants to start that one off? I think like we maintenance and upgrade, upgradability, that is very important even in OpenStack or in any apps because there is going to be 50 billion devices 2020 and also the success of IoT depends on security and how fast it can function. So, the maintenance cycles and upgradability is going to be the key for that usability point of view. Excellent. So, the other thing to discuss as the other panelists said is that there are some applications where it's not desirable to throw everything back up into the cloud or to, you know, your main expensive data center with the ability to, for IoT devices to communicate to each other with no network address translation or middle boxes that create reachability problems. There is more of an ability for these devices amongst each other. So, think of it like the way the airplane that we all flew in here, there are networking equipment on those planes for different pieces to talk to each other. So, that sort of paradigm of multiple devices talking in concert with each other over the network will probably find its way over into the consumer type of devices that are now being built and designed. Another thing I see we still need is currently Internet of Saints focus a lot on the device connectivity, device management, get data into the edge device or into the cloud. Really, the reason we want to do this is once we have all the data, have a device talk to each other, we want to analyze the data to draw some insight. So, this is the next thing I see we are going. It's focused on the analytic power of this. Now, I say IBM Watson provide some analytic power that we're building into the Internet of Saints like natural language processing, predictive analytics, cognitive analytics, et cetera. That's what we see. We will go next that can really benefit to draw the value out of the data. I have to say that the idea of cognitive computing and where it can take all this data that we're getting is, well, it's exciting to me. I don't know about anybody else, but I find it exciting. Did you have something to say? Yeah, I'd just like to point, just say safety first about scalability. If we have such a big number of IT devices and this number is growing and reaching like billions, so we need to think about scalable cloud architecture as well and to think about how we can apply security services inside of the cloud. On another note, I think we're at a point now and those of you who've been involved in OpenStack for a while are probably well aware, but there's a massive talent gap right now. Just for OpenStack knowledge and expertise, people are starting to experiment with OpenStack. Enterprises are rolling it out. They're running it in labs. They're realizing it's a lot of work. And we're talking about billions and billions of devices that are coming online. And even though it may seem simple to the consumer, there's still a huge level of knowledge and expertise that is needed to be able to build and operate these underlying platforms that are going to power all of these devices in the future. And so I think it's time now to start enabling, not only for ourselves to start learning about this stuff, but just doing research for this panel, I was like, man, I need to get with it. There's a lot I don't know about this stuff, but I think we're in a really good place as OpenStack to be able to, being a newer technology, I think we have the opportunity to start attacking this now. But I think it's going to be a while before there's going to be enough people that can run and operate these massively scalable platforms that could be a matter of life or death. Again, with the life or death. Thank you. Yes, go ahead. So regarding the analytics piece, we also, in Juniper, we realize, and we have already have tools to do predictive analysis and powerful analytics and big data analysis. So we have actually proved ourselves in the market that we are one of the leaders in the analytics part, and we are going to be well positioned to help our customers to enable IoT as success. Okay. So before we go into Q&A, did anybody have any final words they wanted to say? I assume you just had your final word. So did anybody else want to go ahead? Okay. My final word is that we defined the attack service, like endpoint devices and cloud infrastructure. So far, we've seen attacks to endpoint devices only by ethical hackers, so the value of the attack is quite high. I mean, you need to spend a lot of effort, but the benefit of it is quite low. I think it's just mostly driven by scientists, by researchers. But information assets available in clouds are much more valuable, and that's why we need to think, invest more money to secure cloud infrastructure. And I think such technology like OpenStack NFV, so this will enable to provide scalable security services. Anybody? Go on once. Go on twice. Okay. Questions? Anybody have any questions? There are mics here and here. A couple of takers, so let's give it a minute. Have you guys thought about what could be the business models for this? I mean, some of them is very useful for anyone, like the traffic on the freeways and where the cars are, so that's obvious. But others, which is more personal, like your experience in consumer doesn't want to participate or wants to participate, how the business model can evolve on this? I think what we're starting to see, and it's interesting because I bought the Philippu light bulbs, and I was actually kind of surprised when I powered these things up and I realized that there was no subscription for it. I was like, wow, they're missing a huge opportunity because I would have paid extra money to have all this stuff work better. But if you look at Nest thermostats or you buy it kind of one time and then you're kind of good, the Nest Cam is interesting because you buy the Nest Cam, they give you a free trial to record your data for a period of 10 days. And at the end of the month, they say, the subscription ran out. If you want us to keep showing you 10 days worth of history, you need to subscribe. And so I'm starting to see the subscription model, the Netflix model kind of infiltrating these new platforms, which is great because a one time purchase to run something for possibly years, I don't think it's sustainable. If you are creating these innovative technologies and you're constantly adding new features, that requires teams of people to keep it up and running and going and new features to be rolled out. And so I'm starting to see the subscription model. Maybe the devices get cheaper in terms of the hardware, but you're going to pay in perpetuity. So I definitely see that shift. It's like the whole CapEx versus OpEx discussion for businesses. It's definitely starting to make its way into at least consumer grade Internet of Things devices. Yeah, I can give you another example that I can see industry solution build upon Internet of Things. For example, with weather data and your current location data, we can build a solution for insurance. Based on your location and the current weather condition, give you advice. Should you stay here or should you get to the next mall or coffee shop, park your car in the garage, you can avoid the hail storm or things like that. If you take those advice, can lower your insurance premium. That's just an example of industry solution. Excellent. Thank you. Another one that I've seen, which is kind of interesting is the farming industry. And you think about, you know, farming industry as kind of being maybe one that's not, you know, something you think of being sort of on the cutting edge of technology. But even as early as, I think it was about four years ago, there was a big, I'll say, farming manufacturing equipment maker that we spoke to who was evaluating OpenStack. And the reason being is because they had these devices that were spread out all over the United States in really rural areas. And so they wanted to make sure that they knew, A, where these devices were, where they were being used, and B, they wanted to know the health of these devices because if these devices were starting to fail or requiring maintenance, it created a new sales opportunity, maintenance opportunities, opportunities to make more money. And so you think of farming, they've got, you know, drones now that can fly over fields and take real-time video and photographs, and they've got sensors in the soil to make sure that all the pH levels are right. They've got lighting systems inside greenhouses that when there's natural light up, they'll turn those lights down as that natural light starts to wane or if the weather is really bad, they'll actually turn on these lights at a certain level to mimic the sun. So you think about, you know, farming as, you know, kind of an old-school industry, but it's definitely one industry where we're starting to see a bunch of solutions for IoT going in. Let me just say something about farming. When your entire yearly income is based on, like, what you get out of a three-month period, it is important for you to make sure that everything goes the way that it should. So there you go. Just one comment. We have this solution in production in Europe today. It's like shameless plug day while you're at it. Cisco acquired this company called Jasper, and they do cool stuff like that, too. What do you got, Morantis? We got this panel. We have an open stack that works. Ding! I wanted to quickly touch upon the healthcare industry. We already have, you know, my doctor devices kind of at home checking out blood pressure and sugar and all that. In that industry, I see a tremendous growth in that industry. And cities, lots of cities. Smart cities, which we'll save XP from having to plug. IBM Smart Cities. Let me just, we're going to do your questions in, like, one second. But let me just tell you that when I was looking for cartoons for this, I found cartoons on, like, all of these. Like, your doctor just called. He said he's noticed that you had a second piece of pie. Or a guy was going up an escalator and there was very embarrassing ads pointed to, you know, Bob, you know, make sure you sleep more than six into four, 6.4 hours at night. Bob, take care of your rather embarrassing disease. And the caption was still feeling about smug, about being an early adopter of those wearable devices. So, all right, go ahead. What's your question? Hi. My question actually touches a lot on what you were just talking about, is what about the ethical implications? What about the ethical implications? What if I want, or I don't want, my car to be knowing where I am. What if I want to opt out? Can you guys talk about that a little bit? Build a cell phone jam. I don't think that, I don't think that, you know, regulations are keeping up with privacy. Undoubtedly, I mean, ever since the Snowden thing, I think privacy has just become a huge thing. I think there's huge ethical implications. You know, I had a friend who got an Amazon Echo, and he was venting about how he didn't like his job. And literally, the next day, he got an ad that said, hey, Amazon is now hiring, which is really strange. And he was like, man, is this connected? Like, I have no idea. Even on Facebook, you know, you send private messages on Messenger with somebody, and then all of a sudden, you're getting ads for whatever it is that you talked about. So, I think there's huge, huge ethical implications. I mean, there was the famous hack of, I think it was like baby monitors that went out, and, you know, people figured out you could drive by and basically pick up on this network and see what's going on and listen to what's going on in someone's home. I mean, you know, it's important to have that security implemented in the design process instead of coming back afterwards and doing that so you don't have like, you know, silly generic IP addresses that are going to your devices. But I think that's where, you know, companies like, you know, IBM and Juniper and others are really focusing is making those platforms ready to address security kind of upfront instead of waiting until something like that happens. So the question was, what if I just don't want to opt out completely and I don't want, you know, my car to be internet connected? That was the question. Yeah, so, yes, I can say for the Watson IoT we will allow some configuration policy that can build in, give that flexibility. But I agree with you that this is a much bigger area. Keep your car healthy, your existing ride. Forever. So Japanese cars are pretty known for their reliability, so you can always just look for those Honda Civics and, you know, the stuff that are in the used market or maybe just go down to a motorcycle. Or bicycle. Bicycle. There you go. Well, until they start strapping stuff onto them. Go ahead. My question is about community concerns. My question is about the community concerns, the diversity. You may know that 10 years ago, every person joined the Linux community that there are a couple of years of conflict of the misunderstanding of each other. IoT world, now, we may collaborate with evidence per guy, with device guy, with a cloud guy, like us. How do you think about how to make collaboration with evidence guy, with cloud guy, with cloud person, where the open stack community can accept the evidence engineers, evidence communities? I'm going to confess here something that most of you don't know. I actually have a very bad hearing problem. I don't hear very well. So come on up here. Come on up here so I can hear you. I think your question is how do we encourage diversity within the open stack community? Yes, diversity with open stack communities. With other communities, got it. With the embedded communities, device communities. Device communities, okay. How do you get embedded device guys and cloud guys to work together? Thank you. See now, we're all working together already. Thank you very much. Okay, so what do you guys think about that? So I know there are several committee like one M2M, MQTT, all things. Those are committees. I think those committees are open. And I can say that for IBM in IoT, we participate in all those committees as well. That's intent is to have a good interaction between committees in device manufacturer, Silicon manufacturer and the IoT service provider. So that's the intent. But I think that also take lots of effort from more company, big, small, medium and the individual contributor and the open source committee to join to make sure we together build the best for our client really, for ourselves. Excellent. Thank you very much. Go ahead. We talked about ethical responsibility. My question is on social responsibility. We are talking about an explosion in the number of devices that are going to spread over the world. We are talking in billions. And what I suspect might happen is we have these embedded devices distributed and forgotten over time until they actually become a problem and when we have to clean up our environment. So unlike the routers and the switches and the storage devices we make that sit in the data center and that may have their own little recycling program that we can very closely control, these devices are going to come from a different paradigm. So I'm hoping that the companies that you all represent have a program from day one that it's part of the organic design from the start understand this nature of these devices that they are going to be out of control, forgotten. These devices, so no one is going to turn them in for any kind of a trade-in. So they go out there and they are forgotten. But I hope they are responsibly, socially responsibly designed so they don't pose a problem to the planet down the lane. I hope so too. We already see that kind of issue, but it looks like the key's got a point. Here's the flip side of that. Obviously it would be great for all companies to think green. Every time I see a styrofoam cup I cringe because why is there a styrofoam still? But thinking about devices, some of the cooler technologies that I was checking out as I was researching for this panel are actually around energy savings, water savings, things even data centers, farming. There's the sensors now in smart cities that go on light poles that can dynamically change lighting. If there's no cars, they actually shut off. So I'm hoping that social responsibility will come up front in the sense that hopefully we'll be saving a ton of resources. Even something like using your Waze app, trying to figure out where to navigate through traffic. If you think about how much fossil fuels are burned getting from point A to point B, my hope is that you'll get a benefit from the Internet of Things devices sort of up front. And hopefully that will be followed up with some social responsibilities from the recycling programs. I think we've been training people to recycle other things. I think at the point at which there's so many chips in everything, maybe we can train them to recycle that as well. Yes, sir? Who's going to own all these devices? I mean they're all software driven. If the license expires or the company goes under, do they just brick it? And that just happened. That just happened with the Nest thermostats that they decided that they're going to discontinue that. And now Google has to pay like $239 to everybody who bought a Nest thermostat or something like that. But it's a good question. What's your opinions on that? Well, I think to both of our contributors who just mentioned, it's sort of the two halves of the same problem. There's going to be a real concern about how quickly these devices, what their service lifetime is, what do you do when it has reached its end of life either through the actions of the company, it's just an outdated device. And then to the contributors before, I don't think that we've wrapped our hands around the external costs that these businesses, when they create devices, how do we handle all the e-waste? Because the normal recycling programs, I don't think are really capable of handling some of these electronics that are being put into the stream. I don't think that they are. I agree with that. But in some respects, this is a different, this is an existing problem on a larger scale. I mean, raise your hand if at any time in the last five years, or not even five years, in the last two years you have bought Polaroid film. No, of course not. Nobody. So what happens to your Polaroid camera? Can't even sell it on eBay, nobody wants it. So this is a problem that we already have in that we're a consumer society and we consume devices that rely on other things and now we're relying on things that we can't hoard. But in a way it's good. I mean, if you are a equipment manufacturer, if you're NEST, you are going to strive to create the best experience for your users as you can. Because if not, you're out of a ton of money. And you're also probably going to try to figure out some kind of subscription-based model so that you have a sustainable business. If you have a dumb device, dumb hardware, but you can keep updating it via software, that's great, right? Because then you can run that thing for a lot longer than you probably otherwise would have. But then you've got a whole team of people that need to be contributing software-wise and pushing all those updates out to all the devices that you have. So in a way, it's almost a survival of the fittest. People are going to have to create really good technologies because if they don't, they're not going to get adopted. And I think the ones that are good, that emerge out of startup land are going to get acquired by the big companies. There you go. And we'll get to your question in one second. But here's my question. At what point do you think we're going to see generic devices that are all software-divined? I think you just got yourself a company idea and hopefully you'll get acquired by one of those big companies that, Nicky. Hear that, Mirantis? I've got other options. Sorry. That's where open APIs though are really beneficial to a lot of people, right? You know, you think about like a SmartThings Hub or some of the other technologies. If this then that, you know, these platforms that can talk to open APIs are huge. Iron.io. We just, the OpenSec Unlock podcast will be featuring Iron.io. See, I had to get a plug in there, too. Thank you. Okay, I think we're about done, but let's get your question. Actually, that was exactly what I was going to ask is that OpenStack is built on open APIs and they enable a service model economy by non-OEMs. How is that going to apply in the embedded market? Well, there you go. So anybody want to give last words before we kick that out? I had Jim Curry who, OpenStack was his idea. He won't take credit fully, but really smart guy and he was talking about that very thing about how OpenStack has actually kind of changed the way that especially enterprises look at open source software. And so my hope is that OpenStack and the success we've had as a community will be influential as people start thinking about creating these devices and making sure that they can be part of an integration engine via APIs. Any last words from anyone else? Go ahead. With all the risks and threats and security and data and all that, the projected market segment for IoT is in trillions and it's going to explode more. So I think we should all adapt and find ways to take care of the security issues and this is a great opportunity rather than a threat.