The [glance]glance_api_servers configuration option has been deprecated
since Pike and removed in 2019 per Ironic commit
dcfb4f10f31c11afa350ef6418a0e12e6be6e5b2. Removing from ironic.conf
template.
Change-Id: I3b09514635ee0c8665c425bd1fe42fb594361a0e
The value for default_boot_interfaces must be supported by all
configured drivers, otherwise conductor won't start. This configuration
can be applied as an override by the operator, if necessary, rather
than OSA.
Change-Id: I780a1f130b0c695822ba50066247688bf4874dac
This patchset adds support for deploying instances using UEFI baremetal
nodes. UEFI may replace Legacy BIOS mode in future Ironic releases. Tested
with Ubuntu Focal 20.04 LTS.
Change-Id: I0fa6234ec7321e1d69901175baeab4ddb08afc50
- Implemented new variable ``connection_recycle_time`` responsible for SQLAlchemy's connection recycling
- Set new default values for db pooling variables which are inherited from the global ones.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/819424
Change-Id: I1c90ce68ce218d538cd89b111dc1ee4142f14eef
This patch fixes at least one issue related to ironic-conductor and
its inability to report to Nova based on lack of Nova-related
configuration in ironic.conf.
Change-Id: I96aac9f0f2c1e9bdb6ebd601ee3546ad13e0d927
With PKI role in place in most cases you don't need to explicitly
provide path to the CA file because PKI role ensures that CA is trusted
by the system overall. In the meanwhile in PyMySQL [1] you must either
provide CA file or cert/key or enable verify.
Since current behaviour is to provide path to the custom CA we expect
certificate being trusted overall. Thus we enable cert verification when
galera_use_ssl is True.
[1] 78f0cf99e5/pymysql/connections.py (L267)
Change-Id: I79e43119830da22f09d7666b25054c6c14c28ffb
Since iSCSI deploy has been removed [1] we should also replace iscsi deploy with direct
since it's suggested deploy option.
[1] https://review.opendev.org/c/openstack/ironic/+/789382
Change-Id: I72f166b2fdd808b623e698f44c4d77747cc987bb
We've created integrated linters check job a while back and it's successfully
working for several releases. At the moment we experience difficulties
with future maintenance of the linters check from the openstack-ansible-tests
repo. So instead of fixing current one, we replace it with modern version of
the test.
Change-Id: I409671bd6c28dc5fa21b292cabf082b5671532ef
Instead of overriding each service separatelly it might make
sense for deployers to define some higher level variable that
will be used first or fallback to default variable.
Change-Id: Ib2928efaa35bd82f6e6f65fecf32cf8da2eb9f5d
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to replace policy.json to
policy.yaml and remove deprecated policy.json.
config_template has been choosen instead of the copy, since it can
properly handle content that has been lookuped.
We make a separate task not to restart service when it's not needed.
[1] https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I701473f4d99e0be06dea494eee4f08212bb7d853
All references to Gentoo, SUSE, Debian stretch and Centos-7 are removed.
Conditional tasks, ternary operators and variables are simplified where possible
OS specific variables files are generalised where possible
Change-Id: Ia73e88947f52a74d9c03a17a7b1201a6346b5ac3
This is necessary to use the new pip resolver
Depends-On: I6003a1004b6042a804ea142684b42b17f16d6da8
Change-Id: I06958da8881c93abde25c114d06943d777ea2b0a
Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: I406244b8d8bfe109e9db74bd6cf5cfb9f7a7bbf7
We use the same condition, which defines against what host some "service"
tasks should run against, several times. It's hard to keep it the same
across the role and ansible spending additional resources to evaluate
it each time, so it's simpler and better for the maintenance to set
a boolean variable which will say for all tasks, that we want to run
only against signle host, if they should run or not now.
Depends-On: https://review.opendev.org/758953
Change-Id: Iab3194322e133282fcb71830f2b94e1279106ebd
This patch allows ironic-inspector to listen on host IP
rather than 0.0.0.0, as well as allows an existing Neutron-managed
inspection network to be used for inspection traffic.
Change-Id: I645857ad62954f08b160e5889f93dc1f6423def2
Even the most modest 4C/8T system would run with the maximum 16 processes
due to the calculation being VCPU*2.
We devide amount of CPUs to number of threads for hyperthreaded CPUs
Change-Id: I67c151181cc358b1adb2ee4dc7aab8fbff2c25ba
This patchset adds support for iPXE, which can speed up baremetal
provisioning considerably due to the use of HTTP versus TFTP.
Change-Id: I8b49ae37a0380cd7a2191f050a52c85cc373026b
When we were migrating service to uwsgi usage, we clean forgot to
trigger uwsgi restart on service config change.
Depends-On: https://review.opendev.org/758953
Change-Id: Iaf42be11b69bd2630c3f2e929ccff8b9ad9f0639
Move it to the service setup host (defaults to utility[0]) instead
of the galera[0] host, and use galera_address (defaults to internal VIP)
as the endpoint instead of a local connection on the db host.
Change-Id: I87d61c619920a945c7a0b0887e3902f39f2b1b3c
We missed adding ironic-inspector to constraints which resulted
in installing always the latest avaialbe version in the pypi.
Depends-On: https://review.opendev.org/746931
Change-Id: I9a6e7273f752b6bdc1639be299e00933889b6cc9
