Deploying to gh-pages from @ dstackai/dstack@916b94e 🚀

Author: peterschmidt85

docs/concepts/fleets/index.html

@@ -886,6 +886,19 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#spot-policy" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        <span class="md-typeset">
+          Spot policy
+        </span>
+      
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -4179,6 +4192,19 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#spot-policy" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        <span class="md-typeset">
+          Spot policy
+        </span>
+      
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -4624,12 +4650,32 @@ <h4 id="pre-provisioning">Pre-provisioning<a class="headerlink" href="#pre-provi
 </details>
 <h3 id="resources">Resources<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h3>
 <p>Backend fleets allow you to specify the resource requirements for the instances to be provisioned. The <code>resources</code> property syntax is the same as for <a href="../dev-environments/#resources">run configurations</a>.</p>
-<blockquote>
-<p>Not directly related, but in addition to <code>resources</code>, you can specify <a href="../../reference/dstack.yml/fleet/#instance_types"><code>spot_policy</code></a>, <a href="../../reference/dstack.yml/fleet/#instance_types"><code>instance_types</code></a>, <a href="../../reference/dstack.yml/fleet/#max_price"><code>max_price</code></a>, <a href="../../reference/dstack.yml/fleet/#max_price"><code>region</code></a>, and other <a href="../../reference/dstack.yml/fleet/">options</a>.</p>
-</blockquote>
-<!-- TODO: add dedicated spot policy example -->
+<h3 id="spot-policy">Spot policy<a class="headerlink" href="#spot-policy" title="Permanent link">&para;</a></h3>
+<p>Backend fleets allow you to specify a <code>spot policy</code>. By default, it is set to <code>on-demand</code>. If you want to use spot instances, you must set it to <code>auto</code> if you plan to use both on-demand and spot instances, or to <code>spot</code> if only spot instances are allowed.</p>
+<div editor-title="fleet.dstack.yml"> 
+
+<div class="highlight"><pre><span></span><code><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">fleet</span>
+<span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">my-fleet</span>
+
+<span class="nt">nodes</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">0..2</span>
+
+<span class="c1"># Uncomment to ensure instances are inter-connected</span>
+<span class="c1">#placement: cluster</span>
+
+<span class="c1"># Allows both on-demand and spot</span>
+<span class="nt">spot_policy</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">auto</span>
+
+<span class="nt">idle_duration</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1h</span>
+
+<span class="nt">resources</span><span class="p">:</span>
+<span class="w">  </span><span class="nt">gpu</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">0..8</span>
+</code></pre></div>
+
+</div>
 
+<p>Note that run configurations must specify their own <code>spot policy</code> which is also set to <code>on-demand</code> by default.</p>
 <h3 id="backends_1">Backends<a class="headerlink" href="#backends_1" title="Permanent link">&para;</a></h3>
+<p>Backend fleets allow you to set <code>backends</code> to specify which backends are allowed to be used.</p>
 <h3 id="idle-duration">Idle duration<a class="headerlink" href="#idle-duration" title="Permanent link">&para;</a></h3>
 <p>By default, instances of a backend fleet stay <code>idle</code> for 3 days and can be reused within that time.
 If an instance is not reused within this period, it is automatically terminated.</p>
@@ -4754,7 +4800,7 @@ <h3 id="environment-variables">Environment variables<a class="headerlink" href="
 </code></pre></div>
 <div class="admonition info">
 <p class="admonition-title">Reference</p>
-<p>The fleet configuration file supports many more options. See the <a href="../../reference/dstack.yml/fleet/">reference</a>.</p>
+<p>The fleet configuration file supports additional options, including <a href="../../reference/dstack.yml/fleet/#instance_types"><code>instance_types</code></a>, <a href="../../reference/dstack.yml/fleet/#max_price"><code>max_price</code></a>, <a href="../../reference/dstack.yml/fleet/#max_price"><code>regions</code></a>, among others. For the complete list, see the <a href="../../reference/dstack.yml/fleet/">reference</a>.</p>
 </div>
 <h2 id="manage-fleets">Manage fleets<a class="headerlink" href="#manage-fleets" title="Permanent link">&para;</a></h2>
 <h3 id="list-fleets">List fleets<a class="headerlink" href="#list-fleets" title="Permanent link">&para;</a></h3>

docs/concepts/fleets/index.md

@@ -281,12 +281,38 @@ Pre-provisioning is supported only for [VM-based backends](backends.md#vm-based)
 
 Backend fleets allow you to specify the resource requirements for the instances to be provisioned. The `resources` property syntax is the same as for [run configurations](dev-environments.md#resources).
 
-> Not directly related, but in addition to `resources`, you can specify [`spot_policy`](../reference/dstack.yml/fleet.md#instance_types), [`instance_types`](../reference/dstack.yml/fleet.md#instance_types), [`max_price`](../reference/dstack.yml/fleet.md#max_price), [`region`](../reference/dstack.yml/fleet.md#max_price), and other [options](../reference/dstack.yml/fleet.md#).
+### Spot policy
 
-<!-- TODO: add dedicated spot policy example -->
+Backend fleets allow you to specify a `spot policy`. By default, it is set to `on-demand`. If you want to use spot instances, you must set it to `auto` if you plan to use both on-demand and spot instances, or to `spot` if only spot instances are allowed.
+
+<div editor-title="fleet.dstack.yml"> 
+
+```yaml
+type: fleet
+name: my-fleet
+
+nodes: 0..2
+
+# Uncomment to ensure instances are inter-connected
+#placement: cluster
+
+# Allows both on-demand and spot
+spot_policy: auto
+
+idle_duration: 1h
+
+resources:
+  gpu: 0..8
+```
+
+</div>
+
+Note that run configurations must specify their own `spot policy` which is also set to `on-demand` by default.
 
 ### Backends
 
+Backend fleets allow you to set `backends` to specify which backends are allowed to be used.
+
 ### Idle duration
 
 By default, instances of a backend fleet stay `idle` for 3 days and can be reused within that time.
@@ -432,7 +458,7 @@ ssh_config:
 ```
 
 !!! info "Reference"
-    The fleet configuration file supports many more options. See the [reference](../reference/dstack.yml/fleet.md).
+    The fleet configuration file supports additional options, including [`instance_types`](../reference/dstack.yml/fleet.md#instance_types), [`max_price`](../reference/dstack.yml/fleet.md#max_price), [`regions`](../reference/dstack.yml/fleet.md#max_price), among others. For the complete list, see the [reference](../reference/dstack.yml/fleet.md).
 
 ## Manage fleets
 

llms-full.txt

@@ -1995,12 +1995,38 @@ Pre-provisioning is supported only for [VM-based backends](backends.md#vm-based)
 
 Backend fleets allow you to specify the resource requirements for the instances to be provisioned. The `resources` property syntax is the same as for [run configurations](dev-environments.md#resources).
 
-> Not directly related, but in addition to `resources`, you can specify [`spot_policy`](../reference/dstack.yml/fleet.md#instance_types), [`instance_types`](../reference/dstack.yml/fleet.md#instance_types), [`max_price`](../reference/dstack.yml/fleet.md#max_price), [`region`](../reference/dstack.yml/fleet.md#max_price), and other [options](../reference/dstack.yml/fleet.md#).
+### Spot policy
+
+Backend fleets allow you to specify a `spot policy`. By default, it is set to `on-demand`. If you want to use spot instances, you must set it to `auto` if you plan to use both on-demand and spot instances, or to `spot` if only spot instances are allowed.
+
+<div editor-title="fleet.dstack.yml"> 
+
+```yaml
+type: fleet
+name: my-fleet
+
+nodes: 0..2
 
-<!-- TODO: add dedicated spot policy example -->
+# Uncomment to ensure instances are inter-connected
+#placement: cluster
+
+# Allows both on-demand and spot
+spot_policy: auto
+
+idle_duration: 1h
+
+resources:
+  gpu: 0..8
+```
+
+</div>
+
+Note that run configurations must specify their own `spot policy` which is also set to `on-demand` by default.
 
 ### Backends
 
+Backend fleets allow you to set `backends` to specify which backends are allowed to be used.
+
 ### Idle duration
 
 By default, instances of a backend fleet stay `idle` for 3 days and can be reused within that time.
@@ -2146,7 +2172,7 @@ ssh_config:
 ```
 
 !!! info "Reference"
-    The fleet configuration file supports many more options. See the [reference](../reference/dstack.yml/fleet.md).
+    The fleet configuration file supports additional options, including [`instance_types`](../reference/dstack.yml/fleet.md#instance_types), [`max_price`](../reference/dstack.yml/fleet.md#max_price), [`regions`](../reference/dstack.yml/fleet.md#max_price), among others. For the complete list, see the [reference](../reference/dstack.yml/fleet.md).
 
 ## Manage fleets