The document discusses OpenStack and its readiness for public service. It questions whether OpenStack is ready to handle issues like scalability, reliability, and security needed for public clouds. OpenStack responds that it provides basic tools and APIs, but that each implementation needs to address weaknesses and ensure their own applications and infrastructure are cloud-ready. It concludes that OpenStack provides open source tools, not complete solutions, and users need to improve upon and test the tools for their own needs.

1. OpenStack
Distance from Public Service
Andrew yongjoon Kong
sstrato.open@gmail.com
Facebook: 엔지니어를 위한 정치

2. Who’s No 1 Cloud
1.
2.
3.
4.
5.
Amazon Web Service.
Force.com
Google App. Engine
Rack Space
Micro Soft Azure

3. When is your heyday?

4. When was the cloud’s heyday

5. Every Body’s Question
• Is OpenStack Ready for the public
service?

6. The Answer from OpenStack
• “Is your Application Ready for the Cloud?”
Open Stack
2010 ~

7. WTF?
• What The F ?
• What is The First?

9. What about you? OpenStack?
you, loosely Coupled?

10. See? MY APIs

11. Your Code is too buggy!

12. OpenStack
• Fix it!
• be quite!
Open Stack
2010 ~

13. You’re saying
you have testing framework.
But it’s not perfect.

14. OpenStack
• You should have your test case set! It‟s
basic(your version of gerrit, test and CI )
Open Stack
2010 ~

15. Your API server’s is the SPOF.
The base component is also
the SPOF

16. OpenStack
• Use your Brain. if you‟re good engineer,
you can solve that issue.
Open Stack
2010 ~

17. Your API’s response result is
not Good enough to tackle
issue.

18. OpenStack
• That‟s your problem. you have to check
through the API, not from response.
Open Stack
2010 ~

19. Your Metering/Monitoring
API(Savanna) is not enough.
because it’s not matured yet
(actually Sucks!)

20. OpenStack
• That‟s your problem. If your infra is
matured enough to serve cloud ? There‟s
that kind of system already.
Open Stack
2010 ~

21. • What about Network?
The Network Node is
SPOF. and
Performance Bottle
neck. I mean the
„Distributed Network
Model‟

22. OpenStack
• That‟s your problem. You should make
„blue print!‟. and Get the proof from
community.
Open Stack
2010 ~

23. • What about user
authentication?
• the keystone is OK?

24. OpenStack
• IF your service is good, you have your
authentication method. make the driver for
keystone.
Open Stack
2010 ~

25. • That means we
should prepare
something for public
service?

26. • We make API. and Give
simple working
scenario. you should
improve that. That’s
what opensource is
working. t
• We are not solution!
• Ask you again “ Are you
ready for the cloud?”

27. By The Way
• KT & Cloudware is hiring