<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/cloud_tests/configs/modules, branch cla</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=cla</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=cla'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2017-10-03T13:01:30+00:00</updated>
<entry>
<title>tests: Combine integration configs and testcases</title>
<updated>2017-10-03T13:01:30+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-10-02T21:32:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=0ee829f91322ae1788ee6fb2a164cf06cdfff7db'/>
<id>urn:sha1:0ee829f91322ae1788ee6fb2a164cf06cdfff7db</id>
<content type='text'>
Combine the configs and testcases directories, so all files are
together in one place. Update the test config location as well.
</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/vyos/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>test: fix incorrect keyid for apt repository.</title>
<updated>2017-07-11T18:08:53+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-07-06T16:35:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=067721672570cc83d54d2c2d5677eeb79bef85e2'/>
<id>urn:sha1:067721672570cc83d54d2c2d5677eeb79bef85e2</id>
<content type='text'>
The test is currently importing the incorrect keyid. It specifies
the curtin developers ppa, rather than the cloud-init ppa. On
Artful this causes failures as a check is made to verify the
correct key is imported for the ppa, whereas on previous releases
only a warning was issued.

Also, change to use a full key fingerprint.

LP: #1702717
</content>
</entry>
<entry>
<title>tests: update ntp tests after sntp added</title>
<updated>2017-06-27T20:25:01+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-06-26T17:16:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f0529559f9688a397f59f041dc6362e91faf96b6'/>
<id>urn:sha1:f0529559f9688a397f59f041dc6362e91faf96b6</id>
<content type='text'>
Recent change to ntp in artful has added the sntp package whenever
ntp is installed. The tests, rather poorly, did a dpkg -l instead
of checking with `which`. This fixes the ntp tests to all use
`which` over expecting a certain number of lines using dpkg and
as a result make the tests OS independent.
</content>
</entry>
<entry>
<title>Integration Testing: tox env, pyxld 2.2.3, and revamp framework</title>
<updated>2017-06-08T22:24:17+00:00</updated>
<author>
<name>Wesley Wiedenmeier</name>
<email>wesley.wiedenmeier@gmail.com</email>
</author>
<published>2017-06-08T22:23:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=76d58265e34851b78e952a7f275340863c90a9f5'/>
<id>urn:sha1:76d58265e34851b78e952a7f275340863c90a9f5</id>
<content type='text'>
Massive update to clean up and greatly enhance the integration testing
framework developed by Wesley Wiedenmeier.

 - Updated tox environment to run integration test 'citest' to utilize
   pylxd 2.2.3
 - Add support for distro feature flags
   - add framework for feature flags to release config with feature groups
     and overrides allowed in any release conf override level
   - add support for feature flags in platform and config handling
   - during collect, skip testcases that require features not supported by
     the image with a warning message
 - Enable additional distros (i.e. centos, debian)
 - Add 'bddeb' command to build a deb from the current working tree
   cleanly in a container, so deps do not have to be installed on host
 - Adds a command line option '--preserve-data' that ensures that
   collected data will be left after tests run. This also allows the
   directory to store collected data in during the run command to be
   specified using '--data-dir'.
 - Updated Read the Docs testing page and doc strings for pep 257
   compliance
</content>
</entry>
<entry>
<title>tests: Apply workaround for snapd bug in test case.</title>
<updated>2017-05-23T19:17:42+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-05-22T19:13:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=06a7f0afc4db3f8ba2a6b3b521274ee45a028ef2'/>
<id>urn:sha1:06a7f0afc4db3f8ba2a6b3b521274ee45a028ef2</id>
<content type='text'>
Snapd does not start on artful or on the versions in proposed. This
changes the behavior of the test to confirm that snapd is installed, not
that it is started, while the snap team fixes the issue (LP: ##1690880).
</content>
</entry>
<entry>
<title>cc_ntp: write template before installing and add service restart</title>
<updated>2017-05-19T20:55:08+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2017-05-19T20:49:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e11d3899d47ec5fcb545e0c7820af9d3995cb574'/>
<id>urn:sha1:e11d3899d47ec5fcb545e0c7820af9d3995cb574</id>
<content type='text'>
On systems which installed ntp and specified servers or pools in the
config ntpd didn't notice the updated configuration file and didn't
use the correct configuration. Resolve this by rendering the template
first which allows the package install to use the existing
configuration. Additionally add a service restart to handle the case
where ntp does not need to be installed but it may not have started.

Add an integration test to confirm that cc_ntp enables ntp to use the
specific servers and pools in the cloud-config.

LP: #1645644
</content>
</entry>
<entry>
<title>Add support for setting hashed passwords</title>
<updated>2017-03-24T20:45:24+00:00</updated>
<author>
<name>Tore S. Lonoy</name>
<email>tore.lonoy@gmail.com</email>
</author>
<published>2016-11-04T10:38:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=21632972df034c200578e1fbc121a07f20bb8774'/>
<id>urn:sha1:21632972df034c200578e1fbc121a07f20bb8774</id>
<content type='text'>
This change will add support for hashed passwords in cc_set_passwords.
It checks if a password is a hash with by checking that it matches
in fairly safe way, and also that the password does not have a ":" in it.

chpasswd needs to know if the password is hashed or not, so two lists
is created so chpasswd is feed with the correct one.

LP: #1570325
</content>
</entry>
<entry>
<title>test: Adding integratiron test for password as list</title>
<updated>2017-03-17T19:47:54+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-03-14T21:28:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=41950e902f5dd6cb3118280d3d27409812702e41'/>
<id>urn:sha1:41950e902f5dd6cb3118280d3d27409812702e41</id>
<content type='text'>
This adds an integration test for setting passwords when given
as a list rather than a string. This also updates the docs and
tests so that Random is now RANDOM as is correct.
</content>
</entry>
<entry>
<title>test: avoid differences in 'date' output due to daylight savings.</title>
<updated>2017-03-13T18:35:29+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-03-13T18:35:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=66dfb0915d4abf3f61948f281c4aff8394494ed3'/>
<id>urn:sha1:66dfb0915d4abf3f61948f281c4aff8394494ed3</id>
<content type='text'>
When testing for timezone we were testing that 'date' output would
contain 'HDT' for the current time.  But after a 'spring forward', the
current time started to have 'HST'.

Instead of asking 'date' for the timezone that applies now, ask it
for a static date.
</content>
</entry>
</feed>
