Skip to content
Snippets Groups Projects
  1. Jan 27, 2025
  2. Sep 28, 2022
  3. Jul 12, 2022
    • Michal Arbet's avatar
      Add api_workers for each service to defaults · 3e8db91a
      Michal Arbet authored
      Render {{ openstack_service_workers }} for workers
      of each openstack service is not enough. There are
      several services which has to have more workers because
      there are more requests sent to them.
      
      This patch is just adding default value for workers for
      each service and sets {{ openstack_service_workers }} as
      default, so value can be overrided in hostvars per server.
      Nothing changed for normal user.
      
      Change-Id: Ifa5863f8ec865bbf8e39c9b2add42c92abe40616
      3e8db91a
  4. Apr 05, 2022
  5. Mar 04, 2021
    • Doug Szumski's avatar
      Add variable for changing Apache HTTP timeout · 647ff667
      Doug Szumski authored
      In services which use the Apache HTTP server to service HTTP requests,
      there exists a TimeOut directive [1] which defaults to 60 seconds. APIs
      which come under heavy load, such as Cinder, can sometimes exceed this
      which results in a HTTP 504 Gateway timeout, or similar. However, the
      request can still be serviced without error. For example, if Nova calls
      the Cinder API to detach a volume, and this operation takes longer
      than the shortest of the two timeouts, Nova will emit a stack trace
      with a 504 Gateway timeout. At some time later, the request to detach
      the volume will succeed. The Nova and Cinder DBs then become
      out-of-sync with each other, and frequently DB surgery is required.
      
      Although strictly this category of bugs should be fixed in OpenStack
      services, it is not realistic to expect this to happen in the short
      term. Therefore, this change makes it easier to set the Apache HTTP
      timeout via a new variable.
      
      An example of a related bug is here:
      
      https://bugs.launchpad.net/nova/+bug/1888665
      
      Whilst this timeout can currently be set by overriding the WSGI
      config for individual services, this change makes it much easier.
      
      Change-Id: Ie452516655cbd40d63bdad3635fd66693e40ce34
      Closes-Bug: #1917648
      647ff667
  6. Oct 16, 2020
  7. Aug 24, 2020
    • Radosław Piliszek's avatar
      Drop python-path · 9c38a0c7
      Radosław Piliszek authored
      It was found to be useless in [1].
      
      It is one of distro_python_version usages.
      
      Note Freezer and Horizon still use python_path (and hence
      distro_python_version) for different purposes.
      
      [1] https://review.opendev.org/675822
      
      Change-Id: I6d6d9fdf4c28cb2b686d548955108c994b685bb1
      Partially-Implements: blueprint drop-distro-python-version
      9c38a0c7
  8. Aug 13, 2020
    • James Kirsch's avatar
      Add Keep Alive Timeout for httpd · 19b028e6
      James Kirsch authored
      This patch introduces a global keep alive timeout value for services
      that leverage httpd + wsgi to handle http/https requests. The default
      value is one minute.
      
      Change-Id: Icf7cb0baf86b428a60a7e9bbed642999711865cd
      Partially-Implements: blueprint add-ssl-internal-network
      19b028e6
  9. Apr 30, 2020
    • James Kirsch's avatar
      Add support for encrypting Horizon and Placement API · e3d5a91a
      James Kirsch authored
      This patch introduces an optional backend encryption for Horizon and
      Placement services. When used in conjunction with enabling TLS for
      service API endpoints, network communcation will be encrypted end to
      end, from client through HAProxy to the Horizon and Placement services.
      
      Change-Id: I9cb274141c95aea20e733baa623da071b30acf2d
      Partially-Implements: blueprint add-ssl-internal-network
      e3d5a91a
  10. Jan 30, 2020
    • Mark Goddard's avatar
      Python 3: Use distro_python_version for WSGI python_path · c56d273c
      Mark Goddard authored
      Currently the WSGI configuration for binary images uses python2.7
      site-packages in some places. This change uses distro_python_version to
      select the correct python path.
      
      Change-Id: Id5f3f0ede106498b9264942fa0399d7c7862c122
      Partially-Implements: blueprint python-3
      c56d273c
  11. Oct 24, 2019
  12. Oct 16, 2019
    • Radosław Piliszek's avatar
      Implement IPv6 support in the control plane · bc053c09
      Radosław Piliszek authored
      Introduce kolla_address filter.
      Introduce put_address_in_context filter.
      
      Add AF config to vars.
      
      Address contexts:
      - raw (default): <ADDR>
      - memcache: inet6:[<ADDR>]
      - url: [<ADDR>]
      
      Other changes:
      
      globals.yml - mention just IP in comment
      
      prechecks/port_checks (api_intf) - kolla_address handles validation
      
      3x interface conditional (swift configs: replication/storage)
      
      2x interface variable definition with hostname
      (haproxy listens; api intf)
      
      1x interface variable definition with hostname with bifrost exclusion
      (baremetal pre-install /etc/hosts; api intf)
      
      neutron's ml2 'overlay_ip_version' set to 6 for IPv6 on tunnel network
      
      basic multinode source CI job for IPv6
      
      prechecks for rabbitmq and qdrouterd use proper NSS database now
      
      MariaDB Galera Cluster WSREP SST mariabackup workaround
      (socat and IPv6)
      
      Ceph naming workaround in CI
      TODO: probably needs documenting
      
      RabbitMQ IPv6-only proto_dist
      
      Ceph ms switch to IPv6 mode
      
      Remove neutron-server ml2_type_vxlan/vxlan_group setting
      as it is not used (let's avoid any confusion)
      and could break setups without proper multicast routing
      if it started working (also IPv4-only)
      
      haproxy upgrade checks for slaves based on ipv6 addresses
      
      TODO:
      
      ovs-dpdk grabs ipv4 network address (w/ prefix len / submask)
      not supported, invalid by default because neutron_external has no address
      No idea whether ovs-dpdk works at all atm.
      
      ml2 for xenapi
      Xen is not supported too well.
      This would require working with XenAPI facts.
      
      rp_filter setting
      This would require meddling with ip6tables (there is no sysctl param).
      By default nothing is dropped.
      Unlikely we really need it.
      
      ironic dnsmasq is configured IPv4-only
      dnsmasq needs DHCPv6 options and testing in vivo.
      
      KNOWN ISSUES (beyond us):
      
      One cannot use IPv6 address to reference the image for docker like we
      currently do, see: https://github.com/moby/moby/issues/39033
      (docker_registry; docker API 400 - invalid reference format)
      workaround: use hostname/FQDN
      
      RabbitMQ may fail to bind to IPv6 if hostname resolves also to IPv4.
      This is due to old RabbitMQ versions available in images.
      IPv4 is preferred by default and may fail in the IPv6-only scenario.
      This should be no problem in real life as IPv6-only is indeed IPv6-only.
      Also, when new RabbitMQ (3.7.16/3.8+) makes it into images, this will
      no longer be relevant as we supply all the necessary config.
      See: https://github.com/rabbitmq/rabbitmq-server/pull/1982
      
      For reliable runs, at least Ansible 2.8 is required (2.8.5 confirmed
      to work well). Older Ansible versions are known to miss IPv6 addresses
      in interface facts. This may affect redeploys, reconfigures and
      upgrades which run after VIP address is assigned.
      See: https://github.com/ansible/ansible/issues/63227
      
      Bifrost Train does not support IPv6 deployments.
      See: https://storyboard.openstack.org/#!/story/2006689
      
      
      
      Change-Id: Ia34e6916ea4f99e9522cd2ddde03a0a4776f7e2c
      Implements: blueprint ipv6-control-plane
      Signed-off-by: default avatarRadosław Piliszek <radoslaw.piliszek@gmail.com>
      bc053c09
  13. Sep 09, 2019
  14. Apr 10, 2019
    • Mark Goddard's avatar
      Fix ubuntu binary deploys · d62ccca3
      Mark Goddard authored
      1. The Keystone WSGI scripts don't have a python3- prefix, although they
         are using python 3.
      
      2. The Placement WSGI script doesn't have a python3- prefix, although it
         is using python 3.
      
      Depends-On: https://review.openstack.org/651327
      Change-Id: I805df8f85634edea8322495ca73897d44967cfe6
      Closes-Bug: #1823989
      d62ccca3
  15. Mar 15, 2019
  16. Mar 13, 2019
  17. Feb 08, 2019
    • Jim Rollenhagen's avatar
      Allow nova services to use independent hostnames · 51c9e1b6
      Jim Rollenhagen authored
      This allows nova service endpoints to use custom hostnames, and adds the
      following variables:
      
      * nova_internal_fqdn
      * nova_external_fqdn
      * placement_internal_fqdn
      * placement_external_fqdn
      * nova_novncproxy_fqdn
      * nova_spicehtml5proxy_fqdn
      * nova_serialproxy_fqdn
      
      These default to the old values of kolla_internal_fqdn or
      kolla_external_fqdn.
      
      This also adds the following variables:
      
      * nova_api_listen_port
      * nova_metadata_listen_port
      * nova_novncproxy_listen_port
      * nova_spicehtml5proxy_listen_port
      * nova_serialproxy_listen_port
      * placement_api_listen_port
      
      These default to <service>_port, e.g. nova_api_port, for backward
      compatibility.
      
      These options allow the user to differentiate between the port the
      service listens on, and the port the service is reachable on. This is
      useful for external load balancers which live on the same host as the
      service itself.
      
      Change-Id: I7bcce56a2138eeadcabac79dd07c8dba1c5af644
      Implements: blueprint service-hostnames
      51c9e1b6
  18. Jan 04, 2019
    • Kien Nguyen's avatar
      Use <project>_install_type instead of kolla_install_type · 04394311
      Kien Nguyen authored
      Use <project>_install_type instead of kolla_install_type
      to set python_path. For example, general kolla_install_type
      is 'binary', but user wants to deploy Horizon from 'source'.
      Horizon templates still use python_path=/usr/share/openstack-dashboard,
      it is wrong.
      
      Change-Id: Ide6a24e17b1f8ab6506aa5e53f70693706830418
      04394311
  19. Mar 14, 2018
  20. Jul 19, 2017
  21. Feb 02, 2017
Loading