<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tools, 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>2019-01-23T12:23:09+00:00</updated>
<entry>
<title>ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo.</title>
<updated>2019-01-23T12:23:09+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-12-20T23:51:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ee6bb34376e1814a91fc513a811b059b04260d4c'/>
<id>urn:sha1:ee6bb34376e1814a91fc513a811b059b04260d4c</id>
<content type='text'>
ovf_vmware_transport_guestinfo is not currently tested.
It used '$1' instead of '$out' when checking for xml content in
the output of vmware-rpctool.
</content>
</entry>
<entry>
<title>Vmware: Add support for the com.vmware.guestInfo OVF transport.</title>
<updated>2019-01-23T12:22:33+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-12-20T17:22:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=d7952d075666122f480f0a5820ac01dfbaa7da1a'/>
<id>urn:sha1:d7952d075666122f480f0a5820ac01dfbaa7da1a</id>
<content type='text'>
This adds support for reading OVF information over the
'com.vmware.guestInfo' tranport.  The current implementation requires
vmware-rpctool be installed in the system.

LP: #1807466
</content>
</entry>
<entry>
<title>Merge tag '18.5' into current</title>
<updated>2019-01-23T12:20:25+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2019-01-23T12:20:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c4da1a5cddacaa7c2a15df9170f21c3fce78fb15'/>
<id>urn:sha1:c4da1a5cddacaa7c2a15df9170f21c3fce78fb15</id>
<content type='text'>
release 18.5

Bump the version on cloudinit/version.py to be 18.5 and update ChangeLog

LP: #1808380

Conflicts:
	config/cloud.cfg.tmpl
</content>
</entry>
<entry>
<title>OVF: identify label iso9660 filesystems with label 'OVF ENV'.</title>
<updated>2018-11-27T21:39:42+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-11-27T21:39:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=530850f971e36f4b0ef216cec9d889a99474ca0e'/>
<id>urn:sha1:530850f971e36f4b0ef216cec9d889a99474ca0e</id>
<content type='text'>
When deploying an OVA, at least some versions of vmware
attach a cdrom with an ISO9660 filesystem label of 'OVF ENV'.
This was seen on Vmware vCenter Server, 6.0.0, 2776510.

In order to accomplish this we had to change the content of
the DI_ISO9660_DEVS variable to be comma delimited rather
than space delimited.
</content>
</entry>
<entry>
<title>Merge tag 'ubuntu/18.4-0ubuntu1_16.04.2' into current</title>
<updated>2018-10-25T20:26:25+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2018-10-25T20:26:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b120f4f7a670674779a93f8c882c81f44a993888'/>
<id>urn:sha1:b120f4f7a670674779a93f8c882c81f44a993888</id>
<content type='text'>
Conflicts:
	cloudinit/sources/DataSourceAzure.py
	config/cloud.cfg.tmpl
	integration-requirements.txt
	tools/read-version
</content>
</entry>
<entry>
<title>do not check git</title>
<updated>2018-10-21T20:50:43+00:00</updated>
<author>
<name>Kim Hagen</name>
<email>kim.sidney@gmail.com</email>
</author>
<published>2018-10-21T20:50:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c6596d86435fdb1933a7755de110e8f6e8de6aaf'/>
<id>urn:sha1:c6596d86435fdb1933a7755de110e8f6e8de6aaf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tools/tox-venv: update for new features.</title>
<updated>2018-09-25T18:03:35+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-25T18:03:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=0b0378dd07f16d45c16e5750b6815b22a771860d'/>
<id>urn:sha1:0b0378dd07f16d45c16e5750b6815b22a771860d</id>
<content type='text'>
This update to tox-venv allows you to do:
 ./tools/tox-venv py3 - tests/unittests/test_util.py
</content>
</entry>
<entry>
<title>ds-identify: doc string cleanup.</title>
<updated>2018-09-14T21:12:17+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-14T21:12:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bb60f61bfcd92465f4076e8d8abbb486cf6bbcf1'/>
<id>urn:sha1:bb60f61bfcd92465f4076e8d8abbb486cf6bbcf1</id>
<content type='text'>
There was a typo in the doc string at the top of ds-identify
(disable -&gt; disabled).  That is fixed here as well as adding some
better examples on content in /etc/cloud/ds-identify.cfg.
</content>
</entry>
<entry>
<title>read-version: enhance error message</title>
<updated>2018-08-31T22:11:49+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2018-08-31T22:11:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=8d9d4c8477732c5cc559eb10ddacef4598f93591'/>
<id>urn:sha1:8d9d4c8477732c5cc559eb10ddacef4598f93591</id>
<content type='text'>
The error message when read-vesion is not very useful and does not help
the end-user know how to overcome the issue. This adds a short message
explaining that the user does not have the latest upstream tags and how
to get those tags.
</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>
</feed>
