CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview


Published on

Apache CloudStack Overview and 4.1 / 4.2 release previews.

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
  • How many of you are using IaaS today?How many of those are using public cloud? Anyone using anything other than Amazon? Anyone work for a service provider?Any interesting use cases that folks want to talk about?
  • Cloud Operators (Small Teams, Enterprise IT Department, Public Cloud Operators)Care about the underlying architectureOwe their users an SLAThe goal is to support their users in just the right waysCloud Users (Application Developers, IT Operations, DevOps Teams)Differing workload stylesCare about speed and flexibilityFocused on supporting the real end users…
  • The value of any infrastructure should be tied to the value that the applications running on it provide to the end usersOur project’s job is to make the operator happy, in service of the application owners, in service of the end users. While lots of hype surrounds the tech in this space, but that hype frequently does a disservice to the IT community by distracting from the end goal.
  • Empower users to “serve themselves”— removing IT from the critical path of the service deliveryAutomate previously labour intensive tasks, helping to reduce IT operation costs and deliver fasterReduces complexity and variability by using standard workloads which ensures consistency with each application and service deploymentRetains visibility into resource allocation and line of business usage on a real-time levelIncreased server/admin ratio and delivers benefits of scale— even if deployed globally
  • Don’t consider these numbers absolute in terms of installed clouds, instead focus on the correlation between the development and user community growth.Users in this context are primarily the operatorsThis level of correlation is a strong indicator of project longevity.
  • Dual Workload Support means:Choice of Hypervisor (or even Bare Metal servers)Choice in networking modelsChoice in storage typesChoice in Availability LevelsStrong ACL models to protect important applications from the “power” of automation to turn it off
  • CloudStack DC Meetup - Apache CloudStack Overview and 4.1/4.2 Preview

    1. 1. Chip ChildersVP of Apache CloudStack | Apache Software FoundationPrincipal Engineer | SunGard Availability | twitter: @chipchilders | irc: chipc on freenode
    2. 2. Let’s start with some questions foryou..
    3. 3. What’s Apache CloudStack? Apache CloudStack is opensource software designed todeploy and manage largenetworks of virtual machines, asa highly available, highlyscalable Infrastructure as aService (IaaS) cloud computingplatform. CloudStack is a Top-LevelProject at the Apache SoftwareFoundation.
    4. 4. We Enable Cloud Operators To design, install, support, upgrade and scale their diverse cloudenvironments Application Owners To easily consume infrastructure services, so that infrastructuregets out of the way of delivering applications to the end users
    5. 5. So They Can EnableThe Application UsersYour end users want access to their applications,all the time from anywhere.They couldn’t care less about the environmentsupporting the apps they use…They care about the business results they achieveusing these applications.
    6. 6. Benefits of CloudStackSelf ServiceCapitalLeverageWorkforceLeverageManagementAutomationWorkloadStandardizationRemove IT as a service delivery critical pathReduce IT operational costsConsistent application and service deploymentUsage MeteringCentralizedManagementSmarterVirtualizationVisibility into user and line of business usageManage complete infrastructure, regardless of scaleDrive reduced capital requirements
    7. 7. We’ve got a “few” users…(Literally hundreds)
    8. 8. Why do we care about the users? We are the users Builds the next generation of developers Drives project sustainability Improves quality
    9. 9. Users Driving the Project leads to Strong support for both traditional and cloud-era workloads Flexible deployment options and infrastructure choice Real-world experiences with scale Upgrades that work New technology integrations by and for the operators Testing of our APIs from diverse consumer tools
    10. 10. So what can I do with it?
    11. 11. Layer 3 Networking (EC2 Style)…DBSecurityGroupWebSecurityGroup… …WebVMWebVMWebVMWebVMDBVMWebVMDBVMWebVM
    12. 12. Guest Virtual Layer-2 NetworkGuest 1VM 1Guest 1VM 2Guest 1VM 3Guest 1 Virtual Network10.1.1.0/24Gateway 1Virtual RouterGuest 2VM 1Guest 2VM 2Guest 2VM 3Guest 2 Virtual Network10.1.1.0/24Gateway10.1.1.1Guest 2Virtual RouterPublic IP65.37.141.2465.37.141.80Public IP65.37.141.1165.37.141.36Internet
    13. 13. Multi-tier NetworkPrivate IP10.1.1.112DHCP, DNSUser-dataPublic IP65.37.141.11210.1.1.1Web VM110.1.1.3Web VM210.1.1.4Web VM310.1.1.5Web VM4NetscalerLoadBalancerPrivate IP10.1.1.111Public IP65.37.141.111 JuniperSRXFirewallVirtualRouterVirtual Network10.1.1.0/24VLAN 100Virtual Network10.1.2.0/24VLAN 100110.1.2.2110.1.2.1810.1.2.3810.1.2.3910.1.2.31App VM1 Network10.1.3.0/24VLAN 14110.1.2.24App VM2 VM 1DHCP, DNS,User-dataDHCP, DNSUser-data,Source-NAT,VPNPublic IP65.37.141.115VirtualRouterVirtualRouter
    14. 14. Unified Multi-tier Network10.1.1.1WebVM 310.1.1.5WebVM 4VirtualNetwork10.1.1.0/24VLAN 100VirtualNetwork10.1.2.0/24VLAN 100110.1.2.31AppVM 1VirtualNetwork10.1.3.0/24VLAN 14110.1.2.24AppVM VM1Virtual Router CustomerPremisesIPSec or SSL site-to-site VPNInternetMonitoring VLANVirtual Router Services• IPAM• DNS• LB [intra]• S-2-S VPN• Static Routes• ACLs• NAT, PF• FW [ingress & egress]• BGPLoad Balancer
    15. 15. How does CloudStack do this?
    16. 16. Infrastructure Model Management Server Farm Management and provisioning tasks Zone Collection of pods, network offerings and secondary storage Pod Collection of clusters in the same failure boundary Cluster A grouping of hosts and their associated storage Hosts Servers onto which services will be provisioned Primary Storage VM disk storage Network Logical network associated with service offerings Secondary Storage Template, snapshot and ISO storage ZoneCloudStack PodClusterHostHostNetworkPrimaryStorageVMVMCloudStack PodClusterSecondaryStorage
    17. 17. Deployment Architecture Hypervisor is the basic unit of scale. Cluster consists of one ore more hostsof same hypervisor All hosts in cluster have access toshared (primary) storage Pod is one or more clusters, usuallywith L2 switches. Availability Zone has one or morepods, has access to secondarystorage. One or more zones represent a cloudPod 1….Cluster NL2Host 2Cluster 1Host 1 PrimaryStorageZone 1….L3SecondaryStoragePod NManagementServerClusterInternet
    18. 18. Management Server Cluster MS is stateless. MS can bedeployed as physical serveror VM Single MS node can manageup to 10K hosts. Multiplenodes can be deployed forscale or redundancy RHEL 5.4+, Ubuntu 10.0.4,Fedora 16ReplicaInfrastructureResourcesUser APIAdmin APILoadBalancerManagementServerManagement ServerMySQLReplication
    19. 19. Software ArchitectureManagement ServerOrchestration Engine- Drives long running VMoperations- Syncs between resourcesmanaged and DB- Generates eventsResourceManagementClusterManagementJobManagementDBUICloudPortalCLIOtherClientsDeployment PlanningNetwork GurusNetwork ElementsHypervisor GurusDatabaseAccessAlert & EventManagementPluginAPIResource APIHypervisorResourcesNetworkResourcesStorageResourcesImageResourcesSnapshotResourcesREST APIOAM&P API End User API EC2 APIPluggable Service APIEngineOtherAPIsSecurity AdaptersAccount ManagementConnectorsACL & Authentication- Accounts, Domains, and Projects- ACL, limits checkingServices APIServicesAPIConsole ProxyManagementTemplateAccessHAUsageCalculationsAdditionalServicesEvent BusMessage BusUsageServer
    20. 20. Got Scale? Running in production at >30,000 physical hosts, supported by only 4management server instances Even greater scale by using CloudStack in a Regional model Remember: The separation of control, management and data planes iscritical for cloud platform scale.
    21. 21. Upcoming Releases4.1.0 - currently being voted on for release4.2.0 - entering feature freeze this week
    22. 22. What’s in 4.1? Lots of internal architectural changes (we want to speed updevelopment of new integrations) 20 new features 24 “improvements” 155 bug fixes
    23. 23. Architectural Changes Converted from custom injection framework to Spring Lots of refactoring: Storage plugin model Network plugin model API implementation refactored (remains compatible)There’s a theme here: We are making CloudStack moreflexible, both for developers and operators…
    24. 24. New Features in 4.1API, UI and Integration Options: AWS style regions Event pub-sub framework (RabbitMQ implementation) Advanced search within the UI API Server request throttling API Discoverer Service Users resetting their own passwords Users directly changing their API keys EC2 query API Cloudmonkey CLI
    25. 25. New Features in 4.1Networking: Nicira integration adds L3 functionality Persistent networks without a running VM Autoscale (Netscaler implementation) Juniper SRX & F5 Big IP inline mode Egress FW rules for guest networks Open vSwitch support for KVM
    26. 26. New Features in 4.1Compute: Support for passing custom VMX settings to vSphere on VMcreate Adding and removing Virtual NICs from VMs Reset SSH key within a VMStorage: Volume resizing S3-backed secondary storage
    27. 27. Great, That’s 4.1…What about 4.2? Many features proposed for 4.1 were moved to 4.2(Remember that time-based release thing?) 58 New Features scheduled for 4.2! 16 of them are already finished, including testing Some of them won’t make the release (again, time-based!) 40 Improvements (same caveats as features)
    28. 28. Sample 4.2 Features Midonet and BigSwitch SDNintegrations Enhanced Baremetal provisioning VM I/O Throttling Hyper-V 2012 Support LXC Support Cisco VSG integration Cisco ASA 1000V VM Affinity Rules Eliminate NFS layer for S3 secondarystorage Zone-wide primary storage Security group isolation in AdvancedNetwork zones Dedicating resources to domains andaccounts IP Address reservation w/o a vNICallocation Improved synchronization betweenCloudStack and what’s actually runningon the hosts vSphere DVS support UI Plugin framework
    29. 29. And we’re just getting started…Come join us at
    30. 30. Thanks! (Any Questions?)(P.S.: slides posted at