Hi Steven,
This is an interesting use-case. When we designed the image repository, we
had to make a compromise between expectable behaviour and advanced
customization usage. I guess this falls into the advanced usage, but
OpenNebula is flexible enough to take this challenge.
To automatically
In
http://www.opennebula.org/documentation:rel2.0:img_guide
it says
When images are published they are always cloned, and persistent images
are never cloned. Therefore, an image cannot be public and persistent at
the same time. To manage a public image that won't be cloned, unpublish it
