1. Virtualization Techniques & Cloud Computing Ahmed Mekkawy [email_address] This presentation is under creative commons BY-NC-SA license

3. Why do we use it?

4. Is it really a new technology?

6. Why to use it?

7. Is it mature and dependable? Should we use it?

8. Example: Amazon Web Services

12. Isolation and creating protected environment.

13. Testing and evaluation of OS, kernel, or an application.

14. Teaching.

15. Ease of duplication.

16. Relocation (and disaster recovery).

17. Running Application not supported by the host.

18. Green IT.

19. … etc.

21. OS-level Virtualization.

22. Partial Virtualization (Historical, not used).

23. Paravirtualization.

24. Hardware-assisted Virtualization.

26. Pros: Stability, comptability, guest OS is not patched.

27. Cons: resources, porfromance.

29. Pros: low overhead, highest performance.

30. Cons: isolation, stability.

31. Examples: FreeBSD Jails, Solaris Containers, Virtuzzo/OpenVZ.

33. If Dom0 crashed (not the hypervisor), the guest OS still runs fine, anyway you won't be able to control the hypervisor till you reboot.

34. The hypervisor provides API's to the DomU's kernels, which are not actually real kernels, they only interface these API's to the userland, not real kernels.

36. Performance is very good (nothing can beat OS-level virtualizatin in this matter).

38. Both host and guest kernels has to be patched.

40. Performance is very good (nothing can beat OS-level virtualizatin in this matter).

42. Both host and guest kernels has to be patched.

43. Maintainability.

45. Concept: Hardware provides support to run instructions independently for each OS.

46. Implementation: IBM 370 (1972), Intel VT, AMD-V, UltraSparc, and others.

47. Examples: linux KVM, Vmware fusion, M$ VirtualPC, Xen, Virtual Box.

49. Theoritically optimal performance.

51. A “pure” hardware-assisted virtualization approach, using entirely unmodified guest operating systems, involves many VM traps, and thus high CPU overheads; this limits scalability and the efficiency of server consolidation. This performance hit can be mitigated by the use of paravirtualized drivers; the combination has been called “hybrid virtualization”.

55. The most known public clouds are Amazon and Rackspace clouds.

56. Everything is great, it's cheaper, more performant, and sustainable... where's the trick?

58. Stability? Talk to me about it.

59. Security and privacy... duh!

60. RMS harsh words about it.. why is all that buzz?

62. Easy scaling up/down.

63. Virtually unlimited resources.

64. Agility.

65. Cost, on certain situations anyway.

66. Metering, you pay as you go.

68. Cloud is also good in application that are memory intensive but not CPU intensive, e.g RoR applications.

69. It should be suitable soon, this technology have the potential but it just needs to get more mature.

70. If you are a system developer, it's a very good chance to enter this hype now, cause later it will be very complicated (if it's not already late).

72. AWS is based on Xen Virtualization.

74. SimpleDB, Relational DB Services (RDS): Database.

75. Simple Queue Service (SQS), Simple Notifications Service (SNS): Messaging.

76. Simple Storage Service (S3): Storage.

77. Elastic Block Storage (EBS): Storage.

80. The smallest instance type is 1.7G RAM, 1 CPU (1~1.2GHz), 32bit OS. The largest is 68.4 G RAM, 8 CPU (3.25~3.9GHz), 64bit OS.

81. Very Obvious that CPU is the most costy part

82. 2 identical instance with only difference in CPU (1 CPU of 1~1.2GHz Vs. 2CPUs of 2.5~3GHz), both are 1.7G RAM, 32 bit OS. The price difference is exactly double.

84. EBS can be mounted to a single EC2, which is bad limitation.

85. S3 is to be accessed via http protocol, can be a great help in serving static http files from outside your servers.

86. Thank You [email_address]