Cloudstack_Management_Server_Internals参考.ppt

High Availability Service Offering contains a flag for whether HA should be supported for the VM Does not use the native HA capability of hypervisors for XenServer and KVM Uses adapters to fine tune HA process High Availability Investigation Uses investigators to find out if VM is alive or down Each investigator returns three states Up Down Unknown Fencing Uses fencers to fence off the VM from accessing storage to ensure VM is not corrupted Each Fencer returns three states Fenced Unable to Fence Don’t know how to fence Restart Restarts the VM Triggering High Availability VM HA are triggered via the following methods: VM Sync detects out of band VM changes Resource Management detects that a resource is unreachable and its state can not be determined. VM start/stop has been sent to the resource but resource does not return Details of how high availability is done is at /CloudStack_Documentation/Design_Documents/CloudStack_High_Availability_-_Developers_Guide High Availability Future Moving toward using the native HA capability of the hypervisor. Looking to do more in the DRS area to coordinate recovery of wide spread outage. * * * 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 * 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 Se