On 12/11/2015 08:25 PM, Alexander Tivelkov wrote:
Hi folks!
As it was decided during the Mitaka design summit, we are separating the
experimental Artifact Repository API from the main Glance API. This API
will have a versioning sequence independent from the main Glance API and
will be run as a standalone optional service, listening on the port
different from the standard glance-api port (currently the proposed
default is 9393). Meanwhile, it will remain an integral part of the
larger Glance project, sharing the database, implementation roadmap,
development and review teams etc.
Since this API will be consumed by both end-users and other Openstack
services, its endpoint should be discoverable via regular service
catalog API. This rises the question: what should be the service name
and service type for the appropriate entree in the service catalog?
We've came out with the idea to call the service "glare" (this is our
internal codename for the artifacts initiative, being an acronym for
"GLance Artifact REpository") and set its type to "artifacts". Other
alternatives for the name may be "arti" or "glance_artifacts" and for
the type - "assets" or "objects" (the latter may be confusing since
swift's type is object-store, so I personally don't like it).
I don't care about the name. In fact, I don't think the "name" should
even exist in the service catalog at all.
I think the type should be "artifact".
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev