Skip to content
Snippets Groups Projects
  1. Sep 29, 2021
  2. Sep 27, 2021
    • Zuul's avatar
      Merge "CI: Fix bashate ignores" · f9e31f0b
      Zuul authored
      f9e31f0b
    • Zuul's avatar
      Merge "Remove haproxy and keepalived groups" · 0d142f93
      Zuul authored
      0d142f93
    • Zuul's avatar
      Merge "Revert to Xena IPA images" · 568a5598
      Zuul authored
      568a5598
    • Mark Goddard's avatar
      Make setup module arguments configurable · 2648f487
      Mark Goddard 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 (kayobe_ansible_setup_gather_subset) and which facts are stored
      (kayobe_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 kayobe_ansible_setup_filter
      variable to help:
      
          kayobe_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 Kayobe.
      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.
      
      This change also introduces a new command to gather facts for Kayobe &
      Kolla Ansible on demand, 'kayobe overcloud facts gather'. This can be
      used to populate a fact cache.
      
      Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/794610
      Story: 2007993
      Task: 42586
      
      Change-Id: I5ce3c734433e1682ee942867505468c57440e689
      2648f487
    • Mark Goddard's avatar
      Support Ansible collections · 5535832c
      Mark Goddard authored
      This change adds support for installing Ansible collections via
      requirements.yml in Kayobe or Kayobe config.
      
      Story: 2008391
      Task: 41315
      
      Change-Id: I764ff019a18266b593add7ab80ee095d7d07a869
      5535832c
  3. Sep 23, 2021
  4. Sep 21, 2021
  5. Sep 20, 2021
  6. Sep 17, 2021
  7. Sep 16, 2021
  8. Sep 15, 2021
  9. Sep 14, 2021
  10. Sep 10, 2021
  11. Sep 09, 2021
  12. Sep 08, 2021
  13. Sep 07, 2021
  14. Sep 05, 2021
  15. Sep 03, 2021
  16. Sep 01, 2021
  17. Aug 31, 2021
  18. Aug 26, 2021
  19. Aug 21, 2021
    • Mark Goddard's avatar
      Use ansible_facts to reference facts · f639ad0b
      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 Kayobe
      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
      
      Story: 2007993
      Task: 42464
      Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/791276
      
      Change-Id: I14db53ed6e57d37bbd28dd5819e432e3fe6628b2
      f639ad0b
  20. Aug 20, 2021
    • Mark Goddard's avatar
      Fix configuration check without public API network · 3c56f32f
      Mark Goddard authored
      If no public API network is used, as in the case of typical all-in-one
      environments, the checks in kolla-ansible.yml, task "Validate Kolla
      Ansible API address configuration" may fail. This happens only when
      using the new kolla_internal_vip_address variable, and not if the legacy
      vip_address network attribute is used.
      
      This change fixes the issue by only checking for valid external VIP
      address/FQDN configuration when a separate public API network is in use.
      If the external VIP/FQDN are not set, then Kayobe no longer defaults
      their values to the internal VIP/FQDN, instead relying on the Kolla
      Ansible defaults to do this. This may have consequences for anyone
      relying on these variables in configuration.
      
      Change-Id: I0b1c963006c044ade5c67c4046da5e2addc9a8c7
      Story: 2009134
      Task: 43070
      3c56f32f
  21. Aug 19, 2021
Loading