I'm deploying Webjob with automate deployment in Azure portal in staging slot, but the problem is this webjob is running directly after deployment and it might cause a confusion between the main slot webjob and the staging one.
Is there a way to deploy the webjob without running it unless I start it and swap slots?
Related
i will be using helm charts to deploy my application in GCP.i want to make my springboot shutdown after completing its process and then on next day start on its own at a particular time -complete the process and shut down .Is this possible in GCP?
You can use Cloud Run Jobs or Batches to complete that and by paying ONLY when you process consume ressources. (Not the case with Kubernetes and GKE where you pay for your cluster (and your node pools) even if nothing runs on it)
I have a small staging and Production setup in AWS for a workflow service where I am trying to implement SQS service. I have created a queue for staging that works fine and similarly another queue for production that seems to be working fine. The challenge is that for now we create an image of the staging server after patches and update and then use that as the base image in production autoscaling. Problem with this approach is that application still points to staging queue. Is there a way to update queue settings on the runtime or through startup configuration file etc. so it points to the right queue or a better way to implement this (without deploying a full ci/cd pipline etc)? I don't have dev background so any help will be appreciated.
I have an app running in cloud foundry which has been working fine for months, but has suddenly stopped responding. The errors in the log are all related to connecting to a postgres database service. I don't really know how to administer this sort of thing in cf, so I decided to just remove the app and service and redeploy from scratch.
However I can't remove the app or service - all requests are blocked due to an in progress operation between the app and service.
For example:
Job (ac7753ee-19e8-4b7a-9f39-85284167fb7d) failed: The service broker rejected the request due to an operation being in progress for the service binding.
So I can't delete the app because it is bound to the service, and I can't unbind the app and service because there is an operation in progress.
What can I do?
For now, to get you unstuck you could try cf purge-service-instance instead, this removes the service instance without making a call to the broker.
I want to schedule restart for an app so is there any way that applications will be restarted automatically after specific timelimit in PCF?
I am not sure if there is anything within PCF that can execute CF Commands. My suggestion is to have a CI/CD Job Configured (Jenkins-Job for example) that will execute cf restart <app_name> at scheduled Intervals
I've been working on a scheduler service which you can register at Cloud Foundry containing service plans also for restarting apps. There are also other service plans like just triggering an arbitrary http-endpoint. I'd be happy if you try it out and provide me feedback. Just check it out in GIT: https://github.com/grimmpp/cloud-foundry-resource-scheduler
I've also started to describe what is provides and how it can be installed and configured. For using it you just need to create service instances in the marketplace of cloud foundry and specify some parameters for e.g. how often or when it should be called. ...
I am trying to deploy a triggered webjob and schedule it with settings.json file. My webapp runs in 3 instances so I assume the webjob will be deployed in 3 instances.
So if I schedule the webjob with settings.json file with cron expression will the job run in all the instances? I am assuming that setting the "is_singleton" to true will make it run only on one instance? But if the instance in which it is running fails, will Azure failover the webjob in spite of the is_singleton setting?
You shouldn't need to use is_singleton in this case. For each schedule occurence, the runtime will pick an instance at random and run your job. Each schedule occurrence will run on one instance only, as you would expect.
If a schedule occurrence is missed or fails, the runtime will try to get back on schedule by running the function again. You can see that logic in the source here.