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

24 lines
440 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": {
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": "dhclient"
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",
Depend on ifupdown in simple-init Newer distros, such as debian jessie and ubuntu xenial, do not provide ifupdown by default, but simple-init depends on it. Add it to the pile. Change-Id: I6f4876863c67c65a82464d4e0593015cdc839c5c
2016-02-18 13:20:48 +00:00
"ifupdown": "ifupdown"
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": {
"dhcp-client": "dhcp-client"
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",
Depend on ifupdown in simple-init Newer distros, such as debian jessie and ubuntu xenial, do not provide ifupdown by default, but simple-init depends on it. Add it to the pile. Change-Id: I6f4876863c67c65a82464d4e0593015cdc839c5c
2016-02-18 13:20:48 +00:00
"ifupdown": ""
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