Exploration of eucalyptus_v2.0


Published on

Published in: Technology
  • 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

No notes for slide

Exploration of eucalyptus_v2.0

  1. 1. Exploration Of Eucalyptus
  2. 2. Cloud Computing Service Layers SaaS (Software as a Service) Cloud Application PaaS(Platform as a Service) Cloud Software Environment Cloud Software Infrastructure IaaS (Infrastructure as a Service) www.themegallery.com
  3. 3. Details cooperation CRM/ERP/HR transaction Enterprise Application Software as a ServiceS middleware Web 2.0a High Volume Java Transactionsa P database Development toolsS a a I Platform as a Service S a a Data Center Servers network storage S Fabric Dynamic scaling Infrastructure as a Service
  4. 4. IAAS• Infrastructure as a Service is a provision model in which an organization outsources the equipment used to support operations, including storage, hardware, servers and networking components. servers storage networking
  5. 5. Characteristics and components of IAAS • Automation of administrative tasks • Virtualization • Dynamic scaling • Desktop virtualization • Policy-based services • Internet connectivity
  6. 6. Virtualization Applications Applications … … … Windows/Linux Windows/Linux Applications … KVM / Xen / VMware Windows/Linux Windows/LinuxPhysical Resources Physical Resources
  7. 7. Applications Applications … … … One … Windows/Linux Windows/Linux KVM / Xen / VMware Or Windows/Linux More Physical Resources Eucalyptus(Used to Manage/Control a set of physical machines with virtual machines running in them)
  8. 8. Eucalyptus Introduction• A software platform for the implementation of private cloud computing on computer clusters.• There is an open-core enterprise edition and an open-source edition.• Began as a research project in the field of high performance computing (HPC) under the direction of Professor Rich Wolski in the Computer Science Department at the University of California, Santa Barbara.
  9. 9. Eucalyptus Architecture• Distributed System – Components implemented as webservice• Components run on top of existing resources – Linux distribution agnostic • Ubuntu, RHEL, CentOS, Debian, opens USE – Hypervisor agnostic • Xen, KVM, VMware
  10. 10. Eucalyptus Architecture
  11. 11. Eucalyptus Architecture• CLC(Cloud Controller) – User interface to interact with the cloud • Standard SOAP API matching the Amazon EC2 API • Query Interface – Euca2ools and ElasticFox – Talks with the Cluster Controllers(CC) • Holds all information linking users to running instances • Collection of available machines to be run • View of the load of the entire system
  12. 12. Eucalyptus Architecture• WS3(Walrus Storage Controller) – Storing the machine images (MI) that can be instantiated on the cloud – Accessing and storing data (either from a running instance or from anywhere on the web) Note: Currently the machine on which the Cloud Controller runs also hosts the Walrus Storage Controller (WS3), this limitation will be removed in a forthcoming version
  13. 13. Eucalyptus Architecture• CC(Cluster Controller) – Receive requests to allocate MI (machine images) from the Cloud Controller – Decides which Node Controller will run the Minst (machine instance) – Manage any virtual networks that the MInst run in and routing traffic to and from them – Runs the EBS Controller• EBS(Elastic Block Storage Controller) – Provides block-level network storage that can be dynamically attached by VMs
  14. 14. Eucalyptus Architecture• NC(Node Controller) – Runs on the physical machines on which the MI(machine image) will be instantiated – When request to start a it will: • 1. Verify the authenticity of the user request • 2. Download the image from WS3 • 3. Create the requested virtual network interface • 4. Start the instance of the machine image running as a virtual machine (VM) – Stopping a virtual machine corresponds to performing the opposite operations
  15. 15. Deploy of EucalyptusThree typical types of deployment
  16. 16. Deploy of EucalyptusDifferent eucalyptus packages should be install intodifferent controllers(CLC, CC, NC). Below is a typicalstructure of a NC.VMI (Virtual Applications ApplicationsMachine Instances) … … … Linux LinuxA Node Controller Eucalyptus packages for NC Hypervisor KVM / Xen Host OS Linux Physical Resources
  17. 17. Our Eucalyptus CloudWe have two machines to deploy the Cloud. One is an IBMServer with 16G memory, we use it as a Node Controller.The other is a ordinary PC with 3G memory .
  18. 18. Our Eucalyptus CloudThe Commandto show therunninginstances EMI EKI ERI Instance Id Internal External VM Type IP IP
  19. 19. • EMI(Eucalyptus Machine Image), EKI(Eucalyptus Kernel Image), ERI(Eucalyptus Ramdisk Image) – To run an instance of a VM image, the image must be associated with a qualified kernel and ramdisk image.• Internal IP – Private IP used to communicate between instances in the same security group• External IP – Public IP connects to the instance and is subjected to the security group rules• VM Types – The type of the running instances
  20. 20. Our Eucalyptus CloudWe can manage and controlthe cloud by provided webinterface.URL: From the web interface wecan configure manyattributes for the cloud.e.g. There are five VM typesprovided by eucalyptus. Wecan manually configure thesize for them.
  21. 21. Comparison between enterpriseand open source Eucalyptus Feature Open Source Enterprise Edition Comparison Amazon AWS interface Compatibility O O Flexible Clustering and Availability O O Network Management, security Groups , Traffic Isolation O O Cloud Semantics and Self- Service Capability O O Bucket-Based Storage Abstraction(S3-Compatible) O O Xen and KVM Hypervisor Supported O O
  22. 22. Eucalyptus Feature Open Source Enterprise Edition ComparisonVMWare Hypervisor Support X O Virtual-Virtual Image Conversion for VMWare X O Microsoft Windows Guest Support X O Direct SAN Integration X O Quota Management and Accounting X O User and Group Access Management X O High-Performance MySQL Database Backend X O
  23. 23. Commonly used Command Instance  Volume – euca-describe-instances – euca-describe-volumes – euca-run-instances – euca-attach-volume – euca-start-instances – euca-create-volume – euca-terminate-instances – euca-delete-volume – euca-reboot-instances – euca-detach-volume Address  Group – euca-describe-addresses – euca-describe-group – euca-allocate-address – euca-add-group – euca-associate-address – euca-delete-group – euca-disassociate-address – euca-release-address