@@ -77,6 +77,17 @@ the configuration drive built by Bifrost during provisioning.
77
77
``overcloud_dib_env_vars_extra ``.
78
78
``overcloud_dib_packages ``
79
79
List of DIB packages to install. Default is to install no extra packages.
80
+ ``overcloud_dib_git_elements_default ``
81
+ List of default git repositories containing Diskimage Builder (DIB)
82
+ elements. See stackhpc.os-images role for usage. Default is empty.
83
+ ``overcloud_dib_git_elements_extra ``
84
+ List of additional git repositories containing Diskimage Builder (DIB)
85
+ elements. See stackhpc.os-images role for usage. Default is empty.
86
+ ``overcloud_dib_git_elements ``
87
+ List of git repositories containing Diskimage Builder (DIB) elements. See
88
+ stackhpc.os-images role for usage. Default is a combination of
89
+ ``overcloud_dib_git_elements_default `` and
90
+ ``overcloud_dib_git_elements_extra ``.
80
91
``overcloud_dib_upper_constraints_file ``
81
92
Upper constraints file for installing packages in the virtual environment
82
93
used for building overcloud host disk images. Default is ``{{
@@ -154,6 +165,28 @@ Alternatively, the :diskimage-builder-doc:`dynamic-login element
154
165
<elements/dynamic-login/README> ` can be used to authorize SSH keys by appending
155
166
them to the kernel arguments.
156
167
168
+ Example: Configuring custom DIB elements
169
+ ----------------------------------------
170
+
171
+ Sometimes it is useful to use custom DIB elements that are not shipped with DIB
172
+ itself. This can be done by sharing them in a git repository.
173
+
174
+ .. code-block :: yaml
175
+ :caption : ` ` overcloud-dib.yml``
176
+
177
+ overcloud_dib_elements_extra :
178
+ - " my-element"
179
+
180
+ overcloud_dib_git_elements :
181
+ - repo : " https://git.example.com/custom-dib-elements"
182
+ local : " {{ source_checkout_path }}/custom-dib-elements"
183
+ version : " master"
184
+ elements_path : " elements"
185
+
186
+ In this example the ``master `` branch of
187
+ https://git.example.com/custom-dib-elements would have a top level ``elements ``
188
+ directory, containing a ``my-element `` directory for the element.
189
+
157
190
Example: Installing a package
158
191
-----------------------------
159
192
0 commit comments