Introducing Windows Azure


Published on

A presentation I gave introducing windows Azure.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Here is where I explain where the cloud came from, where did we get this terminology? What does it represent?What is the network that anyone can connect to anywhere?What is the network that can be used by the most number of devices?
  • Explain mesh
  • Switch failure = all servers loosing connectivity
  • Litware
  • Litware uses username/password todayEnd-users prefer a single-sign-on approachLitware wants to sell into companies that use a range of directories; AD, Tivoli, Sun, Oracle, … And Litware wants to support internet identitiesThe focus is on three Litware customersAdventure Works who customers have Live IDsContoso who has AD Federation Services and GenevaFabrikam who is a small business using ADOther customers use Tivoli, Oracle, …
  • Mesh is a data synchronization service, used to synchronize files, used when users want to work with data offline.
  • Introducing Windows Azure

    1. 1. Windows<br />An introduction to Cloud computing<br />Presented By:<br />Mohamed Samy <br />Technical Architect, iSource<br />
    2. 2. Goals and Takeaways<br />An understanding of Cloud computing<br />An understanding of the Azure environment<br />Understanding the new architecture<br />Understanding why and when this architecture applies<br />
    3. 3. Agenda<br />Introducing Cloud computing 15 mins<br />The Windows Azure Platform 15 mins<br />The Azure Data Services 15 mins<br />.NET Services 15 mins<br />How Cloud computing affects Architecture 15 mins<br />Q & A 15 mins<br />
    4. 4. Agenda<br />Cloud, utility computing – Nice new buzzwords<br />What do they mean?<br />Why do we need this model?<br />Is this the new way of doing things? What do I have to learn?<br />
    5. 5. Agenda Contd<br />Demo<br />What’s next?<br />Introducing Azure<br />The Operations Management perspective<br />Services in Action<br />
    6. 6. The cloud<br />
    7. 7. Another network topology<br />
    8. 8. Another network topology<br />
    9. 9. Evolution <br />Data center <br />Hosted Model<br />Cloud computing<br />
    10. 10. So what exactly is cloud computing?<br />Offerings from Amazon, Google, Microsoft.<br />Amazon Elastic computing (create your own machine with your choice of OS + APIs)<br />Google Apps and API<br />Hosting VMs in the cloud<br />Microsoft created a new offering…..<br />
    11. 11. Anatomy of a Cloud offering<br />A machine Physical/Virtual hosted in a data center (Hardware)<br />An Operating System<br />A framework, APIs and a development environment<br />Might include end user Apps (web sites, office suites..etc)<br />
    12. 12. Hosting locally vs. in the cloud<br />Hardware costs.<br />Software costs.<br />Administration costs.<br />
    13. 13. Resource allocation<br />Machines must be chosen to host roles of the service<br />Fault domains, update domains, resource utilization, hosting environment, etc.<br />Procure additional hardware if necessary<br />IP addresses must be acquired<br />Provisioning<br />Machines must be setup<br />Virtual machines created<br />Applications configured<br />DNS setup<br />Load balancers must be programmed<br />Upgrades<br />Locate appropriate machines<br />Update the software/settings as necessary<br />Only bring down a subset of the service at a time<br />Maintaining service health<br />Software faults must be handled<br />Hardware failures will occur<br />Logging infrastructure is provided to diagnose issues<br />This is ongoing work…you’re never done<br />Deploying A Service Manually<br />
    14. 14. Conclusion<br />Data centers cost a lot of money.<br />It’s cheaper to outsource these costs and headaches to someone who does this all the time.<br />
    15. 15. Previous Attempts<br />UDDI, Web service discovery<br />COM+, CORBA<br />Industry standards started popping up e.g. ws.*<br />
    16. 16. Introducing the Azure Platform<br />What is it?<br />Essentially a new architecture<br />A Service offering, pay as you go<br />An OS, APIs + Operations management (The key differentiator IMHO)<br />
    17. 17. Azure™ Services Platform<br />
    18. 18. A Look Inside Azure<br />Your Applications<br />…<br />ServiceBus<br />Workflow<br />Database<br />Analytics<br />Identity<br />Contacts<br />AccessControl<br />…<br />Reporting<br />…<br />Devices<br />…<br />Compute<br />Storage<br />Manage<br />…<br />
    19. 19. MS Approach to Azure Services<br />Provide a Flexible Services Platform with Internet Scale<br /><ul><li>Simple scenarios are simple – complex scenarios are possible
    20. 20. Services hosted in Microsoft’s data centers
    21. 21. Designed for high availability & scalability</li></ul>Base it on Internet Standards<br /><ul><li>Multiple protocol support including HTTP, REST, SOAP, Atom
    22. 22. Broad investment in open, community-based access to Azure services</li></ul>Extend Your Existing Investments <br /><ul><li>Familiar tools, languages, and frameworks with .NET and Visual Studio
    23. 23. Provides the choice to build on-premises, cloud, or hybrid solutions
    24. 24. Integrate with existing assets such as AD and premises applications</li></li></ul><li>Azure™ Services Platform<br />Interoperability<br />
    25. 25. .NET Framework Evolution<br />
    26. 26. The Operations management perspective<br />What is a fault domain?<br />What percentage of my service can fail at one time?<br />What happens if a switch fails?<br />What is an update domain?<br />How do I upgrade my service?<br />What portions can we take down and upgrade without causing failure?<br />
    27. 27. Allows you to specify what portion of your service can be offline at a time<br />Fault domains are based on the topology of the data center<br />Switch failure<br />Statistical in nature<br />Update domains are determined by what percentage of your service you will take out at a time for an upgrade<br />You may experience outages for both at the same time<br />System considers fault domains when allocating service roles<br />Example: Don’t put all roles in same rack<br />System considers update domains when upgrading a service<br />Fault/Update Domains<br />Fault domains<br />Allocation is across fault domains<br />
    28. 28. Windows Azure Fabric Controller<br />VM<br />Control VM<br />VM<br />VM<br />WS08 Hypervisor<br />Service Roles<br />Control <br />Agent<br />Out-of-band communication – hardware control<br />WS08<br />In-band communication – software control<br />Load-balancers<br />Node can be a VM or a physical machine<br />Switches<br />Highly-available<br />Fabric Controller<br />
    29. 29. Owns all the data center hardware<br />Uses the inventory to host services<br />Similar to what a per machine operating system does with applications<br />The FC provisions the hardware as necessary<br />Maintains the health of the hardware<br />Deploys applications to free resources<br />Maintains the health of those applications<br />Fabric Controller<br />
    30. 30. Windows Azure Automation<br />Fabric Controller<br />“What” is needed<br />Fabric Controller (FC) <br />Maps declarative service specifications to available resources<br />Manages service life cycle starting from bare metal<br />Maintains system health and satisfies SLA<br />What’s special about it<br />Model-driven service management <br />Enables utility-model shared fabric<br />Automates hardware management<br />Make it happen<br />Fabric<br />Switches<br />Load-balancers<br />
    31. 31. Windows Azure provisions and monitors hardware elements<br />Compute nodes, TOR/L2 switches, LBs, access routers, and node OOB control elements<br />Hardware life cycle management<br />Burn-in tests, diagnostics, and repair<br />Failed hardware taken out of pool<br />Application of automatic diagnostics<br />Physical replacement of failed hardware<br />Capacity planning<br />On-going node and network utilization measurements<br />Proven process for bringing new hardware capacity online<br />Behind The Scenes Work<br />
    32. 32. Modeling Services<br />Public Internet<br />Template automatically maps to service model<br />Background <br />Process Role<br />Front-end<br />Web Role<br />Load<br /> Balancer<br />Fundamental Services<br />Load Balancer Channel<br />Endpoint<br />Interface<br />Directory Resource<br />
    33. 33. Windows Azure Service LifecycleGoal is to automate life cycle as much as possible<br />Automated<br />Automated<br />Developer/<br />Deployer<br />Developer<br />
    34. 34. Purpose: Communicate settings to service roles<br />There is no “registry” for services<br />Application configuration settings<br />Declared by developer<br />Set by deployer<br />System configuration settings<br />Pre-declared, same kinds for all roles<br />Instance ID, fault domain ID, update domain ID<br />Assigned by the system<br />In both cases, settings accessible at run time<br />Via call-backs when values change<br />Dynamic Configuration Settings<br />
    35. 35. Resource allocation<br />Nodes are chosen based on constraints encoded in the service model<br />Fault domains, update domains, resource utilization, hosting environment, etc.<br />VIPs/LBs are reserved for each external interface described in the model<br />Provisioning<br />Allocated hardware is assigned a new goal state<br />FC drives hardware into goal state<br />Upgrades<br />FC can upgrade a running service<br />Maintaining service health<br />Software faults must be handled<br />Hardware failures will occur<br />Logging infrastructure is provided to diagnose issues<br />Lifecycle Of A Windows Azure Service<br />
    36. 36. So how do I get started<br />Demo<br />
    37. 37. ISB components<br />
    38. 38. Services In Action<br />
    39. 39. Adventure Works<br />Large Enterprise<br />SAP<br />AD<br />Cory<br />Litware<br />Mail<br />ASP.NET<br />Small Company<br />AD<br />Hosted at Rackspace<br />Francis<br />
    40. 40. IDENTITY AND ACCESS Control<br />36<br />
    41. 41. Identity and Access Control<br />Litware uses username/password today<br />End-users prefer a single-sign-on approach<br />Litware wants to sell into companies that use a range of directories; AD, Tivoli, Sun, Oracle, … <br />And Litware wants to support internet identities<br />The focus is on three Litware customers<br />Adventure Works who customers have Live IDs<br />Contoso who has AD Federation Services and Geneva<br />Fabrikam who is a small business using AD<br />Other customers use Tivoli, Oracle, …<br />37<br />
    42. 42. Adventure Works<br />Azure™ Services<br />AccessControl<br />Mesh<br />Service<br />Bus<br />Workflow<br />LiveID<br />SQLData<br />Contoso<br />SAP<br />AD<br />Litware<br />Cory<br /><br />Geneva<br />Mail<br />ASP.NET<br />Fabrikam<br />Hosted at Rackspace<br />AD<br /><br />Services<br />Connector<br />Francis<br />
    43. 43. Live Services<br />39<br />
    44. 44. User-Centric Interactions<br />Litware customer surveys show <br />Customer don’t like filling in registration forms<br />Often forget where the Litware site is located<br />Want to read or view training materials offline<br />On the plane<br />Remote locations with low-bandwidth connections<br />Would like to be notified when they need to complete training<br />Developers can take advantage of Identity and the Mesh to address these and other concerns<br />40<br />
    45. 45. Azure™ Services<br />AccessControl<br />Mesh<br />Service<br />Bus<br />Workflow<br />LiveID<br />SQLData<br />Litware<br /><br />ASP.NET<br />Hosted at Rackspace<br /><br />
    46. 46. Service BUS<br />42<br />
    47. 47. Azure™ Services<br />AccessControl<br />Mesh<br />Service<br />Bus<br />Workflow<br />LiveID<br />SQLData<br />Contoso<br />SAP<br />AD<br />Litware<br />Cory<br />Mail<br />ASP.NET<br />Hosted at Rackspace<br /><br />
    48. 48. Application Integration<br />Litware customers need integration with on-premises assets such as HR applications<br />Litware does not know ahead of time what the applications are, or how many of them exist<br />Integration must be secure and meet stringent customer security requirements<br />Litware decides to use the Service Bus for application integration<br />44<br />
    49. 49. workflow<br />45<br />
    50. 50. Azure™ Services<br />AccessControl<br />Mesh<br />Service<br />Bus<br />Workflow<br />LiveID<br />SQLData<br />Contoso<br />SAP<br />AD<br />Litware<br />Cory<br />Mail<br />ASP.NET<br />Hosted at Rackspace<br /><br />
    51. 51. Enhancing Application Integration<br />Litware wants an easy-to-use mechanism for custom application extensions<br />Ideally even non-developers could create high-availability, high-scale extensions<br />Ideally customers could use these tools<br />Should be able to easily integrate with existing and cross organization processes<br />Litware decides to use workflow when Contoso wants a custom feature for track low scores…<br />47<br />
    52. 52. SQL DATA services<br />48<br />
    53. 53. Azure™ Services<br />AccessControl<br />Mesh<br />Service<br />Bus<br />Workflow<br />LiveID<br />SQLData<br />Litware<br />ASP.NET<br />Hosted at Rackspace<br /><br />
    54. 54. Database Integration<br />Litware application stores, queries and manages a broad range of data<br />Structured, Semi-structured and Unstructured<br />Semi-structured and unstructured covered previously<br />Emerging Litware needs<br />Data shared with partners across different devices<br />Custom reports<br />Business analytics including ad-hoc analysis through Excel<br />Data mining<br />Litware leverages SQL Data Services in order to fulfill this broad set of data requirements<br />50<br />
    55. 55. Call to Action<br />Register for a .NET Services account & download the SDK<br /><br />Attend tomorrows' .NET Services session<br />