NTT Group has three OpenStack use cases in production and its team has contributed 1,054 total commits, ranking 18 out of 263 total organizations

It’s time for the community to determine the winner of the Superuser Award to be presented at the OpenStack Tokyo Summit. Based on the nominations received, the Superuser Editorial Advisory Board conducted the first round of judging and narrowed the pool to four finalists.

Now, it’s your turn.

Nippon Telegraph and Telephone (NTT Group) is among the four finalists for the Superuser Awards. Review the nomination criteria below, check out the other nominees and vote before the deadline Monday, October 12th at 11:59 p.m. Pacific Time Zone.

What kinds of applications are being built or run on the OpenStack cloud?

We have various applications. The large deployments include the following:

  • Use case number one: web service infrastructure at [NTT Resonant](
  • Use case number two: backend storage of E-Mail system at [NTT DOCOMO](
    ![alt text here](superuser:figure:wxgpz7couj2eke58a2ql)
    built by [NTT DATA]( System Integration team
  • Use case number three: [public cloud service]( at [NTT Communications](

For use case number one, there is a web portal site for Japan market (goo), which has been provided over 18 years and has been running on OpenStack in production since October 2014. It accommodates more than 80 services, 1 billion page views per month including web search engine, web portal site, smartphone application, online store and more.

For use case number two, we applied Swift to build a cloud storage system to store archived data on “DOCOMO Mail,” which is one of NTT DOCOMO’s services that was started in October 2013. As of December 2014, it had reached approximately 18 million users and the number of users and data size stored keeps growing. At the snapshot after one year from when service began, it processed 170 million emails per day.

For use case number three, we have provided a commercial cloud service named Cloudn since 2012. Cloudn has several service types, and the virtual private cloud service, VPC-type service, is built on OpenStack. Cloudn offers flexible network design and combines our VPN service and OpenStack components, which are Nova, Cinder, Glance, Quantum and Keystone.

How has OpenStack transformed your business?

In use case number one, the time to provide a virtual server for application developers and services was shortened to five minutes from five business days. Because a virtual server can be easily scrapped and built, the opportunity for technical evaluation has increased for our application developers. Moreover, a migration of virtual servers between physical servers becomes much easier, so it helps our operators handle a server failure. Applying OpenStack to our production triggered us to join the OpenStack community deeply, and sharing the knowledge with each other in this industry has been inspiring us at various viewpoints, not limited to infrastructure management.

For use case number two, OpenStack gave us a storage system free from vendor lock-in to replace expensive high-end storage. We will be able to reduce the total cost of ownership by 60-70 percent in five years total. Because we deployed the system into many data centers in a distributed manner, it achieves high availability and reliability which is helpful for disasters. In Japan, we suffer natural disasters more often than other countries, and it contributes to keep the communication lifeline available even in such disasters, which is very important socially.

For use case number three, OpenStack enables us to provide a commercial cloud service at a low price. Flexible network features in OpenStack enable us to combine our VPN service and cloud services. Our cloud service built on OpenStack has had no serious trouble since it started our customers who specify OpenStack for their system integration have increased. The application of OpenStack to our cloud service gives us many business opportunities to meet various customer needs.

How has NTT Group participated in or contributed to the OpenStack community?

The design of case web service infrastructure at NTT Resonant was shared during a lightning talk at the OpenStack ops meet-up in Palo Alto in August 2015. We will present the story of case web service infrastructure at NTT Resonant and also the backend storage of email system at NTT DOCOMO use case built by the NTT DATA System Integration team at the OpenStack Summit Tokyo in a breakout session.

A lot of bug fixes and improvements were provided to OpenStack community in connection with the activities of all cases mentioned above. Our contributions include:

  • Total commits: 1,054 (ranked 18 out of 263)
  • Total lines of code (LOC): 124,582
  • Reviews: 5,325 (ranked 16 out of 212)
  • Change requests: 979
  • Patch sets: 3,952
  • Draft blueprints: 103
  • Completed blueprints: 34 (ranked 19 out of 138)
  • Filed Bugs: 770
  • Resolved Bugs: 413 (ranked 14 out of 204)
  • Emails: 325

(Source: Stackalytics)

65 developers of NTT Group have contributed to make the following features in OpenStack:

  • Live migration for KVM, IPv6 support in the Nova project
  • Multiple network interface cards (NICs) support
  • Multiple vendor plugins support (Metaplugin)
  • Static route configuration of a router
  • Multiple nodes support of l3-agent and dhcp-agent
  • Availability zone support
  • Schedule block support at agent start in Neutron project
  • Image transfer between Cinder volume and Glance
  • Image download control with license attribute
  • Taskflow implementation
  • Sheepdog driver in Cinder and Glance project
  • Global cluster replication improvement
  • Amazon S3 compatible API support
  • Plugin interface for erasure code
  • Slogging improvement in Swift project
  • Network gateway as resources in Heat project
  • Policy enforcement for all data source
  • Non-JSON format data source support in Congress project
  • API reference improvement in Documentation project

We developed Virtual Machine High Availability (VMHA) components for OpenStack KVM deployment of Nova and make it open source for community. The project is named Masakari which is published under Apache license at github here. It was also presented at the ops mid-meetup in Palo Alto.

Kota Tsuyuzaki is a core team member of the Swift project. He has participated all four mid-cycle meetups of the Swift project in the last year, and he is leading the Swift development community with other core team members. Mitsuhiro Shigematsu is a team member of Cross project Liaisons. He is in charge of Ironic documentation and inter-project liaisons between Neutron and Ironic.

We have participated in all of the OpenStack Summits. Akihiko Murakami attended the first Summit in Austin in July 2010. Koji Iida attended the second Summit for Bexar in San Antonio in October 2010. We have also participated in all OpenStack ops mid-cycle meetups, except for the first ops mid-cycle meetup. Shintaro Mizuno attended the second ops mid-cycle meet-up in San Antonio in August 2014.

At the attendance of Summit and meet-ups, we shared our knowledge by the following presentation and talks:

  • Shintaro Mizuno, “User Panel: How did you bring OpenStack to your company?” at Hong Kong Summit, breakout session
  • Masahito Muroi, “3 unaccountable specs in OpenStack” at HongKong Summit, lightning talk
  • Masahito Muroi, “sample implementation of stack convergence in heat – A RE RE again !!” at Atlanta Summit, vBrownBag
  • Sampath Priyankara, “Multi-site connectivity and customer on-boarding with OpenStack and NSX” at Atlanta Summit, vBrownBag
  • Takuma Watanabe, “VM High Availability without Modifying VM Settings” at Atlanta Summit, vBrownBag
  • Kota Tsuyuzaki, “More Efficient Object Replication” at Atlanta Summit, design summit
  • Takashi Natsume, “OpenStack Upgrade Without Down Time” at Paris Summit, general session
  • Hirofumi Ichihara, “Neutron CI Run on Docker” at Paris Summit, vBrownBag
  • Masahito Muroi, “How to Build a Carrier Grade Cloud – A RE RE Teck Talk” at Paris Summit, vBrownBag
  • Kentaro Tanaka, “High Availability for VMs using evacuate API” at Paris Summit, vBrownBag
  • Sampath Priyankara, “How to protect glance public image in carrier grade cloud” at Paris Summit, vBrownBag
  • Daisuke Morita, “Future Auth interface design for Tempest” at Paris Summit, design summit
  • Kota Tsuyuzaki, “What’s Up Swift? The Globally Distributed Community Behind Swift” at Vancouver Summit, general session
  • Masahito Muroi, “A RE RE -Making OpenStack more friendly to a newcomer” at Vancouver Summit, vBrownBag
  • Daisuke Morita, “Changing policies (work session)” at Vancouver Summit, design summit
  • Toshikazu Ichikawa, “OpenStack Use Case and related Project in NTT Group” at Ops meetup in Palo Alto, lightning talk
  • Masahito Muroi, “Matcha: fully HA configured OpenStack” at Ops meetup in Palo Alto, lightning talk

What is the scale of your OpenStack deployments?

Our web service infrastructure has 400 hypervisors and 4,800 physical cores. It accommodates more than 1,700 virtual servers in production.

Our backend storage email system has a few hundred nodes to provide the effective capacity of 6.4 Petabytes (PB) and has been in production since January 2015.

More facts about NTT Group

NTT SMARTCONNECT built a service platform for a customer, multiscreen broadcasting conference, which is a general incorporated association, by using OpenStack. The customer provides a content distribution application providing the contents to smartphones and tablets in connection with a TV program, enabling real time communication to TV programs by using websocket. We employed Piston and PLUMgrid to build 5 Piston nodes, 2 PLUMgrid GW servers and one extra server to set up the system, which accommodates 40 virtual servers, 3,000 Input/Output Operations Per Second (IOPS) and nine gigabits per second (Gbps) streaming network capacity. OpenStack enabled us to build the system in a short timeframe and with limited costs. It’s in field trial and working in stable even with burst accesses synchronized by TV broadcast.

NTT Software Innovation Center is using OpenStack to build private cloud for research and development of internal use.

Read more about the Tokyo Superuser Awards finalists here and cast your vote. Voting is limited to one ballot per person, and closes on Monday, October 12th at 11:59 p.m. Pacific Time Zone.

Cover Photo by Guillaume P. Boppe // CC BY NC