Skip to content
Snippets Groups Projects
  1. 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
  2. Jun 09, 2022
    • Will Szumski's avatar
      Add keystone_authtoken.service_type · 49006e56
      Will Szumski authored
      Fixes an issue where access rules failed to validate:
      
          Cannot validate request with restricted access rules. Set
          service_type in [keystone_authtoken] to allow access rule validation
      
      I've used the values from the endpoint. This was mostly a straight
      forward copy and paste, except:
      
      - versioned endpoints e.g cinderv3 where I stripped the version
      - monasca has multiple endpoints associated with a single service. For
        this, I concatenated logging and monitoring to be logging-monitoring.
      
      Closes-Bug: #1965111
      Change-Id: Ic4b3ab60abad8c3dd96cd4923a67f2a8f9d195d7
      49006e56
  3. May 28, 2022
    • Radosław Piliszek's avatar
      Do not use keystone_admin_url et al · 7ca9349b
      Radosław Piliszek authored
      Following up on [1].
      The 3 variables are only introducing noise after we removed
      the reliance on Keystone's admin port.
      
      [1] I5099b08953789b280c915a6b7a22bdd4e3404076
      
      Change-Id: I3f9dab93042799eda9174257e604fd1844684c1c
      7ca9349b
  4. Feb 01, 2022
  5. Jun 22, 2021
  6. Sep 22, 2020
    • Pierre Riteau's avatar
      Reduce the use of SQLAlchemy connection pooling · c8177202
      Pierre Riteau authored
      When the internal VIP is moved in the event of a failure of the active
      controller, OpenStack services can become unresponsive as they try to
      talk with MariaDB using connections from the SQLAlchemy pool.
      
      It has been argued that OpenStack doesn't really need to use connection
      pooling with MariaDB [1]. This commit reduces the use of connection
      pooling via two configuration options:
      
      - max_pool_size is set to 1 to allow only a single connection in the
        pool (it is not possible to disable connection pooling entirely via
        oslo.db, and max_pool_size = 0 means unlimited pool size)
      - lower connection_recycle_time from the default of one hour to 10
        seconds, which means the single connection in the pool will be
        recreated regularly
      
      These settings have shown better reactivity of the system in the event
      of a failover.
      
      [1] http://lists.openstack.org/pipermail/openstack-dev/2015-April/061808.html
      
      Change-Id: Ib6a62d4428db9b95569314084090472870417f3d
      Closes-Bug: #1896635
      c8177202
  7. Sep 17, 2020
    • Mark Goddard's avatar
      Support TLS encryption of RabbitMQ client-server traffic · 761ea9a3
      Mark Goddard authored
      This change adds support for encryption of communication between
      OpenStack services and RabbitMQ. Server certificates are supported, but
      currently client certificates are not.
      
      The kolla-ansible certificates command has been updated to support
      generating certificates for RabbitMQ for development and testing.
      
      RabbitMQ TLS is enabled in the all-in-one source CI jobs, or when
      The Zuul 'tls_enabled' variable is true.
      
      Change-Id: I4f1d04150fb2b5af085b762890092f87ae6076b5
      Implements: blueprint message-queue-ssl-support
      761ea9a3
  8. Aug 06, 2020
  9. Jul 22, 2020
  10. Jul 09, 2020
  11. Apr 30, 2020
    • James Kirsch's avatar
      Add support for encrypting Glance api · f87814f7
      James Kirsch authored
      Add TLS support for Glance api using HAProxy to perform TLS termination.
      
      Change-Id: I77051baaeb5d3f7dd9002262534e7d35f3926809
      Partially-Implements: blueprint add-ssl-internal-network
      f87814f7
  12. Apr 03, 2020
  13. Feb 21, 2020
    • Michal Nasiadka's avatar
      Stop using deprecated stores and default_store in glance · f031560f
      Michal Nasiadka authored
      Option "stores" from group "glance_store" is deprecated for removal
      Option "default_store" from group "glance_store" is deprecated for removal
      
      Multi store support is available since Rocky - time to start using
      it.
      
      Change-Id: I4991d754e34ec42a4b38331839d9679b307589bd
      f031560f
  14. Jan 29, 2020
    • Michal Nasiadka's avatar
      External Ceph: add ceph_*_user variables · fdf3729f
      Michal Nasiadka authored
      To make the configuration easier for the user, and to allow non-standard
      ceph authentication ids - introduce ceph_*_user variables.
      
      Change-Id: I24e01c43c826b62b6748d93a498f4b7d8ce9e309
      fdf3729f
  15. Jan 13, 2020
    • James Kirsch's avatar
      Configure services to use Certificate Authority · c15dc203
      James Kirsch authored
      Include a reference to the globally configured Certificate Authority to
      all services. Services use the CA to verify HTTPs connections.
      
      Change-Id: I38da931cdd7ff46cce1994763b5c713652b096cc
      Partially-Implements: blueprint support-trusted-ca-certificate-file
      c15dc203
  16. 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
  17. Sep 20, 2019
    • Mark Goddard's avatar
      Remove some deprecated config options · e127627d
      Mark Goddard authored
      Heat's [DEFAULT] deferred_auth_method is deprecated, and we are setting
      the default value of 'trusts'.
      
      Glance's [DEFAULT] registry_host is deprecated, and we do not deploy a
      registry.
      
      Change-Id: I80024907c575982699ce323cd9a93bab94c988d3
      e127627d
  18. Mar 06, 2019
    • Jim Rollenhagen's avatar
      Use keystone_*_url var in all configs · 2e4e6050
      Jim Rollenhagen authored
      We're duplicating code to build the keystone URLs in nearly every
      config, where we've already done it in group_vars. Replace the
      redundancy with a variable that does the same thing.
      
      Change-Id: I207d77870e2535c1cdcbc5eaf704f0448ac85a7a
      2e4e6050
  19. Feb 08, 2019
    • Jim Rollenhagen's avatar
      Allow glance services to use independent hostnames · a819ef12
      Jim Rollenhagen authored
      This allows glance service endpoints to use custom hostnames, and adds the
      following variables:
      
      * glance_internal_fqdn
      * glance_external_fqdn
      
      These default to the old values of kolla_internal_fqdn or
      kolla_external_fqdn.
      
      This also adds a glance_api_listen_port option, which defaults to
      glance_api_port for backward compatibility.
      
      This option 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: Icb91f728533e2db1908b23dabb0501cf9f8a2b75
      Implements: blueprint service-hostnames
      a819ef12
  20. Dec 05, 2018
  21. Nov 21, 2018
    • Eduardo Gonzalez's avatar
      Add glance-cache support · cc9dae4d
      Eduardo Gonzalez authored
      Glance cache is used to keep a locally cache image
      in the glance_api service.
      Is an usefull service when an image is commonly used
      to speed times between pulling from storage backend
      and send to nova.
      
      Change-Id: I8e684cc10e4fee1cb52c17a126e3b11f69576cf6
      cc9dae4d
  22. Aug 07, 2018
  23. Jul 20, 2018
    • Joshua Harlow's avatar
      Allow externally managed swift as glance backend · 07dfc202
      Joshua Harlow authored
      
      It is possible to have an accessible swift API that is not managed by
      kolla-ansible -- for example, ceph exposes a swift API, and using that
      requires setting swift as the glance backend.
      
      So, we should loosen the requirement that using the swift backend for
      glance requires swift be enabled in kolla-ansible.
      
      Co-Authored-By: default avatarAdam Harwell <flux.adam@gmail.com>
      
      Change-Id: I17076d5412d2b1e1f13bb0badceaca85a5cee108
      07dfc202
  24. Jun 01, 2018
    • Zhangfei Gao's avatar
      osprofiler support redis · ce809aea
      Zhangfei Gao authored
      Currently osprofiler only choose elasticsearch,
      which is only supported on x86.
      On other platform like aarch64 osprofiler can
      not be used since no elasticsearch package.
      
      Enable osprofiler by enable_osprofiler: "yes",
      which choose elasticsearch by default.
      Choose redis by enable_redis: "yes" & osprofiler_backend: "redis"
      On platform without elasticsearch support like aarch64
      set enable_elasticsearch: "no"
      
      Change-Id: I68fe7a33e11d28684962fc5d0b3d326e90784d78
      ce809aea
  25. Apr 18, 2018
    • Kevin TIBI's avatar
      Fix SSL api for multiple services · a81a5d5d
      Kevin TIBI authored
      If SSL is enabled, api of multiple services returns
      wrong external URL without https prefix.
      
      Removal of condition for deletion of http  header.
      
      Change-Id: I4264e04d0d6b9a3e11ef7dd7add6c5e166cf9fb4
      Closes-Bug: #1749155
      Closes-Bug: #1717491
      a81a5d5d
  26. Mar 21, 2018
    • Joshua Harlow's avatar
      Have glance notifications work like the other projects · 98d1e453
      Joshua Harlow authored
      Currently glance has a very simplistic ability to configure
      notifications which seems different than nova and neutron which
      both allow for selecting the topics used. In order to make glance
      work like the others just have glance be configured like the other
      projects notifications are being configured.
      
      Change-Id: Ia12993e1b86d040c2705e72b32f93b874fe4adc6
      98d1e453
  27. Jan 29, 2018
  28. Jan 03, 2018
    • caoyuan's avatar
      fix the tempest failure for external ceph · d8f6c76f
      caoyuan authored
      
      show_multiple_locations is missing for external ceph, and it will
      cause tempest run failed.
      it means the conditon for show_multiple_locations is
      glance_backend_ceph but not enable_ceph, this patch it fix it.
      
      Change-Id: I3c95c3b0a7e34639b376bdfd0205f3930b06e2cd
      Closes-Bug: #1741022
      Co-Authored-By: default avatarchenqiaomin <chen.qiaomin@99cloud.net>
      d8f6c76f
  29. Dec 27, 2017
  30. Nov 22, 2017
    • Andrew Smith's avatar
      Add support for hybrid messaging backends · fd1d3af0
      Andrew Smith authored
      This commit separates the messaging rpc and notify transports in order
      to support separate and different oslo.messaging backends
      
      This patch:
      * add rpc and notify variables
      * update service role conf templates
      * add example to globals.yaml
      * add release note
      
      Implements: blueprint hybrid-messaging
      Change-Id: I34691c2895c8563f1f322f0850ecff98d11b5185
      fd1d3af0
  31. Oct 26, 2017
  32. Sep 21, 2017
    • goldyfruit's avatar
      filesystem_store_datadir should not be set when external Ceph is used · c20cf018
      goldyfruit authored
      When an external Ceph cluster is used, the "filesystem_store_datadir"
      option is set in the "glance-api.conf" configuration file.
      
      It should not, it's because of this condition:
      
        {% elif enable_ceph | bool and glance_backend_ceph | bool %}
      
      When external Ceph cluster is used "enable_ceph" is false and
      "glance_backend_ceph" is true.
      
      glance_backend_ceph variable should be enought for this condition.
      
      Change-Id: I2a2ab420727888cfd9fcbc4bd30a08410163b36e
      Closes-Bug: #1718728
      c20cf018
  33. Aug 17, 2017
  34. Jul 18, 2017
  35. Jul 06, 2017
  36. Jun 28, 2017
    • zhubingbing's avatar
      Modify glance log name · 08c5de20
      zhubingbing authored
      change api.log and registry.log to glance-api.log and glance-registry.log
      
      Closes-bug: #1700718
      
      Change-Id: Ifcde8699fa9537fa06445f79c4bd14b4ee0df32c
      08c5de20
  37. Jun 02, 2017
  38. May 22, 2017
  39. Apr 12, 2017
  40. Nov 21, 2016
Loading