cloud-init
cloud-init copied to clipboard
canonical
Official upstream for the cloud-init: cloud instance initialization
# Enhancement Please consider adding a logrotate config file to your cloud-init source repository. Looking at bigger files in /var/log/, cloud-init grows quite big logging files. Please also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926424...
## Improve cloud detection failure semantics A fallback datasource may be catastrophic, since if the configured & detected data source is unavailable, cloud-init may still go ahead with ssh key...
# Bug report The configuration of non-Fully Qualified Domain Name (FQDN) hostnames seems to be encountering issues on AlmaLinux and other distributions based on RHEL8, such as Rocky Linux and...
## Steps to reproduce the problem PR #4190 introduced udhcpc client support. As it is, udhcpc may work on some platforms, but is missing support for unknown dhcp options. This...
### How the network is configured today In many cases, manually configuring an instance's network configuration on boot is unnecessary. This is handled automatically by cloud-init in the following way:...
# Documentation request Cloud-init provides code for drop-in 3rd party modules. These can be [custom mergers](https://cloudinit.readthedocs.io/en/latest/reference/merging.html#customisation), [custom handlers](https://cloudinit.readthedocs.io/en/latest/explanation/format.html#part-handler), custom datasources, custom configuration modules, or [custom cleaners](https://github.com/canonical/cloud-init/pull/4761/files). These are categorically different...
# Enhancement Please see the discussion in https://github.com/canonical/cloud-init/pull/4474 . Currently network renderers use various default settings for ip configurations. For example, settings for `IPV4_FAILURE_FATAL` and `IPV6_FAILURE_FATAL` in ifcfg files and...
# ~Documentation~ Explanation request The current colours are blinding and difficult to read:  Reader-mode helps:  But navigation is lost. Dark mode has...
# Bug report Multi-NIC VMs, using GCE metadata flavor, but not running on the Google platform, get stuck in a loop trying to set up DHCP on invalid NICs. #4163...
This bug was originally filed in Launchpad as [LP: #1771583](https://bugs.launchpad.net/cloud-init/+bug/1771583) Launchpad details affected_projects = [] assignee = None assignee_name = None date_closed = None date_created = 2018-05-16T14:01:29.123177+00:00 date_fix_committed = None...
