Hi! Is my mic on? Can you hear me? Can you hear me? Hello. Hello. Hi. Hi, you triple con. Hi. It's been a week. You made it. You made it to Thursday. Amanda, what was your favorite moment this week? I had... You can't hear me, right? I can't hear me, but you can hear me. That's good. I had this awesome moment where I learned how to say good luck and I applauded in sign language. That's awesome. Yeah. I think my favorite moment was when I walked into the exhibit hall for the first time and I saw that some sponsor had made a ball pit. And I was like, this is going to be an amazing week. Did you play in it at all? I didn't because I figured I should leave the fun for everyone else. Missed opportunity. Yep. So I'm Rachel Friesen. I'm the events director here at the Drupal Association. And I'm Amanda Goncer. I am the program manager. Oh, thank you. Amanda, did you see how many people were in that group photo from earlier this week? It looked huge. Did you see me telling everyone to take the group photo? Yeah, I heard you yelling at us to move one way or the other way. Well, you were up there. Did you happen to count how many people you saw? I did. I counted really quick and I said, I bet there's 1,670 people there. And I was very accurate. You were very good, very good, very good. Of all of those people, there were a lot of first timers. If this is your first time at DrupalCon, raise your hand in the air. Wow, welcome. About 29% of you, this is your first time at DrupalCon. And we are 14% female this year, which is a little bit up from last year. So that's really exciting. And this is the first year for DrupalCon Europe that we've started tracking speaker diversity. And so of our speakers of the sessions that you heard, 24% of them, the sessions included at least one first time speaker. So let's give them a round of applause. That's amazing. That's awesome. And we're really working on making diversity a priority. So we asked questions about diversity. And I think 29% of our speakers identified as part of one or more of an underrepresented group. So we're so happy to see some new faces on the stage. And with all of these faces, there's bound to be a lot of repetitive names. This year, the most popular names were Maria and David. Congratulations, Maria and David. Way to represent Maria and David. Yeah. Those Maria's and those David's, they came from all over the world. They do. Those are names that can be from multiple countries. Yeah. Germany represented with the largest contingency at 109. Wow. Pretty good. Congrats, Germany. Yeah.  There's always someone that comes from pretty far. And the person who came from the farthest, I always do that. The person who came from the farthest is Vicki. Good job, Vicki. Thanks for coming and speaking, Vicki.  Yeah. Everybody came from a long distance, but they came here and they ate and drank well this week. We drank a lot of coffee. We ate a lot of sandwiches. We ate almost over 6,000 sandwiches and almost 6,000 cups of coffee. I'm really surprised that it's not more coffee than sandwiches. I know. I would have put the ratio at about 10 cups of coffee to one sandwich. Yeah. I wonder what happened at this con. Besides gobbling up food, we also gobbled up internet. So we had 1,700 concurrent users and we used over 2.5 terabytes of data as of this morning. That is a lot of data. It's so much that I can't really quantify it. So I asked someone on my team to help me figure that out. And if bytes were kilograms, that would be 10 million teradactyls.  So much internet. Some of the data may have been consumed by people in the other room just live streaming the keynote. Also? Yeah. Thanks to JW Player for helping us live stream these events. We had 1,500 people participating online. So we doubled the event size with our online friends. All over the world, people were signed on watching. Pretty awesome. Thanks to JW Player. Amanda, if you've seen her this week, she was probably running from one session room to another to check on speakers. She's been running all week long and she took... I had about 70 kilometers so I tracked it. Lots of steps. I calculated that I could have almost made it to Bratislava. So I could have done two countries, but instead I just did it here with you all. And now is when we start thanking everyone in the room essentially.  This is a good part. Here we go. Let's start with the track team. I will start. This is the track team. This is a team that is near and dear to my heart. I work with them for months before the con to put together the programming. So if you saw a session, which I think that you all did, you have these people to thank. So thank you for them. Thanks, track team. We also have an awesome group that continues to make the con even more special. So thank you to the social media team, the photography team, and our Grants and Scholarship team. Thank you. Once we get on site, it takes another whole bevy of volunteers to help us sort t-shirts and count number of people in the room, stuff badges, that kind of thing. So if you volunteered on site, wave your hand and everybody else give them a round of applause. Thank you, volunteers. Thank you. I also, I do my best to say thank you to every speaker, but I want us as a group to thank the speakers. They spend a lot of time and energy making these sessions for us to hear. And it's a huge contribution not only to the con, but to our community. So if we can have a round of applause for our speakers. Thank you, speakers. And we want to say a special, special thank you to our friends at Drupal Austria. If you are in the local Viennese or Drupal Austria community, will you stand up? You guys made this week so special for us. Thank you. Thank you. They threw an amazing ball on Tuesday. They planned a full day of Monday activities and they've been excellent hosts. So thank you, Drupal Austria. And I'd like to thank people that have worked a lot already and are going to work even more tomorrow at Sprint. Those are Sprint leads and our Sprint mentors. So thank you for making contribution possible. Yes, thank you. I don't know if you've noticed, but there's a lot of people in the background often wearing all black, which we've ironically done today too. But they helped make this event possible and we couldn't do it without our crew at Groundsville Marketing. They're with us for each Drupal con, as well as the crew here at the convention center through Visit Vienna and all of our vendors who help make sure that sessions are archived. You have Wi-Fi, you eat well. So thank you to our crew. And Drupal Association staff, as I'm sure sprinkled throughout, I can see people all over. Every single person at the Drupal Association works on making Drupal con possible. So thank you to all of our colleagues at the Drupal Association for your hard work throughout the year to make this event go. So thank you. Thanks, Rachel. Thanks, Amanda. So I think we're done with the clapping for a little bit, so take a rest. But I do want to make sure we get your... That's great. I do want to make sure that you give your feedback to the speakers. I know that we thank them, but it's really helpful if you evaluate the sessions. Now all the sessions are done, so every session note should have this button that says evaluate the session. So please give feedback about what went well and what they could improve on. It's really helpful for speakers, but it's also helpful for the programming team as we look at programming at future events. So please do that. After that, I have a question for you. Pop quiz. What are you going to do tonight, Amanda? Trivia. Trivia. It's happening tonight at Platinum Vienna. There are 29% of the people in this room that will get you bonus points at Trivia tonight. So be sure and befriend them and invite them to play on your team. That sounds like a great strategy. It's probably the only way I could win. Come to Platinum Vienna. It's off the U-bond, so it should be easy for you to get there. After staying up late and contributing Trivia all night, we want you to come and contribute code tomorrow. Yeah, so we're going to have our sprint leads come up and tell you a little bit about the opportunities for tomorrow. Welcome. The sprint leads up to the stage. Hi, everyone. So there's not really any question that you've been here this week to learn about Drupal. But the best way to solidify that learning is to do some Drupal. So we're inviting you to all come tomorrow to the sprints. It doesn't matter if you're a coder or not, there's roles for everyone. So we'd really love to see you come along. We'll be helping people who haven't contributed before to set up their system and do all of that sort of thing. And there'll be mentors to help people who have been to sprints before, as well as sprints generally for people who've done it lots of time. So it'd be great to see you there. Thanks. Awesome. We hope to see you. All right. So the fun starts tomorrow morning at 9. We've already done a fair bit of committing this week. We definitely have. I think it's 1,064 commits so far. That's up, I think, this morning. So after tomorrow, I'm really curious to see how much more contributing we do. Maybe we can make it past 2,000. That's very high expectations. After you're done with sprints, you may be in an airport or a train station or a bus station just waiting for your ride. Please be sure and take our survey. It helps us know what you liked about Drupalcon, what you'd love to see more of. If there's any suggestions you have about things to include in the future, we really want to know that. So be sure and take the survey. And of the people that fill out the survey, we are doing a drawing for someone to win a free Drupalcon Nashville ticket. So please take it. Speaking of Drupalcon Nashville, our full site will launch later this fall. And we hope to release the call for papers as well as open up the applications for grants and scholarships probably in late November. So stay tuned to the website. But everybody is welcome to Nashville. We hope that you'll join us. But beyond Nashville, there are a lot of other Drupal events coming up. Not only in 2017, but also in 2018. Agreed. So I invite Megan Sanicki and a bunch of the European camp organizers and event planners to come on up to the stage and tell us about what's going on next year. Let's give them a hand. They do amazing work too. Oh my goodness. There's so many of them. We just need a minute. Well, I'll talk while they come up. Oh my goodness. I love this. I hope you all had a wonderful week here at Drupalcon Vienna. It's such a special time for us all to get together. And normally at this part of the show, we'd be revealing what the next Drupalcon is. As you know, we are taking a pause in 2018 and not having a Drupalcon in 2018. So we can really work with the community to figure out a better way to run Drupalcon in 2019 because we know it can better meet your needs. And I'm really excited with the conversations we've had. And I think we're on the right path. Lots of ideas have been surfacing in the different buffs in the community summit. And there's definitely some themes. One is this event is highly valuable. We already knew this, but I mean, people really understood it. It's kind of like when something's not there, you start to realize what it really means to you. And a lot of it has to do with that. It breaks down barriers and allows you to cross pollinate ideas between countries and different personas. I know that Dries and I met with MD Systems, mirrored MD Systems. We wouldn't have a conversation about contribution and how to make that sustainable if we hadn't been here. I'm sure you had your special moments too where you connected with someone and had value you couldn't get any other way. And so I just want you to know we are all committed to Drupalcon 2019. And I am very excited to come out with that plan. In the meantime, the other thing that's happened that's pretty magical and special, but not surprising, is that community members have heard the need for something to happen in 2018 that brings everyone together. In a way that is affordable so more can come together and afford the ticket price. It would serve all the personas and allow for that cross-pollination of ideas to happen. And these leaders have bubbled up and we met today and we have committed, and by we they have, the community will put on an event in 2018. They need some time. Because you guys are amazing and this is what you do when there is a need, you step up and you address it together. And it was a beautiful collaborative process where everybody listened to each other and they just committed that this is going to happen. So stay tuned. They need some more time to really scope this out. And then they're going to come back and let you know where you're going to meet each other next year. So thank you very much. In the meantime, let's talk about what's happening in the world of camps. So 2017, we still have camps to go to. So who is with Drupal Camp Lutsk? Anyone here? They're way in the back. We literally in the back corner. So check them out. I threw in Cape Town because you know, we don't really do too much for, there you go, because we have some people here from Cape Town. We have Mold Camp, Drupal Camp Dublin, Schwerin, Lanion, Uncon. What's that? I don't know what that is. Northwest Dug. Oh, that's the Unconference. Very interesting. And also Drupal Camp Oslo.  What's up? How many camps do you think we have in Europe? Anyone have a guess? How many camps? Over 50 camps. Isn't that amazing? That's not even the meetups, right? That is a vibrant community. Give your hand if you've been to a camp. Yeah, they're really important to this community, right? It allows you on a local level to come together. And even within personas like front end or dev days. And they're all done through volunteers. You have to care so much about bringing people together to put in the amount of hours it takes to run these camps and make them successful. So I would like us all to give all of these camps a big round of applause for all their hard work that they do. So I'm going to hand it over so you can hear about a few camps. As I mentioned, some bring people together in their local region. It's all kinds of personas. And some are for front end developers. Some for developers. Some for the business community. So I'd like you just to hear a little bit about them. So we have DripCamp London, the second to the fourth of March 2018 at City University. We're looking to make it bigger and better. We're going to have 42 sessions. We're going to have a bigger and better social night. We're hoping to spend more than five grand this year. And yeah. Over the course of the weekend, we also have three keynote speakers, which will be announced shortly. A couple already have been. On Friday we have a dedicated business day for CXO people. We also have training throughout that day. Throughout the entire weekend we have sprints and buffs. We have so many people coming together. It's fantastic. I love organizing it with five other people. It's amazing. Tickets, sponsor sessions, sponsor packages, and sessions will all be announced next week. So have a look online. Thank you. So I'm here with Christina representing Drupal Dev Days. So we've been in many beautiful cities. And let's see where it will be next year. Okay. It doesn't work like that. So there's still time for proposals. You have until the 6th of October for submitting your proposal for hosting Dev Days next year. So Dev Days is an event focused around sprints mostly, but also sessions, trainings, wherever you want, because it's your event. We hope to have a lot of proposals and see you there. Frontend United. We will be hosting the event in Utrecht, the amazing city of Utrecht. The conference will be between the 31st of May and the 3rd of June, but we're probably going to organize a bit of stuff around it. So be sure to subscribe to our mailing list or follow us on Twitter. We can follow all the latest updates. For next year in 2018, we're also trying to go for some tryouts like spin-offs. And we have our first, maybe almost confirmed, spin-off in Cape Town, South Africa. So it's very exciting. And our first keynote speakers are Sarah Dresner, Dries, Hermie Roberts and Hayden Pickering. So please all save the days. And yes, you too, back-enders. They will be sprinting as well. And it's going to be awesome. Thank you. And a part of all these amazing camps and conferences, there's another initiative that we would like to highlight. And it's called the Splash Awards. It's been started in 2014 in the Netherlands and in the past few years it expanded already to Denmark and to Germany. And we spoke with another few countries who are willing to organize it as well. Basically it's a ready and steady package that you can use to organize your own splash events. So it has a process written down so that you can organize the camp yourself. The cool thing about this, it's a marketing event. It's a top notch like Suits and Ties. And if your client wins an award for the best website, they will be communicating that on their website and their network, the Dev Wanna Prize. So yeah, it's very good. Yeah, so the great thing is we are not only getting out of case studies in the languages of our own country, but we are also going to do a European Splash Awards event next year. And that is going to be announced when we know first we need to do the local event. So please come and talk to us, splashawards.org. But this is a little bit going to be like a Eurovision. So the best companies or clients or case studies that win, they will then compete against each other in a European event. So that's going to be a lot of fun. Is it working? Nope. Ah. Okay. Well, amazing things to look forward to in 2018. So thank you for that. And as you know, while they're all working very hard, raising families while running camps, working, all those things, the Drupal Association will be working on DrupalCon 2019. And as I mentioned at the beginning of the week, I've asked a group of advisors to come together to help me, especially because as I go back to the U.S., I can't hear as well as I'd like to of all the different ideas that are coming and the best way to move forward. And so I've asked this group, well, you can't see the slides, but I've asked the group of eight to come and help me and fill that role. And I want to be really clear because there was some confusion. They're helping me create the process that the Drupal Association will use for basically identifying who will be running DrupalCon 2019 and the idea that will be moving forward in 2019. So they're not working on 2018. They're working on 2019. Just want to make sure that was clear because I think there was some confusion, but I could not do this work without them. And so I'm very thankful they stepped up because it's eight people getting ideas from all of you. That's a lot. That's a lot. So with that, I just want to have Badi say a few words. So take it from here. Thanks. Thank you. So we have already met and we have talked. We've been in a lot of buffs. We have been in the community summits. We've been trying our best to listen. And that's what we are actually for. We want to listen to your ideas. So within the next one month or something like that, we are going to communicate how we will communicate what's going on. So we don't have that ready yet. So keep just listened or read on Drupal.org what where the communication is going to take place. And we just look forward to hearing all of your ideas of how we can actually do an awesome event in 2019 because that's what we all want. So thanks for that. And just keep, you know, look at Drupal.org. Great. All right. Well, as you can see, there's a wealth of opportunities to connect with fellow Drupalers over the next year. And we want to thank Megan and all the camp organizers for coming up on stage. It's kind of scary to see that many faces out there. But if you have questions about different camps that are coming up, they will all be out in the mall after the closing session adjourned. So you can go and ask them any questions you like. And with that, we will see you tonight and see you tomorrow. Thank you, DrupalCon. It's been a great week. Thanks, DrupalCon.


Hello, good morning, good afternoon. I come from China Mobile. In this presentation, I will introduce you some test framework proposal in China Mobile, non-net project. First, this is the agenda of my presentation. First, I will introduce the background. And then, I will introduce some non-net project in China Mobile. I don't know where you know the non-net project. In fact, it is an NFV project in China Mobile. The third one I will introduce is the most important thing is our automatic integration verification framework. First is about the background. As you know, if we mentioned the test framework, first, we should take a talk about the evolution about the telecom development architect. At the left side, it is a traditional deployment architect. You may see many VNF applications deployed on the dedicated platform. This is a dedicated hardware. But the mode is changed from the vertical mode to the third mode. What means third mode? That means we will provide the common hardware, the x86 hardware. And based on the hardware, we will provide the common cloud platform. And above this, we will use the virtualization technologies, deployment, every kind of VNF applications. For example, the Voity, IMS, IMS, and the EPC, and others. So this is a change about telecom deployment. As you know, in ABAU architect, also the test method have evolution. ABAU is a traditional test. This is our traditional telecom device. If we want to test this device, we should have lots of around the device to the integration test. During this test, most of all, we will depend on our vendors who provide the device. So the test method has evolution. This is now in the cloud, in the third mode platform. How to do the test? This is NFV, Decovering Test Architect. As you know, this is our cloud platform. We will test all the VNF, which is provided by different vendors. So you may see the test method is different from the traditional to the current. So next one, I will introduce our practice in China Mobile. How to do the test in our NFV project, NodeNet project. Mostly, we will do two jobs. One is deployment, another is test. This is the architect. In this architect, I will introduce the process, what we have done during our NodeNet project. This is the architect of ETSI reference. At the bottom is the X86 hardware. Above right is TIC, TIC is Telecom Integrated Cloud Platform, which means the WIM and HyperWire. This is the SDIN controller. And this is the WIMF drawn on the TIC platform. And this is the manual orchestrator. Except these components, we still have many interfaces, three kind of interface. First one is the red one is the interface, which means some API interface, this red one. And the second one, the green one is the standard platform. For example, every WIMF means the virtual machine. And we'll deploy it on the TIC cloud platform. And the third one is the plug-in. Plug-in means, for example, every SDIN controller will provide the plug-in in the OpenStack Cloud Platform. OK, this is the architect. In our project, in fact, we do lots of deployment at test. At the right side, we do SAS deployment at test. First is TIC deployment and test. In this item, we do the WIM deployment. And during this process, we should solve some problems. For example, the adoption between the hardware and the cloud. And then we will do the verification. This one, we will do some function test, performance test, reliability test, and option test. After the TIC deployment at test, we should do the SDIN deployment at test. And first, we will do SDIN deployment and do some SDIN controller function test and do the SDIN and NFC combination. After SDIN development and test, we will install many kinds of VNF and do the VNF deployment at test. After that, also, we will do the test about the manual test or the trigger test. This is the whole process in our non-net project. We will do SAS kind of deployment at test. Next one, I will give you the detailed information about our test about every component. This one is TIC deployment and test. As you know, if we want to do the TIC deployment, first, we should do some network architect design. As you know, this is the deployment architect in every OpenStack platform. Maybe different one that provides different OpenStack solutions. But mostly, we should include the SAS kind of architect. For example, this has different node controller node and network node, computer node. Maybe also, you still have some storage nodes which provide the distributed storage. Except this node, we still have some network play. For example, the administrative play and some application network and some storage network and so on. So when we do the deployment, first, we should do the network architect design. And then we should do the server design. Of course, we will, in our all the architect, we include many kinds of nodes, installation nodes, controller nodes, computer nodes, and storage nodes. After that, we still do the HA design. For example, in the controller node, we will provide many OpenStack services. We should provide the AC solutions for these services. After the deployment, we will do the tick test. First, we should do the function test. For example, affinity or anti-affinity and so on. After that, it's about the performance test. As you know, VNF needs high performance. So we use many kinds of performance technologies. For example, SRIV, DPDK, Neuma, and the OAS enhancement, and so on. And we still do some computing elastic and reliability test. In our reliability, we do the test about we emulate some fault. For example, it's a different node fault. We have different node rows. Some node is a controller node. And some one is a computer node. Some one is storage node. We will do the default test on all these nodes. And also, we do a test about a different network fault. And the last one, we will do the operation management. For example, the update and alarm. So these are our tick deployment and test. After that, we will do the architect. As you know, we should do the SDN deployment hand test. This is the SDN architect in our In-Channel Mobiles, In-Channel Mobiles non-net project. This is open O, but now it is combined with AT&T E-com as own app. And this is Auger Tritter globally. These are two ticks, the Cortic and the Aztec. As you know, we have many ticks in China Mobiles non-net project. And we deploy many ticks in different programs. And in our central data center. So these are two ticks, Cortic and Aztec. And mostly, the control plane, this is the flow about the control plane. This is the flow about the forward plane. You may see the tick interaction based on SDN. So first, SDN will do some connection between ticks. For example, no matter between the Cortic and the Aztec. Another one, SDN will do some data network flow in analytics. So as you know, we will do the SDN deployment and SDN test. For SDN deployment, first we should install the SDN controller. And then we will install the SDN gateway. After that, we will, these two components is outside the cloud platform. But these two ones is inside the OpenStack platform. We will change the network from the default design in Neutron to the SDN. We will install SDN plug-in in the controller node. And also, we will do some less update according to the SDN solutions. This is the SDN deployment. And after that, we'll do the SDN test. First, we will do the basic network function test. And then we will do the security group test, bandwidth-limited test, network traffic, statistic, and so on, all kinds of SDN test. This is our SDN deployment and test. After that, we will do the VNF deployment and test. I don't know, this is all the VNF applications we will test in China Mobile. At first, we do a test about NBIOT, which is the EPC, CPE test, E-Bound test, and IMS test. These tools are deployment on our FACE2. You means different VNF on the same tick and orchestrated by the manual. We will test all this VNF. And first, do deployment, and then do test. Next phase, I will give you an example about the VNF deployment and test. I will take the CPE, the VCP deployment and test as an example. This is the architect of CPE. As you know, in CPE, these ones are hardware. They will deploy the deployment outside of our tick, of our platform. And this one will deploy it in our tick platform. This one is deployed on the eighth tick and this manual is deployed on the code tick. But we have the connection between the round device to the device in our tick platform. So as mentioned in the VCP deployment, first, we should do the spherical equipment and the simulator deployment, this kind of device. And the second, we will do the SCP deployment on our cloud platform. Then we will make the connection through network between the brass and the SCP. This is the deployment network. After that, we will do the test. For example, the VNF lifecycle management, business floor classification and marking, a CPE basic function test. For example, in our cloud, this VNF will have different functions, net function, DCP function, or DNS function, or PPOE function, such kind of VNF applications. And also, we will do lots of value-added business tests. This is the VNF deployment test. Although we have many kinds of VNF application tests from many vendors, but the process deployment and test may be the same. OK, after they introduce about the process of our deployment and test, I will give you, you may see, the total process is about from the TIC deployment and test, the SDN deployment and test, VNF deployment and test, manual deployment test. This is the process in our normal net project. We already have done. This is our hardware architect. As you know, in our project, we involved six vendors, OpenSec solution. And this is our data center. We have multi TICs. And we also have multi RECs, which is the other test equipment. For other test equipment, we have TIC test equipment. For example, network test instrument, software test tools, emulation tools. For SDN test, we have some SDN controller gateway. For VNF test, we have some vehicle equipment instrumentation from ESL or Sprint, other emulation tools. All these test equipment deploy on these areas. And also, we should do the interconnection between the TICs and the other device, around the device. So we should do the interconnection. OK, that's all work we have already done. But how about the integration test architect? We will have some deep thinking about it. At the bottom, this is Weihua Dao, the TIC basic environment. And based on the TIC basic environment, as you know, we have to the development configuration and the test on all the components. But how about the integration architect? We do our work, our jobs. We summarize the integration architect. And we do the integration process and find lots of verification tools. All these things consist of our integration architect. But about that, we still have new things. We will build the development architect, include the VNF optimization and the VNF optimization. As you know, the VNF has evolution, generation by generation. So we should build a process to enhance our integration test. So this is the evolution. You may see the NFV process is also a CICD. At the left side, you may see the TIC development, include hardware, WIM, SDN, VNF manual, which consists the ETSI architect. Maybe this component is provided by different vendors. After their development, they will deployment on our platform and do TIC integration verification. For example, many kinds of components. After that, it will be deployed on the production and go to production. In production, we will find lots of problem issues. And they will feedback to the development. So this is a circle, wronged and wronged. So in this process, traditionally, the carrier operator will depend on the vendors. Most of the test, integrated test, is depend on the vendors who provide the VNF, who provide the telecom device. But now, the view is changed. The carrier itself should take the responsibility of the integration. This is the chance, our integration test chance. As you know, next step, we will try open NFV architect as a reference. This is an open NFV reference. We have the Jenkins master and the Jenkins slew. And do the installation. For example, use Kampas Docker and do some tests. Use test tools, for example, from test on the R disk. About that, we still have some customized test case. We will integrate this test case to the framework. And we also will use some verification tools to verify the platform. But because, as you know, the open NFV now, some kind of test is not involved in open NFV architect. We will take it as a reference and do some enhancement to use these open NFV tools. This is our plan. And we will do some tests after in our next phase in non-net product. OK, thank you. Any questions? Yes, hello. Thank you. Presentation. In your plan with the test cycles for the different components of your deployment, the VNFs, the VIM, MANO, and so forth, do you intend to make upgrades into production only for all components in one tested group? Or do you intend to be able to move new versions into production, let's say, for VNF or for SDN control independently? OK. In fact, now we will have to do some tests, not we build the non-net product, which is the future of the, which have the future mission of the tandem mobile's NFV evolution. So this is the first phase. First phase, we will do the test in our lab and in many of, in many programs aside. So just now I introduced the process, what we had done. But I think now we will do the test framework proposal, which will deploy our production. For example, next phase, we will push the VNF NFV to the production. And we plan to use such kind of test framework to the production. But now it is only the lab test. OK. Any other questions? Are you leveraging OpenStack Tempest for any of your verifications? And then have you extended it to do any VNF testing? You mean the VNF test in this circle? Yeah. Are you using Tempest anywhere? Now we will not use Tempest. But as you know, next phase, we will use, oh, sorry. In fact, we have, in fact, in the WIM test, we use for the API interface test, we use Tempest. And you know, different wanders, different OPSAC solutions providers have different tests throughout. As you know, Tempest test case is about more than 100 test cases. And we have to do the tests on different wanders. Mostly what we need in FA applications, the wanders OPSAC solution passed the Tempest test. OK. Yes. Deployment, configure, research, and test. In fact, the test, we contains the basic function test, performance test, reliability test, operation test, such kind of test. But most of our test is focused on the features which we will use in the NFV applications. Six vendors for all NFV ecosystem. These six vendors is only for VNF or are all, for example, for hardware, for VIN, for another? For all kinds of components? All of components. Yes. And another question is, how many VNF vendors have you got? Approximately two, one, three? OK. This is this kind of for VNF. This is NBIOT. For example, NBIOT could be one vendor. CP could be another vendor. You have in your deploy many vendors for VNFs or only one brand? Yes, we have many vendors. For example, we have three vendors provide the NBIOT solutions. And three vendors provide CPE. In fact, most of the vendors want to take part in our non-net project. We choose three vendors involved in our project, do some tests. We think after we integrate a test, we will do the standard integration process. And then other vendors will take part in, participate in our integration and follow the standard integration flow. So you have an integrator or partner to do all the tests or only China mobile do us own? Now, in fact, we only choose some vendors to test, not the fixed vendors. OK, thanks. Here you come. Any other questions? OK, thank you to come here to my presentation. I think after the presentation, if you have some questions, you may contact me. OK, thanks.