summaryrefslogtreecommitdiff
path: root/tools
AgeCommit message (Collapse)AuthorFilesLines
2016-03-28Remove bootstrap_mariadb with cleanup-containersMauricio Lima1-1/+1
TrivialFix Change-Id: Ic6884d46d8edf2d430f8a9fb8635f7d98d011112
2016-03-27Merge "Fix gate to use world writeable docker socket"Jenkins1-0/+3
2016-03-26Fix gate to use world writeable docker socketSteven Dake1-0/+3
A recent change related to sudo securepath broke how sudo -E works. Now the PATH is reset by sudo as set by tox. As a result we can no longer rely on sudo -E anywhere in our gating system relating to path inheritence from the parent shell. This patch uses a shell operation in the setup_nodes.yml code to chmod the docker socket to 666 so docker containers can build properly. Now docker operations don't return a permission denied and we no longer require the sudo -E operation in any of our tox scripts. This isn't a security vulnerability because our gate scripts are only meant to be run in OpenStack infrastructure. To make this more clear I recommend moving these shell scripts to tests/gate. Change-Id: I5b3d6e280e3c12a25defedb14b5589ba642043fa Closes-Bug: #1562383
2016-03-26Fix typos in KollaNguyen Hung Phuong1-1/+1
TrivialFix Change-Id: I21f51811ec4256d9b6b2e219de6201e4811dfc5a
2016-03-22Merge "Check relevant logging mechanism in the gate"Jenkins1-2/+5
2016-03-22Check relevant logging mechanism in the gatePaul Bourke1-2/+5
Avoids errors about missing journalctl on Ubuntu and missing upstart on redhat bases. Closes-Bug: 1554724 Change-Id: I80bb55688398df85f9020d5cfe5dda757fc5a0ef
2016-03-21Merge "Fix rax-ord commands"Jenkins1-2/+2
2016-03-21Merge "Add generate_passwords.py to generate passwords"Jenkins2-0/+3
2016-03-21Fix rax-ord commandsSamYaple1-2/+2
It isn't always possible to get a rax-ord gate. Last patch wasn't correct. TrivialFix Change-Id: Id94264166e0914f038f32f3f9b68e463aa15ccd3
2016-03-21Merge "Fix rax-ord gate"Jenkins1-0/+8
2016-03-21Add generate_passwords.py to generate passwordsSamYaple2-0/+3
As with all tools, this is a first pass at the generation. Perhaps we even want to move this into kolla/kolla/cmd and be generated with tox itself in the future. This tool, when run, will only populate empty fields that have no values meaning that it is safe to run repeatedly on the same file. Of note, there is no way to preserve comments in the file after it has been processed by the yaml parser in python. Comments and sections will remain in the passwords.yml template for additional documentation if the user wishes to populate the file themselves. Use SystemRandom and clean up the docs a bit to not use pronouns. Co-Authored-By: Steven Dake <stdake@cisco.com> Closes-Bug: #1559266 Change-Id: I2932d592df8871f1b7811059206d0b4d0553a687
2016-03-21Dynamically pull list of projects and versionsSamYaple1-40/+27
This also fixes this version check utility since it was utterly broken before. While it did run to completion, it never properly returned any versions that needed updating. TrivialFix Change-Id: If5d77f20fd8fc97679d58bc9019115157c5f5967
2016-03-21Fix rax-ord gateSamYaple1-0/+8
Change-Id: I169647999b313def30c0605172cf188ef4518cdb Related-Id: Id9ea8c5e402f3a06b9064a939ad4b2e168cd6223
2016-03-21Allow version_check to work on local git repoSamYaple1-0/+10
Same method we use for build.py TrivialFix Change-Id: Ib2a7bbfb8349c473e6fdbacbba239985b05ec0bd
2016-03-19Fix permissions for log extraction in gateSamYaple1-0/+2
Some gates are failing to properly pull all logs out resuling in an UNSTABLE status. This resets all logs to 777 perms to ensure readability by jenkins. TrivialFix Change-Id: Ib92c5bfea5fa8bcc6380ad8aa6001b13888717ac
2016-03-18Install Elasticsearch and Kibana packages using yum/apt-getVikram Hosakote1-0/+1
Test results of this patch set are at http://paste.openstack.org/show/490450/. Change-Id: I2957cc70fcca34706ec50a630d785f0630c3f5c0 Closes-Bug: #1553203
2016-03-18Merge "Change libvirt volume name to libvirtd"Jenkins1-1/+2
2016-03-17Merge "Increase the docker parition for rht bases in gate"Jenkins1-1/+1
2016-03-17Merge "MariaDB lights out recovery"2.0.0.0rc1Jenkins1-0/+6
2016-03-16MariaDB lights out recoverySamYaple1-0/+6
This playbook only matters for multinode since AIO can recover from power outage without additional configuration. DocImpact Implements: blueprint mariadb-lights-out Change-Id: I903c3bcd069af39814bcabcef37684b1f043391f
2016-03-16Increase the docker parition for rht bases in gatePaul Bourke1-1/+1
Currently the binary build for the oraclelinux base is just exceeding the 10GB limit we have set here. Centos is at just under 9GB so will not be long before it reaches this limit also. According to infra - (http://docs.openstack.org/infra/system-config/contribute-cloud.html) gate VMs should have a 80GB disk, so 20GB for the docker partition does not seem excessive here. TrivialFix Change-Id: I4d7fb240ea90e1e58f8f8046dd7acd0b9502c20d
2016-03-16Remove useless dependency on ifconfigMartin André1-10/+10
We can use the ip command to achieve the same thing. TrivialFix Change-Id: I903467c90495388cbc592b56d96bd3a4675df430
2016-03-15Change libvirt volume name to libvirtdSamYaple1-1/+2
This change is a "futureproofing" thing. It has already been discussed that libvirt should not be a child of nova and should be removed out to the base docker directory (just like openvswitch isn't a child of neutron). That is not going to happen this cycle but when it does we can't change the name of the volume. This updates the volumes to the proper name of libvirtd. This is in contrast with the libvirtlogd volume that will be needed in newton due to libvirt 1.3 Of note, the container can remain named nova_libvirt since we can change that on the fly later without breaking instances. This wont break liberty as named_volumes are not backported yet. TrivialFix Change-Id: I16cf9e1b1dbba9b5a9f5cc883494580e276d4f72
2016-03-14Use ubuntu Mitaka repoSamYaple1-1/+1
The rabbitmq-server package is upgraded to 3.5.7 in cloud-archive so we update centos to match The xen-utils package now needs an explict version, xen-utils-4.6 is what is provided by cloud-archive mitaka Libvirt 1.3 is in the ubuntu cloud-archive. This has a new daemon for logging that needs further implementation in newton. For now, it has been disabled within the qemu.conf Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net> TrivialFix Change-Id: I84217824817c484b6800a64cbd7767b127a3098e
2016-03-09Add cron image and playbookÉric Lemoine1-0/+1
Add cron image and playbook for logrotate. The "common" Ansible playbook includes configuration files for logrotate. At this point the operator cannot customize/override the logrotate configuration. Closes-Bug: #1553244 Change-Id: Ic9fdda9a273c9ccd90502f0acc7614d2c7157dca
2016-03-08Rename validate-docker-execute with .sh extensionSteven Dake3-2/+2
TrivialFix Change-Id: I3ad67fd802f7fe3ed7deb88eddebe520ff410a4f
2016-03-09Merge "Copy the logs out of the container"Jenkins2-5/+3
2016-03-09Copy the logs out of the containerJeffrey Zhang2-5/+3
Heka logs almost done. When testing, The collected logs can copy to the /tmp/logs folder, which will be handle by the gate. This will be very useful for our gate debug. TrivialFix Change-Id: I06ca8ebd13933bfd15cb2fb5e53fc3038b17b8c3
2016-03-08Checks the installation of curl command, Nova, Neutron and OpenStack packagesprithiv1-1/+6
related-bug: 1552433 Change-Id: If89e2a1bc959039fc7088c8295e88a199eabbedc
2016-03-08Merge "Add documentation for two-VIP and TLS blueprints"Jenkins1-1/+1
2016-03-08Add documentation for two-VIP and TLS blueprintsDave McCowan1-1/+1
Relates-to: blueprint kolla-ssl Change-Id: Id82d22c2195be5d897c781f28087a1ea422b8bea
2016-03-08Add a new tool to help find the latest versionsSam Yaple1-0/+129
As we will be switching to pinning versions in Kolla this tool will help remove the 'manual' part of that equation by looking up the versions we want. The idea would be to eventually turn this into an autoproposal bot so we only ever need to approve changes. More work can be done here like automatically updating the kolla-build.conf Co-Authored-By: Martin André <m.andre@redhat.com> Partially-Implements: blueprint upgrade-kolla Change-Id: I052159850b2579ca6db79be71672be382be8a3a3
2016-03-06Merge "Add two more examples of openrc for use with public endpoints"Jenkins1-0/+38
2016-03-05Add two more examples of openrc for use with public endpointsDave McCowan1-0/+38
Relates-to: blueprint kolla-ssl Change-Id: I6d9531ce4513ed06f1d13081418b167ad264aaff
2016-03-05Merge "Use alphabetical order in cleanup-containers"2.0.0.0b3Jenkins1-12/+12
2016-03-05Merge "Make Heka send logs to Elasticsearch"Jenkins1-2/+5
2016-03-05Use alphabetical order in cleanup-containersÉric Lemoine1-12/+12
TrivialFix Change-Id: I95f2e6d17ba7960b2f87344f30b7884d621f9ecb
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine1-2/+5
This patch includes changes relative to integrating Heka with Elasticsearch and Kibana. The main change is the addition of an Heka ElasticSearchOutput plugin to make Heka send the logs it collects to Elasticsearch. Since Logstash is not used the enable_elk deploy variable is renamed to enable_central_logging. If enable_central_logging is false then Elasticsearch and Kibana are not started, and Heka won't attempt to send logs to Elasticsearch. By default enable_central_logging is set to false. If enable_central_logging is set to true after deployment then the Heka container needs to be recreated (for Heka to get the new configuration). The Kibana configuration used property names that are deprecated in Kibana 4.2. This is changed to use non-deprecated property names. Previously logs read from files and from Syslog had a different Type in Heka. This is changed to always use "log" for the Type. In this way just one index instead of two is used in Elasticsearch, making things easier to the user on the visualization side. The HAProxy configuration is changed to add entries for Kibana. Kibana server is now accessible via the internal VIP, and also via the external VIP if there's one configured. The HAProxy configuration is changed to add an entry for Elasticsearch. So Elasticsearch is now accessible via the internal VIP. Heka uses that channel for communicating with Elasticsearch. Note that currently the Heka logs include "Plugin elasticsearch_output" errors when Heka starts. This occurs when Heka starts processing logs while Elasticsearch is not yet started. These are transient errors that go away when Elasticsearch is ready. And with buffering enabled on the ElasticSearchOuput plugin logs will be buffered and then retransmitted when Elasticsearch is ready. Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb Implements: blueprint central-logging-service
2016-03-02heatclient has invalid json validation picks upSamYaple1-1/+1
We shouldn't be scanning .tox dir anyway. TrivialFix Change-Id: If570abdfa69375091751199dcce637682e8de1ef
2016-03-01Merge "Update cleanup-containers to remove ceph containers"Jenkins1-1/+3
2016-03-01Update cleanup-containers to remove ceph containersMauricio Lima1-1/+3
TrivialFix Change-Id: Ia47429a38503d4982049c3fa1fc6fca4a8000fbd
2016-02-29Move ironic-discoverd to ironic-inspectorAllen Gao1-1/+1
Closes-Bug: #1551052 Change-Id: Ic226287bbf1f1e8d5cc2e1d80ce2975448b1f95c
2016-02-27Merge "Change kolla_internal_address variable"Jenkins2-3/+3
2016-02-26Change kolla_internal_address variableSamYaple2-3/+3
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-26Add Ansible scripts to generate TLS certificates for testingDave McCowan1-0/+6
Working towards the blueprint that will add TLS protection for the external endpoints, kolla needs certificates. When kolla deploys OpenStack, the external VIP will need a server side certifcate. Clients that access those endpoints will need the public CA certificate that signed that certificate. This ansible script will create these two certificates to make it easy to use TLS in a test environment. The generated certificate files are: /etc/kolla/certificates/haproxy.pem (server side certificate) /etc/kolla/certificates/haproxy-ca.pem (CA certificate) The generated certificates are not suitable for use in a production environment, but will be useful for testing and verifying operations. Partially-implements: blueprint ssl-kolla Change-Id: I208777f9e5eee3bfb06810c7b18a2727beda234d
2016-02-25Add the default empty reconfigure.yml file to all rolesJeffrey Zhang1-1/+4
DocImpact Partially-implements: bp kolla-reconfig Change-Id: I9738e80960bcfbef18d1ef1b7942f81c45684e85
2016-02-23Remove Rsyslog entirelyÉric Lemoine2-3/+1
Partially implements: blueprint heka Change-Id: I1322d2dc870e6f8fe052926995d993e8a08a25db
2016-02-23Merge "Add elasticsearch repo to gate"Jenkins1-0/+1
2016-02-22Add elasticsearch repo to gateSamYaple1-0/+1
TrivialFix Change-Id: I0f083654df901fb765e9517308ac94316859d971
2016-02-22Merge "Make cleanup-containers remove bootstrap_heka"Jenkins1-1/+1
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-06 18:15:48 +0000