 Ladies and gentlemen, thank you very much for waiting. We are delighted to have you all here. Now we are ready to resume our seminar program for this NAC Breakout Speaking Truck. We'd like to invite Mr. Toshifumi Uesaka, executive strategic specialist, SDN Business Development Division, telecom carrier business unit, NAC, to talk about NAC Cloud System, NAC SDN, virtual data center solution. Mr. Uesaka, please. Hi, everyone. Good afternoon. My name is Toshifumi Uesaka. I'm glad to show you our brand new solution, which name is NAC Cloud System. This is today's agenda. First of all, let me introduce myself. So, Rena, I have a responsibility for the cloud and the SDN business for NAC. But previously, my background is I read NAC software product to the market. But as you know, the customer won't avoid vendor lock-in. That means it's very difficult to adapt our NAC software to the customer. So, reason why I shift to the OSS business for customer's demand. Next agenda is activity for open-source communities. NAC are joining five major open-source community. Since 2000, we joined the Linux Foundation. And then we joined the OpenSec Foundation since 2012. And do you join today's keynote? Shibata-san's speech, other board members. And next, we joined Open Daylight for the SDN since 2013. And right now, I belong to the telecom carrier business unit of NAC. So, we are focusing telecom carrier area also. So, we joined the ONOS and the OPNFV community to realize the carrier grade. And we joined the core infrastructure initiative to support OSS security. Right now, NAC involved in activity for OpenSec. We have two aspects. One is a core developer. And the second one is a super integrator. Today, Shibata-san explained what is a super integrator. Right now, we have eight core developers for eight main components. And regarding super integrator, right now, we're applied to NAC cloud service, which is a public cloud presented by NAC. And the second one is applied to on-premise cloud infrastructure, which name is NAC cloud system. This is the latest situation of the contribution. Right now, we are contributing for the Mitaka next version. Right now, we have 15 developers. And we are contributing nine components. And we have eight core developers for eight components. And NAC is our number one contributor in Japan. This is a liberty situation. NAC is our 10th top contributor. Next slide is an overview of NAC cloud platform. Left side, this is NAC cloud years for the public cloud. We have two types of cloud environment. Wines are high availability cloud environment, which is presented by VMware. And the second environment for the standard, that is the OSS base, OpenSack base. And the right side, we announced this NAC cloud system 20th October. And then we have two types of on-premise cloud solution. Wines are semi-order cloud solution. And on the other hand, it's already made for the vertical appliance for the cloud. And then we can realize our hybrid cloud for the customer. Maybe customers have two types of systems. Wines are SOR and Wines are SOE. We can support two types of applications based on our cloud solution. This is an activity as a super integrator. As you know, the super user is very difficult to lead that area. Sorry, sorry. Common user will be the super user. That activity is very hard. But NAC can support that normal user shift to their super user. That is our NAC's activity as a super integrator. Next slide is a cloud service NAC cloud, yes. This is an overview of NAC cloud platform service. We have previously, I mentioned the two types of cloud. Wines are standard and Wines are HA. And we released this cloud environment last April. And we have knowledge how to use an open stack for this cloud environment. And then we keep this knowledge. And then we will establish an on-premise cloud solution as a NAC cloud system. If you will adopt our cloud solution on your environment, you can realize such kind of cloud service. Even if we can support the VM provisioning and you need some storage backup service and resource management service and network service and operation and security. Such kind of service can be used if you will adopt our solution. Next slide is an on-premise cloud infrastructure which name is NAC cloud system. This is the target area of NAC cloud system. We have three customer segments. Wines are telecom carrier customer for NFVI infrastructure. And the second one is a service provider. And the third one is enterprise information system, something. As you know, that area is quite a different area. But we got several RFI and RFP, almost common requirement from each areas. But some specific area is there. For example, NFV case, user need to realize a carrier grade. And service provider's case, user need some chargeback capability. Such kind of way. We can, NAC will provide such kind of common requirement function and some specific function for each customer areas. So we will support a building blocks solution. If user want to realize, want to establish user's cloud environment, that case, maybe some requirement are different for each. So we can get such kind of requirement and then we try to build for cloud environment from user's demand. This is, for example, enterprise and service provider and the telecom carrier needs a little bit difference. But we can provide such kind of user's demand, something like this. Next slide is NUC cloud system offering. We have three type of two service and one support service. And first of all, we will provide integration service to build a cloud environment. User can choose much vendor service storage network and user want to request NUC will support a cloud infrastructure. And then, especially point, technology vendor just support such cloud environment. But NUC have a cloud operation knowledge. That means we provide operation design also. If NUC will provide that OSS-based cloud infrastructure to the customer, we can support some managed service if user need. And then, we will adopt not only open-stack OSS but also the other OSS. But NUC can support a single window to support every OSS. Next slide is architecture of the NUC cloud system. We published this architecture last November. This is a map to our architecture. We realize no vendor lock-in and contribute additional code to OSS. As you know, open-stack realize a provisioning capability. But open-stack don't have any monitoring and management capability. We add other OSS to realize such kind of monitoring and management. For example, Zabix and the ELK and the Bacula, such kind of OSS can be adapted to our solution. And NUC is one of SDN provider. Right now, we are contributing SDN solution to the open-day light. And we have a lot of use case by our product, which name is a programmable law. Next slide is a map to the NFV architecture. As you know, we provide NFV infrastructure by NUC cloud system. NUC cloud system cover the beam and the NFVI area. Next slide is a user have some concern if user will adopt OSS-based cloud environment. For example, one is a CapExOpex and the second one is a MissionCutica. And the third one is a support and the security of OSS. NUC have some solution for such user's concern. One is we have our public cloud environment. We have already verified OSS combination by our cloud service. And the second one is operation automation by SDN. And the MissionCutica, NUC have a lot of know-how to integrate some MissionCutica system. And the third one is we can support 24-7 days support and we can provide hot-fix patch and we prepare some cloud security solution as well. This is for example, as I mentioned, we have already adopted this OSS-based cloud environment to our public cloud. This is a fact number of cost reduction. We can be successful to reduce TCO 60%. How to realize do that? One is, I don't know, we adopt OSS. That means we can reduce the license fee. And NUC is a hardware vendor. We prepare some high-density server and storage. And the third one is SDN. And the fourth one is automation. In such kind of way, we can be successful to reduce TCO. Next slide is rapid integration of the cloud environment. We prepare some template for design. And we have some automation tool to integrate ES environment. And we have some test tool to reduce the distillation of the integration. Next slide is NAC, our open mission critical knowledge. Bottom box, that is a non-function requirement from the customer. Wines availability, winds performance and scalability, confidentiality, cooperability, operability. In such kind of non-function, non-function requirement also user request NAC to realize. I don't know that OSS have some ban, but user cannot allow to down the quality. How to realize, how to achieve that quality? NAC have eight core developer and 15 developer. And then right now we are increasing number of this engineer to support such OSS. So we analyze the code and we evaluate that OSS. And as you know, some function or some configuration is required to achieve some quality or capability. We prepare some configuration guide or some integration guide for the system integration. In such kind of way, we can provide high availability and high performance system for the customer. Next one is improving quality and advanced support. We adapt Red Hat OpenStack platform. We have over the 10 years collaboration with Red Hat. And then we provide advanced mission critical support to the customer. So we have a lot of knowledge how to realize mission critical support. So NAC will be a single window to support every OSS. And then we can support 24-hour, 7-days support. And we can provide a bug fix if some critical issue might be there. Next slide is cloud security measures. We define the four segment. Why is there for platform? Why is there for tenant? And then we need to take care of the two situations. Why is there for attacks from the outside? And why is there for internal security threats? We prepare such kind of cloud security solution. Next slide is how to satisfy customer demand and contribute to OSS communities. We got several RFI and RFP. And then we extracted common demand from the customers. That's a requirement over the 2000 plus alpha. This is an actual situation. So 2000 requirement we got. And then we try to do the fit and gap. What's demand maybe put by OpenSack or other OSS? Currently OpenSack just covered 30% user requirement. Other 17% we need to put other OSS or we need to enhance some capability to the OpenSack. For example, user request an agency to realize some silver, gold, silver, bronze type of ICT resources. In such kind of case, we need to take care of the dynamic code management for each ICT resources. So right now we are contributing such kind of capability to the community. And the third one is the SI with other OSS. Today we can show you the network appliance situation. This is a non-function analysis example. As you know, the OpenSack user message queue, RabbitMQ, something like this. This is OpenSack generated exchange and queue on RabbitMQ like this. It's very complex. But this is a very key component. So that's the case. We need to take care of the redundancy for this message queue. And if you will adapt OpenSack to default, such case issue for the queue message lost. And if you will take care of the redundancy environment, you need to take care of the split-brain situation. We found that such issue and then we are contributing such our knowledge to the community. Regarding message lost, RabbitMQ have a durable option and the split-brain case, RabbitMQ have a pose minority mode or something. We found out such kind of issue and the solution and we contribute to the community. The next slide is dynamic code management. Customer need setting different limitation of the codes for each availability zone. Such kind of requirement and discussion must be there. But right now, just discussing that dynamic code management by Novak project. But that is not enough because that case, you need some portal to define and manage it. Right now, NEC is proposed this capability, top of rise. Next slide is our VNF manager issue. Customer needs provide virtual security appliance as a virtual network functions. V5.0 and the VROD balancer and the IDS, IPS, VWAP, something. But as you know, the current neutron project not reach to the production level. So this is a challenge. Right now, Tucker is one of project to realize VNF manager capability. But this Tucker is just stuck for a level right now. That means currently, such VNF capability might not be there as OSS. But we need to realize such VNF manager capability into our NEC cloud system. Now, we are evaluating some product to realize this VNF manager. And then, we will adapt some virtual appliance, virtual network functions. Next slide is our NEC cloud system support. We can support the management hardware. And we support 24 hours, 7 days. And we provide a hot-fix patch. And as you know, such kind of bug-fix and code-changing should be contributed to the community. Finally, regarding our core developer, we realize customer's needs by OpenStack and other OSS. Regarding a super integrator, we provide OSS-based open-cloud infrastructure which can apply to mission-critical system and the turning user to a super user. NEC is our headline sponsor. And this NEC cloud system exhibit in our NEC booth. I appreciate it if you come our booth. And I'm very glad to introduce our solution to you. Thank you. Do you have any questions if you have? Yes. We have evaluated the neutron project regarding the L-verse and the F-verse. This is our conclusion of this evaluation. L-verse maybe will be used for production environment, but F-verse not production rival right now. And then we're discussing how to realize such L-verse and F-verse type of VNF capability. As you know, we try to standardization to manage such VNF, but I fortunately network vendor need to have competitive capability to order other network vendors. In that case, maybe some API and some functions difference for each network vendor. So it's very difficult to adjust one adapter to manage a multi-vendor network function virtualization. But as you know, it defines this VNF manager capability. Right now, we are focusing, we are watching this VNF manager to manage VNF. Is that the answer for you, VNF manager? Right now, we are evaluating the third party product. Yes. If Tucker will be useful for this area, definitely we want to join this community and we want to realize such VNF manager as OSS. OpenSec upgrade? Very difficult question. As you know, the currently OpenSec source code increased so far, and then some uncompatibility as well, and then some new capability as well. So current our NECs approach, we establish one OpenSec domain, and if you want to adapt a new environment, in that case, we recommend you to establish one more OpenSec domain, and then if you don't want to use the previous OpenSec domain, we recommend you to use V2V migration from previous environment to the new one. If live migration situation, that KVM should be same control, but if domain will be split, it's very difficult to realize a live migration. That means we recommend you to migrate called migration. How about the other question? Okay, thank you very much.