fba2902dc6
Currently the only way to specify the CPU architecture of the overcloud images is by setting it in the appropriate yaml file. This is fine until you need to install a single package on multiple CPU architectures. Then you're either going to attempt to build the wrong image type or you have to edit the yaml files, which makes problems for upgrades. This change removes the default architecture from the yaml files and defaults to the appropriate DiB architecture based on running kernel. This enables builds on multiple CPU architectures from a single unmodified package Change-Id: I34f00a30c1e07869243fb95a437e05d6973a97da
7 lines
247 B
YAML
7 lines
247 B
YAML
---
|
|
features:
|
|
- |
|
|
The default architecure for image builds now defaults to the cpu of the
|
|
host instead of x86_64/amd64. This allows for a single package of
|
|
tripleo-common to be used across multiple architectures to generate images.
|