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-10-11T14:33:36+00:00 Paul Bourke paul.bourke@oracle.com 2016-10-11T14:29:00+00:00 urn:sha1:0e0fedb05b70a6e51257ab8966499434ac79c2f9 Some base image distros don't ship new enough versions of libvirt/qemu to support hw_disk_discard in Nova (libvirt (1, 0, 6) or later and qemu (1, 6, 0) or later). When deploying Nova with Ceph enabled this config item is automatically turned on, we should give operators a chance to disable it. Change-Id: I0b2615c64a9569c09567bf456815f93254d90ade Closes-Bug: #1632348 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-05-13T12:12:25+00:00 Waldemar Znoinski waldemar.znoinski@intel.com 2016-05-06T14:51:55+00:00 urn:sha1:a2c2eba34fb7077346d651918dfb22a53a63cb00 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 2016-04-03T07:21:17+00:00 Jeffrey Zhang jeffrey.zhang@99cloud.net 2016-03-26T16:39:07+00:00 urn:sha1:42420830f65c0a76ba8e7e1b6a8d2974dabb9cfa Add a nova-ssh container to handle the `nova migrate` and `nova resize` case, in which the nova will use ssh to copy files between machines. Change-Id: Ie6675943f3aeabfbba8589d308d55b9c89d732db Closes-Bug: #1562141 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-29T18:40:15+00:00 SamYaple sam@yaple.net 2016-02-29T15:08:30+00:00 urn:sha1:f1bf9a4a1eb0fa83618d0cf6e0e7f6f531d066af This follows the structure we have for Ironic and Nova Closes-Bug: #1551316 Change-Id: I609e3dda40c65b73bb5e1208f702740416a042ed 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-15T12:37:30+00:00 venkatamahesh venkatamaheshkotha@gmail.com 2016-02-04T13:41:05+00:00 urn:sha1:70de590a11528105b56d5c549a8436c34b88426a Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4 2016-02-02T21:56:54+00:00 SamYaple sam@yaple.net 2016-02-01T23:01:59+00:00 urn:sha1:e7dfd63bfc5cfba0117c410d418feaff0f7999f3 This is a required patch. Kilo introduced a nova-api database but didn't use it. [1] Mitaka now uses it and has broken booting instances. [2] [1] https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Compute_.28Nova.29 [2] https://github.com/openstack/nova/blob/df0fca62cf5324f5b6eae0fed1f88c6c9ed61c71/releasenotes/notes/request-spec-api-db-b9cc6e0624d563c5.yaml Change-Id: If0a7f4ba4937fab8d60f5236ca00db06faa768c7 Closes-Bug: #1540579