How to configure failover for a cosmosdb serverless account? - azure

CosmosDB serverless account doesn’t support automatic-failover? I have checked for documentation and SLA and have not found anywhere on how to configure serverless account failover etc.
Any help would be appreciated!

The answer is NO, have you looked at the serverless documentation.
A serverless account can only run in a single Azure region. It is not
possible to add additional Azure regions to a serverless account after
you create it.
which means you cannot configure by any ways.

Related

Is Terraform the official Infrastructure as code solution for IBM Cloud?

Every major cloud provider like AWS or Google Cloud provide their own solutions for infrastructure as code (cloud formation, cloud deployment management).
As far as I am aware IBM used to have its own solution but now all I see is on Terraform.
That observation seems correct, IBM Cloud settled on Terraform to provide automation for deploying resources.
You need to set up the IBM Cloud provider for Terraform, configure and then you can deploy resources. Details on the different resources and how to specify them can be found in the IBM Cloud Provider for Terraform docs.

Alternative to using Azure Cloud service in a CSP subscription

Team,
I have a complete running cloud service application upgraded to latest Azure SDK version and unfortunately need to dump this into a CSP subscription. But I came to know that Azure CSP supports only the Azure Resource Manager model, the cloud service is a classic deployment model. So we cannot create a cloud service within a CSP subscription.
Is there any other alternative within Azure CSP to using "cloud service" so that we can migrate with minimal changes. Please help
Firstly, here are some good reads on Microsoft Docs to help comparing the options available and make decisions based on your requirements:
(I mean requirements like Hosting features, Service Limits, 3rd party software installation and RDP access is required or not, Network isolation to a separate VNET is required or not, Cost considerations, minimum SLA, Regions available, instant deployment and auto-scaling, state management etc.):
Azure App Service, Virtual Machines, Service Fabric, and Cloud Services comparison
Decision tree for Azure compute services (This one covers a big spectrum.. simple virtual machines, Batch, Functions, Containers, AKS, ServiceFabric)
Criteria for choosing an Azure Compute Service
Also know that when looking for alternatives, it's not uncommon to make use of multiple compute or other Azure service options by breaking up an older solution into parts at the time of such migration (for e.g. A serverless compute option like Azure Function + Service Fabric + something else if needed).
Generally speaking (and without knowing much about your application from your question currently), Azure App Service and Service Fabric could be considerations IMHO when migrating from an existing Cloud Service, but this is exactly where detailed requirements help you in decision making.
On a side note, here is a list of Azure Services available in CSP - Available Azure services in Azure CSP

How do I create Internal Load Balancer (ILB) using Azure Management SDK?

I want to configure an ILB for my Azure Cloud Service, similar to discussed in this article https://azure.microsoft.com/en-us/documentation/articles/load-balancer-internal-getstarted/
- but using the .Net SDK instead of powershell. (Also I have some conceptual confusion about the article/powershell maybe people will be able to explain. For VM scenario you have to explicitly create the ILB, but it seems like for cloud service you do not - is it already created, or automatically created? Why are New-AzureVM commandlets being used in a cloud service context?)
Documentation has been updated
https://azure.microsoft.com/en-us/documentation/articles/load-balancer-get-started-ilb-classic-cloud/
Or are you looking for a C# sample?
You should probably not be using cloud services. These are being deprecated. Just use v2 - Azure Resource Manager (portal.azure.com) and create a load balancer instead of a cloud service. Regardless, in v1 (Azure Service Management), when you create a VM, you automatically get a cloud service if you don't have one already - which is why new-azurevm is being used in cloud service context.

Moving Azure Instance to AWS

I have received $200 credit to host my 2 Windows Azure Cloud projects on AWS. Just wondering what the quick and dirty process is to migrate my Visual studio projects to being published on the AWS cloud?
I could seem to find much documentation available, with the exception that apparently it's possible.
Are you using Cloud Services (web role), an Azure Web Site, or a VM? Depending on how the ASP.NET MVC code is written, you could provision whatever compute capability you need in AWS and deploy there.
The blob storage would likely be the problem. That is unless the code has an abstraction layer to isolate the app from storage implementation details. Azure blob storage and whatever you using in AWS have different platform APIs.

Has Any one tried in Deploying the package programatically in Azure

Has Any one tried implementing deployment of Azure CSPKG deployment programmatically using Service Management REST API. Please share with me any guideline or website which explain me clearly. Especially I Want my Web ROle to deploy the Worker ROle where package is in Azure blob storage.
Check out this article by Neil Mackenzie. This covers working with the REST API to perform deployments. Also, you could check out the code that is used under the hood by the Windows Azure PowerShell cmdlets by looking in the code on GitHub.

Resources