Skip to content
Snippets Groups Projects
  1. Aug 05, 2016
  2. Aug 04, 2016
  3. Aug 03, 2016
  4. Aug 02, 2016
    • Ken Wronkiewicz's avatar
      Glance interface address, memcached override, and glance override. · 85db94e5
      Ken Wronkiewicz authored
      Note: This should not result in any behavior changes in regular Kolla, just
      Kolla-Kubernetes and only when you've overridden stuff in globals.yml
      
      Allows override of interface address, memcached pools, and glance registry
      host so that Kubernetes can do the right thing.
      
      There are some significant architectural issues involved in memcached pooling
      in the Kolla-kubernetes world.  Avoiding them right now.
      
      Current working with this Kolla-Kubernetes globals.yml file:
      
      api_interface_address: "0.0.0.0"
      
      memcached_servers: "memcached"
      
      keystone_database_address: "mariadb"
      keystone_admin_url: "http://keystone-admin:35357/v3"
      keystone_internal_url: "http://keystone-public:5000/v3"
      keystone_public_url: "http://keystone-public:5000/v3
      
      "
      glance_registry_host: "glance-registry"
      
      Two tings to note:
       * This depends on a kolla-kubernetes patch, so that it won't be merged
         until it's safe for glance to bind to 0.0.0.0.  It's OK to bind to
         0.0.0.0 in the Kubernetes world because the network fabric controls
         access.
       * In Kolla-Kubernetes, the global.yml file doesn't do var substitution
         so you have to be explicit about the URLs, otherwise Keystone will
         look like it was provisioned but it won't quite be provisioned right.
      
      Co-Authored-By: default avatarRyan Hallisey <rhallise@redhat.com>
      Change-Id: Ic87566118a1d4f552748392ff394b9b121c91887
      Partially-implements: blueprint api-interface-bind-address-override
      Depends-On: I586ce1c6c3300254c4e2a398ff46645df576aeb0
      85db94e5
Loading