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/
Related
I have an HDInsight cluster in Azure Government and want to add an additional storage account that resides in Azure Government.
I’m attempting to do this via the portal’s Script Actions > + Submit New > Add an Azure Storage account and providing my Azure Government storage account’s name and key.
This fails with the error (from the cluster’s output file in /var/lib/ambari-agent/data/output-XXXX.txt):
Key encryption is enabled STORAGE ACCOUNT IS: testgovwebiaasdiag
Validate storage account creds: Invalid Credentials provided for
storage account ('Start downloading script locally: ',
u'https://hdiconfigactions.blob.core.windows.net/linuxaddstorageaccountv01/add-storage-account-v01.sh')
Fromdos line ending conversion successful ('Unexpected error:',
"('Execution of custom script failed with exit code', 139)")
Looking at the documentation for “Add additional storage accounts to HDInsight”, there is no indication that this script supports Azure Government.
What is the recommended path forward? Should I download the script and modify it? If so, what modifications are needed to support Azure Government?
At this time, the out of the box "Add additional storage accounts to HDInsight" script does not support Azure Government.
This is because it does not allow for the storage endpoints to be set for the different Azure Government endpoints.
I have created this script which supports Azure Goverment. It is a modified version of the out of the box one that overrides the endpoints with those for Azure Government.
You can use this script via Script Actions > + Submit New > - Custom and provide this URI in the Bash script URI. You can then provide the same parameters, storage account name and storage account key and run you script.
To get support for Azure Government in the out of the box script, please vote for this in the Azure Government feedback forum: Support for Azure Government storage accounts in HDInsight
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'm using Azure Storage Explorer to connect to storage accounts that I've created by hand on Azure. However when I go to browse the storage account that was created by Azure when I created a Media Services account, I'm unable to connect to it.
I'm using blob.core.windows.net as the storage endpoint domain, and setting the storage account name and storage account key to be the same as Azure has defined it in the dashboard, but attempts to connect (with or without HTTPS) result in a 502-Bad Gateway HTTP error.
I'd like an easy way to browse all media files I've created without having to write special code. Has anyone been able to get this to work?
All storage accounts regardless the way they are being created are browsable with Storage Explorer!
For such storage accounts, created when you Create Media Services, you have to use the Storage Account Name and Storage Account Key, but not the Media Service Account Name and Media Service Account Key! You will not be able to access Storage service with Media Key and vice-versa.
When you create a Media Services account, one/multiple storage accounts could be attached to a particular media services account. Let's say your account name is "MediaStorage123". I believe you need to pass the following data to storage explorer:
Account name/key: this can be found in the bottom of your storage account page in Azure portal: press Manage Key button you will see the data.
storage endpoint domain: Not sure why you need this, but if so, you can see the information in Dashboard of your media services account: https://xxx.blob.core.windows.net/.
Hope this helps.
Just for the record, In my case (with the use of proxy) I had do install a previous version of the Azure Storage Explorer
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.