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-11-07T17:57:54+00:00 xionglingfeng xionglingfeng@Gmail.com 2016-02-14T03:20:46+00:00 urn:sha1:17e6e629f5660a364498b2bfd2f5aa6aede79859 Allow cinder-volume, nova-compute and nova-libvirtd to be configured to use NFS. In order to mount and work with NFS shares, several containers needed the NFS packages installed during build time. One somewhat significant change is the addition of an explicit bind volume for nova-compute that has shared mounts enabled. According to docker-run(1), the shared mount propagation flag can only be specified for bind mounted Docker volumes and not named volumes. In an NFS setup, cinder-volume mounts the NFS shares so that it can create and manage the Cinder volumes. When a new instance is created with a Cinder volume or a Cinder volume is attached to an existing instance, nova-compute mounts the Cinder volume from the NFS share for nova-libvirtd. In order for nova-libvirtd to then see those Cinder volumes the shared mounts flag must be enabled for the Docker volume. Remove the rpcbind container as it is only necessary for operators who are using NFSv3 or lower. There is no known need for this currently however, this container can be added in the future should an operator require it. Co-authored-by: Ryan Hallisey <rhallise@redhat.com> Co-authored-by: Andrew Widdersheim <amwiddersheim@gmail.com> Change-Id: Iad77c05bce8876bdcc69b7ec22edd50e3bf48b9f Closes-Bug: #1530515 Partially implements: blueprint nfs-support-in-cinder 2016-10-13T09:49:07+00:00 Vladislav Belogrudov vladislav.belogrudov@oracle.com 2016-10-13T09:49:07+00:00 urn:sha1:a0da381d00347a1de51dedff3e6a5c84fec574fd cinder_volume_group property is not seen by precheck tasks - moving it to common group variables. Change-Id: Id7614bb428bb0bf7217eab71b3ec28189e4032b5 Closes-Bug: #1631569 2016-09-26T09:40:15+00:00 caoyuan cao.yuan@99cloud.net 2016-09-23T00:16:51+00:00 urn:sha1:cfe93911dadd710ca5041726d625aa8959bcc7e6 When use "openstack endpoint list" to list the endpoints of cinder service, the url is not right. This patch fix it. closes-Bug: #1627061 Change-Id: I43756421680f4ce59f7cbfb02509aa96c9e5ca9b 2016-09-13T15:39:56+00:00 Paul Bourke paul.bourke@oracle.com 2016-08-11T15:18:01+00:00 urn:sha1:233090300ea4acee033f64bd7975c7031aaf8cfb Add a service check for Cinder when using iscsi/LVM, that the appropriate volume group exists. TrivialFix Change-Id: I54e01911709db73549334760498b4246fe6271d7 Co-Authored-By: Vladislav Belogrudov <vladislav.belogrudov@oracle.com> 2016-07-25T01:50:12+00:00 Jeffrey Zhang jeffrey.zhang@99cloud.net 2016-07-23T14:48:54+00:00 urn:sha1:1b0e701402c5105bad98395b974b9edb4c20dd36 Remove the unnecessary option in the group_vars/all.yml file. * removed some cinder.conf options like volume_backend_name, iscsi_helper, iscsi_protocol etc. these value can be configured by custom cinder.conf file, no need export as global variables. * remove meaningless iscsi_ip_addess, which is not used in LVM driver * force start iscsi relate when enable_cinder_backend_lvm is yes TrivialFix Change-Id: Ifcbfdad15e4d68bc5f20fc77e0315a09983ef022 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-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-15T12:37:30+00:00 venkatamahesh venkatamaheshkotha@gmail.com 2016-02-04T13:41:05+00:00 urn:sha1:70de590a11528105b56d5c549a8436c34b88426a Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4