| 2020-09-17 16:47:17 |
Adrian Vladu |
description |
Because of the commit that introduced platform checks for enabling / using http openstack metadata (https://github.com/canonical/cloud-init/commit/1efa8a0a030794cec68197100f31a856d0d264ab), Linux machines will stop loading http metadata when running on "unsupported" platforms / hypervisors like Hyper-V, XEN, OracleCloud, VMware, OpenTelekomCloud - leading to a whole suite of bug reports and fixes to a non-issue.
Let's try to solve this problem once for all the upcoming platforms / hypervisors by adding a configuration option on the metadata level: platform_check or is_platform_supported (suggestions are welcome for the naming). The value of the config option should be true in order to maintain backwards compatibility.
No one would like to patch well-working OpenStack environments for this kind of issues and it is always easier to control / build the images you use on private OpenStack. |
Because of the commit that introduced platform checks for enabling / using http openstack metadata (https://github.com/canonical/cloud-init/commit/1efa8a0a030794cec68197100f31a856d0d264ab), cloud-init on Linux machines will stop loading http metadata when running on "unsupported" platforms / hypervisors like Hyper-V, XEN, OracleCloud, VMware, OpenTelekomCloud - leading to a whole suite of bug reports and fixes to a non-issue.
Let's try to solve this problem once for all the upcoming platforms / hypervisors by adding a configuration option on the metadata level: perform_platform_check or check_if_platform_is_supported (suggestions are welcome for the naming). The value of the config option should be true in order to maintain backwards compatibility. When set to true, cloud-init will check if the platform is supported.
No one would like to patch well-working OpenStack environments for this kind of issues and it is always easier to control / build the images you use on private OpenStack. |
|
