Windows Azure ile Kesintisiz İş Süreci

1,226 views

Published on

Tütev - Windows Azure ile Kesintisiz İş Süreci Seminer Notları
http://www.ibrahimatay.org/post/2013/06/tutev-windows-azure-ile-kesintisiz-is-sureci-seminer-notlari/

Windows Azure
http://www.ibrahimatay.org/category/windows-azure/

Dünya şekilleniyor. İş süreçleri, kesintisiz ve başarılı gerçekleşebilmesi için çeşitli iş uygulamalar geliştirilmektedir. Geliştirilen iş uygulamalarının en az maliyet, başarılı ve performanslı sonuçlar üretebilmesi amaçlanmaktadır.

İş uygulamalarının amaçlanan sonuçlar ile istenildiği gibi çalışabilmesi amacı ile Cloud Computing mimarileri oluşturulmuştur. Şirketlerin iş uygulamalarını konumlandırması amacı ile en iyi Cloud Computing altyapısını seçilmesi gerekmektedir. Konu ile ilgili olarak, geçtiğimiz günler de Tutev de “Windows Azure ile Kesintisiz İş Süreci” isimli semineri gerçekleştirmiş bulunmaktayım.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,226
On SlideShare
0
From Embeds
0
Number of Embeds
894
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Speaking Points:Windows Azure itself is deployed around the worldWith Windows Azure, we have a concept of regions, which is where you choose to place your code and run. In each of the regions, we have a Microsoft datacenter. These datacenters are massive facilities that host 10s or in some cases hundreds of thousands of serversWe have currently four regions in North America, two regions in Europe, and two in AisaAs you can see on this slide we also have a number of CDN edge points, which we can use to cache your content and deliver it even faster for customers. %What you’re going to see in the next couple months and years is that we will rapidly expand our datacenter footprint around the world, so you will have more options for running your applications. Once you build an application, you can choose where you want to run in the world and you can move your workloads from region to region. You can also run your application in multiple regions simultaneously and just direct traffic and customers to whichever version of the app is closest to them. That gives you a global footprint and a chance to reach a bigger customer base or audience in new marketsNotes:Windows Azure services such as compute and storage are now available in 8 worldwide datacenters with an additional 24 Content Delivery Network endpoints. You can’t have a real cloud without a data center.
  • Slide Objectives:Describe the various computing patterns that are good for Cloud ComputingSpeaking Points:There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc.Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices.The cloud can help deliver IT as a standardized service…freeing you up to focus on your businessCover the workloads in the slide
  • Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaking Points:With this in mind, it’s important to understand how to talk about our Cloud Services offerings.There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
  • Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaking Points:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
  • Slide Objectives:Provide an understanding of which Distributions of Linux are offered in the Windows Azure Image Gallery.Speaking Points: 1) Only Certain distributions of Linux are officially supported: SUSE Enterprise 11 SP2, OpenSUSE 12.1, CentOS 6.2, Ubuntu 12.04 2) Virtual Machine Images of these Distributions are provided by Partners who are experts in each distribution 3) Other Distributions of Linux can be installed as “Bring-Your-Own-Linux” however, some integration work will be needed.Notes:Linux Virtual Machines Product Page: http://www.windowsazure.com/en-us/manage/linux
  • Windows ServerWindows Server 2008 R2 and later versions are supported for the following roles: Active Directory Domain ServicesActive Directory Federation ServicesActive Directory Lightweight Directory ServicesApplication ServerDNS ServerFax ServerNetwork Policy and Access ServicesPrint and Document ServicesWeb Server (IIS)Windows Deployment ServicesWindows Server Update ServicesFile Services
  • In this slide I want to show you how easy it is to use System Center 2012 SP1 to take virtual machines that are running on premise and move them to Windows Azure. Using the App Controller component you can actually save to the library a virtual machine that’s running and then using App Controller you can actually take the virtual machine that’s been stored in the library and then move it to Windows Azure. We will do our best attempt to actually fit the VM according the capabilities that exist for Windows Azure VM role, if not we allow you as a customer to modify the settings of the virtual machine as it is moved to Windows Azure. We also allow the use of Orchestrator and it’s Azure IP to automate tasks against Windows Azure. And from a monitoring perspective we support or rather System Center SP1 Operations Manager allows you to monitor the virtual machine that is now running inside the data center. New Capabilities in SP1Windows Azure IaaS features – disks, images (AC)Build runbooks against Azure (SCO)Copy VMs from on-premises to Windows Azure, and vice-versa (AC, SCO)Deploy VMs on Azure (AC, SCO)Backup running workloads onto Windows Azure (DPM)Orchestrate & Automate Windows Azure Service management tasks (SCO)Leverage outside-in view of service health (OM)Leverage Visio Authoring tool to monitor Windows Azure (OM)
  • Slide Objective:Explain workflow for provisioning VMs in the cloud Notes:Cloud First Provisioning means exactly what is says. Building a VM in the cloud first. You have three methods of starting this process: Build a VM from the portal, from the command line OR programmatically calling the REST API. Once your choice of provisioning is made you will need to select the image and instance size to start from. The newly created disk will be stored in blob storage and your machine will boot.
  • Slide Objective:You need an availability set for a 99.95% SLANotes:Without at least two virtual machines performing the same workload grouped into an availability set you get a 99.95% SLA.
  • Slide Objective:Discuss achieving very high availability with Windows AzureNotes:Fault 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 Objective:Explain availability setsNotes: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.
  • Use DEMO-GettingStartedVMs
  • Windows Azure ile Kesintisiz İş Süreci

    1. 1. Windows Azure ile Kesintisiz İş Süreci İbrahim ATAY | Software Consultant www.ibrahimatay.org | @ibrahim_atay
    2. 2. Compute Compute Inactivity Period t On & off workloads (e.g. batch job) Over provisioned capacity is wasted Time to market can be cumbersome Growing Fast t Successful services needs to grow/scale Keeping up w/ growth is big IT challenge Cannot provision hardware fast enough Unpredictable Bursting t Unexpected/unplanned peak in demand Sudden spike impacts performance Can’t over provision for extreme cases Predictable Bursting Compute Compute On and Off t Services with micro seasonality trends Peaks due to periodic increased demand IT complexity and wasted capacity Cloud Computing Patterns
    3. 3. IaaS PaaS SaaS Infrastructure-as-a-Service Platform-as-a-Service Software-as-a-Service host build consume
    4. 4. Platform Software (as a Service) (as a Service) (as a Service) Applications Data Data Data Runtime Runtime Runtime Middleware Middleware Middleware O/S O/S O/S Virtualization Virtualization Virtualization Servers Servers Storage Storage Networking Networking You manage Runtime Middleware Servers Storage Networking O/S Virtualization Servers Storage Networking Managed by vendor Data Managed by vendor Applications Managed by vendor Applications You manage Applications You manage Infrastructure Packaged Software
    5. 5. We will support Specific versions are endorsed !  *Image provided by OpenLogic based on CentOS 6.2
    6. 6. Gallery Images Available Microsoft Windows Server 2008 R2 SQL Server Eval 2012 Windows Server 2012 Biztalk Server 2013 Beta Open Source OpenSUSE 12.2 CentOS 6.3 Ubuntu 12.04/12.10 SUSE Linux Enterprise Server 11 SP2
    7. 7. http://support.microsoft.com/kb/2721672
    8. 8. Move OnPremise App Controller Manage App Controller Orchestrator Azure IP Monitor DPM App Controller Operations Manager Azure MP Advisor
    9. 9. IaaS Treat as normal server, including using a SCOM agent PaaS Monitoring is agentless, use normal API and diagnostics for monitoring Use certs for authentication System Center Operations Manager + Management Pack for Windows Azure
    10. 10. Windows Intune Macs X86/x64 AD Windows Server 2008 R2 VPN Tunnel Windows RT Windows Phone 8 iOS Windows Windows Windows Server 2012 Server 2008 Server 2003 Windows Windows Server 2012Server 2012 Android
    11. 11. Management Portal Boot VM from New Disk >_ Scripting (Windows, Linux and Mac) Cloud REST API
    12. 12. 99.95% for multiple role instances 4.38 hours of downtime per year What’s included Compute Hardware failure (disk, cpu, memory) Datacenter failures - Network failure, power failure Hardware upgrades, Software maintenance – Host OS Updates What is not included VM Container crashes, Guest OS Updates
    13. 13. Fault Domains •  Represent groups of resources anticipated to fail together •  i.e. Same rack, same server •  Fabric spreads instances across fault at least 2 fault domains Update Domains •  Represents groups of resources that will be updated together •  Host OS updates honour service update domains •  Specified in service definition •  Default of 5 (up to 20) Fabric spreads role instances across Update Domains and Fault Domains
    14. 14. Update Domains are honored by host OS updates
    15. 15. http://www.ibrahimatay.org/post/2013/4/1/A-dan-Z-ye-Windows-Azure-ile-Uygulama-Surecleri-Internet-Seminerleri-Tamamlamadi.aspx
    16. 16. İbrahim ATAY | Software Consultant www.ibrahimatay.org | @ibrahim_atay

    ×