Setting up a private cloud for academicenvironment with open source software         Cloud Computing Course             IT...
Who am I?   Zoran Pantić   Infrastructure Architect & Systems Specialist    Corporate IT @ University of Copenhagen       ...
Agenda Non-technical part:   A bit about the project   Why OSS?   Focusing on academic environments Technical part:   UEC/...
Project: Implementing private cloudsolution in academic environments Based on Open Source Software (OSS) Focus on the logi...
Why OSS?In general:   Lowering the costs (no licensing headaches!)   Interchangeability & portability (general)   Socio-or...
Academic environments – why privatecloud? Usually, the budget is low, and the project should start as soon as possible Gro...
Academic environments – why privatecloud? (continued)Private clouds:  Higher ROI than traditional infrastructure  More cus...
Academic environments – private cloudchallengesChallenges: Sociological Technological
Academic environments – private cloudsociological challengesSociological challenges, mostly political and economic:    Exi...
Academic environments – private cloudtechnological challengesTechnological challenges:  Private cloud maturity,  Problems ...
Suggestions for implementing cloudsolutions in academic environments  To determine the needs and their nature, consult the...
Focus on academic environments Difference in implementing for “infantry” and “supply troops” “Infantry” - to support resea...
Academic environments – “Infantry” Uses non-standard & advanced research instruments Applicable in research, scientific co...
Academic environments – “Infantry”(continued)Summarized suggestions    Have social psychology in mind as important factor ...
Academic environments – “Infantry” –UEC WebGUI
Academic environments – “Infantry” –HybridFox
Academic environments – “Supply” Needs a stable and supported solution Summarized suggestions   Have social psychology in ...
Academic environments – “Supply” –VMware vSphere
UEC/Eucalyptus componentsUEC/Eucalyptus is an on-premise private cloud platform,designed as a distributed system - a modul...
UEC/Eucalyptus levelsThree levels:  Cloud level    Cloud Controller (CLC)    Walrus Storage Controller (WS3)  Cluster leve...
Cloud Controller (CLC) Entry point to Eucalyptus cloud   web interfaces for administering the infrastructure   web service...
Walrus Storage Controller (WS3) Equivalent to Amazon’s S3 Bucket based storage system with put/get storage model WS3 is st...
Cluster Controller (CC) Entry point to a cluster Manages NCs and instances running on them Controls the virtual network av...
Storage Controller (SC) Allows creation of block storage similar to Amazon’s Elastic Block Storage (EBS) Provides the pers...
Node Controller (NC) Compute node (“work horse”) Controls the instances supported hypervisors: KVM (preferred) and Xen in ...
Reflections on hardware Processor architecture:   Definitely 64-bit – for performance reasons   Multiprocessor, multicore,...
Reflections on software Ubuntu versions:   Newest – new features, but less stability (more bugs)   LTS (Long Time Support)...
Reflections on network 2 or 3 networks: WAN, Cloud public & Cloud private Firewall: open source based pfSense - to make th...
Reflections on redundancy No redundancy available in UEC – by design In case of software or hardware error on a component:...
Scaling out the environment     CLUSTER 1CLOUD   CLUSTER 2                                  CLUSTER                       ...
Suggested scaling out possibilities 2 physical servers   Server 1: CLC/WS3/CC/SC   Server 2: NC 3 physical servers:   Serv...
Suggested scaling out possibilities 4 physical servers   Server 1: CLC   Server 2: WS3   Server 3: CC/SC   Server 4: NC 5 ...
Conclusion & recommendations forprivate clouds based on open source Although still at an early stage, being hard to instal...
Alternative – public clouds  More mature  Well documented  Rich with features  Easy to useExamples:Amazon’s initiatives fo...
Questions            ?
DemoDemonstration of UEC environment and WebGUI
Thank you!      Thank you for your attention!             Still having questions?                   zopa@itu.dk           ...
Upcoming SlideShare
Loading in …5
×

Setting up a private cloud for academic environment with OSS by Zoran Pantic at the IT University of Copenhagen

1,942 views

Published on

Take a look of this interesting presentation performed by Zoran Pantic at the IT University of Copenhagen.


More information here: https://blog.itu.dk/MCLC-F2012/

https://blog.itu.dk/MCLC-F2012/lectures/ (lecture 7 of week 5)

Additional Links which Zoran briefly mentioned in the lecture:
http://ken.pepple.info/openstack/2011/04/22/openstack-nova-architecture/
http://ken.pepple.info/openstack/2012/02/21/revisit-openstack-architecture-diablo/

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,942
On SlideShare
0
From Embeds
0
Number of Embeds
110
Actions
Shares
0
Downloads
51
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Setting up a private cloud for academic environment with OSS by Zoran Pantic at the IT University of Copenhagen

  1. 1. Setting up a private cloud for academicenvironment with open source software Cloud Computing Course ITU of Copenhagen February 27th, 2012
  2. 2. Who am I? Zoran Pantić Infrastructure Architect & Systems Specialist Corporate IT @ University of Copenhagen zopa@itu.dk & zoran@pantic.dk http://zoranpantic.wordpress.com http://dk.linkedin.com/in/zoranpantic
  3. 3. Agenda Non-technical part: A bit about the project Why OSS? Focusing on academic environments Technical part: UEC/Eucalyptus Reflections on hardware, software, network & redundancy Scaling out UEC Conclusion Questions? Video demo
  4. 4. Project: Implementing private cloudsolution in academic environments Based on Open Source Software (OSS) Focus on the logistical and technical challenges, and strategies of setting up a private cloud for academic environment Goal - providing guidelines and tutorials for implementing private cloud solution in academic environments: Design of the server- and network infrastructure
  5. 5. Why OSS?In general: Lowering the costs (no licensing headaches!) Interchangeability & portability (general) Socio-organizational reasonsUEC/Eucalyptus: Amazon AWS-like on-premise private cloud Using Amazons API Big community supporting it
  6. 6. Academic environments – why privatecloud? Usually, the budget is low, and the project should start as soon as possible Growing strongly: The need for processing large data volumes The need to conserve power by optimizing server utilization
  7. 7. Academic environments – why privatecloud? (continued)Private clouds: Higher ROI than traditional infrastructure More customizable Quick responses to changes in demands Rapid deployment Increased security Focus on an organization’s core business Effort required for running a private cloud is having a downward tendency
  8. 8. Academic environments – private cloudchallengesChallenges: Sociological Technological
  9. 9. Academic environments – private cloudsociological challengesSociological challenges, mostly political and economic: Existing structures oppose implementation of private cloud, Weak transparency of who is in charge of systems and economy, Researches cannot be market cost-effective, Administrators de facto in charge, instead of scientific groups, Tendency of IT department implementing things because they are interesting and “fun”, while maybe there is no need for those systems.
  10. 10. Academic environments – private cloudtechnological challengesTechnological challenges: Private cloud maturity, Problems porting of programming code, IT departments should be big enough, with enough expertize OSS: community cannot fix all your problems
  11. 11. Suggestions for implementing cloudsolutions in academic environments To determine the needs and their nature, consult the professors that are in charge of the project (and its funding), Once started, implementation should be top-down steered, A test case should be designed and implemented, Researchers should be allowed to thoroughly test the solution - free of charge, Make sure that implementation succeeds first time!In general - get a very clear picture of what services are to beoffered, who will use them, what they will use them for, andhow!
  12. 12. Focus on academic environments Difference in implementing for “infantry” and “supply troops” “Infantry” - to support research, scientific computing and High Performance Computing (HPC) “Supply” - to support daily operational systems and tasks i.e. joint administration Bookkeeping, administration, Communications (telephony, e- mail, messaging) “Infantry” – stateless instances vs. “Supply” – stateful instances
  13. 13. Academic environments – “Infantry” Uses non-standard & advanced research instruments Applicable in research, scientific computing and HPC, i.e.: Generally if users need VMs that they administer themselves (root access) - more appropriate to supply them with machines from private cloud, then giving access to virtual hosts behind firewall Organizations like ITU: for numerous different projects Organizations like DCSC: 1/3 of the jobs would be runnable on private cloud in HPC: Only in low end, for low memory and low core number jobs
  14. 14. Academic environments – “Infantry”(continued)Summarized suggestions Have social psychology in mind as important factor Consult the professor in charge of money for the project Implement an open source solution – UEC based on Eucalyptus, OpenStack, Joyent SmartOS (with both HW-level and OS-level virtualization!), OpenNebula, …)
  15. 15. Academic environments – “Infantry” –UEC WebGUI
  16. 16. Academic environments – “Infantry” –HybridFox
  17. 17. Academic environments – “Supply” Needs a stable and supported solution Summarized suggestions Have social psychology in mind as important factor Consult the system owner in charge of money for the project Implement a proprietary solution from reputable provider Microsoft Hyper-V, VMware Virtual Infrastructure, … Sign a support agreement & agree a good SLA
  18. 18. Academic environments – “Supply” –VMware vSphere
  19. 19. UEC/Eucalyptus componentsUEC/Eucalyptus is an on-premise private cloud platform,designed as a distributed system - a modular set of 5 simpleelements: Cloud Controller (CLC) Walrus Storage Controller (WS3) Cluster Controller (CC) Storage Controller (SC) Node Controller (NC)
  20. 20. UEC/Eucalyptus levelsThree levels: Cloud level Cloud Controller (CLC) Walrus Storage Controller (WS3) Cluster level Cluster Controller (CC) Storage Controller (SC) Computing level Node Controller (NC)
  21. 21. Cloud Controller (CLC) Entry point to Eucalyptus cloud web interfaces for administering the infrastructure web services interface (EC2/S3 compliant) for end users /client tools Frontend for managing the entire UEC infrastructure Gathers info on usage and availability of the resources in the cloud Arbitrates the available resources, dispatching the load to the clusters Only one per cloud (no redundancy)
  22. 22. Walrus Storage Controller (WS3) Equivalent to Amazon’s S3 Bucket based storage system with put/get storage model WS3 is storing the machine images and snapshots Persistent simple storage service, storing and serving files
  23. 23. Cluster Controller (CC) Entry point to a cluster Manages NCs and instances running on them Controls the virtual network available to the instances Collects information on NCs, reporting it to CLC One or several per cloud Only one per cluster (no redundancy)
  24. 24. Storage Controller (SC) Allows creation of block storage similar to Amazon’s Elastic Block Storage (EBS) Provides the persistent storage for instances on the cluster level, in form of block level storage volumes Supports creation of storage volumes, attaching, detaching and creation of snapshots
  25. 25. Node Controller (NC) Compute node (“work horse”) Controls the instances supported hypervisors: KVM (preferred) and Xen in open source version, and VMware (ESX/ESXi) in Enterprise Edition Communicating with both OS and the hypervisor running on the node, and Cluster Controller Gathers the data about physical resource availability on the node and their utilization, and data about instances running on that node, reporting it to CC One or several per cluster
  26. 26. Reflections on hardware Processor architecture: Definitely 64-bit – for performance reasons Multiprocessor, multicore, hyper threading VT-x enabled Node Controllers is a must Intel VT or AMD-V virtualization extensions Disk configuration: Local disks: RAID 10 (storage limits soon reached) Preferably SAN (iSCSI) – open source, see Nexenta /Napp-it
  27. 27. Reflections on software Ubuntu versions: Newest – new features, but less stability (more bugs) LTS (Long Time Support) – for more stability or larger deployments
  28. 28. Reflections on network 2 or 3 networks: WAN, Cloud public & Cloud private Firewall: open source based pfSense - to make the whole environment independent of the network infrastructure / environment where it will be “plugged in”
  29. 29. Reflections on redundancy No redundancy available in UEC – by design In case of software or hardware error on a component: no failover solution is available; Solution: adding a new server, and then restoring the data
  30. 30. Scaling out the environment CLUSTER 1CLOUD CLUSTER 2 CLUSTER 3NC NC NC NC NC NC
  31. 31. Suggested scaling out possibilities 2 physical servers Server 1: CLC/WS3/CC/SC Server 2: NC 3 physical servers: Server 1: CLC/WS3 Server 2: CC/SC Server 3: NC
  32. 32. Suggested scaling out possibilities 4 physical servers Server 1: CLC Server 2: WS3 Server 3: CC/SC Server 4: NC 5 physical servers Server 1: CLC/WS3 Server 2: CC1/SC1 Server 3: NC1 Server 4: CC2/SC2 Server 5: NC2
  33. 33. Conclusion & recommendations forprivate clouds based on open source Although still at an early stage, being hard to install, manage and maintain for a regular admin and have steep learning curve (admins & users), implementation is suggested, at affordable, smaller scale Implement on a current/modern hardware Keep the knowledge updated Keep software platform and hardware updated if possible Monitor & analyze costs, available features and complexity, compared to budget, needs and internal resources available Asses the implementation possibilities based on the analyses
  34. 34. Alternative – public clouds More mature Well documented Rich with features Easy to useExamples:Amazon’s initiatives for academic use: Amazon Education programwith grants for research applications; Having a project, academicorganization applies for a recurring grant, gets the approval withintwo weeks’ time, and starts using it immediately after.Locally in Denmark, CABO was willing to supply the project withresources.
  35. 35. Questions ?
  36. 36. DemoDemonstration of UEC environment and WebGUI
  37. 37. Thank you! Thank you for your attention! Still having questions? zopa@itu.dk zoran@pantic.dk

×