Cloudstack_Management_Server_Internals.ppt

cloudstack architecture,alex huang,old architecture,pros agile development for existing developers scales well horizontally cons monolithic difficult to educate new and third-party developers easy to introduce bugs,2,xenserver resource,agent manager,api layer,ec2,cloudstack,virtual machine manager,kvm resource,srx resource,f5 resource,netscaler resource,other resources,access control,storage manager,network manager,console proxy manager,snapshot manager,template manager,async job manager,new deployment architecture,scales horizontally to different pressure points automatically scales service vms in zones to facilitate most efficient data path transfers fault isolation between api servers and execution servers and resources within zones,api server,new architecture api server,api server isolates integration code from execution server api server can horizontally scale to handle traffic easily adds other api compatibility easily exposes api needed by third party vendors,pluggable api engine,oam&p api,end user api,ec2 api,other apis,acl & authentication accounts, domains, and projects acl, limits checking,management services resource management configuration additional operations added by third party,rest,framework job queue database access layer osgi,integration,new architecture execution server,execution server protected by job queue kernel kept small for stability. it only drives processes. plugins provide mappings of virtual entities to physical resources third party plugins to provide vendor differentiation in cloudstack communicates with resources within data center over message bus,execution server,kernel drives long running vm operations syncs between resources managed and db generates events,framework cluster management job management alert & event management database access layer messaging layer,plugins storage handling network handling deployment planning hypervisor handling,component framework (osgi) transaction management,services api,new architecture resources,resources are carried in service vms to be in close network proximity to the physical resources it manages easily scales to utilize the most abundant resource in data center (cpu & ram) communicates with execution server over message bus (json) can be replicated for fault tolerance control gateway to resources within data center,agent,hypervisor resources,network resources,storage resources,image & template resources,snapshot resources,management server,kernel drives long running vm operations syncs between resources managed and db generates events,resource management,cluster management,job management,db,job queue,deployment planning,network configurations,network elements,hypervisor gurus,database access,alert & event management,plugin api,hypervisor resources,network resources,storage resources,image resources,snapshot resources,rest api,oam&p api,end user api,ec2 api,pluggable service api engine,other apis,security adapters,account management connectors,acl & authentication accounts, domains, and projects acl, limits checking,services api,services api,console proxy management,template access,ha,usage calculations,additional services,event bus,message bus,kernel module,understands how to orchestrate long running processes (i.e. vm starts, snapshot copies, template propagation) well defined process steps calls plugin api to execute functionalities that it needs,plugins,various ways to add more capability to cloudstack implements clearly defined interfaces all operations must be idempotent all calls are at transaction boundaries compiles only against the plugin api module,anatomy of a plugin,serverresource optional. required if plugin needs to be co-located with the resource implements translation layer to talk to resource communicates with server component via json,rest api optional. required only if needs to expose configuration api to admin.,plugin api,data access layer,implmentation,anatomy of a plugin,can be two jars: server component to be deployed on management server and an optional serverresource component to be deployed co-located with the resource server component can implement multiple plugin apis to affect its feature can expose its own api through pluggable service so administrators can configure the plugin as an example, ovs plugin actually implements both networkguru and networkelement,plugin interfaces available,networkguru implements various network isolation technologies and ip address technologies networkelement facilitate network services on network elements to support a vm (i.e. dns, dhcp, lb, vpn, port forwarding, etc) deploymentplanner different algorithms to place a vm and volumes. investigator ways to find out if a host is down or vm is down. fencer ways to fence off a vm if the state is unknown userauthenticator methods of authenticating a user securitychecker acl access hostallocator provides different ways to allocate host storagepoolallocator provides different ways to allocate volumes,adding a plugin to cloudstack,components are configured though components.xml supports dao, manager, and adapter patterns open to other component frameworks (osgi a possibility),components.xml example,kernel,sequence flow for deploy vm,end user rest api,security checkers,user vm mgr,network mgr,storage mgr,job scheduling,virtualmachine mgr,network guru,deploy vm,acl checks,allocate entity in cs,allocate vm,allocate nic,allocate volume,allocate ip,schedules deploy job,returns with job id, vm id,query job result,returns with job status,sequence flow for deploy vm,job threads,network element,user vm mgr,network mgr,storage mgr,virtualmachine mgr,network guru,start vm,start vm,prepare nics,notify that nic is about to be started in network,reserve resources for nic,services api,server resources,start user vm,agent calls,prepare volumes,template mgr,deployment planner,get a deployment plan (host and storagepool),prepare template on primary storage,agent calls,agent start vm call,stores job result,serverresource,translation layer between cloudstack commands and resource api may be co-located with resource have no access to db api defined in json messages,dao,sql generation done mostly in genericdaobase uses jpa annotations very little code to write for each individual dao database access layer for kernel no support for more complicated features such as fetch strategy welcome to use other types of orm in other modules but like to hear about preferred library. (hibernate is out due to licensing issues),example dao,/ examplevo.java entity table(name=“example”) public class examplevo id generatedvalue(strategy= generationtype.identity) column(name=“id”) long id; column(name=“name”) string name; column(name=“value”) string value; ,/ exampledao.java public interface exampledao extends genericdao / exampledaoimpl.java local(value=exampledao.class) public class exampledaoimpl extends genericdaobase implements exampledao protected exampledaoimpl() ,cloudstack storage,alex huang,storage,zone-level layer 3 switch,pod 2,pod n,private network,pod 1,scale-out nfs,cluster 2,cluster 1,primary storage,scale-out nfs,primary storage block device to the vm iops intensive accessible from host or cluster wide supports storage tiering worm storage secondary storage or object store for templates, iso, and snapshot archiving high capacity cloudstack manages the storage between the two to achieve maximum benefit and resiliency,primary storage support matrix,disk offering,disk offering specifies how block storage are offered to the end user disk space local or shared disk disk offering has storage tags which can be used to implementing storage tiering service offering actually contains a disk offering for the root disk,storage tiering,supported via storage tags for primary storage specify a tag when adding a storage pool specify a tag when adding a disk offering only storage pools with the tag will be allocated for the volume,worm storage,write once read many storage pattern is supported by two different storage types secondary storage (nfs server within an availability zone) object store (swift implementation for cross-zone) objective for worm storage high capacity, cheap storage easy to increase capacity used to store templates, isos, and snapshots,snapshots,snapshots are used as backups for drs taken on the primary storage and moved to secondary storage supports individual snapshots and recurring snapshots full snapshots on vmware and kvm. need help. incremental snapshots on xenserver allows backup network traffic to be specified in zone to segregate the backup network traffic from other network traffic types,base copy,template,d1,s1,d2,vm,s2,full1,s11,s12,s13,full2,s21,s22,s23,snapshot example (xenserver),primary storage,secondary storage,new storage is allocated when a snapshot is taken and changes are written into new storage once snapshot is taken, it is transferred to secondary storage old snapshots are removed to allow for storage to be garbage collected one snapshot is always kept on primary storage to prevent coalescing of the delta data every nth copy is a full copy to work against bad data in delta copies corrupting the entire chain cannot delete physical data until snapshots kept have passed the full copy,storage network,direct access to storage server (iscsi, cifs, nfs, etc) from within a vm setup the storage access via a shared network vms deployed will have two or more nics: one or more nics for internet access one nic for storage access security around storage network is lacking and requires work acl support is done by the operator,storage future,secondary storage multi-homed in pod object store for between zones production storage network for enterprise storage plugin framework,cloudstack resource management,organized into zones, pods, clusters each can be enabled, disabled, unmanaged, and inactive,cloudstack high availability,alex huang,high availability,service offering contains a flag for wheth