Adds a new pkg-map element which can be used to install packages based on an in element 'pkg-map' JSON config file format. As part of this change we expose DIB's IMAGE_ELEMENT variable so that we can have access to the element names which are being installed in a clean manner. This change is intended to decouple elements from DIB and allow new elements to support multiple distributions (with various package naming schemes) without having to constantly maintain DIB's various bin/map-packages files. Change-Id: Ic0a061995e2ae708c95a535cba6237bff58f7d93
2 KiB
Map package names to distro specific packages.
Provides the following:
-
bin/pkg-map
usage: pkg-map [-h] [--element ELEMENT] [--distro DISTRO]
Translate package name to distro specific name.
optional arguments: -h, --help show this help message and exit --element ELEMENT The element (namespace) to use for translation. --distro DISTRO The distro name to use for translation. Defaults to DISTRO_NAME
-
Any element may create its own pkg-map JSON config file using the one of 3 sections for the distro/family/ and or default. The family is set automatically within pkg-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: using fictitious package names for Fedora to provide a good example!)
Example format: { "distro": { "fedora": { "nova_package": "openstack-compute", "glance_package": "openstack-image" } }, "family": { "redhat": { "nova_package": "openstack-nova", "glance_package": "openstack-glance" } }, "default": { "nova_package": "nova", "glance_package": "glance" } }
Example commands using this format:
pkg-map --element nova-compute --distro fedora nova_package
Returns: openstack-compute
pkg-map --element nova-compute --distro rhel nova_package
Returns: openstack-nova
pkg-map --element nova-compute --distro ubuntu nova_package
Returns: nova
-
This output can be used to filter what other tools actually install (install-packages can be modified to use this for example)
-
Individual pkg-map files live within each element. For example if you are created an Apache element your pkg-map JSON file should be created at elements/apache/pkg-map.