Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2018-11-12T02:15:38+00:00 2018-11-12T02:15:38+00:00 Kien Nguyen kiennt65@viettel.com.vn 2018-10-16T10:40:51+00:00 urn:sha1:cf2b2b55b6a6ceb295c574ac5e0bdcdf40687f9c Follow Zaqar installation documentation [1] [1] https://docs.openstack.org/zaqar/latest/install/ Change-Id: Ic356fb81c19ebbc78aa3c7e871c4946d1f712a45 Implements: blueprint ansible-zaqar 2017-05-12T12:40:52+00:00 egonzalez90 dabarren@gmail.com 2017-05-12T11:56:13+00:00 urn:sha1:45c54d7959a04dd95e871d6d00dd0fb84a5126d0 In ubuntu is not evaluating correctly if $user == root check at extend_start. Changing to "$(whoami)" == 'root' fixes the issue Change-Id: I296a1f98764cdfa09650c483bc7beba53e6bdba4 Closes-Bug: #1690360 2017-05-02T13:15:50+00:00 Martin André m.andre@redhat.com 2017-05-02T13:14:36+00:00 urn:sha1:a2c0087b3842c00e27440e69abc3c57125a50cc0 Some projects that use Kolla docker containers (TripleO) run zaqar under httpd. This patch adds the httpd package so that it exists in the container and can optionally by used via Docker entrypoints. As many of these projects do not require the use of Apache (it is opt-in) at this point not all deployment frameworks support the use of it so the existing configuration defaults have been left as-is for now. Change-Id: I35cfd1c2320eb972890b44668c8f9f0a047a65dc Partially-Implements: blueprint apache-packages-for-apis 2017-01-07T12:54:51+00:00 Eduardo Gonzalez dabarren@gmail.com 2016-12-06T19:51:11+00:00 urn:sha1:69e2e9fff15ea9d20d81426cf384fe85177fb69b This PS is part of a rework on zaqar container. In it's current state is not working in kolla. Will be adding/fixing issues under this PS. - Remove bootstrap zaqar: At this point zaqar-manage command does not exist. Boostraping is not needed while starting zaqar container. - Add pymongo package in source install. - Create /var/log/kolla folder. - Change zaqar homedir to /var/lib/zaqar and unify creation. - Zaqar's source default have config files as *.sample. Policy.json need to be present if keystone auth is going to be used. - Zaqar uses wsgi to the API, heka decoder need to be added Change-Id: I9c6716b64345d9e846902ffbfbf033135e3eabd9 Closes-Bug: #1647831 2015-11-13T19:20:36+00:00 Josh Lothian jlothian@cisco.com 2015-11-13T18:10:33+00:00 urn:sha1:63d5e9b5524d5e917dcf9848d74830d6dad08391 Change-Id: I59797a8539406e478f6953a9aa0c933e73eb5892 Partially-Implements: blueprint drop-root 2015-10-13T15:13:55+00:00 Sam Yaple sam@yaple.net 2015-10-13T06:30:30+00:00 urn:sha1:5f200e044648efe64f297d186432839762f91395 Long story short, some kernels before 3.15 had an issue with using su in a container when the network namespace was --net=host. The gate has a 3.10 and a 3.13 kernel and has a problem with this. This changes everything to use sudo backport: liberty Partially-Implements: blueprint functional-testing-gate Change-Id: I4d79ccaa1cddffcc8393f64e7e1be2538efe33e5 2015-10-06T03:30:26+00:00 Sam Yaple sam@yaple.net 2015-09-30T11:23:39+00:00 urn:sha1:cb4e875ae1e1ec2e6ddf8a6b37f42283697fd50c The majority of the start.sh code is identical. This removes that duplicate code while still maintaining the ability to call code in a specific container. The start.sh is moved into /usr/local/bin/kolla_start in the container The extend_start.sh script is called by the kolla_start script at the location /usr/local/bin/kolla_extend_start . It always exists because we create a noop kolla_extend_start in the base directory. We override it with extend_start.sh in a specific image should we need to. Of note, the neutron-agents container is exempt from this new structure due to it being a fat container. Additionally, we fix the inconsistent permissions throughout. 644 for repo files and the scripts are set to 755 via a Docker RUN command to ensure someones local perm change won't break upstream containers. Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad Closes-Bug: #1501295