Skip to content

Components

White stone citadel towers connect through arches and aqueducts above the turquoise sea.

The entry point by component: twelve OpenStack services and nine infrastructure components, each with a page that says where the study covers it and that ends with its service card. Two more pages cut across the components: Component dependencies and Nova deep dive.

One row per service card. The columns "Role and tag", "Containers" and "Runs on" restate the card; "Runs on" is the card row "Node types running its containers", read with the Ussuri example multinode inventory (How to read a service card).

OpenStack services

Component Role and tag Containers Runs on
Keystone role keystone, tag keystone keystone, keystone_ssh, keystone_fernet control
Glance role glance, tag glance glance_api, glance_tls_proxy control
Placement role placement, tag placement placement_api control
Nova, API level role nova, tags nova, nova-api(-*) nova_api, nova_scheduler, nova_super_conductor control
Nova, cell level role nova-cell, tags nova, nova-cell(-*) nova_libvirt, nova_ssh, nova_novncproxy, nova_spicehtml5proxy, nova_serialproxy, nova_conductor, nova_compute, nova_compute_ironic compute, control
Neutron role neutron, tag neutron neutron_server, neutron_openvswitch_agent, neutron_openvswitch_agent_xenapi, neutron_linuxbridge_agent, neutron_dhcp_agent, neutron_l3_agent, neutron_sriov_agent, neutron_metadata_agent, neutron_ovn_metadata_agent, neutron_bgp_dragent, neutron_infoblox_ipam_agent, neutron_metering_agent, ironic_neutron_agent compute, control, network
Cinder role cinder, tag cinder cinder_api, cinder_scheduler, cinder_volume, cinder_backup control, storage
Horizon role horizon, tag horizon horizon control
Heat role heat, tag heat heat_api, heat_api_cfn, heat_engine control
Barbican role barbican, tag barbican barbican_api, barbican_keystone_listener, barbican_worker control
Octavia role octavia, tag octavia octavia_api, octavia_health_manager, octavia_housekeeping, octavia_worker control
Swift role swift, tag swift swift_proxy_server, swift_rsyncd, swift_account_server, swift_account_auditor, swift_account_replication_server, swift_account_replicator, swift_account_reaper, swift_container_server, swift_container_auditor, swift_container_replication_server, swift_container_replicator, swift_container_updater, swift_object_server, swift_object_auditor, swift_object_replication_server, swift_object_replicator, swift_object_updater, swift_object_expirer control, storage
Manila role manila, tag manila manila_api, manila_scheduler, manila_share, manila_data control, network

Infrastructure and dependencies

Component Role and tag Containers Runs on
MariaDB/Galera role mariadb, tag mariadb mariadb, mariadb_clustercheck control
RabbitMQ role rabbitmq, tag rabbitmq rabbitmq, outward_rabbitmq control
Memcached role memcached, tags memcache, memcached memcached control
HAProxy + Keepalived role haproxy, tag haproxy; each of the 49 per-service include_role … tasks_from: loadbalancer tasks in this play also carries its service tag haproxy, keepalived network
Common: fluentd, cron, kolla_toolbox role common; inherits the tag of the first play reaching the host (-t common alone is a no-op) fluentd, kolla_toolbox, cron compute, control, monitoring, network, storage
Open vSwitch role openvswitch, tag openvswitch openvswitch_db, openvswitch_vswitchd compute, network
OVN role ovn, tag ovn ovn_controller, ovn_northd, ovn_nb_db, ovn_sb_db compute, control, network
Chrony role chrony, tag chrony chrony compute, control, monitoring, network, storage
iscsid / tgtd role iscsi, tag iscsi iscsid, tgtd compute, control, storage

Across components

  • Component dependencies — what depends on what, in four kinds of dependency: installation, configuration, runtime and operational
  • Nova deep dive — Nova in depth: its two roles and ten plays, its dependencies, what restarts what, and the nova_libvirt restart

Roles without a component page

Other roles: the roles that place containers on compute hosts (ceilometer, multipathd, collectd, telegraf, prometheus exporters, masakari, zun, kuryr, cyborg, skydive, monasca, nova-hyperv) are in fact sheet D §5; bootstrap-servers and the operational playbooks are in fact sheet E; every play, container, role and handler is listed in Generated inventory.

How to read a component page

Every component page has the same two main parts: "Where to look", then the service card.

"Where to look" lists the sections of the study that cover the component, under these sub-headings when the study has something to list:

  • Operate — the scenario and the command lines;
  • Impact and risk — what the tag executes, and the risks;
  • Dependencies — the rows of Component dependencies;
  • Evidence — the fact sheet, the image side, and "Also";
  • Before and after a run — the checks, prerequisites and precautions the study gives;
  • Known limits and open points — known bugs, open questions, findings, and what the sources do not establish.

"Fact sheet" is the per-role evidence; "–" means no fact sheet covers the role, and the "Also" bullet says where it is traced instead.

How to read a service card

For each core service: Kolla role, play in site.yml, tags, task flow for deploy/reconfigure, templates, handlers, key variables, and the node types its play touches with the Ussuri example multinode inventory. "Play hosts" = every host matched by the play's host patterns (before enable_* filtering). "Container hosts" = hosts where at least one container of the role is placed (group-based placement; host_in_groups expressions are summarised by their groups).

In the cards, "Play hosts" is the row "Node types in play (example inventory)" and "Container hosts" is the row "Node types running its containers". There are 22 cards on the 21 component pages: the Nova page has one for the role nova and one for the role nova-cell. The cards are generated by tools/service_cards.py.