... because the latest lint no longer allows usage of legacy facts and
top scope fact.
This also disables puppet 5 unit test job because the job is broken
with structured facts.
Change-Id: Id11ccaf89a44d093de29ba3c15165153eea4be56
This change removes the Puppetfile from puppet-ceph as the dependencies
are tracked in the metadata.json file.
Change-Id: Iab231840647e9bc8c6ed26cbaea8302f3b28b110
Previously facter parameters ipaddress_eth0 and ipaddress_eth1 were
hardcoded at various places in the tests. RHEL 7, CentOS 7, Fedora 21
and similar are using systemd's predictable naming instead which in
vagrant/virtualbox leads to things like ipaddress_enp0s3 or
ipaddress_enp0s8 instead and consequently breaks testing on those
systems.
Change-Id: I0a045c673e218d6a611dc9f4e2f187b7e33eb143
during the refactoring where the inheritance was removed from the
usecases the client code was missed and ended up referencing a parent
config which is no longer available.
Change-Id: I95c170e2a6873a73229e4440b280f0dec702c1a4
The CI VMs have only 10G of disk space on the root disk available.
When creating an OSD backed by a folder on the root file system this
leads to out of space errors during the test runs.
Change-Id: I0637781b362fbfcca0180fb7506acf7059a75f79
Only one of the usecases was clearly marked as not working in this form,
while in reality all but the first do not work.
This could have led to confusion for prospective users of the module or
worse turn them away from using the module.
As the current puppet recipes are proven via CI to actually support these
usecases on Ubuntu Precise and RedHat 6.4 family, instead of adding a
header about them not being expected to work, they were instead adapted
to working examples (with minor adaptions to user specific setups as a
caveat).
Change-Id: Id30d339ef1295bb50dcf017eefc996edfc8dbe60
Closes-Bug: #1327785
The first use case works with the current implementation. It is updated
to remove the warning and the syntax is adapted to match the
reality. Instead of a laptop, it is suggested that the test is done on a
virtual machine because it is much more likely.
Change-Id: I7fafb2a6d06eb146b6a2407fb20fdfc4846889f9
Signed-off-by: Loic Dachary <loic@dachary.org>
It is a use case listed in https://wiki.openstack.org/
wiki/Puppet-openstack/ceph-blueprint
Adding the ceph blueprint in USECASES.md
Adding a link in the README.md
Closes-Bug: #1243333
Change-Id: Iff1415cace170676c9ff8ec57d05d9bd6bf8ccdf
Blueprint: Add the "I want to spawn a cluster configured with continuous integration" use case to USECASES.md
Signed-off-by: Romain Salot <romain.salot@gmail.com>
It is a use case listed in https://wiki.openstack.org/wiki/Puppet-
openstack/ceph-blueprint and it would be a useful example when
considering what the puppet-ceph module can do. It must be linked
from the README.md
Closes-Bug: #1243331
Change-Id: I6d477353a0e1bc00eef77e96099e92845f47f21f
Takashi Kajinami