190 likes | 401 Views
Jason Gallicchio SharePoint Enthusiast. Tome Tanasovski PowerShell MVP. Twitter: @ jasongall. Blog : http://powertoe.wordpress.com / Twitter: @toenuff. Edwin Woo Windows Extremist. Blog : Too cool for one Twitter: Too cool for one. Eric Fellen. Website : http://www.nyewin.org.
E N D
Jason Gallicchio SharePoint Enthusiast Tome Tanasovski PowerShell MVP Twitter: @jasongall Blog: http://powertoe.wordpress.com/ Twitter: @toenuff Edwin Woo Windows Extremist Blog: Too cool for one Twitter: Too cool for one Eric Fellen Website: http://www.nyewin.org Ken Reid Ben Serebin Exchange Junkie Website: http://www.nyewin.org Blog: http://blog.reefsolutions.com Twitter:@bserebin Thanks to our Organizers!
NYC SharePoint User Group • Meetings: First Wednesday of the month, 5:30 to 7:30 PM, Microsoft NYC Office • Web:http://www.meetup.com/NYCSPUG/ User Group Communities Princeton Area SharePoint User Group • Meetings: Fourth Wednesday of the month, 6:00 to 8:00 PM, Infragistics Building Cranberry NJ • Web:www.princetonsug.com NYC PowerShell User Group • Meetings: Second Monday of the month, 6:00PM, Microsoft NYC Office • Web:http://powershellgroup.org/nyc New York Exchange User Group (NYExUG) • Meetings: Second Tuesday of the month, 5:45PM to 9PM, Microsoft NYC Office • Web: www.nyexug.com NY Enterprise Windows User Group (NYeWin) • Meetings: First Thursday of the month, 6:00PM, Microsoft NYC Office • Web:http://www.nyewin.org/
Event Sponsors Thanks to our Sponsors!
Event User Groups NY Enterprise Windows User Group Thanks to our User Groups!
Cloud Computing & Application Delivery with Windows Azure and KEMP Bhargav Shukla, Director of Product Research & Innovation Jason Dover, Global Product Marketing Manager New York: 631-345-5292 • Limerick: +353-61-260-101 • Hannover: +49-511-367393-0• Singapore: +65-62222429
Basic Azure Terminology Platform as a Service (PaaS) Services platform for applications with low infrastructure maintenance. Lowers administration and provides easily scalable environment for websites and services. No need to worry about patching, backing up, HA, etc. Infrastructure as a Service (IaaS) VMs on demand created from available images and requiring same administration as on premise virtual infrastructure. Gives greater flexibility. Region Windows Azure Datacenter Cloud Service A resource container possessing a URL attribute for addressing VMs in the service Availability Set A group of VMs in different fault domains to ensure redundancy Affinity Group Provides higher degree of proximity within datacenters North America Europe Asia North Central US North Europe East Asia South Central US West Europe South East Asia East US West US
Common Use Cases Enables O365 deployments w/ADFS HA in Azure Supports Azure-only or hybrid deployments Supports DRaaS when VPN is used Provides HA for workloads now supported in Azure such as SharePoint and RDS Web Applications w/L7 proxy needs SNI and single IP use for multiple workloads in multi-tenant deployments SharePoint RDS ADFS Farm ADFS Proxy Optional Site-to-Site VPN On Premise Data Center RDS ADFS Farm ADFS Proxy SharePoint
Azure Load Balancer Only vs. Azure Load Balancer + VLM for Azure
Cloud Only Deployment Client request received by LoadMaster LoadMaster checks to see if client session exists LoadMaster applies content rules, provides L7 services (IPS, SSL overlay, content switching, etc.) LoadMaster distributes traffic based on scheduling method and health/status of VMs Cloud Service Endpoint Public IP Virtual LoadMaster for Azure Cloud Service for Virtual LoadMaster VM ApplicationVM ApplicationVM ApplicationVM ApplicationVM ApplicationVM Cloud Service for Application VMs (optional) Virtual Network
Hybrid Deployment Cloud Service Endpoint Public IP Virtual LoadMaster for Azure Cloud Service for Virtual LoadMaster VM LoadMaster ApplicationVM ApplicationVM ApplicationVM Application VM Cloud Service for Application VMs (optional) Application VM Enterprise Network Virtual Network
HA Deployment with GEO Example DNS Info A/PTR Records vlmjddemo1.cloudapp.net = 23.96.32.110 vlmjddemo2.cloudapp.net = 23.96.35.230 NS Recordscloud.kempdemo.com = vlmjddemo1.cloudapp.netcloud.kempdemo.com = vlmjddemo2.cloudapp.net
HA Deployment with GEO Client receives response with service IP to connect to Client requests name resolution to access the service or application DNS entry for Service or application endpoint (URL i.e. cloud.kempdemo.com) is delegated to LoadMaster GEO Cloud Service Endpoint Public IP Cloud Service Endpoint Public IP Client application connects to resolved IP address Virtual LoadMaster for Azure 1 Virtual LoadMaster for Azure 2 Cloud Service for Virtual LoadMaster VM Cloud Service for Virtual LoadMaster VM VLM forwards the request to the application servers according to the configured load balancing mechanism and server’s health state LoadMaster uses GEO functionality to determine the health status of each participating LoadMaster and Virtual Service ApplicationVM ApplicationVM ApplicationVM ApplicationVM ApplicationVM Cloud Service for Application VMs (optional) VLM 1 becomes unavailable! Future Connections Redirected to alternative LoadMaster Virtual Network
Virtual LoadMaster Deployment Steps in Azure Deployment Steps Login to Azure management portal Add VLM-Azure image to My Images from VM Depot Deploy new VM using VLM image License new VLM with username/password Configure virtual services
Demo Setup LoadMaster for Azure Configure prerequisites in Azure environment Virtual Network Provision Virtual LoadMaster Add Image from VMDepot Create Virtual LoadMaster VM from image License Virtual LoadMaster Provision application VMs Setup web servers to be load balanced Configure load balancer Create virtual service
Demo Advanced Load Balancing Services Configure SSL offloading Configure content switching rules
Demo High Availability Configure load balancer high availability Handle failure of load balancing instance
Considerations When Using Azure Platform All VMs and LMs must be in same virtual network to communicate (virtual networks can’t span regions) Azure Load Balancer is ALWAYS used If virtual network isn’t predefined, Azure auto-assigns, preventing communication between separate cloud service(s) When separate cloud services are used for app VMs and VLMs, ACL should be configured on app cloud service endpoint only allowing ‘internal’ connections Storage and image region must be the same It’s not possible to change the VS IP address that is assigned VLM-Azure virtual services must be non-transparent It’s not possible to move a VM from one virtual network to another after provisioning it Configuring static IPs on application VMs being load balanced helps limit downtime
RESOURCES Virtual LoadMaster For Azure Datasheet http://kemptechnologies.com/files/downloads/documentation/Datasheets/LM-Azure.pdf Virtual LoadMaster for Azure HA Guide http://kemptechnologies.com/files/downloads/documentation/7.0/Feature_Description/Feature_Description_HA_for_Azure.pdf Virtual LoadMaster for Azure Beginners Guide http://kemptechnologies.com/files/downloads/documentation/7.0/Feature_Description/Feature_Description-LoadMaster_for_Azure.pdf How to Assign Static IP Addresses to Azure Virtual Machines http://www.bhargavs.com/index.php/2014/03/13/how-to-assign-static-ip-to-azure-vm/