Apache CloudStack 4.2 architecture and integration with VMware vSphere
•Télécharger en tant que PPTX, PDF•
1 j'aime•565 vues
This is a short introduction to the Apache Software Foundation and Apache CloudStack running on VMware vSphere. It will be presented at the vBrownBag sessions of VMworld 2013.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
En vedette
En vedette (7)
Similaire à Apache CloudStack 4.2 architecture and integration with VMware vSphere
Similaire à Apache CloudStack 4.2 architecture and integration with VMware vSphere (20)
Dernier
Dernier (20)
Apache CloudStack 4.2 architecture and integration with VMware vSphere
- 1. August, 2013 Apache CloudStack (ACS) 4.2 & VMware vSphere
- 3. Good
- 4. Bad
- 6. Pod 1 Cluster 1 Host 2 ACS Architecture Host 1 …. L3 switch Secondary Storage Pod N Zone 1 FirewallLoad Balancer Primary Storage L2 switch …. Cluster N New in ACS 4.2 – Regions • Regions hold multiple zones • Geographic Scalability & Resilience • Management Server per Region • Object Storage Region Wide
- 7. ACS Management Server Back Up DB Management Server MySQL DB Replication Load Balancer Infrastructure Resources Management Server
- 8. ACS Hypervisor Interaction ACS Management Server XenServer XAPI • XenServer 5.6 and higher • Incremental Snapshots • VHD • NFS, iSCSI, FC and Local disk • Storage over- provisioning: NFS vSphere vCenter HTTP • vSphere 4.1 and 5.X • Full Snapshots • VMDK • NFS, iSCSI, FC and Local disk • Storage over- provisioning: NFS, iSCSI KVM Agent • RHEL 6.0, 6.1 and Ubuntu 10.04 • Full Snapshots (not live) • QCOW2 • NFS, iSCSI and FC • Storage over- provisioning: NFS OVM Agent • OVM 2.2 • No Snapshots • RAW • NFS and iSCSi • No storage over- provisioning
- 9. ACS / VMware Integration • Dynamic scaling of CPU & RAM • Hot plug additional NICs to VM • CPU/RAM overcommit • HA & DRS • vSphere VM snapshots & thin provisioning • Improved ACS volume snapshots • Storage live migration • Zone-wide block storage • Not Supported: Storage DRS – planned for 4.3 • Nicira NVP support (Layer 2 & 3 today) • DVS support • Cisco 1000v and ASA 1000v Compute Storage Networking ACS Management Server vCenter
Notes de l'éditeur
- Incorporated in 1999Governed solely by members – not companiesNon-profit corporation & public charity statusVolunteer OrganizationExists to “Let Developers Develop”Over 100 Top Level ProjectsSupplies established framework environment for projects to collaborate & growSuccess of the project is up to the projectIndependent legal entity for companies and individuals to donate resources with assurance of protection by the foundation
- Source: https://www.ohloh.net/orgs/apache/projects – Apache CloudStack is a very active project with a healthy amount of contributorsand commits
- A Host is the basic unit of scale.A Cluster groups compatible hostsAll hosts in a cluster have access to shared (primary) storageA Pod is one or more clusters, usually with a L2 switch. Typically a pod is a rack.Zones contain one or more pods, and have access to secondary storage for templates Firewall and Load balancers separate public and private networksAn availability zone is typically a Data CenterThe core components of a Citrix CloudPlatform implementation are:Hosts – Hosts are servers from at least one of the supported virtualization providers. Citrix CloudPlatform fully supports hosts from multiple providers, but does not convert VM images from one hypervisor type to another. Depending on the hypervisor, a “host” may be a higher level concept. For example, in XenServer a Citrix CloudPlatform “host” is equivalent to a XenServer resource pool and the “host” entry is the pool master.Primary Storage – Primary storage is the hypervisor level storage containing the deployed VM storage. Primary storage options will vary by hypervisor, and depending upon the hypervisor selected, CloudPlatform may impose requirements upon it.Cluster – Host groups are combined into Clusters which contain the primary storage options for the Cluster. Primary storage isn’t shared outside of a Cluster. In the case of CloudPlatform, a Cluster in of itself does not imply modification of any clustering concept within the hypervisor. For example, in XenServer a resource pool is a host to CloudPlatform, and CloudPlatform does not create a super set of Cluster functionality for XenServer. Pod -- Host groups are combined first into Clusters and then into Pods. For many customers, a pod represents a high level physical concept like a server rackNetwork – Network is the logical and physical network associated with service offerings. Multiple concurrent network service offerings and topologies can be supported within CloudPlatformSecondary Storage – Secondary storage is the storage system used for template and ISO management. It also is where snapshot events occur.Zone – A zone is a collection pods to form some level of service availability. While Amazon EC2 defines an availability zone as a data center, CloudPlatform keeps the concept more abstract allowing cloud operators to have multiple availability zones within a given data center.Management Server Farm – The CloudPlatform management server farm is a grouping of CentOS/RHEL CloudPlatform servers forming a web farm, with an underlying MySQL cluster database. The management server farm can manage multiple Zones, and can be virtualized.
- Management Server is statelessSingle Management Server per 5000 hostsDeploy using RHEL 5.4 + or CentOS 5.4 + MySQL database as data storeManagement server and database support clustering for redundancy and scale
- See hypervisor notes for full detailsXenServerCitrix CloudPlatform includes and entitlement for XenServer Advanced edition. When using XenServer, you will first add the XenServer pool master to CloudPlatform as a host, and CloudPlatform will transparently add all slave hosts to CloudPlatform. Oracle VMLimitations: No snapshot because OVM is using raw format for volumeNo system VM because OVM won’t support Debian guestNeed a helper cluster(xenserver/kvm/vmware)Advantage:Oracle provides lots of templates which have Oracle DB frameworks, applications built in, customer can quickly deploy Oracle serviceCreate templateCreate template from root volume of VMStart system VMAdd a helper cluster(XenServer/KVM/Vmware) before creating any OVM VmThe domain router will automatically be created in helper cluster when creating first OVM instanceNo OVM manager and CloudPlatform mixedOvs-agent will store data in local database on hostSupported OS typeAll Linux/Solaris templates must be from Oracle siteWindows can be installed from ISOOracle Cluster File SystemOracle recommendation solution for using ISCSIUser responsibilitySetup ISCSI device on every hostCreate OCFS2 file system on every deviceCloudPlatform responsibilityConfigure every ocfs2 nodeAdd/Remove node on demandKVMFor KVM, Support is only for RHEL 6 based KVM and Ubuntu 10.04. No other flavors of KVM are supported, including RHEV.vCenter cluster/hostA vCenter cluster is mapped directly to a CloudPlatform cluster under PodA vCenter cluster for CloudPlatform can only belong to one vCenter datacenterWhy?vCenterDatastore used by vCenter cluster is at scope of vCenter datacentervCentervSwitch used by vCenter cluster is at scope of vCenter datacenterSharing vCenter datacenter resource outside of CloudPlatform will be problematicSystem VM bootstrapFirst generation is done by CloudPlatform management serverSecond/beyond generations is done through a running SSVMSSVM (Secondary Storage VM)SSVM for template processingSSVM for VMware volume/snapshot/template operationCommand delegationSystem VM, extension of CloudPlatform management serverResource manager can be running in context of a system VMCommand delegation in CloudPlatform management serverSnapshotsCloudPlatform snapshot is taken at volume basisSnapshot in vCenter is take at VM basisFill the gapTake a VM snapshot, if it is for a detached volume in CloudPlatform, create a worker VMParse VM snapshot meta data, build up disk chain information at volume basisCreate intermediate VM on top of a selected disk chainExport VM (full backup) to secondary storageCleanupsvCentervSwitchvSwitch setup is done through vCenterNIC-bonding is done through vCenterCloudPlatform creates networks (portgroups) dynamicallyCloudPlatform propagates networks across clusterWhy? To support independent VM live migration both in CloudPlatform and vCenterDefault vSwitch portsNot enough, usually needs to extend