Age | Commit message (Collapse) | Author | Files | Lines |
|
This patch avoids conflicts when cherry picking
docker services in our ad-hoc docker services
patch series and enables them all at once.
Change-Id: Ia4f7c8071d8b4f3c9a7d73173e9120eb1e79ce53
|
|
This patch adds a new (optional) section to the docker post.j2.yaml
that collects any 'docker_puppet_tasks' data from enabled
services and applies it on the primary role node (the
first node in the primary (first) role).
The use case for this is although we are generally only using
puppet for configuration there are several exceptions that we
desire to make use of today for parity with baremetal. This
includes things like database creation and keystone endpoint
initialization which we rely on configuration via hiera variables
controlled by the puppet services.
Change-Id: Ic14ef48f26de761b0d0eabd0e1c0eae52d90e68a
|
|
This patch implements a new docker deployment architecture that
should us to install docker services in a stepwise manner alongside
of baremetal puppet services. This works by using Yaql to select
docker specific services (docker/services/*.yaml) vs the puppet
specific ones and then applying the selected Json to relevant Heat
software deployments for docker and baremetal puppet in a stepwise
fashion.
Additionally the new architecture
leverages new composable services interfaces from Newton to
allow configuration of per-service container configuration
sets (directories that are bind mounted into kolla containers) by
using the Kolla containers themselves. It does this by spinning up
a throw away "configuration only" version of the container being
configured itself, then running the puppet apply in that container and
copying the generated config files into /var/lib/config-data. This
avoids having to install all of the OpenStack dependency packages
in the heat-agent-container itself (our previous approach) and should
allow us to configure a much wider variety of container config files
that would otherwise be impossible with the previous shared approach.
The new approach (combined) should allow us to configure containers in
both the undercloud and overcloud and incrementally add CI coverage to
services as we containerize them.
Co-Authored-By: Martin André <m.andre@redhat.com>
Co-Authored-By: Ian Main <imain@redhat.com>
Co-Authored-By: Flavio Percoco <flavio@redhat.com>
Change-Id: Ibcff99f03e6751fbf3197adefd5d344178b71fc2
|
|
|
|
|
|
These were assumed to be always passed, but as the script gets
different cases (novajoin vs pre-defined service principals) we might
get "unbound variable" errors when used outside of CI. Exporting these
variables beforehand prevents that.
Change-Id: I195321354df167c09cfc87c5b9f86c6dc5026d75
|
|
|
|
|
|
|
|
|
|
This patch adds upgrade tasks for sensu-client, fluentd and collectd
Change-Id: I3a8096159664b1934b34f6c79b8afb4a3dc645c8
|
|
This parameter is passed in by the parent overcloud.yaml template, so we
have to listen accept it in docker/post.j2.yaml, otherwise the
deployment fails.
Change-Id: Ia3fdcfa01d52006a6e9fd0bb02c7379411f3d900
Closes-Bug: #1664569
|
|
|
|
|
|
|
|
This will provide an option in the UI to deploy Ceph RGW as a
replacement for Swift.
Change-Id: If2281edce49d2981f891c95ebb507e3a4b9e438e
|
|
|
|
Change-Id: Ic4cfdedfc0a60ebfd2391d03112f68e7a11629ce
|
|
Providing an empty 'parameter_defaults' is resulting in overriding
of all the previously populated 'parameters_defaults' as None.
Commenting the empty statement and cleaned-up emtpy line in j2
templating.
Change-Id: I75bac6b558ac16a08e0964599cecae5bf10edf8a
|
|
Add reno for:
- I1213a83ef8693c1cca1d20de974f7949a801d9f1
- Ib1103c00ddb7d6d624f4911147197d8355a3a6dd
Change-Id: Iecbbab5aeeade46b5cc238bc5542396e78db751c
|
|
As per I1213a83ef8693c1cca1d20de974f7949a801d9f1 this moves to
using KeystoneInternal for the nova-ironic template and updates
some deprecated hiera keys.
Change-Id: Ib1103c00ddb7d6d624f4911147197d8355a3a6dd
|
|
The admin endpoint is listening on the ctlplane network by default;
services should ideally be using the internal api network for this kind
of traffic, as the ctlplane network is mostly for provisioning. On the
other hand, the admin endpoint shouldn't be as relevant with services
switching to keystone v3.
Change-Id: I1213a83ef8693c1cca1d20de974f7949a801d9f1
|
|
|
|
|
|
|
|
backend."
|
|
Change-Id: I8c2e0af3ad4e47b12f4ecf2d5762df95e66fa34d
|
|
|
|
|
|
|
|
|
|
Add:
- OS::TripleO::Services::TripleoPackages
- OS::TripleO::Services::TripleoFirewall
to the CI environments, so we can test Firewalling and also TripleO
packages upgrades.
Change-Id: I5d39c7a332a4c376fb4d6ee9463d27f481b6a0d0
|
|
|
|
|
|
Upgrade nova-placement service with Ansible.
Change-Id: I43cac37afbc8b39708389895d9f7350b6bd4bcfd
|
|
|
|
These are handle by puppet as usual (puppet run comes after the
ansible steps) so remove them from these remaining upgrade_tasks
Change-Id: Ic341f31251622ccb11a5f7818b2edf7a82391560
|
|
|
|
In line with other service we leave the db sync to puppet unless
needed for some workaround/upgrade related reason.
Change-Id: I9ae463cda19ffdd66f9ccbae40e85551841ab938
|
|
Due to the keystoneauth library's defaults, it uses the public interface
currently. This is not desirable in most cases (specially when using
network isolation); so we set it to use the internal one.
Change-Id: Ic222a2b734f4d512349fd8556aa2864b13a1eb07
Depends-On: I1c7fd3a32d04e2fafb3820d1c1f221f45c613c83
Closes-Bug: #1663187
|
|
|
|
Previously the memcached configuration was set to use the defaults which
would be 95% of the avaiable ram in the system. This can lead to memory
contention issues if memcache is heavily utilized. This change reduces
the default to 50% and exposes the ability to tune this configuration.
Change-Id: Ie8a48ff4cf509e93d7c1487813d5feed5e5131a4
Closes-Bug: #1662941
|
|
Change-Id: I1bc3f37f910d6dfa833166217b1f58931d06be02
|
|
|
|
... instead of using NovaApiNetwork.
Change-Id: I34043c68c24b05bac98f864bc2ac2fc4743617ab
|
|
Default in puppet-neutron is 'RegionOne', so let's override it with the
right parameter in TripleO.
Change-Id: I3f1693b91178027c8e05288aeba72b7d6bd042be
|
|
|
|
|
|
|
|
Since gnocchi db sync for upgrade is made by puppet
we need to remove it from ansible tasks
Change-Id: I4a26513c3e3d0dcf77c007ea865364e38da3a94a
|