Ask Your Question

Revision history [back]

If you set image visibility to private (openstack image set --private IMAGE-ID), as recommended by the Ocata installation guides, they can only be seen by the project that owns them, and the admin project.

I don't know if images can be hidden from the admin project, if that is your particular problem.

Note that the Trove developer web site has images owned by the trove project, and they have public visibility.

If you set image visibility to private (openstack private (openstack image set --private IMAGE-ID), IMAGE-ID), as recommended by the Ocata installation guides, they can only be seen by the project that owns them, and the admin project.

I don't know if images can be hidden from the admin project, if that is your particular problem.

Note that the Trove developer web site has images owned by the trove trove project, and they have public public visibility.

If you set image visibility to private (openstack image set --private IMAGE-ID), as recommended by the Ocata installation guides, they can only be seen by the project that owns them, and the admin project.

I don't know if images can be hidden from the admin project, if that is your particular problem.

Note that the Trove developer web site has images owned by the trove project, and they have public visibility.visibility. I wonder if setting them to private in this configuration breaks Trove?

If you set image visibility to private (openstack image set --private IMAGE-ID), as recommended by the Ocata installation guides, they can only be seen by the project that owns them, and the admin project.

I don't know if images can be hidden from the admin project, if that is your particular problem.

Note that the Trove developer web site has images owned by the trove project, and they have public visibility. I wonder if setting them to private private in this configuration breaks Trove?