Project

General

Profile

Actions

Bug #4337

open

EC2 use block device mapping

Added by Daniel Lobato Garcia about 10 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

EC2 instances can have a block device mapping to EBS volumes, as per http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html
We should be able to design this block device mapping in Foreman and set ephemeral disks for the EC2 instances too.

Originally from: https://groups.google.com/d/msg/foreman-dev/TbXtZ5fmyrc/Gbf-WQcn3HsJ


Related issues 4 (3 open1 closed)

Related to Foreman - Bug #4521: Openstack boot from volumeClosedDaniel Lobato Garcia03/03/2014Actions
Related to Foreman - Feature #3022: Set disk size of ec2 instance from "Virtual Machine" tab of UINewActions
Related to Foreman - Feature #7072: More EC2 IntegrationNew08/13/2014Actions
Related to Foreman - Bug #9550: unable to provision vm in rackspace using the compute or memory flavorNew02/25/2015Actions
Actions #1

Updated by Dominic Cleal about 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Daniel Lobato Garcia
  • Target version set to 1.9.1
Actions #2

Updated by Daniel Lobato Garcia about 10 years ago

  • Target version changed from 1.9.1 to 1.9.0

Same feature in Openstack tracked here: http://projects.theforeman.org/issues/4521

Actions #3

Updated by Daniel Lobato Garcia about 10 years ago

It will easily get done after #4521 is closed, for the moment I'm focusing on that and waiting for a test EC2 account

Actions #4

Updated by Dominic Cleal about 10 years ago

  • Related to Bug #4521: Openstack boot from volume added
Actions #5

Updated by Anonymous about 10 years ago

  • Target version deleted (1.9.0)
Actions #6

Updated by Dominic Cleal over 9 years ago

  • Category changed from Compute resources to Compute resources - EC2
Actions #7

Updated by Dominic Cleal over 9 years ago

  • Related to Feature #3022: Set disk size of ec2 instance from "Virtual Machine" tab of UI added
Actions #8

Updated by Dominic Cleal over 9 years ago

Actions #9

Updated by Dominic Cleal about 9 years ago

  • Related to Bug #9550: unable to provision vm in rackspace using the compute or memory flavor added
Actions #10

Updated by Anonymous almost 7 years ago

  • Status changed from Assigned to New
Actions #11

Updated by Andrew Cooper over 4 years ago

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.

Actions #12

Updated by Adam Cécile over 4 years ago

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...

Actions

Also available in: Atom PDF