Présentation cloud services

Editor's Notes

• #6: NOTE: Add spectrum (arrow) that shows the “PaaS Continuum”We’re going to talk about a new sevice. You think about WAWS as the highest level service, abstracts away .. .. .. even web server.Reducing complexity, reducing management overhead.Add animation to build out each part -> final click reviels the cloud box at the bottom.
• #9: Slide ObjectiveUnderstand how a Web Role extends the standard worker roleSpeaker NotesA web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web CoreWeb Roles run ASP.NET websites- they do this by using the IIS hostage web core. pretty much anything that will work in a standard IIS ASP.NET Web Site should work in Windows Azure. At MIX09, we additionally added support for IIS7’s FastCGI capability. As a note, any files that are part of a asp.net project on windows azure are READ ONLY! If you need to be able to change the contents of files:User Blob StorageIf its configuration, use the service model files – which can be changed at runtime.Inbound protocols are http(s) – outbound protocols are any TCP connection but NOT UDP.Noteshttp://msdn.microsoft.com/en-us/library/dd179341.aspxhttp://blogs.msdn.com/b/carlosag/archive/2008/04/14/hostyourownwebserverusingiis7.aspxhttp://blogs.iis.net/ksingla/archive/2007/12/20/ins-amp-outs-of-hostable-web-core.aspx
• #10: Slide ObjectiveUnderstand the 3 common patterns of worker rolesSpeaker NotesPattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue againPattern 2 Worker listens for inbound TCP requestCan implement with Raw TcpListeners or use WCF or use Hosted Web CorePattern 3 Run a 3rd party processWhen the role starts up or runs use a Process.Start() call to run a standard windows executable E.g. Running a database serverNoteshttp://blog.smarx.com/posts/build-your-own-web-role-running-hosted-web-core-in-windows-azurehttp://blog.smarx.com/posts/making-songs-swing-with-windows-azure-python-and-the-echo-nest-api
• #11: Slide ObjectiveUnderstand the difference between Roles and InstancesSpeaker NotesThe Service model defines the shape of a service- the Roles it will haveendpoints it will listen onTypes of VMs that will be runAt runtime each Role will run at a given scaleSpecifically each role will be deployed onto and executed on one or more VMsA VM runs a single roleNotesNotes on the various security roles involved in running a Windows Azure accounthttp://blog.toddysm.com/2010/01/subscription-and-service-administration-in-windows-azure.html
• #13: Slide ObjectiveUnderstand what a scale-out application looks likeSpeaking notesHigh scale applications often follow this sort of an patternInbound connectivity comes through a load balancerRequests are round robin routedLoad balancer is typically aware of the state of the web servers (i.e. are they up)There are one or more tiers or groups of stateless web or app serversBy stateless we mean that they do not hold state between client requestsStateless means that simple load balancing works – no need for sticky sessionsStateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancerA stateful or storage tierThis will generally involve some sort of scale out approach for large appsOften using partitioned databasesOften some sort of queuing mechanismApplications will often perform processing in the background. Improves response time for usersAllows load peaks to be buffered in queuesWindows Azure provides us with a Platform as a Service offering to implement these sorts of applicationsNoteshttp://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
• #14: The infrastructure of each Windows Azure data center is notionally divided into multiple sections known as fault domains. These sections of the infrastructure (which are not necessarily individual servers or server racks) are designed in such a way that a failure of one fault domain is extremely unlikely to affect any other fault domain. When you deploy a service, the Windows Azure Fabric Controller automatically locates the roles in at least two different fault domains so that a failure in one domain will not affect all instances of your service.
• #19: 1. Create a new ASP.Net application.2. Add a Cloud project to convert it to a Cloud Service.3. Add a worker role to the project.4. Launch app in local emulator. Examine emulator UI.5. Stop app. Scale up web role and/or worker role.6. Launch app again. Examine emulator UI changes.7. Set breakpoint in worker role, observe how you can debug locally.8. Stop app. Open service defination file. Walk through other settings such as startup task and endpoints.9. Publish the app (with RDC enabled).
• #20: Slide ObjectiveCODE – PACKAGE – UPLOAD – DEPLOYShows how service makes it from code living in Visual Studio to a running deployed instance in Windows AzureShow how Roles are packaged up and uploaded with the config to Windows AzureSpeaking PointsCode is compiled, then packaged into a single file. This is the service package.This, along with the configuration/service model – are deployed via the web portal.NotesVisual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api
• #21: Slide ObjectiveCODE – PACKAGE – UPLOAD – DEPLOYShows how service makes it from code living in Visual Studio to a running deployed instance in Windows AzureShow how Roles are packaged up and uploaded with the config to Windows AzureSpeaking PointsCode is compiled, then packaged into a single file. This is the service package.This, along with the configuration/service model – are deployed via the web portal.NotesVisual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api
• #24: Slide ObjectiveUnderstand the lifecycle of a Windows Azure roleUnderstand the methods that can be overridden in RoleEntryPointUnderstand the events that are raised by role instances when their status is changingSpeaker NotesRoles will typically extend RoleEntryPointThe fabric calls RoleEntryPoint methods as it starts and stops a roleWaWorkerHost process is started.Worker Role assembly is loaded and surfed for a class that derives from RoleEntryPoint. This class is instantiated. RoleEntryPoint.OnStart() is called. RoleEntryPoint.Run() is called. If the RoleEntryPoint.Run() method exits, the RoleEntryPoint.OnStop() method is called . WaWorkerHost process is stopped. The role will recycle and startup again.As a role changes state it will raise the StatusCheck event.A status of Busy will mean the load balancer will not route requests to the instance.Notehttp://blogs.msdn.com/b/jnak/archive/2010/02/11/windows-azure-roleentrypoint-method-call-order.aspxhttp://msdn.microsoft.com/en-us/library/ee848065.aspx
• #25: Slide ObjectiveUnderstand the role programming model in overviewSpeaker NotesA role is similar to a windows service. It gets started once deployed, and will get stopped when required.It could get stopped because we are re-deploying you to a different serverYou actioned the stop from the web-portalIt’s up to you to keep running and NEVER return from Start() unless you have been told to stop. Note: you do not need to handle the stop – you can simply “fail”Noteshttp://msdn.microsoft.com/en-us/library/ee848065.aspxhttp://blogs.msdn.com/b/jnak/archive/2010/02/11/windows-azure-roleentrypoint-method-call-order.aspxes
• #26: 1. Launch management portal.2. Navigate to a previously deployed Cloud Service.3. Walk through management UI.4. Explain how scaling, upgrade, WIP can be performed on UI.
• #30: K #8
• #31: Slide ObjectiveUnderstand what a scale-out application looks likeSpeaking notesHigh scale applications often follow this sort of an patternInbound connectivity comes through a load balancerRequests are round robin routedLoad balancer is typically aware of the state of the web servers (i.e. are they up)There are one or more tiers or groups of stateless web or app serversBy stateless we mean that they do not hold state between client requestsStateless means that simple load balancing works – no need for sticky sessionsStateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancerA stateful or storage tierThis will generally involve some sort of scale out approach for large appsOften using partitioned databasesOften some sort of queuing mechanismApplications will often perform processing in the background. Improves response time for usersAllows load peaks to be buffered in queuesWindows Azure provides us with a Platform as a Service offering to implement these sorts of applicationsNoteshttp://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
• #33: http://weatherservice.cloudapp.net/
• #34: http://weatherservice.cloudapp.net/
• #43: http://weatherservice.cloudapp.net/
• #44: http://weatherservice.cloudapp.net/
• #47: Slide ObjectiveCODE – PACKAGE – UPLOAD – DEPLOYShows how service makes it from code living in Visual Studio to a running deployed instance in Windows AzureShow how Roles are packaged up and uploaded with the config to Windows AzureSpeaking PointsCode is compiled, then packaged into a single file. This is the service package.This, along with the configuration/service model – are deployed via the web portal.NotesVisual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api
• #48: http://weatherservice.cloudapp.net/
• #67: The ACS would deserve multiple sessions on its own right to be properly covered, here I'm just giving you a quick sampler.What we have seen so far is just a small part of its surface. The schema here shows the ws-federation subsystem, what is normally used for browser-based, session-oriented application types. We've been playing only with ADFS IP types, but in fact <click> there are many out of the box popular IPs you can use right away with your application sticking to the same protocol <click> and a browser<click>.ACS can also do WS-Trust, a high-security protocol for SOAP web services, accepting identities from ADFS2 ws-trust endpoints or bare credentials registered in ACS for management purposes.<click> the same sources can be used within OAuth2.0 calls. OAuth is the current state of the art for securing REST calls: it is still in draft state, hence expect changes, but you can already experiment with it.<click> Both protocols can be used for rich client application types and in general <click> server 2 server interactions.Not shown here there are the management endpoints, the other portion of ACS' development surface, which can be used instead or alongside the portal for managing the namespace.
• #71: http://weatherservice.cloudapp.net/