| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
When installing from binary, packaging tools create a user for
Keystone which does not have a shell. This results in fernet
token operations failing due to the fact that `rsync` cannot
connect over SSH because the Keystone user cannot login.
This patch addresses this issue by enabling shell access
to the Keystone user, it also refactors the Nova SSH controller
to use the pre-existing macro.
Change-Id: Ic753a94311c5d7d72a82d91c1279dfe982e9afbd
Related-Bug: #1617902
|
|
The latest release of OpenStack has moved a lot of the neutron
metadata proxy processes to use HAproxy instead. This package
is not installed by default and causes builds to fail.
This patch addresses this issue by adding the HAproxy package
which should clear out gate problems for source installs.
Change-Id: I2e42828b1ccdb3a79b95bee85648d55508c0f2f9
|
|
|
|
|
|
|
|
|
|
Added neutron-bgp-dragent Dockerfile.
Updated kolla/common/config.py with necessary sources.
Implements: blueprint neutron-bgp-dragent
Change-Id: If7f5c80eb10a1c418785d9c659ae18bfecfcfe33
|
|
congress binary package is available in rpm base distro
https://trunk.rdoproject.org/
Change-Id: I4f2f9396925d28322d2d5a625cc96d8a5386b129
|
|
|
|
libosinfo is required by nova-compute.
Change-Id: I5615e191d1a9a2ea35cab41b6b03803ebfaf3cb1
Closes-Bug: #1670692
|
|
|
|
|
|
Some projects that use Kolla docker containers (TripleO) run heat 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: I4d648c4ce4f5f6ba311bfbbf9c78e06104163c61
Partially-Implements: blueprint apache-packages-for-apis
|
|
ironic-conductor depends on iscsi_tcp module
Change-Id: I1dd7d1a8cd67bbdfc1262b39aa96997c12681900
Closes-Bug: #1672245
|
|
Debian/stretch container image does not have them installed so apt-key
calls fail.
Partially-Implements: multiarch-and-arm64-containers
Change-Id: Ia1ca5e62d815a224716074cf81e7d7519f33d6fc
|
|
|
|
When using panko event dispather in ceilometer, panko's code is
required.
Closes-Bug: #1672241
Change-Id: Ie03f6fcda0ecd09511c09c962b9bd14ae67f1ad3
|
|
Currently Windows and non-declared os_type images (defaults
to Windows) attempt to format ephemeral volumes with
mkfs.vfat but fail as this tool is not available in the
container.
This is resolved by installing dosfstools on the Source
builds (as I believe this is handled in binary builds
through dependencies).
Change-Id: Iefa5fb0a16eed30aea935268f2a9becb1481b018
Closes-bug: #1672199
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
|
|
osprofiler package is required when using osprofiler tool.
[0] https://github.com/openstack/osprofiler
Change-Id: I2d11778e94564ad0c04685eeff45f36430779099
Closes-Bug: #1672125
|
|
Move debian based family package installs to base_distro
from binary conditional.
This follows RedHat based family install
Closes-Bug: #1671923
Change-Id: I038b6a198d7fd0cf805b211bc32d55bfe88bd581
|
|
In order to generate keypair and access to cluster instances,
sahara-base container must include this binary, even when we
deploy based on source type.
Change-Id: I40747bceba3fede66864b781df1da1034ea22d11
Closes-Bug: #1665293
|
|
|
|
|
|
Ironic-ui packages are missing in Horizon binary
installations, when enable Ironic Horizon
does not start due failed to stat necessary files.
Ubuntu repos does not have an available package yet.
Change-Id: I1278023e481b3057377ecddc0daaf0552c39d5a2
Closes-Bug: #1671322
|
|
The heat-api-cloudwatch service is used in TripleO.
Partially-Implements: blueprint containerize-tripleo
Change-Id: I98d251ea34cf7ee451b45f0b8c6873488a229c36
|
|
|
|
The dependencies of ceilometer packages missed
python pecan and wsme.
Change-Id: Ia0d7b8de530f42a1d84e455486fb4b66ff833914
Closes-Bug: #1668548
|
|
To facilitate build custimisations in template-overrides.j2
for bifrost-base, added a block section wrapping the execution
of the ansible install.yaml playbook.
Change-Id: I4eb18d03b7d7b2a2f65ec3c844af9149f9426949
|
|
|
|
Now we use flunetd version is v12.0
we use fluent-plugin-grok-parser plugin shoud < 1.0.0.
https://github.com/fluent/fluent-plugin-grok-parser
Change-Id: I013e1e6d1070c4ba050be5dd75be7be4df652e4e
Closes-Bug: #1669405
|
|
|
|
neutron-metadata-agent image expected the /var/lib/neutron/kolla
directory to be present but it was not created as part of the image
building. As a result, the extend_start.sh script fails with:
stat: cannot stat '/var/lib/neutron/kolla': No such file or directory
This commit defers setting the right ownership for files and directories
to the kolla config API via a config.json file.
Kolla-ansible already mounts the directory as the
neutron_metadata_socket named volume and uses kolla API to set the
ownership and permissions [1].
[1] https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/neutron/templates/neutron-metadata-agent.json.j2
Closes-Bug: #1669487
Change-Id: Ib521b0fc69ab6a72295a2fde3309a001bc3063c2
|
|
Change-Id: I2b2ef84589ca6cbb0d27934000f9640a8eb202a3
Closes-Bug: #1660092
|
|
|
|
|
|
|
|
|
|
|
|
Shade has new functionality we need for sanity checks. This also
requires a newer os-client-config.
Change-Id: If6d10f2ce90c7fc72353566554352b0310942f30
Partially-Implements: blueprint sanity-check-container
|
|
|
|
Heka is removed and replaced by fluentd.
Change-Id: I4ed0f61b02bea5dcb02b61a9eb99e3ff3f460682
|
|
|
|
/etc/openstack-dashboard/local_settings.py is deleted in the followup
command, the sed is never used.
Change-Id: Ife02321a4077544ae13428968c4bfe27eb7a7a48
|
|
Change-Id: Idb5a40f080937c74008caf2650ba82d82ab520c4
|
|
The location of the binaries in these images can be overridden by
setting ENV in the header blocks, but if an operator wants to use a
different install method all together (e.g. rpm), these blocks will
allow that.
Also import the macros in kube-base to allow their use in overrides.
Change-Id: I3e52e315f0103d8a1c95d4489fa3841900fdff75
|
|
When built with the binary install type (at least on CentOS), Ironic
inspector fails to start and the container remains in a restarting
state. The log file shows that it is failing to execute iptables, and
analysis found that this was due to an incorrect rootwrap
configuration. The RDO ironic inspector RPM expects Ironic inspector
to be run as the ironic-inspector user, however Kolla uses the ironic
user. This means that neither of the packaged ironic nor
ironic-inspector sudoers configuration files works for us.
Kolla currently installs a sudoers file pointing to the rootwrap
script in the virtualenv of the source install, but of course this
only makes sense for source installs, and should not be installed for
binary installs.
This change adds a second sudoers file that will work for the binary
install type, and installs the correct sudoers file for the install
type.
Change-Id: I8ecd0b658b8df8f38ddf717fa9443d4dc2896984
Closes-Bug: #1624457
|
|
|
|
|
|
Allow operators to customise these using the usual Kolla mechanisms.
Change-Id: I59d5eae43fb12f8301b26f5b693c104fca635762
|