korejanai story

Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015

Korejanai Story

Oct 29, 2015 Kentaro Takeda [email protected] Kensuke Ishizu

1

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

mailto:[email protected]


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

Copyright © 2015 NTT DATA Corporation OpenStack Summit | Tokyo 2015 3

27 user stories presented

https://openstacksummitoctober2015tokyo.sched.org/overview/type/user+stories





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


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


Reality Expectation

https://www.flickr.com/photos/cgpgrey/5023794412/

https://www.flickr.com/photos/cgpgrey/5023794412/

https://creativecommons.org/licenses/by/2.0/


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”.


https://www.flickr.com/photos/gumuz/7340412/

https://www.flickr.com/photos/gumuz/7340412/



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


Basic concept

10


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


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

https://www.flickr.com/photos/dskley/15447707963

https://www.flickr.com/photos/dskley/15447707963

https://creativecommons.org/licenses/by-nd/2.0/




http://www.oxforddictionaries.com/definition/american_english/service

http://www.oxforddictionaries.com/definition/american_english/service


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


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


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


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

https://www.flickr.com/photos/docsearls/5500714140/

https://www.flickr.com/photos/docsearls/5500714140/




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/ .

https://www.flickr.com/photos/iqremix/15680326587

https://www.flickr.com/photos/iqremix/15680326587

https://creativecommons.org/licenses/by-sa/2.0/




https://www.flickr.com/photos/48722974@N07/5249420021

https://www.flickr.com/photos/48722974@N07/5249420021




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


App division Infrastructure division

Workflow of IaaS

19

1. Get resources

(self-service)

Line of business

Apps

App developers Architect

App users

Operators


Agility vs Individuality

20

ind

ivid

uality

ability

to m

eet in

div

idual re

quire

ments

agility speed to adjust resources according to changes

IaaS

Server Consolidation


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


Korejanai Examples

22


App division


Good Case

23

OpenStack

1. Request resources

Compute Node Compute Node Compute Node

VM VM VM VM VM VM VM VM VM

2. Provision resources

3. Provide resources

VM VM

VM


App division

Korejanai Case A “1 request / year”

24


OpenStack





1 request / year

Frozen VMs VM Life-Cycle > 1Y


VM VM

VM


App division

Korejanai Case A “1 request / year”

25


OpenStack

1. Get resources




1 request / year

These will be not moved a long time


VM VM

VM

“It takes unnecessary cost for OpenStack.”


Korejanai Case B “Human nova scheduler”

26

OpenStack


Compute Node New Compute Node Compute Node


1. Request for resources

2. Resource scheduling

3. Procure ＆

Build

5. Build resources

Design with every request

Procure according to request

Architect App developers

Excel…


Korejanai Case B “Human nova scheduler”

27

OpenStack


Compute Node New Compute Node Compute Node



2. Resource scheduling

3. Procure ＆

Build

5. Build resources


Procure according to request


Excel…

“It takes a long time to get resources.”

“It is impossible to change resources flexibly.”

“Provisioning and managing resources by human”


NW devices

Korejanai Case C “Human neutron”

28

OpenStack


2. Network design



Specify vlan-id



5. Build resources

3. Configuration for NW device

Manual configuration


Excel…


NW devices

Korejanai Case C “Human neutron”

29

OpenStack


2. Network design



Specify vlan-id



5. Build resources

3. Configuration for NW device

Manual configuration


“It takes a long time to get resources.”

“It is impossible build NW flexibly & quickly.”

Excel…


Korejanai Case D “Physically separated NW”

30

OpenStack


Compute Node (Public)

Compute Node (Internal2)





3. Build resources

VM VM

VM

NW is separated physically

(security policy)



Korejanai Case D “Physically separated NW”

31

OpenStack


Compute Node (Public)






3. Build resources

VM VM

VM

NW is separated physically

(security policy)


“It is impossible to build NW flexibly.”


Things we need to remember

32


Service and product options

Consolidation IaaS

Public (service)

Hosting Collocation Managed services

Private (product)

33


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


https://www.flickr.com/photos/jeepersmedia/15006639941/

https://www.flickr.com/photos/jeepersmedia/15006639941/


http://www.slideshare.net/masahito12/matcha-51836442





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


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

korejanai story

Technology