I noticed that the time required for reboot is different between Docs and Portal.
Which is correct?
Docs
1
Portal
2
Related
I am trying to use the "FREE" layer of Azure App Services using the GitLab Container Registry.
To do the DEPLOY I am using WebHook, but I am not having success. I call WebHook to start Deploy (via Postman) and when analyzing the deployment LOGs, nothing happens.
The strangest thing is that at times it works, but it seems to be only once a day.
I call WebHook as follows:
https://$<my-app>:<token>#<my-app>.scm.azurewebsites.net/docker/hook
Are there any limitations for being a free tier?
#Junior, please note that with Web Apps free tier there are a few quotas.
The two that you might be hitting are:
You can only use the CPU 3 out of every 5 minutes
You can only use the CPU 60 minutes every 24 hours
Source:https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits
Windows Web Apps have a quota blade that allow you to see if you are actively hitting a quota. I would suggest checking there. Also check the diagnose and solve blade for your app to verify one of the above quotas are being hit.
I have started to use Azure Update Management, but I am finding that it is missing updates, which show up when I go into the VM I am running it against, then to Windows Updates.
For Example, in Azure Update Management, for VM1 I can see the following as outstanding:
But if I log into VM1 and open Windows Update, I see the following:
But isn't the Update Management showing these updates, which are available if I go into the VM.
I have also noticed that for some VM's, Azure Update Management reports that during the scheduled deployment, a certain KB has successfully installed, but if I log into the VM and go to Windows Update, it shows as available to be installed.
how to schedule web jobs with day light saving. we have schedule web jobs on azure to run service(15:00 UTC and 8:00 MST) but when day light saving start it run 9 AM MST. could you please tell me, how to manage fix it.
If your app is hosted on Azure Virtual Machines, you have complete access to the VM so you can configure the time zone to whatever you want.
If your app is hosted on Azure Cloud Services, it is possible to write a startup script that calls the tzutil utility to change the time zone; however this isn’t recommended and can apparently lead to instability.
If your app is hosted as a Web App on the Azure App Service (formerly known as Azure Websites), until recently you were completely out of luck. However, there is now an easy and supported way to change the time zone for your w3wp process (and any processes it spawns):
All you need to do is add an Application Setting (via the portal or the management APIs) called WEBSITE_TIME_ZONE and set that to the name of the time zone as defined in the Windows Registry under HKLM\Software\Microsoft\Windows Nt\CurrentVersion\Time Zones\ (for example, “AUS Eastern Standard Time”).
Refer: Add DST timezone support for webjobs
I'm able to register my existing Azure VM as build agent in VSTS. Build works fine but I would like to turn the machine on and off only if there is any work for it. Is there any way how I can turn on the VM if I see there is some work for it in a queue and then turn it off if the queue is idle for let's say 5 minutes?
Add a hosted agent job to the start to start the VM and add an agent job or additional step to the end to shut down the VM when finished.
Add an Agent job to run this as hosted to start the VM. Then use all build steps as self-hosted(private).
Add your Azure subscription
Choose Inline Script to add the following to start it with VM name and resource group
start-AzureRmVM -Name ""-ResourceGroupName ""
Add another Agent Job or additional step as the last Step
To shut down the VM when the build has finished.
With the following Script
stop-AzureRmVM -Name ""-ResourceGroupName "" -Force
I'm wondering if this could be helpful for you because this is not exactly what you asked for. I used REST API calls before the build and after the build to start and then stop a specific VM. See how to start and power off a VM in the API documentation.
I created an agentless job as the first step, with a task entitled Invoke REST API. The task lets you authenticate to your Azure account, so you don't have to handle that manually. All you have to do is specify the URL suffix. For instance, to start a VM named MyVm, you add a suffix similar to the following one:
/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.Compute/virtualMachines/MyVm/start?api-version=2018-06-01
where the subscription ID and resource group can be verified in the Overview page of your virtual machine in Azure.
After the build you can add another agentless job, but this time with a REST call of the powerOff endpoint:
/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.Compute/virtualMachines/MyVm/powerOff?api-version=2018-06-01
There isn’t the good way to start/stop azure VM when build in VSTS. Regarding WebHook, there isn’t the event for queue build, for other events, they aren’t meet many requirements (e.g. non-CI build, queue build manually)
I recommend you use Hosted agent, with free Hosted Pipeline, you get 4 hours (240 minutes) per month and maximum duration of 30 minutes per build or deployment in Team Services.
How to buy more pipeline capacity for builds and releases in Visual Studio Team Services
Workaround:
Queue build at the specify time, for example, 7:00 am on Monday and Thursday, then you can auto-start and auto-shutdown the VM
Run on Hosted agent (Execute Powershell to start VM)=> Run on private agent
More information, you can refer to: How to Create a Monster Build Agent in Azure for Cheap
You could try using a WebHook in VSTS, and select the most appropriate event (like code pushed, or release created). Open the admin page for the team project in Visual Studio Team Services, and on the Service Hooks tab, run the subscription wizard, select the event you're interested in, and fill in the relevant criteria.
You could then use an Azure Automation Runbook to subscribe to the WebHook and, using PowerShell, either use the build VM if it's already started or else start it up. You could use another WebHook to signal that a build has been completed, or poll VSTS from the VM via its various APIs.
You might want to delay shutting the VM down after a build, as there is a time cost associated with starting up / shutting down.
I am new to Microsoft Azure and I started deploying visual studio with windows 10 and tried all different versions (Enterprise, Professional). After 20 minutes deployment, I get same error which is as follows: These are in my audit log.
OPERATION NAME Microsoft.Compute/virtualMachines/write
PROPERTIES: statusCode:Conflict statusMessage:{"status":"Failed","error":{"code":"ResourceDeploymentFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"OSProvisioningTimedOut","message":"OS Provisioning for VM 'ShaunPsm' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later."}]}}
Hint: I started my subscription today. I also in my subscription I have visual studio enterprise.
Is there any solution? thank you in advance.
Did you assign a storage account for your azure project. If not do that first.
Try taking package of the azure solution
Right click azure project > Package >
select Cloud, Release and take package.
Then goto azure portal and create a cloud service, then upload package.
select check boxes to overwrite existing roles. then press OK.