Comment 4 for bug 962998

Well, we already allow the owner attribute to be settable when the image is created directly via:

  POST /v1/images
  x-image-meta-owner: fred
  ...

and also when the image is updated either via the glance CLI or PUT /v1/images.

So it sounds like what's needed instead is to disallow the above existing degrees of freedom on create and update.

Otherwise we'd have very inconsistent enforcement and a false sense of security by simply making the change to the image owner a little indirect but still very possible.