The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Feature #12224: openstack support for cloud provisioner through nova ec2 api
type option should not hardcode allowed flavors
|Assignee:||Dan Bode||% Done:|
|Keywords:||openstack nova cloud_provisioner||Affected URL:|
|Branch:||Affected PE version:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
The default types of openstack are the same as ec2,
The user, however, is free to create any arbitrary types that they wish. If the openstack ec2 implementation for coud provisioner plans on reusing the same type option definition as ec2, then this option definition should be smart enough to query the list of allowed types from its endpoint.
#2 Updated by Dan Bode over 2 years ago
After further research:
Fog does not actually support the ability to query for existing flavors (types). It just returns a hard-coded list. For now, I think I am going to just implement my own option definition for type that does not do validation and fail early.
If I have time, I may look into adding support for this to fog. I opened the following issue against fog: https://github.com/fog/fog/issues/715