COS301 Windows Azure = Managed for You Standalone Servers IaaS PaaS SaaS Applications Runtimes Database Operating System Virtualization Server Storage Networking Efficiency Control Automated, Consistent Application Updates Automated, Consistent Configuration Changes Multi-Instance Management Scale-out High Availability Automated, Consistent OS Servicing Updates to the application occur in an automated way Updates result in clean components forcing consistency Local storage and OS are left untouched Updates to the settings occur in an automated way Updates result in clean settings Local storage and OS are left untouched Identical instances are deployed across the service Large scale-out services are guaranteed to be consistent No configuration drift Application scale-out can occur automatically The application has no downtime, even in the face of hardware failures. The OS system hosting the application can be updated with the most recent patches in a coordinated and automated way. Windows Azure Single Instance Persistent OS Automated, Consistent Application Updates Automated, Consistent Configuration Changes Multi-Instance Management Scale-out High Availability Automated, Consistent OS Servicing Single Instance Stateless OS Multi-Instance Stateless OS Front-End Front-End FrontEnd-1 End-2 Middle Tier-3 Tier-1 Tier-2 FrontEnd-1 FrontEnd-2 Middle Tier-1 Middle Tier-2 Middle Tier-3 Update Domain 1 Update Domain 2 Update Domain 3 FrontEnd-1 FrontEnd-2 Middle Tier-1 Middle Tier-2 Middle Tier-3 Mark’s Service Role: Front-End Definition Type: Web VM Size: Small Endpoints: External-1 Configuration Instances: 2 Update Domains: 2 Fault Domains: 2 FC US-North Central Datacenter Server Datacenter Datacenter Routers Aggregation Routers and Load Balancers Agg LB Agg LB LB Agg LB LB Agg LB Agg LB LB LB Agg LB LB LB Power Distribution Units PDU PDU PDU TOR … Nodes PDU … TOR Nodes PDU … TOR Nodes PDU … TOR Nodes PDU TOR Nodes PDU TOR Nodes PDU … TOR Nodes PDU TOR Nodes PDU TOR Nodes PDU … TOR Nodes TOR Nodes PDU TOR Nodes PDU TOR Nodes TOR Nodes Racks TOR Nodes Top of Rack Switches PDU Image Repository Maintenance OS FC Host Agent Fabric Controller Windows Azure Parent OS Role Role Role Role Images Images Images Images Windows Azure Node OS Windows Azure Hypervisor PXE Server Physical Node Guest Partition Guest Partition Guest Partition Guest Partition Role Instance Role Instance Role Instance Role Instance Guest Agent Guest Agent Guest Agent Guest Agent Trust boundary Host Partition FC Host Agent (trusted) Fabric Controller (Primary) Fabric Controller (Replica) … Fabric Controller (Replica) 27 www.mycloudapp.net Role A Role B Count: 3 Update Domains: 2 Fault Domains: 2 Size: Large Count: 2 Update Domains: 2 Fault Domains: 2 Size: Medium www.mycloudapp.net Load Balancer OS Volume Resource Volume Role Volume Guest Agent Role Host Role Entry Point Secondary Differencing VHD Shadow Differencing VHD Base VHD Shadow Differencing VHD Shadow Base Windows VHD Azure Blob Storage Role A UD 1 Role A UD 2 Role B UD 1 Role B UD 2 Role A UD 1 Role A UD 2 Role A UD 1 Role A UD 2 Role B UD 1 Role B UD 2 Role B UD 1 Role B UD 2 Supported Changes In-place VIP Swap Delete and Redeploy Operating system version Yes Yes Yes .NET trust level Yes Yes Yes Soon Yes Yes Yes Yes Yes Soon Yes Yes Yes Yes Yes Number or type of endpoints Soon No Yes Names and values of configuration settings Soon Yes Yes Yes Yes Yes Soon Yes Yes Change existing certificates Yes Yes Yes Deploy new code Yes Yes Yes Virtual machine size Local storage settings (increase only) Number of roles Number of role instances Values (but not names) of configuration settings Add new certificates • Allocation 1 allows for 2 nodes rebooting simultaneously Service B Role A-1 UD 2 Service A Role B-2 UD 2 Service B Role B-2 UD 2 Allocation 1 Service B Role A-1 UD 2 • Host OS upgrade rollout is 2x faster with allocation 1 Service A Role A-1 UD 2 Service A Role A-1 UD 2 Service A Role B-2 UD 2 Allocation 2 Service B Role B-2 UD 2 Missed Heartbeat Recovery Initiated Problem How Detected Fabric Response Role instance crashes FC guest agent monitors role termination FC restarts role Guest VM or agent crashes FC restarts VM and hosted role Host OS or agent crashes FC host agent notices missing guest agent heartbeats FC notices missing host agent heartbeat Detected node hardware issue Host agent informs FC Tries to recover node FC reallocates roles to other nodes FC migrates roles to other nodes Marks node “out for repair” Guest Agent Heartbeat 5s 25 min Guest Agent Heartbeat Timeout 10 min Guest Agent Guest Agent Connect Timeout Role Instance Role Instance Launch Indefinite Role Instance Load Balancer Load Balancer Role Instance Heartbeat “Unresponsive” Timeout Heartbeat Timeout 15s 15s 15 min 30s 30s Role Role Instance Instance Start Ready (for updates only) Blue Section http://www.microsoft.com/cloud/ http://www.microsoft.com/privatecloud/ http://www.microsoft.com/windowsserver/ http://www.microsoft.com/windowsazure/ http://www.microsoft.com/systemcenter/ http://www.microsoft.com/forefront/ http://northamerica.msteched.com www.microsoft.com/teched www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn
© Copyright 2024