Skip to content
Snippets Groups Projects
Select Git revision
  • deployment default
1 result
Search by author
  • Any Author
  • KANAPA SYLVERE p1919734 KANAPA SYLVERE p1919734 p1919734
1 author
  1. Jan 07, 2022
  3. Dec 31, 2021
  5. Dec 21, 2021
  7. Dec 20, 2021
    • Radosław Piliszek's avatar
      [docs] Mark init-runonce properly · 1c93c8ea
      Radosław Piliszek authored 
      This is a docs amendment to let users know that calling
init-runonce is not a required deployment step and it may not work
for them if they modified the defaults.

Change-Id: Ia3922b53d91a1a820447fec6a8074b941edc2ee9
      1c93c8ea
  9. Nov 11, 2021
  11. Nov 10, 2021
  13. Nov 09, 2021
  15. Nov 04, 2021
  17. Oct 27, 2021
  19. Sep 30, 2021
  21. Sep 28, 2021
    • Niklas Hagman's avatar
      Transition Keystone admin user to system scope · 2e933dce
      Niklas Hagman authored 
      A system-scoped token implies the user has authorization to act on the
deployment system. These tokens are useful for interacting with
resources that affect the deployment as a whole, or exposes resources
that may otherwise violate project or domain isolation.

Since Queens, the keystone-manage bootstrap command assigns the admin
role to the admin user with system scope, as well as in the admin
project. This patch transitions the Keystone admin user from
authenticating using project scoped tokens to system scoped tokens.
This is a necessary step towards being able to enable the updated oslo
policies in services that allow finer grained access to system-level
resources and APIs.

An etherpad with discussion about the transition to the new oslo
service policies is:

https://etherpad.opendev.org/p/enabling-system-scope-in-kolla-ansible



Change-Id: Ib631e2211682862296cce9ea179f2661c90fa585
Signed-off-by: default avatarNiklas Hagman <ubuntu@post.blinkiz.com>
      2e933dce
  23. Sep 23, 2021
  25. Sep 16, 2021
  27. Aug 25, 2021
    • Mark Goddard's avatar
      Add kolla-ansible gather-facts command · d9a37589
      Mark Goddard authored 
      In some situations it may be helpful to populate the fact cache on
demand. The 'kolla-ansible gather-facts' command may be used to do this.

One specific case where this may be helpful is when running kolla-ansible
with a --limit argument, since in that case hosts that match the limit
will gather facts for hosts that fall outside the limit. In the extreme
case of a limit that matches only one host, it will serially gather
facts for all other hosts. To avoid this issue, run 'kolla-ansible
gather-facts' without a limit to populate the fact cache in parallel
before running the required command with a limit.

Change-Id: I79db9bca23aa1bd45bafa7e7500a90de5a684593
      d9a37589
  29. Aug 22, 2021
  31. Jul 29, 2021
    • Will Szumski's avatar
      Support multiple inventories · 6c72fa81
      Will Szumski authored 
      Multiple inventories can now be passed to `kolla-ansible`.  This can be
useful to construct a common inventory that is shared between multiple
environments.

Change-Id: I2ac5d7851b310bea2ba362b353f18c592a0a6a2e
      6c72fa81
  33. Jul 02, 2021
    • Rafael Weingärtner's avatar
      Make setup module arguments configurable · 15f2fdcd
      Rafael Weingärtner authored 
      
Ansible facts can have a large impact on the performance of the Ansible
control host. This patch introduces some control over which facts are
gathered (kolla_ansible_setup_gather_subset) and which facts are stored
(kolla_ansible_setup_filter). By default we do not change the default
values of these arguments to the setup module. The flexibility of these
arguments is limited, but they do provide enough for a large performance
improvement in a typical moderate to large OpenStack cloud.

In particular, the large complex dict fact for each interface has a
large effect, and on an OpenStack controller or hypervisor there may be
many virtual interfaces. We can use the kolla_ansible_setup_filter
variable to help:

    kolla_ansible_setup_filter: 'ansible_[!qt]*'

This causes Ansible to collect but not store facts matching that
pattern, which includes the virtual interface facts. Currently we are
not referencing other facts matching the pattern within Kolla Ansible.
Note that including the 'ansible_' prefix causes meta facts module_setup
and gather_subset to be filtered, but this seems to be the only way to
get a good match on the interface facts. To work around this, we use
ansible_facts rather than module_setup to detect whether facts exist in
the cache.

The exact improvement will vary, but has been reported to be as large as
18x on systems with many virtual interfaces.

For reference, here are some other tunings tried:

* Increased the number of forks (great speedup depending of the size of
  the deployment)
* Use `strategy = mitogen_linear` (cut processing time in half)
* Ansible caching (little speed up)
* SSH tunning (little speed up)

Co-Authored-By: default avatarMark Goddard <mark@stackhpc.com>
Closes-Bug: #1921538
Change-Id: Iae8ca4aae945892f1dc65e1b10381d2e26e88805
      15f2fdcd
  35. Jun 30, 2021
  37. Jun 23, 2021
    • Mark Goddard's avatar
      Use ansible_facts to reference facts · ade5bfa3
      Mark Goddard authored 
      By default, Ansible injects a variable for every fact, prefixed with
ansible_. This can result in a large number of variables for each host,
which at scale can incur a performance penalty. Ansible provides a
configuration option [0] that can be set to False to prevent this
injection of facts. In this case, facts should be referenced via
ansible_facts.<fact>.

This change updates all references to Ansible facts within Kolla Ansible
from using individual fact variables to using the items in the
ansible_facts dictionary. This allows users to disable fact variable
injection in their Ansible configuration, which may provide some
performance improvement.

This change disables fact variable injection in the ansible
configuration used in CI, to catch any attempts to use the injected
variables.

[0] https://docs.ansible.com/ansible/latest/reference_appendices/config.html#inject-facts-as-vars

Change-Id: I7e9d5c9b8b9164d4aee3abb4e37c8f28d98ff5d1
Partially-Implements: blueprint performance-improvements
      ade5bfa3
  39. May 12, 2021
  41. Mar 18, 2021
  43. Mar 08, 2021
  45. Feb 08, 2021
  47. Jan 27, 2021
    • Piotr Parczewski's avatar
      [docs] Unify project's naming convention · 5db72659
      Piotr Parczewski authored 
      There are inconsitencies across the documentation and the source code files
when it comes to project's name (Kolla Ansible vs. Kolla-Ansible). This
commit aims at unifying it so that the naming becomes consistent everywhere.

Change-Id: I903b2e08f5458b1a1abc4af3abefe20b66c23a54
      5db72659
  49. Dec 11, 2020
    • Adrian Andreias's avatar
      [docs] Add python3-venv package to quickstart.rst · 43a1e386
      Adrian Andreias authored 
      Python virtual environment creation fails on a fresh system if
python3-venv is not installed (Debian/Ubuntu).

Installation instructions used to be in the Quick Start guide, but
were removed in kolla-ansible/+/735894

Change-Id: I867322ee43d509fe46b6afba9216586515fee0d5
      43a1e386
  51. Nov 20, 2020
    • likui's avatar
      Update docs for Ubuntu 20.04 · a62cce67
      likui authored 
      * Use 'apt install' command instead of legacy 'apt-get'

Change-Id: Idae8d325bce354fa3b4c5be412965122af8f1413
      a62cce67
  53. Oct 29, 2020
    • Mark Goddard's avatar
      docs: Improve multinode Docker registry setup · 34cce4c5
      Mark Goddard authored 
      The multinode guide hints at how to setup the registry as a registry
mirror, however it does not provide all information necessary. This
change fixes that, and separates the local registry and registry mirror
cases.

Change-Id: I0790830e1c21520df2534d2f3b1ea96010064355
Closes-Bug: #1901768
      34cce4c5
  55. Oct 23, 2020
  57. Oct 21, 2020
  59. Oct 14, 2020
  61. Sep 29, 2020
  63. Sep 25, 2020
  65. Sep 23, 2020
  67. Aug 11, 2020
  69. Jun 30, 2020
  71. Jun 18, 2020
    • Konstantinos Mouzakitis's avatar
      Adding support for multiple globals files · f6d8c0d4
      Konstantinos Mouzakitis authored 
      Added a spec file for this blueprint.
Changed the kolla-ansible script to accept more than one
globals.yml file. That will still be the main one but operators
will be able to create more, under the /etc/kolla/globals.d
directory.
Also added some paragraphs in the quickstart documentation
about this.
Finally, Adding a release note

Change-Id: I34eb91d0e2ed80694594b8fc6801cf8ad77da754
Implements: blueprint multiple-globals-files
      f6d8c0d4
  73. May 29, 2020