Feature #3178
closed
add ability to apply a virtual hardware template at hostgroup level
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.
Updated by Dominic Cleal about 10 years ago
- Status changed from New to Assigned
- Assignee set to Joseph Magen
You may want to follow and join in with this discussion on foreman-dev, where Joseph's looking at just this problem.
https://groups.google.com/forum/#!topic/foreman-dev/M9_mGo1lGl8
Updated by Dominic Cleal almost 10 years ago
- Target version changed from 1.10.0 to 1.9.3
Updated by Ohad Levy almost 10 years ago
- Status changed from Assigned to Ready For Testing
Updated by Anonymous almost 10 years ago
- Target version changed from 1.9.3 to 1.9.2
Updated by Anonymous almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset c6e02bd3cf59da85d3e97b0a7b2c221003eb494c.
Updated by Dominic Cleal almost 10 years ago
- translation missing: en.field_release set to 2
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #3980: Compute profiles not rendering Openstack attributes correctly added
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #4126: libvirt network selection doesn't work when editing compute profiles added
Updated by Ewoud Kohl van Wijngaarden almost 10 years ago
- Related to Bug #4159: Thin provisioning for VMware disks in compute profiles can't be saved added
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #4221: Unable to delete Compute Resource/Deassociate Compute Profile added
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #4235: EC2 compute profile loses Security Group setting. added
Updated by Dominic Cleal almost 10 years ago
- Related to Feature #4250: Expose compute profiles via API added
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #4330: Can't remove network interface or volume from compute profile added
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #4375: Kickstart provisioning is on a loop when using compute profiles with ovirt Compute Resource. added