- Feb 04, 2017
-
-
Jeffrey Zhang authored
Change-Id: I1577cc3afef4dadd3a188c8ba749c9cdfad313ae
-
- Feb 03, 2017
-
-
Eduardo Gonzalez authored
Usernames can be configured with variables in configuration files, but user creation is hardcoded. Change-Id: I057cfb921d776217db66f59226dcfa79f3eb7368 Closes-Bug: #1661587
-
- Jan 26, 2017
-
-
Jeffrey Zhang authored
Co-Authored-By:
Mauricio Lima <mauriciolimab@gmail.com> Change-Id: I9a4a6b6523dee4b388513386b7d85d421f2b7b89
-
- Oct 07, 2016
-
-
Martin Matyáš authored
Genconfig and reconfigure failing for magnum. Chainging magnum trust configuretion parameters to user/domain names instead of ids so they don't depend on register.yml task anymore. Change-Id: I55fddf48eafc44892fd0ab96835bfb0b51849d37 Closes-bug: #1630248
-
- Sep 28, 2016
-
-
Vikram Hosakote authored
This patch set fixes all Magnum issues in kolla master. The [trust] section set to magnum.conf using created trustee domain and user for Magnum in ansible/roles/magnum/tasks/register.yml using ansible openstack modules. Bump shade to 1.5.0 in kolla-toolbox because of os_user_role ansible module dependency. Certificate storage is changed from 'local' (non-production) to magnum's internal storage (x509keypair) or barbican. Co-Authored-By:
Martin Matyas <martinx.maty@intel.com> Change-Id: Ifcb016c0bc4c8c3fc20e063fa05dc8838aae838c Closes-Bug: #1551992
-
- Jul 08, 2016
-
-
ZhongShengping authored
Magnum default service type changed from "container" to "container-infra". It is recommended to update the service type at Keystone service catalog accordingly. Closes-Bug: #1600163 Change-Id: Ief1fed0ef15ab1b86a9500d9a7557828f8e6afc4
-
- Mar 03, 2016
-
-
SamYaple authored
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
-
- Feb 26, 2016
-
-
SamYaple authored
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
-
- Feb 15, 2016
-
-
Dave McCowan authored
To allow for TLS to protect the service endpoints, the protocol in the URLs for the endpoints will be either http or https. This patch removes the hardcoded values of http and replaces them with variables that can be adjusted accordingly in future patches. Change-Id: Ibca6f8aac09c65115d1ac9957410e7f81ac7671e Partially-implements: blueprint ssl-kolla
-
- Feb 02, 2016
-
-
SamYaple authored
This change is needed for clarity. We have a kolla-ansible script. We have a kolla-mesos repo. We plan to have a kolla-ansible repo. Already we have had far too much confusion about whether we are talking about the container or the project. Naming this kolla-toolbox eliminates all of that confusion and its probably a bit more accurate of a name too. Closes-Bug: #1541053 Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e
-
- Nov 13, 2015
-
-
Michal Rostecki authored
Change-Id: Idb25ac4d3148c9b9400cf675ac2e47d35cce6224 Implements: blueprint ansible-magnum
-