Project

General

Profile

Actions

Feature #3178

closed

add ability to apply a virtual hardware template at hostgroup level

Added by Greg Petras about 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Host creation
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I would like to be able to specify the following attributes in a "virtual hardware" profile:

- number of vCPUs
- RAM
- number of disks and their size
- number of interfaces and their network name

Ideally, in a child hostgroup, Foreman would allow the profile to be inherited from its parent unless it had it's own override profile specified.

This would significantly reduce complexity in our provisioning scripts, which currently require the user to pass in these parameters per host, even though they are the same across a hostgroup.


Related issues 8 (3 open5 closed)

Related to Foreman - Bug #3980: Compute profiles not rendering Openstack attributes correctlyClosedJoseph Magen01/09/2014Actions
Related to Foreman - Bug #4126: libvirt network selection doesn't work when editing compute profilesNew01/19/2014Actions
Related to Foreman - Bug #4159: Thin provisioning for VMware disks in compute profiles can't be savedClosedMartin Matuška01/22/2014Actions
Related to Foreman - Bug #4221: Unable to delete Compute Resource/Deassociate Compute ProfileClosedSam Kottler01/29/2014Actions
Related to Foreman - Bug #4235: EC2 compute profile loses Security Group setting.New02/03/2014Actions
Related to Foreman - Feature #4250: Expose compute profiles via APIClosedJoseph Magen02/04/2014Actions
Related to Foreman - Bug #4330: Can't remove network interface or volume from compute profileNew02/12/2014Actions
Related to Foreman - Bug #4375: Kickstart provisioning is on a loop when using compute profiles with ovirt Compute Resource.Closed02/18/2014Actions
Actions

Also available in: Atom PDF