1. edubase Cloud
on the
OpenStack
Osamu Habuka
@habuka036
NTT DATA INTELLILINK Corp.
2012/10/15

2. about me
●chairman of Eucalyptus Users Group Japan
◇I'm the number one fan of Eucalyptus in Japan.
◇I published a book of Eucalyptus in Japanese
◇I have a series of web articles of Eucalyptus
in Japanese.
1

3. Of course,
I like
OpenStack
2

4. but actually,
I love
Eucalyptus
3

5. I love CLC
4

6. I love CC
5

7. I love NC
6

8. I love
SC/Walrus
7

9. Eucalyptus
running in
the USA
8

10. in Japan
9

11. at Companies...
on Campuses...
10

12. on my desk
11

13. 12

14. but
today is OpenStack
day.
so, shall we get down
to main subject.
13

15. edubase Cloud
on the
OpenStack
14

16. Eucalyptus
coexists with
OpenStack
15

17. What is edubase Cloud?
edubase Cloud is the IaaS for
students at the National
Institute of Informatics (NII)
This IaaS is
made of
Eucalyptus!
(CLCx1,CCx1,NCx14)x10 +
(CLCx1,CCx1,NCx6)x5 = This system is very very... very
almost 1360 VMs good
16

18. this system has some issues.
17

19. Some Problems…
● took a long time to build
◇Many configurations/tunings were need
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS
18

20. Some Problems…
● took a long time to build
◇Many configurations/tunings were need
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS
19

21. Some Problems…
● took a long time to build
◇Many configurations/tunings were need
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS
20

22. Some Problems…
● took a long time to build
◇Many configurations/tunings were need
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS
21

23. Some Problems…
● took a long time to build
◇Many configurations/tunings were need
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS
22

24. Problems Solved!
● took a long time to build
◇Many configurations/tunings were need
-> by dodai-deploy
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
◆ Of course, the same can be said for any other
IaaS.
23

25. Problems Solved!
● took a long time to build
◇Many configurations/tunings were need
-> by dodai-deploy
because edubase Cloud's Eucalyptus is a
custom edition.
● inflexible
◇Eucalyptus system is on the hardware itself,
so it’s hard to scale up/down the node
controller.
-> by dodai-compute
◆ Of course, the same can be said for any other
IaaS.
24

26. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
25

27. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
26

28. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
27

29. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
28

30. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
29

31. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
30

32. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
31

33. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
32

34. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
33

35. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
34

36. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
35

37. dodai...what?!
●dodai-deploy
◇It's a Deployment tool!
◇But it's NOT just any deployment tool.
◇You will have a memorable experience thanks to
"Install as a Service".
●dodai-compute
◇It's Bare-metal as a Service by OpenStack!
◇But it's NOT just any Bare-metal as a Service.
◆ derived from Essex? NO!
◆ Folsom? NO!
◆ Diablo!
◇We are planning to customize Folsom.
36

38. What we did
●First, We deploy Eucalyptus using dodai-
deploy.
◇Ubuntu 12.04 with Eucalyptus 3.1
◇However, edubase Cloud only works on CentOS 5.
◆ dodai-deploy does notwork yet on CentOS 5...
◆ Why did I select that? Because I like newest
version...
●Next, We made machine images for edubase
Cloud.
◇CLC(included walrus, sc) image
◇CC image
◇NC image
37

39. What we did
●It only takes 3 steps to build a cloud.
1. Run instances using the machine images.
2. Configure eucalyptus.conf on CC.
3. Register all components to CLC/CC.
A M I
Diablo
dodai-compute
resource pool
38

40. What we did
●It only takes 3 steps to build a cloud.
1. Run instances using the machine images.
2. Configure eucalyptus.conf on CC.
3. Register all components to CLC/CC.
A M I
Diablo
dodai-compute
resource pool
39

41. What we did
●It only takes 3 steps to build a cloud.
1. Run instances using the machine images.
2. Configure eucalyptus.conf on CC.
3. Register all components to CLC/CC.
A M I
Diablo
dodai-compute
resource pool
40

42. What we did
●It only takes 3 steps to build a cloud.
1. Run instances using the machine images.
2. Configure eucalyptus.conf on CC.
3. Register all components to CLC/CC.
A M I
Diablo
dodai-compute
resource pool
41

43. What we did
● Q: scale up?
● A: Yes!!! 2 steps only.
◇ 1. RunInstances
◇ 2. euca_conf --register-nodes
A M I
Diablo
dodai-compute
resource pool
42

44. What we did
● Q: scale up?
● A: Yes!!! 2 steps only.
◇ 1. RunInstances
◇ 2. euca_conf --register-nodes
A M I
Diablo
dodai-compute
resource pool
43

45. What we did
● Q: scale up?
● A: Yes!!! 2 steps only.
◇ 1. RunInstances
◇ 2. euca_conf --register-nodes
A M I
Diablo
dodai-compute
resource pool
44

46. What we did
● Q: scale up?
● A: Yes!!! 2 steps only.
◇ 1. RunInstances
◇ 2. euca_conf --register-nodes
A M I
Diablo
dodai-compute
resource pool
45

47. Please join us!
Mr.Guan will talk to you
in Manchester D
at 5:20 pm tomorrow,
And give you all the details
about dodai.
Thank you!
46