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.
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.
- Status changed from New to Assigned
- Assignee set to Joseph Magen
- Target version set to 1.10.0
- Target version changed from 1.10.0 to 1.9.3
- Status changed from Assigned to Ready For Testing
- Target version changed from 1.9.3 to 1.9.2
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 2
- Related to Bug #3980: Compute profiles not rendering Openstack attributes correctly added
- Related to Bug #4126: libvirt network selection doesn't work when editing compute profiles added
- Related to Bug #4159: Thin provisioning for VMware disks in compute profiles can't be saved added
- Related to Bug #4221: Unable to delete Compute Resource/Deassociate Compute Profile added
- Related to Bug #4235: EC2 compute profile loses Security Group setting. added
- Related to Bug #4330: Can't remove network interface or volume from compute profile added
- Related to Bug #4375: Kickstart provisioning is on a loop when using compute profiles with ovirt Compute Resource. added
Also available in: Atom
PDF