Orientation
Once you have deployed an initial OpenStack Cluster let's go over where things are and some ways to access them and view your environment.
Clustered Services
In a multinode deployment, it's important to understand where the services are deployed and how they are clustered. Kolla deploys the following services in a clustered fashion:
Database
Kolla deploys MariaDB as the database for OpenStack and is deployed as a Galera Cluster. It is recommended to have at least 3 nodes in the cluster to allow for one failure. You can also have five nodes in the cluster to allow for two failures. The database is deployed with a VIP that is managed by Keepalived and HAProxy. This allows for a single endpoint for the database cluster.
Message Queues
Kolla deploys RabbitMQ cluster as the message queue for OpenStack. RabbitMQ is how most of the OpenStack services communicate to each other.
Containers
By default, Kolla will deploy all of the OpenStack services as containers. It uses Docker by default and you can view the containers by running the following command:
docker ps -a
And you should see something like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c24fce0305d2 quay.io/openstack.kolla/horizon:2023.1-rocky-9 "dumb-init --single-…" 12 hours ago Up 12 hours (healthy) horizon
5b55e00d9500 quay.io/openstack.kolla/heat-engine:2023.1-rocky-9 "dumb-init --single-…" 12 hours ago Up 12 hours (healthy) heat_engine
109815d2712f quay.io/openstack.kolla/heat-api-cfn:2023.1-rocky-9 "dumb-init --single-…" 12 hours ago Up 12 hours (healthy) heat_api_cfn
a452dc750c11 quay.io/openstack.kolla/heat-api:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) heat_api
cc13b1fc47c5 quay.io/openstack.kolla/neutron-metadata-agent:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) neutron_metadata_agent
a337151e6d44 quay.io/openstack.kolla/neutron-l3-agent:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) neutron_l3_agent
51c9989de169 quay.io/openstack.kolla/neutron-dhcp-agent:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) neutron_dhcp_agent
96a0a406612d quay.io/openstack.kolla/neutron-openvswitch-agent:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) neutron_openvswitch_agent
53510ee8ed3e quay.io/openstack.kolla/neutron-server:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) neutron_server
858d3fba3694 quay.io/openstack.kolla/openvswitch-vswitchd:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) openvswitch_vswitchd
1d59c55f2086 quay.io/openstack.kolla/openvswitch-db-server:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) openvswitch_db
baeaae78a8f9 quay.io/openstack.kolla/nova-compute:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_compute
4a92866937d2 quay.io/openstack.kolla/nova-libvirt:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_libvirt
af7ee25c196a quay.io/openstack.kolla/nova-ssh:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_ssh
aeaef52c451e quay.io/openstack.kolla/nova-novncproxy:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_novncproxy
ac45d763f22f quay.io/openstack.kolla/nova-conductor:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_conductor
8ca39b83e877 quay.io/openstack.kolla/nova-api:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_api
4e30b3786304 quay.io/openstack.kolla/nova-scheduler:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) nova_scheduler
efbfec7aa638 quay.io/openstack.kolla/placement-api:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) placement_api
dadc7f7e8e2f quay.io/openstack.kolla/glance-api:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) glance_api
72d513a231d4 quay.io/openstack.kolla/keystone:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) keystone
6276dc91e795 quay.io/openstack.kolla/keystone-fernet:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) keystone_fernet
813f6dcf753e quay.io/openstack.kolla/keystone-ssh:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) keystone_ssh
4d191547086c quay.io/openstack.kolla/rabbitmq:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) rabbitmq
39ea9399429f quay.io/openstack.kolla/memcached:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) memcached
b79e23c8d3c8 quay.io/openstack.kolla/mariadb-server:2023.1-rocky-9 "dumb-init -- kolla_…" 13 hours ago Up 13 hours (healthy) mariadb
c30e599f8dab quay.io/openstack.kolla/mariadb-clustercheck:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours mariadb_clustercheck
5cba073ef1d3 quay.io/openstack.kolla/keepalived:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours keepalived
c1c4fcff19e1 quay.io/openstack.kolla/haproxy:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours (healthy) haproxy
5f42fbcafb7c quay.io/openstack.kolla/cron:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours cron
c7a6813a4adc quay.io/openstack.kolla/kolla-toolbox:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours kolla_toolbox
df582147019d quay.io/openstack.kolla/fluentd:2023.1-rocky-9 "dumb-init --single-…" 13 hours ago Up 13 hours fluentd
If you want to enter a container, you can use the following command:
docker exec -it nova_compute -u 0 /bin/bash # for superuser access or
docker exec -it nova_compute /bin/bash # for non-superuser access
This is useful for debugging and troubleshooting issues with the containers. You can also use the docker logs command to view the logs of the containers.
docker logs -f nova_compute
Podman support is also coming in 2023.2.
Config and Log Locations
By default there are a few places where Kolla will store configuration files and logs. These locations are:
/etc/kolla- Location of the configuration files for the containers it deploys and where all of the configs are generated during the Kolla-Ansible run that the containers use/var/log/kolla- This is where Kolla stores the logs for the containers it deploys. This is also where you can store your own logs for the services.
When the containers load, they reference the configurations in /etc/kolla/<<service>> and use those configs when starting the individual services in the containers. This allows you to make changes to the configuration files in /etc/kolla/ and then restart the containers to pick up the changes if you are testing something out. This is useful if you need to enable debug logging or change a configuration setting temporarily. In order to make it permanent you will want to make the change in the globals.yml file or overrides directory and then re-run kolla-ansible deploy.