Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2016-11-16T04:34:17+00:00 2016-11-16T04:34:17+00:00 Steven Dake stdake@cisco.com 2016-11-16T02:01:25+00:00 urn:sha1:3fcef82946f7053affcfb0b1b3ef4292beb9fa95 Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b 2016-08-07T10:06:02+00:00 Jeffrey Zhang jeffrey.zhang@99cloud.net 2016-07-28T14:58:58+00:00 urn:sha1:1ce1cd10fe867d002b0e87013e236842c4af68a6 * Use the nova microversion api for compute service * Use the legacy nova api for compute_legacy service * Update the nova service and endpoint during the upgrade stage This is what the devstack used now[0] [0] https://github.com/openstack-dev/devstack/blob/e777bbce3b18ce50abe683a2d96394e96a3b70bc/lib/nova#L408,L422 TrivialFix Change-Id: I0574a3116b1dd1702b4eccb2394538866675c4c1 2016-03-03T15:44:53+00:00 SamYaple sam@yaple.net 2016-03-01T14:38:47+00:00 urn:sha1:57124620ab633216bb2110670f3b4284ab945cba 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 2016-02-26T20:00:09+00:00 SamYaple sam@yaple.net 2016-02-26T01:02:25+00:00 urn:sha1:d3cfb2052a7321606e3a46fd6846f776d28afd86 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 2016-02-15T14:48:58+00:00 Dave McCowan dmccowan@cisco.com 2016-02-12T17:37:13+00:00 urn:sha1:1cedf77f19ccd0b01791553016fde77748a2ce74 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 2016-02-02T18:12:15+00:00 SamYaple sam@yaple.net 2016-01-29T16:40:54+00:00 urn:sha1:80b7266ed1b10fb302a507d250d28a964ce14e49 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 2015-08-06T01:32:05+00:00 Sam Yaple sam@yaple.net 2015-08-03T07:50:01+00:00 urn:sha1:98a379b0fd0c24da6bfc5b9828aa5e734788c9bc Currently we require a slew of deps on each destination node, this includes a gcc compiler and installing things via pip. We can remove these dependencies by containerizing them and running and Ansible inside the container itself. The container would then report back facts about idempotency. DocImpact Closes-Bug: #1481495 Implements: blueprint containerize-dependencies Change-Id: I3dfccbf9fafc06ffc36e78f3006fe5d3367891df 2015-07-31T22:40:21+00:00 Sam Yaple sam@yaple.net 2015-07-31T21:55:22+00:00 urn:sha1:8e03952c1009353f3e5f898dbb671a7529af80de Bundling in a run_once error that beaks with multinode and the race Change-Id: Ia3779d9a291f8d652fc81fe5ebcab88241805c8d Closes-Bug: #1480468 2015-07-12T12:44:14+00:00 Sam Yaple sam@yaple.net 2015-07-12T03:02:33+00:00 urn:sha1:7da0b2a80c093661766f9998760be8844584b0cc Initial support for Nova in Ansible Partially-Implements: blueprint ansible-service Change-Id: I4b0a74bd3e5daa5664f5e1e622bfb40c3285949e