Doc: reality check on endpoint ports

Bug #1721975 reported by Matt McEuen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-helm
Low
Unassigned

Bug Description

The OSH endpoint documentation[1] says: "Some components, such as glance, provide an api port and a registry port, for example."

However, the Glance values[2] actually specify an entirely different endpoint for glance-registry, not a different port.

Which approach is correct? Should the doc or the endpoint spec be trued up?

1. https://github.com/openstack/openstack-helm/blob/8ac7ec6525f9acf3c6506cdddea96f5786ff0037/doc/source/devref/endpoints.rst
2. https://github.com/openstack/openstack-helm/blob/8ac7ec6525f9acf3c6506cdddea96f5786ff0037/glance/values.yaml#L330

Revision history for this message
Pete Birley (portdirect) wrote :

The doc here is out of date, and needs to be updated.

Changed in openstack-helm:
status: New → Confirmed
Revision history for this message
Deshi Xiao (xiaods) wrote :

@Pete Birley (portdirect) which content need update, please give me a hits. i can update it.

Revision history for this message
Matt McEuen (mm9745) wrote :

If you could help update this, it would be really awesome - I appreciate it xiaods! The code is correct and the doc is out of date.

We could just update the glance example to describe "default" vs "public" port. However maybe a different example than glance would illustrate the point better now that image_registry has been split out as a different service?

oslo_messaging has different ports for "amqp" (5672) and "http" (15672)-- perhaps that would be a better example?

Revision history for this message
Gage Hugo (gagehugo) wrote :

The registry bit can be removed IMO now that glance registry is deprecated/removed in the latest few releases.

Changed in openstack-helm:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers