- Microsoft Azure - Scenarios
- Microsoft Azure - Datacenters
- Microsoft Azure - Security
- Microsoft Azure - Applications
- Microsoft Azure - CDN
- Microsoft Azure - Tables
- Microsoft Azure - Queues
- Microsoft Azure - Blobs
- Microsoft Azure - Storage
- Microsoft Azure - Fabric Controller
- Microsoft Azure - Compute Module
- Microsoft Azure - Components
- Microsoft Azure - Windows
- Cloud Computing - Overview
- Microsoft Azure - Home
Microsoft Azure Advanced
- Microsoft Azure - Upgrades
- Microsoft Azure - Health Monitoring
- Azure - Orchestrated Recovery
- Azure - Security Reports & Alerts
- Microsoft Azure - Create a Group
- Microsoft Azure - Self-Service Group
- Azure - Self-Service Password Reset
- Azure - Personalize Company Brand
- Microsoft Azure - Personalize Access
- Microsoft Azure - Disk Caching
- Microsoft Azure - Disk Configuration
- Microsoft Azure - Scalability
- Microsoft Azure - Websites
- Azure - Data Import & Export Job
- Azure - Forefront Identity Manager
- Azure - Multi-Factor Authentication
- Azure - Self-Service Capabilities
- Microsoft Azure - Backup & Recovery
- Azure - Application Deployment
- Azure - Setting Up Alert Rules
- Azure - Monitoring Virtual Machines
- Microsoft Azure - PowerShell
- Microsoft Azure - Traffic Manager
- Azure - Site-to-Site Connectivity
- Azure - Point-to-Site Connectivity
- Azure - Endpoint Configuration
- Azure - Deploying Virtual Machines
- Azure - Create Virtual Network
- Microsoft Azure - Management Portal
Microsoft Azure Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Microsoft Azure - Upgrades
Let us say, that our services are running fine on Azure. After sometime, we need to make changes and upgrade the services which are already running. Here comes the tricky part, sometimes upgrading would go smooth and sometimes you won’t know what is causing the problem. Windows Azure has tried to address these issues.
Update a Cloud Service
The apppcation code can be updated easily in Azure management portal. You will need a service package (.cspkg) and service configuration files (.cscfg) before moving ahead.
Step 1 − Login to the management portal.
Step 2 − Go to the service you want to update.
Step 3 − Cpck ‘Instances’ from the top menu and then cpck ‘update’. The following screen will pop up.
Step 4 − Enter the deployment label name and upload .cspkg and .cscfg files.
Step 5 − Select the role you want to update or select ‘all’ if want to update all roles.
Step 6 − Check the checkbox as required and cpck the ‘Arrow’ on the right side.
VIP (Virtual IP) Swap
You might come across a scenario, when you need to make changes to the architecture of service. Azure provisions a way which can handle the upgrading easily. There are two deployment environments - production and staging. Let’s assume that your service is at production, but you can deploy the new version in the staging environment. After that you just test it and if everything is fine, you swap it with the production deployment. Behind the scene, the virtual IPs of production and staging deployment are swapped, hence staging becomes production and production becomes staging. While the swapping happens, the service is not interrupted. All this is done with no downtime for service. It also makes it easy to rollback to older production version in case you need to do it.
Step 1 − Login to the management portal.
Step 2 − Go to the service. Select ‘Instances’ from the top menu. You can see in the following screen, two instances are there for this service.
Step 3 − When you have deployed the service in staging and production you will see that ‘Swap’ at that bottom of the screen is activated. You just have to cpck that Swap icon and it will be done.
Considerations
You can’t swap if you have different number of endpoints for each deployment.
It does not change the IP address of your service.