Windows Azure : reseaux, équilibreurs de charge et CDN
•Descargar como PPTX, PDF•
0 recomendaciones•367 vistas
Recomendados
Recomendados
Más contenido relacionado
Similar a Windows Azure : reseaux, équilibreurs de charge et CDN
Similar a Windows Azure : reseaux, équilibreurs de charge et CDN (20)
Más de Microsoft Technet France
Más de Microsoft Technet France (20)
Windows Azure : reseaux, équilibreurs de charge et CDN
- 8. (10.0.0.0/16) (10.2.0.0/16) (10.1.0.0/16) 10.0.0.10 10.0.0.11 131.57.23.120 10.2.2.0/24 10.2.3.0/24 10.1.2.0/24 10.1.3.0/24 10.1.2.3 10.1.2.4 10.1.3.4
- 10. 10.0.0.2010.0.0.21 131.57.23.45 IT Admin Network Admin (10.1.0.0/16) (10.1.1.0/24) (10.1.3.0/24) (10.1.2.0/24) (10.1.4.0/24) SQLSubnet (10.1.3.0/24) GW IP 65.57.23.45 CorpOffice Network configuration Deployment package (10.0.0.0/16)
- 11. • IKE v1 • 3DES, AES128 • SHA1
- 25. Permet aux clients de délivrer du contenu plus proche de leur utilisateurs finaux www.customer.com Ceci conduit à une meilleure experience utilisateur, une audience vraiment mondiale, améliore l’engagement, augmentation du chiffre d’affaire
- 26. Une capacité de multiple terabits par seconde est disponible depuis nos 24 sites mondiaux avec une disponibilités de 99,95%.Les services CDN grandissent automatiquement sans intervention humaine. Utilisez par Microsoft depuis déjà 4 ans. Désormais disponible pour les clients de Windows Azure.
- 27. s
Notas del editor
- Customer-managed private virtual networks within Windows Azure“Bring your own IPv4 addresses”Control over placement of Windows Azure Roles within the networkStable IPv4 addresses for VMsHosted VPN Gateway that enables site-to-site connectivityAutomated provisioning & managementSupport existing on-premises VPN devicesUse servers for name resolutionEnables VMs runningon-premise DNS servers for name resolutionEnables customers to use their on-premise DNS in Windows Azure to be joined to corporate domains running on-premise (use your on-premise Active Directory)
- Enterprise app in Windows Azure requiring connectivity to on-premise resourcesManage identity and access control with on-premise resources (on-prem Active Directory)Remote monitoring and trouble-shooting of resources running in Windows AzureRunning services in Mixed ModeCloud only deployments requiring stable IP addresses and connectivity across tenants
- In Windows Azure previously you did not have control over the VM names. This is a net new. Windows Azure Provided DNS is also new. Previously you had to use the Windows Azure object model to get the IP addresses of different roles in your deployment. Bring You Own Device = BYOD, allows you to host Active Directory directly in the cloud or when used in conjunction with Virtual Networks (VPN) to build hybrid solutions where AD is hosted on premises and consumed in the cloud or both.
- UDP is now a supported protocol in WA (previously wasn’t). Discuss that by default with virtual machines there is an internal endpoint defined with protocol=“all” so essentially all traffic is open between virtual machines. Windows Server firewall and Linux firewall will still need to be configured to allow traffic.Health probes allow the load balancer to check a custom HTTP path that tells the LB whether the server is healthy or not. For TCP endpoints no http path is required just the port to connect to.
- Input port forwarding is how you can configure direct/non load balanced communication to multiple VMs that have services listening on the same port.
- Load Balanced Input Endpoints allow you to configure the load balance to distribute traffic to multiple VMs. This works with TCP/UDP and you can also configure an HTTP probe with a custom path to test the health of the VM.
- Load Balanced Input Endpoints allow you to configure the load balance to distribute traffic to multiple VMs. This works with TCP/UDP and you can also configure an HTTP probe with a custom path to test the health of the VM. Definissable via Powershell / check toutes les 15sGet-AzureVM -ServiceName "MyService" -Name "MyTestVM2" | Set-AzureEndpoint -LBSetName "MyLBSet" –Name MyTestEndpoint2 –Protocol tcp –LocalPort 80 -ProbePort 80 -ProbeProtocol http -ProbePath "/" | Update-AzureVM