lp:~chad.smith/livecd-rootfs

Owned by Chad Smith
Get this repository:
git clone https://git.not.enabled/~chad.smith/livecd-rootfs
Only Chad Smith can upload to this repository. If you are Chad Smith please log in for upload directions.

Branches

Name Last Modified Last Commit
cloud-init-network-nm-override 2024-09-20 16:41:57 UTC
fix(functions): cloud-init.service renamed cloud-init-network.service

Author: Chad Smith
Author Date: 2024-09-20 16:37:20 UTC

fix(functions): cloud-init.service renamed cloud-init-network.service

In cloud-init version 24.3, single process mode where a shared python
systemd service cloud-init-main. In that release, cloud-init.service was
renamed cloud-init-network.service to better clarify cloud-init's
systemd unit names relative to the cloud-init boot stages.

This rename only applies to Oracular and newer releases.

See: https://discourse.ubuntu.com/t/announcement-cloud-init-perfomance-optimization-single-process/47505

functions drops in a complete override for cloud-init.service. That
override in /etc/systemd/system needs to be renamed and refreshed to
latest single process configuration.

LP: #2081325

cloud-init-nm-in-override 2024-07-16 16:58:09 UTC
functions: proper cloud-init.service full unit override in etc

Author: Chad Smith
Author Date: 2024-07-16 12:32:34 UTC

functions: proper cloud-init.service full unit override in etc

System override drop-ins cannot redact dependencies (Before or After) and
thus require a full unit override. Avoid writing the unit file delivered
by cloud-init deb package in /lib/systemd/system/cloud-init.service because
it will generate warnings fron debsums -c about modified files.

The correct place to provide a full unit override is in
/etc/systemd/system/cloud-init.service in order to drop
Before=sysinit.target from the packaged cloud-init.service file.

Note vigilance will be needed across cloud-init SRU boundaries to ensure
we sync any cloud-init.service unit changes that are introduced to
stable releases because livecd-rootfs is overriding the whole file.

LP: #2069391

functions-clean-script-declare-interpreter 2024-03-01 21:00:57 UTC
functions: cloud-init clean script needs to declar interpreter

Author: Chad Smith
Author Date: 2024-03-01 21:00:57 UTC

functions: cloud-init clean script needs to declar interpreter

LP: #2055729

functions-clean-script-declar-interpreter 2024-03-01 21:00:57 UTC
functions: cloud-init clean script needs to declar interpreter

Author: Chad Smith
Author Date: 2024-03-01 21:00:57 UTC

functions: cloud-init clean script needs to declar interpreter

LP: #2055729

cloud-init-desktop-use-netplan 2023-04-07 23:11:48 UTC
releasing package livecd-rootfs version 2.821

Author: Chad Smith
Author Date: 2023-04-07 22:56:38 UTC

releasing package livecd-rootfs version 2.821

desktop-cloud-init-after-network-manager-ordering 2023-03-23 23:05:30 UTC
cloud-init.service: systemd ordering after after NetworkManager

Author: Chad Smith
Author Date: 2023-03-23 23:05:30 UTC

cloud-init.service: systemd ordering after after NetworkManager

Autoinstall directives can be provided on the grub cmdline to
cloud-init via kernel parameters like the following:
 autoinstall 'ds=nocloud-net;s=http://somedomain/'

In order to support DNS resolution for NoCloud datasource at
datasource discovery time, cloud-init.service needs to be
orderered after NetworkManager.service and
NetworkManager-wait-online.service
which will have brought up applicable NICs.

Since NetworkManager is After=dbus.service, the cloud-init.service
avoids systemd ordering cycles by also dropping
Before=sysinit.target when it adds, After=NetworkManager.service and
After=NetworkManager-wait-online.service

Add this file overlay for /lib/systemd/system/cloud-init.service
because systemd drop-in files can only add constraints and not
drop prexisting service constraints.

Also add an AUTOMATION_HEADER comment to any generated files to
add discoverability in the event of future bugs/concerns.

LP: #2008952

use-cloud-cfg-d-parts 2023-03-23 21:54:37 UTC
cloud.cfg: migrate remaining cloud cfg modules to cloud.cfg.d/ parts

Author: Chad Smith
Author Date: 2023-03-23 21:54:37 UTC

cloud.cfg: migrate remaining cloud cfg modules to cloud.cfg.d/ parts

Preserve this list of config modules allowed to run in ephmeral
installer stage.

Is there a reason some modules are redacted?

  It's likely some of this (certainly the final modules) were cut to
  save time intentionally in ephemeral boot.

  - Note that cloud-init now performs schema validation to avoid
    running inapplicable modules avoiding sunk cost into loading 50+
    config modules that NOOP.

  Another reason these modules were trimmed was probably to filter
  unwanted behavior from ephemeral boot stage.

It's likely a mix of many reasons but we should review this list
again to see if we still want to retain the subset of modules and
if we should include more. One element take into account is if we
want to support modification of ephemeral install stage with
cloud-config user-data, we need to think about whether we want
derivative installers to leverage standard #cloud-config options.

The missing modules unrepresented from upstream:
  cloud_init_modules:
    - migrator
    - seed_random
    - growpart
    - resizefs
    - disk_setup
    - mounts
    - set_hostname
    - update_hostname
    - update_etc_hosts

  cloud_config_modules:
    - wireguard
    - snap
    - ubuntu_autoinstall
    - keyboard
    - locale
    - grub-dpkg
    - apt-pipelining
    - apt-configure
    - ubuntu-advantage
    - ntp
    - byobu

   cloud_final_modules:
   - package-update-upgrade-install
   - fan
   - landscape
   - lxd
   - ubuntu-drivers
   - write-files-deferred
   - puppet
   - chef
   - ansible
   - mcollective
   - salt-minion
   - reset_rmc
   - refresh_rmc_and_interface
   - rightscale_userdata
   - scripts-vendor
   - scripts-per-boot
   - scripts-per-instance
   - install-hotplug
   - power-state-change

17 of 7 results
This repository contains Public information 
Everyone can see this information.

Subscribers