Bug #4337
open
- Status changed from New to Assigned
- Assignee set to Daniel Lobato Garcia
- Target version set to 1.9.1
- Target version changed from 1.9.1 to 1.9.0
It will easily get done after #4521 is closed, for the moment I'm focusing on that and waiting for a test EC2 account
- Related to Bug #4521: Openstack boot from volume added
- Target version deleted (
1.9.0)
- Category changed from Compute resources to Compute resources - EC2
- Related to Feature #3022: Set disk size of ec2 instance from "Virtual Machine" tab of UI added
- Related to Bug #9550: unable to provision vm in rackspace using the compute or memory flavor added
- Status changed from Assigned to New
Is this feature dead? Based on associated bugs/tickets it looks like fog might have introduced new capabilities to support more customization around boot volumes size/types. We just attempted to hook up 1.20 foreman to AWS and found this to be show stopping.
Sadly it seems so yes, it's been two years since I sent an empiric patch to raise default size here: https://projects.theforeman.org/issues/3022 and nothing has been done since.
I looked already a bit into integrating up to the creation form but ruby syntax is ways too "weird" and I don't think I'm going to make it...
Also available in: Atom
PDF