Operating Your Deployment

Once you’ve successfully created a deployment, you’ll be redirected to its Deployment View. This page provides all the tools you need to operate, monitor, and manage your deployment.

Summary

The Deployment View makes it possible to:

• Operate and automate your deployment lifecycle
• Manage users and permissions
• Track costs and operations
• Maintain order, visibility, and control

Deployment View Overview

The Deployment View is composed of several key sections:

1. Header – Displays the deployment name and its current state.
2. Tags Section – Lets you view, add, or remove tags for your deployment. See Tagging for more details.
3. Operations Bar – Contains operational controls such as start, stop, patch, and more. See Operations.
4. Grid Layout – Displays deployment-specific widgets in a customizable grid. To learn more about navigating or editing the grid, refer to the Portal/Grid documentation.

Operations

The Action Bar provides the most common operations you’ll use to manage your deployment:

1. Start Deployment

Starts all underlying resources of the deployment. Resources start in the order defined in your Start Sequence configuration. See Set Start/Stop Sequence for details.

2. Stop Deployment

Stops all underlying resources of the deployment. The stop order follows your Start Sequence in reverse.

3. Manage Patching

Opens the Patching Dialog, where you can assign a patch schedule to resource groups.

4. Manage Schedule

Allows you to define automated operations (such as Start and Stop) using cron expressions. See Set Schedules for more details.

5. Edit Deployment Info

Opens a dialog to edit basic information such as Display Name and Description.

6. Move Deployment

Lets you move the deployment to a different parent collection. You’ll see a preview of the new technical name before confirming the move.

7. Delete Deployment

Deletes the deployment and all of its children. To confirm, you’ll need to type the deployment’s display name before deletion.

Set Start/Stop Sequence

You can define a start/stop sequence that controls the order in which resources are started, stopped, or restarted. (Does not apply to patching)

How It Works

• Access this feature through the Start/Stop Sequence widget.
• By default, all compute nodes are placed in a single batch named Batch 0.
• Batches define execution order:
  • Resources in the same batch run in parallel.
  • Batches run sequentially.
• The Stop sequence runs in reverse order of the Start sequence.
• Sequences are applied at each start and stop of the deployment. So whenever start/stop gets triggered via the action bar or by a schedule.

Editing the Sequence

1. Click the pen icon to switch to edit mode. The icon will change to a check icon.
2. Drag and drop to move resources into new batches.
3. Dragging a resource to the “New Batch” area automatically creates a batch.
4. Reorder batches using the drag handle on the right.
5. Optionally, set a delay for each batch to define waiting time between executions.

⚠️ Important: The delay gets executed after the operation for the current batch is done. Example -> Batch 0 with a database resource gets started. The delay will kick in for 5 min after the db resource has started and is running. Once the 5 minute delay is over the next batch will be executed.

Set Schedules

Schedules allow automated deployment operations such as Start and Stop at specific times.

How to Set a Schedule

Open the Manage Schedule dialog from:

• The Action Bar, or
• The Schedule widget.

Select the Start or Stop tab.

1. Enable the schedule using the Enable Schedule checkbox.
2. Enter a cron expression in the input field.
   • A link to crontab.guru and an info icon are available for guidance.
   • The cron expression is saved in UTC.
3. Review the human-readable summary and the “Next 3 Runs” preview.
4. Click Save to assign the schedule to your deployment.

⚠️ Important: Cron expressions are stored in UTC. Always verify the “Next 3 Runs” preview to ensure correct timing.

Viewing and Managing Schedules

• The Start/Stop Schedules widget displays:
  • A table of schedules on the left
  • A timeline on the right showing the next two runs
• Hover over or select a table row to highlight runs in the timeline.
• To delete a schedule, click the bin icon in the Actions column and confirm.

Currently, only one schedule per action (Start or Stop) is supported. Editing a cron expression will update the existing schedule.

User Management

The Users widget lists all users assigned to the deployment by role.

For more information, you can check out the Portal/Permissions(Owners) documentation page.

Patching

To view or manage patching information for your deployment and its underlying resources:

• Navigate to the Patching widget.
• From here, you can assign or modify patch schedules.

For detailed instructions, refer to the Portal/Patching documentation.

Cost Tracking

The Costs widget provides insights into monthly and historical costs.

Features

• View current and past monthly costs.
• Set a Monthly Budget by clicking the pen icon.
• Adjust the Budget Warning Threshold (in %) using the slider.

Notifications

• When costs exceed your threshold:
• A warning flag appears under the Action Bar.
• Optionally, enable email notifications for alerts.

Job Insights

Most operations in Dune generate a Job, allowing you to track their progress.

Jobs Widget

• Displays a sortable table of jobs (latest first).
• Expand a row to view job details.
• Click a job to open a side-by-side view with the job events.
  • Resize the panes using the divider.
  • Close the details view by dragging the divider to the right or clicking the close icon.

Tagging

Tags allow you to categorize and identify deployments easily.

Adding Tags

1. Click the Plus icon of Add Tag chip below the deployment title.
2. Enter a Key (required) and Value (optional).
3. Click Add to create the tag.
   • Tags are also synchronized with Azure.

Removing Tags

• Click the Minus icon next to a tag.
• Confirm deletion when prompted.