diff --git a/playbooks/roles/pip_install/CONTRIBUTING.rst b/playbooks/roles/pip_install/CONTRIBUTING.rst index f84dc6c576..73bef46a31 100644 --- a/playbooks/roles/pip_install/CONTRIBUTING.rst +++ b/playbooks/roles/pip_install/CONTRIBUTING.rst @@ -9,43 +9,55 @@ contributor guidelines Filing Bugs ----------- -Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible" +Bugs should be filed on Launchpad, not GitHub: +"https://bugs.launchpad.net/openstack-ansible" -When submitting a bug, or working on a bug, please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * Steps to reproduce the problem if possible. +When submitting a bug, or working on a bug, please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* Steps to reproduce the problem if possible. Submitting Code --------------- -Changes to the project should be submitted for review via the Gerrit tool, following -the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow" +Changes to the project should be submitted for review via the Gerrit tool, +following the workflow documented at: +"http://docs.openstack.org/infra/manual/developers.html#development-workflow" -Pull requests submitted through GitHub will be ignored and closed without regard. +Pull requests submitted through GitHub will be ignored and closed without +regard. Extra ----- -Tags: - If it's a bug that needs fixing in a branch in addition to Master, add a '\-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete. +Tags: + If it's a bug that needs fixing in a branch in addition to Master, add a + '\-backport-potential' tag (eg ``juno-backport-potential``). + There are predefined tags that will autocomplete. Status: Please leave this alone, it should be New till someone triages the issue. Importance: - Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures. + Should only be touched if it is a Blocker/Gating issue. If it is, please + set to High, and only use Critical if you have found a bug that can take + down whole infrastructures. Style guide ----------- -When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format. +When creating tasks and other roles for use in Ansible please create then using +the YAML dictionary format. Example YAML dictionary format: .. code-block:: yaml @@ -69,17 +81,23 @@ Example **NOT** in YAML dictionary format: - some-other-tag -Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible ``shell`` module. +Usage of the ">" and "|" operators should be limited to Ansible conditionals +and command modules such as the ansible ``shell`` module. Issues ------ -When submitting an issue, or working on an issue please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR). - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * If the issue is needed for a hotfix release, add the 'expedite' label. - * Steps to reproduce the problem if possible. +When submitting an issue, or working on an issue please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* If the issue is a bug that needs fixing in a branch other than Master, add + the ‘backport potential’ tag TO THE ISSUE (not the PR). +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* If the issue is needed for a hotfix release, add the 'expedite' label. +* Steps to reproduce the problem if possible. diff --git a/playbooks/roles/pip_lock_down/CONTRIBUTING.rst b/playbooks/roles/pip_lock_down/CONTRIBUTING.rst index 9fa8b72266..cfe3830de3 100644 --- a/playbooks/roles/pip_lock_down/CONTRIBUTING.rst +++ b/playbooks/roles/pip_lock_down/CONTRIBUTING.rst @@ -9,43 +9,55 @@ contributor guidelines Filing Bugs ----------- -Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible" +Bugs should be filed on Launchpad, not GitHub: +"https://bugs.launchpad.net/openstack-ansible" -When submitting a bug, or working on a bug, please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * Steps to reproduce the problem if possible. +When submitting a bug, or working on a bug, please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* Steps to reproduce the problem if possible. Submitting Code --------------- -Changes to the project should be submitted for review via the Gerrit tool, following -the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow" +Changes to the project should be submitted for review via the Gerrit tool, +following the workflow documented at: +"http://docs.openstack.org/infra/manual/developers.html#development-workflow" -Pull requests submitted through GitHub will be ignored and closed without regard. +Pull requests submitted through GitHub will be ignored and closed without +regard. Extra ----- -Tags: - If it's a bug that needs fixing in a branch in addition to Master, add a '\-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete. +Tags: + If it's a bug that needs fixing in a branch in addition to Master, add a + '\-backport-potential' tag (eg ``juno-backport-potential``). + There are predefined tags that will autocomplete. Status: Please leave this alone, it should be New till someone triages the issue. Importance: - Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures. + Should only be touched if it is a Blocker/Gating issue. If it is, please + set to High, and only use Critical if you have found a bug that can take + down whole infrastructures. Style guide ----------- -When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format. +When creating tasks and other roles for use in Ansible please create then using +the YAML dictionary format. Example YAML dictionary format: .. code-block:: yaml @@ -69,17 +81,23 @@ Example **NOT** in YAML dictionary format: - some-other-tag -Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible ``shell`` module. +Usage of the ">" and "|" operators should be limited to Ansible conditionals +and command modules such as the ansible ``shell`` module. Issues ------ -When submitting an issue, or working on an issue please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR). - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * If the issue is needed for a hotfix release, add the 'expedite' label. - * Steps to reproduce the problem if possible. +When submitting an issue, or working on an issue please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* If the issue is a bug that needs fixing in a branch other than Master, add + the ‘backport potential’ tag TO THE ISSUE (not the PR). +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* If the issue is needed for a hotfix release, add the 'expedite' label. +* Steps to reproduce the problem if possible. diff --git a/playbooks/roles/pip_lock_down/README.rst b/playbooks/roles/pip_lock_down/README.rst index eca84c6a8e..1e64a1245f 100644 --- a/playbooks/roles/pip_lock_down/README.rst +++ b/playbooks/roles/pip_lock_down/README.rst @@ -3,7 +3,9 @@ OpenStack pip lockdown :tags: openstack, pip, lockdown, cloud, ansible :category: \*nix -Role to lock pip down to a particular links repo. This will create a ``.pip.conf`` which will ensure that the only python packages installed when using pip are from a known repository of packages. +Role to lock pip down to a particular links repo. This will create a +``.pip.conf`` which will ensure that the only python packages installed when +using pip are from a known repository of packages. .. code-block:: yaml diff --git a/playbooks/roles/py_from_git/CONTRIBUTING.rst b/playbooks/roles/py_from_git/CONTRIBUTING.rst index 8ae9146928..f81a46c019 100644 --- a/playbooks/roles/py_from_git/CONTRIBUTING.rst +++ b/playbooks/roles/py_from_git/CONTRIBUTING.rst @@ -9,43 +9,55 @@ contributor guidelines Filing Bugs ----------- -Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible" +Bugs should be filed on Launchpad, not GitHub: +"https://bugs.launchpad.net/openstack-ansible" -When submitting a bug, or working on a bug, please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * Steps to reproduce the problem if possible. +When submitting a bug, or working on a bug, please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* Steps to reproduce the problem if possible. Submitting Code --------------- -Changes to the project should be submitted for review via the Gerrit tool, following -the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow" +Changes to the project should be submitted for review via the Gerrit tool, +following the workflow documented at: +"http://docs.openstack.org/infra/manual/developers.html#development-workflow" -Pull requests submitted through GitHub will be ignored and closed without regard. +Pull requests submitted through GitHub will be ignored and closed without +regard. Extra ----- -Tags: - If it's a bug that needs fixing in a branch in addition to Master, add a '\-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete. +Tags: + If it's a bug that needs fixing in a branch in addition to Master, add a + '\-backport-potential' tag (eg ``juno-backport-potential``). + There are predefined tags that will autocomplete. Status: Please leave this alone, it should be New till someone triages the issue. Importance: - Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures. + Should only be touched if it is a Blocker/Gating issue. If it is, please + set to High, and only use Critical if you have found a bug that can take + down whole infrastructures. Style guide ----------- -When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format. +When creating tasks and other roles for use in Ansible please create then using +the YAML dictionary format. Example YAML dictionary format: .. code-block:: yaml @@ -69,17 +81,23 @@ Example **NOT** in YAML dictionary format: - some-other-tag -Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible ``shell`` module. +Usage of the ">" and "|" operators should be limited to Ansible conditionals +and command modules such as the ansible ``shell`` module. Issues ------ -When submitting an issue, or working on an issue please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR). - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * If the issue is needed for a hotfix release, add the 'expedite' label. - * Steps to reproduce the problem if possible. +When submitting an issue, or working on an issue please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* If the issue is a bug that needs fixing in a branch other than Master, add + the ‘backport potential’ tag TO THE ISSUE (not the PR). +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* If the issue is needed for a hotfix release, add the 'expedite' label. +* Steps to reproduce the problem if possible. diff --git a/playbooks/roles/rabbitmq_server/CONTRIBUTING.rst b/playbooks/roles/rabbitmq_server/CONTRIBUTING.rst index 47411ddfea..3601ce4ed2 100644 --- a/playbooks/roles/rabbitmq_server/CONTRIBUTING.rst +++ b/playbooks/roles/rabbitmq_server/CONTRIBUTING.rst @@ -9,43 +9,55 @@ contributor guidelines Filing Bugs ----------- -Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible" +Bugs should be filed on Launchpad, not GitHub: +"https://bugs.launchpad.net/openstack-ansible" -When submitting a bug, or working on a bug, please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * Steps to reproduce the problem if possible. +When submitting a bug, or working on a bug, please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* Steps to reproduce the problem if possible. Submitting Code --------------- -Changes to the project should be submitted for review via the Gerrit tool, following -the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow" +Changes to the project should be submitted for review via the Gerrit tool, +following the workflow documented at: +"http://docs.openstack.org/infra/manual/developers.html#development-workflow" -Pull requests submitted through GitHub will be ignored and closed without regard. +Pull requests submitted through GitHub will be ignored and closed without +regard. Extra ----- -Tags: - If it's a bug that needs fixing in a branch in addition to Master, add a '\-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete. +Tags: + If it's a bug that needs fixing in a branch in addition to Master, add a + '\-backport-potential' tag (eg ``juno-backport-potential``). + There are predefined tags that will autocomplete. Status: Please leave this alone, it should be New till someone triages the issue. Importance: - Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures. + Should only be touched if it is a Blocker/Gating issue. If it is, please + set to High, and only use Critical if you have found a bug that can take + down whole infrastructures. Style guide ----------- -When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format. +When creating tasks and other roles for use in Ansible please create then using +the YAML dictionary format. Example YAML dictionary format: .. code-block:: yaml @@ -69,17 +81,23 @@ Example **NOT** in YAML dictionary format: - some-other-tag -Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible ``shell`` module. +Usage of the ">" and "|" operators should be limited to Ansible conditionals +and command modules such as the ansible ``shell`` module. Issues ------ -When submitting an issue, or working on an issue please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR). - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * If the issue is needed for a hotfix release, add the 'expedite' label. - * Steps to reproduce the problem if possible. +When submitting an issue, or working on an issue please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* If the issue is a bug that needs fixing in a branch other than Master, add + the ‘backport potential’ tag TO THE ISSUE (not the PR). +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* If the issue is needed for a hotfix release, add the 'expedite' label. +* Steps to reproduce the problem if possible. diff --git a/playbooks/roles/repo_server/CONTRIBUTING.rst b/playbooks/roles/repo_server/CONTRIBUTING.rst index 33c1f9ee9b..505977923d 100644 --- a/playbooks/roles/repo_server/CONTRIBUTING.rst +++ b/playbooks/roles/repo_server/CONTRIBUTING.rst @@ -12,40 +12,51 @@ Filing Bugs Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible" -When submitting a bug, or working on a bug, please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * Steps to reproduce the problem if possible. +When submitting a bug, or working on a bug, please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* Steps to reproduce the problem if possible. Submitting Code --------------- -Changes to the project should be submitted for review via the Gerrit tool, following -the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow" +Changes to the project should be submitted for review via the Gerrit tool, +following the workflow documented at: +"http://docs.openstack.org/infra/manual/developers.html#development-workflow" -Pull requests submitted through GitHub will be ignored and closed without regard. +Pull requests submitted through GitHub will be ignored and closed without +regard. Extra ----- -Tags: - If it's a bug that needs fixing in a branch in addition to Master, add a '\-backport-potential' tag (eg ``juno-backport-potential``). There are predefined tags that will autocomplete. +Tags: + If it's a bug that needs fixing in a branch in addition to Master, add a + '\-backport-potential' tag (eg ``juno-backport-potential``). + There are predefined tags that will autocomplete. Status: Please leave this alone, it should be New till someone triages the issue. Importance: - Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures. + Should only be touched if it is a Blocker/Gating issue. If it is, please + set to High, and only use Critical if you have found a bug that can take + down whole infrastructures. Style guide ----------- -When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format. +When creating tasks and other roles for use in Ansible please create then using +the YAML dictionary format. Example YAML dictionary format: .. code-block:: yaml @@ -69,17 +80,23 @@ Example **NOT** in YAML dictionary format: - some-other-tag -Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible ``shell`` module. +Usage of the ">" and "|" operators should be limited to Ansible conditionals +and command modules such as the ansible ``shell`` module. Issues ------ -When submitting an issue, or working on an issue please ensure the following criteria are met: - * The description clearly states or describes the original problem or root cause of the problem. - * Include historical information on how the problem was identified. - * Any relevant logs are included. - * If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR). - * The provided information should be totally self-contained. External access to web services/sites should not be needed. - * If the issue is needed for a hotfix release, add the 'expedite' label. - * Steps to reproduce the problem if possible. +When submitting an issue, or working on an issue please ensure the following +criteria are met: + +* The description clearly states or describes the original problem or root + cause of the problem. +* Include historical information on how the problem was identified. +* Any relevant logs are included. +* If the issue is a bug that needs fixing in a branch other than Master, add + the ‘backport potential’ tag TO THE ISSUE (not the PR). +* The provided information should be totally self-contained. External access to + web services/sites should not be needed. +* If the issue is needed for a hotfix release, add the 'expedite' label. +* Steps to reproduce the problem if possible.