Infrastructure
Loadbalancer
For the manage-loadbalancer play to work, the internal control socket
of the HAProxy service must be set to admin level. This is the default.
You can check in the HAProxy configuration whether the control socket is configured correctly.
global
[...]
stats socket /var/lib/kolla/haproxy/haproxy.sock group kolla mode 660 level admin
-
Disable the host
testbed-node-0in all backends of the servicekeystoneosism apply manage-loadbalancer \-e manage_loadbalancer_action=disable \-e manage_loadbalancer_service=keystone \-e manage_loadbalancer_host=testbed-node-0 -
Enable the host
testbed-node-0in all backends of the servicekeystoneosism apply manage-loadbalancer \-e manage_loadbalancer_action=enable \-e manage_loadbalancer_service=keystone \-e manage_loadbalancer_host=testbed-node-0 -
Disable the host
testbed-node-0in all backendsosism apply manage-loadbalancer \-e manage_loadbalancer_action=disable \-e manage_loadbalancer_service=all \-e manage_loadbalancer_host=testbed-node-0 -
Enable the host
testbed-node-0in all backendsosism apply manage-loadbalancer \-e manage_loadbalancer_action=enable \-e manage_loadbalancer_service=all \-e manage_loadbalancer_host=testbed-node-0
MariaDB
Backing up the control plane database and restoring it are covered under MariaDB Backup & Restore.
Recovery
If you stopped your mariadb galera cluster completely, you can use the following procedure to start a recovery.
osism apply mariadb-recovery
Create database & user
-
Create a custom play
playbook-database-sample.ymlinenvironments/kollain the configuration repository.---- name: Manage sample databasehosts: controlvars:database_sample_username: sampledatabase_sample_name: sampletasks:- name: Create sample databasebecome: truekolla_toolbox:container_engine: "{{ kolla_container_engine }}"module_name: mysql_dbmodule_args:login_host: "{{ database_address }}"login_port: "{{ database_port }}"login_user: "root"login_password: "{{ database_password }}"name: "{{ database_sample_name }}"run_once: true- name: Create sample userbecome: truekolla_toolbox:container_engine: "{{ kolla_container_engine }}"module_name: mysql_usermodule_args:login_host: "{{ api_interface_address }}"login_port: "{{ mariadb_port }}"login_user: "root"login_password: "{{ database_password }}"name: "{{ database_sample_username }}"password: "{{ database_sample_password }}"host: "%"priv: "{{ database_sample_name }}.*:ALL"append_privs: Truerun_once: true -
Add secret
database_sample_passwordinenvironments/kolla/secrets.ymlin the configuration repository. -
Commit the custom play and the secret. Sync the configuration on the manager node with
osism apply configuration. -
Run
osism apply xxxon the manager node.
Open Search
Get all indices
$ curl https://api-int.testbed.osism.xyz:9200/_cat/indices?v
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open flog-2024.04.17 1rCP3NpUQSS5wmulCn6Y5g 1 1 1657832 0 1gb 654.4mb
green open .opensearch-observability UnS2gFb-QhC8oIefL3C52Q 1 2 0 0 624b 208b
green open .plugins-ml-config hMdzW6ooRMGZ_0OGcdNSgA 1 1 1 0 7.8kb 3.9kb
green open .opendistro-job-scheduler-lock fa_Io8bJQ8qfGII4DypxFg 1 1 1 3 51.1kb 35.1kb
green open .kibana_1 v-aJ6ioSQsOwHQn_NNbeOg 1 1 0 0 416b 208b
Delete an index
$ curl -X DELETE https://api-int.testbed.osism.xyz:9200/flog-2024.04.17
{"acknowledged":true}