masakari/.gitignore
Shilpa Devharakar 596b3d142e Reorganize masakari documentation
Updated operator guide documentation for
1. segregated sections appropriately
2. referred masakariclient for CLI section
3. added detailed 'Install and configure for Ubuntu' section
4. added detailed 'Verify operation' section
5. used sphinx-build instead of the pbr sphinx extention for building docs
   as instructed by the PTI[1]
6. cleaned up build_sphinx related entries in setup.cfg

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html#documentation

Change-Id: Iec93bebdbc7ffe1ccd27bb11f474384ff06a559c
2019-10-11 01:32:08 +00:00

74 lines
923 B
Plaintext

*.py[cod]
# C extensions
*.so
# Packages
*.egg*
*.egg-info
dist
build
eggs
parts
bin
var
sdist
develop-eggs
.installed.cfg
lib
lib64
# Installer logs
pip-log.txt
# Unit test / coverage reports
cover/
.coverage*
!.coveragerc
.tox
nosetests.xml
.stestr
.venv
# Translations
*.mo
# Mr Developer
.mr.developer.cfg
.project
.pydevproject
# Complexity
output/*.html
output/*/index.html
# Sphinx
doc/build
# pbr generates these
AUTHORS
ChangeLog
# Editors
*~
.*.swp
.*sw?
# Files created by releasenotes build
releasenotes/build
# PyCharm IDE
.idea/
# configuration sample generation
etc/masakari/masakari.conf.sample
etc/masakari/masakari-custom-recovery-methods.conf.sample
# policy sample generation
etc/masakari/policy.yaml.sample
# Files created by doc build
doc/source/_static/masakari.conf.sample
doc/source/_static/masakari-custom-recovery-methods.conf.sample
doc/source/_static/masakari.policy.yaml.sample