- Mar 21, 2016
-
-
SamYaple authored
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
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
SamYaple authored
The lightsout recover patch broke multinode mysql. Also the lightsout recovery didnt probably pass the --wsrep-new-cluster flag. This updates the mariadb bootstrap to work with multinode again. Closes-Bug: #1559480 Related-Id: I903c3bcd069af39814bcabcef37684b1f043391f Change-Id: I1ec91a8b2144930ea8f04cc1c201b53712352e4e
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jeffrey Zhang authored
TrivialFix Change-Id: Idfc5d03d3359003cdb82b85b71b87ccefd4a0a43
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Vikram Hosakote authored
This bug was reported by eandersson in IRC today. TrivialFix Change-Id: I3100d2bc567f641894817bd9cf3b2213416085b2
-
Jenkins authored
-
Jenkins authored
-
- Mar 20, 2016
-
-
Andrei-Lucian Șerb authored
On computers with wi-fi adapters, promiscuous mode on the VirtualBox (or maybe other hypervisors as well) NICs does not work, which means the default way of connecting the Neutron external interface to a bridged adapter, will not allow communication to and from the Nova VMs over floating IPs with any computer on the external network (except the host computer) or with the wi-fi router. This means no ability to connect to the Nova VMs and no internet access inside the Nova VMs. According to VirtualBox documentation (excerpt): "Bridging to a wireless interface is done differently from bridging to a wired interface, because most wireless adapters do not support promiscuous mode. All traffic has to use the MAC address of the host’s wireless adapter, and therefore VirtualBox needs to replace the source MAC address in the Ethernet header of an outgoing packet to make sure the reply will be sent to the host interface. When VirtualBox sees an incoming packet with a destination IP address that belongs to one of the virtual machine adapters it replaces the destination MAC address in the Ethernet header with the VM adapter’s MAC address and passes it on. VirtualBox examines ARP and DHCP packets in order to learn the IP addresses of virtual machines." To fix this issue, a new flag has been introduced: WIFI. If true, the default Vagrant public network is not created anymore. Instead, the 3rd NIC will be connected to a NAT-Network named OSNetwork. The NAT-Network has a virtual gateway, which will be used to communicate with the external physical wi-fi router. Since Vagrant does not have a high-level mechanism to attach an adapter to a NAT-Network, the code uses the low-level Vagrant construct vm.customize which makes it provider specific. Promiscuous mode is now activated by default on the 3rd NIC. The WIFI flag is false by default. This commit only addresses VirtualBox, and it is currently unknown if the problem described and fixed in this commit is present in other hypervisors. DocImpact Closes-Bug: #1558766 Change-Id: I0b4dbbc562d87191b2179f47b634cdd6f6361a5e Signed-off-by:
Andrei-Lucian Șerb <lucian.serb@icloud.com>
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jenkins authored
-
Jeffrey Zhang authored
the prechecks role should be idempotent and should changed nothing when running. TrivialFix Change-Id: Ib5063d879e0f5f414d607bd9b6493a7499fc5652
-
Jenkins authored
-
Hui Kang authored
pymongo is needed when ceilometer uses mongodb as backend database Change-Id: Id75dc7bed30cdfa12f95bb66ca6d4cdf7be0261c Closes-Bug: #1559370 Related-Bug: #1559390
-
- Mar 19, 2016
-
-
SamYaple authored
The user variable was incorrectly in passwords.yml The naming was inconsistent, it should be prefixed with manila_* Removed old unused variable TrivialFix Change-Id: I182797fcc6d62d35174403d78d71c8ad7ddcbc43
-
SamYaple authored
These options have all be deprecated/removed. This switches all options to thier proper mitaka values. TrivialFix Change-Id: Ica8d5ea0d48da01ee11672a32890431acd6a306d
-
SamYaple authored
These values are optional only when the services are not enabled. If the file does not exist we should not warn, but rather inform. Ceph-mon is an exception here since its bootstrap process means the files may or may not exist initially. TrivialFix Change-Id: Ic02bece76d480e99deecf612036f37abb5604135
-
SamYaple authored
Now that we have reconfigure we dont have to copy over all config files at the same time. TrivialFix Change-Id: I866be0f05e604151e081974a64f17bf65787f604
-
SamYaple authored
This allows us to specify external journals for osds which can greatly improve performance when the external journals are on the solid-state drives. The new lookup and startup methods fix the previous races we had preventing osds from being created properly. This retains the same functionality as before and is completely compatible with the previous method and labels, however this does set new labels for all new bootstrap OSDs. This was due to a limitation in the length of the name of a GPT partition. Closes-Bug: #1558853 DocImpact Partially-Implements: blueprint ceph-improvements Change-Id: I61fd10cb35c67dabc53bd82270f26909ef51fc38
-
SamYaple authored
Change-Id: I9c770a08219d2eead5ece8e3462157359cd920cb Partially-Implements: blueprint ceph-improvements
-
SamYaple authored
The in-process cache for keystone tokens has been deprecated due to "incosistent results and high memory usage" with the expectation we switch to memcached_servers if we want to stay performant. Add memcache_servers [cache] section to the appropriate servers as the [DEFAULT]\memcache_servers options was deprecated. TrivialFix Related-Id: Ied2b88c8cefe5655a88d0c2f334de04e588fa75a Change-Id: Ic971bdddc0be3338b15924f7cc0f97d4a3ad2440
-
SamYaple authored
Just like last cycle, I ran all of the requirements and found the packages that were installed >=10 times throughout our containers. By combining them in the openstack-base we reduce the size of the images by ~600MB (10%) and decrease build time by a measurable amount (5-10m in the case of Centos) TrivialFix Change-Id: I582d75644a8e8b936c6f9fc10c6b5821e1e8c5c4
-
SamYaple authored
We were specifying the wrong driver in our nova.conf Change-Id: I37a3d366f2895b9d1281815ef85209feaa37b92d Closes-Bug: #1559494
-
SamYaple authored
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
-
Maru Newby authored
While it's possible to edit distro/package unit files installed to /lib/systemd/system, a cleaner solution exists. systemd will pick up 'drop-in' unit files located in '/etc/systemd/system/[unit name].d/'. A drop-in unit file only has to include fields that override those in the main unit file, and the drop-in unit and main unit file can change independently. This change updates the quickstart doc to use drop-in unit files to configure docker.service instead of editing the main unit file. See: https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html Change-Id: Iddbebf658741937e3c4157fc0a021751f10fabd2
-
Michal (inc0) Jastrzebski authored
Rabbitmq can't work with IPs, so we need to make sure that all rabbit cluster hosts can resolve each others hostnames. We should also require that in docs. DocImpact Closes-Bug: #1559158 Change-Id: I2418187138988d21da3dc3624e9cdbda891d4894
-
- Mar 18, 2016
-
-
Steven Dake authored
During multi-node, it is possible for master target node images to be older then the Ansible master playboks if the repository is updated. Add documentation to explain this situation. Change-Id: I2ccf57004147873e89f23fbb996d01f550e90c3f
-