You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,3 +17,28 @@ This collection includes content for interacting with OpenStack clouds.
17
17
- os_projects
18
18
- os_ratings
19
19
- os_volumes
20
+
21
+
### Changing platform architecture in os_images
22
+
23
+
The `Generate diskimage-builder images` job in the ``os_images`` role can build an
24
+
image for a chosen CPU architecture by defining the ``cpu_arch`` image property before
25
+
calling the ``os_images`` role. This is an [example](https://github.com/stackhpc/kayobe/blob/18ca11b47af42ce10507516c2f9e34f447d5e39a/ansible/overcloud-host-image-build.yml#L21_)
26
+
of a playbook calling the ``os_image`` role & below is an example of how to set the
27
+
``cpu_arch`` image property in a configuration like StackHPC-Kayobe-Config:
28
+
29
+
```yaml
30
+
stackhpc_overcloud_dib_host_image:
31
+
name: "{{ image_name }}"
32
+
elements: "{{ dib_elements }}"
33
+
env: "{{ dib_env_vars }}"
34
+
packages: "{{ dib_packages }}"
35
+
properties:
36
+
- cpu_arch: "arm64"
37
+
```
38
+
39
+
The ``cpu_arch`` variable will also be set as an image property within the `Upload
40
+
cloud tenant images` task in the ``upload.yml`` task.
41
+
42
+
If left unset the ``cpu_arch`` variable will default to `x86_64` for ``upload.yml``.
43
+
However, if not set, the `Generate diskimage-builder images` job will takes the
0 commit comments