Windows Azure IaaS - Mit Cloud Computing Ideen schneller umsetzen

Uploaded on


More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Zu einem Cloud-Dienst gehören die Fähigkeiten, dass diese automatisiert verwaltet und skaliert werden können.Die Verwaltung der Komponenten in Windows Azure ist über verschiedene Wege möglich. Der Standardzugriff geschieht über das Verwaltungsportal von Windows Azure. Dies kann allerdings auch automatisiert werden. Zum einen ist dies möglich über Skript-Funktionen von PowerShell unter Windows oder Kommandozeilen-Tools unter Windows, Mac und Linux.Über PowerShell lassen sich alle Komponenten im Detail automatisieren und steuern.Cloud-Dienste und VMs können nach Bedarf horizontal über mehr Instanzen und vertikal über stärkere Hardware skaliert werden. Dabei ist sowohl eine Erhöhung von Ressourcen möglich als auch eine Reduzierung.VMs in Windows Azure verwenden als Image-Format VHDs, wie sie vom Hyper-V-Server von Windows eingesetzt werden. Es ist möglich, diese VHDs aus dem lokalen Rechenzentrum in den Blog-Storage von Windows Azure hochzuladen und mit VMs von Windows Azure zu nutzen als auch der umgekehrte Weg, VHDs von Windows Azure herunterzuladen und wieder auf einem lokalen Hyper-V-Server auszuführen.
  • Das Verwaltungsportal von Windows Azure bringt einen Image-Katalog für Windows- und Linux-Betriebssysteme mit. Zusätzlich existieren Windows-Images mit fertigen Installationen von SQL Server 2012, BizTalk Server 2013 und SharePoint Server 2013.Neben den Windows-Betriebsystemen sind auch fertige Linux-Images im Katalog u.a. mit OpenSUSE, CentOS, Ubuntu und SUSE Linux Enterprise Server 11.Ein zusätzliches Angebot an Images und gepflegt durch die Community gibt es auf VM Depot, welches durch Microsoft Open Technologies gehostet wird. Dort kann die Community eigene Images hochladen und teilen. Seit dem Start im Januar 2013 liegen im VM Depot nun schon über 250 Images. (Stand 14.05.2013)
  • Aber halt! Bevor wir zur Demo kommen, die Infos, damit sie es selber testen können.Link:
  • Slide Objectives:Explain how Windows Azure websites are simple, easy, and open.Notes:
  • Slide Objectives:Explain that Windows Azure Web Sites supports Classic ASP, ASP.NET, PHP, and Node.js out of the box and that you can also host any custom FastCGI handler.Notes:
  • Git Deployment is Native, or through a Service hook from CodePlex, GitHub or BitBucket
  • Slide Objectives:Highlight the ability to get started quickly with the Windows Azure Web App GallerySpeaking Points:Along-side the publishing capabilities, Windows Azure Web Sites also offers the Web App Gallery which provides many turn key solutions based off of well known open source web applications.Notes:
  • Slide Objectives:Highlight the benefits of the Windows Azure StoreSpeaking Points:Much like the Windows Azure Web App Gallery brings a turn key solution to Web Applications, the Windows Azure Store quickly exposes Application and Data Services for use in your applications.Notes:
  • This slide explains web and worker role architecture within a cloud service.Things to call out: Each role can have multiple identical instances You can currently have up to 25 roles per cloud service.
  • Virtual Machines work in a similar way.A cloud service can have up to 25 roles but if that role has a virtual machine there can only be a single instance. Implicit Cloud service is a reference to the portal. If you only have a single VM the portal will not display the cloud service although it is created and exists.Add another role (or remove the VM) and the cloud service will show.
  • When there are multiple VMs in the same cloud service they can communicate directly as they are on the same network.
  • 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 protcol=“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.
  • Building new PaaS applications is a no-brainer when looking at some of the benefits:Simplified Deployment and ConfigurationHealth ModelEasy High AvailabilityInstance ScalabilityOS PatchingAutomatic Firewall ConfigurationSimple Certificate DeploymentHowever, building new applications sometimes comes with a dependency on other systems or legacy code. This has sometimes blocked the development of PaaS applications. The IaaS offering will unblock these types of applications and allow for the two development models to co-exist and directly communicate.
  • Compare the current mixed mode developer models
  • This diagram illustrates how you can configure applications such as Windows Azure Web Sites or Cloud Services to connect to applications running on virtual machines without directly putting them on the same virtual network. Note currently Windows Azure Web Sites do not support virtual networks. The application on the VM will need to have an endpoint opened on it to allow inbound traffic from the other service. To secure connections it is recommended the firewall on the VM be configured to restrict traffic only from the service.
  • In this scenario a web/worker role is deployed on the same virtual network as the virtual machines.The benefit is direct connectivity without the need for configuring endpoints on the load balancer. This is a requirement for scenarios like AD that require persistent IP addresses or lots of ports (RPC/COM+).
  • Slide Objective:Multiple virtual machines grouped in an availability set are required to have an SLA
  • Slide ObjectiveDiscuss achieving very high availability with Windows AzureSpeaker NotesFault Domain is a physical unit of failure, and is closely related to the physical infrastructure in the data centers. In Windows Azure the rack can be considered a fault domain. However there is no 1:1 mapping between fault domain and rack. Windows Azure Fabric is responsible to deploy the instances of your application in different fault domains. Obviously this only applies if you run more than 1 instanceRight now Fabric makes sure that your application uses at least 2 (two) fault domains, however depending on capacity and VM availability it may happen that it is spread across more than that. As a developer u have no direct control over how many fault domains your application will use but the way you configure it may impact your availabilityUpgrade Domain is a logical unit, which determines how particular service will be upgraded. The default number of upgrade domains that are configured for your application is 5 (five). You can control how many upgrade domains your application will use through the upgradeDomain configuration setting in your service definition file (CSDEF). Windows Azure Fabric ensures that particular upgrade domain is not within single fault domainThat is Upgrade domains are orthogonal to fault domainsRoles are then spread out over upgrade domains and fault domains. Subject to running a reasonable number of instances this removes the risk of a single point of failure
  • Slide ObjectiveProvide a graphical view of fault and upgrade domains for existing web and worker roles. Use to contrast existing skills with availability sets.Speaker NotesYou can see that our service is well spread out across both fault and upgrade domainsThe loss of a fault domain will not cause a failure of our service nor will the restart or change of an upgrade domain cause a failure of our serviceNotesUseful pre-reading here.
  • Availability sets tell the Fabric Controller to place VMs in the same set on different racks for faults and in separate upgrade domains for updates. This essentially tells the FC not to take the guest OS down of all VMs in the same set for host updates.
  • To achieve a 99.95% SLA you must use multiple instances grouped in availability sets.
  • Explain that each tier of an application can be enabled with its own availability set which ensures at a physical hardware level in the data center that there is no single point of failure.


  • 1. 5.5+ billion worldwide queries each month 280+ millionconnected users per month 50+ million Office Web Apps 4 trillion objects in Azure Storage 2-4+billion emails per day 32 languages 88 markets 40+ million users in 35 markets active accounts 60+ million active users 200+ million
  • 2. cloud services on premises 280+ millionconnected users per month active users 50+ million Office Web Apps 4 trillion objects in Azure Storage
  • 3. development management identity virtualization data platform
  • 4. Cloud Services
  • 5. Inactivity Period An & Aus Nicht planbare Lasten Schnelles Wachstum Planbare Lasten
  • 6. Kein Cloud-Lock- In Verwaltung >_ Skalieren
  • 7. Image-Kataloge Microsoft Windows Server 2008 R2 SQL Server 2012 Windows Server 2012 Biztalk Server 2013 Open Source OpenSUSE 12.3 CentOS 6.3 Ubuntu 12.04 LTS/12.10/13.04 SUSE Linux Enterprise Server 11 SP2
  • 8.
  • 9. Beratung Konzeption Design Go Live! Service Websites + Cloud Computing Prototyping Isolation von Websites- und Datenbanken Skalieren der Front- und Back-Ends Auftragsarbeit oder Full Service
  • 10. On-premises Datacenter Einzelne Computer hinter einer Firewall Route-based VPN Windows Azure Virtual Network <subnet 1> <subnet 2> <subnet 3> DNS Server DynamicRouting Gateway
  • 11. P2S VPNs Active Directory SharePoint SQL Server Windows Azure Existing Datacenter S2S VPN