Skip to content
Snippets Groups Projects
  • Jim Rollenhagen's avatar
    bece976b
    Allow keystone services to use independent hostnames · bece976b
    Jim Rollenhagen authored
    This allows keystone service endpoints to use custom hostnames, and adds the
    following variables:
    
    * keystone_internal_fqdn
    * keystone_external_fqdn
    
    These default to the old values of kolla_internal_fqdn or
    kolla_external_fqdn.
    
    This also adds the following variables:
    
    * keystone_admin_listen_port
    * keystone_public_listen_port
    
    These default to keystone_admin_port and keystone_public_port,
    respectively, 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: I50c46c674134f9958ee4357f0f4eed5483af2214
    Implements: blueprint service-hostnames
    bece976b
    History
    Allow keystone services to use independent hostnames
    Jim Rollenhagen authored
    This allows keystone service endpoints to use custom hostnames, and adds the
    following variables:
    
    * keystone_internal_fqdn
    * keystone_external_fqdn
    
    These default to the old values of kolla_internal_fqdn or
    kolla_external_fqdn.
    
    This also adds the following variables:
    
    * keystone_admin_listen_port
    * keystone_public_listen_port
    
    These default to keystone_admin_port and keystone_public_port,
    respectively, 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: I50c46c674134f9958ee4357f0f4eed5483af2214
    Implements: blueprint service-hostnames