openstack/kolla.git/ansible/roles/keystone/defaults/main.yml, branch master

Remove Ansible from Kolla

2016-11-16T04:34:17+00:00

Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b

Add full support for fernet

2016-08-25T10:08:22+00:00

This addresses the ansible aspects of fernet key bootstrapping as well as distributed key rotation. - Bootstrapping is handled in the same way as keystone bootstrap. - A new keystone-fernet and keystone-ssh container is created to allow the nodes to communicate with each other (taken from nova-ssh). - The keystone-fernet is a keystone container with crontab installed. This will handle key rotations through keystone-manage and trigger an rsync to push new tokens to other nodes. - Key rotation is setup to be balanced across the keystone nodes using a round-robbin style. This ensures that any node failures will not stop the keys from rotating. This is configured by a desired token expiration time which then determines the cron scheduling for each node as well as the number of fernet tokens in rotation. - Ability for recovered node to resync with the cluster. When a node starts it will run sanity checks to ensure that its fernet tokens are not stale. If they are it will rsync with other nodes to ensure its tokens are up to date. The Docker component is implemented in: https://review.openstack.org/#/c/349366 Change-Id: I15052c25a1d1149d364236f10ced2e2346119738 Implements: blueprint keystone-fernet-token

Horizon interface address and memcached override

2016-08-02T16:39:22+00:00

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: Ryan Hallisey Change-Id: I586ce1c6c3300254c4e2a398ff46645df576aeb0 Partially-implements: blueprint api-interface-bind-address-override

Keystones openstack_auth was undefined

2016-07-14T13:40:19+00:00

Keystones openstack_auth is undefined for Keystones sanity check closes-bug: #1601808 Change-Id: I445482ce32b924d9220e8c351363b6793558d3b4

add support for non-default database_port in kolla/ansible

2016-05-13T12:12:25+00:00

This change makes each step of the kolla deployment aware of the port database was configured to listen on. It defaults mariadb_port to database_port. Change-Id: I8e85d5732015afc0a5481cb33e0b629fdfa84a1b Closes-Bug: #1576151 DocImpact

Fix Keystone v3 and Horizon

2016-03-03T15:44:53+00:00

After our switch to keystone-manage bootstrap Horizon is not happy due to v3 not being setup correctly. This patch fixes that This also includes removal of unused variables (transforms them into endpoint url variables) TrivialFix Change-Id: I1e04db8c24049f80e974c063f03068a2ab32a563

Remove keystone admin token

2016-03-01T00:14:06+00:00

Admin token has been deprecated upstream. It will be removed in O. We switch over to the new `keystone-manage bootstrap` method for creating the initial admin user, role, and project. Co-Authored-By: Sam Yaple Change-Id: I6ca90e8d4c3b71009e24b049b2efbc08c05ebfbf

Change kolla_internal_address variable

2016-02-26T20:00:09+00:00

Due to poor planning on our variable names we have a situation where we have "internal_address" which must be a VIP, but "external_address" which should be a DNS name. Now with two vips "external_vip_address" is a new variable. This corrects that issue by deprecating kolla_internal_address and replacing it with 4 nicely named variables. kolla_internal_vip_address kolla_internal_fqdn kolla_external_vip_address kolla_external_fqdn The default behaviour will remain the same, and the way the variable inheritance is setup the kolla_internal_address variable can still be set in globals.yml and propogate out to these 4 new variables like it normally would, but all reference to kolla_internal_address has been completely removed. Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5 Partially-Implements: blueprint ssl-kolla

Use uppercase 'S' in word "OpenStack"

2016-02-15T12:37:30+00:00

Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4

remove option verbose define in defaults/main.yml

2016-01-20T08:17:05+00:00

References: https://review.openstack.org/#/c/269042/ TrivialFix Change-Id: Ief08781342a06f956fc4cf00ba4383759da8c897