I don’t think I have a perfect answer here, but just to add fodder to the discussion: it’s often been suggested in the past that one way of dealing with this is to simply ensure that you can bring your image to any cloud you work with. Thus, rather than relying on an image to be named the same across the clouds you deal with, you can simply provide it yourself on those clouds so you know it’s identical. Many of the caveats to this approach should be fairly obvious (footprint, duplication, quotas, format conversion, etc), but for some workflows it provides the sorts of useful guarantees an end user may want.
At Your Service,
Mark T. Voelker
On Apr 7, 2019, at 5:35 PM, Mohammed Naser mnaser@vexxhost.com wrote:
Hi everyone,
Something that I've been dealing with is the fact that regardless of what cloud you're using, the naming structure is very much different. While we aim to be interoperable, if I want to "boot an Debian Stretch server", the image name will probably be different all over the places.
Is there some sort of way we can eliminate this by implementing a standard naming convention which would allow us to use the same images across all systems?
I'm just opening the idea for discussion, I'd love to hear what others think about this.
Mohammed
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvexxhost.co...