1. Windows Azure
Brief intro
Windows Azure is a cloud-based operating system which enables running of business applications, services and workload in the cloud itself.
This works similar to traditional operating system functionality on any hardware platform and it allows applications to run in a virtual
environment by providing them indispensable physical hardware components and a set of services.
Microsoft designed Azure to enable .NET professionals to strengthen their capability to develop ASP.NET websites, XML and WCF web
services.
The main advantage of this is that it offers a distributed operating system in which we can build, test, and deploy applications without
worrying about the front-end interface. Moreover, we forget choices of hardware, capacity, server, location of disk space or the computer
names while using PaaS. The standard protocols such as REST and HTTP are associated with the interactions with this kind of virtual storage.
• History
Microsoft Azure, commonly referred to as Azure, is a cloud computing service created by Microsoft for building, testing, deploying, and
managing applications and services through Microsoft-managed data centres. It provides software as a service (SAAS) platform as a services
(PAAS) and infrastructure as a services (IAAS) and supports many different programming language, tools, and frameworks, including both
Microsoft-specific and third-party software and systems. Azure is the largest commercial cloud vendor by revenue, although that designation
stems in part from the company's "power of incumbency in Office 365 Commercial and Microsoft 365," which may artificially inflate the
company's "pure cloud" revenue totals.
2. Azure, announced at Microsoft's Professional Developers Conference (PDC) in October 2008, went by the internal project codename "Project
Red Dog", and formally released in February 2010, as Windows Azure before being renamed to Microsoft Azure on March 25, 2014.
• Versions
• Customers can now choose when their applications receive new operating system updates and patches by selecting which version of the
operating system their applications will run on in Windows Azure. Right now there is only one available operating system version (released on
December 17th, 2009), but new builds with the latest updates and patches will be released regularly. This new feature allows developers to
test their applications when new patches come out before upgrading their production deployments.
• To select an operating system version for your application, add the new osversion attribute to your service configuration file. The full list of
available operating system versions is maintained in the Configuring Operating System Versions topic in the Windows Azure MSDN
documentation.
•
its unique feature
• Iaas and PaaS
• Azure is the only cloud platform ranked as an industry leader by Gartner for both infrastructure-as-a-service and platform-as-a-service. It
supports various programming languages, tools and frameworks and lets you build, deploy and manage applications any way you like.
3. Hybrid Ready
Some service providers make you choose between the public cloud and your data centre. Auer offers you enterprise proven hybrid cloud solution
like amazon web services that can help you expand your IT options without added complexity. The data storage, backup and recovery become
easier with Azure. Also, it becomes easy to build applications that span both cloud and on-premises.
Open and Flexible
Azure is open and flexible and supports any language, operating system, framework right from Windows to Linux, Oracle to SQL Server, C# to
Java. It brings the best of Linux and Windows ecosystems and enables you to build robust SharePoint applications and services that works well
with every device.
Scalable and Economical
Azure is quite scalable and matches every demand so you can pay for what you use.
4. Advantage
Microsoft Azure offers high availabity.
It offers you a strong security profile.
Azure offers good scalability options.
It is a cost-effective solution for an IT budget.
There are multiple redundancies in place to maintain data access.
Azure allows you to use any framework, language, or tool.
You can automate many of your repetitive tasks.
You have access to a rich set of artificial intelligence services.
5. Disadvantage
You’ll need to manage Azure to make it effect.
You must have platform expertise available.
Azure almost forces you to put all your eggs into one basket.
Speed can be an issue for some businesses.
The ease of access may be problematic for some businesses.
6. Applications in real world
This two-part talk will explore how to build real world cloud applications using Windows Azure. The talk will cover key patterns of cloud computing
including: -Automating Everything -Source Control Best Practices - Continuous Integration/Delivery -Enterprise Identity and SSO Integration -Web
Development Best Practices Data Storage Options -Data Storage Partitioning Approaches -Using unstructured Blob storage-Designing to survive
failures_ -Monitoring and Diagnostics¢ Transient Fault Handling -Distributed Caching - Using the Queue Centric Work Pattern We'll discuss each of
the above cloud patterns in the talk, and then demonstrate how to really use them by walking through real code that shows how to leverage them
within a Windows Azure application.
The talk will cover key patterns of cloud computing including: _x000D_ _x000D_ -Automating Everything_x000D_ -Source Control Best
Practices_x000D_ - Continuous Integration/Delivery_x000D_ -Enterprise Identity and SSO Integration_x000D_ -Web Development Best
Practices_x000D_ - Data Storage Options _x000D_ -Data Storage Partitioning Approaches_x000D_ - Using unstructured Blob storage_x000D_ -
Designing to survive failures_x000D_ -Monitoring and Diagnostics_x000D_ - Transient Fault Handling_x000D_ - Distributed Caching_x000D_ - Using
the Queue Centric Work Pattern_x000D_ _x000D_ We'll discuss each of the above cloud patterns in the talk, and then demonstrate how to really
use them by walking through real code that shows how to leverage them within a Windows Azure application._x000D_
7. Installation/Usage steps
Start the installation of Windows Azure Pack: Web Sites
Install and configure Windows Azure Pack for Windows Server by following the steps in Deploy Windows Azure Pack for Windows
Server.
Determine your web sites scenario architecture by reviewing Capacity Planning for Windows azure Pack: Web sites.
Perform the Windows Azure Pack: Web Sites Pre-installation Steps.
Read the Update Rollup 6 for Windows Azure Pack:Web Sites Version 2 knowledge base article.
The following instructions give you the option to install from scratch or upgrade from a previous version. The install and upgrade
options are supported online and offline.
8. Install the Web Sites Controller with internet connectivity
If you have internet connectivity on your Web Sites Controller server, you can use these steps to install. If your server is offline, follow
the steps in the next section.
On the server that will become the Web Sites controller (for example, SitesCN1), install and start the Web Platform Installer.
On the Products tab, click Windows Azure. Click Add next to Windows Azure Pack: Web Sites v2 U6, and then click Install.
Review the items to be installed. Some of these items are third-party dependencies. For a separate reference list, see Windows Azure
Pack: Web Sites v2 U6, Click I Accept to accept the license terms.
Click Install Locally. The Windows Azure Pack: Web Sites Installer will guide you through installing and configuring an instance of
Windows Azure Pack: Web Sites on a machine connected to the internet.
Click Install Websites Controller, review and accept the Software License Terms, and then click Next.
The next screen lists the Open Source Software products used in Windows Azure Pack: Web Sites, such as Python, PHP, etc. Review and
agree to the license terms and then click Next.
After the setup tasks complete successfully, click Configure to open the Windows Azure Pack: Web Sites Management Console. Then
follow the steps under Configure the Web Sites controller section below.
9. Install the Web Sites Controller with no internet connectivity
You can install Windows Azure Pack: Web Sites on a machine not connected to the internet. To do so, you must create an installation package to
use during an offline installation as explained in the following steps:
1. On a server connected to the internet, install and start the Web Platform Installer.
2. On the Products tab, click Windows Azure. Click Add next to Windows Azure Pack: Web Sites v2 U6, and then click Install.
3. Review the items to be installed. Some of these items are third-party dependencies. For a separate reference list, see Windows Azure Pack: Web
Sites Dependencies.
4. Click I Accept to accept the license terms.
5. The Windows Azure Pack: Web Sites Installer will guide you through installing and configuring an instance of Windows Azure Pack: Web Sites for an
offline installation.
6. Click Install Offline and click Create offline installation package.
7. Review and agree to the Microsoft Software License Terms and then click Next.
8. The next screen lists the Open Source Software products that Windows Azure Pack: Websites uses, such as Python, PHP, etc. Review and agree to
the terms and then click Next.
9. After the setup tasks complete successfully, the location of the installation package is provided.
10. Copy the installation package to the Web Sites Controller server.
11. On the Web Sites Controller machine, start the Web Platform Installer.
12. Click Install Offline and then click Complete offline Web Sites controller installation.
13. Browse to the location of the installation package you have copied to the machine.
14. Click Next and you will see the progress of the installation on the controller.
15. After the setup tasks complete successfully, click Configure to open the Windows Azure Pack: Web Sites Management Console. Then follow the
steps under Configure the Web Sites controller section below.
10. Configure the Web Sites Controller
Before configuring the Web Sites Controller you must install it as explained in the previous sections.
1. Start the Windows Azure Pack Websites Management Console.
2. Step one decide whether this is a Primary Controller for a new websites cloud or whether this controller machine is going to be added to an existing
websites cloud as a secondary controller. For this walkthrough we are creating a New Websites Cloud so we will select the option to create a
Primary Controller.
3. Under Configure Websites Controller, select a Controller type and a File server type.
4. Under Databases, next to Hosting Database or and Metering Database, click Configure and enter the details of your server for the hosting and
metering databases.
5. Under System Settings, click Configure next to the following items to open dialog boxes and Enable provide the appropriate information:
DNS Suffix: Enter the DNS suffix for you farm.
automatic updating: Enable this option to update your Websites deployment automatically (recommended).
Send usage information to Microsoft: Enable this option to send usage information to Microsoft. This information is not used to identify or contact
you or your company
1. Under System Credentials, provide the required information by clicking Configure next to each setting. These credentials are required to operate
various roles and functions in the deployment.
o Administrator credential to provision front-ends, publishers, management servers and the standalone file server
o Administrator credential to provision Web worker servers
o File Shareowner credential
o FileShareUser credential
o Service Endpoint Credentials
11. Under Storage, click Change to add a server to act as a storage volume (fileserver) to store sites, configuration, assets, and certificates.
1. Under Roles, click Configure to add a server for the management server role.
2. Windows Azure Pack: Web Sites finalizes the configuration of the controller and begins configuring the management server and fileserver.
3. After configuration completes successfully, click Start to start the Web Farm Controller Service.
4. You can select Servers in the left hand pane to monitor the progress of the installation of the management server and fileserver
5. You can view the status of the role in the Trace Messages pane.
6. Windows Azure Pack: Web Sites requires at least thee more roles:
o A front end
o A publisher
o At least one web worker
You must add each of these roles by clicking Add Server and providing the following information
o Server Name
o Role: Publisher, Management, Front-End and Web Worker
o Mode (web worker only): Shared or Dedicated
o Size (web worker only): Small, Medium, or Large
1. Click the Servers node in the left pane to monitor the health and progress of these new roles. When they are all marked as Ready your Windows
Azure Pack: Web Sites Farm has been successfully provisioned.
12. Update the Web Sites Controller to Windows Azure Pack: Web Sites version 2 update 6
Windows Azure Pack: Web Sites version 2 update 6 is an optional update. For detailed information about the changes in this update, see the Update
Rollup 6 for Windows Azure Pack: Web Sites version 2 article.
You upgrade in either of two ways:
Microsoft Update
o To upgrade with Microsoft Update, you must have enabled Microsoft Update during the Web Sites Controller installation and configuration
process.
o When upgrading with Microsoft Update your system must be able to access the internet.
o If you are using WSUS to distribute the upgrade, your Web Sites Controller role must have internet access. To perform the upgrade, use the
standard Windows update console and select Update for Windows Azure Pack Version 2.
Web Platform Installer (select the Windows Azure Pack Web Sites version 2 update 6 option)
o If the configuration portal that is a part of the normal installation experience pops up, simply close it.
Upgrade with internet connectivity
When upgrading, you must update on each Web Sites Controller role as explained in the following steps:
Start the installer from either Microsoft Update or the Web Platform Installer.
If you want to install the upgrade on a controller with no internet connectivity, click Update Websites Controller, click Install Offline,
and then click Create an offline Installation Package. See the steps under Install or upgrade the Web Sites Controller with no internet
connectivity section of this document.
Review and accept the Software License Terms and then click Next.
The next screen lists the Open Source Software products used in Windows Azure Pack: Web Sites, such as Python, PHP etc. Review and agree to the
license terms and then click Next.
13. After the setup tasks complete successfully, click Configure to open the Windows Azure Pack: Web Sites Management Console so that you can view the
progress of the update on the other roles in the farm.
Upgrade without internet connectivity
When upgrading, you must update on each Web Sites Controller role as explained in the following steps:
1. On a server connected to the internet, start the installer from either Microsoft Update or the Web Platform Installer.
2. Click Update Websites Controller, click Install Offline, and then click Create an Offline Installation Package.
3. Review and accept the Software License Terms and then click Next.
4. The next screen lists the Open Source Software products used in Windows Azure Pack: Web Sites, such as Python, PHP etc. Review and agree to the
license terms and then click Next.
5. After the setup tasks complete successfully, the location of the installation package is provided.
6. Copy the installation package to the Web Sites Controller machine.
7. On the Web Sites Controller machine, run the installer again.
8. Click Install Offline and click Complete offline Websites Controller update.
9. Browse to the location of the installation package you have copied to the machine.
10. Click Next.
11. After the setup tasks complete successfully, click Configure to open the Windows Azure Pack: Web Sites Management Console so that you can view
the progress of the update on the other roles in the farm.
14. Conclusion
Container-based solutions ultimately provide cost savings benefits. Containers are a solution to deployment problems because they remove the
friction caused by an absence of dependencies in production environments. By removing those issues, it improves Dev/Test, DevOps, and
production operations significantly.
A Docker container is becoming the standard unit of deployment for any server-based application or service.
For production environments, you should use an orchestrator (like Kubernetes) to host scalable containers–based applications.
Azure VMs hosting containers are a fast and simple way to create small Dev/Test environments in the cloud.
Azure SQL Database Managed Instance is recommended by default when migrating your relational databases from existing applications to Azure.
Visual Studio 2017 and Image2Docker are basic tools for you to start modernizing your existing .NET applications with Windows Containers by
accelerating the getting started learning curve.
When placing containerized applications in production you will always create or adopt a DevOps culture and DevOps tools for CI/CD pipelines, like
Azure DevOps Services or Jenkins.
Microsoft Azure provides the most comprehensive and complete environment to modernize your existing .NET Framework applications with
Windows Containers, cloud infrastructure and PaaS services.