Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I want to make sure I am taking the right approach.
I am building virtual environments in Azure on a regular anywhere from 3 to 5 servers at a time. Each server has 1 of 4 different resources (RAM/CPU/...) that it will need. Obviously I could script out each VM and just use powershell to deploy each individual VM each time.
More over what I want is a utility or webpage where I can say I need to create x servers and here are the specifications for them, how much will it cost and make it start building them.
Is there any tool like this or what would be the best approach to this?
You could automatically create Azure resources from a Resource Manager template. You create a template file that deploys the resources and a parameters file that supplies parameter values to the template.
Also, you could easily edit and deploy the template on the Azure portal. In this way, you could search Template----Deploy from a custom template---Build your own template in the editor. You could reuse the template after you save it. You could find multiple guidances and sample about the template what you want to deploy.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
Is Azure appropriate for building an entire database-backed website, with custom tables on the backend, and custom pages, forms, and CSS on the frontend?
Like any database-backed website, there should be facility for backend logic in response to client-browser GET & POST requests.
Which Azure resources are appropriate? Logic Apps?
Sharing an answer i received on MSDN. (not sure yet if i will mark this one as best answer):
While is it possible, you have better options to consider.
If you are building a JS-powered frontend (using Angular/React), you could host the static assets directly on blob storage and expose it as a static website. The doc also covers how you could add a CDN to it for faster delivery to your customers.
The backend could be built entirely using Azure Functions. If you are using Table Storage or CosmosDB, there are bindings available that you could use and simplify the code that you would have to manage.
If you have background workflows (like batch jobs) that you have to run, then Logic Apps are indeed a good option. For complex use cases, Durable Functions might be a better fit though.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Our application is currently an ASP.NET Core application hosted on Azure and our code and pipelines are hosted on Azure Dev Ops. The app is pretty simple with just a Web Application and Azure SQL Database.
We currently have a large number of tenants that we would like to deploy to after each release.
We currently have 3 Build Pipelines (which are triggered off dev, test and master branches):
- Dev
- Test
- Production
Where I currently get lost is on where to put the individual tenants, our current path was to make a "Release" pipeline for every tenant. Is this the best way to do this? Should we be using stages instead?
I'm a bit confused as to why you have separate build pipelines for dev, test, and production.
You might consider consolidating all of your pipelines (build and release) into a single YAML pipeline. Under this approach, you'd have 1 build stage which you would capture as a YAML stage template and make use of expressions/conditions to account for the variances between the various environments. Alternatively, if the build process varies widely between environments, you could have separate build stage templates for each and include the appropriate one based on branch that triggered the build.
For releases, you could capture each as a YAML template and then include them at the end of the pipeline using the new deployment job element that has been added to the YAML schema.
Hopefully this gets you closer to a solution or at least gives you some things to think about.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
All these Azure technologies (Bots, FaaS, Logic Apps and Runbooks) are used to run schadule jobs.
I don't know when we should use these and which scenario we should use them.
YMMV, but here are some pretty good rule of thumbs:
Are you doing PowerShell based Automation work? If Yes, consider Azure Automation Runbooks.
Are you building a bot? If Yes, consider the Azure Bot Framework service.
Are you build a workflow that executes on a timer, especially one that integrates with other services (etc.)? If Yes, consider Logic Apps.
Are you writing generic application code? If Yes, consider Azure Functions.
If none of those fit, I'd be surprised, but you might try starting with Azure Functions since we're kind of an "Everything as a Service", but there is a reason we have the different products - they specialize to enable better productivity within their specialty (Bots, Automation, and Integration).
Note: I'm one of the PMs on the Azure Functions team here at Microsoft.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
We've recently set-up our resources in our Azure Portal and especially giving rights was a lot of work.
I wonder if we did it correctly and in the proper order. Our web application seems to work fine.
Next week our client wants us to set-up our environment in his account. This time I want to do it properly ;)
What is the best approach to do this? I don't want to bother him everytime I need to change something.
The situation:
2 developers. 1 of them (myself) needs to add extra resources.
1 resource group
Web app using the S1 plan
4 deployment slots. 2 will be created right away, the other two later
1 Storage account
1 SQL Server
1 Elastic pool
Several SQL databases. Some will be created by code.
The last time I needed to give my co-worker access to each resources in the project. I assume that can be done eassier.
What role do I need myself to be able to access all resources and create deployment slots, create databases and set-up continuous build?
Assuming that all the relevant resources are located in the same resource group (which is the recommended pattern), you just need to give Contributor access to the resource group, and it will apply to everything in it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
How to use REST API to add a VM role?
I can't use this http://msdn.microsoft.com/en-us/library/windowsazure/jj157184.aspx to delete a VM. Do I need some other steps for that?
And also I want to get some code for adding a VM Role to existed VM Role service.
I think Autoscaling will solve all of your problems here. Check out this guide to get you started.
With autoscaling, you can set up rules to add/remove instances on a deployment based on certain events or constraints. This can run on-premise or on a separate worker role. If you use WASABi, then you won't have to mess with making the role management API calls yourself.
I hope this helps, if you have any specific questions just ask and I will do my best to answer them.
I have also posed a few errors I have encountered and the solutions for them on my blog.