Until Ocata, there were only two image visibility values: 'private' and 'public'. Thus a shared image had visibility 'private' because it was not a public image.
The confusing aspect is that the image-list filter in the Image API v2 that's used to list shared images is: GET v2/images?visibility=shared ... but none of the images in that list actually had 'visibility' == 'shared'.
This is being changed in Ocata. As part of the community images implementation, the values for 'visibility' are being expanded to {'public', 'private', 'shared', 'community'}. So with the Ocata release, the visibility of a shared image will be 'shared'.
Until Ocata, there were only two image visibility values: 'private' and 'public'. Thus a shared image had visibility 'private' because it was not a public image.
The confusing aspect is that the image-list filter in the Image API v2 that's used to list shared images is: GET v2/images? visibility= shared ... but none of the images in that list actually had 'visibility' == 'shared'.
This is being changed in Ocata. As part of the community images implementation, the values for 'visibility' are being expanded to {'public', 'private', 'shared', 'community'}. So with the Ocata release, the visibility of a shared image will be 'shared'.