Skip to content
Snippets Groups Projects
  1. Aug 03, 2016
  2. 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
    • Ken Wronkiewicz's avatar
      Horizon interface address and memcached override · a6d89f44
      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 and memcached pools, 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
      
      "
      
      Three tings to note:
       * In Kolla-Kubernetes, the service is not using net=host, so a
         0.0.0.0 interface address is totally OK.  That patch has been merged.
       * 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.
       * In order to not duplicate tons of code, moved the keystone_admin_url /
         keystone_internal_url / keystone_public_url to the common defaults
         from the keystone defaults.
      
      Co-Authored-By: default avatarRyan Hallisey <rhallise@redhat.com>
      Change-Id: I586ce1c6c3300254c4e2a398ff46645df576aeb0
      Partially-implements: blueprint api-interface-bind-address-override
      a6d89f44
    • Ken Wronkiewicz's avatar
      Fix interface address for memcached atop kubernetes · 492411f2
      Ken Wronkiewicz authored
      Change-Id: I0fdbef7c5a2bfc13e01c26d8107c7ad03881b520
      Partially-implements: blueprint api-interface-bind-address-override
      Depends-On: Ia0e4951c327be01b717aebb86ef4c3a4e7ed170e
      492411f2
    • Jenkins's avatar
      Merge "Change config for lbaas service_plugins" · 5ce4de6b
      Jenkins authored
      5ce4de6b
    • Lu lei's avatar
      Using sys.exit(main()) instead of main() · 684b483f
      Lu lei authored
      As we known, Exceptions are raised by the sys.exit() function. When they
      are not handled, no stack traceback is printed in the Python interpreter.
      
      In this patch we have known main() got return values(eg:0, 1), but
      it can't specifies exit status when terminate the main thread by
      unusing sys.exit(). So when using sys.exit(main()) instead of main()
      may be more readable and reasonable.
      TrivialFix.
      
      Change-Id: I184289d28b92a7e345907247c045535a0c42c974
      684b483f
  3. Aug 01, 2016
  4. Jul 31, 2016
  5. Jul 29, 2016
  6. Jul 28, 2016
  7. Jul 27, 2016
  8. Jul 26, 2016
Loading