- Microsoft Azure Tutorial
- Microsoft Azure - Home
- Cloud Computing - Overview
- Microsoft Azure - Windows
- Microsoft Azure - Components
- Microsoft Azure - Compute Module
- Microsoft Azure - Fabric Controller
- Microsoft Azure - Storage
- Microsoft Azure - Blobs
- Microsoft Azure - Queues
- Microsoft Azure - Tables
- Microsoft Azure - CDN
- Microsoft Azure - Applications
- Microsoft Azure - Security
- Microsoft Azure - Datacenters
- Microsoft Azure - Scenarios
- Microsoft Azure Advanced
- Microsoft Azure - Management Portal
- Azure - Create Virtual Network
- Azure - Deploying Virtual Machines
- Azure - Endpoint Configuration
- Azure - Point-to-Site Connectivity
- Azure - Site-to-Site Connectivity
- Microsoft Azure - Traffic Manager
- Microsoft Azure - PowerShell
- Azure - Monitoring Virtual Machines
- Azure - Setting Up Alert Rules
- Azure - Application Deployment
- Microsoft Azure - Backup & Recovery
- Azure - Self-Service Capabilities
- Azure - Multi-Factor Authentication
- Azure - Forefront Identity Manager
- Azure - Data Import & Export Job
- Microsoft Azure - Websites
- Microsoft Azure - Scalability
- Microsoft Azure - Disk Configuration
- Microsoft Azure - Disk Caching
- Microsoft Azure - Personalize Access
- Azure - Personalize Company Brand
- Azure - Self-Service Password Reset
- Microsoft Azure - Self-Service Group
- Microsoft Azure - Create a Group
- Azure - Security Reports & Alerts
- Azure - Orchestrated Recovery
- Microsoft Azure - Health Monitoring
- Microsoft Azure - Upgrades
- Microsoft Azure Useful Resources
- Microsoft Azure - Quick Guide
- Microsoft Azure - Useful Resources
- Microsoft Azure - Discussion
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 application 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 − Click ‘Instances’ from the top menu and then click ‘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 click 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 click 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.