Jesse - they're appended to the physical host's name to make the containers. So, as an example: aio1-nova_api_metadata_container-dcbb9152. aio1 is the host name, nova_api_metadata_container is the group name from inventory, and the hash is generated on first run. nova_api_metadata_container is taken from playbooks/inventory/env.d/nova.yml L38.
There's also the option of not using the group names, though I think it's useful for managing a deployment to identify what container is associated with what function by name.
Jesse - they're appended to the physical host's name to make the containers. So, as an example: aio1-nova_ api_metadata_ container- dcbb9152. aio1 is the host name, nova_api_ metadata_ container is the group name from inventory, and the hash is generated on first run. nova_api_ metadata_ container is taken from playbooks/ inventory/ env.d/nova. yml L38.
There's also the option of not using the group names, though I think it's useful for managing a deployment to identify what container is associated with what function by name.