Open Stack

Hi,

I take a different view, possibly because I am in a similar position as the requestor.
I also work on a openstack installation, which we need to patch to our needs.
We try to do everything upstream first, but chances are, there will be changes which are not upstreamable.

We also have large user-base, and it is a great advantage to be able to point people to the official client, even if the server is not the official one.
A strict client policy would require us to fork the client as well, and distribute that to our user-base. With a couple of thousand users, that is not so trivial.
In my point-of-view, such a decision would tightly couple the client to the server for a limited benefit (a fraction of seconds earlier error message).

As a compromise, I would suggest to make the client validation configurable as in kubectl with --validate=true.

Cheers,
  Fabian