Validate service types

Should this be end-user configurable?

    valid_service_types=object-store,compute,etc

I wouldn't want arbitrarily block an implementation of keystone from properly supporting a new service.

Only services with extension:name should added. The XSD in the contract for v2.0 is limited to the core services. New services will be added as extensions until they get into core for the next version. So this config setting could result in broken contracts. If anything, it should just be used to limit extended services.

On Jan 26, 2012, at 10:21 AM, "Dolph Mathews" <email address hidden> wrote:

> Should this be end-user configurable?
>
> valid_service_types=object-store,compute,etc
>
> I wouldn't want arbitrarily block an implementation of keystone from
> properly supporting a new service.
>
> --
> You received this bug notification because you are a member of Keystone
> Bugs, which is subscribed to Keystone.
> https://bugs.launchpad.net/bugs/919013
>
> Title:
> Validate service types
>
> Status in OpenStack Identity (Keystone):
> Confirmed
>
> Bug description:
> We do not validate service types in Keystone.
>
> That also allowed erroneous documentation to sneak in:
>
> Here is the documentation the type is "storage" rather than "object-
> store": http://keystone.openstack.org/configuringservices.html.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/keystone/+bug/919013/+subscriptions

Is this still applicable, post-merge of redux?

Core service types certainly need to be well documented, but keystone should support arbitrary service types to facilitate new projects.