| Age | Commit message (Collapse) | Author | Files | Lines |
|
This directory is needed for kolla-mesos to save config files
there.
Change-Id: Ia9810061d370bc600dfffeb33a4d4402c423e3fc
Closes-Bug: 1567437
|
|
|
|
neutron-plugin-linuxbridge and neutron-plugin-openvswitch package
is useless and removed in Mitaka on Ubuntu
Change-Id: Ia156d58410198af969f579cd5e7461c31ea63408
Closes-Bug: #1568281
|
|
Updates to ensure commands run in the swift containers
are done as the 'swift' user rather than root.
Change-Id: I8c5a12e24b9940200241dbe09d6bde8f1cc1cf05
Closes-Bug: #1553895
Co-Authored-By: Serguei Bezverkhi <sbezverk@cisco.com>
|
|
As suggested it was created the variable KOLLA_SERVICE_NAME to identify
the container service name through PS1 shell variable.
This method it was previously discussed in IRC.
https://goo.gl/k7AdEg
The other option it was usage hostname param in kolla_docker, but
currently docker does not support it due this issue:
https://github.com/docker/compose/issues/2460
The final result is like this:
$ docker exec -it heka /bin/bash
(heka)[heka@kolla-control /]$
$ docker exec -it mariadb /bin/bash
(mariadb)[mysql@kolla-control /]$
More details can be accessed through this link
http://paste.openstack.org/show/493689/
Closes-Bug: #1557454
Change-Id: I6aab8d640a8ebb17baa9d6d4f1edd6e331674713
|
|
|
|
|
|
In the gate, it is possible for /etc/hostname to not have a valid
SELinux security conext. So, reset them to default before we update
the hostname to avoid:
TASK: [Assign hostname]
failed: [node1] => {"failed": true}
msg: Command failed rc=1, out=, err=Could not set property: Access
denied
Closes-Bug: #1568047
Change-Id: Ie30c8437b310d1ea5bc75307375c255131dfe934
Needed-By: I2ff5fbb315832b8cf07c93d0dd0cdaacd958631e
|
|
Use a random virtual_router_id in case there are multi keepalived
instances exist at the same time in the gate.
Closes-Bug: #1568818
Change-Id: Iebb3dec088a21820e641b63bb2a5f40586d1df8c
|
|
|
|
Make sure that all the sevices will attempt to
connect to the database an infinite about of times.
If the database ever disappears for some reason we
want the services to try and reconnect more than just
10 times.
Closes-bug: #1505636
Change-Id: I77abbf72ce5bfd68faa451bb9a72bd2544963f4b
|
|
This reverts commit 99761c5cdce0d4e59adc19d1c33d32fa30872ceb.
Change-Id: Ib40224841f3399c6794b8aa71ca5cd7f0308a722
|
|
The comment was confusing and not explaining what the real issue is
when binding erlang to an IPv4 address.
Change-Id: I819ea137fa37c0b2711efb1e7cb1e518ae26b9ab
Related-Bug: #1562701
|
|
|
|
Heat development environments don't work at all.
As such document this so folks avoid them unless they want to
work on making them better.
Change-Id: Ibe3296660d30ccc24213c272ef379e6d3e2c21f2
|
|
kolla_external_vip_address"
|
|
Please refer to the Closes-Bug identifier for detailed information
pertaining to this issue.
Closes-Bug: #1562701
Change-Id: I77563930e14e11ea48e7edfef0bff80002279381
|
|
This reverts commit 86bafeee7a8926d212e8d089fade667772dbcc83.
Closes-Bug: #1568670
Change-Id: I88563292e29d691c27a3640e5232b9f22c7a288a
|
|
kolla_external_vip_address
Change-Id: I4bd3b4283b85bd675927b9a54d6906bb3c0d668e
Closes-Bug: #1566571
|
|
This fix adds a check of Rabbitmq's image version during the upgrade.
The container gets restarted only when the image version is different.
Change-Id: Ie038845c0c8fff1ac51b7cbf21e1b593229c2c0e
Closes-Bug: #1558832
|
|
This partially implements iscsi and lvm2 support for cinder
in Kolla. Adds iscsid and tgtd docker containers.
Change-Id: I7fb48c954e578772b90a2aa619c8bcfa990b3ae8
Partially-Implements: blueprint iscsi-lvm2-docker
|
|
|
|
|
|
Change-Id: I108397dbc86e44a81f82d6e9fce9ae2ad9d0976b
Closes-Bug: #1565054
|
|
|
|
Change-Id: I69a19a028fd0ac7f88f84ba1ff246e91d2a8c223
Closes-Bug: #1568424
|
|
Kolla deployment creates /etc/kolla folder on a target host
with multiple configuration files. In some scenarios,
the presence of these files prevent successful deployment
of certain services especially when their configuration parameters
have been changed on the deployment host.
Change-Id: Iefd544b50fc90b7f00d6e137bc14ab4807ef7c0f
Closes-Bug: #1561055
|
|
Change-Id: Icca182a9d570f6e7b39bec91ee6d1558a4da855f
Closes-Bug: #1567932
|
|
|
|
|
|
This patch adds to cinder-guide.rst LVM2/iSCSI related
information.
TrivialFix
Change-Id: I2c7b3090bbf314dd1281ca3d02148490936d5b86
|
|
Fix following two issues
* neutron-linuxbridge-agent container lacks bridge-utils package
* neutron-dhcp-agent container lacks dnsmasq-utils
Co-Authored-By: Manjeet Singh Bhatia <manjeet.s.bhatia@intel.com>
Closes-Bug: #1567406
Change-Id: I93a445b06612671f0331cd94573da41d2d3b60a0
|
|
Fix the permission issue on different distro
* In CentOS, add the qemu to nova group in CentOS
* In Ubuntu, add the nova to libvirtd group
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I1f4f9ce29abf0d788965fe94d8918b10a7169a75
Closes-Bug: #1568012
|
|
erlang parser, cant parse hostname with minus symbol, it returns:
Ignoring external configuration due to error: {1,erl_parse,"bad term"}
Adding single quotes fix this issue.
Co-Authored-By: weiyu <weiyu@unitedstack.com>
Closes-Bug: #1540234
Change-Id: I80e0789aa31febd552a851e6dc3a835d89c0e9d1
|
|
The nova team is removing the default flavors from a standard
deployment. This is great for operators, who have to delete
the defaults anyways. This patch adds the original default
flavors back during init-runonce so kolla users can be ready
to launch instances.
Closes-Bug: #1567964
Change-Id: I17daec98997a6e412a99f34d3f8a4324460d8c60
|
|
|
|
When horizon is used to launch 2000 VMs, nova-conductor is very
busy making database connections. All 55 database connections are
in use, resulting in an inability to garbage collect database
connections. Instead raise the max pool to 50 which will allow
50 concurrent database connections and the max overflow to 1000
which permits the database connections to finish the job at
large nodecount scales.
Closes-Bug: #1565105
Change-Id: I26dc2f7fda8760197888a1d61fbc45dfada2dd06
|
|
Fix some minor changes
ruby-dev package required for installing
vagrant-libvirt plugin.
TrivialFix
Change-Id: Id6d3552275ee28ab49804fe6cd1b00d2e8e3c1f4
|
|
|
|
related blueprint kolla-kubernetes
Co-Authored-By: mrostecki@mirantis.com
Change-Id: I5ef968a0f9b4a1b47b32bb041fbc5d5a3c2e2be7
|
|
Change-Id: I0605f406b5c03f0a6cdba9de2a180ed877f7dfa6
|
|
|
|
Change-Id: I0901802e0e349956f2c01dcd86746b4de0cc2382
Closes-Bug: #1567642
|
|
|
|
|
|
|
|
|
|
The Kolla design is for services to use the internalURL for
service to service communication. In Mitaka, Neutron added
a new config parameter specifying which URL to use to to
contact Nova, making the default 'public'. This patch sets
the value to 'internal'.
Change-Id: I2d36f3b4a860af9e9034ebfb2b5cea56450e5e4e
Closes-Bug: #1565624
|
|
Kibana requires creating an index for the first time when you log
in since we don't have a default dashboard yet. Documenting that
step in quickstart.rst.
Change-Id: I82ecd228c61e2affa5c8f9f9c93f8845728f707f
|
|
|