 Welcome OpenStack Community! To kick things off, please welcome Akihiro Hasegawa. Hello, everyone. Welcome to Tokyo! Yes, my name is Akira Hasegawa from Japan OpenStack User Group. So when we started our user group, the number of members is really, really small. Maybe I think it's the same situation as your user group, I think. But today, I see a lot of influential OpenStackers here. And you know, in this Tokyo Summit, we have more than 5,000 attendees from the 56 countries. It's quite a nice number, right? Yes, now OpenStack is one of the greatest open source projects without any questions. So as you know, OpenStack is a community-based project. So we need your power to keep growing these communities. So let's put our head together here and make the world more innovative here in Tokyo. Okay? So I'm ready to start. Okay. We cannot talk about OpenStack without these guys. So please join me in welcoming OpenStack Foundation's Executive Director, Jonathan Bryce. Thank you, Hasegawa-san. That is, I would say by far, the nicest introduction anyone has ever given me. It was great. A couple of quick notes here just before we get started. We have simultaneous interpretation today. Everyone has a headset on their seat. Channel one is Japanese. Channel two is English. We will have some Japanese speakers later this morning. So you'll need that for the English later. Channel three is Chinese. And channel four is Korean. So here we are in Tokyo. This is so exciting to be here. It's been a summit that we've been planning for quite a while. And it's, as Akihiro said, we have over 5,000 people here this week from 56 countries. So it's definitely the largest event that we have had outside of North America. And a couple of housekeeping notes before we get going here. As always, there is a lot of information on your badge besides just your name. If you look inside, there's a packet. I think it's like an octo fold this time or something. We keep getting bigger and bigger. That's because this is a summit with a lot of content and a lot of locations. We are spread all around this complex here with the different Prince hotels and the International Convention Center. Right now, we are here in the blue building. And here in this room, we are up on the top floor. But we actually, you know, this is a very big event. And we've had to expand our general sessions to a number of rooms. We actually have, I think, eight overflow rooms. So, you know, we have community members all over right now. There's some filing into one of the other wave to them. They can see us. And throughout the week, there's going to be great content all over the campus. In the Grand Prince Hotel, that is where the marketplace is. And I just want to say thank you to all of the sponsors. They make this event possible. And they make it possible for us to support having our developers here, having our travel support attendees here, and really, you know, allow us to do great things for the community. So, when you get a chance, go down to the marketplace. There's some cool things. I saw this, like, this 3D car simulation down there. That looked pretty cool. And some race tracks and stuff. Design Summit sessions are happening in the Grand Prince Takenawa Hotel. And then there are a lot of work groups over at the Sakura Tower. It's a lot of information I know. Read the maps, as Claire Massey says. Read the maps. But if you have any questions, there are friendly wayfinders everywhere. One other thing to mention. We have a new updated version of our mobile app for this event. You can go through and you can find information on all of the sessions. And a new feature is you can provide feedback. So, please take the time to do this. And give us feedback on the different sessions that are happening. We take all of that and we use it to help plan future summits and to be able to know what kind of content is really valuable for our attendees. So, please, when you get a chance, do that. Lunch, again, you know, it's in a number of different locations. There is a lunch map available online. And also, if you pick up a copy of Super User Magazine, those are available downstairs in this building. It has a lunch map. It's kind of like a treasure map, except for delicious food. And you can find out where you need to go to eat lunch. In pretty much every building, there are a couple of different options. And Super User Magazine has some really great content. It has features on all of our Super User finalists. It has articles from different community members, different work groups, users. And so there's a lot of good information in there, too. And one final thing to mention. In the marketplace, we have our stacker swag store. And that's where you can go get your giveaway. We have beautiful umbrellas, and we have shirts that feature the We Are Open Stack symbol. This is something that ties into an initiative that has been kicked off this year around diversity. You know, we really have been trying to put effort into encouraging diversity in the Open Stack community and in the tech industry overall. So, you know, we are Open Stack. Use that as a hashtag as well. You know, tweet, Instagram, share your experience, show our diversity, and also make sure that you go get your swag from the store. NTT Communications has provided our network this week. And they know a little bit about networks. So they have been able to set up a really fabulous network environment for us here. So thank you to them. And one final thank you that I want to make is to the leaders of the Japanese Open Stack user group. Putting these events on takes a lot of work. And, you know, the foundation staff is really small. So we depend on a lot of assistance from people in the community. And the Japanese Open Stack user group has been helping us for over a year to find the venue to help get things worked out. And it was maybe earlier this year, Akihiro-san and Tori-san were walking us around Tokyo in what I think was a record snowstorm to help us figure out how to pull this off. So thank you very much to them for the support. You know, Open Stack is a very global community. We're here in Japan. Some of you may not realize we actually have three gold members who are based here in Japan. AC Hitachi and Fujitsu is a new gold member this year. We have a large number of contributors who are from Japan, especially on the network side. And we're going to have some really strong Japanese users who are speaking today and tomorrow in the keynotes and then also throughout the conference. So it's really cool to see when we go to these events and we move them all around the world to see how global our community is. And that's what we talked about in Vancouver is the Open Stack powered planet. How many attendees here are from Japan actually? Raise your hand if you're from Japan. Okay, good. So the rest of you are not. How many of you who are not from Japan are here in Japan for the first time? Wow, that's amazing. That is so amazing to see how many people are here in Japan for the first time. It's amazing enough to be able to come here a number of times and I always love being able to come interact with the community and it's great that all of you are here and you're going to get to experience that this week. As we travel around, as we see our global community, as we put on events like this, one of the things that we always see is a need for talent. We need more Open Stack talent. We need more Open Stack expertise. A couple of years ago, we launched an initiative at the foundation to create a training marketplace. This was a marketplace where training providers could list out courses and different sessions that they would teach to help more Open Stack experts be available. And you know, this has been pretty successful. We've delivered hundreds of courses in dozens of countries around the world in the last two years. There's more that needs to be done. We still have this gap in talent. And so one of the things that I'm really excited to announce today is our first certification for individuals. And this is the certified Open Stack administrator. Anytime that you have a new technology, there's always a challenge in finding that talent. The talent always lags the technology. As I mentioned, we've had our training program. We've been working with universities and now we're launching a professional certification to help tie those programs together and help establish a good standard baseline of expertise and of skills that can be available worldwide. So this is going to be an Open Stack certification test that is going to be delivered virtually so that it can be used globally and the tests are going to be administered starting in 2016. I'm really excited about that and looking forward to seeing how that rolls out and helps push more Open Stack talent. This is something that's been developed in the community with help from operators, from training partners, and a number of different people who have a passion for education and for bringing more talent into Open Stack. Another thing that we just announced was the latest release, Liberty. This was the 12th release of Open Stack and it was the biggest release yet. We had almost 2,000 developers that contributed to this release. How many of you here had a contribution in the Liberty release cycle? Yeah, great. Thank you. So these are the people that are building the Open Stack software and they're going to have a busy week ahead of them as well. The Liberty release cycle had over four million lines of code in it and so the Open Stack world of software is continuing to grow larger and larger thanks to the efforts of our developers. In this release cycle, I think that there were a few themes that really stood out if you looked at the work that got done. Manageability, scalability, and extensibility. And those first two, when I went through and I looked at some of the updates that had happened and some of the new features that rolled out, things like a pluggable scheduler, easier upgrades and better performance in the upgrades, especially on the data side. You know, these are things that, when I talk to operators, when I go to the operators' meetups, when our working groups like the Enterprise Work Group and the Product Work Group talk about Open Stack, these are things that they say are so important to improve the user experience. And I think that, you know, that focus on manageability and scalability was really visible in Liberty and so that really excites me because I think that shows that, you know, we're on the right path and meeting user needs. I think there's an interesting dynamic there. Anytime you have software, you have two groups, you have developers and you have users. And we have always, you know, talked about users and talked about developers, especially at this event. It's actually built into the logo for the summit. If you look at that, there are the arrows with the users and the devs. But, you know, in some software development models, the users are almost firewalled off from the developers, you know. The developers are hidden away somewhere and there are layers of sales and product management that are between them. And, you know, maybe the users can be involved at the front end on the requirements phase. They can talk a little bit about what they'd like to see and then it goes into this giant machine and sometime, you know, a year or two year, depends on the company, could be three years later, something comes out and they, that's their version and they have to take it. But what's really awesome about open development models and the Open Stack development model is that everyone can be involved in every phase of the process and users have the opportunity to be right in the middle of it. They can help with the requirements. We have users who have been in the top 20 contributors consistently like Comcast and Yahoo and others that are actually writing the software. And we have new mechanisms like the working groups that I mentioned earlier that allow users to have a voice. And so this is such a key part of Open Stack, the ability to get involved and to impact the direction of the software and to contribute directly to it. That's a huge thing and I think we, you know, as I mentioned earlier, we saw that in Liberty with the manageability and the scalability and some of those updates. But let's talk about extensibility a little more. The Liberty release cycle was the first release cycle that happened under our new project organization model. And the goal of reorganizing the way that upstream work was recognized and managed was really to encourage more innovation, to encourage more projects to operate in that model that we just talked about. To follow the Open Stack way and to open up their development so that people could participate in it. And so we went from a release that had a pretty limited set of projects to something where we see a lot of projects now that are developed here. And this is not an extensive list that says many more. Now, you know, there are official projects for things like governance with Congress, for Magnum, the container service and a variety of new ones. Astara was one of the latest that is an SDN networking service. And so it's really encouraging, you know, the ability to innovate and to move projects along and to get a lot of good development effort around them. But, you know, that has been something that has been confusing to some people because now it's like, what is Open Stack? And what are all of these other projects? And so I think that we're going to talk a little bit about this and hopefully we can clear it up a little bit. I think that, you know, as you look at the world of Open Stack and you look at data that we get from our user survey, for instance, what you see here, there are some core services that are deployed 80, 90% of the time. Here are the services that are common across almost every Open Stack environment. They provide that base functionality of compute, storage and networking. And then you look and you see great functionality, great innovative technology like big data analytics or relational databases of service that may not be as widely deployed but that still provides a critical business function. And people and organizations, you know, they optionally deploy that as well if they need that capability. I think something that is a really powerful model when you have a common baseline plus all of this additional capability built around it. That common baseline is something that we talked about in Vancouver. In Vancouver, we announced our interoperability requirements. And that was something that we've been rolling out this year. And if you go to the OpenStack.org slash Marketplace website, you can see the products and services that have complied with that interoperability guidelines. They're over 25 now in just the last five months that have gone through the testing process and have met all these requirements and have a common baseline deployed in there. And so that's super exciting to see that come along. Those interoperability guidelines as, you know, pretty much everything we do, those are designed and built through a community process. And interoperability is so key to user experience. It's so key to ensuring that as we continue to move quickly on the development side, we still have a common user experience that is available for all of our OpenStack operators. So to talk a little bit more about this, I want to bring out the co-chair of the DeafCore Committee, Agla Sigler. So help me welcome Agla. Thank you. Thank you for joining us, Agla. Thank you for having me. So I'm going to talk about why you think that interoperability is important and strategic and really key to making sure that there's a common experience for users. So I think interoperability is really about user experience. With OpenStack growing in size and scope, each release, it is really up to operators to decide what will be in each cloud that they operate. This could lead to slightly different flavors of OpenStack. Interoperability and DeafCore is about making sure that the lock-in in these special flavors does not happen. So, you mentioned that DeafCore is the committee that sets the standards for interoperability. Can you tell us how you guys approach that and the process that you take to define those specifications? DeafCore is really a community-driven process. We start out by scoring capabilities. Scoring includes looking at each capability and seeing how commonly it is used, our other tools are using it, and what is its technical direction. After we score it, we take it back to the community and say, is this really commonly used? What do you think about it? And we take the feedback and reevaluate and then publish in the next guideline. And so, you know, it's a community process and we have a big chunk of the community here this week. I'm assuming that DeafCore is going to have some sessions. Can you tell people how they can get involved if they are interested in helping to push DeafCore and interoperability forward? We really need all of your help and you have two ways to get involved. One is by providing data. To provide us data, run DeafCore tests using RevStack. RevStack was written specifically for DeafCore testing so you can upload your cloud test data to the OpenStack foundation that they can evaluate and we can actually see what is really commonly used. Another way to get involved is by participating in DeafCore meetings. We have meetings weekly on IRC. We also have DeafCore mailing list and you can reach out to either myself or Rob Hirschfeld, my co-chair to directly talk to us if you are having any issues or questions. Also, this afternoon we are having DeafCore 101 session. Hope you are able to join us and tomorrow we will have two working sessions. Okay, well thank you very much Agla. Thank you Jonathan. So if interoperability and a common experience across OpenStack Cloud is something that you care about there are a lot of ways to get involved and some that are happening this week. Agla mentioned that they score and one of the things they score on is around adoption and maturity and the time that a project has been in development and a number of other factors, but I think maturity and adoption are actually two really important ones and when we were in Vancouver we talked about maturity and adoption and put together kind of a quadrant we call the innovation quadrant. Mark Collier talked about how most technologies start out as an experiment and experiments lead to breakthroughs and you end up with successful technologies being widely adopted and mature and those are the ones that stand the test of time and really make their mark. If we go back a few years, we go back to 2010 when OpenStack was first starting we had the Nova Compute Service that was in development and that was a project that was fairly immature no offense to the team that started it, but it was very young and also there were two organizations that were running it Rackspace and NASA and Rackspace was really only doing a POC work on Nova at the time but you look at something like virtualization and it was right near that breakthrough point and you move forward five years and virtualization is pretty much ubiquitous everybody's running virtualization in some form or fashion and in the OpenStack world Nova is extremely widely adopted and has made huge strides in maturity so that's a couple of technologies but I think it's interesting to think about this from an OpenStack perspective and after Mark talked about this I made a slide that I presented a few times over the summer that had some different OpenStack projects on this quadrant and I see a lot of you taking a picture of this slide which happens every time that I put it up and so I thought that's kind of sad maybe we should give them this information in another way so they don't always have to take a picture of the slide and the other piece of it is it's constantly changing if we look at it now six months later in the most recent user survey it was really interesting to see how heat and salameter adoption had climbed neutron adoption had climbed a lot Mark Collier is going to talk about that tomorrow in his keynote and we have new projects I mentioned Astara, Agla mentioned RefStack, a variety of them but we want you to have this information all the time not just when I put it on a slide so another thing that we're announcing today that I'm really excited about is a new section on our website which is all about navigating the world of OpenStack software and we call this the project navigator so this section talks about those common services and it talks about a lot of that awesome innovation and the great functionality that we're seeing happen in the OpenStack ecosystem what's really cool about this is it pulls in data from the technical committee tagging effort it pulls in data from the user survey it pulls in data from the ops meetups tagging it has stackalytics data pulls in tons of data from all of these different sources and presents it in a way where you can go and you can look at these projects and you can see how widely deployed is it, how long has it been in development and decide for yourself do I want to deploy this now, do I want to wait until it's more well tested and more mature or maybe this is a piece of functionality that I know my business needs and I'm willing to be on the bleeding edge and take a little bit more risk so really happy to announce this and I hope that you all go check it out openstack.org slash software this is the initial release so we want a lot of feedback tell us what's missing, tell us what you'd like to see in there and we can iterate on it as we go what all of this points to though is I think an interesting situation that we're seeing develop many OpenStack environments start out and they look like this, it's a bunch of physical machines with a bunch of virtual machines packed on top of them so we'll start with OpenStack when you look at the data from the user survey and if you go to that software section you'll see that there are some sample configurations one of the things that was really interesting to see is that as people deploy something like Sahara to do Hadoop to do big data analysis they are more likely to deploy Ironic as well and far more likely than in other configurations and so it's interesting to start to see some of those patterns emerge and that's what happens a lot of times they start out with virtual machines and they have a use case like that where they want bare metal Magnum is a project that has gained a lot of interest in the last year and especially in the last six months and that is about managing containers and so eventually they want to offer a container workflow to their users and a lot of times they start out with containers and virtual machines so they can have some extra isolation and more control around their environment but eventually maybe they want to get maximum density and maximum performance and so they put containers on bare metal as well and this is something that is happening in the real world in open stack environments and what is so powerful about all of these technologies being developed in this community is that you have all of these options and it's all in one platform and then you look beyond just bare metal containers you look out to the emerging technologies that are so hot right now like Docker and Kubernetes and Mezos and other things that are so nice to work together and there's so many cool technologies being built right now and you know it again raises questions people will ask me do these technologies compete with open stack are they going to replace it do they need to run independently well I have my thoughts but what I want to do is actually bring out some really successful users and let them tell us how they see the world so to start with help me welcome Lachlan Evensson good morning everyone it's great to be here you're all excited yeah come on I'm excited today to share our journey with containers to production on open stack but that's not the best part I'm going to demo a little bit of the workflow from commit to deploy in less than a minute in front of your eyes before I get into the story though and our journey I want to tell you a little bit about lithium technologies at lithium we help brands connect engage and understand their customers and we do that via online communities and social monitoring tools we do this for a bunch of big brands like AT&T Skype and Virgin back to my story so six months ago almost to the day my boss and I were sitting in Vancouver at the summit and we were reflecting on our cloud platform we'd been really successfully deploying cloud and it was consumed but we didn't feel like we had that aha moment where the cloud had completely transformed the way that developers were deploying our app around that time we started looking at containers and what containers could do we thought they would refine the process they gave developers a clean handoff where they could build and ship their applications to a common infrastructure we could also run that container on private cloud or public cloud we thought this was really powerful it just so happens that at that time the developers came to us and issued us with a challenge they asked us can you give us a platform to deploy 30 microservices standard pattern in one month now this might sound like a feat but we took them up on their challenge we said we accept your challenge so before I went out on paternity leave I threw up an internal repository and with very little info gave a few developers access and said containerize your apps two weeks later I returned the repo was full and there was a post-it note on my desk saying when can we go to production and this was a testament to containers and the way developers could put their apps in and the ease of deployment so then it was on us we had two weeks to deploy an orchestration framework on the cloud thankfully with OpenStack we could overlay Kubernetes on top of OpenStack in less than one day the rest of the journey was using the platform that OpenStack gave us to integrate logging, monitoring and all these other suite of tools that we needed to correctly monitor and deploy containers so with that I want to go into what we did with containers and we've been successfully running them for two months now in production and I'm going to show you so here is our workflow we're going to go through today so this is our deployment pipeline from commit all the way through to push on the cloud platform now the real bonus points down the bottom is we're actually deploying the same container to AWS and to OpenStack and attaching that all back so this is the same container in both places this is very powerful before I go into the demo though I want to just show you a couple of apps that we've pushed out and the monitoring we have so let me go over to my demo okay so here is an app this app is called realtime now this app is running completely on containers in OpenStack and what this does is aggregates globally all our customer data and plots it on a map this is a pulse of all the community activity around the world as we see it so this is what's going on right now as a testament to this I asked for this feature one week ago to have an anonymous view of this data the developer sent me an email five minutes after I made the request and said he had deployed it on the train to work to production that is a testament less than five minutes he had this out with the URL so this is a great result this application is running completely on containers in OpenStack another thing I wanted to show was this is monitoring and logging this is a dashboard we have this is all open source through Datadog this dashboard actually gives developers a bird's eye view of how the resources are being consumed what I would really love to highlight down the bottom is we now have 122 running containers in production across 68 different images and down on the bottom bottom right there you see the honeycomb so that's the utilization of one production Kubernetes cluster alright now come with me on a journey I am now Lachlan the software developer you're going to see the pipeline in action I've written this app and deployed it it's in prod now this app is going to change the world I think you'll love it but wait I just got a slack from my boss saying your app isn't in high availability and I don't really like the app it's not politically correct fix it so there are two challenges he's given me one minute to actually go through and fix all this quite graciously so here I am I'm at my workstation just got out of bed I'm going to interrogate my little friend Cubot who talks to Kubernetes and I'm going to ask him what's running in a OpenStack in AWS my boss is right I have one instance of my app running in AWS in OpenStack so I can ask Cubot to give me more please scale that up okay thank you Cubot scaled so now I have three in OpenStack and I have two in AWS but we can see that they're not all running so let's just ask him again and make sure they're all running so I'm all happy now I have five versions of my app fantastic okay before I go into fixing my app though I really want to play it and you guys are all really welcome to play this as well it's online croc-hunter.lcloud.com and this is my contribution to the world as an Australian so you can see this I just want to get one little kick out of it oh yeah okay I don't think lasers and crocodiles are actually a good way to go so you know what I think my boss is right let's go fix the code here's my code okay let's bump it to version 2 and let's I just so happen to have a more politically correct version of the app and I'm going to go check that in bumped version this is all live I've checked it into git right off that git commit let's go back and see what happens let's watch the magic here okay so here's my build server we can see now that it's on git commit noticed that there's another another artifact that it needs to build it is building that right now in real time what it's done is it's checked out the code built built a docker container put in the repository and it's ready to fire off a deploy job so that should take it's packing the artifact right now it shouldn't take too much longer but while I'm waiting how about I just actually go back and play the game a little bit more because it shouldn't take too much longer so if you guys want to get on on this game help yourself it should be there okay so as always it takes a little bit longer when you're doing a live demo so it shouldn't be too much longer it's telling me it's 34 seconds longer than usual but hopefully it should actually push this out great it's been built now I'm in a deployment step if I go into the deployment step I can see that it's rolling out the replicas so I'm doing a rolling upgrade of that container in real time in AWS and an open stack that's getting pushed out right now and we should be green that is deployed let's the proof is in the pudding right okay I'm on v2 of the app now you see v2 I've rolled that out it's live okay much better I think the world really needs to fire fish at crocodiles and I think you know I do not encourage this if you ever go to Australia because you may be the last thing you ever do so really wanted to highlight is how we could utilize the open stack platform to deploy new infrastructure like container orchestration with no engineering effort and no more capex bend which is really the power of the platform I want to thank you guys I'm doing a session with the deep dive into this on Thursday at 1150 if you guys would like to join come and ask me lots of questions I'll dig into how it all works but thank you for having me thank you Auckland that was great and just to clarify when he said he's doing a deep dive on this on Thursday he's doing a deep dive into the infrastructure not the crocodile hunter game that was a really cool demo and he kept talking about containers and open stack and also as you saw AWS and that's what I hear over and over and over again people want these technologies to work together they don't want them to be different islands so Laughlin talked about containers but there are a lot of other things out there there's bare metal there's platform as a service and so I have another user to bring out who is making use of different technologies and integrating them into open stack help me welcome from Yahoo Japan Takuya Ito Good morning Embra My name is Takuya Ito I am manager of infrastructure division related to open stack in Yahoo Japan Today I will talk about open stack use case in Yahoo Japan at first I will talk about Yahoo Japan with some example of our scale then I will show you some data from our open stack production environment discuss the practical use case and operations of open stack and finally the reason why we choose open stack first I would like to show you the scale of Yahoo Japan this is the main Yahoo Japan site we currently reach 64.99 billion page view a month next is the site for smartphones monthly page view for the smartphone is 31.9 billion which is become almost same as half of the total page view from all the devices over 270 million apps has been downloaded Yahoo Japan has more than 100 services like news weather shopping, car navigation and movies statistics of our operation in only open stack environment the number of concurrent instances is now more than 50,000 network utilization is 6 times more efficient than old bare metal environment there is 20 petabytes of dedicated for the open stack environment we have more than 20 open stack clusters running open stack environment has doubled in the last year alone one year ago we ran 25,000 instances and now more than 20,000 50,000 the number of hypervisor has doubled from 2000 to 4000 okay let's move to next topic can you imagine what this graph shows the answer is workload of our day center when some event happened you can see spike here can you imagine what happened the answer is an earthquake in Japan just before this spike in workload we only had tens of seconds for such sudden event I'll explain what our app actually does later but when people know certain natural disaster happened or received disaster from app they all come to a portal site like Yahoo Japan to know what's happening and that causes the spike in the workload we have some applications that give important information to users for example we have emergency notification and weather related applications these applications send emergency information like earthquake tsunami volcano heat stroke rainstorms as you saw we have some mission critical application in our day center there are some discussions in Japan whether open stack can be used in the enterprise production environment or not I think it is possible but depends on the implementation of the applications as an operator of the data center we need to provide the resources rapidly need to keep working properly in case of emergency and having the same interface for any operating environment is important whether it's KBM Breamer container and bare metal our mission is to make abstraction of the data center and open stack is a core technology why is it important to provide the same API in various environment one is the importance of the speed of the development environment for applications also if the API are the same it would be easy to move on operating environment to another hence if the same API are provided then it would be possible to abstract the data center itself I will talk that we can abstract the data center itself in progress right we can easily migrate physical environment to the new one having this production abstraction also we can easily set hardware right side so can keep to have latest hardware and technology continuously okay let's move to next topic the function of the IOS can be divided to three things basic function, minor function by each vendors and the unique function used by each company the unique function is such as monitoring system for security approval system and compliance monitoring before adopting open stack we developed IOS by our shapes there were more than 10,000 instances operated in the environment before open stack but the problem was that the API were proprietary and it could not work with open source software and now after adopting open stack we can use the common APIs and it has been more compatible with open source software the basic function of the IOS are developed by the community we developed the unique function by our shapes and the minor function for the appliances will be the cooperation of the vendors we call this co-creation by developing together we can get the new function that is needed and vendors can highlight the function to sell the product also if there are people who want to use it they can use the product has been proved to be operated in the large scale environment in Japan we want a data center that evolves to reach this we need the concept of data center lifecycle management to keep the technology evolving we can use the same APIs in all of the environments the user do not need to be aware of the difference of the physical environment this will allow us to use the right environment at the right time we will be able to abstract the data center by this concept also the cost is important even though it is an internal private cloud the user should be aware of the cost lastly we consider that co-creation with our partners important we contribute back to OpenStack community by releasing all the work we do with vendors in Yahoo Japan OpenStack is operated as an infrastructure to support many users one of the great things about OpenSource software is that everyone's efforts combine to make success stories the activities of the OpenStack community supports important applications like Yahoo Japan we would like to say thank you to all the OpenStackers thank you Ito-san for coming and sharing that story it's so exciting when we do these summits and we're able to travel around and we meet so many awesome users developers, companies it's just one of my favorite things that we get to do the interesting thing that he mentioned is exactly what we were talking about earlier this one platform with all of those capabilities that you care about virtual machines bare metal containers emerging technologies these are things that are happening in OpenStack and our open development model with all the innovation that our community is building one of the things that was in the Kilo release was the ability to federate identity between OpenStack clouds and this was something that we talked about in Vancouver if you go to that marketplace I mentioned earlier you'll see a number of companies who are already supporting this think about that kind of turnaround of innovation on a feature like federated identity it comes out in Kilo five months ago and now it's already downstream in commercial products and services that are available so that is what is so cool about OpenStack it's the only platform that lets you do this bring together all of this innovation virtual machines platform as a service private cloud, public cloud tie it all together with federated identity it is incredible what we're building here so I want to just close by saying thank you to everyone who contributes to the software who contributes to these events to local events in your countries and to the community overall thank you very much you're making a huge impact and I love seeing what's happening and what we're doing to the technology world so thank you guys let's have an awesome week here in Tokyo in Paris we started awarding the SuperUser award to a team from an organization that was doing really great things in transforming the way their organizations use technology and also in pushing the community forward for OpenStack Comcast won the SuperUser award in Vancouver inaugural one in Paris and we're going to go ahead and reveal the latest SuperUser award winner so we have Mark Mule and Sheila Sabi from Comcast to come back and help us make this announcement but before we do that I just wanted to mention that as you know we have the board of directors we have the technical committee and we also have the user committee who are all key parts of the governance of the OpenStack foundation was just named as the latest and newest member of our OpenStack user committee so help me welcome Mark and Sheila thanks Jonathan it's a privilege to be here today to pass on the SuperUser award it's we've got some slide issues here one second there we go it's not running on OpenStack so the SuperUser award is meant to recognize teams and they're back to meaningfully transform and improve their organizations while still giving back to the community the impressive nominees are reviewed by the SuperUser judges and they're narrowed down to four the winners are then chosen by a community vote more information on this process can be found on the infographic in the print version of the SuperUser magazine or in the user stories track and here are our finalists alright the first company FICO FICO is a global credit scoring company 90% of lending decisions are based on the FICO system FICO has tripled in size and number of deployments and serving multiple Fortune 500 companies in production with OpenStack and our second nominee is GoDaddy one of the largest web hosting providers in the world serving more than 13 million customers on the OpenStack platform congratulations and consistent 25% growth month over month alright and the third company is Lithium Technologies Lithium Technologies provides social customer experience management software to customers they've currently got 1,000 VMs and expected to double by the year's end like Lachlan mentioned earlier they also implemented Kubernetes running on top of OpenStack VMs and our fourth finalist is the NTT group one of the largest telecom companies in Japan they're going to be sharing several of their use cases this week including one on a web portal serving a billion page views and a million unique visitors per month and at the one year snapshot they had their DoCoMo email platform processing 170 million messages per day and the winner is drumroll NTT group congratulations congratulations come on up for a picture everybody come on down can you go down this way come on you get to take back and display with pride we also are going to be paying for the travel and lodging and passes for two of your team to go to our next event which is going to be in April of 2016 in Austin, Texas so thank you guys and congratulations yeah thank you alright that was quite a crew fintech built this stage well this is what I was thinking as they all came running up here so congratulations congratulations to NTT it's great to have a new super user crown and we'll do it again in Austin look for when we open nominations and get your submissions in