 So do you have any, so how can I pitch down, pitch up? Use like my laptop? Okay, okay, okay. So, hello everyone, good morning, and thank you for coming my session. So I'm going to present the real test on the undergraduate students for the innovation contest. So you can see how the students were deployed and used OpenStack to build their cloud application. So my name is Shen Wang. So I'm the individual board of OpenStack Foundation. I also work in Shanghai. I work for Intel as an engineer manager. There's two speakers. One is from our engineer, and the other one is Zhen Zhan Zhou. He used to be a senior engineer at Intel, but now he's an emcee. So both of them help me to set up the environment for the undergraduate students. I'm going to talk about the objective of the innovation contest and also give you some background and show some highlights and lowlights. And I'm going to tell the operation, OpenStack operation and the deployments during the contest. And we made this a way among the students. And you can see what's the difference, what's the survey result, and we get some key learnings and make some suggestions for the community to improve the OpenStack, especially for the universities. And also I can introduce some of the cloud applications they made. First is the context objective. I think we have a lot of objectives, two of them are very important. One is to accelerate the adoption of OpenStack in academia. And the other one is to provide the OpenStack environment to the students so they can build new usage models, new usage scenario based on the cloud service. Here's the schedule. The innovation contest last, it's almost a half a year. And at the beginning we kick off and determine the theme to be cloud service, cloud application. So from this, I think you must know the application hackathon at Taiwan. So it's similar, but we also emphasize the OpenStack usage, especially OpenStack deployment. So we determine the theme and also define the rule for the contest. And on the first stage, we opened a registration and we got almost 100 teams to join the contest. And at the beginning we also promote OpenStack by delivering the trainings. Like we set up the website for the online training and also deliver the onsite training at different universities. We also distributed the OpenStack book and unfortunately the book is in Mandarin, so it's in China. And the second stage, we make some judgment. At the first stage, the students will submit the proposal, just ideas of different cloud applications. So there's no implementation. But at the second stage, we make some judgment on the cloud application based on the innovation and the creative ideas, how creative the idea is. And then we request the students to implement the idea at the final round. So at the second round, we cut half of the team. And at the final round, we invited 20 teams to come to the university, Tianjin University and deploy OpenStack based on the hardware we offered and deploy their cloud application on the OpenStack cloud and show the live demo, live demonstration to the judges. The highlight is, we know this event, this event attracts the attention of the university and also the government. So the government also recognized the event because this event promoted cloud technologies. And we got a lot of the university, especially software college, to involve the event. And we have more than 2,000 students to join the event. And they formed almost 100 teams. And the other thing is, as I said, we set up the infrastructure for the online training and for the online forum for them to ask questions and get answers. So those kind of infrastructure achieved a lot of web views. And at the final round, we also invite the local media to promote the event and also promote OpenStack in the local community. So we talk a lot about the highlights, so let's look at something bad. Sorry, there's one more. So this is kind of the snapshot of the media magazine or newspaper. On the internet. So for the best things, we know at the final round there are 20 teams joining the final round, but only one team successfully deployed OpenStack within 36 hours without any help. So because at the final round, we just give them the limited time and also I also want to say that the cloud is not complex. It's just several nodes, but only one team successfully deployed it. So for the innovation context, this is how hardware settings we donate a rack. The rack contains several servers and also we may connect each other by a switcher. And one of the things that it's different is we didn't provide the hardware, the physical hardware to the students. We provided virtual machines to them and this is used in national virtualization. That is to say, the students have to deploy OpenStack on top of OpenStack. This is different. So for one team, for each team, the team will get at most four virtual machines, two large virtual machines and two small virtual machines and deploy the different nodes onto loads for virtual machines. I think the idea of this is to show the steps for the students to deploy and do the operation on OpenStack. So the idea of this step is the students will get the virtual machine and create a network to make all the virtual machines connect to each other and also create the virtual nick and attach to the virtual machines. Sometimes they will use their own image because we also offer the image to the students but they have their own image built at the school and they will use that and they upload the image to the ground service. So after all the operation is done, the students will deploy OpenStack based on the tenant, the tenant network. Okay, this is... We made this a way for the 20 teams. The diagram shows the tools they will choose. We don't have any recommendation to the students which tool is the best, which tool is the hard to use, but they choose the... I think you can see from the picture that the popular tool is DevStack. I think maybe the DevStack is a part of the OpenStack projects and also DevStack is easy to use just run some of the scripts. But the second... the second most popular tool is Ubuntu and the installation manual guide, installation guide. So the students will look at the web link and install the OpenStack step-by-step manually. So there are also other tools like RBO, like a few, like a puppet. But because it's... I don't know the reason, but I just take a guess because they are complex enough except for enterprise. The students doesn't need it. They don't need a lot of things. Yeah, so... Or maybe it's not popular in the community. It's popular in the enterprise, in the commercial products. So what are successful... This slide shows what are successful for deployment should be. Ideally, we have four watcher machines. So the students can deploy one watcher machine as a controller and two as the compute nodes. And the other one is the network node. And this is the basic infrastructure for the cloud application. So based on that, they can deploy the different application on top of the compute nodes. So this is the ideal picture, ideal architect for the students to follow. I think it's very easy. So next slide shows the survey result we made among the students. What's the top issue they met? So the top issue is connectivity. So the connectivity is very hard for them to make the watcher machines connect to each other or also make the watcher machine access the public internet. And second thing is network configuration. I will show you some of the details in the next slide. And then we can get some of the issues from the package. The package is not a student's force. It's not an open-stack force. It's our environment because the environment is very... It's a little bit bad. It's a little bit slow. So they are not able to upload the image or get the image service. So apart from that loss, we also get some image and glance related issues and the others. The other issue is not so many. Okay, top issue, connectivity. So a lot of students meet the same problem. They are not able to... We give them the four watcher machines but they are not able to build a network among those four watcher machines. They cannot make them connect to each other. Also they cannot make any of the watcher machine to access the internet. The second issue is, as I said, is network configuration. This service from students is not what I said. They said it's not familiar with the multi-we nick to a watcher machine. If they want to set up the network controller, the watcher machine has to attach multiple watcher nick. So they don't know... They have no idea how to do that, how to achieve that. And secondly, they are not familiar with the configuration files. There's a lot of configuration files in the open stack but it's so complex. A lot of sections, they don't know how well they should modify to make the network work. They also made some cloud IP problems. And for the image, I do think some of the problem is also related to network because they also said that the glance service is not available. Sometimes it's not reachable and the image cannot upload to the glance and I do believe it's a kind of network issue. So we also did non-less away for the top issue, top blocking issue. So you know, they made a lot of problems but they can spend enough time to solve the problem. And you know, only one team succeed but for the others, they met the blocking issue. They have no time to solve the issues. So similar as the last picture, the blocking issue, there's a 19-meter blocking issue of connectivity. That is to say in the end, they fail to solve the issue. And the other thing is like a package error and the third thing is network configuration. So this picture shows some of the bad of OpenStack. So looking at the, what we can learn from the lesson is because that is a real test. The students, undergraduate students, you can treat them as a freshman in the OpenStack world. You can treat them as a newcomer. So at the beginning, they know nothing about OpenStack. They know nothing about the cloud. So they spend half a year to study and give a final examination within 36 hours. So the key learning, the first one is very hard to master OpenStack operations. We know there's operation manuals. I think it's very easy for an operator to deal with different kinds of situations for the undergraduate students, especially those students in science and the software college. So I do think they are familiar with the computer operation. The second is for the newcomer, the learning curve is pretty long. The learning curve for OpenStack deployment and the operation is pretty long. And the third thing is as you see, most of the issue existing in network, especially in neutral. So I think as a user, you can think that neutral is very easy to make the issues and it's not easy for them to solve the issues in network. And for the OpenStack deployment, the process, for the simple case, I think the case is simple enough. But for this case, for this scenario, for the students, they always spend a long time solving the issue to deploy OpenStack. So you can see the OpenStack deployment process is a little bit complex. So next stage is about suggestion. So we get some learning and we want to make some suggestion for the community. One is to improve documents. We know the documents are not well-organized in the community. Unlike the code, the document, sometimes the document is out of date and no one to maintain to keep them updated. And also the documents are, most of the documents are in English. So we hope the community can put some efforts to translate to multi-languages. And second is we know OpenStack Foundation initiate a program. It's OpenStack professional certification. But there's a lot of examination there. But those are for operators. But for students, like the students' university, they don't have any chance to study OpenStack and pass the certification. But I do think we can emphasize that in the community to promote OpenStack at the beginning, at the students, from the students. And third thing is very interesting because we know the students can DIY parameter machines. So they are familiar with the physical hardware. They can buy the parameter machine from the IT market. They also have the access to the school, actually lab in the school. So they can DIY. If they want to make the network work, they can open the desktop. They can plug in the NIC. They can plug in the cable anyway. But for the virtual machines, it's virtual. So it's in the software. They know how to deal with that. They cannot crash the software. They cannot crash the virtual machine. So we think for the students, the community needs to offer more chance for the students, especially the teachers, the students in the university to use the cloud environment. Use the virtual machines. Like we know, we have the public cloud in AWS and the other big companies offer the public cloud. But for students, they have a fair chance to use the cloud. But public cloud, I don't think, because public cloud is not similar as the private cloud. So I hope the community can offer more chance for students to to face the private cloud the problems. And last one is we did a lot of efforts for the industry. Just like Summit, we have a lot of operators, developers from different companies, large company or small company. However, did you see any researchers? Any students? No. I cannot say no, but there's a few. So we involve a lot in the industry, but I also hope we can involve the academia area, because there are special persona in the open-stack world. Yeah. So I hope we can help them to do some research and to educate from university course. Okay, the last page is about the I can introduce some of the application they created and first prize is a winner. The first prize application is about real detector. They use the cloud to collect the data from the behavior of the user in front of the desktop and use that data. Analyze the agnostic data to send some warning source provide suggestions to the desktop users. You have to correct your behavior so otherwise you will be hurt. Hurt it, yeah. So this is the first prize. They take and leverage the cloud to do the analysis and do the data collection. And the second prize we also have several we have three winners. The first one is called eWallet. The eWallet is that you treat the smartphone as the credit card. You can pay something and make the transaction based on the with the smartphone. So the smartphone has the camera so they use the face recognition as a password. And back when they use the cloud to connect the bank and the retail. So if you want to pay something for the retail, you just use the smartphone if you take any money. Yeah. It's another I think it's a very creative idea. The second application for the second prize is first aid outdoors. It's interesting. And you know they also use the smartphone. So like outdoor you see some patients they have something very emergent. You see some emergency. So they use the smartphone to take a picture and send out the picture to end the location. All of this is done by automatically. So send the picture to the cloud to the back end call center and hospital and then call center and hospital will send the ambulance to the patient. They know the location of the patients. Yeah. And the last one is about security. So far we have a lot of we have a lot of the password to remember if you make one password for all the accounts it's not safe. So the students made the application on the smartphone. So the application divided the password in two parts. One part is on the smartphone. It's like a hint. The other part is the rest of the parts is saved on the cloud. So if you want to if you open the application and want to input any password they will they will achieve the password from the cloud and you get some input. You input the other part and make a combination and send the password to the application server. So make your logging. This is another user scenario for the cloud. They use the cloud to save the password and to make the password more secure. This I showed a photo as I do think it's a very good chance to I do think it's a very good chance to do some real tests on the open stack. So it's it's also a good opportunity to promote the open stack and also we can know some weakness of the community. So we hope we can leverage the chance to improve open stack and improve the community and to involve more people into the community. This is a photo after the final round. Okay, thank you. I think that's pretty much all of it. Do we have any questions? No, okay. Thank you. Thank you for coming.