Developers run all sorts of different tools within Git repositories,
any of which can leave their own special trashfiles all over the
place. We can't every hope to catalog them all, so better to
recommend developers simply configure a global core.excludesfile to
filter the irrelevant files which tend to get created by their
personal choice of tools. Add a comment block explaining this, for
clarity, and remove the one current editor-specific entry present.
We can, and should of course, continue to list files created by the
tools recommended by our workflow (test frameworks, documentation
and packaging builds, et cetera).
This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7
from the openstack-dev/cookiecutter repository.
Change-Id: I818e0bdeb949c6e0adf062951c0716635fecf555
Current puppet-ceph CI is broken for all functional jobs.
I would like to restart from scratch the way we test the module.
1) centos7: deploy Jewel using buildlogs.centos.org repo
CentOS SIG does not provide packaging to deploy the Jewel repository,
let's install it by hand.
2) Remove RGW tests for now. We'll re-add them later, in a
puppet-openstack-integration scenario.
3) Reset spec files to match with other Puppet OpenStack modules.
4) On CentOS, use systemd resource and not sysvinit.
5) Fix keyring idempotency with SElinux.
Change-Id: Ie9ba521cdb4ac6823746d37bb5d1697e274e4119
From http://ceph.com/packages/ceph-extras/debian/
"The requested resource /packages/ceph-extras/debian/
is no longer available on this server and there is no forwarding
address. Please remove all references to this resource."
Change-Id: Ic37b3b047568418d70a49a72f5b77b5c42a330e7
Since puppet 3.x, Puppet Labs Forge accept only the metadata.json file
for module description (Modulefile is now deprecated).
This patch :
- convert the Modulefile to metadata.json.
- switch to stackforge namespace.
- relax pe version_requirement to 3.x.
- switch to SPDX license name.
- fix open ended module dependency versions.
Change-Id: I7a91a6d6627d71f589f1393b0c2cd6e4e38ad0a6
Use https://github.com/puppetlabs/rspec-system-puppet to implement
vagrant based integration tests. The README.md is updated with
instructions to run the integration tests locally. These tests could be
run by a deamon listening to the gerrit stream, when a changeset is
submitted for review, to prove that they do not introduce a regression.
The dependencies from .fixtures.yml have been manually replicated to
spec/spec_helper_system.rb . rspec system puppet is still young and
people do this. It will be a burden only for long term maintenance. And
when it does, in a few months from now, it is safe to assume that rspec
system puppet will have support for reading from an existing file. The
alternative is that rspec system puppet is obsoleted / dead, in which
case this is even a bigger problem. In any case, if work had to be done
to fix this, it should be a patch against rspec system puppet and not
part of puppet-ceph.
https://github.com/puppetlabs/rspec-system-puppet/issues/5
A test for the ceph::repo class is included to demonstrate the
environment actually works. It is not meant to fully test the ceph::repo
integration this would require a separate patch. rspec-system-puppet
requires at least one file in spec/system otherwise it will fail with
an unrelated error:
Could not autoload puppet/provider/ceph_config/ini_setting: undefined
method `provider' for nil:NilClass (Puppet::Error)
This test can be removed as soon as another is added.
Change-Id: Ib65120a58ce203126be5897f602e280c474642dc
Signed-off-by: Loic Dachary <loic@dachary.org>
* add a ini_file helper as ceph_config.
* set the seperator as ' = ' in order to be the same as ceph-deploy
* add path param so that seperator can be easily tested.
** also allows for users to change the default path if desired.
* add test case to prove spacing around seperator.
* add simple test case to ensure type works.
Closes-bug: #1243852
Change-Id: I0f3bb41d75d48d8af3b5b7cfb7768c4d3de2c002
ZhongShengping