When creating an "Instance Template," there is an option under "Boot Disk" > "Show Advanced Configuration" to add a snapshot schedule. When you click the dropdown, it shows "There are no schedules in GLOBAL."
How do you add a GLOBAL Snapshot Schedule? I have several Snapshot schedules that do not have a GLOBAL option to select, and none appear in the list.
Related
I have a requirement to incrementally copy data from one SQL table to another SQL table. The watermark or key column is an Identity column. My boss wants me to restart the load as soon as it's done...and as you know, the completion time may vary. In Azure Data Factory, the trigger options are Scheduled, Tumbling Window and Custom Event. Does anyone know which option would allow me to achieve this continuous running of the pipeline and how to configure it?
Create a new pipeline. Call it "run forever". Add an "until" activity with a never-true condition e.g. #equals(1, 2).
Inside the until execute the pipeline which copies between tables. Ensure "wait for completion" is ticked.
If the table copy fails then "run forever" will fail and will have to be manually re-started. You likely do not want "run forever" to be scheduled as the scheduled invocations will queue should it, in fact, not fail.
Pipeline in ADF are batch-based. You can set "micro batches" of 1 min with schedule trigger or 5 mins with tumbling window.
ADF will run in a batch. If you want to continuously load the data then you can go for Stream Analytics / Event Hub which would load real-time data
I have a project in Azure DevOps where there are multiple epics, each with features and tasks. Is there a way to assign the epic with all its features and tasks to me without having to go to each feature and to each task inside and assign them to me one by one?
You can do these things easily through the queries tab:
Make it a Tree of work items:
Set the top level work item type to Epic and the relationship to parent/child:
Save the query:
Switch to the results tab. Hit ctrl-a to select all the results. Use the ... and pick Assign to >:
Hit Save Items....
And as it turns out, you can do the same from the Backlogs tab. Make sure you select the Epics level, ctrl-a and basically follow the same steps (but you have to expand all the levels manually it seems):
Currently, we manually set the iteration as Current iteration in Azure Devops (VSTS):
Could you please help how this can be automated? So we do not have set for every iteration.
I have tried all possible ways through web UI.
To set a default Iteration path for newly created workitems, go to 'Project Settings > Team Configuration'.
Use #CurrentIteration for the default iteration path. This will automatically map to todays valid iteration (by start and end date).
There is no need to do that manually.
Once you work with iteration dates (Start date, End date) for your sprints, Azure DevOps will automatically determine which sprint is the current one.
All steps to schedule a sprint date are described here.
Tasks are a child of Backlog Items or Bugs and by default inherit the iteration of the Backlog Item or Bug that they are created under.
So you don't have to always set them manually, do the following:
If it is a new backlog item,
Go to the Backlog for your current sprint, create a backlog item or bug and the iteration path will automatically be set to the current sprint because you created it in the context of the sprint. Now when you add tasks they too will have the same iteration.
If backlog item exists but no tasks yet,
If you already have a backlog item that is sitting on the backlog (not in a sprint backlog yet) move the backlog item to your sprint first, then create tasks underneath
If your backlog items and tasks are already created,
You can set the iteration path for all of them at once by using multi select and edit (shift+click) to select then select ... menu and select edit. You can then select Iteration Path for the field and select the sprint you want to set and then click Save.
We are creating deployments with TFS 2018.3. If I click on tasks in a deployment and create a Task Group out if it, it recognizes the used parameters but if I change parameter usage in an already existing Task Group, or edit the newly create group, parameter changes are not applied to the parameter list in the group.
I deleted the existing stages in Odoo project and created three stages:
Todo
Doing
Done
How to ensure that the tasks moved to "Done" are assumed as complete (ie. they are no longer highlighted with RED after assigned deadline)?
I tried enabling the Debug view and "Edit Workflow" from the Projects page. The workflow is empty. There is an option to "Import" a csv file. Is there a way to generate this CSV?
Update1:
Based on this bug/explanation , I think I have deleted the stages. (extract below)
Bug Description
This is a usability issue:
After creating a new project, A Project Manager clicks on it project
at the Project Kanban view and navigates to the Task Kanban View.
There he deletes one of the Stage, to remove it from it's project
stage list. However, this actually deletes the Stage from the Stages
table, so it's also removed from all other projects.
My suggestion is to remove the Stages "delete" option at Kanban Views:
this should be done only on the Project's definitions Stage list.
Is it possible to restore the original stages so that I can use the stage "Completed" for marking tasks as complete?
Mark the stage "Done" as a 'folded' state.
The original stage definitions are contained in the file addons/project/project_data.xml and marked as no_update=='1' so that they will not be recreated upon updating the project module.
There are three 'folded' stage definitions, which you can refer to with the external IDs project.project_tt_merge, project.project_tt_deployment (labeled 'Done'), and project.project_tt_cancel.
These are suggestions only and can certainly be deleted and replaced with your own definitions.
Configure the "Done" activity with the "flow_stop" attribute set to True. That is the way a workflow instance is considered completed.
Info: https://www.odoo.com/documentation/8.0/reference/workflows.html