Kirin User Story: Migrating Mission Critical Applications to OpenStack Private Cloud.

Copyright © 2015 NTT DATA Corporation
Wednesday, 28 October 2015
Atsushi Koga, Motoki Kakinuma
User Story:
Migrate all Kirin enterprise applications to
OpenStack private cloud

3Copyright © 2015 NTT DATA Corporation
Troubleshooting

Corporate Data
■ Name:
NTT DATA Corporation
■ Head Office:
Toyosu Center Building,
3-3, Toyosu 3-chome,
Koto-ku, Tokyo 135-6033, Japan
■ Established:
May 23, 1988
■ Common Stock:
142,520 million (as of March 31, 2014)
■ Fiscal Year:
April 1 to March 31 of the following year
■ URL:
http://www.nttdata.com
■ Business Areas:
- System integration
- Networking system services
- Other business activities related
to the above
1. About NTT DATA
1988 NTT DATA Communications Systems Corporation spun
off into a separate company from NTT
1995 Listed on the Second Section of the Tokyo Stock Exchange
1996 Changed English name to NTT DATA Corporation
Listed on the First Section of the Tokyo Stock Exchange
2007 Achieved consolidated net sales of 1 trillion
2008 20th anniversary of establishment
2012 Start of four-year Medium-Term Management Policy
(covering the period to March 31, 2016)
2013 25th anniversary of establishment
Overview of NTT DATA History

Provides high-value-added global IT services
that support manufacturing, distribution,
services, media, communications
and other business activities.
Offers platforms and solutions
that support cutting-edge IT services.
Provides high-value-added IT services
that support public administration,
healthcare, finance, settlement and other
systems that form the social foundation.
Segments of NTT DATA
Enterprise IT Services
(E-IT)
Public & Financial
IT Services
(P&F)
Provides high-value-added IT
services in overseas markets.
Solutions & Technologies
(S&T)
Global Business
(GB)
Note: Per-segment data includes internal transactions.
1. About NTT DATA

Bases
Status of Overseas Bases
1. About NTT DATA

Kirin Group Overview （December, 2014）
Trade Name
Date of Incorporation
Paid-in Capital
Head Office
Number of Employees
Business
Kirin Holdings Company, Limited
February 23, 1907（Kirin Brewery Co., Ltd.）
102 billion yen
Nakano, Tokyo
39,922
Alcohol Beverages, Soft Drinks, Pharmaceuticals,
Biochemical, etc…
Corporate Philosophy

8
(Unit: 100 million yen)
Business Segment （December, 2014）

nfrastructure
 Solving creaky infrastructure becomes an big issue in Kirin.
• Kirin has managed various types of infrastructure as below.
BCPBCP

Issues to be solved in Kirin (1)
0
100
200
300
400
500
600
700
FAT シンクラ2015 2016 2017 20182014……

Drastic reduction in
Infrastructure cost
2015 2018
Issues to be solved in Kirin (2)

Why we adopt OpenStack?
- Simple Architecture.
- Extensive enterprise level experience over the world.
- Quick bug report and fix by community members.
- Not just an IaaS, there is a possibility to be a PaaS
with customize.
- Start small, go big.
- “Selecting optimal hardware for each customer” is
NTTDATA’s way.
Sophisticated
Flexibility
Vendor
Neutral

Our Challenges
Full
Automation
• Deployment
automation
• Testing automation
Mass
migration
• Mission Critical
• Minimal downtime
• Quick migration
Drastic cost
reduction
• Operational
efficiency
• Small start to avoid
buying extra server
scale
migration
main
topic
One-Stop deployment

Estimated introduction effects
Apply
for
deploy
confirm
by
admin
Internal
review
Requirement
definition
Design
server
Build
&
Test
Release
Full automated deployment methods
Usual deployment methods
Apply
for
deploy
confirm
by
admin
Internal
review
Build & Test Release
FULL AUTOMATION
Cost reduction effect estimate: 75% OFF per server

Kirin OpenStack Overview
 Kirin OpenStack is fully automated and optimized private
cloud system.
Kirin
OpenStack
3. Consistent inventory management
1. Deployment automation 2. Testing automation

 Kirin EA user sends a deployment request to the Kirin EA(web
application), then build process is started automatically.
1. Deployment automation
User Kirin EA
(Web application)
OpenStack
Request Build
Kirin OpenStack

 Kirin EA enables to us,
 3 Operating systems deployment
• Windows Server 2012 R2/2008 R2
• Red Hat Enterprise Linux 6.6
 11 middleware deployment
• Java, Apache, Tomcat, Hinemos, JP1, Security Software,
SQL Server, etc..
 800+ parameters setting
• Kernel parameter, create OS user/group, create DB user,
• Active Directory, Windows-Feature, etc...

Kirin EA screen sample
password
disk
hostname
network
middleware
select
version
check if
install

Kirin EA screen sample (e.g. Apace HTTP Server)
change paramater of
kernel settings (/etc/sysctl.conf)
change parameter of
/etc/sysconfig/httpd
change parameter of
/etc/httpd/httpd.conf

 Kirin EA registers instances with Big-IP/Hinemos automatically.
Operator
1. Deployment
Request
Kirin EA
3. register
Big-IP

 Kirin EA suspends balancing/monitoring setting from Big-
IP/Hinemos automatically.
 Resume also works.
Operator
1. Instance
stop
3.Stop instances
Kirin EA
2. suspend
Big-IP

2. Testing automation
 Mission: “Getting automatically tested server.”
 Testing automation enables to reduce the costs almost exactly
zero compared to usual manually methods.
 Kirin EA testing automation consists of,
• Parameter test
• Function test (e.g. process-start/stop, log error check)
• Apache-Tomcat(modjk) connectivity test
• DB access test
• Load-balancing(BIG-IP) test
• Monitoring(Hinemos) test ..etc

• Testing tools
1. Serverspec
• Parameter check, state check, command result check..etc
2. Original scripts
 BIG-IP test
• Health check works correctly?
• Failover works correctly in the case of server down?
 Hinemos test
• Registered correctly?
• Monitoring is started correctly?
 DB (Oracle) test
• Databases access works correctly with new user?
describe file('/etc/sysconfig/i18n') do
its(:content) { should match("^LANG=ja_JP.UTF-8") }
end
e.g.

• Test result is reported automatically.
• In the case of Linux deployment with full middleware, +140
test cases will be executed.
Test results summary
Automated test report
Test result summary
OK or NG
Server information
Test score

• Before Kirin OpenStack implementation, IT assets were managed
inconsistent way.
…by the way, how many servers we have?
does anyone know it?

• Kirin EA uses “metadata service” in order to tag servers with
metadata.
• Kirin EA user can get all server list anytime.
“application number": "12345",
“sector name”: “sales group",
“ipaddress-01": “10.1.10.23",
"os": "Windows2012R2“,
“cpu”: “2”,
“memory”:”8GB”
middlewares:[
“Java JRE 8u60”
“Apache Tomcat”
・・・
metadata sample
get sever list!

• Kirin EA also manages servers which are moved from other
infrastructure by P2V or V2V.
• Operator inputs metadata manually on each server after
migration.
P2V
V2V
EOL
EOL
metadata
metadata

How we implemented OpenStack?
• Install OpenStack was completely easy.
 IBM OpenStack provides each OpenStack Component as a
VMWare virtual server.
• Implementation of availability.
 Use the VMware HA technology.
Compute Cluster
OpenStack
components
VMware HA
Storage
Controller Cluster
VMware #1 VMware #2
nova
cinder
neutron
keystone
VMware HA

How we use the OpenStack?
• OpenStack version: Icehouse
• Virtual technology: VMware
• Used components:
• Nova, Cinder, Neutron, Keystone.
 Implementing OpenStack is NOT our primary purpose.
 Stable, cost effective, easy to use and easy to operate
platform is customer requirement.
We implemented OpenStack as simple as possible.

４．Summary and suggestions

Summary and suggestion
Summary
Suggestion
 It is sufficient to implement IaaS with OpenStack as an
enterprise level.
 Not only automated building, but also automated
testing is effective.
 Retaining aging IT infrastructure with OpenStack will
spreads more and more in Japan.
1. Using OpenStack as PaaS
 Fast and easy implementation of PaaS function on
OpenStack is helpful.
2. Hybrid Cloud
 API compatibility for AWS
3. Software-defined infrastructure with converged
infrastructure
 Free from management of Storage on OpenStack.

All product names mentioned are trademarks or registered trademarks of the respective companies.
記載されている商品名はみな各社の商標または登録商標です

Kirin User Story: Migrating Mission Critical Applications to OpenStack Private Cloud.

More Related Content

What's hot

Viewers also liked

Similar to Kirin User Story: Migrating Mission Critical Applications to OpenStack Private Cloud.

Recently uploaded

Kirin User Story: Migrating Mission Critical Applications to OpenStack Private Cloud.