Allow lists in config values

[mangelajo]

This may allow, for example using a list of flavors which could
not be compatible across clouds, but allowing to fall back.

For example:
os.flavor = ['mylab.4cpu.8gb.20hd', 'm1.large']

Will try the first one, and then the next one, if not found.

[mangelajo]

I need to test it locally, but still don't know how. How do I set my modified plugin to be used in my local vagrant installation?

[mangelajo]

I now understand this can be done via regular expressions /....|....|..../ , but may be it's a more intuitive way (similar to what we have with floating ip pools).

The only gain here is usability, the functionality is already there.

[julienvey]

Hi Miguel and thanks for the contribution.

I agree with you, it would be more intuitive to allow an array of floating_ip_pool. But allowing the 2 syntax is a good idea.

To test the plugin locally, you can use bundle within the source directory, for instance:

bundle exec vagrant up

The other way to test it locally (from anywhere in your path), is to create a gem from the sources and install it with vagrant itself. In the source directory

gem build vagrant-openstack-provider.gemspec
vagrant plugin install vagrant-openstack-provider-<the current version of the gem>.gem

[ggiamarchi]

I just test it, LGTM

[mangelajo]

Thank you very much @julienvey & @ggiamarchi , I will keep contributing where I find the opportunity.

[ggiamarchi]

@mangelajo Thanks again for your contribution. Don't hesitate to continue to contribute if you wish. Feel free to have a look on the non assigned issues and to pick one. Just comment the issue to inform you're working on.