lp:~vkuznets/cloud-init

Owned by Vitaly Kuznetsov
Get this repository:
git clone https://git.launchpad.net/~vkuznets/cloud-init
Only Vitaly Kuznetsov can upload to this repository. If you are Vitaly Kuznetsov please log in for upload directions.

Branches

Name Last Modified Last Commit
cloud-init-per-dashes 2019-01-29 17:35:47 UTC 2019-01-29
cloud-init-per: don't use dashes in sem names

Author: Vitaly Kuznetsov
Author Date: 2019-01-21 14:03:18 UTC

cloud-init-per: don't use dashes in sem names

It was found that when there is a dash in cloud-init-per command
name and cloud-init-per is executed through cloud-init's bootcmd, e.g:

bootcmd:
 - cloud-init-per instance mycmd-bootcmd /usr/bin/mycmd

the command is executed on each boot. However, running the same
cloud-init-per command manually after boot doesn't reveal the issue. Turns
out the issue comes from 'migrator' cloud-init module which renames all
files in /var/lib/cloud/instance/sem/ replacing dashes with underscores. As
migrator runs before bootcmd it renames

/var/lib/cloud/instance/sem/bootper.mycmd-bootcmd.instance
to
/var/lib/cloud/instance/sem/bootper.mycmd_bootcmd.instance

so cloud-init-per doesn't see it and thinks that the comment was never ran
before. On next boot the sequence repeats.

There are multiple ways to resolve the issue. This patch takes the
following approach: 'canonicalize' sem names by replacing dashes with
underscores (this is consistent with post-'migrator' contents of
/var/lib/cloud/instance/sem/). We, however, need to be careful: in case
someone had a command with dashes before and he had migrator module enables
we need to see the old sem file (or the command will run again and this can
be as bad as formatting a partition!) so we add a small 'migrator' part to
cloud-init-per script itself checking for legacy sem names.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>

master 2019-01-08 18:46:44 UTC 2019-01-08
Add documentation on adding a datasource.

Author: Scott Moser
Author Date: 2019-01-08 18:46:44 UTC

Add documentation on adding a datasource.

This adds documentation intended for a developer on how to add
a new datasource to cloud-init.

dhcp6_only 2018-04-19 14:19:52 UTC 2018-04-19
sysconfig: dhcp6 subnet type should not imply dhcpv4

Author: Vitaly Kuznetsov
Author Date: 2018-04-19 11:45:45 UTC

sysconfig: dhcp6 subnet type should not imply dhcpv4

BOOTPROTO=dhcp in sysconfig enables DHCPv4 and we should not do this
implicitly when 'dhcp6' subnet is specified. In case both dhcpv4 and
dhcpv6 are needed users should specify both:
    subnets:
      - type: dhcp6
      - type: dhcp

Fix the current code and add a dhcpv6 only test.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>

hostnamectl_hack 2018-04-09 09:26:58 UTC 2018-04-09
sources/DataSourceAzure.py: use hostnamectl

Author: Vitaly Kuznetsov
Author Date: 2018-04-09 09:26:58 UTC

sources/DataSourceAzure.py: use hostnamectl

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>

14 of 4 results
This repository contains Public information 
Everyone can see this information.

Subscribers