<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware/imc/config_nic.py, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2022-02-08T14:49:00+00:00</updated>
<entry>
<title>Fix IPv6 netmask format for sysconfig (#1215)</title>
<updated>2022-02-08T14:49:00+00:00</updated>
<author>
<name>Harald</name>
<email>hjensas@redhat.com</email>
</author>
<published>2022-02-08T14:49:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b97a30f0a05c1dea918c46ca9c05c869d15fe2d5'/>
<id>urn:sha1:b97a30f0a05c1dea918c46ca9c05c869d15fe2d5</id>
<content type='text'>
This change converts the IPv6 netmask from the network_data.json[1]
format to the CIDR style, &lt;IPv6_addr&gt;/&lt;prefix&gt;.

Using an IPv6 address like ffff:ffff:ffff:ffff:: does not work with
NetworkManager, nor networkscripts.

NetworkManager will ignore the route, logging:
  ifcfg-rh: ignoring invalid route at \
    "::/:: via fd00:fd00:fd00:2::fffe dev $DEV" \
    (/etc/sysconfig/network-scripts/route6-$DEV:3): \
    Argument for "::/::" is not ADDR/PREFIX format

Similarly if using networkscripts, ip route fail with error:
  Error: inet6 prefix is expected rather than \
    "fd00:fd00:fd00::/ffff:ffff:ffff:ffff::".

Also a bit of refactoring ...

cloudinit.net.sysconfig.Route.to_string:
* Move a couple of lines around to reduce repeated code.
* if "ADDRESS" not in key -&gt; continute, so that the
  code block following it can be de-indented.
cloudinit.net.network_state:
* Refactors the ipv4_mask_to_net_prefix, ipv6_mask_to_net_prefix
  removes mask_to_net_prefix methods. Utilize ipaddress library to
  do some of the heavy lifting.

LP: #1959148</content>
</entry>
<entry>
<title>Adopt Black and isort (SC-700) (#1157)</title>
<updated>2021-12-16T02:16:38+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-12-16T02:16:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf'/>
<id>urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf</id>
<content type='text'>
Applied Black and isort, fixed any linting issues, updated tox.ini
and CI.
</content>
</entry>
<entry>
<title>VMware: source /etc/network/interfaces.d/* on Debian</title>
<updated>2021-11-18T21:58:06+00:00</updated>
<author>
<name>chengcheng-chcheng</name>
<email>63850735+chengcheng-chcheng@users.noreply.github.com</email>
</author>
<published>2021-11-18T21:58:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3c6b594b90b0647f398f41962def45fd0953ce5b'/>
<id>urn:sha1:3c6b594b90b0647f398f41962def45fd0953ce5b</id>
<content type='text'>
For Debian, the network configure file was named
/etc/network/interfaces.d/50-cloud-init, not the 50-cloud-init.cfg,
related to
https://github.com/canonical/cloud-init/blob/62721ae71057530e41779ff02ce578b7b802a60f/cloudinit/distros/debian.py#L56
the static IP customization on Debian will fail owing to
"source /etc/network/interfaces.d/*.cfg".
This change will fix this issue.

LP: #1950136</content>
</entry>
<entry>
<title>Fix not sourcing default 50-cloud-init ENI file on Debian (#598)</title>
<updated>2020-11-03T14:47:03+00:00</updated>
<author>
<name>WebSpider</name>
<email>WebSpider@users.noreply.github.com</email>
</author>
<published>2020-11-03T14:47:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=7978feb3af5846a1a2ac489cde83febe975b046d'/>
<id>urn:sha1:7978feb3af5846a1a2ac489cde83febe975b046d</id>
<content type='text'>
* Include both Ubuntu-style cfg file, and Debian-style directory in ENI
* Add WebSpider as contributor</content>
</entry>
<entry>
<title>Move subp into its own module. (#416)</title>
<updated>2020-06-08T16:49:12+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2020-06-08T16:49:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3c551f6ebc12f7729a2755c89b19b9000e27cc88'/>
<id>urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88</id>
<content type='text'>
This was painful, but it finishes a TODO from cloudinit/subp.py.

It moves the following from util to subp:
  ProcessExecutionError
  subp
  which
  target_path

I moved subp_blob_in_tempfile into cc_chef, which is its only caller.
That saved us from having to deal with it using write_file
and temp_utils from subp (which does not import any cloudinit things now).

It is arguable that 'target_path' could be moved to a 'path_utils' or
something, but in order to use it from subp and also from utils,
we had to get it out of utils.</content>
</entry>
<entry>
<title>ovf: Fix ovf network config generation gateway/routes</title>
<updated>2018-12-03T18:43:21+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2018-12-03T18:43:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6'/>
<id>urn:sha1:cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6</id>
<content type='text'>
Move routes under the nic's subnet rather than use top-level
("global") route config ensuring all net renderers will provide the
configured route.

Also updated cloudinit/cmd/devel/net_convert.py:
 - Add input type 'vmware-imc' for OVF customization config files
 - Fix bug when output-type was netplan which invoked netplan
   generate/apply and attempted to write to
   /etc/netplan/50-cloud-init.yaml instead of joining with the
   output directory.

LP: #1806103
</content>
</entry>
<entry>
<title>VMWare: Fix a network config bug in vm with static IPv4 and no gateway.</title>
<updated>2018-08-28T22:52:28+00:00</updated>
<author>
<name>Pengpeng Sun</name>
<email>pengpengs@vmware.com</email>
</author>
<published>2018-08-28T22:52:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=9c35f9762028b8bf15cdcd6b42c0fafc233ddda3'/>
<id>urn:sha1:9c35f9762028b8bf15cdcd6b42c0fafc233ddda3</id>
<content type='text'>
The issue is when customize a VM with static IPv4 and without gateway, it
will still extend route list and will loop a gateways list which is None.
This fix is to make sure when no gateway is here, it will not extend route
list.

LP: #1766538
</content>
</entry>
<entry>
<title>pylint: pay attention to unused variable warnings.</title>
<updated>2018-04-20T03:30:08+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-04-20T03:30:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1081962eacf2814fea6f4fa3255c530de14e4a24'/>
<id>urn:sha1:1081962eacf2814fea6f4fa3255c530de14e4a24</id>
<content type='text'>
This enables warnings produced by pylint for unused variables (W0612),
and fixes the existing errors.
</content>
</entry>
<entry>
<title>VMware: Support for user provided pre and post-customization scripts</title>
<updated>2017-12-08T17:15:00+00:00</updated>
<author>
<name>Maitreyee Saikia</name>
<email>msaikia@vmware.com</email>
</author>
<published>2017-12-08T17:10:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ce33e423cde806a0590fec635778d62836e1bd37'/>
<id>urn:sha1:ce33e423cde806a0590fec635778d62836e1bd37</id>
<content type='text'>
In the VMware customization workflow, we have some options for the user
to upload scripts for additional customization. Based on user request,
those custom scripts can be either run before regular customization or
after. For post customization scripts, we decide whether to run the scripts
just after customization or post system reboot.
</content>
</entry>
<entry>
<title>vmware customization: return network config format</title>
<updated>2017-09-08T04:21:30+00:00</updated>
<author>
<name>Sankar Tanguturi</name>
<email>stanguturi@vmware.com</email>
</author>
<published>2017-09-08T04:16:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a1dfdda2a2ae20fe026881980ddf7d16110f06e2'/>
<id>urn:sha1:a1dfdda2a2ae20fe026881980ddf7d16110f06e2</id>
<content type='text'>
For customizing the machines hosted on 'VMWare' hypervisor, the datasource
should return the 'network config' data in 'curtin' format.

This branch also fixes /etc/network/interfaces replacing the line
"source /etc/network/interfaces.d/*.cfg" which is incorrectly removed
when VMWare's Perl Customization Engine writes /etc/network/interfaces.

Modify the code to read the customization configuration and return the
converted data.

Added few tests.

LP: #1675063
</content>
</entry>
</feed>
