The glance charm has a “ceph” network binding. This allows the glance service to be configured to have an ip on the network space where ceph lives, such that glance can talk to the ceph-mon and subsequently the ceph-osd.
The nova-compute, cinder, and ceph-radosgw charm need this same network binding. Without this there is an inconsistency where glance can be configured to talk to ceph, but cinder, nova-compute, and radosgw cannot.
@openstack-charmers - SOS
This seems like such an obvious and incredibly important bit here… I’m wondering if there is a reason those services don’t have the ceph endpoint binding? Possibly I’m just confused and missing something? Maybe its in next somewhere?