Cloud-init network templates

lzap · June 4, 2020, 9:38am

Hello,

does anybody have cloud-init snippets/templates which configure network interfaces defined in Foreman, including ethernet, bond, bridge or vlan devices? Preferred is the native format (https://cloudinit.readthedocs.io/en/latest/topics/network-config.html) but I’d be happy for anything related.

Foreman currently ships with cloud-init that completely ignores network configuration for some reason. I now that on most clouds networking is usually DHCP and that’s the default, but it matters in virtualized environments.

I haven’t tried this myself, it looks like networking info should be passed as a separate field into oVirt for some reason, in cloud-init docs the networking data is often passed in a separate file: http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/initialization

If we add this into Foreman templates, I’d like to write some tests validating syntax around it via cloud-init devel schema command.

github.com

theforeman/community-templates/blob/develop/provisioning_templates/user_data/userdata_default.erb

<%#
kind: user_data
name: UserData default
model: ProvisioningTemplate
oses:
- CentOS
- Fedora
- Debian
- Ubuntu
-%>
<%#
This template accepts the following parameters:
- ssh_pwauth: boolean (default=true unless ssh_authorized_keys)
- ssh_authorized_keys: string w newline seperated keys (default="")
- package_upgrade: boolean (default=false)
- reboot: boolean (default=false)
-%>
<%
  ssh_pwauth = host_param('ssh_pwauth') ? host_param_true?('ssh_pwauth') : !host_param('ssh_authorized_keys')
  rhel_compatible = @host.operatingsystem.family == 'Redhat' && @host.operatingsystem.name != 'Fedora'

This file has been truncated. show original

Also I have noticed we carry few user data templates which are actually shell scripts. Does anyone use that? What’s the use case?

github.com

theforeman/community-templates/blob/develop/provisioning_templates/user_data/kickstart_default_user_data.erb

<%#
kind: user_data
name: Kickstart default user data
model: ProvisioningTemplate
oses:
- CentOS
- Fedora
-%>
<%
  rhel_compatible = @host.operatingsystem.family == 'Redhat' && @host.operatingsystem.name != 'Fedora'
  # safemode renderer does not support unary negation
  pm_set = @host.puppetmaster.empty? ? false : true
  puppet_enabled = pm_set || host_param_true?('force-puppet')
  salt_enabled = host_param('salt_master') ? true : false
  chef_enabled = @host.respond_to?(:chef_proxy) && @host.chef_proxy
-%>
#!/bin/bash

<%# Cloud instances frequently have incorrect hosts data %>
<%= snippet 'fix_hosts' %>

This file has been truncated. show original

Thanks

TimoGoebel · June 4, 2020, 10:02am

One small remark/hint/comment: If I remember correctly there was an issue with the cloud-init network config combined with the NoCloud datasource we use for the vmware workflow. I don’t remember the exact details, though.

lzap · June 5, 2020, 5:54am

Yeah, when I was reading cloud-init docs it was a mess. Multiple syntax formats, different “implementations”. I wonder why this is so complex, isn’t this just dropping a configuration file somewhere and restarting network?

I wonder if we could at least implement a temporary solution - including kickstart_networking_setup snippet from cloud-init for debian and redhat systems. That could be a good starting point.