Since we do no have maas-ingress for sloop type environments we need to
exclude maas_ingress dependancy introduced in https://review.opendev.org/655571
Change-Id: I37f6046c5bb1269d3b8447b51780f71d6ec893c0
Warning: Nameserver limits were exceeded, some nameservers have been omitted,
the applied nameserver line is: 10.96.0.10 8.8.8.8 8.8.4.4
Removing 3rd DNS server entry fixes the issue.
Change-Id: I14fae0d884223050eb3106b4a9cf1adde01def8f
TimeoutError QueuePool limit of size 10 overflow 20 reached error.
This issue is resolved by increasing the max_pool_size and
max_overflow settings to the database to increase the number of
connections to keep open in a pool and the max_overflow value for
SQLAlchemy.
Change-Id: I769a446d5947de07dcc4bf3f339831bf6b45326a
This change integrates changes related to the new Patroni-enabled
high availability included in the postgresql helm chart.
1. Updates the version of the postgresql chart
2. Adds users/passphrases for the postgresql replication and exporter users
3. Sets the default number of replicas to 3 (except for skiff & sloop)
4. Adds documentation/scripting for upgrading the chart
Co-Authored-By: Evgeniy L <eli@mirantis.com>
Change-Id: I51e63fb2444610cfb144bc587a6a179fa4830809
The intention for the patch is to increase the stability of
OpenStack installation:
1. Use a single RabbitMQ cluster for all OpenStack services.
2. Use 2 replicas for RabbitMQ clusters instead of 3; RabbitMQ
does not implement a quorum mechanism which allows us to have
even number of nodes, this should provide better performance
by reducing the number of instances where the data should be
replicated. This should also reduce the odds of getting
RabbitMQ partitioning.
Co-authored-by: Drew Walters <andrew.walters@att.com>
Change-Id: Id981e2650efc24a9e67cf87a0abd414a96f40088
Airsloop is using generic kernel instead of HWE.
We may revert this once Airsloop is also aligned.
Change-Id: Ia53ef0a598034f8652ab208416e23298cf051e3f
After enablement of etcd encryption in https://review.opendev.org/628290 for
promenade, bootstrap-armada pod should be run with
'--experimental-encryption-provider-config' service parameter to avoid issue:
'ERROR: No API token found for service account "airship-ucp-ceph-osd-test"'
Change-Id: Ib9bf1fa7333874b2d88db84019b26a2691a7d18a
fluent-logging chart was splitter into fluentbit and fluentd charts
in the following PS: https://review.opendev.org/642146
Change-Id: Ic72f9fb6293b99395a0acf48064b9c04e312d365
Uplifts the Promenade image as well as other modifications required
because of recent changes to Promenade, namely:
* HostSystem schema changes for new image and new key under packages
* New chart configuration to utilize new source for hyperkube
* Refactoring names to make more sense and added new monitoring_image
Change-Id: I6c8e0c9f7c51438aa1d911c5fcd0d2f197ca37cf
BaremetalNode/v1.yaml: volume_group is
defined twice in same section in lines 58 and 66.
HostProfile/v1.yaml: volume_group is
defined twice in same section in lines 49 and 57.
SoftwareVersions/v1.yaml: type is defined twice
for dep_check
config/service_accounts.yaml: user_domain_name
defined twice in same section in lines 109 and 114.
config/service_accounts.yaml: user_domain_name
defined twice in same section in lines 111 and 116.
Change-Id: I1597c0afc6b3a9674c0c74692f6575d797bd714d
This enables coredns to run as a daemonset across the control plane
hosts, for increased resiliency. This change retains the deployment-
controlled coredns pods as well (with two replicas) to make sure there
is no interruption to DNS service while the change is rolled out in
existing Airship deployments. The deployment can be turned off in a
future release, once the daemonset is in place.
Change-Id: I4678ff2490ab36a2f5a1cc5030492d85ef70b7ac
Previous version of nfs-provisioner was 2 years old,
uplift the version to possibly fix current instabilities,
such as data-lose for MariaDB and PostgreSQL pods.
Change-Id: Iaccca71527d8f746d85509713feed1e9d057ea21
Note: all scripts in tools/deployment/aiab directory have been
moved into this repository as is (except a few changes to make
them work), they require a heavy refactoring that will be done
in separate patch-sets.
* Add a virtual single node manifests that are based on a sloop type.
* Use NFS provisioner instead of Ceph.
* Update tools/openstack to be non-seaworthy specific, use a default
region name and auth url.
* Make type/sloop/config/common-software-config.yaml to be site specific,
to allow to configure custom region_name.
* Remove max-pods-per-cpu parameter for kubelet, treasuremap needs
to support a diverse set of environments, without constraints
on the number of available cores. Max pods configuration parameter
is still present and helps to mitigate problems when kubernetes
unexpectedly starts a large number of pods.
Change-Id: I379a50d810b91b989f039dbb7c691f5ceec0cc67
Added service specific version of helm toolkit for all OSH services
in treasuremap global chart and version definitions. Kept the current
version of htk for all services to limit the changes in this commit.
Change-Id: I35cf8fce32f1e414aebd284054feb36f8305b628
Globals have logging override defined which is now different from
openstack services values in openstack-helm.
Openstack-helm addressed issue of missing logs related to warnings and
above for root logger which is catch-all logger when component specific
logger is not explictly defined.
OSH review: https://review.opendev.org/#/c/639711
Dropping logs in case of error or warnings can be problem for operators
in triaging an issue. We should not be hiding warning/error/critical logs
even when specific component logger is not defined as there can be cases
where each component is not defined in logging definition. See example
from OSH review.
In addition, is there a specific reason to have logging override for OS services
in airship side as they appear to be quite similar to defaults defined in
openstack-helm side. So may be we should revisit its need and address in
different patch if needed.
Change-Id: Iea24280546af1959d9da7164f0f18bf6a0a86e2d
