sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
761fb12682
diskimage-builder/diskimage_builder/elements/simple-init/pkg-map

44 lines
980 B
Plaintext
Raw Normal View History

Add element to process config-drive network info If you don't want cloud-init, you may need to get a few things from config-drive because you may be operating on a cloud with no DHCP. In that case, simply reading some values from config-drive and writing out either DHCP or static network info, in addition to grabbing ssh keys is helpful. Both Infra and bifrost want this for their images. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I2746ed256b9783eab058b803130d3ccac484eaeb
2015-03-23 20:48:51 +00:00
{
"family": {
"redhat": {
simple-init: support installing Glean from packages Such package is in progress for RDO: Depends-On: https://review.rdoproject.org/r/c/openstack/glean-distgit/+/32656 Change-Id: I2655b6b9037477c26743d51b0c9a9e31a23707fb
2021-03-22 17:04:31 +00:00
"dhcp-client": "dhclient",
"glean": "python3-glean"
Add element to process config-drive network info If you don't want cloud-init, you may need to get a few things from config-drive because you may be operating on a cloud with no DHCP. In that case, simply reading some values from config-drive and writing out either DHCP or static network info, in addition to grabbing ssh keys is helpful. Both Infra and bifrost want this for their images. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I2746ed256b9783eab058b803130d3ccac484eaeb
2015-03-23 20:48:51 +00:00
},
"debian": {
Use generic "dhcp-client" name Every platform has a different name for their DHCP client, so use a generic name "dhcp-client" in the package name and let everyone choose their sub-name. This also brings some consistency across simple-init & dhcp-all-interfaces Change-Id: I797aa7aacb13dfb7f35700463dc11d55552eb108
2016-04-01 00:12:29 +00:00
"dhcp-client": "isc-dhcp-client",
simple-init: allow for NetworkManager support This plumbs through an "--use-nm" flag to glean which instructs it to setup interface bringup with NetworkManager rather than legacy network enablement scripts. In this case, install the NetworkManager package. In the non-nm case, also install the network-scripts for Fedora 29 -- this has stopped being installed by default (it's been deprecated since forever). As noted in the docs, this is currently really only relevant on the supported rpm distros which are using the ifcfg-rh NetworkManager plugin to effectively re-use old config files. However, NetworkManager has similar plugins for other platforms, so support can be expanded if changes are proposed. Depends-On: https://review.openstack.org/618964 Change-Id: I4d76e88ce25e5675fd5ef48924acd09915a62a4b
2018-11-20 23:36:12 +00:00
"ifupdown": "ifupdown",
"NetworkManager": "network-manager"
Add support for gentoo to simple-init Needed to remove interface config Depends-On: Id1487bc82ee4b03aa57258f71f48ca7d377afc47 Change-Id: Iaa1a16b0f65c088f03c9b440ef16427e93ec9b03 Closes-Bug: 1537453
2016-01-28 22:14:24 +00:00
},
"gentoo": {
Use generic "dhcp-client" name Every platform has a different name for their DHCP client, so use a generic name "dhcp-client" in the package name and let everyone choose their sub-name. This also brings some consistency across simple-init & dhcp-all-interfaces Change-Id: I797aa7aacb13dfb7f35700463dc11d55552eb108
2016-04-01 00:12:29 +00:00
"dhcp-client": "net-misc/dhcp",
Add support for gentoo to simple-init Needed to remove interface config Depends-On: Id1487bc82ee4b03aa57258f71f48ca7d377afc47 Change-Id: Iaa1a16b0f65c088f03c9b440ef16427e93ec9b03 Closes-Bug: 1537453
2016-01-28 22:14:24 +00:00
"python-pip": "dev-python/pip",
"net-tools": "sys-apps/net-tools"
Fix OpenSUSE support The dhcp-all-interfaces and simple-init elements did not have the ISC DHCP Client package mapped for OpenSUSE, which caused DIB to fail with "'isc-dhcp-client' not found in package names. Trying capabilities." Similarly, the bootloader element did not have the grub-pc package properly mapped for OpenSuse, which caused DIB to fail with "Package 'grub-pc' not found.". This patch adds the package mappings for these elements so that the opensuse element can be created and booted successfully. Change-Id: Ife478158fec3a95de73a9206b38dcc6511d56cc8
2016-05-04 05:23:51 +00:00
},
"suse": {
Enable nodepool testing for opensuse 15.1 There are several jobs depending on working opensuse 15.1 images in nodepool, so it makes sense to ensure its working. Also upgrade the previously marked experimental opensuse-15.0 job as it tests the xenial->opensuse combination, which is particularly difficult to keep working and we'll need it in the CI. Change-Id: Icb6d998756ce5221e017959dcb59b21f0f023454
2019-06-26 07:50:44 +00:00
"dhcp-client": "dhcp-client",
"network-scripts": "wicked-service"
Add element to process config-drive network info If you don't want cloud-init, you may need to get a few things from config-drive because you may be operating on a cloud with no DHCP. In that case, simply reading some values from config-drive and writing out either DHCP or static network info, in addition to grabbing ssh keys is helpful. Both Infra and bifrost want this for their images. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I2746ed256b9783eab058b803130d3ccac484eaeb
2015-03-23 20:48:51 +00:00
}
},
Fedora 32 support Update for Fedora 32 support. Change-Id: I51c5645856a76e2877c013d72e9849a758ba12ff
2020-06-22 06:35:44 +00:00
"distro": {
simple-init: allow for NetworkManager support This plumbs through an "--use-nm" flag to glean which instructs it to setup interface bringup with NetworkManager rather than legacy network enablement scripts. In this case, install the NetworkManager package. In the non-nm case, also install the network-scripts for Fedora 29 -- this has stopped being installed by default (it's been deprecated since forever). As noted in the docs, this is currently really only relevant on the supported rpm distros which are using the ifcfg-rh NetworkManager plugin to effectively re-use old config files. However, NetworkManager has similar plugins for other platforms, so support can be expanded if changes are proposed. Depends-On: https://review.openstack.org/618964 Change-Id: I4d76e88ce25e5675fd5ef48924acd09915a62a4b
2018-11-20 23:36:12 +00:00
"fedora": {
Fedora 32 support Update for Fedora 32 support. Change-Id: I51c5645856a76e2877c013d72e9849a758ba12ff
2020-06-22 06:35:44 +00:00
"network-scripts": "network-scripts"
simple-init: allow for NetworkManager support This plumbs through an "--use-nm" flag to glean which instructs it to setup interface bringup with NetworkManager rather than legacy network enablement scripts. In this case, install the NetworkManager package. In the non-nm case, also install the network-scripts for Fedora 29 -- this has stopped being installed by default (it's been deprecated since forever). As noted in the docs, this is currently really only relevant on the supported rpm distros which are using the ifcfg-rh NetworkManager plugin to effectively re-use old config files. However, NetworkManager has similar plugins for other platforms, so support can be expanded if changes are proposed. Depends-On: https://review.openstack.org/618964 Change-Id: I4d76e88ce25e5675fd5ef48924acd09915a62a4b
2018-11-20 23:36:12 +00:00
}
},
Install Fedora ifcfg NM compat package Starting with Fedora 36 the NetworkManager package no longer includes ifcfg support by default. You need an additional package "NetworkManager-initscripts-ifcfg-rh" to pull in the compatibility plugin. Glean's support for Fedora relies on this compatibility system so we install this package via the simple-init element package deps. Change-Id: I76ac39b8dedcb1c5bc4595aedc0a732c99c8721e
2022-09-20 15:58:37 +00:00
"release": {
"fedora": {
"36": {
"NetworkManager-initscripts-ifcfg-rh": "NetworkManager-initscripts-ifcfg-rh"
},
"37": {
"NetworkManager-initscripts-ifcfg-rh": "NetworkManager-initscripts-ifcfg-rh"
}
}
},
Add element to process config-drive network info If you don't want cloud-init, you may need to get a few things from config-drive because you may be operating on a cloud with no DHCP. In that case, simply reading some values from config-drive and writing out either DHCP or static network info, in addition to grabbing ssh keys is helpful. Both Infra and bifrost want this for their images. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I2746ed256b9783eab058b803130d3ccac484eaeb
2015-03-23 20:48:51 +00:00
"default": {
Use generic "dhcp-client" name Every platform has a different name for their DHCP client, so use a generic name "dhcp-client" in the package name and let everyone choose their sub-name. This also brings some consistency across simple-init & dhcp-all-interfaces Change-Id: I797aa7aacb13dfb7f35700463dc11d55552eb108
2016-04-01 00:12:29 +00:00
"dhcp-client": "isc-dhcp-client",
simple-init: allow for NetworkManager support This plumbs through an "--use-nm" flag to glean which instructs it to setup interface bringup with NetworkManager rather than legacy network enablement scripts. In this case, install the NetworkManager package. In the non-nm case, also install the network-scripts for Fedora 29 -- this has stopped being installed by default (it's been deprecated since forever). As noted in the docs, this is currently really only relevant on the supported rpm distros which are using the ifcfg-rh NetworkManager plugin to effectively re-use old config files. However, NetworkManager has similar plugins for other platforms, so support can be expanded if changes are proposed. Depends-On: https://review.openstack.org/618964 Change-Id: I4d76e88ce25e5675fd5ef48924acd09915a62a4b
2018-11-20 23:36:12 +00:00
"ifupdown": "",
Install Fedora ifcfg NM compat package Starting with Fedora 36 the NetworkManager package no longer includes ifcfg support by default. You need an additional package "NetworkManager-initscripts-ifcfg-rh" to pull in the compatibility plugin. Glean's support for Fedora relies on this compatibility system so we install this package via the simple-init element package deps. Change-Id: I76ac39b8dedcb1c5bc4595aedc0a732c99c8721e
2022-09-20 15:58:37 +00:00
"network-scripts": "",
"NetworkManager-initscripts-ifcfg-rh": ""
Add element to process config-drive network info If you don't want cloud-init, you may need to get a few things from config-drive because you may be operating on a cloud with no DHCP. In that case, simply reading some values from config-drive and writing out either DHCP or static network info, in addition to grabbing ssh keys is helpful. Both Infra and bifrost want this for their images. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I2746ed256b9783eab058b803130d3ccac484eaeb
2015-03-23 20:48:51 +00:00
}
}
Reference in New Issue Copy Permalink