<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers, branch crux</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=crux</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2018-12-03T18:43:21+00:00</updated>
<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>azure: detect vnet migration via netlink media change event</title>
<updated>2018-11-29T21:53:18+00:00</updated>
<author>
<name>Tamilmani Manoharan</name>
<email>tamanoha@microsoft.com</email>
</author>
<published>2018-11-29T21:53:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bf7917159dbb292c9fcdef82b004e0f5ecb32c16'/>
<id>urn:sha1:bf7917159dbb292c9fcdef82b004e0f5ecb32c16</id>
<content type='text'>
Replace Azure pre-provision polling on IMDS with a blocking call
which watches for netlink link state change messages.  The media
change event happens when a pre-provisioned VM has been activated
and is connected to the users virtual network and cloud-init can
then resume operation to complete image instantiation.
</content>
</entry>
<entry>
<title>Add support for Infiniband network interfaces (IPoIB).</title>
<updated>2018-09-26T17:59:07+00:00</updated>
<author>
<name>Mark Goddard</name>
<email>mark@stackhpc.com</email>
</author>
<published>2018-09-26T17:59:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e7b0e5f72e134779cfe22cd07b09a42c22d2bfe1'/>
<id>urn:sha1:e7b0e5f72e134779cfe22cd07b09a42c22d2bfe1</id>
<content type='text'>
OpenStack ironic references Infiniband interfaces via a 6 byte 'MAC
address' formed from bytes 13-15 and 18-20 of interface's hardware
address. This address is used as the ethernet_mac_address of Infiniband
links in network_data.json in configdrives generated by OpenStack nova.
We can use this address to map links in network_data.json to their
corresponding interface names.

When generating interface configuration files, we need to use the
interface's full hardware address as the HWADDR, rather than the 6 byte
MAC address provided by network_data.json.

This change allows IB interfaces to be referenced in this dual mode - by
MAC address and hardware address, depending on the context.

Support TYPE=InfiniBand for sysconfig configuration of IB interfaces.
</content>
</entry>
<entry>
<title>OpenStack: Support setting mac address on bond.</title>
<updated>2018-09-14T19:33:01+00:00</updated>
<author>
<name>Fabian Wiesel</name>
<email>fabian.wiesel@sap.com</email>
</author>
<published>2018-09-14T19:33:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c6cfed7fb58be76a3f95963a5de469aa03542cd3'/>
<id>urn:sha1:c6cfed7fb58be76a3f95963a5de469aa03542cd3</id>
<content type='text'>
Fix a bug where setting of mac address on a bond device was
ignored when provided in OpenStack network_config.json.

LP: #1682064
</content>
</entry>
<entry>
<title>EphemeralIPv4Network: Be more explicit when adding default route.</title>
<updated>2018-09-13T22:15:39+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-13T22:15:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=12066fc8f6518d294501aa126b5332ea90c4896c'/>
<id>urn:sha1:12066fc8f6518d294501aa126b5332ea90c4896c</id>
<content type='text'>
On OpenStack based OVH public cloud, we got DHCP response with
  fixed-address 54.36.113.86;
  option subnet-mask 255.255.255.255;
  option routers 54.36.112.1;

The router clearly is not on the subnet.  So 'ip' would fail when
we tried to add the default route.
The solution here is to add an explicit route on that interface
to the router and then add the default route.

Also add 'bgpovs' to the list of 'physical' types for OpenStack
network configuration.  That type is used on OVH public cloud.

LP: #1792415
</content>
</entry>
<entry>
<title>OpenStack: support reading of newer versions of metdata.</title>
<updated>2018-09-13T18:44:20+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-13T18:44:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4361e0e42a34ebf9f49dde2356b7261715cf0cd5'/>
<id>urn:sha1:4361e0e42a34ebf9f49dde2356b7261715cf0cd5</id>
<content type='text'>
Mark as supported for reading some newer versions of openstack metadata:
 2016-06-30 : Newton one
 2016-10-06 : Newton two
 2017-02-22 : Ocata
 2018-08-27 : Rocky
</content>
</entry>
<entry>
<title>OpenStack: fix bug causing 'latest' version to be used from network.</title>
<updated>2018-09-12T18:44:19+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-12T18:44:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c75c582ed1824dc3ff39cefdbddccfc2924b868c'/>
<id>urn:sha1:c75c582ed1824dc3ff39cefdbddccfc2924b868c</id>
<content type='text'>
Cloud-init was reading a list of versions from the OpenStack metadata
service (http://169.254.169.254/openstack/) and attempt to select the
newest known supported version.  The problem was that the list
of versions was not being decoded, so we were comparing a list of
bytes (found versions) to a list of strings (known versions).

LP: #1792157
</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>Add datasource Oracle Compute Infrastructure (OCI).</title>
<updated>2018-08-17T20:25:31+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-08-17T20:25:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=aaffd59431fe05932a66016db941fe197c4e7620'/>
<id>urn:sha1:aaffd59431fe05932a66016db941fe197c4e7620</id>
<content type='text'>
This adds a Oracle specific datasource that functions with OCI.
It is a simplified version of the OpenStack metadata server
with support for vendor-data.

It does not support the OCI-C (classic) platform.

Also here is a move of BrokenMetadata to common 'sources'
as this was the third occurrence of that class.
</content>
</entry>
<entry>
<title>read_file_or_url: move to url_helper, fix bug in its FileResponse.</title>
<updated>2018-05-17T20:59:54+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-05-17T20:59:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=30e730f7ca111487d243ba9f40c66df6d7a49953'/>
<id>urn:sha1:30e730f7ca111487d243ba9f40c66df6d7a49953</id>
<content type='text'>
The result of a read_file_or_url on a file and on a url would differ
in behavior.
  str(UrlResponse) would return UrlResponse.contents.decode('utf-8')
while
  str(FileResponse) would return str(FileResponse.contents)

The difference being "b'foo'" versus "foo".

As part of the general goal of cleaning util, move read_file_or_url
into url_helper.
</content>
</entry>
</feed>
