Enrique lima azure-it-pro-ps

Editor's Notes

• #7: Slide Objectives: Describe the various computing patterns that are good for Cloud Computing Speaking 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 business Cover the workloads in the slide
• #8: Slide Objectives: Explain the three established terms in the industry for cloud services Speaking 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.
• #9: 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 Software With packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaS With 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 OS The 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. PaaS With 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. SaaS Finally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
• #10: Slide Objectives: Provide a high level summary of Windows Azure and what it enables at a high level Speaking Points: What is Azure? Flexible Windows Azure is now more flexible then ever before Windows Azure helped pioneer the concept of Platform as a Service It provides a rich set of managed services enabling you to compose applications. We’re now making those services richer. With the June update we have now have enabled infrastructure as a service. Including the ability to host and deploy durable virtual machines in the cloud running both Windows and Linux Open Some of you maybe surprised to hear Linux at a Microsoft conference. Our support of Linux is just one example of how we’re embracing openness in a fundamental new way. With the June release we are supporting more operating systems, more languages, and more open protocols Releasing all of the Azure SDKs on GitHub under an open source license. Summary We believe the end result is truly a unique model You can now use both platform as a service and infrastructure as a service *together* You can now use the best of the Microsoft ecosystem and the best of the open source ecosystem *together* Enabling you to build better and more scalable solutions. Notes: Comprehensive set of services that enable you to build, host and scale applications in Microsoft datacenters Windows Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.
• #11: Slide Objectives: Discuss the instance sizing and costs Speaking Points:
• #13: Slide Objective: You need an availability set for a 99.95% SLA Notes: Without at least two virtual machines performing the same workload grouped into an availability set you get a 99.95% SLA.
• #14: Slide Objectives: Speaking Points: Windows Azure runs on datacenters around the world Enabling you to deploy and run applications and infrastructure close to your customers. Notes: 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.
• #15: Slide Objectives: Discuss Windows Azure Country Availability Speaking Points: Windows Azure is now available in over 89 countries and territories. Anyone within these countries can sign up for a free trial or a paid subscription to use Windows Azure services Of course you can build and deliver solutions to any of your customers worldwide
• #17: Slide Objectives: Describe the three main feature components of Windows Azure that will be discussed through the rest of the presentation. You should state to the audience you will not be covering Mobile Services or Media Services, so you might want to spend a little more time now to explain these.
• #19: Slide Objectives: Explain how to setup a subscription Notes: The .publishsettings file contains your subscription information, the service endpoint, subscription name and certificate. Once downloaded the Import-AzurePublishSettingsFile cmdlet will install the certificate and configure your PowerShell environment.
• #20: Slide Objectives: Use this method if you want to specify a certificate that you have created on your own.
• #21: Slide Objectives: Explain where subscription settings are persisted Notes: The subscription XML file supports multiple subscriptions. You can use a single PowerShell session to administer VMs and services across all of your configured subscriptions.
• #22: Slide Objectives: Explain how to switch contexts when scripting against multiple subscriptions Notes: Get-AzureSubscription returns all configured subscriptions and Select-AzureSubscription sets the current subscription
• #23: Slide Objectives: Explain how to set the current storage account that the cmdlets will use. Notes: Certain cmdlets like New-AzureVM or New-AzureQuickVM require the user to specify the storage account to use. Since each subscription can contain multiple storage accounts the property name to set is CurrentStorageAccount. This allows you to easily change the storage account for the next operation.
• #24: Slide Objectives: To create a VM you either need to start with an Image or Disk and specify the location where to place the VM.
• #26: Slide Objectives: Show three examples that show a key component of using the cmdlets. Notes:When you specify -Location or -AffinityGroup the cmdlets will attempt to create a new cloud service to deploy the VM to. If you do not specify either the cmdlets assume the cloud service exists in the current subscription.
• #27: Slide Objectives: With PowerShell you can configure various settings in a batch Notes: New New-AzureVMConfig and New-AzureVM to allow a batched creation of a VM. New-AzureVMConfig returns a configuration object that is then passed to other cmdlets to modify via the PowerShell pipeline. Finally, it is passed to New-AzureVM where the VM is created with all of the configuration specified.
• #28: Slide Objectives: It is also possible to create multiple configuration objects for multiple VMs and pass them to the New-AzureVM cmdlet as an array.
• #29: Slide Objectives: Another example of batch VM creation: using an array/loop to create multiple VMs
• #30: Slide Objectives: Explain other common settings used to provision a VM
• #31: Slide Objectives: The Add-AzureProvisioningConfig cmdlet supports two parameter sets for Windows. Notes: -Windows allows just setting the password of the VM on boot. -WindowsDomain allows you to specify all of the settings necessary to have the VM join the domain on boot. This scenario only works in a VNET environment where the DNS specified knows how to have the VM find the domain controller. -DisableAutomaticUpdates allows for disabling automatic updates by default. Available to both parameter sets. -NoRDPEndpoint does not create the RDP endpoint on creation. Of course you can add this later through PS or the Portal. -TimeZone allows you to specify the VMs timezone on provisioning. -Certificates allows you to automatically install certificates on the VM on provisioning. Note: the certificates must already be installed in the cloud service. For an example: http://michaelwasham.com/2012/08/23/deploying-certificates-with-windows-azure-virtual-machines-and-powershell/
• #32: Slide Objectives: The Add-AzureProvisioningConfig cmdlet supports one parameter set for Linux Notes: The Linux parameter set requires specifying the user name and also allows for disabling SSH on the Linux VM or just not adding the SSH endpoint. Additionally, you can deploy SSH certificates as long as they are already in the cloud service.
• #33: Slide Objectives: Deploying into a Virtual Network requires multiple settings. Notes: When configuring the VM you must specify the subnet using the Set-AzureSubnet cmdlet. You can only specify the VNET and DNS settings for a cloud service on the creation of the first VM. If you add a second VM to the cloud service it will inherit the networking settings.
• #34: Slide Objectives: In this example we’re specifying two AD/DNS servers – one that lives on our on-premises environment and the other is a DC that lives in the cloud. Notes: You can pass the DNS names when calling New-AzureVM. Also required is the VNET that establishes the hybrid connectivity.
• #35: Slide Objectives: Show different methods of discovering virtual machines
• #36: Slide Objectives: Explain storage options
• #37: Slide Objectives: Show examples of configuring storage Notes: The first example creates a new VM with a 10GB disk attached. The second example gets an existing VM, adds a 10GB disk to it and updates it live.
• #38: Slide Objectives: Explain disk caching defaults and how to modify it Notes: By default OS disks have read / write caching enabled and data disks have no caching. You can use Set-AzureOSDisk or Set-AzureDataDisk to modify these settings at run time. Set-AzureOSDisk requires a reboot.
• #39: Slide Objectives: Demonstrate how to configure network endpoints on a VM
• #40: Slide Objectives: Numerous examples that show how to filer output from the disk and image repository.
• #41: Slide Objectives: Show how you can iterate through a list of VMs (like all VMs that have a name starting with wfe and perform an update such as adding a new disk and removing an endpoint.
• #42: Slide Objectives: Show how to capture a VM
• #43: Slide Objectives: Operations allowed from PowerShell for updating an modifying VNET Settings.
• #60: Slide Objectives: Summarize presentation