ee46e2f9b7
Make a version-less RHEL element to handle both '7' and '8' DIB_RELEASE.
The element usage should align with other elements which operate in the
same way such as the Fedora element.
Additionally, this patch adds support for RHEL8 that operates with
Python 3.
As of now, users of diskimage-builder will still be able to use the
'rhel7' element, or migrate to 'rhel' and specify their respective
DIB_RELEASE value.
* mount the xfs file-system for extraction as read-only. vaguely
based on explaination in [1] and the fact we only read the image
data into a tar, so can ignore this.
XFS (dm-1): Superblock has unknown read-only compatible features (0x4) enabled.
* Use the redhat system python as the dib-python version. dib was
ahead of it's time making an abstracted python interpreter for
system work ;) the system python should work for running the various
dib element scripts.
[1] https://unix.stackexchange.com/questions/247550/unmountable-xfs-filesystem
Redhat-Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1700253
Co-Authored-By: Ian Wienand <iwienand@redhat.com>
Change-Id: I90540675c70bb475d9db2ae24f81c648a31f3f95
|
||
|---|---|---|
| .. | ||
| bin | ||
| extra-data.d | ||
| tests | ||
| README.rst | ||
| __init__.py | ||
| package-installs.yaml | ||
| pkg-map | ||
README.rst
svc-map
Map service names to distro specific services.
Provides the following:
bin/svc-map
usage: svc-map [-h] SERVICE
Translate service name to distro specific name.
- optional arguments:
-h, --help show this help message and exit
Any element may create its own svc-map YAML config file using the one of 3 sections for the distro/family/ and or default. The family is set automatically within svc-map based on the supplied distro name. Families include:
- redhat: includes centos, fedora, and rhel distros
- debian: includes debian and ubuntu distros
- suse: includes the opensuse distro
The most specific section takes priority. Example for Nova and Glance (NOTE: default is using the common value for redhat and suse families)
The key used for the service name should always be the same name used for the source installation of the service. The svc-map script will check for the source name against systemd and upstart and return that name if it exists instead of the mapped name.
Example format for Nova:
nova-api: default: openstack-nova-api debian: nova-api nova-cert: default: openstack-nova-cert debian: nova-cert nova-compute: default: openstack-nova-compute debian: nova-compute nova-conductor: default: openstack-nova-conductor debian: nova-conductor nova-consoleauth: default: openstack-nova-console debian: nova-consoleExample format for Glance:
glance-api: debian: glance-api default: openstack-glance-api glance-reg: debian: glance-reg default: openstack-glance-registryIf the distro is of the debian family the combined services file would be:
nova-cert: nova-cert nova-compute: nova-compute glance-api: glance-api nova-conductor: nova-conductor nova-api: nova-api glance-reg: glance-reg nova-consoleauth: nova-consoleIf the distro is of the suse or redhat families the combined services file would be:
nova-cert: openstack-nova-cert nova-compute: openstack-nova-compute glance-reg: openstack-glance-registry nova-conductor: openstack-nova-conductor glance-api: openstack-glance-api nova-consoleauth: openstack-nova-console nova-api: openstack-nova-apiExample commands using this format:
svc-map nova-compute Returns: openstack-nova-compute svc-map nova-compute Returns: openstack-nova-compute svc-map nova-compute Returns: nova-computeThis output can be used to filter what other tools actually install (install-services can be modified to use this for example)
If you pass more than one service argument, the result for each service is printed on its own line.
Individual svc-map files live within each element. For example if you have created an Apache element your svc-map YAML file should be created at elements/apache/svc-map.