Dynamically Support Friendlier Images and/or Flavors

[hartmantis]

#17 added a hash of friendly image names:Rackspace image IDs. The next step beyond that would be to grab the available images and flavors from Fog and parse those so this project doesn't need updates each time there's a new image released.

[filler]

This is pretty much done with #17 , no?

[hartmantis]

As it was worded, very true. I've updated the description to reflect the current state of things.

[maxlinc]

@RoboticCheese I recommend doing what vagrant-rackspace does. It let's users specify the image as any of:

• ID (e.g. 928e709d-35f0-47eb-b296-d18e1b0a76b7)
• Name (e.g. Ubuntu 12.04 LTS (Precise Pangolin) (PVHVM))
• Regex (e.g. /precise.*pvhvm/i)

[martinb3]

As long as the compatibility with the vagrant box names is maintained, I'm okay with also allowing IDs/Names/Regexes. E.g. as long as 'centos-65' still works, as that will keep the configurations usable across different test-kitchen drivers. I regularly switch between kitchen-vagrant and kitchen-<rackspace/aws/etc>, and so do many other projects.

[maxlinc]

Yeah, it would still work fine, because the keys (which are what match vagrant) would remain the same. I'm just talking about mapping the keys to more maintainable values.

[martinb3]

With #48 and Rackspace dropping point releases from names, my colleagues and I are stuck in a position of having kitchen-vagrant platforms and kitchen-rackspace platforms that don't overlap. We want to switch back and forth from those two drivers, but there's no platform strings they have in common for CentOS.

It feels like regex support may be something useful for all the drivers.