This document outlines an Azure training course for .NET developers. The course will introduce fundamental Azure concepts like IaaS, PaaS, and SaaS. It will teach how to develop solutions on the cloud through practical lab sessions and daily coding assignments. Students will learn about scalability, billing models in Azure, and how cloud differs from on-premises infrastructure. The course aims to prepare students for Azure interviews through mock interviews and review sessions.
+97470301568>> buy weed in qatar,buy thc oil qatar,buy weed and vape oil in d...
Windows azure jump start - ppt's - 2-6-2017
1. Kick start azure course for a .NET Developer
https://www.facebook.com/Azureupdates/
@azureupdatesblog.wordpress.com
2. Need at least one azure free trial account.
Need to be well acquaintance at least in .NET & knowledge in
Infra and Networking is a big plus.
Can do Attitude :)
4. What Azure doing there ?
What are IaaS, PaaS & SaaS ?
How cloud is different from on-prem ?
Scalability, Billing in cloud ?
How do we develop solutions on cloud ?
44. Kick start azure course for a .NET Developer
Presentation Deck's - https://1drv.ms/p/s!Ahz9dAejE-aXmWuchtVQGCFsykLR
https://www.facebook.com/Azureupdates/
@azureupdatesblog.wordpress.com
Editor's Notes
Task Status - AzureJumpStart_Training_Zen3 - https://1drv.ms/f/s!Ahz9dAejE-aXmWdQSzobWqUaW32z
Session 0 Task Status File - https://1drv.ms/x/s!Ahz9dAejE-aXmWgcUV4yL_1Bc7Tt
PPT's - https://1drv.ms/p/s!Ahz9dAejE-aXmWuchtVQGCFsykLR
* Deployment Slots
-----------------------
Robust way of deploying a website
Max 5 Deployment Slots can be added
Changes are persisted with no Downtime
Types:-
Staged deployment – Website requires a testing in non prod env.
Incremental deployment – Website requires incremental steps that need to take post deployment, persist changes and then swap with prod slot.
*Rolling back deployment
Caution: Slot Resources are Shared
All deployment slots for a given website share the same web hosting plan and are created within the same virtual machine (VM) instance that is hosting the production slot. Therefore, take care when performing stress tests on a non-production slot because you will in effect be stressing the production website by virtue of stressing the VM that hosts it. Because the same VM instance is used for all slots, you cannot scale a non-production deployment slot independently of the production slot—you can only adjust the scale settings for the production slot.
* Hosting Plans :
- Two websites can participate in the same web hosting plan only when they are created in the same subscription, resource group, and region (with the same pricing tier requirements).
Thought experiment: Website deployment
You are preparing a new website for deployment and are planning how your deployment process will proceed.
1. You envision a need for multiple related deployments of the website for staging and testing purposes. Explain how deployment slots can help with this.
2. You want to guarantee that this website will have its own VM resources and not compete against other deployed websites. How can you use web hosting plans to do this?
*Objective summary
- Websites can be deployed to a primary slot or to as many as four additional slots you can use for staging or testing.
- Web hosting plans describe the capacity characteristics of the infrastructure supporting your websites as well as the pricing tier.
- Multiple websites can be hosted within a single web hosting plan.
This simplifies management of configuration in your source code. For example, code on your local machine can use a development configuration that targets only development resources, a local development database for instance, but upon deployment to the production website, the production settings can transparently override the development settings so that the code uses the appropriate production configuration, for instance to target an Azure SQL database, all without any explicit effort on your part.
*Defining and using virtual directories and virtual applications:
- Physical path site\wwwroot\static\content\current\images can be represented as \images by using Virtual Directory options
-Common scenario is to expose a subdirectory of wwwroot as the root website while also exposing a peer to that subdirectory as a separate web application. For example, under wwwroot, you might have three separate web applications:
/website
/blog
/store
Learn about Tools – AzCopy
Use Windows Powershell Tool
This objective covers how to: Automate configuration management with the Custom Script Extension and PowerShell Desired State Configuration (DSC) Enable Puppet and Chef extensions Enable remote debugging
Note: VM Agent Installation
When you create a new VM through the management portal (existing portal or Preview portal), or with Windows PowerShell, the VM Agent is installed by default on the VM. If you create a VM from the gallery, you can optionally clear the option for installing the VM Agent and later install it with Windows PowerShell if necessary.
More Info: Azure CLI
Azure CLI is an open source project providing the same functionality as the management portal via command line. It is written in JavaScript and requires Node.js. For more details, see http://azure.microsoft.com/en-us/documentation/articles/xplat-cli/.
With the VM Agent installed, you can add VM extensions. Popular VM extensions include the following:
DSC (to enable PowerShell DSC commands)
Custom Script Extension (for Windows or Linux)
Visual Studio Release Manager (DSC-based extension)
Octopus Deploy (DSC-based extension)
Docker extension
Puppet Enterprise agent
Chef client (for Windows or Linux)
*With PowerShell DSC, you can instruct a VM to self-provision to a desired state on first deployment and then have it automatically update if there is “configuration drift.” Configuration drift happens when the desired state of the node no longer matches what is described by DSC.
Exam Tip: We can use ACL to restrict access to a single host instead of the many hosts that would be described by an IP address range. To do so, when specifying the remote subnet, use the /32 subnet mask, for example 70.0.0.1/32.