The log metrics service generates metrics from log messages
which allows further analysis and alerting to be performed
on them. Basic configuration is provided so that metrics
are generated for high level warning logs such as error, or
warning.

Change-Id: I45cc17817c716296451f620f304c0b1108162a56
Partially-Implements: blueprint monasca-roles

Change-Id: Id8948fcf2d165f8285c7562e7aebd4145c4ff0db
Partially-Implements: blueprint monasca-roles

Set sensible defaults for replica counts and minimum insync replicas
as a function of the number of nodes in the Kafka cluster.

Partially-Implements: blueprint monasca-roles
Change-Id: Icf1dddb7dd6a64f4e5efb7dffa5ffdf0880f891f

This option doesn't actually do anything and a bug to remove
it from the Monasca API config file has been raised.

Partially-Implements: blueprint monasca-roles
Change-Id: I7ec1786b5828ab0135ca86ec040f83a6f4c78d9f

Change-Id: I0444b23aee900d028c879ec64d153d59a18ff504

 - Uses swift if swift is enabled.
 - Uses ceph if ceph is enabled.
 - Defaults to file if swift and ceph are enabled.
   Explicitly set to swift or ceph when both are enabled.
 - Include swift client detail in storage section of gnocchi conf

Change-Id: I78df9a2fbe546038e1d6df350d8db0fd9b6f6d49

Depends-On: I75e00312b36e1678b90a42cf58d24652323eff27
Change-Id: Ia716fabffca41eff816e59bbf9f4cab79ee8b72f

Fix a typo in the policy task name

Change-Id: I43b9c1ea1e3ff4bef1713c889e2cb885207abb0e

Add a possibility to mount sources as volumes to containers,
in "more than documentation" way. That will let us to use kolla
as a replacement for devstack.

Partially implements: blueprint mount-sources
Co-Authored-By: wu.chunyang <wu.chunyang@99cloud.net>

Change-Id: Ia3112a0d297ac777e1f25d3ddecced7746ca6418

Change-Id: Ia1fa141acd7233f0c9dd30dd3d13e31cf1a2fb8e

Alembic uses the monasca-agent config file for the DB
credentials. These are therefore no longer required.

Partially-Implements: blueprint monasca-roles
Change-Id: Id076e7a0b838888314159dd9e76697f89adecb5e

This patchset apply Nova rolling upgrade logic [1]

[1] https://docs.openstack.org/nova/latest/user/upgrade.html



Implements: blueprint apply-service-upgrade-procedure

Co-Authored-By: Ha Manh Dong <donghm@vn.fujitsu.com>
Depends-On: https://review.openstack.org/#/c/558765/
Change-Id: I20531a25dc7f5b05dc70ba771cf4c4222ade33e3

For now, we use api interface/network for Octavia.

This change will make more flexible for Octavia deployment
with Kolla when we want to use another network for managing
amphora instances (config, health check, clean up)

Change-Id: Ief12f1f8b6c7d3974932e6320af95bb58d46bdb9
Co-Authored-By: Duc Nguyen Cong <ducnc7@viettel.com.vn>
Closes-Bug: #1791207

Change-Id: I5bc56c843e1d8986b1c7bf649a6f8dafc0928e0b
Closes-Bug: #1793637

Add support to remove images from kolla_docker
ansible module.

Change-Id: Ib6bcb98b5b295a2d590df3013188913d1f7f3584

Since glance_api only start one container when using file
backend, the haproxy should follow this rule.

See: https://review.openstack.org/#/c/448654

Closes-Bug: #1722422

Change-Id: Id3519581e0f54509dacd24d0dd542c630342c771

Co-authored-by: Mark Goddard <mark@stackhpc.com>
Change-Id: I2e5ecf5b01cc842ec480fc4d883a7d2283fc1c31

backport: rocky

Change-Id: Id437c26376f80462369db1fb3888db2098278f16
Closes-Bug: #1791686

Since I701d495675178c3ed8ec1f00b31d09f198b38a6f merged, etcd only runs
on the control hosts, not the compute hosts. We therefore no longer
require the etcd group to include the compute hosts.

Since the group mapping is now static, we can remove the use of
host_in_groups from the etcd service, in favour of the simpler method of
specifying the group.

Change-Id: Id8f888d7321a30a85ff95e742f7e6c8e2b9c696f
Related-Bug: #1790415

Without this, kolla-ansible check fails with the following error:

Unable to retrieve file contents
Could not find or access '/path/to/kolla-ansible/ansible/check.yml'"}

Also adds the check command to the CI tests, to ensure that it does not
break again.

Change-Id: I9fc2f9999f55cb742ac3ac38579dcf26524a9fc7
Closes-Bug: #1790653

In before, etcd container is launched in compute node if kuryr is
enabled. This logic breaks the all-in-one setup in which the etcd
cluster is configured with two members (controller and compute)
but it actually has one member only.

However, even if kuryr is enabled, running etcd in compute node
is not the common practice and kuryr has changed its devstack
plugin to run etcd on controller only [1].

[1] https://review.openstack.org/#/c/514815/

Closes-Bug: #1790415
Change-Id: I701d495675178c3ed8ec1f00b31d09f198b38a6f

Change-Id: Ia459d8b9925b22b23c90a33364da6ef40f4b1a70

The destination folder for this task requires root permissions.

Change-Id: Icdc37cde7ba7b6971cf36632a9b6071b3cf600c2

The current bluestore disk label naming is inconsistent with the
filestore. The filestore naming format is that the disk prefixes
belonging to the same osd are the same and the suffixes are
different.

This patch keeps the bluestore's disk naming as well.

Change-Id: I71dda29fc4a6765300ce7bb173d2c448c24f6eca

when creating Nova databases user and setting permissions,
no need to register the database_user_create, and it used
nowhere, remove it is safe

Change-Id: If456b7c2ed25aa729be7d98ef875230c66581d65

As of https://review.openstack.org/596502/ in Stein
the RamFilter in nova is deprecated. It is not needed
when using the filter_scheduler driver (which is the
default scheduler driver).

Change-Id: Iee3dab7b5dc7074e9840826afe58ce2bfa40a3df

Add a possibility to mount sources as volumes to containers,
in "more than documentation" way. That will let us to use kolla
as a replacement for devstack.

Partially implements: blueprint mount-sources
Co-Authored-By: zhulingjie <easyzlj@gmail.com>

Change-Id: I10677e5ad22f2107a0657feeeaf32287ab9f8e28

If you use COPY_ALWAYS, kolla will overwrite /etc/redis/redis.conf.
But Redis Sentinel will store myid in this file. So when it restart,
Redis Sentinel will regenerate new myid every time. Redis Sentinel
cluster will see more and more sentinel, This patch use hash value
with hostname as sentinel myid.

Change-Id: I6d9403231e41baac177f29c58e67ba605795385d
Closes-bug: #1788179

In order to migrate to the latest release of rabbitmq (3.7), we need to
first remove this deprecated plugin which is no longer supported (the
problems it solved are now addressed in rabbitmq itself).

This avoids a circular dependency in CI where the new images depend on
the new clustering and the new clustering depends on the new images.

Change-Id: I921459f3e40b9e0d4af9497384e49aabf0abe79b

now,the trove does not support policy customization.
this ps to add it.

Change-Id: I32d62d0293ddf63572cf754a7108ed74f94b216a

Monasca defaults to using the public endpoint to register
Monasca endpoints which is bad practice and doesn't work on
some deployments. This change uses the admin interface by
default.

Change-Id: Ia9c5e041e71867fe72aad43e1344cd2107652d7d
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Closes-Bug: #1787610

To create a magnum cluster, its required to specify
'default_docker_volume_type' with some default value (default cinder
 volume type). And, it also enables users to select
diffferent cinder volume types for their volumes.

Change-Id: I50b4c436875e4daac48a14fc1e119136eb5fd844

Change-Id: Icc949ce71fb2788d8aa91346bf8559c2c11bcb2c
Close-Bug: #1787097

When deploying designate if no designate_forwarders_addresses
is provided, bind9 container keeps restarting due an invalid(empty)
forwarder addresses is set in named.conf

Change-Id: I7d309eb077243435dd2038629074251abec7d3e1
Closes-Bug: #1787092

Now kolla dev mode only support clone master branch from git,
add version tag to support clone dedicated branch.

Change-Id: I88de238e5dc7461ba0662a3ecea9a2d80fd0db60

Disable neutron-lbaas-agent and use lbaasv2-proxy  when enable octavia.
Use keystone-auth v3 and internal endpoint for lbaasv2 plugin.

Change-Id: I69e8436f3722cf99644457323b71b94dc9036bb9
Co-Authored-By: Hieu LE <hieulq2@viettel.com.vn>
Closes-Bug: #1756771
Closes-Bug: #1738115

With the more recent versions of ansible, we should now use
"is" instead of the "|"

This should update it.

Change-Id: I6fba56fca182349972e8b0ee5452b37aa4090e0c

shara_api need auth_url arguments in keystone_authtoken group.
follow the configure document[0], the auth_url should under
trustee group. but the keystone use default "keystone_authtoken "
group to authenticate,if we wanna use trustee group to authenticate,
we need add "auth_section=trustee" under keystone_authtoken group
,when add this , the trustee group also need auth_type which sahara
have not register into oslo_config.when add to register,the username may
hardcode[1],so i think the best way to reslove this problem is to
add auth_url under keystone_authtoken

[0]https://docs.openstack.org/sahara/latest/configuration/descriptionconfig.html
[1]https://github.com/openstack/sahara/blob/d60a3b152b4ff3ba48cb9199eac1aad8e182f6e1/sahara/utils/openstack/keystone.py#L41

Change-Id: I7e94cf56fa38f01e2b3d93303f8192cb66ba76ab

fix monasca api warning,the new config file name is api.conf

Change-Id: Iabfbeab45d4e16602781d5fdf1ff0b2b67168d77
Closes-Bug: #1784656

Tacker is failing registering VIM monitoring
into mistral because the v3 in the auth url.

The auth url is being used auth_url + '/v3' in the code,
ending in a http://url:35357/v3/v3

https://github.com/openstack/tacker/blob/210d8f93bb5e7e179bff176d98d3079ab7f33ca0/tacker/nfvo/nfvo_plugin.py#L93


Change-Id: If5abbee1377ecdb2913a42bdfa77e7fbbfbe9367