Change-Id: I7934bda26a134fe38a63716f9878a27b4f3819ce

check if generated prometheus config is valid
via promtool.

This should help prevent bugs like:
https://bugs.launchpad.net/kolla-ansible/+bug/2076660

prior art: haproxy config validation:
https://review.opendev.org/c/openstack/kolla-ansible/+/922840



also add some basic documentation for the
`kolla-ansible validate-config` command.

Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Ief90861b2c422e0e6c2dd9cb605c94e86c0f2ba1

Change-Id: Ia7bd309479f098bc0b65ecf76dc294d893dadbc4

ansible-core 2.16 and later requires python 3.10+ (see [1])

[1]: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix

Change-Id: Id5e10872de413e7b476c5343360d73c109b9667a

Remove Bullseye from support matrix

Change-Id: If29ab064af9968784995115da6dd2cdf6e723c0b

Fix existing spelling errors

Change-Id: Ie689cf5a344aaa630a4860448b09242333a8e119

Change-Id: I0f35c2ea1400ea25fdb253580c6c1b2e06ae591e

support for jammy was added to yoga in:
https://review.opendev.org/c/openstack/kolla-ansible/+/869127



it should thus be perfectly fine to directly upgrade to jammy
and then upgrade to zed.

Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Id77704f4386b48c9bfd7b684bee3fb47d2b4a93a

Change-Id: I8609cf211316d8224c925d57a5e832ccff37b906

Change-Id: Iab40eb92c7e4a9092471bef9d4477a4fa34f1c85

there are currently known bugs in our interaction with the ansible
--limit option. document those and recommend not to use this like it
was agreed in the kolla meeting:
https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-02-21-14.00.log.txt



Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Iaeaa8c667ce7cd677b2b3dc2096ef4e52c1f651f

The development quickstart document has not been updated for a
while, and it has become desynchronized with the regular quickstart.

Change-Id: I6b14623b73b0032df94f0f633659a1b6dfc15dea

This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.

The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kolla_max_fail_percentage, and individual services may define a max
failure percentage via <service>_max_fail_percentage.

Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.

Closes-Bug: #1833737
Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f

Just some minor formatting and wording updates

Change-Id: Ia42944512f8d14a1993bd4ae3d09f0f2ab431322

This commit addresses a few shortcomings in the etcd service:
  * Adding or removing etcd nodes required manual intervention.

  * The etcd service would have brief outages during upgrades or
    reconfigures because restarts weren't always serialised.

This makes the etcd service follow a similar pattern to mariadb:
  * There is now a distiction between bootstrapping the cluster
    and adding / removing another member.

  * This more closely follows etcd's upstream bootstrapping
    guidelines.

  * The etcd role now serialises restarts internally so the
    kolla_serial pattern is no longer appropriate (or necessary).

This does not remove the need for manual intervention in all
failure modes: the documentation has been updated to address the
most common issues.

Note that there's repetition in the container specifications: this
is somewhat deliberate. In a future cleanup, it's intended to reduce
the duplication.

Change-Id: I39829ba0c5894f8e549f9b83b416e6db4fafd96f

Collections version taken from official Ansible 7 package [1]
and limited to the same major version.

[1]: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.7.0.yaml

Change-Id: I0f1ea9717397adc2d2c3215d74ec3759f351a57a

Change-Id: Ic26e5c06990b25572929bad275c0de35fa3552ec
Signed-off-by: chenxing <chason.chan@foxmail.com>

Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/892323

Change-Id: I11db700511233aa60229ee65d0cc96e46aafdf90

While this section of the guide does not need to explain every command
available, ``kolla-ansible genconfig`` is a useful command for people
newer to using KA, so it seems worth mentioning in the guide.

Change-Id: I6f58bb395012b701ad349e967fb3d2f16e9373c7

Ansible 2.14.3 introduced a change that broke the method used for
restarting MariaDB and RabbitMQ serially [1][2]. In
I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8 we limited to 2.14.2 to work
around this. Ansible upstream claim this behaviour was unintentional,
and will not fix it.

This change moves to a different approach where we use separate plays
with a 'serial' keyword to execute the restart.

This change also removes the restriction on the maximum supported
version of 2.14.2 on ansible-core - any 2.14 release is now supported.

[1] https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35
[2] https://github.com/ansible/ansible/issues/80848

Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208

Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff

Followup on I34fd1dcb52cffd9d545d10526109772aeebc2393

Change-Id: I3a14f85fbe5be6ae635774c49872e17f5daea805
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

Where a list item has multiple paragraphs, the additional paragraphs
must be indented by three spaces (i.e. the level of the first paragraph)
to be considered part of the list item.

Change-Id: I34fd1dcb52cffd9d545d10526109772aeebc2393
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

We limit to 2.14.2 due to a regression in ansible-core [1] that breaks
conditional include_task loops in handlers. This is used for controlled
restarts of MariaDB and RabbitMQ.

[1]: https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35



Change-Id: I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8
Co-Authored-By: Michal Nasiadka <michal@stackhpc.com>

This reverts commit 9867060b.

Reason for revert: seems this broke some jobs

Change-Id: I1ca81214ece403351c0a522ea05bf07802e4c4c0

Change-Id: Ibc9cc91f64b0450de3cae6e2830b4ff2c52c0395

Remove notes referring to old releases (Train, Victoria). Add a note to
cover migration to RL9.

Change-Id: I57bcc9c3967fb6cdea56cb9a252255322ec2f1c9

Users running on a Focal host will now fail in prechecks.

Change-Id: Icaef4b25458490e46f623b055658abc678d2f1c6

As per the RBAC new direction in Zed cycle, we have dropped the
system scope from API policies and all the policies are hardcoded
to project scoped so that any user accessing APIs using system scope
will get 403 error. It is dropped from all the OpenStack services
except for the Ironic service which will have system scope and to
support ironic only deployment, we are keeping system as well as project
scope in Keystone.

Complete discussion and direction can be found in the below gerrit
change and TC goal direction:

- https://review.opendev.org/c/openstack/governance/+/847418
- https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#the-issues-we-are-facing-with-scope-concept

As phase-2 of RBAC goal, services will start enabling the new
defaults and project scope by default. For example: Nova did in
- https://review.opendev.org/c/openstack/nova/+/866218

Kolla who start accessing the services using system scope token
- https://review.opendev.org/c/openstack/kolla-ansible/+/692179

This commit partially revert the above change except keeping
system scope usage for Keystone and Ironic. Rest all services are changed
to use the project scope token.

And enable the scope and new defaults for Nova which was disabled
by https://review.opendev.org/c/openstack/kolla-ansible/+/870804

Change-Id: I0adbe0a6c39e11d7c9542569085fc5d580f26c9d

Users of aarch64 architecture need to set tag suffix if they use
official images.

Change-Id: Iefc2e736d23e0e86ed55d8225e71857fb997a4c3

In the quickstart there is need the git package to install
kolla-ansible from the source for deployment or evaluation and
to clone repository for development.

Closes-Bug: #1999370
Change-Id: Ia623694c801c03b151944947141551ecbc1d24f5
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

There are too many ways in one guide for the deployment. This
makes it hard for newcomers to stay at one track and get a working
installation. I reworked this from many possible ways to two.
Only virtual enviroment and non virtual enviroment. For the
developer guide I will make a new patchset.

Signed-off-by: Ramona Beermann <rautenberg@osism.tech>
Change-Id: I0c8739077ad41609596f7687bf2fd3628eb082c5

Follow up patch from https://review.opendev.org/c/openstack/kolla-ansible/+/861953



Signed-off-by: Ramona Beermann <ramona.beermann@osism.tech>
Change-Id: Ia21bb4ccadf0104c8e049bb7b8091d4742f6c1c1

We agreed that CentOS Stream 9 images are not published as we keep it
for CI use only (to check potential failures before it hits RHEL).

We recommend Rocky Linux 9 instead.

Change-Id: I06e6746e5c2abbdcd97912ea2f99d82fc662531d

Some time ago we dropped RHEL as one of possible options. During 'Zed'
cycle we added Rocky Linux 9 as alternative to CentOS Stream 9.

This change updates some mentions of both.

Change-Id: I9ed93efcb7d1ff97b1c7d8342db8252aba2a9887

It's a followup to 73a1812c
addressing post-merge comments.

Change-Id: Idd458ad6ef29e4eee2f9e537b4eae39d26eb9f64

As we disabled docker bridge network, we should run docker registry
with host network now.

Change-Id: I4cc4175ddc9b90847bf956007e2b9fe803960651

openEuler 20.03 LTS SP2 is out of date. This patch:
1. Upgrade openEuler to 22.03 TLS for host OS.
2. Switch guest OS from centOS 8 to ubuntu

Change-Id: If2ff036e965def141f67240945802611e1f4dc4e

clouds.yaml[0] is a richer way to express configuration for OpenStack
clouds. It's also fully supported by Ansible's OpenStack modules as
well as python-openstackclient and openstacksdk. It's the future - who
doesn't like the future?

Write a file using both the public (default) and the internal endpoints
for the admin user. Also, change all of the examples to reference it
and to get python-openstackclient to use it too.

[0] https://docs.openstack.org/openstacksdk/latest/user/guides/connect_from_config.html

Implements: blueprint use-clouds-yaml
Change-Id: I557d2e4975c7b3d3c713a556b9ba47af9567ce6e

This change introduces automated configuration of firewalld and adds
a new filter for extracting services from the project_services dict.
the filter selects any enabled services and their haproxy element
and returns them so they can be iterated over.
This commit also enables automated configuration of firewalld from enabled
openstack services and adds them to the defined zone and reloads the
system firewall.

Change-Id: Iea3680142711873984efff2b701347b6a56dd355

Per comments on [1].

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/843727

Change-Id: I60162b54bc06e158534d29311d4474b34750c64d