summaryrefslogtreecommitdiff
path: root/docker
AgeCommit message (Collapse)AuthorFilesLines
2015-11-17Merge "Use pip upper-constraints in magnum-base"Jenkins1-1/+1
2015-11-17Merge "Fix issues in Glance filesystem backend"Jenkins3-1/+7
2015-11-17Drop root for MagnumPaul Bourke3-1/+5
This change ensures commands run in the magnum containers are done as the 'magnum' user rather than root. Change-Id: I18e2febae98aae6d6fc6c61cc2817442f408cb75 Partially-Implements: blueprint drop-root
2015-11-17Remove old config-external.sh scripts for magnumPaul Bourke2-20/+0
These are no longer used. Trivial-Fix Change-Id: Ia4dced3b8ac8512097f5cafbb1b06661c6f3eb88
2015-11-17Use pip upper-constraints in magnum-basePaul Bourke1-1/+1
Change-Id: Ibb5636d897c2b9177c54dfc13f6193e00107776b Closes-Bug: #1517144
2015-11-17Fix issues in Glance filesystem backendPaul Bourke3-1/+7
The drop root change for Glance highlighted the fact that we were binding volumes from glance_data into the wrong container - it was glance_registry whereas it should be glance_api. This would result in all images being lost if the glance_api container happens to restart. Also, we need a sudoers file to chown the file backend dir to the glance user. Change-Id: If04337045bb94b3126e48d1f5bf0ea29e20373ae Closes-Bug: #1516729
2015-11-17Add support for loading kolla config from ENVAngus Salkeld1-10/+27
Implements: blueprint zookeeper Change-Id: Ibabcb5d6d304be9290633338c513f16651d4479a
2015-11-16Fix namespace regression for neutronSam Yaple2-0/+6
Due the to way network namespaces work, they will not survive a container restart. This is not an issue related to Kolla or Neutron but rather an issue with how network namespaces work. This is putting back into place a workaround that was in correctly removed in the past. We simply cleanup the namespace cruft when the neutron-agents container restarts thus avoiding this issue. Change-Id: Ic16f2f766b4fa46347ea14a1ece5a4653c69d779 Closes-Bug: #1511216
2015-11-14Add usermod to Zaqar containerBritt Houser1-1/+2
When we dropped root, we forgot the usermod. Updated. Change-Id: I72a452c9b3b6a9aac0a8edd073887a1b79c34e8e
2015-11-14Merge "drop root on memcached"Jenkins1-2/+8
2015-11-14drop root on memcachedBritt Houser1-2/+8
This patch add the USER directive to the memcached container. It also removes the -u from the command line to launch memcached, since it will already be run as that use. Change-Id: I87d782a424df99fe1b5694debafa3c0c4a9aba27 Partially-Implements: blueprint drop-root
2015-11-13Merge "Revert "Drop root for Horizon service""Jenkins1-19/+1
2015-11-13Merge "Drop root for Zaqar service"Jenkins2-1/+3
2015-11-13Merge "Add ZooKeeper support in kolla-ansible"Jenkins1-0/+66
2015-11-13Drop root for Zaqar serviceJosh Lothian2-1/+3
Change-Id: I59797a8539406e478f6953a9aa0c933e73eb5892 Partially-Implements: blueprint drop-root
2015-11-13Add ZooKeeper support in kolla-ansibleMichal Rostecki1-0/+66
In kolla-mesos, ZK will be used for storing information about actions done in bootstrap. Change-Id: Id7067a493b457cf7b73eb007852df7b13f4363b3 Partially-Implements: blueprint zookeeper
2015-11-13Merge "Add Ansible support for Magnum"Jenkins1-1/+1
2015-11-13Add Ansible support for MagnumMichal Rostecki1-1/+1
Change-Id: Idb25ac4d3148c9b9400cf675ac2e47d35cce6224 Implements: blueprint ansible-magnum
2015-11-13Revert "Drop root for Horizon service"Sam Yaple1-19/+1
This reverts commit f9ccb1c8829cef551b875c7c387530e7980414a7. There are many issues with this patch that prevents it from working under numerous circumstances. The implementation is entirely busted on Ubuntu. Additionally, best practice for apache is to run as root. Apache itself does the privlege dropping. Change-Id: I4395debb7d32223fb3752a6d3e7c4d7672d29916
2015-11-13Merge "Drop root privileges for rabbitmq"Jenkins3-2/+9
2015-11-12Drop root privileges for rabbitmqRyan Hallisey3-2/+9
Drop root privileges for rabbitmq. Only the rabbitmq user will be able to execute chown of /var/lib/rabbitmq. Change-Id: I546e6b475a8462bfbc75972854e1fee64f96d9cb Partially-Implements: blueprint drop-root
2015-11-12Move USER operation after footerSam Yaple14-28/+27
The USER operation affects all docker commands after it. This causes a problem with our {{ include_footer }} implementation since commands in that footer may require elevated permissions to perform. In the current implementation I can no longer remove my proxy settings once the USER has been changed. Change-Id: I9b2bab5a15f595f6d52a46c64ddf59ba5608b938 Partially-Implements: blueprint drop-root
2015-11-12Drop root privileges for mariadbSteven Dake4-5/+15
Drop root privileges for mariadb. This isn't perfect. If somemone breaks out of the container and can run sudo within the contianer, it would be possible to replace the root credentials of the database. Any container that uses sudo suffers from some extra attack vector related to the sudo command. That said, the sudo commands are locked down to minimize harm. Change-Id: I4b3573725d940bb8aa90d43a6235d8cf7d30fc64 Partially-Implements: blueprint drop-root
2015-11-11Move the mariadb expect code to a scriptSteven Dake3-21/+25
Atleast in a script, sudo can be made to only allow the script to run from the mysql process in the future, versus all the proceesses being able to be executed as root presently. Change-Id: I030b57086e37e4dc8f668f98c04335d94ab9d2b0 Partially-Implements: blueprint drop-root
2015-11-11Drop root for Horizon serviceSteven Dake1-1/+19
Drop root privileges for Horizon service. It is necesssary to set a capability on the filesystem to allow binding to port 80 as a non-root user. I have tested this works correctly from a registry on both CentOS and Ubuntu. Change-Id: I4c26f28bb28b6633784e6842f3423a2425332c27 Partially-Implements: blueprint drop-root
2015-11-11Merge "Install keystoneauthv1 in openstack-base image"Jenkins2-1/+1
2015-11-11Merge "Drop root for kolla-ansible"Jenkins2-2/+8
2015-11-11Merge "Clean up horizon httpd pid files for RPM distros"Jenkins1-0/+7
2015-11-11Install keystoneauthv1 in openstack-base imageSteven Dake2-1/+1
Lots of tools rqeuire keystoneeauthv1 not just horizon TrivialFix Change-Id: I35eb958e35500b04657679371019f2e6f3c2f2dd
2015-11-11Drop root for heatSteven Dake5-1/+9
Drop root user for heat containers. Change-Id: Ib07c0193f97bb18cc6154b4015b4056fd983f6c1 Partially-Implements: blueprint drop-root
2015-11-11install openstack-heat-common in heat-baseSteven Dake1-1/+9
the openstack-heat-common package installs the Heat UID/GID. This is necessary pre-work for drop-root for heat services. Change-Id: I247b0209248de144d20f5245973833be5cd8f14f Partially-Implements: blueprint drop-root
2015-11-11Merge "Drop root for designate"Jenkins8-1/+15
2015-11-11Drop root for kolla-ansiblePaul Bourke2-2/+8
This change ensures commands run in the kolla-ansible container are done as the 'ansible' user rather than root. By default Ansible tries to write it's temporary files to $HOME/.ansible on the target, which in most cases won't exist when run as the new user. Hence we now supply the kolla-ansible container with an ansible.cfg, to tweak the remote_dir option to /tmp. Change-Id: I838a8c8cd0c7dc1aeca4d12e38c346f252170e7c Partially-Implements: blueprint drop-root
2015-11-11Clean up horizon httpd pid files for RPM distrosPaul Bourke1-0/+7
(apply same fix that we did for keystone, to horizon) In some cases we're seeing httpd not cleaning up properly after itself, which results in the horizon container failing to restart. This is confirmed to happen on rpm based distros, but have not had any reports on Ubuntu. Change-Id: I8ece6da1a8a1180730d68be0d129a656ddcede07 Closes-Bug: #1515214 backport: liberty
2015-11-10Drop root for designateMichal Rostecki8-1/+15
Change-Id: I1df05608be62cc008ccef1ca88d0b37983568d22 Partially-Implements: blueprint drop-root
2015-11-10Horizon rdo package requires python-keystoneauth1Martin André1-0/+1
Change-Id: I0d98399d7d573ea43689746dda59a647c307b25f Closes-Bug: #1514697
2015-11-09Merge "drop root for glance"Jenkins4-1/+7
2015-11-09Merge "Base image changes for drop-root"Jenkins3-3/+24
2015-11-09drop root for glanceSteven Dake4-1/+7
This uses the grouping feature of sudo to limit the amount of times the base sudo file has to be modified to only once. The container contents always runs as the user root, except the software which is controlled by Kolla. This software may run as root, but it has undergone a security audit and preserves permissions of the correct files and does not permit the glance user to write any of the set_config.py control files. Change-Id: Ie3cd23edcde5b408a8f66970456279a1b15028e0 Partially-Implements: blueprint drop-root
2015-11-09Base image changes for drop-rootSteven Dake3-3/+24
The reason we are doing drop root is so that a network exposed software component (i.e. glance) cannot be used to affect the immutability of the container which it runs in. I have tried several different approaches and this is the only approach which puts glance in PID=1 while ensuring no files may be written by the glance process in the container image except for the log files. Change-Id: Ifd3c8c361b78d0e4791dade3afa6435290407c41 Partially-Implements: blueprint drop-root
2015-11-09Fix validate-all-maintainer.sh to look for Dockerfile.j2Angus Salkeld29-29/+29
And fix the fallout. Change-Id: Iccad3f4fdb0a6a7c14246df3408cae0425b833a5
2015-11-06Switch to RDO untested master repositoryDavid Moreau Simard1-1/+1
RDO does not yet provide a CI tested Mitaka repository. As such, the current-passed-ci repository is the last tested repository before the stable/liberty branch was cut. To be able to test against the latest packages, we need to use the untested repositories until the CI tested repository is in place. TrivialFix Change-Id: I4a125eb3c84fa790746a9a8eca19e4fb2d9ecf38
2015-11-06Remove mysql-devel cruftMartin André1-1/+0
This was conflicting with Percona-Server-devel-55 and broke centos source build for openstack-base image. Backport: Liberty Change-Id: Ia2bb2106038e8e2eadb6668f4ae1ad1d95710c09 Closes-Bug: #1513711
2015-11-05Merge "Clean up keystone httpd pid files for RPM distros"Jenkins1-0/+7
2015-11-05Clean up keystone httpd pid files for RPM distrosPaul Bourke1-0/+7
In some cases we're seeing httpd not cleaning up properly after itself, which results in the keystone container failing to restart. This is confirmed to happen on rpm based distros, but have not had any reports on Ubuntu. Change-Id: I58b006189e700f1c851601b4f64dd0fae931103c Closes-Bug: #1489676 Co-Authored-By: Tim Potter <tpot@hpe.com>
2015-11-05Add Docker in Docker containerSam Yaple2-0/+56
Change-Id: I3c953125ed0105b7e8b62e62da56bf3fa30889d1 Partially-Implements: blueprint multinode-gate
2015-11-05Merge "Fix RHEL builds"Jenkins1-4/+4
2015-11-04Fix RHEL buildsRyan Hallisey1-4/+4
Register with RHEL on the host machine and use yum to setup the repos in the container. Change-Id: I38aaf43fffaf7a235e69b330d5d9f0f1be31fe83 Backport: Liberty Closes-Bug: #1513088
2015-11-04Adjust package name for Ubuntu IronicSam Yaple1-3/+3
We target 14.04 which has the package name 'syslinux' >14.04 has the package name 'pxelinux' TrivialFix Backport: Liberty Change-Id: Id0f4f503257d62d9ce45be5eb8f4faa766244d0a
2015-11-03Merge "Make nova-spice5htmlproxy build on RDO"Jenkins1-2/+2
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-07 22:31:42 +0000