0ebd6723b4
For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ifb8ee9e4c79b64d9c9162fecdaa35c5e9c850871
2980 lines
120 KiB
Plaintext
2980 lines
120 KiB
Plaintext
# Andi Chandler <andi@gowling.com>, 2018. #zanata
|
|
# Ian Y. Choi <ianyrchoi@gmail.com>, 2018. #zanata
|
|
# Andi Chandler <andi@gowling.com>, 2020. #zanata
|
|
# Andi Chandler <andi@gowling.com>, 2021. #zanata
|
|
# Andi Chandler <andi@gowling.com>, 2022. #zanata
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: openstack-ansible 24.1.0.dev221\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"POT-Creation-Date: 2022-05-27 20:22+0000\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
"PO-Revision-Date: 2022-06-01 06:46+0000\n"
|
|
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
|
|
"Language-Team: English (United Kingdom)\n"
|
|
"Language: en_GB\n"
|
|
"X-Generator: Zanata 4.3.3\n"
|
|
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
|
|
|
|
msgid ""
|
|
"\"Bug triage is a process where tracker issues are screened and prioritised. "
|
|
"Triage should help ensure we appropriately manage all reported issues - bugs "
|
|
"as well as improvements and feature requests.\" (Source: `Moodle bug "
|
|
"triage`_)"
|
|
msgstr ""
|
|
"\"Bug triage is a process where tracker issues are screened and prioritised. "
|
|
"Triage should help ensure we appropriately manage all reported issues - bugs "
|
|
"as well as improvements and feature requests.\" (Source: `Moodle bug "
|
|
"triage`_)"
|
|
|
|
msgid "**OpenStack-Ansible**"
|
|
msgstr "**OpenStack-Ansible**"
|
|
|
|
msgid "..."
|
|
msgstr "..."
|
|
|
|
msgid "A"
|
|
msgstr "A"
|
|
|
|
msgid "A consolidated set of all lint tests may be done locally by executing:"
|
|
msgstr "A consolidated set of all lint tests may be done locally by executing:"
|
|
|
|
msgid "A core reviewer's responsibility doesn't end with merging code."
|
|
msgstr "A core reviewer's responsibility doesn't end with merging code."
|
|
|
|
msgid ""
|
|
"A description of how these work can be found in :ref:`inventory-confd` and :"
|
|
"ref:`inventory-envd`."
|
|
msgstr ""
|
|
"A description of how these work can be found in :ref:`inventory-confd` and :"
|
|
"ref:`inventory-envd`."
|
|
|
|
msgid ""
|
|
"A feature release note must be added to announce the new service "
|
|
"availability and to refer to the role documentation for further details. "
|
|
"This content must adhere to the :ref:`documentation`."
|
|
msgstr ""
|
|
"A feature release note must be added to announce the new service "
|
|
"availability and to refer to the role documentation for further details. "
|
|
"This content must adhere to the :ref:`documentation`."
|
|
|
|
msgid ""
|
|
"A member of the OpenStack-Ansible community should monitor the **OpenStack-"
|
|
"discuss** `mailing lists`_."
|
|
msgstr ""
|
|
"A member of the OpenStack-Ansible community should monitor the **OpenStack-"
|
|
"discuss** `mailing lists`_."
|
|
|
|
msgid ""
|
|
"A new project in \"openstack-ansible-ops\" can be started at any time, with "
|
|
"no constraint like writing a specification, or creating a bug."
|
|
msgstr ""
|
|
"A new project in \"openstack-ansible-ops\" can be started at any time, with "
|
|
"no constraint like writing a specification, or creating a bug."
|
|
|
|
msgid "A role can be ``Incubated`` for maximum 2 cycles."
|
|
msgstr "A role can be ``Incubated`` for maximum 2 cycles."
|
|
|
|
msgid "A role can be in one of the four maturity levels:"
|
|
msgstr "A role can be in one of the four maturity levels:"
|
|
|
|
msgid "A role can be retired at any time if it is not relevant anymore."
|
|
msgstr "A role can be retired at any time if it is not relevant anymore."
|
|
|
|
msgid ""
|
|
"A role in ``Complete`` status can be downgraded to ``Unmaintained``. status, "
|
|
"according to the maturity downgrade procedure."
|
|
msgstr ""
|
|
"A role in ``Complete`` status can be downgraded to ``Unmaintained``. status, "
|
|
"according to the maturity downgrade procedure."
|
|
|
|
msgid ""
|
|
"A role may be fully mature, even if it is not integrated in the ``openstack-"
|
|
"ansible`` repository. The maturity depends on its testing levels."
|
|
msgstr ""
|
|
"A role may be fully mature, even if it is not integrated in the ``openstack-"
|
|
"ansible`` repository. The maturity depends on its testing levels."
|
|
|
|
msgid ""
|
|
"A tag including the word ``config`` prepares the configuration of the "
|
|
"software (adapted to your needs), and all the components necessary to run "
|
|
"the service(s) configured in the role. Running a playbook with ``--tags "
|
|
"<role>-config`` is only possible if the target already ran the tags ``<role>-"
|
|
"install``."
|
|
msgstr ""
|
|
"A tag including the word ``config`` prepares the configuration of the "
|
|
"software (adapted to your needs), and all the components necessary to run "
|
|
"the service(s) configured in the role. Running a playbook with ``--tags "
|
|
"<role>-config`` is only possible if the target already ran the tags ``<role>-"
|
|
"install``."
|
|
|
|
msgid ""
|
|
"A tag including the word ``install`` handles software installation tasks. "
|
|
"Running a playbook with ``--tags <role>-install`` only deploys the necessary "
|
|
"software on the target, and will not configure it to your needs or run any "
|
|
"service."
|
|
msgstr ""
|
|
"A tag including the word ``install`` handles software installation tasks. "
|
|
"Running a playbook with ``--tags <role>-install`` only deploys the necessary "
|
|
"software on the target, and will not configure it to your needs or run any "
|
|
"service."
|
|
|
|
msgid "A tag including the word ``upgrade`` handles all the upgrade tasks."
|
|
msgstr "A tag including the word ``upgrade`` handles all the upgrade tasks."
|
|
|
|
msgid ""
|
|
"Actively reviewing patch submissions, considering whether the patch: - is "
|
|
"functional - fits the use-cases and vision of the project - is complete in "
|
|
"terms of testing, documentation, and release notes - takes into "
|
|
"consideration upgrade concerns from previous versions"
|
|
msgstr ""
|
|
"Actively reviewing patch submissions, considering whether the patch: - is "
|
|
"functional - fits the use-cases and vision of the project - is complete in "
|
|
"terms of testing, documentation, and release notes - takes into "
|
|
"consideration upgrade concerns from previous versions"
|
|
|
|
msgid ""
|
|
"Add a new non-voting job in ``zuul.d/jobs.yaml``, and wire it in the project "
|
|
"tests file ``zuul.d/project.yaml``."
|
|
msgstr ""
|
|
"Add a new non-voting job in ``zuul.d/jobs.yaml``, and wire it in the project "
|
|
"tests file ``zuul.d/project.yaml``."
|
|
|
|
msgid ""
|
|
"Add an extra role test scenario, to ensure your code path is tested and "
|
|
"working."
|
|
msgstr ""
|
|
"Add an extra role test scenario, to ensure your code path is tested and "
|
|
"working."
|
|
|
|
msgid "Add tests to the role. See also our :ref:`tests` page."
|
|
msgstr "Add tests to the role. See also our :ref:`tests` page."
|
|
|
|
msgid "Adding patch in releases repo"
|
|
msgstr "Adding patch in releases repo"
|
|
|
|
msgid "Adding tests to a new role"
|
|
msgstr "Adding tests to a new role"
|
|
|
|
msgid "After creating a new stable branch:"
|
|
msgstr "After creating a new stable branch:"
|
|
|
|
msgid "After milestone 3:"
|
|
msgstr "After milestone 3:"
|
|
|
|
msgid ""
|
|
"After official project release, before official OpenStack-Ansible release:"
|
|
msgstr ""
|
|
"After official project release, before official OpenStack-Ansible release:"
|
|
|
|
msgid ""
|
|
"All Core reviewer duties are described on the page :dev_docs:`Core Reviewers "
|
|
"<contributor/core-reviewers.html>`."
|
|
msgstr ""
|
|
"All Core reviewer duties are described on the page :dev_docs:`Core Reviewers "
|
|
"<contributor/core-reviewers.html>`."
|
|
|
|
msgid ""
|
|
"All blueprints/specs should be voted on and approved by core reviewers "
|
|
"before any associated code will be merged. For more information on "
|
|
"blueprints/specs please review the OpenStack documentation regarding "
|
|
"`Working on Specifications and Blueprints`_ and our own :ref:`specs`."
|
|
msgstr ""
|
|
"All blueprints/specs should be voted on and approved by core reviewers "
|
|
"before any associated code will be merged. For more information on "
|
|
"blueprints/specs please review the OpenStack documentation regarding "
|
|
"`Working on Specifications and Blueprints`_ and our own :ref:`specs`."
|
|
|
|
msgid ""
|
|
"All changes should be clearly listed in the commit message, with an "
|
|
"associated bug id/blueprint along with any extra information where "
|
|
"applicable."
|
|
msgstr ""
|
|
"All changes should be clearly listed in the commit message, with an "
|
|
"associated bug id/blueprint along with any extra information where "
|
|
"applicable."
|
|
|
|
msgid "All code requires to go through our :ref:`reviews`."
|
|
msgstr "All code requires to go through our :ref:`reviews`."
|
|
|
|
msgid "All code should match our :ref:`codeguidelines`."
|
|
msgstr "All code should match our :ref:`codeguidelines`."
|
|
|
|
msgid ""
|
|
"All common PTL duties are enumerated in the `PTL guide <https://docs."
|
|
"openstack.org/project-team-guide/ptl.html>`_."
|
|
msgstr ""
|
|
"All common PTL duties are enumerated in the `PTL guide <https://docs."
|
|
"openstack.org/project-team-guide/ptl.html>`_."
|
|
|
|
msgid ""
|
|
"All forms of documentation should comply with the guidelines provided in the "
|
|
"`OpenStack Documentation Contributor Guide`_, with particular reference to "
|
|
"the following sections:"
|
|
msgstr ""
|
|
"All forms of documentation should comply with the guidelines provided in the "
|
|
"`OpenStack Documentation Contributor Guide`_, with particular reference to "
|
|
"the following sections:"
|
|
|
|
msgid ""
|
|
"All large feature additions/deletions should be accompanied by a blueprint/"
|
|
"spec. e.g. adding additional active agents to neutron, developing a new "
|
|
"service role, etc... See also :ref:`specs`."
|
|
msgstr ""
|
|
"All large feature additions/deletions should be accompanied by a blueprint/"
|
|
"spec. e.g. adding additional active agents to neutron, developing a new "
|
|
"service role, etc... See also :ref:`specs`."
|
|
|
|
msgid ""
|
|
"All of our core team is available through IRC and present in #openstack-"
|
|
"ansible channel on OFTC. The list of the current members of the OpenStack-"
|
|
"Ansible Team might be found on `gerrit`_."
|
|
msgstr ""
|
|
"All of our core team is available through IRC and present in #openstack-"
|
|
"ansible channel on OFTC. The list of the current members of the OpenStack-"
|
|
"Ansible Team might be found on `gerrit`_."
|
|
|
|
msgid ""
|
|
"All of the OpenStack-Ansible roles do not have the same level of maturity "
|
|
"and testing."
|
|
msgstr ""
|
|
"All of the OpenStack-Ansible roles do not have the same level of maturity "
|
|
"and testing."
|
|
|
|
msgid "All our communications should be prefixed with **[openstack-ansible]**."
|
|
msgstr ""
|
|
"All our communications should be prefixed with **[openstack-ansible]**."
|
|
|
|
msgid ""
|
|
"All patch sets should adhere to the :ref:`Ansible Style Guide` listed here "
|
|
"as well as adhere to the `Ansible best practices`_ when possible."
|
|
msgstr ""
|
|
"All patch sets should adhere to the :ref:`Ansible Style Guide` listed here "
|
|
"as well as adhere to the `Ansible best practices`_ when possible."
|
|
|
|
msgid ""
|
|
"All patches including code, documentation and release notes should be built "
|
|
"and tested locally with the appropriate test suite before submitting for "
|
|
"review. See :ref:`Development and Testing<devel_and_testing>` for more "
|
|
"information."
|
|
msgstr ""
|
|
"All patches including code, documentation and release notes should be built "
|
|
"and tested locally with the appropriate test suite before submitting for "
|
|
"review. See :ref:`Development and Testing<devel_and_testing>` for more "
|
|
"information."
|
|
|
|
msgid "Also called *integrated repository*"
|
|
msgstr "Also called *integrated repository*"
|
|
|
|
msgid ""
|
|
"Also you may find more detailed information about how to work with bugs on "
|
|
"the page :dev_docs:`Bug Handling <contributor/bugs.html>`"
|
|
msgstr ""
|
|
"Also you may find more detailed information about how to work with bugs on "
|
|
"the page :dev_docs:`Bug Handling <contributor/bugs.html>`"
|
|
|
|
msgid ""
|
|
"Alternatively, you can check the :ref:`aio guide<quickstart-aio>`, or even "
|
|
"run the gate wrapper script, named ``scripts/gate-check-commit.sh``, "
|
|
"described below."
|
|
msgstr ""
|
|
"Alternatively, you can check the :ref:`aio guide<quickstart-aio>`, or even "
|
|
"run the gate wrapper script, named ``scripts/gate-check-commit.sh``, "
|
|
"described below."
|
|
|
|
msgid ""
|
|
"An ``Incubated`` role that didn't implement functional testing in the six "
|
|
"month timeframe will become ``Unmaintained``."
|
|
msgstr ""
|
|
"An ``Incubated`` role that didn't implement functional testing in the six "
|
|
"month timeframe will become ``Unmaintained``."
|
|
|
|
msgid ""
|
|
"An ``Incubated`` role that passes functional testing will be upgraded to the "
|
|
"``Complete`` status, and cannot return in ``Incubated`` status."
|
|
msgstr ""
|
|
"An ``Incubated`` role that passes functional testing will be upgraded to the "
|
|
"``Complete`` status, and cannot return in ``Incubated`` status."
|
|
|
|
msgid "Ansible Style Guide"
|
|
msgstr "Ansible Style Guide"
|
|
|
|
msgid "Ansible is lint tested using `ansible-lint`_."
|
|
msgstr "Ansible is lint tested using `ansible-lint`_."
|
|
|
|
msgid "Ansible playbook syntax is tested using ansible-playbook."
|
|
msgstr "Ansible playbook syntax is tested using ansible-playbook."
|
|
|
|
msgid "Answering questions and participating in mailing list discussions"
|
|
msgstr "Answering questions and participating in mailing list discussions"
|
|
|
|
msgid "Any bug fix should have, in its commit message:"
|
|
msgstr "Any bug fix should have, in its commit message:"
|
|
|
|
msgid ""
|
|
"Any new OpenStack services implemented which have `Tempest`_ tests available "
|
|
"must be implemented along with suitable functional tests enabled as part of "
|
|
"the feature development in order to ensure that any changes to the code base "
|
|
"do not break the service functionality."
|
|
msgstr ""
|
|
"Any new OpenStack services implemented which have `Tempest`_ tests available "
|
|
"must be implemented along with suitable functional tests enabled as part of "
|
|
"the feature development in order to ensure that any changes to the code base "
|
|
"do not break the service functionality."
|
|
|
|
msgid ""
|
|
"Any new code will be reviewed before merging into our repositories and "
|
|
"requires at least 2 approvals from our Core team."
|
|
msgstr ""
|
|
"Any new code will be reviewed before merging into our repositories and "
|
|
"requires at least 2 approvals from our Core team."
|
|
|
|
msgid "Any new code will be reviewed before merging into our repositories."
|
|
msgstr "Any new code will be reviewed before merging into our repositories."
|
|
|
|
msgid ""
|
|
"Any relevant logs or user configuration are included, either directly or "
|
|
"through a pastebin."
|
|
msgstr ""
|
|
"Any relevant logs or user configuration are included, either directly or "
|
|
"through a pastebin."
|
|
|
|
msgid ""
|
|
"Any secrets (For example: passwords) should not be provided with default "
|
|
"values in the tasks, role vars, or role defaults. The tasks should be "
|
|
"implemented in such a way that any secrets required, but not provided, "
|
|
"should result in the task execution failure. It is important for a secure-by-"
|
|
"default implementation to ensure that an environment is not vulnerable due "
|
|
"to the production use of default secrets. Deployers must be forced to "
|
|
"properly provide their own secret variable values."
|
|
msgstr ""
|
|
"Any secrets (For example: passwords) should not be provided with default "
|
|
"values in the tasks, role vars, or role defaults. The tasks should be "
|
|
"implemented in such a way that any secrets required, but not provided, "
|
|
"should result in the task execution failure. It is important for a secure-by-"
|
|
"default implementation to ensure that an environment is not vulnerable due "
|
|
"to the production use of default secrets. Deployers must be forced to "
|
|
"properly provide their own secret variable values."
|
|
|
|
msgid ""
|
|
"Any secrets required for the role to work must be noted in the ``etc/"
|
|
"openstack_deploy/user_secrets.yml`` file for reuse by other users."
|
|
msgstr ""
|
|
"Any secrets required for the role to work must be noted in the ``etc/"
|
|
"openstack_deploy/user_secrets.yml`` file for reuse by other users."
|
|
|
|
msgid ""
|
|
"Any variables needed by other roles to connect to the new role, or by the "
|
|
"new role to connect to other roles, should be implemented in ``inventory/"
|
|
"group_vars``. The group vars are essentially the glue which playbooks use to "
|
|
"ensure that all roles are given the appropriate information. When group vars "
|
|
"are implemented it should be a minimum set to achieve the goal of "
|
|
"integrating the new role into the integrated build."
|
|
msgstr ""
|
|
"Any variables needed by other roles to connect to the new role, or by the "
|
|
"new role to connect to other roles, should be implemented in ``inventory/"
|
|
"group_vars``. The group vars are essentially the glue which playbooks use to "
|
|
"ensure that all roles are given the appropriate information. When group vars "
|
|
"are implemented it should be a minimum set to achieve the goal of "
|
|
"integrating the new role into the integrated build."
|
|
|
|
msgid ""
|
|
"Are you sure nobody is working on this problem at the moment? Could there be "
|
|
"a review pending fixing the same issue?"
|
|
msgstr ""
|
|
"Are you sure nobody is working on this problem at the moment? Could there be "
|
|
"a review pending fixing the same issue?"
|
|
|
|
msgid "Assist in bug triage and delivery of bug fixes"
|
|
msgstr "Assist in bug triage and delivery of bug fixes"
|
|
|
|
msgid "Attend and participate in the weekly IRC meetings"
|
|
msgstr "Attend and participate in the weekly IRC meetings"
|
|
|
|
msgid ""
|
|
"Backport reviews should be done with due consideration to the effect of the "
|
|
"patch on any existing environment deployed by OpenStack-Ansible. The general "
|
|
"`OpenStack Guidelines for stable branches`_ can be used as a reference."
|
|
msgstr ""
|
|
"Backport reviews should be done with due consideration to the effect of the "
|
|
"patch on any existing environment deployed by OpenStack-Ansible. The general "
|
|
"`OpenStack Guidelines for stable branches`_ can be used as a reference."
|
|
|
|
msgid "Backporting"
|
|
msgstr "Backporting"
|
|
|
|
msgid ""
|
|
"Backporting is defined as the act of reproducing a change from another "
|
|
"branch. Unclean/squashed/modified cherry-picks and complete "
|
|
"reimplementations are OK."
|
|
msgstr ""
|
|
"Backporting is defined as the act of reproducing a change from another "
|
|
"branch. Unclean/squashed/modified cherry-picks and complete "
|
|
"reimplementations are OK."
|
|
|
|
msgid ""
|
|
"Backporting is often done by using the same code (via cherry picking), but "
|
|
"this is not always the case. This method is preferred when the cherry-pick "
|
|
"provides a complete solution for the targeted problem."
|
|
msgstr ""
|
|
"Backporting is often done by using the same code (via cherry-picking), but "
|
|
"this is not always the case. This method is preferred when the cherry-pick "
|
|
"provides a complete solution for the targeted problem."
|
|
|
|
msgid ""
|
|
"Bash coding conventions are tested using `Bashate`_, with the following "
|
|
"convention exceptions:"
|
|
msgstr ""
|
|
"Bash coding conventions are tested using `Bashate`_, with the following "
|
|
"convention exceptions:"
|
|
|
|
msgid ""
|
|
"Before creating blueprint/spec an associated 'Wishlist Bug' can be raised on "
|
|
"launchpad. This issue will be triaged and a determination will be made on "
|
|
"how large the change is and whether or not the change warrants a blueprint/"
|
|
"spec. Both features and bug fixes may require the creation of a blueprint/"
|
|
"spec. This requirement will be voted on by core reviewers and will be based "
|
|
"on the size and impact of the change."
|
|
msgstr ""
|
|
"Before creating blueprint/spec an associated 'Wishlist Bug' can be raised on "
|
|
"launchpad. This issue will be triaged and a determination will be made on "
|
|
"how large the change is and whether or not the change warrants a blueprint/"
|
|
"spec. Both features and bug fixes may require the creation of a blueprint/"
|
|
"spec. This requirement will be voted on by core reviewers and will be based "
|
|
"on the size and impact of the change."
|
|
|
|
msgid ""
|
|
"Before jumping ahead and working on code, a series of steps should be taken:"
|
|
msgstr ""
|
|
"Before jumping ahead and working on code, a series of steps should be taken:"
|
|
|
|
msgid "Before submitting code"
|
|
msgstr "Before submitting code"
|
|
|
|
msgid ""
|
|
"Below will cover the more project specific information you need to get "
|
|
"started with OpenStack-Ansible."
|
|
msgstr ""
|
|
"Below will cover the more project-specific information you need to get "
|
|
"started with OpenStack-Ansible."
|
|
|
|
msgid ""
|
|
"Branch all the independent repos that aren't part of the release in gerrit. "
|
|
"See also the ``projects.yaml`` in the governance repo. Manually branched "
|
|
"repos need extra editions, like updating the .gitreview, or the reno index. "
|
|
"Please reference previous branch creations by using the appropriate topic in "
|
|
"gerrit (e.g.: ``create-stein``). The previous new branch creation may be "
|
|
"different as the tooling/process may have evolved, so be aware that the "
|
|
"changes needed may need to be adapted."
|
|
msgstr ""
|
|
"Branch all the independent repos that aren't part of the release in Gerrit. "
|
|
"See also the ``projects.yaml`` in the governance repo. Manually branched "
|
|
"repos need extra editions, like updating the .gitreview, or the reno index. "
|
|
"Please reference previous branch creations by using the appropriate topic in "
|
|
"Gerrit (e.g.: ``create-stein``). The previous new branch creation may be "
|
|
"different as the tooling/process may have evolved, so be aware that the "
|
|
"changes needed may need to be adapted."
|
|
|
|
msgid "Bug Reporting"
|
|
msgstr "Bug Reporting"
|
|
|
|
msgid "Bug Tags"
|
|
msgstr "Bug Tags"
|
|
|
|
msgid "Bug skimming duty"
|
|
msgstr "Bug skimming duty"
|
|
|
|
msgid ""
|
|
"Bug skimming duty reduces the amount of work other developers have to spend "
|
|
"to do a proper root cause analysis (and later fix) of bug reports. For this, "
|
|
"close the obviously invalid bug reports, confirm the obviously valid bug "
|
|
"reports, ask questions if things are unclear."
|
|
msgstr ""
|
|
"Bug skimming duty reduces the amount of work other developers have to spend "
|
|
"to do a proper root cause analysis (and later fix) of bug reports. For this, "
|
|
"close the obviously invalid bug reports, confirm the obviously valid bug "
|
|
"reports, ask questions if things are unclear."
|
|
|
|
msgid "Bug skimming duty weekly checklist"
|
|
msgstr "Bug skimming duty weekly checklist"
|
|
|
|
msgid "Bug triage"
|
|
msgstr "Bug triage"
|
|
|
|
msgid "Bug triage meeting duties"
|
|
msgstr "Bug triage meeting duties"
|
|
|
|
msgid "Bugs should be filed on the `OpenStack-Ansible Launchpad project`_."
|
|
msgstr "Bugs should be filed on the `OpenStack-Ansible Launchpad project`_."
|
|
|
|
msgid ""
|
|
"Bump RDO and Ubuntu Cloud Archive repositories if they are ready on time."
|
|
msgstr ""
|
|
"Bump RDO and Ubuntu Cloud Archive repositories if they are ready on time."
|
|
|
|
msgid ""
|
|
"Bump ``ceph_stable_release`` to latest Ceph LTS release in the integrated "
|
|
"OpenStack-Ansible repo, and inside the ``ceph_client`` role defaults."
|
|
msgstr ""
|
|
"Bump ``ceph_stable_release`` to the latest Ceph LTS release in the "
|
|
"integrated OpenStack-Ansible repo, and inside the ``ceph_client`` role "
|
|
"defaults."
|
|
|
|
msgid "By milestone 1:"
|
|
msgstr "By milestone 1:"
|
|
|
|
msgid "By milestone 2:"
|
|
msgstr "By milestone 2:"
|
|
|
|
msgid "By milestone 3:"
|
|
msgstr "By milestone 3:"
|
|
|
|
msgid ""
|
|
"By proposing a draft spec you can help the OpenStack-Ansible community keep "
|
|
"track of what roles or large changes are being developed, and perhaps "
|
|
"connect you with others who may be interested and able to help you in the "
|
|
"process."
|
|
msgstr ""
|
|
"By proposing a draft spec you can help the OpenStack-Ansible community keep "
|
|
"track of what roles or large changes are being developed, and perhaps "
|
|
"connect you with others who may be interested and able to help you in the "
|
|
"process."
|
|
|
|
msgid ""
|
|
"Changes in the project over time which may affect an existing deployment."
|
|
msgstr ""
|
|
"Changes in the project over time which may affect an existing deployment."
|
|
|
|
msgid ""
|
|
"Changes to the project should be submitted for review via the Gerrit tool, "
|
|
"following the `workflow documented here`_."
|
|
msgstr ""
|
|
"Changes to the project should be submitted for review via the Gerrit tool, "
|
|
"following the `workflow documented here`_."
|
|
|
|
msgid "Check and bump galera versions if required."
|
|
msgstr "Check and bump Galera versions if required."
|
|
|
|
msgid "Check and bump rabbitmq versions if required."
|
|
msgstr "Check and bump RabbitMQ versions if required."
|
|
|
|
msgid "Check current pins status"
|
|
msgstr "Check current pins status"
|
|
|
|
msgid ""
|
|
"Check outstanding reviews and move to merge or abandon them if no longer "
|
|
"valid."
|
|
msgstr ""
|
|
"Check outstanding reviews and move to merge or abandon them if no longer "
|
|
"valid."
|
|
|
|
msgid "Closes-Bug: #bugnumber"
|
|
msgstr "Closes-Bug: #bugnumber"
|
|
|
|
msgid "Code Comments"
|
|
msgstr "Code Comments"
|
|
|
|
msgid "Code Merge Responsibilities"
|
|
msgstr "Code Merge Responsibilities"
|
|
|
|
msgid ""
|
|
"Code comments for bash/python scripts should give guidance to the purpose of "
|
|
"the code. This is important to provide context for reviewers before the "
|
|
"patch has merged, and for later modifications to remind the contributors "
|
|
"what the purpose was and why it was done that way."
|
|
msgstr ""
|
|
"Code comments for bash/python scripts should give guidance to the purpose of "
|
|
"the code. This is important to provide context for reviewers before the "
|
|
"patch has merged, and for later modifications to remind the contributors "
|
|
"what the purpose was and why it was done that way."
|
|
|
|
msgid ""
|
|
"Code comments for variables should be used to explain the purpose of the "
|
|
"variable. This is particularly important for the role defaults file as the "
|
|
"file is included verbatim in the role's documentation. Where there is an "
|
|
"optional variable, the variable and an explanation of what it is used for "
|
|
"should be added to the defaults file."
|
|
msgstr ""
|
|
"Code comments for variables should be used to explain the purpose of the "
|
|
"variable. This is particularly important for the role defaults file as the "
|
|
"file is included verbatim in the role's documentation. Where there is an "
|
|
"optional variable, the variable and an explanation of what it is used for "
|
|
"should be added to the defaults file."
|
|
|
|
msgid "Code location"
|
|
msgstr "Code location"
|
|
|
|
msgid "Code rules"
|
|
msgstr "Code rules"
|
|
|
|
msgid "Communication"
|
|
msgstr "Communication"
|
|
|
|
msgid "Community communication channels"
|
|
msgstr "Community communication channels"
|
|
|
|
msgid "Community goal acknowledgement."
|
|
msgstr "Community goal acknowledgement."
|
|
|
|
msgid "Contacting the Core Team"
|
|
msgstr "Contacting the Core Team"
|
|
|
|
msgid "Container technology independence"
|
|
msgstr "Container technology independence"
|
|
|
|
msgid "Contents:"
|
|
msgstr "Contents:"
|
|
|
|
msgid "Contributor Guidelines"
|
|
msgstr "Contributor Guidelines"
|
|
|
|
msgid "Copy release notes relevant to the freeze."
|
|
msgstr "Copy release notes relevant to the freeze."
|
|
|
|
msgid "Core Reviewer Expectations"
|
|
msgstr "Core Reviewer Expectations"
|
|
|
|
msgid "Core Reviewers"
|
|
msgstr "Core Reviewers"
|
|
|
|
msgid ""
|
|
"Create a source repository (e.g. on Github) to start your work on the Role."
|
|
msgstr ""
|
|
"Create a source repository (e.g. on Github) to start your work on the Role."
|
|
|
|
msgid "Curating the gate and triaging failures"
|
|
msgstr "Curating the gate and triaging failures"
|
|
|
|
msgid ""
|
|
"Definitively *Invalid*. The status *Incomplete* is an open state and means "
|
|
"that more information is necessary."
|
|
msgstr ""
|
|
"Definitively *Invalid*. The status *Incomplete* is an open state and means "
|
|
"that more information is necessary."
|
|
|
|
msgid "Deploy the applicable configuration files in the right places."
|
|
msgstr "Deploy the applicable configuration files in the right places."
|
|
|
|
msgid ""
|
|
"Develop task files for each of the install stages in turn, creating any "
|
|
"handlers and templates as needed. Ensure that you notify handlers after any "
|
|
"task which impacts the way the service would run (such as configuration file "
|
|
"modifications). Also take care that file ownership and permissions are "
|
|
"appropriate."
|
|
msgstr ""
|
|
"Develop task files for each of the install stages in turn, creating any "
|
|
"handlers and templates as needed. Ensure that you notify handlers after any "
|
|
"task which impacts the way the service would run (such as configuration file "
|
|
"modifications). Also take care that file ownership and permissions are "
|
|
"appropriate."
|
|
|
|
msgid "Developer Documentation"
|
|
msgstr "Developer Documentation"
|
|
|
|
msgid "Development cycle checklist"
|
|
msgstr "Development cycle checklist"
|
|
|
|
msgid "Distribution support"
|
|
msgstr "Distribution support"
|
|
|
|
msgid ""
|
|
"Distributions can be promoted to voting jobs on individual roles once they "
|
|
"move to the `Graduation` phase and their stability has been confirmed by the "
|
|
"core OpenStack-Ansible developers. Similar to this, voting can also be "
|
|
"enabled in the integration repository for all the scenarios or a specific "
|
|
"one."
|
|
msgstr ""
|
|
"Distributions can be promoted to voting jobs on individual roles once they "
|
|
"move to the `Graduation` phase and their stability has been confirmed by the "
|
|
"core OpenStack-Ansible developers. Similar to this, voting can also be "
|
|
"enabled in the integration repository for all the scenarios or a specific "
|
|
"one."
|
|
|
|
msgid ""
|
|
"Do I have to double-check bug reports which are New and have an assignee?"
|
|
msgstr ""
|
|
"Do I have to double-check bug reports which are New and have an assignee?"
|
|
|
|
msgid ""
|
|
"Do I need to prove that a bug report is valid/invalid before I can set it to "
|
|
"*Confirmed*/*Invalid* ?"
|
|
msgstr ""
|
|
"Do I need to prove that a bug report is valid/invalid before I can set it to "
|
|
"*Confirmed*/*Invalid* ?"
|
|
|
|
msgid "Documentation and Release Note Guidelines"
|
|
msgstr "Documentation and Release Note Guidelines"
|
|
|
|
msgid "Documentation building"
|
|
msgstr "Documentation building"
|
|
|
|
msgid ""
|
|
"Documentation is a critical part of ensuring that the deployers of OpenStack-"
|
|
"Ansible are appropriately informed about:"
|
|
msgstr ""
|
|
"Documentation is a critical part of ensuring that the deployers of OpenStack-"
|
|
"Ansible are appropriately informed about:"
|
|
|
|
msgid ""
|
|
"Documentation is developed in reStructuredText_ (RST) and compiled into HTML "
|
|
"using Sphinx."
|
|
msgstr ""
|
|
"Documentation is developed in reStructuredText_ (RST) and compiled into HTML "
|
|
"using Sphinx."
|
|
|
|
msgid "Documentation locations"
|
|
msgstr "Documentation locations"
|
|
|
|
msgid "Documentation may be built locally by executing:"
|
|
msgstr "Documentation may be built locally by executing:"
|
|
|
|
msgid ""
|
|
"Documentation must be added in the role to describe how to implement the new "
|
|
"service in an integrated environement. This content must adhere to the :ref:"
|
|
"`documentation`. Until the role has integrated functional testing "
|
|
"implemented (see also the Role development maturity paragraph), the "
|
|
"documentation must make it clear that the service inclusion in OpenStack-"
|
|
"Ansible is experimental and is not fully tested by OpenStack-Ansible in an "
|
|
"integrated build. Alternatively, an user story can be created."
|
|
msgstr ""
|
|
"Documentation must be added in the role to describe how to implement the new "
|
|
"service in an integrated environment. This content must adhere to the :ref:"
|
|
"`documentation`. Until the role has integrated functional testing "
|
|
"implemented (see also the Role development maturity paragraph), the "
|
|
"documentation must make it clear that the service inclusion in OpenStack-"
|
|
"Ansible is experimental and is not fully tested by OpenStack-Ansible in an "
|
|
"integrated build. Alternatively, an user story can be created."
|
|
|
|
msgid ""
|
|
"Documentation should be provided with the code directly. See also :ref:"
|
|
"`documentation`."
|
|
msgstr ""
|
|
"Documentation should be provided with the code directly. See also :ref:"
|
|
"`documentation`."
|
|
|
|
msgid ""
|
|
"E003: Indent not multiple of 4. We prefer to use multiples of 2 instead."
|
|
msgstr ""
|
|
"E003: Indent not multiple of 4. We prefer to use multiples of 2 instead."
|
|
|
|
msgid ""
|
|
"E006: Line longer than 79 columns. As many scripts are deployed as templates"
|
|
msgstr ""
|
|
"E006: Line longer than 79 columns. As many scripts are deployed as templates"
|
|
|
|
msgid ""
|
|
"E040: Syntax error determined using `bash -n`. As many scripts are deployed"
|
|
msgstr ""
|
|
"E040: Syntax error determined using `bash -n`. As many scripts are deployed"
|
|
|
|
msgid ""
|
|
"Each list item must make sense to read without the context of the patch or "
|
|
"the repository the patch is being submitted into. The reason for this is "
|
|
"that all release notes are consolidated and presented in a long list without "
|
|
"reference to the source patch or the context of the repository."
|
|
msgstr ""
|
|
"Each list item must make sense to read without the context of the patch or "
|
|
"the repository the patch is being submitted into. The reason for this is "
|
|
"that all release notes are consolidated and presented in a long list without "
|
|
"reference to the source patch or the context of the repository."
|
|
|
|
msgid ""
|
|
"Each note should be brief and to the point. Try to avoid multi-paragraph "
|
|
"notes. For features the note should typically refer to documentation for "
|
|
"more details. For bug fixes the note can refer to a registered bug for more "
|
|
"details."
|
|
msgstr ""
|
|
"Each note should be brief and to the point. Try to avoid multi-paragraph "
|
|
"notes. For features the note should typically refer to documentation for "
|
|
"more details. For bug fixes the note can refer to a registered bug for more "
|
|
"details."
|
|
|
|
msgid "Each of the role tests is in its tests/ folder."
|
|
msgstr "Each of the role tests is in its tests/ folder."
|
|
|
|
msgid ""
|
|
"Each role is in charge of deploying **exactly one** component of an "
|
|
"OpenStack-Ansible deployment."
|
|
msgstr ""
|
|
"Each role is in charge of deploying **exactly one** component of an "
|
|
"OpenStack-Ansible deployment."
|
|
|
|
msgid ""
|
|
"Easy to fix bugs are marked with the tag *low hanging fruit*, and should be "
|
|
"the target of first time contributors."
|
|
msgstr ""
|
|
"Easy to fix bugs are marked with the tag *low hanging fruit*, and should be "
|
|
"the target of first-time contributors."
|
|
|
|
msgid "Ensure that the service starts."
|
|
msgstr "Ensure that the service starts."
|
|
|
|
msgid "Ensure the role converges:"
|
|
msgstr "Ensure the role converges:"
|
|
|
|
msgid ""
|
|
"Ensuring the level of testing is adequate and remains relevant as features "
|
|
"are added"
|
|
msgstr ""
|
|
"Ensuring the level of testing is adequate and remains relevant as features "
|
|
"are added"
|
|
|
|
msgid ""
|
|
"Ensuring the role matches OpenStack-Ansible's latest standards. See also "
|
|
"our :ref:`code_rules` page."
|
|
msgstr ""
|
|
"Ensuring the role matches OpenStack-Ansible's latest standards. See also "
|
|
"our :ref:`code_rules` page."
|
|
|
|
msgid ""
|
|
"Every backport commit must still only solve one problem, as per the "
|
|
"guidelines in :ref:`codeguidelines`."
|
|
msgstr ""
|
|
"Every backport commit must still only solve one problem, as per the "
|
|
"guidelines in :ref:`codeguidelines`."
|
|
|
|
msgid "Example YAML dictionary format:"
|
|
msgstr "Example YAML dictionary format:"
|
|
|
|
msgid "Example process for adding a feature to an existing role"
|
|
msgstr "Example process for adding a feature to an existing role"
|
|
|
|
msgid "Example process to develop a new role"
|
|
msgstr "Example process to develop a new role"
|
|
|
|
msgid "Example process to incubate a new \"ops\" project"
|
|
msgstr "Example process to incubate a new \"ops\" project"
|
|
|
|
msgid "Example what **NOT** to do:"
|
|
msgstr "Example what **NOT** to do:"
|
|
|
|
msgid ""
|
|
"Existing and new distributions are expected to meet the following "
|
|
"requirements in order for them to be accepted in the individual OpenStack-"
|
|
"Ansible roles:"
|
|
msgstr ""
|
|
"Existing and new distributions are expected to meet the following "
|
|
"requirements in order for them to be accepted in the individual OpenStack-"
|
|
"Ansible roles:"
|
|
|
|
msgid "Extending tests of an existing role"
|
|
msgstr "Extending tests of an existing role"
|
|
|
|
msgid "External repositories"
|
|
msgstr "External repositories"
|
|
|
|
msgid "F403 - 'from ansible.module_utils.basic import \\*'"
|
|
msgstr "F403 - 'from ansible.module_utils.basic import \\*'"
|
|
|
|
msgid ""
|
|
"Feature additions must include documentation which provides reference to "
|
|
"OpenStack documentation about what the feature is and how it works. The "
|
|
"documentation should then describe how it is implemented in OpenStack-"
|
|
"Ansible and what configuration options there are. See also the :ref:"
|
|
"`documentation` section."
|
|
msgstr ""
|
|
"Feature additions must include documentation which provides reference to "
|
|
"OpenStack documentation about what the feature is and how it works. The "
|
|
"documentation should then describe how it is implemented in OpenStack-"
|
|
"Ansible and what configuration options there are. See also the :ref:"
|
|
"`documentation` section."
|
|
|
|
msgid "Feature freeze, bug fixes, and testing improvements."
|
|
msgstr "Feature freeze, bug fixes, and testing improvements."
|
|
|
|
msgid ""
|
|
"Fill in variable defaults, libraries, and prerequisites as you discover a "
|
|
"need for them. You can also develop documentation for your role at the same "
|
|
"time."
|
|
msgstr ""
|
|
"Fill in variable defaults, libraries, and prerequisites as you discover a "
|
|
"need for them. You can also develop documentation for your role at the same "
|
|
"time."
|
|
|
|
msgid ""
|
|
"Fixing bugs and increasing test coverage have priority to new features. See "
|
|
"also the section :ref:`bugfixing`."
|
|
msgstr ""
|
|
"Fixing bugs and increasing test coverage have priority to new features. See "
|
|
"also the section :ref:`bugfixing`."
|
|
|
|
msgid ""
|
|
"For a distribution to be considered supported by the OpenStack-Ansible "
|
|
"project, it has to meet the following minimum requirements:"
|
|
msgstr ""
|
|
"For a distribution to be considered supported by the OpenStack-Ansible "
|
|
"project, it has to meet the following minimum requirements:"
|
|
|
|
msgid ""
|
|
"For all the repos, update the eventual static files refering to master/"
|
|
"previous branch name. The main documentation should be updated to add the "
|
|
"new branch. The #openstack-docs team should also be updated, for linking the "
|
|
"newly created deployment-guide."
|
|
msgstr ""
|
|
"For all the repos, update the eventual static files referring to master/"
|
|
"previous branch name. The main documentation should be updated to add the "
|
|
"new branch. The #openstack-docs team should also be updated, for linking the "
|
|
"newly created deployment guide."
|
|
|
|
msgid ""
|
|
"For contributing code and documentation, you must follow the OpenStack "
|
|
"practices. Nothing special is required for OpenStack-Ansible."
|
|
msgstr ""
|
|
"For contributing code and documentation, you must follow the OpenStack "
|
|
"practices. Nothing special is required for OpenStack-Ansible."
|
|
|
|
msgid ""
|
|
"For general information on contributing to OpenStack, please check out the "
|
|
"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
|
|
"started. It covers all the basics that are common to all OpenStack projects: "
|
|
"the accounts you need, the basics of interacting with our Gerrit review "
|
|
"system, how we communicate as a community, etc."
|
|
msgstr ""
|
|
"For general information on contributing to OpenStack, please check out the "
|
|
"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
|
|
"started. It covers all the basics that are common to all OpenStack projects: "
|
|
"the accounts you need, the basics of interacting with our Gerrit review "
|
|
"system, how we communicate as a community, etc."
|
|
|
|
msgid ""
|
|
"For helping on or submitting bugs, you must have an account on ubuntu "
|
|
"Launchpad. All our repositories share the same `Launchpad project`_."
|
|
msgstr ""
|
|
"For helping on or submitting bugs, you must have an account on Ubuntu "
|
|
"Launchpad. All our repositories share the same `Launchpad project`_."
|
|
|
|
msgid ""
|
|
"For in-depth technical information, see the :dev_docs:`OpenStack-Ansible "
|
|
"Reference <reference/index.html>`."
|
|
msgstr ""
|
|
"For in-depth technical information, see the :dev_docs:`OpenStack-Ansible "
|
|
"Reference <reference/index.html>`."
|
|
|
|
msgid ""
|
|
"For information on how to deploy your OpenStack-Ansible cloud, refer to the :"
|
|
"deploy_guide:`Deployment Guide <index.html>` for step-by-step instructions "
|
|
"on how to deploy the OpenStack packages and dependencies on your cloud using "
|
|
"OpenStack-Ansible."
|
|
msgstr ""
|
|
"For information on how to deploy your OpenStack-Ansible cloud, refer to the :"
|
|
"deploy_guide:`Deployment Guide <index.html>` for step-by-step instructions "
|
|
"on how to deploy the OpenStack packages and dependencies on your cloud using "
|
|
"OpenStack-Ansible."
|
|
|
|
msgid ""
|
|
"For information on how to manage and operate OpenStack-Ansible, see the see "
|
|
"the :dev_docs:`Operations Guide <admin/index.html>`."
|
|
msgstr ""
|
|
"For information on how to manage and operate OpenStack-Ansible, see the see "
|
|
"the :dev_docs:`Operations Guide <admin/index.html>`."
|
|
|
|
msgid ""
|
|
"For sharing your user experience, stories, and helping other users, please "
|
|
"join us in our :ref:`IRC channel<irc>`."
|
|
msgstr ""
|
|
"For sharing your user experience, stories, and helping other users, please "
|
|
"join us in our :ref:`IRC channel<irc>`."
|
|
|
|
msgid "For user guides, see the :dev_docs:`User Guide <user/index.html>`."
|
|
msgstr "For user guides, see the :dev_docs:`User Guide <user/index.html>`."
|
|
|
|
msgid ""
|
|
"Freeze ansible-role-requirements to their latest SHAs for the branch they "
|
|
"are tracking."
|
|
msgstr ""
|
|
"Freeze ansible-role-requirements to their latest SHAs for the branch they "
|
|
"are tracking."
|
|
|
|
msgid "General Guidelines for Submitting Code"
|
|
msgstr "General Guidelines for Submitting Code"
|
|
|
|
msgid "General Responsibilities"
|
|
msgstr "General Responsibilities"
|
|
|
|
msgid ""
|
|
"Generate a meta/main.yml right away. This file is important to Ansible to "
|
|
"ensure your dependent roles are installed and available and provides others "
|
|
"with the information they will need to understand the purpose of your role."
|
|
msgstr ""
|
|
"Generate a meta/main.yml right away. This file is important to Ansible to "
|
|
"ensure your dependent roles are installed and available and provides others "
|
|
"with the information they will need to understand the purpose of your role."
|
|
|
|
msgid ""
|
|
"Generate files to include your service in the Ansible inventory using ``env."
|
|
"d`` and ``conf.d`` files for use on your deploy host."
|
|
msgstr ""
|
|
"Generate files to include your service in the Ansible inventory using ``env."
|
|
"d`` and ``conf.d`` files for use on your deploy host."
|
|
|
|
msgid ""
|
|
"Generate secrets, if any, as described in the :deploy_guide:`Configure "
|
|
"Service Credentials <configure.html#configuring-service-credentials>`. You "
|
|
"can append your keys to an existing ``user_secrets.yml`` file or add a new "
|
|
"file to the ``openstack_deploy`` directory to contain them. Provide "
|
|
"overrides for any other variables you will need at this time as well, either "
|
|
"in ``user_variables.yml`` or another file."
|
|
msgstr ""
|
|
"Generate secrets, if any, as described in the :deploy_guide:`Configure "
|
|
"Service Credentials <configure.html#configuring-service-credentials>`. You "
|
|
"can append your keys to an existing ``user_secrets.yml`` file or add a new "
|
|
"file to the ``openstack_deploy`` directory to contain them. Provide "
|
|
"overrides for any other variables you will need at this time as well, either "
|
|
"in ``user_variables.yml`` or another file."
|
|
|
|
msgid ""
|
|
"Generate the reference directory structure for an Ansible role which is the "
|
|
"necessary subset of the documented `Best Practice`_. You might use Ansible "
|
|
"Galaxy tools to do this for you (e.g. ``ansible-galaxy init``). You may "
|
|
"additionally want to include directories such as ``docs`` and ``examples`` "
|
|
"and ``tests`` for your role."
|
|
msgstr ""
|
|
"Generate the reference directory structure for an Ansible role which is the "
|
|
"necessary subset of the documented `Best Practice`_. You might use Ansible "
|
|
"Galaxy tools to do this for you (e.g. ``ansible-galaxy init``). You may "
|
|
"additionally want to include directories such as ``docs`` and ``examples`` "
|
|
"and ``tests`` for your role."
|
|
|
|
msgid "Getting Your Patch Merged"
|
|
msgstr "Getting Your Patch Merged"
|
|
|
|
msgid "Graduation"
|
|
msgstr "Graduation"
|
|
|
|
msgid "Handle OpenStack-Ansible roles deprecations from the previous cycle."
|
|
msgstr "Handle OpenStack-Ansible roles deprecations from the previous cycle."
|
|
|
|
msgid "Handle deprecations from upstream project's previous cycle."
|
|
msgstr "Handle deprecations from upstream project's previous cycle."
|
|
|
|
msgid ""
|
|
"Have you checked if your issue/feature request hasn't been solved in another "
|
|
"branch?"
|
|
msgstr ""
|
|
"Have you checked if your issue/feature request hasn't been solved in another "
|
|
"branch?"
|
|
|
|
msgid "Here are a few rules to get started:"
|
|
msgstr "Here are a few rules to get started:"
|
|
|
|
msgid "Here are a series of rules that define maturity levels:"
|
|
msgstr "Here are a series of rules that define maturity levels:"
|
|
|
|
msgid "Here are the steps to write the role:"
|
|
msgstr "Here are the steps to write the role:"
|
|
|
|
msgid "Here is a dashboard of the current status of the roles:"
|
|
msgstr "Here is a dashboard of the current status of the roles:"
|
|
|
|
msgid ""
|
|
"How do I handle dependencies to other bugs or TBD features in other "
|
|
"projects? For example, I can fix a bug in OpenStack-Ansible but I need that "
|
|
"a feature in Compute (nova) gets implemented before."
|
|
msgstr ""
|
|
"How do I handle dependencies to other bugs or TBD features in other "
|
|
"projects? For example, I can fix a bug in OpenStack-Ansible but I need that "
|
|
"a feature in Compute (Nova) gets implemented before."
|
|
|
|
msgid "How do I handle open bug reports which are Incomplete for too long?"
|
|
msgstr "How do I handle open bug reports which are Incomplete for too long?"
|
|
|
|
msgid "How to contribute on code or issues"
|
|
msgstr "How to contribute on code or issues"
|
|
|
|
msgid ""
|
|
"How to implement the right configuration to meet the needs of their specific "
|
|
"use-case."
|
|
msgstr ""
|
|
"How to implement the right configuration to meet the needs of their specific "
|
|
"use-case."
|
|
|
|
msgid "How to use the project's tooling effectively to deploy OpenStack."
|
|
msgstr "How to use the project's tooling effectively to deploy OpenStack."
|
|
|
|
msgid ""
|
|
"However, for reliability purposes, a few variables are defined to point to "
|
|
"the OpenStack infra pypi and packages mirrors."
|
|
msgstr ""
|
|
"However, for reliability purposes, a few variables are defined to point to "
|
|
"the OpenStack infra pypi and packages mirrors."
|
|
|
|
msgid ""
|
|
"However, to help you in the writing of the specification, we have a "
|
|
"`specification template`_ that can be copied into the latest release name "
|
|
"folder. Rename and edit it for your needs."
|
|
msgstr ""
|
|
"However, to help you in the writing of the specification, we have a "
|
|
"`specification template`_ that can be copied into the latest release name "
|
|
"folder. Rename and edit it for your needs."
|
|
|
|
msgid "IRC channel"
|
|
msgstr "IRC channel"
|
|
|
|
msgid ""
|
|
"Ideally, the functional tests for an OpenStack role should make use of "
|
|
"Tempest to execute the functional tests. The ideal tests to execute are "
|
|
"scenario tests as they test the functions that the service is expected to do "
|
|
"in a production deployment. In the absence of any scenario tests for the "
|
|
"service a fallback option is to implement the smoke tests instead."
|
|
msgstr ""
|
|
"Ideally, the functional tests for an OpenStack role should make use of "
|
|
"Tempest to execute the functional tests. The ideal tests to execute are "
|
|
"scenario tests as they test the functions that the service is expected to do "
|
|
"in a production deployment. In the absence of any scenario tests for the "
|
|
"service a fallback option is to implement the smoke tests instead."
|
|
|
|
msgid ""
|
|
"If a backport is a squashed set of cherry-picked commits, the original SHAs "
|
|
"should be referenced in the commit message and the reason for squashing the "
|
|
"commits should be clearly explained."
|
|
msgstr ""
|
|
"If a backport is a squashed set of cherry-picked commits, the original SHAs "
|
|
"should be referenced in the commit message and the reason for squashing the "
|
|
"commits should be clearly explained."
|
|
|
|
msgid ""
|
|
"If a role has failed periodics or gate test for two weeks, a bug should be "
|
|
"filed, and a message to the mailing list will be sent, referencing the bug."
|
|
msgstr ""
|
|
"If a role has failed periodically or gate test for two weeks, a bug should "
|
|
"be filed, and a message to the mailing list will be sent, referencing the "
|
|
"bug."
|
|
|
|
msgid ""
|
|
"If developing a new role, please follow the conventions set by existing "
|
|
"roles."
|
|
msgstr ""
|
|
"If developing a new role, please follow the conventions set by existing "
|
|
"roles."
|
|
|
|
msgid ""
|
|
"If it is in this state for more than 30 days and no answers to the open "
|
|
"questions are given, close it with Won't Fix."
|
|
msgstr ""
|
|
"If it is in this state for more than 30 days and no answers to the open "
|
|
"questions are given, close it with Won't Fix."
|
|
|
|
msgid ""
|
|
"If necessary, work on the integration within the openstack-ansible "
|
|
"integrated repository, and deploy the role on an AIO. See also :ref:"
|
|
"`integrate-new-role-with-aio`."
|
|
msgstr ""
|
|
"If necessary, work on the integration within the OpenStack-ansible "
|
|
"integrated repository, and deploy the role on an AIO. See also :ref:"
|
|
"`integrate-new-role-with-aio`."
|
|
|
|
msgid ""
|
|
"If no \"Wishlist\" item exist in Launchpad for your feature, create a bug "
|
|
"for it. Don't hesitate to ask if a spec is required in the bug."
|
|
msgstr ""
|
|
"If no \"Wishlist\" item exists in Launchpad for your feature, create a bug "
|
|
"for it. Don't hesitate to ask if a spec is required in the bug."
|
|
|
|
msgid ""
|
|
"If no tempest is provided, some other functional testing should be done. For "
|
|
"APIs, you can probably check the HTTP response codes, with specially crafted "
|
|
"requests."
|
|
msgstr ""
|
|
"If no tempest is provided, some other functional testing should be done. For "
|
|
"APIs, you can probably check the HTTP response codes, with specially crafted "
|
|
"requests."
|
|
|
|
msgid ""
|
|
"If required, ask the OpenStack-Ansible PTL to import the github role into "
|
|
"the openstack-ansible namespace (This can only be done early in the "
|
|
"development cycle, and may be postponed to next cycle)."
|
|
msgstr ""
|
|
"If required, ask the OpenStack-Ansible PTL to import the github role into "
|
|
"the OpenStack-ansible namespace (This can only be done early in the "
|
|
"development cycle, and may be postponed to next cycle)."
|
|
|
|
msgid ""
|
|
"If the bug affects a specific area covered by an official tag, you should "
|
|
"set the tag. For example, if the bug is likely to be quite easy to solve, "
|
|
"add the `low-hanging-fruit` tag."
|
|
msgstr ""
|
|
"If the bug affects a specific area covered by an official tag, you should "
|
|
"set the tag. For example, if the bug is likely to be quite easy to solve, "
|
|
"add the `low-hanging-fruit` tag."
|
|
|
|
msgid ""
|
|
"If the bug description is incomplete, or the report is lacking the "
|
|
"information necessary to reproduce the issue, ask the reporter to provide "
|
|
"missing information, and set the bug status to *Incomplete*"
|
|
msgstr ""
|
|
"If the bug description is incomplete, or the report is lacking the "
|
|
"information necessary to reproduce the issue, ask the reporter to provide "
|
|
"missing information, and set the bug status to *Incomplete*"
|
|
|
|
msgid ""
|
|
"If the bug has security implications, set the security flag (under \"This "
|
|
"report is public\" on the top right)"
|
|
msgstr ""
|
|
"If the bug has security implications, set the security flag (under \"This "
|
|
"report is public\" on the top right)"
|
|
|
|
msgid ""
|
|
"If the bug report contains enough information and you can reproduce it (or "
|
|
"it looks valid), then you should set its status to *Confirmed*."
|
|
msgstr ""
|
|
"If the bug report contains enough information and you can reproduce it (or "
|
|
"it looks valid), then you should set its status to *Confirmed*."
|
|
|
|
msgid ""
|
|
"If the issue is a bug that needs fixing in a branch other than master, "
|
|
"please note the associated branch within the launchpad issue."
|
|
msgstr ""
|
|
"If the issue is a bug that needs fixing in a branch other than master, "
|
|
"please note the associated branch within the launchpad issue."
|
|
|
|
msgid ""
|
|
"If the reported needs fixing in a branch in addition to master, add a "
|
|
"'\\<release\\>-backport-potential' tag (e.g. ``liberty-backport-"
|
|
"potential``). There are predefined tags that will auto-complete."
|
|
msgstr ""
|
|
"If the reported needs fixing in a branch in addition to master, add a "
|
|
"'\\<release\\>-backport-potential' tag (e.g. ``liberty-backport-"
|
|
"potential``). There are predefined tags that will auto-complete."
|
|
|
|
msgid ""
|
|
"If you adhere to the pattern of isolating your role's extra deployment "
|
|
"requirements (secrets and var files, HAProxy yml fragments, repo_package "
|
|
"files, etc.) in their own files it makes it easy for you to automate these "
|
|
"additional steps when testing your role."
|
|
msgstr ""
|
|
"If you adhere to the pattern of isolating your role's extra deployment "
|
|
"requirements (secrets and var files, HAProxy yml fragments, repo_package "
|
|
"files, etc.) in their own files it makes it easy for you to automate these "
|
|
"additional steps when testing your role."
|
|
|
|
msgid ""
|
|
"If you would like to contribute towards a role to introduce an OpenStack or "
|
|
"infrastructure service, or to improve an existing role, the OpenStack-"
|
|
"Ansible project would welcome that contribution and your assistance in "
|
|
"maintaining it."
|
|
msgstr ""
|
|
"If you would like to contribute towards a role to introduce an OpenStack or "
|
|
"infrastructure service, or to improve an existing role, the OpenStack-"
|
|
"Ansible project would welcome that contribution and your assistance in "
|
|
"maintaining it."
|
|
|
|
msgid ""
|
|
"If you're looking for some smaller, easier work item to pick up and get "
|
|
"started on, search for the 'low-hanging-fruit' tag."
|
|
msgstr ""
|
|
"If you're looking for some smaller, easier work item to pick up and get "
|
|
"started on, search for the 'low-hanging-fruit' tag."
|
|
|
|
msgid "If you're willing to submit code, please remember the following rules:"
|
|
msgstr "If you're willing to submit code, please remember the following rules:"
|
|
|
|
msgid ""
|
|
"If your service is installed from source or relies on python packages which "
|
|
"need to be installed from source, specify a repository for the source code "
|
|
"of each requirement by adding a file to your deploy host under ``playbooks/"
|
|
"defaults/repo_packages`` in the OpenStack-Ansible source repository and "
|
|
"following the pattern of files currently in that directory. You could also "
|
|
"simply add an entry to an existing file there. Be sure to run the ``repo-"
|
|
"build.yml`` play later so that wheels for your packages will be included in "
|
|
"the repository infrastructure."
|
|
msgstr ""
|
|
"If your service is installed from source or relies on python packages which "
|
|
"need to be installed from source, specify a repository for the source code "
|
|
"of each requirement by adding a file to your deploy host under ``playbooks/"
|
|
"defaults/repo_packages`` in the OpenStack-Ansible source repository and "
|
|
"following the pattern of files currently in that directory. You could also "
|
|
"simply add an entry to an existing file there. Be sure to run the ``repo-"
|
|
"build.yml`` play later so that wheels for your packages will be included in "
|
|
"the repository infrastructure."
|
|
|
|
msgid "Immediately after official OpenStack-Ansible release:"
|
|
msgstr "Immediately after official OpenStack-Ansible release:"
|
|
|
|
msgid ""
|
|
"Implement **developer_mode** to build from a git source into a Python "
|
|
"virtual environment."
|
|
msgstr ""
|
|
"Implement **developer_mode** to build from a git source into a Python "
|
|
"virtual environment."
|
|
|
|
msgid "Implement features"
|
|
msgstr "Implement features"
|
|
|
|
msgid "Importance"
|
|
msgstr "Importance"
|
|
|
|
msgid "Improve testing with tempest"
|
|
msgstr "Improve testing with Tempest"
|
|
|
|
msgid "In essence, core reviewers share the following common ideals:"
|
|
msgstr "In essence, core reviewers share the following common ideals:"
|
|
|
|
msgid ""
|
|
"In most cases only the following sections should be used for new release "
|
|
"notes submitted with patches:"
|
|
msgstr ""
|
|
"In most cases only the following sections should be used for new release "
|
|
"notes submitted with patches:"
|
|
|
|
msgid ""
|
|
"In other words, `defaults/main.yml` contains variables that are meant to be "
|
|
"overridable by a deployer or a continuous integration system. These "
|
|
"variables should be limited as much as possible, to avoid increasing the "
|
|
"test matrix."
|
|
msgstr ""
|
|
"In other words, `defaults/main.yml` contains variables that are meant to be "
|
|
"overridable by a deployer or a continuous integration system. These "
|
|
"variables should be limited as much as possible, to avoid increasing the "
|
|
"test matrix."
|
|
|
|
msgid ""
|
|
"In this section, you will find documentation relevant to developing "
|
|
"OpenStack-Ansible."
|
|
msgstr ""
|
|
"In this section, you will find documentation relevant to developing "
|
|
"OpenStack-Ansible."
|
|
|
|
msgid "Include historical information on how the problem was identified."
|
|
msgstr "Include historical information on how the problem was identified."
|
|
|
|
msgid "Include your role on the deploy host. See also :ref:`extend_osa_roles`."
|
|
msgstr ""
|
|
"Include your role on the deploy host. See also :ref:`extend_osa_roles`."
|
|
|
|
msgid ""
|
|
"Instead, the new code has to be isolated on a separate folder of the "
|
|
"`openstack-ansible-ops repo`_."
|
|
msgstr ""
|
|
"Instead, the new code has to be isolated on a separate folder of the "
|
|
"`openstack-ansible-ops repo`_."
|
|
|
|
msgid "Integrated repo functional or scenario testing"
|
|
msgstr "Integrated repo functional or scenario testing"
|
|
|
|
msgid "Interfacing with other OpenStack teams"
|
|
msgstr "Interfacing with other OpenStack teams"
|
|
|
|
msgid ""
|
|
"Is there a bug for it? Can your track if someone else has seen the same bug?"
|
|
msgstr ""
|
|
"Is there a bug for it? Can your track if someone else has seen the same bug?"
|
|
|
|
msgid ""
|
|
"It allows us to not repeat ourselves: it is the location of common "
|
|
"playbooks, common tasks and scripts."
|
|
msgstr ""
|
|
"It allows us to not repeat ourselves: it is the location of common "
|
|
"playbooks, common tasks and scripts."
|
|
|
|
msgid ""
|
|
"It must be possible to execute a functional, integrated test which executes "
|
|
"a deployment in the same way as a production environment. The test must "
|
|
"execute a set of functional tests using Tempest. This is the required last "
|
|
"step before a service can remove the experimental warning from the "
|
|
"documentation."
|
|
msgstr ""
|
|
"It must be possible to execute a functional, integrated test which executes "
|
|
"a deployment in the same way as a production environment. The test must "
|
|
"execute a set of functional tests using Tempest. This is the required last "
|
|
"step before a service can remove the experimental warning from the "
|
|
"documentation."
|
|
|
|
msgid ""
|
|
"Leave a comment in the OpenStack-Ansible bug report which explains this "
|
|
"dependency and leave a link to the blueprint or bug report of the other "
|
|
"project you depend on."
|
|
msgstr ""
|
|
"Leave a comment in the OpenStack-Ansible bug report which explains this "
|
|
"dependency and leave a link to the blueprint or bug report of the other "
|
|
"project you depend on."
|
|
|
|
msgid "Linting"
|
|
msgstr "Linting"
|
|
|
|
msgid "Mailing lists"
|
|
msgstr "Mailing lists"
|
|
|
|
msgid "Maintaining accurate, complete, and relevant documentation"
|
|
msgstr "Maintaining accurate, complete, and relevant documentation"
|
|
|
|
msgid ""
|
|
"Make any required adjustments to the load balancer configuration (e.g. "
|
|
"modify ``inventory/group_vars/all/haproxy.yml`` in the OpenStack-Ansible "
|
|
"source repository on your deploy host) so that your service can be reached "
|
|
"through a load balancer, if appropriate, and be sure to run the ``haproxy-"
|
|
"install.yml`` play later so your changes will be applied. Please note, you "
|
|
"can also use ``haproxy_extra_services`` variable if you don't want to "
|
|
"provide your service as default for everyone."
|
|
msgstr ""
|
|
"Make any required adjustments to the load balancer configuration (e.g. "
|
|
"modify ``inventory/group_vars/all/haproxy.yml`` in the OpenStack-Ansible "
|
|
"source repository on your deploy host) so that your service can be reached "
|
|
"through a load balancer, if appropriate, and be sure to run the ``haproxy-"
|
|
"install.yml`` play later so your changes will be applied. Please note, you "
|
|
"can also use ``haproxy_extra_services`` variable if you don't want to "
|
|
"provide your service as default for everyone."
|
|
|
|
msgid ""
|
|
"Master doesn't get frozen, unless explicitly asked for it for release "
|
|
"milestones, using the command ``osa releases freeze_roles_for_milestone``"
|
|
msgstr ""
|
|
"Master doesn't get frozen, unless explicitly asked for it for release "
|
|
"milestones, using the command ``osa releases freeze_roles_for_milestone``"
|
|
|
|
msgid "Maturity Matrix"
|
|
msgstr "Maturity Matrix"
|
|
|
|
msgid "Maturity downgrade procedure"
|
|
msgstr "Maturity downgrade procedure"
|
|
|
|
msgid ""
|
|
"Members of the OpenStack-Ansible community should monitor the **OpenStack-"
|
|
"discuss** `mailing lists`_."
|
|
msgstr ""
|
|
"Members of the OpenStack-Ansible community should monitor the **OpenStack-"
|
|
"discuss** `mailing lists`_."
|
|
|
|
msgid "Members of the core reviewer team are expected to:"
|
|
msgstr "Members of the core reviewer team are expected to:"
|
|
|
|
msgid ""
|
|
"Mentor community contributors in solution design, testing, and the review "
|
|
"process"
|
|
msgstr ""
|
|
"Mentor community contributors in solution design, testing, and the review "
|
|
"process"
|
|
|
|
msgid "Minimum requirements for OpenStack-Ansible roles"
|
|
msgstr "Minimum requirements for OpenStack-Ansible roles"
|
|
|
|
msgid "Minimum supported distributions"
|
|
msgstr "Minimum supported distributions"
|
|
|
|
msgid ""
|
|
"Modify the tox.ini to add your new scenario. If required, you can override "
|
|
"the inventory, and/or the variable files."
|
|
msgstr ""
|
|
"Modify the tox.ini to add your new scenario. If required, you can override "
|
|
"the inventory, and/or the variable files."
|
|
|
|
msgid ""
|
|
"Monitor and participate in OpenStack-Ansible discussions on the mailing list"
|
|
msgstr ""
|
|
"Monitor and participate in OpenStack-Ansible discussions on the mailing list"
|
|
|
|
msgid "Monitor and participate in-channel at #openstack-ansible"
|
|
msgstr "Monitor and participate in-channel at #openstack-ansible"
|
|
|
|
msgid ""
|
|
"Most OpenStack services will follow a common series of stages to install, "
|
|
"configure, or update a service deployment. This is apparent when you review "
|
|
"`tasks/main.yml` for existing roles."
|
|
msgstr ""
|
|
"Most OpenStack services will follow a common series of stages to install, "
|
|
"configure, or update a service deployment. This is apparent when you review "
|
|
"`tasks/main.yml` for existing roles."
|
|
|
|
msgid ""
|
|
"Move bugs that can not be reproduced to an invalid state if they are "
|
|
"unmodified for more than a month."
|
|
msgstr ""
|
|
"Move bugs that can not be reproduced to an invalid state if they are "
|
|
"unmodified for more than a month."
|
|
|
|
msgid ""
|
|
"Move year old `wishlist bugs`_ to Opinion/Wishlist to remove clutter. You "
|
|
"can use the following message:"
|
|
msgstr ""
|
|
"Move year old `wishlist bugs`_ to Opinion/Wishlist to remove clutter. You "
|
|
"can use the following message:"
|
|
|
|
msgid "New Feature Planning"
|
|
msgstr "New Feature Planning"
|
|
|
|
msgid ""
|
|
"New features are following a process, explained in the section :ref:"
|
|
"`newfeatures`. New features are less likely to be :ref:"
|
|
"`backported<backport>` to previous branches."
|
|
msgstr ""
|
|
"New features are following a process, explained in the section :ref:"
|
|
"`newfeatures`. New features are less likely to be :ref:"
|
|
"`backported<backport>` to previous branches."
|
|
|
|
msgid ""
|
|
"New features, breaking changes and other patches of note must include a "
|
|
"release note generated using `the reno tool`_. Please see the :ref:"
|
|
"`Documentation and Release Note Guidelines<documentation>` for more "
|
|
"information."
|
|
msgstr ""
|
|
"New features, breaking changes and other patches of note must include a "
|
|
"release note generated using `the reno tool`_. Please see the :ref:"
|
|
"`Documentation and Release Note Guidelines<documentation>` for more "
|
|
"information."
|
|
|
|
msgid ""
|
|
"No. Sometimes it is not even possible because you do not have the resources. "
|
|
"Looking at the code and tests often enables you to make an educated guess. "
|
|
"Citing your sources in a comment helps the discussion."
|
|
msgstr ""
|
|
"No. Sometimes it is not even possible because you do not have the resources. "
|
|
"Looking at the code and tests often enables you to make an educated guess. "
|
|
"Citing your sources in a comment helps the discussion."
|
|
|
|
msgid ""
|
|
"Now, all the functions are separated, and included into a branch independent "
|
|
"tooling, `osa_cli_releases`."
|
|
msgstr ""
|
|
"Now, all the functions are separated, and included into a branch independent "
|
|
"tooling, `osa_cli_releases`."
|
|
|
|
msgid "OSA CLI tooling"
|
|
msgstr "OSA CLI tooling"
|
|
|
|
msgid ""
|
|
"On top of the normal cycle goals, a contributor can help the OpenStack-"
|
|
"Ansible development team by performing one of the following recurring tasks:"
|
|
msgstr ""
|
|
"On top of the normal cycle goals, a contributor can help the OpenStack-"
|
|
"Ansible development team by performing one of the following recurring tasks:"
|
|
|
|
msgid ""
|
|
"Once the blueprint work is completed the author(s) can request a backport of "
|
|
"the blueprint work into a stable branch. Each backport will be evaluated on "
|
|
"a case by case basis with cautious consideration based on how the backport "
|
|
"affects any existing deployments. See the :ref:`backport` section for more "
|
|
"information."
|
|
msgstr ""
|
|
"Once the blueprint work is completed the author(s) can request a backport of "
|
|
"the blueprint work into a stable branch. Each backport will be evaluated on "
|
|
"a case by case basis with cautious consideration based on how the backport "
|
|
"affects any existing deployments. See the :ref:`backport` section for more "
|
|
"information."
|
|
|
|
msgid ""
|
|
"Once the initial convergence is working and the services are running, the "
|
|
"role development should focus on implementing some level of functional "
|
|
"testing."
|
|
msgstr ""
|
|
"Once the initial convergence is working and the services are running, the "
|
|
"role development should focus on implementing some level of functional "
|
|
"testing."
|
|
|
|
msgid ""
|
|
"Once the initial convergence is working and the services are running, the "
|
|
"role development should focus on implementing some level of functional "
|
|
"testing. See also :ref:`tempest-testing`."
|
|
msgstr ""
|
|
"Once the initial convergence is working and the services are running, the "
|
|
"role development should focus on implementing some level of functional "
|
|
"testing. See also :ref:`tempest-testing`."
|
|
|
|
msgid ""
|
|
"Only add a ``zuul.d`` folder when your role is imported into the openstack-"
|
|
"ansible namespace."
|
|
msgstr ""
|
|
"Only add a ``zuul.d`` folder when your role is imported into the OpenStack-"
|
|
"Ansible namespace."
|
|
|
|
msgid "OpenStack-Ansible Bug Handling"
|
|
msgstr "OpenStack-Ansible Bug Handling"
|
|
|
|
msgid ""
|
|
"OpenStack-Ansible has multiple forms of documentation with different intent."
|
|
msgstr ""
|
|
"OpenStack-Ansible has multiple forms of documentation with different intent."
|
|
|
|
msgid ""
|
|
"OpenStack-Ansible is not re-inventing the wheel, and tries to reuse as much "
|
|
"as possible existing roles. A bugfix for one of those repositories must be "
|
|
"handled to these repositories' maintainers."
|
|
msgstr ""
|
|
"OpenStack-Ansible is not re-inventing the wheel, and tries to reuse as much "
|
|
"as possible existing roles. A bugfix for one of those repositories must be "
|
|
"handled to these repositories' maintainers."
|
|
|
|
msgid ""
|
|
"OpenStack-Ansible used to bump everything in a single script, which made it "
|
|
"hard to maintain, and was very branch specific. It made it hard for users to "
|
|
"consume either an update of the upstream shas, or to bump roles with their "
|
|
"own pace."
|
|
msgstr ""
|
|
"OpenStack-Ansible used to bump everything in a single script, which made it "
|
|
"hard to maintain, and was very branch specific. It made it hard for users to "
|
|
"consume either an update of the upstream SHAs, or to bump roles with their "
|
|
"own pace."
|
|
|
|
msgid "Other OpenStack-Ansible conventions"
|
|
msgstr "Other OpenStack-Ansible conventions"
|
|
|
|
msgid "Our main repository, used by deployers. Uses the other repositories."
|
|
msgstr "Our main repository, used by deployers. Uses the other repositories."
|
|
|
|
msgid "Our release frequency is discussed in :ref:`reference_release`."
|
|
msgstr "Our release frequency is discussed in :ref:`reference_release`."
|
|
|
|
msgid ""
|
|
"Our specifications repository follows the usual OpenStack and OpenStack-"
|
|
"Ansible guidelines for submitting code."
|
|
msgstr ""
|
|
"Our specifications repository follows the usual OpenStack and OpenStack-"
|
|
"Ansible guidelines for submitting code."
|
|
|
|
msgid "Participate in Forum sessions at the OpenStack Summits"
|
|
msgstr "Participate in Forum sessions at the OpenStack Summits"
|
|
|
|
msgid ""
|
|
"Participate in team sessions at the OpenStack Projects Team Gatherings (PTG)"
|
|
msgstr ""
|
|
"Participate in team sessions at the OpenStack Projects Team Gatherings (PTG)"
|
|
|
|
msgid "Pass functional tests"
|
|
msgstr "Pass functional tests"
|
|
|
|
msgid ""
|
|
"Patches should be focused on solving one problem at a time. If the review is "
|
|
"overly complex or generally large the initial commit will receive a \"**-2**"
|
|
"\" and the contributor will be asked to split the patch up across multiple "
|
|
"reviews. In the case of complex feature additions the design and "
|
|
"implementation of the feature should be done in such a way that it can be "
|
|
"submitted in multiple patches using dependencies. Using dependent changes "
|
|
"should always aim to result in a working build throughout the dependency "
|
|
"chain. Documentation is available for `advanced gerrit usage`_ too."
|
|
msgstr ""
|
|
"Patches should be focused on solving one problem at a time. If the review is "
|
|
"overly complex or generally large the initial commit will receive a \"**-2**"
|
|
"\" and the contributor will be asked to split the patch up across multiple "
|
|
"reviews. In the case of complex feature additions the design and "
|
|
"implementation of the feature should be done in such a way that it can be "
|
|
"submitted in multiple patches using dependencies. Using dependent changes "
|
|
"should always aim to result in a working build throughout the dependency "
|
|
"chain. Documentation is available for `advanced gerrit usage`_ too."
|
|
|
|
msgid ""
|
|
"Perform any other host preparation (such as the tasks performed by the "
|
|
"``bootstrap-aio.yml`` playbook). This includes any preparation tasks that "
|
|
"are particular to your service."
|
|
msgstr ""
|
|
"Perform any other host preparation (such as the tasks performed by the "
|
|
"``bootstrap-aio.yml`` playbook). This includes any preparation tasks that "
|
|
"are particular to your service."
|
|
|
|
msgid "Periodic Work"
|
|
msgstr "Periodic Work"
|
|
|
|
msgid ""
|
|
"Please be aware that any patch can be refused by the community if they don't "
|
|
"match the :ref:`codeguidelines`."
|
|
msgstr ""
|
|
"Please be aware that any patch can be refused by the community if they don't "
|
|
"match the :ref:`codeguidelines`."
|
|
|
|
msgid ""
|
|
"Please check our :ref:`bug report<bug_reporting>` and :ref:`bug "
|
|
"triage<bug_triage>` processes."
|
|
msgstr ""
|
|
"Please check our :ref:`bug report<bug_reporting>` and :ref:`bug "
|
|
"triage<bug_triage>` processes."
|
|
|
|
msgid ""
|
|
"Please have a look at a role like os_cinder, os_keystone, or os_neutron for "
|
|
"latest files."
|
|
msgstr ""
|
|
"Please have a look at a role like os_cinder, os_keystone, or os_neutron for "
|
|
"latest files."
|
|
|
|
msgid ""
|
|
"Please leave the **status** of an issue alone until someone confirms it or a "
|
|
"member of the bugs team triages it. While waiting for the issue to be "
|
|
"confirmed or triaged the status should remain as **New**."
|
|
msgstr ""
|
|
"Please leave the **status** of an issue alone until someone confirms it or a "
|
|
"member of the bugs team triages it. While waiting for the issue to be "
|
|
"confirmed or triaged the status should remain as **New**."
|
|
|
|
msgid ""
|
|
"Please look through :dev_docs:`Contributor Guidelines <contributor/"
|
|
"contribute.html>` page for more information about the process."
|
|
msgstr ""
|
|
"Please look through :dev_docs:`Contributor Guidelines <contributor/"
|
|
"contribute.html>` page for more information about the process."
|
|
|
|
msgid ""
|
|
"Please note in-person attendance at PTG, Summit, mid-cycles, and other code "
|
|
"sprints is not a requirement to be a core reviewer. The team will do its "
|
|
"best to facilitate virtual attendance at all events. Travel is not to be "
|
|
"taken lightly, and we realize the costs involved for those who attend these "
|
|
"events."
|
|
msgstr ""
|
|
"Please note in-person attendance at PTG, Summit, mid-cycles, and other code "
|
|
"sprints is not a requirement to be a core reviewer. The team will do its "
|
|
"best to facilitate virtual attendance at all events. Travel is not to be "
|
|
"taken lightly, and we realise the costs involved for those who attend these "
|
|
"events."
|
|
|
|
msgid ""
|
|
"Please note that branches before Stein will require cleanup of the YAML file "
|
|
"generated by new_releases, as it will contain ALL the roles and openstack-"
|
|
"ansible repo SHAs. We have decided to NOT tag the roles anymore, so you will "
|
|
"need to remove all the lines which are not relevant to the `openstack-"
|
|
"ansible` repository."
|
|
msgstr ""
|
|
"Please note that branches before Stein will require cleanup of the YAML file "
|
|
"generated by new_releases, as it will contain ALL the roles and OpenStack-"
|
|
"Ansible repo SHAs. We have decided to NOT tag the roles anymore, so you will "
|
|
"need to remove all the lines which are not relevant to the `openstack-"
|
|
"ansible` repository."
|
|
|
|
msgid ""
|
|
"Please reference the `Project Team Guide bugs reference_` for information "
|
|
"about bug status/importance and the life cycle of a bug."
|
|
msgstr ""
|
|
"Please reference the `Project Team Guide bugs reference_` for information "
|
|
"about bug status/importance and the life cycle of a bug."
|
|
|
|
msgid "Prioritize or reprioritize OpenStack-Ansible `confirmed bugs`_."
|
|
msgstr "Prioritize or reprioritise OpenStack-Ansible `confirmed bugs`_."
|
|
|
|
msgid "Project Onboarding"
|
|
msgstr "Project Onboarding"
|
|
|
|
msgid "Project Team Lead Duties"
|
|
msgstr "Project Team Lead Duties"
|
|
|
|
msgid "Project repositories"
|
|
msgstr "Project repositories"
|
|
|
|
msgid ""
|
|
"Pull requests submitted through GitHub will be ignored and closed without "
|
|
"regard."
|
|
msgstr ""
|
|
"Pull requests submitted through GitHub will be ignored and closed without "
|
|
"regard."
|
|
|
|
msgid ""
|
|
"Put together a service install playbook file for your role. This can also be "
|
|
"modeled from any existing service playbook that has similar dependencies to "
|
|
"your service (database, messaging, storage drivers, container mount points, "
|
|
"etc.). A common place to keep playbook files in a Galaxy role is in an "
|
|
"``examples`` directory off the root of the role. If the playbook is meant "
|
|
"for installing an OpenStack service, name it ``os-<service>-install.yml`` "
|
|
"and target it at the appropriate group defined in the service ``env.d`` "
|
|
"file. It is crucial that the implementation of the service is optional and "
|
|
"that the deployer must opt-in to the deployment through the population of a "
|
|
"host in the applicable host group. If the host group has no hosts, Ansible "
|
|
"skips the playbook's tasks automatically."
|
|
msgstr ""
|
|
"Put together a service install playbook file for your role. This can also be "
|
|
"modelled from any existing service playbook that has similar dependencies to "
|
|
"your service (database, messaging, storage drivers, container mount points, "
|
|
"etc.). A common place to keep playbook files in a Galaxy role is in an "
|
|
"``examples`` directory off the root of the role. If the playbook is meant "
|
|
"for installing an OpenStack service, name it ``os-<service>-install.yml`` "
|
|
"and target it at the appropriate group defined in the service ``env.d`` "
|
|
"file. It is crucial that the implementation of the service is optional and "
|
|
"that the deployer must opt-in to the deployment through the population of a "
|
|
"host in the applicable host group. If the host group has no hosts, Ansible "
|
|
"skips the playbook's tasks automatically."
|
|
|
|
msgid ""
|
|
"Python coding conventions are tested using `PEP8`_, with the following "
|
|
"convention exceptions:"
|
|
msgstr ""
|
|
"Python coding conventions are tested using `PEP8`_, with the following "
|
|
"convention exceptions:"
|
|
|
|
msgid "Q"
|
|
msgstr "Q"
|
|
|
|
msgid "RST formatting conventions"
|
|
msgstr "RST formatting conventions"
|
|
|
|
msgid "Refactoring work must not be backported to a \"released\" branch."
|
|
msgstr "Refactoring work must not be backported to a \"released\" branch."
|
|
|
|
msgid ""
|
|
"Refactoring work should never include additional \"rider\" features. "
|
|
"Features that may pertain to something that was re-factored should be raised "
|
|
"as an issue and submitted in prior or subsequent patches."
|
|
msgstr ""
|
|
"Refactoring work should never include additional \"rider\" features. "
|
|
"Features that may pertain to something that was re-factored should be raised "
|
|
"as an issue and submitted in prior or subsequent patches."
|
|
|
|
msgid ""
|
|
"Refresh static elements in roles. For example, update a specific version of "
|
|
"the software packages."
|
|
msgstr ""
|
|
"Refresh static elements in roles. For example, update a specific version of "
|
|
"the software packages."
|
|
|
|
msgid "Related-Bug: #bugnumber"
|
|
msgstr "Related-Bug: #bugnumber"
|
|
|
|
msgid "Release Notes"
|
|
msgstr "Release Notes"
|
|
|
|
msgid ""
|
|
"Release notes are generated using `the reno tool`_. Release notes must be "
|
|
"written with the following guidelines in mind:"
|
|
msgstr ""
|
|
"Release notes are generated using `the reno tool`_. Release notes must be "
|
|
"written with the following guidelines in mind:"
|
|
|
|
msgid ""
|
|
"Release notes are generated using the `the reno tool`_ and compiled into "
|
|
"HTML using Sphinx."
|
|
msgstr ""
|
|
"Release notes are generated using the `the reno tool`_ and compiled into "
|
|
"HTML using Sphinx."
|
|
|
|
msgid "Release notes building"
|
|
msgstr "Release notes building"
|
|
|
|
msgid "Release notes may be built locally by executing:"
|
|
msgstr "Release notes may be built locally by executing:"
|
|
|
|
msgid "Releasing"
|
|
msgstr "Releasing"
|
|
|
|
msgid ""
|
|
"Reported bugs need confirmation, prioritization, and ensure they do not go "
|
|
"stale. If you care about OpenStack stability but are not wanting to actively "
|
|
"develop the roles and playbooks used within the OpenStack-Ansible project, "
|
|
"consider contributing in the area of bug triage."
|
|
msgstr ""
|
|
"Reported bugs need confirmation, prioritisation, and ensure they do not go "
|
|
"stale. If you care about OpenStack stability but are not wanting to actively "
|
|
"develop the roles and playbooks used within the OpenStack-Ansible project, "
|
|
"consider contributing in the area of bug triage."
|
|
|
|
msgid "Reporting a Bug"
|
|
msgstr "Reporting a Bug"
|
|
|
|
msgid "Repository purpose"
|
|
msgstr "Repository purpose"
|
|
|
|
msgid "Repository type or name"
|
|
msgstr "Repository type or name"
|
|
|
|
msgid "Review patch submissions actively and consistently"
|
|
msgstr "Review patch submissions actively and consistently"
|
|
|
|
msgid "Review process"
|
|
msgstr "Review process"
|
|
|
|
msgid "Role development maturity"
|
|
msgstr "Role development maturity"
|
|
|
|
msgid "Roles functional or scenario testing"
|
|
msgstr "Roles functional or scenario testing"
|
|
|
|
msgid "Running tests locally"
|
|
msgstr "Running tests locally"
|
|
|
|
msgid ""
|
|
"Search for in the `OpenStack-Ansible Launchpad project`_ for the feature "
|
|
"request."
|
|
msgstr ""
|
|
"Search for in the `OpenStack-Ansible Launchpad project`_ for the feature "
|
|
"request."
|
|
|
|
msgid "Secrets"
|
|
msgstr "Secrets"
|
|
|
|
msgid "See also our :ref:`user-overrides` page."
|
|
msgstr "See also our :ref:`user-overrides` page."
|
|
|
|
msgid ""
|
|
"See also the `OpenStack developers getting started page`_. and our :ref:"
|
|
"`contributor guidelines<contributing>` before hacking."
|
|
msgstr ""
|
|
"See also the `OpenStack developers getting started page`_. and our :ref:"
|
|
"`contributor guidelines<contributing>` before hacking."
|
|
|
|
msgid "See also the `working on bugs`_ section of the openstack documentation."
|
|
msgstr ""
|
|
"See also the `working on bugs`_ section of the OpenStack documentation."
|
|
|
|
msgid "See also the `zuul user guide`_."
|
|
msgstr "See also the `zuul user guide`_."
|
|
|
|
msgid "See our :ref:`supported-distros` page."
|
|
msgstr "See our :ref:`supported-distros` page."
|
|
|
|
msgid ""
|
|
"Send a thank you note to all the contributors through the mailing lists. "
|
|
"They deserve it."
|
|
msgstr ""
|
|
"Send a thank you note to all the contributors through the mailing lists. "
|
|
"They deserve it."
|
|
|
|
msgid ""
|
|
"Send an email to the openstack-discuss list with the `list of bugs to "
|
|
"triage`_ during the week. A new bug marked as *Critical* or *High* must be "
|
|
"treated in priority."
|
|
msgstr ""
|
|
"Send an email to the openstack-discuss list with the `list of bugs to "
|
|
"triage`_ during the week. A new bug marked as *Critical* or *High* must be "
|
|
"treated in priority."
|
|
|
|
msgid ""
|
|
"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. Once the importance has been changed the status "
|
|
"should be changed to **Triaged** by someone other than the bug creator."
|
|
msgstr ""
|
|
"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. Once the importance has been changed the status "
|
|
"should be changed to **Triaged** by someone other than the bug creator."
|
|
|
|
msgid ""
|
|
"Since then, the OpenStack-Ansible has agreed to provide more metadata "
|
|
"necessary for releasing into the openstack-ansible code tree. This allowed "
|
|
"the tooling for releasing to be more flexible, and lighter, over time."
|
|
msgstr ""
|
|
"Since then, the OpenStack-Ansible has agreed to provide more metadata "
|
|
"necessary for releasing into the OpenStack-Ansible code tree. This allowed "
|
|
"the tooling for releasing to be more flexible, and lighter, over time."
|
|
|
|
msgid "So You Want to Contribute..."
|
|
msgstr "So You Want to Contribute..."
|
|
|
|
msgid "Some roles have extra tests, like neutron, defined in ``tox.ini``."
|
|
msgstr "Some roles have extra tests, like neutron, defined in ``tox.ini``."
|
|
|
|
msgid "Status"
|
|
msgstr "Status"
|
|
|
|
msgid "Steps to reproduce the problem if possible."
|
|
msgstr "Steps to reproduce the problem if possible."
|
|
|
|
msgid ""
|
|
"Submit your code for review, with its necessary documentation and release "
|
|
"notes."
|
|
msgstr ""
|
|
"Submit your code for review, with its necessary documentation and release "
|
|
"notes."
|
|
|
|
msgid "Submit your role for review."
|
|
msgstr "Submit your role for review."
|
|
|
|
msgid "Submitting a specification"
|
|
msgstr "Submitting a specification"
|
|
|
|
msgid "Supported distributions"
|
|
msgstr "Supported distributions"
|
|
|
|
msgid "Tags and tags conventions"
|
|
msgstr "Tags and tags conventions"
|
|
|
|
msgid ""
|
|
"Tags are assigned based on the relevance of each individual item. Higher "
|
|
"level includes (for example in the ``tasks/main.yml``) need high level tags. "
|
|
"For example, ``*-config`` or ``*-install``. Included tasks can have more "
|
|
"detailed tags."
|
|
msgstr ""
|
|
"Tags are assigned based on the relevance of each individual item. Higher "
|
|
"level includes (for example in the ``tasks/main.yml``) need high level tags. "
|
|
"For example, ``*-config`` or ``*-install``. Included tasks can have more "
|
|
"detailed tags."
|
|
|
|
msgid "Task Tracking"
|
|
msgstr "Task Tracking"
|
|
|
|
msgid "Task files conventions"
|
|
msgstr "Task files conventions"
|
|
|
|
msgid "Test the role on a new machine, using our provided scripts."
|
|
msgstr "Test the role on a new machine, using our provided scripts."
|
|
|
|
msgid ""
|
|
"Test your new scenario with a new machine. See also the :ref:"
|
|
"`devel_and_testing` page."
|
|
msgstr ""
|
|
"Test your new scenario with a new machine. See also the :ref:"
|
|
"`devel_and_testing` page."
|
|
|
|
msgid "Testing"
|
|
msgstr "Testing"
|
|
|
|
msgid "Testing a new role with an AIO"
|
|
msgstr "Testing a new role with an AIO"
|
|
|
|
msgid "Testing may be done locally by executing:"
|
|
msgstr "Testing may be done locally by executing:"
|
|
|
|
msgid "Tests conventions"
|
|
msgstr "Tests conventions"
|
|
|
|
msgid "The **OpenStack-Ansible roles** repositories"
|
|
msgstr "The **OpenStack-Ansible roles** repositories"
|
|
|
|
msgid "The **ops** repository"
|
|
msgstr "The **ops** repository"
|
|
|
|
msgid "The **specs** repository"
|
|
msgstr "The **specs** repository"
|
|
|
|
msgid "The **tests repository**"
|
|
msgstr "The **tests repository**"
|
|
|
|
msgid ""
|
|
"The :deploy_guide:`Deployment Guide <index.html>` intends to help deployers "
|
|
"deploy OpenStack-Ansible for the first time."
|
|
msgstr ""
|
|
"The :deploy_guide:`Deployment Guide <index.html>` intends to help deployers "
|
|
"deploy OpenStack-Ansible for the first time."
|
|
|
|
msgid ""
|
|
"The :dev_docs:`Operations Guide <admin/index.html>` provide help on how to "
|
|
"manage and operate OpenStack-Ansible."
|
|
msgstr ""
|
|
"The :dev_docs:`Operations Guide <admin/index.html>` provide help on how to "
|
|
"manage and operate OpenStack-Ansible."
|
|
|
|
msgid ""
|
|
"The :dev_docs:`User Guide <user/index.html>` intends to provide user stories "
|
|
"on how to do specific things with OpenStack-Ansible."
|
|
msgstr ""
|
|
"The :dev_docs:`User Guide <user/index.html>` intends to provide user stories "
|
|
"on how to do specific things with OpenStack-Ansible."
|
|
|
|
msgid ""
|
|
"The :ref:`bug_triage` will classify if this new feature requires a spec or "
|
|
"not."
|
|
msgstr ""
|
|
"The :ref:`bug_triage` will classify if this new feature requires a spec or "
|
|
"not."
|
|
|
|
msgid ""
|
|
"The OpenStack Community moved the IRC network from Freenode to OFTC on May "
|
|
"31, 2021. All the current IRC channels used in The OpenStack community are "
|
|
"registered in OFTC network too."
|
|
msgstr ""
|
|
"The OpenStack Community moved the IRC network from Freenode to OFTC on May "
|
|
"31, 2021. All the current IRC channels used in The OpenStack community are "
|
|
"registered in OFTC network too."
|
|
|
|
msgid "The OpenStack Infrastructure automated tests"
|
|
msgstr "The OpenStack Infrastructure automated tests"
|
|
|
|
msgid ""
|
|
"The OpenStack-Ansible community communicates a lot through IRC, in the "
|
|
"#openstack-ansible channel, on OFTC. This channel is logged, and its logs "
|
|
"are published on http://eavesdrop.openstack.org/irclogs/%23openstack-"
|
|
"ansible/."
|
|
msgstr ""
|
|
"The OpenStack-Ansible community communicates a lot through IRC, in the "
|
|
"#openstack-ansible channel, on OFTC. This channel is logged, and its logs "
|
|
"are published on http://eavesdrop.openstack.org/irclogs/%23openstack-"
|
|
"ansible/."
|
|
|
|
msgid ""
|
|
"The OpenStack-Ansible community communicates in the #openstack-ansible IRC "
|
|
"channel hosted on OFTC. This channel is logged, and its logs are published "
|
|
"on http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/."
|
|
msgstr ""
|
|
"The OpenStack-Ansible community communicates in the #openstack-ansible IRC "
|
|
"channel hosted on OFTC. This channel is logged, and its logs are published "
|
|
"on http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/."
|
|
|
|
msgid ""
|
|
"The OpenStack-Ansible integrated repo also has an extra documentation "
|
|
"building process, to build the deployment guide."
|
|
msgstr ""
|
|
"The OpenStack-Ansible integrated repo also has an extra documentation "
|
|
"building process, to build the deployment guide."
|
|
|
|
msgid ""
|
|
"The OpenStack-Ansible project has different kinds of git repositories, each "
|
|
"of them with specific use cases, and different sets of practices."
|
|
msgstr ""
|
|
"The OpenStack-Ansible project has different kinds of git repositories, each "
|
|
"of them with specific use cases, and different sets of practices."
|
|
|
|
msgid ""
|
|
"The OpenStack-Ansible project has recurring tasks that need attention, like "
|
|
"releasing, or other code duties. See our page :ref:`Periodic "
|
|
"work<periodicwork>`."
|
|
msgstr ""
|
|
"The OpenStack-Ansible project has recurring tasks that need attention, like "
|
|
"releasing, or other code duties. See our page :ref:`Periodic "
|
|
"work<periodicwork>`."
|
|
|
|
msgid ""
|
|
"The `OpenStack-Ansible Core Reviewer Team`_ is responsible for many aspects "
|
|
"of the OpenStack-Ansible project. These include, but are not limited to:"
|
|
msgstr ""
|
|
"The `OpenStack-Ansible Core Reviewer Team`_ is responsible for many aspects "
|
|
"of the OpenStack-Ansible project. These include, but are not limited to:"
|
|
|
|
msgid ""
|
|
"The ``releasenotes`` build argument only tests committed changes. Ensure "
|
|
"your local changes are committed before running the ``releasenotes`` build."
|
|
msgstr ""
|
|
"The ``releasenotes`` build argument only tests committed changes. Ensure "
|
|
"your local changes are committed before running the ``releasenotes`` build."
|
|
|
|
msgid "The `defaults/main.yml` file"
|
|
msgstr "The `defaults/main.yml` file"
|
|
|
|
msgid "The `vars/<platform specific>.yml` file"
|
|
msgstr "The `vars/<platform specific>.yml` file"
|
|
|
|
msgid ""
|
|
"The `vars/<platform specific>.yml` is the place where distribution specific "
|
|
"content will be stored. For example, this file will hold the package names, "
|
|
"repositories urls and keys, file paths, service names/init scripts."
|
|
msgstr ""
|
|
"The `vars/<platform specific>.yml` is the place where distribution specific "
|
|
"content will be stored. For example, this file will hold the package names, "
|
|
"repositories URLs and keys, file paths, service names/init scripts."
|
|
|
|
msgid "The `vars/main.yml` file"
|
|
msgstr "The `vars/main.yml` file"
|
|
|
|
msgid ""
|
|
"The `vars/main.yml` is always included. It contains generic variables that "
|
|
"aren't meant to be changed by a deployer. This includes for example static "
|
|
"information that aren't distribution specific (like aggregation of role "
|
|
"internal variables for example)."
|
|
msgstr ""
|
|
"The `vars/main.yml` is always included. It contains generic variables that "
|
|
"aren't meant to be changed by a deployer. This includes for example static "
|
|
"information that aren't distribution specific (like aggregation of role "
|
|
"internal variables for example)."
|
|
|
|
msgid ""
|
|
"The bug triage meeting is probably a good time for people with bug "
|
|
"supervisors rights to also prioritize bugs per importance (on top of "
|
|
"classifying them on status)."
|
|
msgstr ""
|
|
"The bug triage meeting is probably a good time for people with bug "
|
|
"supervisors rights to also prioritise bugs per importance (on top of "
|
|
"classifying them on status)."
|
|
|
|
msgid ""
|
|
"The conventions for writing tests are described in the :ref:`tests` page."
|
|
msgstr ""
|
|
"The conventions for writing tests are described in the :ref:`tests` page."
|
|
|
|
msgid ""
|
|
"The convergence may involve consuming other OpenStack-Ansible roles (For "
|
|
"example: **galera_server, galera_client, rabbitmq_server**) in order to "
|
|
"ensure that the appropriate infrastructure is in place. Re-using existing "
|
|
"roles in OpenStack-Ansible or Ansible Galaxy is strongly encouraged."
|
|
msgstr ""
|
|
"The convergence may involve consuming other OpenStack-Ansible roles (For "
|
|
"example: **galera_server, galera_client, rabbitmq_server**) in order to "
|
|
"ensure that the appropriate infrastructure is in place. Re-using existing "
|
|
"roles in OpenStack-Ansible or Ansible Galaxy is strongly encouraged."
|
|
|
|
msgid ""
|
|
"The dependencies for OpenStack-Ansible are updated through the use of ``osa "
|
|
"releases bump_upstream_shas``. This script updates the project's pinned "
|
|
"SHAs, located in the `repo_packages folder`, based on their "
|
|
"``_git_track_branch`` value."
|
|
msgstr ""
|
|
"The dependencies for OpenStack-Ansible are updated through the use of ``osa "
|
|
"releases bump_upstream_shas``. This script updates the project's pinned "
|
|
"SHAs, located in the `repo_packages folder`, based on their "
|
|
"``_git_track_branch`` value."
|
|
|
|
msgid ""
|
|
"The description clearly states or describes the original problem or root "
|
|
"cause of the problem."
|
|
msgstr ""
|
|
"The description clearly states or describes the original problem or root "
|
|
"cause of the problem."
|
|
|
|
msgid "The description clearly states the expected outcome of the user action."
|
|
msgstr ""
|
|
"The description clearly states the expected outcome of the user action."
|
|
|
|
msgid "The following convention is used:"
|
|
msgstr "The following convention is used:"
|
|
|
|
msgid ""
|
|
"The in-depth technical information is located in the :dev_docs:`OpenStack-"
|
|
"Ansible Reference <reference/index.html>`."
|
|
msgstr ""
|
|
"The in-depth technical information is located in the :dev_docs:`OpenStack-"
|
|
"Ansible Reference <reference/index.html>`."
|
|
|
|
msgid ""
|
|
"The integrated repo functional test is using the ``scripts/gate-check-commit."
|
|
"sh`` script, which receives arguments from the zuul run playbook definition."
|
|
msgstr ""
|
|
"The integrated repo functional test is using the ``scripts/gate-check-commit."
|
|
"sh`` script, which receives arguments from the Zuul run playbook definition."
|
|
|
|
msgid ""
|
|
"The integration repository contains at least one job which passes the "
|
|
"Temptest testing framework."
|
|
msgstr ""
|
|
"The integration repository contains at least one job which passes the "
|
|
"Temptest testing framework."
|
|
|
|
msgid ""
|
|
"The list of supported distributions can be found in the :deploy_guide:"
|
|
"`Deployment Guide <deploymenthost.html>`"
|
|
msgstr ""
|
|
"The list of supported distributions can be found in the :deploy_guide:"
|
|
"`Deployment Guide <deploymenthost.html>`"
|
|
|
|
msgid ""
|
|
"The necessary steps for bootstrapping the operating system have to be "
|
|
"documented in the :deploy_guide:`Deployment Guide <index.html>`."
|
|
msgstr ""
|
|
"The necessary steps for bootstrapping the operating system have to be "
|
|
"documented in the :deploy_guide:`Deployment Guide <index.html>`."
|
|
|
|
msgid ""
|
|
"The next community meeting should discuss about role deprecation, and if no "
|
|
"contributor comes forward to fix the role, periodic testing will be turned "
|
|
"off, and the role will move to an ``unmaintained`` state."
|
|
msgstr ""
|
|
"The next community meeting should discuss about role deprecation, and if no "
|
|
"contributor comes forward to fix the role, periodic testing will be turned "
|
|
"off, and the role will move to an ``unmaintained`` state."
|
|
|
|
msgid ""
|
|
"The provided information should be totally self-contained. External access "
|
|
"to web services/sites should not be needed."
|
|
msgstr ""
|
|
"The provided information should be totally self-contained. External access "
|
|
"to web services/sites should not be needed."
|
|
|
|
msgid ""
|
|
"The role documentation (for example, the `keystone role documentation`_) "
|
|
"intends to explain all the options available for the role and how to "
|
|
"implement more advanced requirements. To reduce duplication, the role "
|
|
"documentation directly includes the role's default variables file which "
|
|
"includes the comments explaining the purpose of the variables. The long hand "
|
|
"documentation for the roles should focus less on explaining variables and "
|
|
"more on explaining how to implement advanced use cases."
|
|
msgstr ""
|
|
"The role documentation (for example, the `keystone role documentation`_) "
|
|
"intends to explain all the options available for the role and how to "
|
|
"implement more advanced requirements. To reduce duplication, the role "
|
|
"documentation directly includes the role's default variables file which "
|
|
"includes the comments explaining the purpose of the variables. The long hand "
|
|
"documentation for the roles should focus less on explaining variables and "
|
|
"more on explaining how to implement advanced use cases."
|
|
|
|
msgid ""
|
|
"The role documentation must include a description of the mandatory "
|
|
"infrastructure (For example: a database and a message queue are required), "
|
|
"variables (For example: the database name and credentials) and group names "
|
|
"(For example: The role expects a group named ``foo_all`` to be present and "
|
|
"it expects the host to be a member of it) for the role's execution to "
|
|
"succeed."
|
|
msgstr ""
|
|
"The role documentation must include a description of the mandatory "
|
|
"infrastructure (For example: a database and a message queue are required), "
|
|
"variables (For example: the database name and credentials) and group names "
|
|
"(For example: The role expects a group named ``foo_all`` to be present and "
|
|
"it expects the host to be a member of it) for the role's execution to "
|
|
"succeed."
|
|
|
|
msgid ""
|
|
"The role implementation should be done in such a way that it is agnostic "
|
|
"with regards to whether it is implemented in a container, or on a physical "
|
|
"host. The test infrastructure may make use of containers for the separation "
|
|
"of services, but if a role is used by a playbook that targets a host, it "
|
|
"must work regardless of whether that host is a container, a virtual server, "
|
|
"or a physical server. The use of containers for role tests is not required "
|
|
"but it may be useful in order to simulate a multi-node build out as part of "
|
|
"the testing infrastructure."
|
|
msgstr ""
|
|
"The role implementation should be done in such a way that it is agnostic "
|
|
"with regards to whether it is implemented in a container, or on a physical "
|
|
"host. The test infrastructure may make use of containers for the separation "
|
|
"of services, but if a role is used by a playbook that targets a host, it "
|
|
"must work regardless of whether that host is a container, a virtual server, "
|
|
"or a physical server. The use of containers for role tests is not required "
|
|
"but it may be useful in order to simulate a multi-node build out as part of "
|
|
"the testing infrastructure."
|
|
|
|
msgid ""
|
|
"The tests in the openstack infrastructure are triggered by jobs defined in "
|
|
"each repo ``zuul.d`` folder."
|
|
msgstr ""
|
|
"The tests in the OpenStack infrastructure are triggered by jobs defined in "
|
|
"each repo ``zuul.d`` folder."
|
|
|
|
msgid ""
|
|
"The tests repository is the location for common code used in the integrated "
|
|
"repo and role repos tests."
|
|
msgstr ""
|
|
"The tests repository is the location for common code used in the integrated "
|
|
"repo and role repos tests."
|
|
|
|
msgid "The triaging process is explained here below."
|
|
msgstr "The triaging process is explained here below."
|
|
|
|
msgid "The variables files in a role are split in 3 locations:"
|
|
msgstr "The variables files in a role are split in 3 locations:"
|
|
|
|
msgid ""
|
|
"The variables with lower priority should be in the `defaults/main.yml`. This "
|
|
"allows their overriding with group variables or host variables. A good "
|
|
"example for this are default database connection details, default queues "
|
|
"connection details, or debug mode."
|
|
msgstr ""
|
|
"The variables with lower priority should be in the `defaults/main.yml`. This "
|
|
"allows their overriding with group variables or host variables. A good "
|
|
"example for this are default database connection details, default queues "
|
|
"connection details, or debug mode."
|
|
|
|
msgid ""
|
|
"There should be no difference between running tests in the openstack "
|
|
"infrastructure, versus running locally."
|
|
msgstr ""
|
|
"There should be no difference between running tests in the OpenStack "
|
|
"infrastructure, versus running locally."
|
|
|
|
msgid ""
|
|
"They have made a long-term, recurring time investment to improve the project."
|
|
msgstr ""
|
|
"They have made a long-term, recurring time investment to improve the project."
|
|
|
|
msgid "They share responsibility in the project's success in its `mission`_."
|
|
msgstr "They share responsibility in the project's success in its `mission`_."
|
|
|
|
msgid ""
|
|
"They spend their time doing what needs to be done to ensure the project's "
|
|
"success, not necessarily what is the most interesting or fun."
|
|
msgstr ""
|
|
"They spend their time doing what needs to be done to ensure the project's "
|
|
"success, not necessarily what is the most interesting or fun."
|
|
|
|
msgid "They value a healthy, vibrant, and active developer and user community."
|
|
msgstr ""
|
|
"They value a healthy, vibrant, and active developer and user community."
|
|
|
|
msgid ""
|
|
"This can be done using the ``new-release`` command, and then editing the SHA "
|
|
"used for openstack-ansible. See also `new_releases page`_ for an explanation "
|
|
"of this command."
|
|
msgstr ""
|
|
"This can be done using the ``new-release`` command, and then editing the SHA "
|
|
"used for OpenStack-Ansible. See also `new_releases page`_ for an explanation "
|
|
"of this command."
|
|
|
|
msgid "This can do multiple things:"
|
|
msgstr "This can do multiple things:"
|
|
|
|
msgid ""
|
|
"This document should help you understand how to contribute to OpenStack-"
|
|
"Ansible."
|
|
msgstr ""
|
|
"This document should help you understand how to contribute to OpenStack-"
|
|
"Ansible."
|
|
|
|
msgid ""
|
|
"This doesn't patch the ``global-requirements-pins``, as this should be a "
|
|
"manual operation. See the :ref:`cycle-checklist` to know when to bump the "
|
|
"global-requirements-pins."
|
|
msgstr ""
|
|
"This doesn't patch the ``global-requirements-pins``, as this should be a "
|
|
"manual operation. See the :ref:`cycle-checklist` to know when to bump the "
|
|
"global-requirements-pins."
|
|
|
|
msgid "This folder contains at least the following files:"
|
|
msgstr "This folder contains at least the following files:"
|
|
|
|
msgid "This guide may be built locally by executing:"
|
|
msgstr "This guide may be built locally by executing:"
|
|
|
|
msgid ""
|
|
"This repository contains all the information concerning large bodies of work "
|
|
"done in OpenStack-Ansible, split by cycle."
|
|
msgstr ""
|
|
"This repository contains all the information concerning large bodies of work "
|
|
"done in OpenStack-Ansible, split by cycle."
|
|
|
|
msgid ""
|
|
"This repository is an incubator for new projects, each project solving a "
|
|
"particular operational problem. Each project has its own folder in this "
|
|
"repository."
|
|
msgstr ""
|
|
"This repository is an incubator for new projects, each project solving a "
|
|
"particular operational problem. Each project has its own folder in this "
|
|
"repository."
|
|
|
|
msgid ""
|
|
"This tooling can then be called using ``osa releases``. Each subcommand "
|
|
"contains help by default."
|
|
msgstr ""
|
|
"This tooling can then be called using ``osa releases``. Each subcommand "
|
|
"contains help by default."
|
|
|
|
msgid ""
|
|
"This wishlist bug has been open a year without any activity. I am moving "
|
|
"this to \"Opinion / Wishlist\". This is an easily-obtainable queue of older "
|
|
"requests. This bug can be reopened (set back to \"New\") if someone decides "
|
|
"to work on this."
|
|
msgstr ""
|
|
"This wishlist bug has been open a year without any activity. I am moving "
|
|
"this to \"Opinion / Wishlist\". This is an easily-obtainable queue of older "
|
|
"requests. This bug can be reopened (set back to \"New\") if someone decides "
|
|
"to work on this."
|
|
|
|
msgid ""
|
|
"To facilitate the development and tests implemented across all OpenStack-"
|
|
"Ansible roles, a base set of folders and files need to be implemented. A "
|
|
"base set of configuration and test facilitation scripts must include at "
|
|
"least the following:"
|
|
msgstr ""
|
|
"To facilitate the development and tests implemented across all OpenStack-"
|
|
"Ansible roles, a base set of folders and files need to be implemented. A "
|
|
"base set of configuration and test facilitation scripts must include at "
|
|
"least the following:"
|
|
|
|
msgid ""
|
|
"To help triaging bugs, one person of the bug team can be on \"bug skimming "
|
|
"duty\"."
|
|
msgstr ""
|
|
"To help triaging bugs, one person of the bug team can be on \"bug skimming "
|
|
"duty\"."
|
|
|
|
msgid ""
|
|
"To meet these needs developers must submit :ref:`code "
|
|
"comments<codecomments>`, documentation (see also the :ref:`documentation "
|
|
"locations section<docslocations>`) and :ref:`release notes<reno>` with any "
|
|
"code submissions."
|
|
msgstr ""
|
|
"To meet these needs developers must submit :ref:`code "
|
|
"comments<codecomments>`, documentation (see also the :ref:`documentation "
|
|
"locations section<docslocations>`) and :ref:`release notes<reno>` with any "
|
|
"code submissions."
|
|
|
|
msgid "To run a functional test named \"calico\", execute:"
|
|
msgstr "To run a functional test named \"calico\", execute:"
|
|
|
|
msgid "To run a functional test of the role, execute:"
|
|
msgstr "To run a functional test of the role, execute:"
|
|
|
|
msgid ""
|
|
"To test the integrated repo, follow the :deploy_guide:`Deployment Guide "
|
|
"<index.html>`"
|
|
msgstr ""
|
|
"To test the integrated repo, follow the :deploy_guide:`Deployment Guide "
|
|
"<index.html>`"
|
|
|
|
msgid "Unfreeze of master."
|
|
msgstr "Unfreeze of master."
|
|
|
|
msgid "Update ``global-requirements-pins``"
|
|
msgstr "Update ``global-requirements-pins``"
|
|
|
|
msgid "Updating OpenStack-Ansible roles"
|
|
msgstr "Updating OpenStack-Ansible roles"
|
|
|
|
msgid ""
|
|
"Updating the roles to their latest version per branch is done through ``osa "
|
|
"releases bump_roles $gitbranchname``."
|
|
msgstr ""
|
|
"Updating the roles to their latest version per branch is done through ``osa "
|
|
"releases bump_roles $gitbranchname``."
|
|
|
|
msgid "Updating upstream SHAs"
|
|
msgstr "Updating upstream SHAs"
|
|
|
|
msgid ""
|
|
"Usage of the \">\" and \"|\" operators should be limited to Ansible "
|
|
"conditionals and command modules such as the Ansible ``shell`` or "
|
|
"``command``."
|
|
msgstr ""
|
|
"Usage of the \">\" and \"|\" operators should be limited to Ansible "
|
|
"conditionals and command modules such as the Ansible ``shell`` or "
|
|
"``command``."
|
|
|
|
msgid ""
|
|
"Use the topic ``create-<branchname>`` (e.g: ``create-stein``) for future "
|
|
"reference."
|
|
msgstr ""
|
|
"Use the topic ``create-<branchname>`` (e.g: ``create-stein``) for future "
|
|
"reference."
|
|
|
|
msgid ""
|
|
"Usually not. This bug report has an inconsistent state though. If a bug "
|
|
"report has an assignee, it should be In Progress and have an importance set."
|
|
msgstr ""
|
|
"Usually not. This bug report has an inconsistent state though. If a bug "
|
|
"report has an assignee, it should be In Progress and have an importance set."
|
|
|
|
msgid "Variable files conventions"
|
|
msgstr "Variable files conventions"
|
|
|
|
msgid "Voting"
|
|
msgstr "Voting"
|
|
|
|
msgid ""
|
|
"We follow openstack guidelines for the `code reviewing <https://docs."
|
|
"openstack.org/project-team-guide/review-the-openstack-way.html>`_ process."
|
|
msgstr ""
|
|
"We follow OpenStack guidelines for the `code reviewing <https://docs."
|
|
"openstack.org/project-team-guide/review-the-openstack-way.html>`_ process."
|
|
|
|
msgid "We track our tasks in Launchpad"
|
|
msgstr "We track our tasks in Launchpad"
|
|
|
|
msgid ""
|
|
"Weekly meetings are held in our IRC channel. The schedule and logs can be "
|
|
"found on http://eavesdrop.openstack.org/"
|
|
"#OpenStack_Ansible_Deployment_Meeting. Next meeting agenda can be found on "
|
|
"our `Meetings wiki page <https://wiki.openstack.org/wiki/Meetings/openstack-"
|
|
"ansible>`_."
|
|
msgstr ""
|
|
"Weekly meetings are held in our IRC channel. The schedule and logs can be "
|
|
"found on http://eavesdrop.openstack.org/"
|
|
"#OpenStack_Ansible_Deployment_Meeting. The next meeting agenda can be found "
|
|
"on our `Meetings wiki page <https://wiki.openstack.org/wiki/Meetings/"
|
|
"openstack-ansible>`_."
|
|
|
|
msgid ""
|
|
"Weekly meetings are held in our IRC channel. The schedule and logs can be "
|
|
"found on http://eavesdrop.openstack.org/"
|
|
"#OpenStack_Ansible_Deployment_Meeting. The agenda for the next meeting can "
|
|
"be found on our `Meetings wiki page <https://wiki.openstack.org/wiki/"
|
|
"Meetings/openstack-ansible>`_."
|
|
msgstr ""
|
|
"Weekly meetings are held in our IRC channel. The schedule and logs can be "
|
|
"found on http://eavesdrop.openstack.org/"
|
|
"#OpenStack_Ansible_Deployment_Meeting. The agenda for the next meeting can "
|
|
"be found on our `Meetings wiki page <https://wiki.openstack.org/wiki/"
|
|
"Meetings/openstack-ansible>`_."
|
|
|
|
msgid "What is a bug triage"
|
|
msgstr "What is a bug triage"
|
|
|
|
msgid ""
|
|
"What is the best status to close a bug report if its issue cannot be "
|
|
"reproduced?"
|
|
msgstr ""
|
|
"What is the best status to close a bug report if its issue cannot be "
|
|
"reproduced?"
|
|
|
|
msgid "What is the goal of the bug skimming duty?"
|
|
msgstr "What is the goal of the bug skimming duty?"
|
|
|
|
msgid ""
|
|
"When a cherry-pick is modified in any way, the changes made and the reasons "
|
|
"for them must be explicitly expressed in the commit message."
|
|
msgstr ""
|
|
"When a cherry-pick is modified in any way, the changes made and the reasons "
|
|
"for them must be explicitly expressed in the commit message."
|
|
|
|
msgid ""
|
|
"When cherry-picking a commit from one branch to another the commit message "
|
|
"should be amended with any files that may have been in conflict while "
|
|
"performing the cherry-pick operation. Additionally, cherry-pick commit "
|
|
"messages should contain the original commit *SHA* near the bottom of the new "
|
|
"commit message. This can be done with ``cherry-pick -x``. Here's more "
|
|
"information on `Submitting a change to a branch for review`_."
|
|
msgstr ""
|
|
"When cherry-picking a commit from one branch to another the commit message "
|
|
"should be amended with any files that may have been in conflict while "
|
|
"performing the cherry-pick operation. Additionally, cherry-pick commit "
|
|
"messages should contain the original commit *SHA* near the bottom of the new "
|
|
"commit message. This can be done with ``cherry-pick -x``. Here's more "
|
|
"information on `Submitting a change to a branch for review`_."
|
|
|
|
msgid ""
|
|
"When creating tasks and other roles for use in Ansible please create them "
|
|
"using the YAML dictionary format."
|
|
msgstr ""
|
|
"When creating tasks and other roles for use in Ansible please create them "
|
|
"using the YAML dictionary format."
|
|
|
|
msgid ""
|
|
"When submitting a bug, or working on a bug, please ensure the following "
|
|
"criteria are met:"
|
|
msgstr ""
|
|
"When submitting a bug, or working on a bug, please ensure the following "
|
|
"criteria are met:"
|
|
|
|
msgid ""
|
|
"When the patches to update SHAs and roles have landed, you can propose the "
|
|
"parent SHA as a release in the releases repo."
|
|
msgstr ""
|
|
"When the patches to update SHAs and roles have landed, you can propose the "
|
|
"parent SHA as a release in the releases repo."
|
|
|
|
msgid ""
|
|
"Where possible the documentation in OpenStack-Ansible should steer clear of "
|
|
"trying to explain OpenStack concepts. Those explanations belong in the "
|
|
"OpenStack Manuals or service documentation and OpenStack-Ansible "
|
|
"documentation should link to those documents when available, rather than "
|
|
"duplicate their content."
|
|
msgstr ""
|
|
"Where possible the documentation in OpenStack-Ansible should steer clear of "
|
|
"trying to explain OpenStack concepts. Those explanations belong in the "
|
|
"OpenStack Manuals or service documentation and OpenStack-Ansible "
|
|
"documentation should link to those documents when available, rather than "
|
|
"duplicate their content."
|
|
|
|
msgid ""
|
|
"While everyone is encouraged to review changes, members of the core reviewer "
|
|
"team have the ability to +2/-2 and +W changes to these repositories. This is "
|
|
"an extra level of responsibility not to be taken lightly. Correctly merging "
|
|
"code requires not only understanding the code itself, but also how the code "
|
|
"affects things like documentation, testing, upgrade impacts and interactions "
|
|
"with other projects. It also means you pay attention to release milestones "
|
|
"and understand if a patch you are merging is marked for the release, "
|
|
"especially critical during the feature freeze."
|
|
msgstr ""
|
|
"While everyone is encouraged to review changes, members of the core reviewer "
|
|
"team have the ability to +2/-2 and +W changes to these repositories. This is "
|
|
"an extra level of responsibility not to be taken lightly. Correctly merging "
|
|
"code requires not only understanding the code itself, but also how the code "
|
|
"affects things like documentation, testing, upgrade impacts and interactions "
|
|
"with other projects. It also means you pay attention to release milestones "
|
|
"and understand if a patch you are merging is marked for the release, "
|
|
"especially critical during the feature freeze."
|
|
|
|
msgid ""
|
|
"While this script is primarily developed and maintained for use in OpenStack-"
|
|
"CI, it can be used in other environments."
|
|
msgstr ""
|
|
"While this script is primarily developed and maintained for use in OpenStack-"
|
|
"CI, it can be used in other environments."
|
|
|
|
msgid "Work on the role files, following our :ref:`code_rules`."
|
|
msgstr "Work on the role files, following our :ref:`code_rules`."
|
|
|
|
msgid "Working on bug fixes"
|
|
msgstr "Working on bug fixes"
|
|
|
|
msgid "Working on new features"
|
|
msgstr "Working on new features"
|
|
|
|
msgid ""
|
|
"Write good commit messages. We follow the OpenStack \"`Git Commit Good "
|
|
"Practice`_\" guide. if you have any questions regarding how to write good "
|
|
"commit messages please review the upstream OpenStack documentation."
|
|
msgstr ""
|
|
"Write good commit messages. We follow the OpenStack \"`Git Commit Good "
|
|
"Practice`_\" guide. if you have any questions regarding how to write good "
|
|
"commit messages please review the upstream OpenStack documentation."
|
|
|
|
msgid "Writing style"
|
|
msgstr "Writing style"
|
|
|
|
msgid "YAML formatting"
|
|
msgstr "YAML formatting"
|
|
|
|
msgid ""
|
|
"You can check the current PyPI pins that are used in openstack-ansible "
|
|
"repository by running ``osa releases check_pins``. This will display a "
|
|
"table, showing the current pin in OSA, and what is available upstream on "
|
|
"PyPI."
|
|
msgstr ""
|
|
"You can check the current PyPI pins that are used in OpenStack-Ansible "
|
|
"repository by running ``osa releases check_pins``. This will display a "
|
|
"table, showing the current pin in OSA, and what is available upstream on "
|
|
"PyPI."
|
|
|
|
msgid ""
|
|
"You can follow examples from other roles, making the appropriate "
|
|
"modifications being sure that group labels in ``env.d`` and ``conf.d`` files "
|
|
"are consistent."
|
|
msgstr ""
|
|
"You can follow examples from other roles, making the appropriate "
|
|
"modifications being sure that group labels in ``env.d`` and ``conf.d`` files "
|
|
"are consistent."
|
|
|
|
msgid "You can install the latest version of this tooling by running:"
|
|
msgstr "You can install the latest version of this tooling by running:"
|
|
|
|
msgid ""
|
|
"You can review roles which may be currently in development by checking our "
|
|
"`specs repository`_ and `unmerged specs`_ on review.openstack.org. If you do "
|
|
"not find a spec for the role, propose a blueprint/spec. See also :ref:"
|
|
"`specs`."
|
|
msgstr ""
|
|
"You can review roles which may be currently in development by checking our "
|
|
"`specs repository`_ and `unmerged specs`_ on review.openstack.org. If you do "
|
|
"not find a spec for the role, propose a blueprint/spec. See also :ref:"
|
|
"`specs`."
|
|
|
|
msgid ""
|
|
"You found an issue and want to make sure we are aware of it? You can do so "
|
|
"on `Launchpad <https://bugs.launchpad.net/openstack-ansible>`_."
|
|
msgstr ""
|
|
"You found an issue and want to make sure we are aware of it? You can do so "
|
|
"on `Launchpad <https://bugs.launchpad.net/openstack-ansible>`_."
|
|
|
|
msgid ""
|
|
"``.gitignore``: A standard git configuration file for the repository which "
|
|
"should be pretty uniform across all the repositories. This must be copied "
|
|
"from the ``openstack-ansible-tests`` repository and will be automatically be "
|
|
"overridden by our proposal bot should any change happen."
|
|
msgstr ""
|
|
"``.gitignore``: A standard git configuration file for the repository which "
|
|
"should be pretty uniform across all the repositories. This must be copied "
|
|
"from the ``openstack-ansible-tests`` repository and will be automatically be "
|
|
"overridden by our proposal bot should any change happen."
|
|
|
|
msgid ""
|
|
"``.gitreview``: A standard file configured for the project to inform the "
|
|
"``git-review`` plugin where to find the upstream gerrit remote for the "
|
|
"repository."
|
|
msgstr ""
|
|
"``.gitreview``: A standard file configured for the project to inform the "
|
|
"``git-review`` plugin where to find the upstream gerrit remote for the "
|
|
"repository."
|
|
|
|
msgid ""
|
|
"``<role name>-overrides.yml``. This var file is automatically loaded by our "
|
|
"shell script in our `tests repository`_."
|
|
msgstr ""
|
|
"``<role name>-overrides.yml``. This var file is automatically loaded by our "
|
|
"shell script in our `tests repository`_."
|
|
|
|
msgid "``Complete``"
|
|
msgstr "``Complete``"
|
|
|
|
msgid "``Incubated``"
|
|
msgstr "``Incubated``"
|
|
|
|
msgid ""
|
|
"``README.rst``, ``LICENSE``, ``CONTRIBUTING.rst``: A set of standard files "
|
|
"whose content is self-explanatory."
|
|
msgstr ""
|
|
"``README.rst``, ``LICENSE``, ``CONTRIBUTING.rst``: A set of standard files "
|
|
"whose content is self-explanatory."
|
|
|
|
msgid "``Retired``"
|
|
msgstr "``Retired``"
|
|
|
|
msgid "``Unmaintained``"
|
|
msgstr "``Unmaintained``"
|
|
|
|
msgid ""
|
|
"``Vagrantfile``: A configuration file to allow a developer to easily create "
|
|
"a test virtual machine using `Vagrant`_. This must automatically execute "
|
|
"``run_tests.sh``. This must be copied from the ``openstack-ansible-tests`` "
|
|
"repository and will be automatically be overridden by our proposal bot "
|
|
"should any change happen."
|
|
msgstr ""
|
|
"``Vagrantfile``: A configuration file to allow a developer to easily create "
|
|
"a test virtual machine using `Vagrant`_. This must automatically execute "
|
|
"``run_tests.sh``. This must be copied from the ``openstack-ansible-tests`` "
|
|
"repository and will be automatically be overridden by our proposal bot "
|
|
"should any change happen."
|
|
|
|
msgid ""
|
|
"``ansible-role-requirements.yml``. This should be fairly straightforward: "
|
|
"this file contains all the roles to clone before running your role. The "
|
|
"roles' relative playbooks will have to be listed in the ``test.yml`` file. "
|
|
"However, keep in mind to NOT re-invent the wheel. For example, if your role "
|
|
"needs keystone, you don't need to create your own keystone install playbook, "
|
|
"because we have a generic keystone install playbook in the `tests "
|
|
"repository`."
|
|
msgstr ""
|
|
"``ansible-role-requirements.yml``. This should be fairly straightforward: "
|
|
"this file contains all the roles to clone before running your role. The "
|
|
"roles' relative playbooks will have to be listed in the ``test.yml`` file. "
|
|
"However, keep in mind to NOT re-invent the wheel. For example, if your role "
|
|
"needs keystone, you don't need to create your own keystone install playbook, "
|
|
"because we have a generic keystone install playbook in the `tests "
|
|
"repository`."
|
|
|
|
msgid ""
|
|
"``bindep.txt``: The binary requirements that must be installed on the host "
|
|
"the tests are executed on for the Python requirements and the tox execution "
|
|
"to work. This must be copied from the ``openstack-ansible-tests`` repository "
|
|
"and will be automatically be overridden by our proposal bot should any "
|
|
"change happen."
|
|
msgstr ""
|
|
"``bindep.txt``: The binary requirements that must be installed on the host "
|
|
"the tests are executed on for the Python requirements and the tox execution "
|
|
"to work. This must be copied from the ``openstack-ansible-tests`` repository "
|
|
"and will be automatically be overridden by our proposal bot should any "
|
|
"change happen."
|
|
|
|
msgid ""
|
|
"``deprecations``: If a variable has been deprecated (ideally using the "
|
|
"deprecation filter), then it should be communicated through notes in this "
|
|
"section. Note that if a variable has been removed entirely then it has not "
|
|
"been deprecated and the removal should be noted in the ``upgrade`` section."
|
|
msgstr ""
|
|
"``deprecations``: If a variable has been deprecated (ideally using the "
|
|
"deprecation filter), then it should be communicated through notes in this "
|
|
"section. Note that if a variable has been removed entirely then it has not "
|
|
"been deprecated and the removal should be noted in the ``upgrade`` section."
|
|
|
|
msgid ""
|
|
"``docs/`` and ``releasenotes/`` folders need to be exist and be properly "
|
|
"configured."
|
|
msgstr ""
|
|
"``docs/`` and ``releasenotes/`` folders need to be exist and be properly "
|
|
"configured."
|
|
|
|
msgid ""
|
|
"``features``: This should inform the deployer briefly about a new feature "
|
|
"and should describe how to use it either by referencing the variables to set "
|
|
"or by referring to documentation."
|
|
msgstr ""
|
|
"``features``: This should inform the deployer briefly about a new feature "
|
|
"and should describe how to use it either by referencing the variables to set "
|
|
"or by referring to documentation."
|
|
|
|
msgid ""
|
|
"``group_vars`` and ``host_vars``. These folders will hold override the "
|
|
"necessary files for testing. For example, this is where you override the IP "
|
|
"addresses, IP ranges, and ansible connection details."
|
|
msgstr ""
|
|
"``group_vars`` and ``host_vars``. These folders will hold override the "
|
|
"necessary files for testing. For example, this is where you override the IP "
|
|
"addresses, IP ranges, and Ansible connection details."
|
|
|
|
msgid ""
|
|
"``inventory``. A static inventory for role testing. It's possible some roles "
|
|
"have multiple inventories. See for example the neutron role with its "
|
|
"``lxb_inventory``, ``calico_inventory``."
|
|
msgstr ""
|
|
"``inventory``. A static inventory for role testing. It's possible some roles "
|
|
"have multiple inventories. See for example the Neutron role with its "
|
|
"``lxb_inventory``, ``calico_inventory``."
|
|
|
|
msgid ""
|
|
"``issues``: This should inform the deployer about known issues. This may be "
|
|
"used when fixing an issue and wanting to inform deployers about a workaround "
|
|
"that can be used for versions prior to that which contains the patch that "
|
|
"fixes the issue. Issue notes should specifically make mention of what "
|
|
"versions of OpenStack-Ansible are affected by the issue."
|
|
msgstr ""
|
|
"``issues``: This should inform the deployer about known issues. This may be "
|
|
"used when fixing an issue and wanting to inform deployers about a workaround "
|
|
"that can be used for versions prior to that which contains the patch that "
|
|
"fixes the issue. Issue notes should specifically make mention of what "
|
|
"versions of OpenStack-Ansible are affected by the issue."
|
|
|
|
msgid ""
|
|
"``run_tests.sh``: A script for developers to execute all standard tests on a "
|
|
"suitable host. This must be copied from the ``openstack-ansible-tests`` "
|
|
"repository and will be automatically be overridden by our proposal bot "
|
|
"should any change happen."
|
|
msgstr ""
|
|
"``run_tests.sh``: A script for developers to execute all standard tests on a "
|
|
"suitable host. This must be copied from the ``openstack-ansible-tests`` "
|
|
"repository and will be automatically be overridden by our proposal bot "
|
|
"should any change happen."
|
|
|
|
msgid ""
|
|
"``setup.cfg`` and ``setup.py``: Information about the repository used when "
|
|
"building artifacts."
|
|
msgstr ""
|
|
"``setup.cfg`` and ``setup.py``: Information about the repository used when "
|
|
"building artifacts."
|
|
|
|
msgid ""
|
|
"``test-requirements.txt``: The Python requirements that must be installed "
|
|
"when executing the tests."
|
|
msgstr ""
|
|
"``test-requirements.txt``: The Python requirements that must be installed "
|
|
"when executing the tests."
|
|
|
|
msgid ""
|
|
"``test.yml`` (\"super\" playbook acting as test router to sub-playbooks)"
|
|
msgstr ""
|
|
"``test.yml`` (\"super\" playbook acting as test router to sub-playbooks)"
|
|
|
|
msgid ""
|
|
"``tox.ini``: The lint testing, documentation build, release note build and "
|
|
"functional build execution process for the role's gate tests are all defined "
|
|
"in this file."
|
|
msgstr ""
|
|
"``tox.ini``: The lint testing, documentation build, release note build and "
|
|
"functional build execution process for the role's gate tests are all defined "
|
|
"in this file."
|
|
|
|
msgid ""
|
|
"``upgrade``: This should inform the deployer about changes which may affect "
|
|
"them when upgrading from a previous major or minor version. Typically, these "
|
|
"notes would describe changes to default variable values or variables that "
|
|
"have been removed."
|
|
msgstr ""
|
|
"``upgrade``: This should inform the deployer about changes which may affect "
|
|
"them when upgrading from a previous major or minor version. Typically, these "
|
|
"notes would describe changes to default variable values or variables that "
|
|
"have been removed."
|
|
|
|
msgid ""
|
|
"and use jinja templating, this is very difficult to achieve. It is still "
|
|
"considered a preference and should be a goal to improve readability, within "
|
|
"reason."
|
|
msgstr ""
|
|
"and use jinja templating, this is very difficult to achieve. It is still "
|
|
"considered a preference and should be a goal to improve readability, within "
|
|
"reason."
|
|
|
|
msgid ""
|
|
"as templates and use jinja templating, this will often fail. This test is "
|
|
"reasonably safely ignored as the syntax error will be identified when "
|
|
"executing the resulting script."
|
|
msgstr ""
|
|
"as templates and use jinja templating, this will often fail. This test is "
|
|
"reasonably safely ignored as the syntax error will be identified when "
|
|
"executing the resulting script."
|
|
|
|
msgid "https://bugs.launchpad.net/openstack-ansible"
|
|
msgstr "https://bugs.launchpad.net/openstack-ansible"
|
|
|
|
msgid "https://github.com/ceph/ceph-ansible"
|
|
msgstr "https://github.com/ceph/ceph-ansible"
|
|
|
|
msgid "https://github.com/evrardjp/ansible-keepalived"
|
|
msgstr "https://github.com/evrardjp/ansible-keepalived"
|
|
|
|
msgid "https://github.com/logan2211/ansible-resolvconf"
|
|
msgstr "https://github.com/logan2211/ansible-resolvconf"
|
|
|
|
msgid ""
|
|
"https://github.com/opendaylight/integration-packaging-ansible-opendaylight"
|
|
msgstr ""
|
|
"https://github.com/opendaylight/integration-packaging-ansible-opendaylight"
|
|
|
|
msgid "https://github.com/openstack/ansible-config_template"
|
|
msgstr "https://github.com/openstack/ansible-config_template"
|
|
|
|
msgid "https://github.com/openstack/ansible-hardening"
|
|
msgstr "https://github.com/openstack/ansible-hardening"
|
|
|
|
msgid "https://github.com/openstack/ansible-role-systemd_mount"
|
|
msgstr "https://github.com/openstack/ansible-role-systemd_mount"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible"
|
|
msgstr "https://github.com/openstack/openstack-ansible"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible-ops"
|
|
msgstr "https://github.com/openstack/openstack-ansible-ops"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible-os_glance"
|
|
msgstr "https://github.com/openstack/openstack-ansible-os_glance"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible-os_nova"
|
|
msgstr "https://github.com/openstack/openstack-ansible-os_nova"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible-specs"
|
|
msgstr "https://github.com/openstack/openstack-ansible-specs"
|
|
|
|
msgid "https://github.com/openstack/openstack-ansible-tests"
|
|
msgstr "https://github.com/openstack/openstack-ansible-tests"
|
|
|
|
msgid "https://github.com/willshersystems/ansible-sshd"
|
|
msgstr "https://github.com/willshersystems/ansible-sshd"
|
|
|
|
msgid "or"
|
|
msgstr "or"
|
|
|
|
msgid "where #bugnumber refers to a Launchpad issue."
|
|
msgstr "where #bugnumber refers to a Launchpad issue."
|