<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/config, branch crux</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2021-01-29T21:37:03+00:00</updated>
<entry>
<title>T3270: Backported all changes from the equuleus branch</title>
<updated>2021-01-29T21:37:03+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2021-01-29T16:19:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=8129a37a936de781467c4d053f5ad6b1bcf585ba'/>
<id>urn:sha1:8129a37a936de781467c4d053f5ad6b1bcf585ba</id>
<content type='text'>
The behavior of VyOS modules was almost totally changed. Therefore instead of changes, here is a list of what is supported by new versions:

`cc_vyos.py`:

  - extended logging for debugging purposes
  - work with any environment or datasource
  - all available in VyOS SSH keys (ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ssh-ed25519, ecdsa-sha2-nistp521) with options
  - both encrypted and plain-text passwords
  - multiple user accounts
  - the fallback user creating (default "vyos/vyos") in credentials are missed in a Meta-Data
  - interfaces configuration using Network-Config v1 or v2
  - fallback interface config (DHCP on eth0) if Network-config is not available
  - both IPv4 and IPv6 addresses in Network-Config
  - MTU, multiple addresses, DHCP or static addresses, gateway, routes, DNS nameserver, DNS search domain in Network-Config
  - filtration of a hostname value from metadata
  - VyOS-specific options from the OVF template
  - automatically enabling SSH server

`cc_vyos_userdata.py`:

set and delete configuration commands inside the User-Data (#cloud-config). See details: https://github.com/vyos/vyos-cloud-init/commit/1607eec32641ad93ea211e447336b3366c28de06

Configuration template:

  - enabled `write_files` module
  - disabled the `runcmd` module (functionality replaced by `cc_vyos_userdata.py` and `write_files`)
</content>
</entry>
<entry>
<title>Add cloud.cfg file for vyos</title>
<updated>2018-10-21T19:37:52+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2018-10-21T19:37:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=acb53fd6ea1ab907f86c877f509dbfee5d06cce6'/>
<id>urn:sha1:acb53fd6ea1ab907f86c877f509dbfee5d06cce6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ubuntu-advantage: Add new config module to support ubuntu-advantage-tools</title>
<updated>2018-03-23T01:13:06+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-03-23T01:13:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=0d51e912146b3031c458ce415b7d4cd6eb17d06e'/>
<id>urn:sha1:0d51e912146b3031c458ce415b7d4cd6eb17d06e</id>
<content type='text'>
ubuntu-advantage-tools is a package for enabling and disabling extended
support services such as Extended Security Maintenance (ESM), Canonical
Livepatch and FIPS certified PPAs. Simplify Ubuntu Advantage setup on
machines by allowing users to provide a list of ubuntu-advantage commands
in cloud-config.
</content>
</entry>
<entry>
<title>cc_snap: Add new module to install and configure snapd and snap packages.</title>
<updated>2018-03-16T19:43:31+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-03-16T19:43:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=a1f678f8ebc080d4737f32275f42947b84ae025a'/>
<id>urn:sha1:a1f678f8ebc080d4737f32275f42947b84ae025a</id>
<content type='text'>
Support installing and configuring snaps on ubuntu systems. Now,
cloud-config files can provide a list or dictionary of snap:assertions
which will be allow configuration of snapd on a system via 'snap ack'
calls. The snap:commands configuration option supports arbitrary system
commands intended to interact with snappy's cli. This allows users to run
arbitrary snappy commands to create users, download, install and
configure snap packages and snapd.

This branch also deprecates old snappy and snap_config modules leaving
warnings in documentation and runtime for consumers of these modules.
Deprecated snap* modules will be dropped in cloud-init v.18.2 release.
</content>
</entry>
<entry>
<title>Make salt minion module work on FreeBSD.</title>
<updated>2018-03-08T11:13:38+00:00</updated>
<author>
<name>Dominic Schlegel</name>
<email>dominic.schlegel@hostpoint.ch</email>
</author>
<published>2018-03-08T11:13:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=1e2e810f3f7cb6a163a0229ac37037e8c6744d72'/>
<id>urn:sha1:1e2e810f3f7cb6a163a0229ac37037e8c6744d72</id>
<content type='text'>
Previously the module was not working under FreeBSD due to a different
package name and some different paths. The module now has OS specific
default values which can even be customized via corresponding cloud config
variables.

LP: #1721503
</content>
</entry>
<entry>
<title>SUSE: Fix groups used for ownership of cloud-init.log</title>
<updated>2018-02-14T18:52:37+00:00</updated>
<author>
<name>Robert Schweikert</name>
<email>rjschwei@suse.com</email>
</author>
<published>2018-02-13T19:28:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=99171fb7b9bec446e25a338a0d36a820844fbc2d'/>
<id>urn:sha1:99171fb7b9bec446e25a338a0d36a820844fbc2d</id>
<content type='text'>
On SUSE distributions the neither the "adm" nor the "wheel" group are set
up by default causing log file permission change to fail. Set the
user:group to root:root in the cloud-init default config file generated
during install.

boo: 1080595
</content>
</entry>
<entry>
<title>suse: Support addition of zypper repos via cloud-config.</title>
<updated>2017-10-03T13:53:28+00:00</updated>
<author>
<name>Robert Schweikert</name>
<email>rjschwei@suse.com</email>
</author>
<published>2017-09-21T15:58:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=cc1475d07b9d0727012634ee9c7a914d67b051f5'/>
<id>urn:sha1:cc1475d07b9d0727012634ee9c7a914d67b051f5</id>
<content type='text'>
This adds a config module so support for adding zypper repositories
via cloud-config.

LP: #1718675
</content>
</entry>
<entry>
<title>suse: updates to templates to support openSUSE and SLES.</title>
<updated>2017-09-21T18:15:50+00:00</updated>
<author>
<name>Robert Schweikert</name>
<email>rjschwei@suse.com</email>
</author>
<published>2017-09-21T11:38:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=0451a9f60960da56e3af4f97bbcece3d98482f86'/>
<id>urn:sha1:0451a9f60960da56e3af4f97bbcece3d98482f86</id>
<content type='text'>
Things done here:
 - identify 'suse' as a variant in util.system_info and
   also tools/render-cloudcfg.
 - update systemd and cloud.cfg templates for suse specific changes.

LP: #1718640
</content>
</entry>
<entry>
<title>upstart: do not package upstart jobs, drop ubuntu-init-switch module.</title>
<updated>2017-09-01T02:01:57+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-09-01T02:01:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=fa266bf8818a08e37cd32a603d076ba2db300124'/>
<id>urn:sha1:fa266bf8818a08e37cd32a603d076ba2db300124</id>
<content type='text'>
The ubuntu-init-switch module allowed the use to launch an instance that
was booted with upstart and have it switch its init system to systemd and
then reboot itself. It was only useful for the time period when Ubuntu was
transitioning to systemd but only produced images using upstart.

Also, do not run setup with --init-system=upstart. This means that by
default, debian packages built with packages/bddeb will not have upstart
unit files included. No other removal is done here.
</content>
</entry>
<entry>
<title>FreeBSD: Make freebsd a variant, fix unittests and tools/build-on-freebsd.</title>
<updated>2017-06-15T21:10:54+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-06-15T14:03:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=ecb408afa1104fe49ce6eb1dc5708be56abd5cb2'/>
<id>urn:sha1:ecb408afa1104fe49ce6eb1dc5708be56abd5cb2</id>
<content type='text'>
 - Simplify the logic of 'variant' in util.system_info
   much of the data from
   https://github.com/hpcugent/easybuild/wiki/OS_flavor_name_version
 - fix get_resource_disk_on_freebsd when running on a system without
   an Azure resource disk.
 - fix tools/build-on-freebsd to replace oauth with oauthlib and add
   bash which is a dependency for tests.
 - update a fiew places that were checking for freebsd but not using
   the util.is_FreeBSD()
</content>
</entry>
</feed>
