• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Introducing Windows Azure
 

Introducing Windows Azure

on

  • 1,828 views

A presentation I gave introducing windows Azure.

A presentation I gave introducing windows Azure.

Statistics

Views

Total Views
1,828
Views on SlideShare
1,613
Embed Views
215

Actions

Likes
1
Downloads
48
Comments
0

3 Embeds 215

http://www.techgig.com 199
http://www.slideshare.net 15
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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 Introducing Windows Azure Presentation Transcript

  • Windows Azurem_raafat_samy@hotmail.com
    An introduction to Cloud computing
    Presented By:
    Mohamed Samy
    Technical Architect, iSource
  • Goals and Takeaways
    An understanding of Cloud computing
    An understanding of the Azure environment
    Understanding the new architecture
    Understanding why and when this architecture applies
  • Agenda
    Introducing Cloud computing 15 mins
    The Windows Azure Platform 15 mins
    The Azure Data Services 15 mins
    .NET Services 15 mins
    How Cloud computing affects Architecture 15 mins
    Q & A 15 mins
  • Agenda
    Cloud, utility computing – Nice new buzzwords
    What do they mean?
    Why do we need this model?
    Is this the new way of doing things? What do I have to learn?
  • Agenda Contd
    Demo
    What’s next?
    Introducing Azure
    The Operations Management perspective
    Services in Action
  • The cloud
  • Another network topology
  • Another network topology
  • Evolution
    Data center
    Hosted Model
    Cloud computing
  • So what exactly is cloud computing?
    Offerings from Amazon, Google, Microsoft.
    Amazon Elastic computing (create your own machine with your choice of OS + APIs)
    Google Apps and API
    Hosting VMs in the cloud
    Microsoft created a new offering…..
  • Anatomy of a Cloud offering
    A machine Physical/Virtual hosted in a data center (Hardware)
    An Operating System
    A framework, APIs and a development environment
    Might include end user Apps (web sites, office suites..etc)
  • Hosting locally vs. in the cloud
    Hardware costs.
    Software costs.
    Administration costs.
  • Resource allocation
    Machines must be chosen to host roles of the service
    Fault domains, update domains, resource utilization, hosting environment, etc.
    Procure additional hardware if necessary
    IP addresses must be acquired
    Provisioning
    Machines must be setup
    Virtual machines created
    Applications configured
    DNS setup
    Load balancers must be programmed
    Upgrades
    Locate appropriate machines
    Update the software/settings as necessary
    Only bring down a subset of the service at a time
    Maintaining service health
    Software faults must be handled
    Hardware failures will occur
    Logging infrastructure is provided to diagnose issues
    This is ongoing work…you’re never done
    Deploying A Service Manually
  • Conclusion
    Data centers cost a lot of money.
    It’s cheaper to outsource these costs and headaches to someone who does this all the time.
  • Previous Attempts
    UDDI, Web service discovery
    COM+, CORBA
    Industry standards started popping up e.g. ws.*
  • Introducing the Azure Platform
    What is it?
    Essentially a new architecture
    A Service offering, pay as you go
    An OS, APIs + Operations management (The key differentiator IMHO)
  • Azure™ Services Platform
  • A Look Inside Azure
    Your Applications

    ServiceBus
    Workflow
    Database
    Analytics
    Identity
    Contacts
    AccessControl

    Reporting

    Devices

    Compute
    Storage
    Manage

  • MS Approach to Azure Services
    Provide a Flexible Services Platform with Internet Scale
    • Simple scenarios are simple – complex scenarios are possible
    • Services hosted in Microsoft’s data centers
    • Designed for high availability & scalability
    Base it on Internet Standards
    • Multiple protocol support including HTTP, REST, SOAP, Atom
    • Broad investment in open, community-based access to Azure services
    Extend Your Existing Investments
    • Familiar tools, languages, and frameworks with .NET and Visual Studio
    • Provides the choice to build on-premises, cloud, or hybrid solutions
    • Integrate with existing assets such as AD and premises applications
  • Azure™ Services Platform
    Interoperability
  • .NET Framework Evolution
  • The Operations management perspective
    What is a fault domain?
    What percentage of my service can fail at one time?
    What happens if a switch fails?
    What is an update domain?
    How do I upgrade my service?
    What portions can we take down and upgrade without causing failure?
  • Allows you to specify what portion of your service can be offline at a time
    Fault domains are based on the topology of the data center
    Switch failure
    Statistical in nature
    Update domains are determined by what percentage of your service you will take out at a time for an upgrade
    You may experience outages for both at the same time
    System considers fault domains when allocating service roles
    Example: Don’t put all roles in same rack
    System considers update domains when upgrading a service
    Fault/Update Domains
    Fault domains
    Allocation is across fault domains
  • Windows Azure Fabric Controller
    VM
    Control VM
    VM
    VM
    WS08 Hypervisor
    Service Roles
    Control
    Agent
    Out-of-band communication – hardware control
    WS08
    In-band communication – software control
    Load-balancers
    Node can be a VM or a physical machine
    Switches
    Highly-available
    Fabric Controller
  • Owns all the data center hardware
    Uses the inventory to host services
    Similar to what a per machine operating system does with applications
    The FC provisions the hardware as necessary
    Maintains the health of the hardware
    Deploys applications to free resources
    Maintains the health of those applications
    Fabric Controller
  • Windows Azure Automation
    Fabric Controller
    “What” is needed
    Fabric Controller (FC)
    Maps declarative service specifications to available resources
    Manages service life cycle starting from bare metal
    Maintains system health and satisfies SLA
    What’s special about it
    Model-driven service management
    Enables utility-model shared fabric
    Automates hardware management
    Make it happen
    Fabric
    Switches
    Load-balancers
  • Windows Azure provisions and monitors hardware elements
    Compute nodes, TOR/L2 switches, LBs, access routers, and node OOB control elements
    Hardware life cycle management
    Burn-in tests, diagnostics, and repair
    Failed hardware taken out of pool
    Application of automatic diagnostics
    Physical replacement of failed hardware
    Capacity planning
    On-going node and network utilization measurements
    Proven process for bringing new hardware capacity online
    Behind The Scenes Work
  • Modeling Services
    Public Internet
    Template automatically maps to service model
    Background
    Process Role
    Front-end
    Web Role
    Load
    Balancer
    Fundamental Services
    Load Balancer Channel
    Endpoint
    Interface
    Directory Resource
  • Windows Azure Service LifecycleGoal is to automate life cycle as much as possible
    Automated
    Automated
    Developer/
    Deployer
    Developer
  • Purpose: Communicate settings to service roles
    There is no “registry” for services
    Application configuration settings
    Declared by developer
    Set by deployer
    System configuration settings
    Pre-declared, same kinds for all roles
    Instance ID, fault domain ID, update domain ID
    Assigned by the system
    In both cases, settings accessible at run time
    Via call-backs when values change
    Dynamic Configuration Settings
  • Resource allocation
    Nodes are chosen based on constraints encoded in the service model
    Fault domains, update domains, resource utilization, hosting environment, etc.
    VIPs/LBs are reserved for each external interface described in the model
    Provisioning
    Allocated hardware is assigned a new goal state
    FC drives hardware into goal state
    Upgrades
    FC can upgrade a running service
    Maintaining service health
    Software faults must be handled
    Hardware failures will occur
    Logging infrastructure is provided to diagnose issues
    Lifecycle Of A Windows Azure Service
  • So how do I get started
    Demo
  • ISB components
  • Services In Action
  • Adventure Works
    Large Enterprise
    SAP
    AD
    Cory
    Litware
    Mail
    ASP.NET
    Small Company
    AD
    Hosted at Rackspace
    Francis
  • IDENTITY AND ACCESS Control
    36
  • Identity and Access Control
    Litware uses username/password today
    End-users prefer a single-sign-on approach
    Litware wants to sell into companies that use a range of directories; AD, Tivoli, Sun, Oracle, …
    And Litware wants to support internet identities
    The focus is on three Litware customers
    Adventure Works who customers have Live IDs
    Contoso who has AD Federation Services and Geneva
    Fabrikam who is a small business using AD
    Other customers use Tivoli, Oracle, …
    37
  • Adventure Works
    Azure™ Services
    AccessControl
    Mesh
    Service
    Bus
    Workflow
    LiveID
    SQLData
    Contoso
    SAP
    AD
    Litware
    Cory
    Sandy@hotmail.com
    Geneva
    Mail
    ASP.NET
    Fabrikam
    Hosted at Rackspace
    AD
    Lane@Litware.com
    Services
    Connector
    Francis
  • Live Services
    39
  • User-Centric Interactions
    Litware customer surveys show
    Customer don’t like filling in registration forms
    Often forget where the Litware site is located
    Want to read or view training materials offline
    On the plane
    Remote locations with low-bandwidth connections
    Would like to be notified when they need to complete training
    Developers can take advantage of Identity and the Mesh to address these and other concerns
    40
  • Azure™ Services
    AccessControl
    Mesh
    Service
    Bus
    Workflow
    LiveID
    SQLData
    Litware
    Sandy@hotmail.com
    ASP.NET
    Hosted at Rackspace
    Lane@Litware.com
  • Service BUS
    42
  • Azure™ Services
    AccessControl
    Mesh
    Service
    Bus
    Workflow
    LiveID
    SQLData
    Contoso
    SAP
    AD
    Litware
    Cory
    Mail
    ASP.NET
    Hosted at Rackspace
    Lane@Litware.com
  • Application Integration
    Litware customers need integration with on-premises assets such as HR applications
    Litware does not know ahead of time what the applications are, or how many of them exist
    Integration must be secure and meet stringent customer security requirements
    Litware decides to use the Service Bus for application integration
    44
  • workflow
    45
  • Azure™ Services
    AccessControl
    Mesh
    Service
    Bus
    Workflow
    LiveID
    SQLData
    Contoso
    SAP
    AD
    Litware
    Cory
    Mail
    ASP.NET
    Hosted at Rackspace
    Lane@Litware.com
  • Enhancing Application Integration
    Litware wants an easy-to-use mechanism for custom application extensions
    Ideally even non-developers could create high-availability, high-scale extensions
    Ideally customers could use these tools
    Should be able to easily integrate with existing and cross organization processes
    Litware decides to use workflow when Contoso wants a custom feature for track low scores…
    47
  • SQL DATA services
    48
  • Azure™ Services
    AccessControl
    Mesh
    Service
    Bus
    Workflow
    LiveID
    SQLData
    Litware
    ASP.NET
    Hosted at Rackspace
    Lane@Litware.com
  • Database Integration
    Litware application stores, queries and manages a broad range of data
    Structured, Semi-structured and Unstructured
    Semi-structured and unstructured covered previously
    Emerging Litware needs
    Data shared with partners across different devices
    Custom reports
    Business analytics including ad-hoc analysis through Excel
    Data mining
    Litware leverages SQL Data Services in order to fulfill this broad set of data requirements
    50
  • Call to Action
    Register for a .NET Services account & download the SDK
    http://www.azure.com
    Attend tomorrows' .NET Services session