• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. What is cloud? Is a term for technologies that provide computation, software, data access, and storage services that do not require end user knowledge of physical location and configuration of the system that delivers the service So basically a user consumes without having to know the details of what happens where and why
  • 2. What most of us visualize
  • 3. Terms that come about Software as a service Infrastructure as a service Platform as a service Everything as a service Computing as a service
  • 4. Terms commonly used Cloud Client Consists of computer hardware or software that depends on the cloud to deliver services and is therefore partially of fully useless without it. Example: Meego Android
  • 5. Cloud Application This is basically cloud computing services or what we know as Software as a service Software is delivered over the internet so no need to install and run application on customers computer thus simplifying tasks such as: Maintenance Support
  • 6. Cloud platform This is commonly known as platform as a service where it delivers a computing platform/solution stack as a service thus consuming cloud infrastructure and sustaining cloud applications Facilitates deployment of applications without need to worry about hardware and software that exists beneath
  • 7. Cloud infrastructure Also known as infrastructure as a service Deliver computing infrastructure as a service such as raw block storage and networking Client need not worry about purchasing servers , software and data center. This is delivered to them and they are charged on a utility basis
  • 8. Server Consists of hardware or software fine tuned to allow the delivery of cloud services such as multi core processors systems and some cloud specific operating systems
  • 9. Diagram of what we get
  • 10. Deployment models Public cloud Community cloud Hybrid cloud Private cloud
  • 11. Architecture of the cloud It is important to recall that the systems architecture or the software systems that exist work on loosely coupled mechanism There exists two main approaches here: The Inter-cloud Cloud engineering
  • 12. Who is the Penguin
  • 13. Linux It is an open source operating system that allows us to modify and redistribute. Key factor: Easy to learn Free Modular based
  • 14. Clear factor!
  • 15. Lets go back to cloud Linux and Cloud relation How does Linux come in Why Linux GlusterFS HekaFS
  • 16. Cloud issues or is it cloudsolutions Privacy Compliance Legal Open source and Open standards Security Sustainability Abuse
  • 17. GlusterFS Is a powerful network/cluster file system written in user space which uses FUSE to hook itself with VFS layer. It takes a layered approach to the file system where features are added and removed as required therefore just like linux it is clearly modular
  • 18. GlusterFS (cont..) It is clearly abstract because it works on the existing file systems that are already there. It therefore easily scales up to petabytes of storage which is made available under a single mount point
  • 19. TermsBrick:-This is a storage file system that has beenassigned to a volumeClient: Machine that mounts the volume (at timesthis may be the server)Server: The machine (virtual or bare metal) thathas the actual file system where the data isstored
  • 20. Terms (cont..) Sub volume:- a brick after being processed by at least one translator Volume:- The final share after passing through all translators Translator: connects to one or more sub volumes and does something with them and offers a sub volume connection
  • 21. What is the commoninfrastructurearchitecture
  • 22. The Distribution Takes a common sub volume and distributes files across them effectively making them one single storage volume from a series of smaller ones
  • 23. Distribution(cont.…)
  • 24. Files and how they arestored If you have for example 4 image files (.JPEG) named a, b, c and d They will be stored across all servers using the distribute translator The server the file is written to is calculated by hashing the filename and if there are changes a pointer file is written to the server
  • 25. Translator pattern
  • 26. Plus and Minus Disadvantage: If a server is lost then all information on that server goes with it, thus to solve this we use a replication translator If your file is larger than the sub volume then your file will fail If the file is not where the hash code translates to then that means there will be extra look up time thus latency on system
  • 27. Plus and minus(cont.) Advantages:- The more the servers the better the system scales in terms of random file access but this is dependent that people are not accessing the same file Increasing volume is done by adding a new server that can be done on the fly
  • 29. HekaFS (cont..) Formally known as CloudFS It is intended to solve problems faced by cloud providers when offering file system access as a service. Already have a database(e.g bigtable) Already have a blob(e.g swift) Already have block storage
  • 30. WHY?What we sometimes need: A file system shared between instances A system to be billed by usage and not your worst case scenario
  • 31. Provider needs: Providers need a single file system to manage Add capacity and bandwidth globally and not per user: James Hamilton “non-correlated peaks” Higher Utilization = lower cost of operation Basic cloud value proposition
  • 32. Provider needs(cont..) Better resource sharing per user. Server-per-user=contention waste Quota, billing, e.t.c
  • 33. Tenant needs Private needs I only see my files and I see my files Private UID/GID Cloud users can make up and UID they want Auth by UID is useless Freedom to manage own users One need not register own users with provider-wide system Tenants can therefore implement own LDAP/Kerberos e.t.c
  • 34. Encryption Purely client side encryption Threat here are normally insider(provider) and not other users Provider with key and ciphertext has plaintext Yes, there is a performance cost Yes, it makes cloudFS harder to implement Yes, Key management is still a problem No, that does not mean that we forego it
  • 35. What cloudFS is not It is not a new distributed file system Been there, done that 20+ engineers for more than 3 years Gaining acceptance even harder than development Enhance an existing and accepted option(GlusterFS) Lets take advantage of the translator architecture It is not about high performance as yet It is not a fork
  • 36. Lets look at File systems What goals have we achieved so far with file systems: NTFS, ext2, ext3 ,glusterFS,PVFSS2 Why don’t we just use the file system as it is ? Simple there are some basics still not covered
  • 37. Grades
  • 38. What do we bring to thetable
  • 39. Performance questions How does it stack up to NFS? What if we run side by side will we get results How does it scale
  • 40. Reads
  • 41. Read scalability-Baremetal
  • 42. Virtualized performance So the bare metal stuff was interesting. Lets play with some virtualization Use KVM Guests running RHEL 6.1
  • 43. Virtualized performance
  • 44. Comparison between VM and baremetal write throughput
  • 45. Where is the increase The guest above was CPU bound. What happens when we try and increase CPU from 2 to 4? Is there any other tuning we can do?
  • 46. Tuning here is just anincrease in VCPU
  • 47. Cont.…
  • 48. CloudFS implimentation
  • 49. What is on the table Namespace isolation ID isolation Network encryption Disk encryption Management interface quota
  • 50. DonePresentation by Frankie Onuonga Twitter : FOnonga