My Web Role is on StorageAccount1 and my Azure Storage Table on StorageAccountB.
My Web Role performs operations (inserts, updates, queries) on the Storage Table.
Both of these Storage Accounts are in the SAME Affinity Group.
Will performance be better if my Web Role and Storage Table are in the same Storage Account?
You are probably confused by the "Publish" window in Visual Studio. The "Publish" window allows you to choose some info on how your application is deployed, like the Cloud Service but also the Storage Account. When you choose a storage account it doesn't mean your application will be stored in that storage account, it only means that the service package (the package which contains your application) will be uploaded there. Once the package is uploaded the Fabric Controller will take it and deploy it to your Cloud Service.
Besides that it's still a good idea to deploy your Cloud Service (Web Role) in the same affinity group as your Storage Account. By choosing the same affinity group Windows Azure will try to physically group your Cloud Services and Storage Accounts to minimize the network overhead.
Related
In Azure I have 2 load balanced VMs with an IIS shared config. These are linked to a premium storage account. All up and running. I have persisted the premium fileshare to both VMs as a drive (S).
The wwwroot is on the storage account, along with the IIS config files.
The app pool is set up as the storage account password so I have access the the share.
All good up to this point.
My issue is that the app also needs to see data on another fileshare. (general fileshare, not premium). This will be used for storage and Archive.
The problem is that the IIS app pool is configured with the creds for the premium storage and fails when trying to also use the general storage.
Can this be done?
Is there a way to link to both fileshares in IIS or should I be looking somewhere else?
Thanks
Colin
I am trying to integrate my odoo with azure blob storage, how can I do that?
you should checkout the capabilities of odoo on their documentation page: https://docs.bitnami.com/azure/faq/
There is a section of the supported capabilities in Azure as bellow:
The Bitnami Launchpad for Microsoft Azure creates the following resources in your Microsoft Azure account:
A storage account for each region in which the user launches an instance.
Application images are added to that storage account when the user launches instances.
Machine disks are created in that storage account when the user launches instances.
A resource group with the rest of the resources needed by the instance.
A resource group for the various storage accounts.
Source: https://docs.bitnami.com/azure/faq/
Where can I find the file share associated with the App Service?
I can view the files from Kudo console, but I don't see the share on my Storage Account using either the portal or Storage Explorer.
While the files are backed by a storage account, it is in a platform account and not one of your own accounts. That's why you cannot see the files in storage explorer. It's also why you can create a Web App without specifying a storage account.
One exception is for Azure Functions on Consumption plan, where the user storage account is used, and you'd see the Azure Files in storage explorer.
I want to deploy cloud service to Azure, but when deploying must select Storage Account(tried both in new portal and in Visual Studio 2015). My storage account was created using new portal "Storage accounts" and was assigned to some Resource group, as a result I can't choose it when deploying. Any suggestions how to deploy?
One possible reason is that the storage account created by the new portal was likely created under the resource manager deployment model, while the cloud service is still under the classic deployment model. These don't play well together. You can read a little more at https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/. I don't think that a cloud service can use a resource manager storage account for deployment.
In the new portal look at the All Resources blade. If the storage account has a green icon it is a resource manager account. If the storage account has a blue icon it's a classic account.
Create a new storage account as a classic account, either by creating it in the older portal or by using the drop down in the new portal before you click create on the blade that talks about the storage accounts (the before you provide the account name, etc.). Once you do this then I think the account show show up as an option for your cloud service to deploy with.
Also note that if the storage account was created just prior to trying to select it, it might take a minute or two to become visible as an option.
I just created a windows 2012 datacenter VM in azure, however I notice in management portal that Azure also created a cloud service with same name. Is this normal?I don't want to be double charged..
This is normal. You are not charged for Cloud Services. You're only charged for actual VM's deployed in them. Cloud Service is just a record in a database and a concept that is used to group Azure resources together