Kentaro Takeda and Kensuke Ishizu of NTT DATA presented on common misunderstandings enterprises have about OpenStack and how it differs from traditional infrastructure models. They explained that OpenStack is software for building infrastructure as a service (IaaS) and outlined key differences between IaaS and traditional server consolidation approaches. Specifically, IaaS follows a "cattle not pets" approach where infrastructure resources are treated as interchangeable and provisioned on-demand, unlike dedicated server silos. The presentation provided examples of how enterprises sometimes try to use OpenStack in ways that don't align with its IaaS model, resulting in projects deemed "Korejanai" or "not it".

1. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Story
Oct 29, 2015
Kentaro Takeda takedakn@nttdata.co.jp
Kensuke Ishizu
1
Any product name, service name, software name and other marks are trade
mark or registered mark of corresponding companies.
記載されている会社名、商品名、又はサービス名は、各社の登録商標又は商標です。

2. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
About us
• Kentaro Takeda / 武田健太郎 (a.k.a. takedakn)
• Technical consultant
• Kensuke Ishizu / 石津健佑 (a.k.a. ishiduk)
• Platform engineer
• About NTT DATA: System Integrator for enterprises
– OpenStack Customers:
• Telco: NTT DOCOMO (Swift)
• Enterprises: KIRIN (Nova)
• Public sectors
• etc.
2

3. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 3
27 user stories
presented
https://openstacksummitoctober2015tokyo.sched.org/overview/type/user+stories

4. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Frequently found (and not disclosed) enterprise user stories
1. Inquire about OpenStack
2. Receive explanations and see demo
3. (PoC)
4. Find big gap between expectation and reality
5. Say “Korejanai!” / “It’s not this!”
4

5. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Purpose of this session
Improve percentage of “successful engagement with OpenStack”
Reduce number of “unsuccessful engagement with OpenStack”
5


How to increase
# of engagements




How to make
everyone happy


 Successful engagement
Unsuccessful engagement
not covered,
please ask Marketer
not covered,
please find Socialistcovered in this session




How to reduce
# of unsuccessful
engagements

6. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 6
RealityExpectation

7. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
One biggest expectation from enterprises
“OpenStack is cheap
replacement for our old-
fashioned infrastructure”
7
Open source?
It must be cheap!
“Cloud” should mean “infrastructure”.
We can simply replace our one with “cloud”.

8. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 8

9. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Why no?
• OpenStack brings some painful paradigm
shift for enterprises.
• The transition cost would not be so low.
• And simply replacing existing infrastructure
will never go well.
• If the company is not ready to change the
way of thinking, you will say “Korejanai!” /
“It’s not this!”.
9

10. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Basic concept
10

11. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
What we need to understand
• OpenStack: Software to build IaaS
–Even though many misleading marketing
statements are there, this is definitely true.
• IaaS: Infrastructure as a Service
• Infrastructure: Server, Storage, Network
• “As a service”
11

12. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
What is “Service”?
• Service serv·ice /ˈsərvəs/
– A system supplying a public need such as
transport, communications, or utilities such as
electricity and water: a regular bus service
• A few service providers
• Many users
12
“Service” by Dennis Skley available at
https://www.flickr.com/photos/dskley/15447707963
under a Creative Commons Attribution-NoDerivatives 2.0.
Full terms at https://creativecommons.org/licenses/by-nd/2.0/ .
service: definition of service in Oxford dictionary (American English)
http://www.oxforddictionaries.com/definition/american_english/service

13. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Healthy relationship b/w service provider and users
• Service provider:
– Focus on the normal service operations.
– Listen to users and continuously improve the service.
• Service users:
– Understand the service menu and make use of it.
– Send any feedback to the service provider for improvement.
13
user
service
provider
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user

14. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Healthy relationship b/w service provider and users
• Service provider: “keep detached from each user”
– Focus on the normal service operations
– Listen to users and continuously improve the service
• Service users: “don’t expect dedication from service”
– Understand the service menu and make use of it
– Send any feedback to the service provider for improvement
14
user
service
provider
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user

15. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Healthy relationship b/w IaaS and users
• Service provider: “keep detached from each user”
– Focus on the normal service operations
– Listen to users and continuously improve the service
• Service users: “don’t expect dedication from service”
– Understand the service menu and make use of it
– Send any feedback to the service provider for improvement
15
user
IaaS
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
user
Just use it
Provide infrastructure

16. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Infrastructure not like a service
• Just a Consolidation.
– Consolidate many servers, and build silos.
– Single or a very few number of users.
– Each silo is dedicated to specific user.
16
user user user user

17. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Pet vs Cattle
• Server Consolidation: treat servers like pet
– Highly available servers
• IaaS: treat servers like cattle
– Highly available apps on set of servers
17
“Shiba Inu all Dressed up” by IQRemix available at
https://www.flickr.com/photos/iqremix/15680326587 under a Creative Commons Attribution-ShareAlike 2.0.
Full terms at https://creativecommons.org/licenses/by-sa/2.0/ .
“Livestock production” by eutrophication&hypoxia available at
https://www.flickr.com/photos/48722974@N07/5249420021 under a Creative Commons Attribution 2.0.
Full terms at https://creativecommons.org/licenses/by/2.0/ .

18. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
App division
Infrastructure division
Line of business
Workflow of Server Consolidation
18
Operators
App developers
App users
Apps 2. build and
arrange
resources
Architect
3. provide
resources
1. request for
resources

19. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
App division
Infrastructure division
Workflow of IaaS
19
1. Get
resources
(self-service)
Line of business
Apps
App developers Architect
App users
Operators

20. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Agility vs Individuality
20
individuality
abilitytomeetindividualrequirements
agility
speed to adjust resources according to changes
IaaS
Server
Consolidation

21. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Examples
• OpenStack itself is just software.
• So we can integrate it even in a not suitable
manner.
• Here’re some real/unreal examples of
“Korejanai OpenStack”.
21

22. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Examples
22

23. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
App division
App developers Architect
Good Case
23
OpenStack
1. Request
resources
Compute Node Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
2. Provision
resources
3. Provide
resources
VM VM
VM

24. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
App division
Korejanai Case A “1 request / year”
24
App developers Architect
OpenStack
1. Request
resources
Compute Node Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
2. Provision
resources
1 request / year
Frozen VMs
VM Life-Cycle > 1Y
3. Provide
resources
VM VM
VM

25. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
App division
Korejanai Case A “1 request / year”
25
App developers Architect
OpenStack
1. Get
resources
Compute Node Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
2. Provision
resources
1 request / year
These will be not
moved a long time
3. Provide
resources
VM VM
VM
“It takes unnecessary cost for OpenStack.”

26. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Case B “Human nova scheduler”
26
OpenStack
4. Request
resources
Compute Node New Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
1. Request for
resources
2. Resource
scheduling
3. Procure
＆
Build
5. Build
resources
Design with
every request
Procure
according
to request
ArchitectApp developers
Excel…

27. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Case B “Human nova scheduler”
27
OpenStack
4. Request
resources
Compute Node New Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
1. Request for
resources
2. Resource
scheduling
3. Procure
＆
Build
5. Build
resources
Design with
every request
Procure
according
to request
ArchitectApp developers
Excel…
“It takes a long time to get resources.”
“It is impossible to change resources flexibly.”
“Provisioning and managing resources by human”

28. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
NW devices
Korejanai Case C “Human neutron”
28
OpenStack
4. Request
resources
2. Network
design
Design with
every request
ArchitectApp developers
Specify vlan-id
Compute Node Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
5. Build
resources
3. Configuration
for NW device
Manual
configuration
1. Request for
resources
Excel…

29. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
NW devices
Korejanai Case C “Human neutron”
29
OpenStack
4. Request
resources
2. Network
design
Design with
every request
ArchitectApp developers
Specify vlan-id
Compute Node Compute NodeCompute Node
VM VM VM VM VM VM VM VM VM
5. Build
resources
3. Configuration
for NW device
Manual
configuration
1. Request for
resources
“It takes a long time to get resources.”
“It is impossible build NW flexibly & quickly.”
Excel…

30. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Case D “Physically separated NW”
30
OpenStack
2. Request
resources
Compute Node
(Public)
Compute Node
(Internal2)
Compute Node
(Internal1)
4. Provide
resources
ArchitectApp developers
VM VM VM VM VM VM VM VM VM
3. Build
resources
VM VM
VM
NW is separated
physically
(security policy)
1. Request for
resources

31. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Korejanai Case D “Physically separated NW”
31
OpenStack
2. Request
resources
Compute Node
(Public)
Compute Node
(Internal2)
Compute Node
(Internal1)
4. Provide
resources
ArchitectApp developers
VM VM VM VM VM VM VM VM VM
3. Build
resources
VM VM
VM
NW is separated
physically
(security policy)
1. Request for
resources
“It is impossible to build NW flexibly.”

32. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Things we need to remember
32

33. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Service and product options
Consolidation IaaS
Public
(service)
Hosting
Collocation
Managed services
Private
(product)
33

34. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Simple decision tree
34
Need IaaS?
OK to use
public service?
Just use it!
Build your own IaaS!
Build your own silos!
or
on premise
y
n
y
n

35. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 35

36. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015
Conclusion
• OpenStack is software to build IaaS.
• IaaS brings some painful paradigm shift for
enterprises.
• Even though there are some pain relievers,
essentially you need to change the way of
thinking:
– Don’t expect dedication from service; service is
for many users.
– Treat infrastructure resources like cattle, not like
pet.
• If you’re not willing to have the new way of
thinking, just forget about IaaS.
36

37. Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 37
Any product name, service name, software name and other marks are trade
mark or registered mark of corresponding companies.
記載されている会社名、商品名、又はサービス名は、各社の登録商標又は商標です。