The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #12226

Feature #12224: openstack support for cloud provisioner through nova ec2 api

type option should not hardcode allowed flavors

Added by Dan Bode over 2 years ago. Updated 10 months ago.

Status:RejectedStart date:01/27/2012
Priority:NormalDue date:
Assignee:Dan Bode% Done:

0%

Category:cloud provisioner
Target version:-
Keywords:openstack nova cloud_provisioner Affected URL:
Branch: Affected PE version:

We've Moved!

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.


Description

The default types of openstack are the same as ec2,

([‘m1.small’,‘m1.large’,‘m1.xlarge’,‘t1.micro’,‘m2.xlarge’,‘m2.2xlarge’,‘x2.4xlarge’,‘c1.medium’,‘c1.xlarge’,‘cc1.4xlarge’])

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.

History

#1 Updated by Dan Bode over 2 years ago

I will be exploring this to ensure that the ability to query a valid type listing is supported by fog, ec2, and nova’s ec2 implementation.

As an alternative, I can just have the openstack face implement its own definition of the type option.

#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

#3 Updated by Dan Bode over 2 years ago

  • Status changed from Investigating to Rejected

after some thought, I decided that this is not necessary. I will just re-implement my own type option.

#4 Updated by Kenn Hussey 10 months ago

  • Category set to cloud provisioner

Also available in: Atom PDF