Project

General

Profile

Feature #3178

add ability to apply a virtual hardware template at hostgroup level

Added by Greg Petras almost 6 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Joseph Magen
Category:
Host creation
Target version:
1.4.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
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

Related to Foreman - Bug #3980: Compute profiles not rendering Openstack attributes correctlyClosed2014-01-09
Related to Foreman - Bug #4126: libvirt network selection doesn't work when editing compute profilesNew2014-01-19
Related to Foreman - Bug #4159: Thin provisioning for VMware disks in compute profiles can't be savedClosed2014-01-22
Related to Foreman - Bug #4221: Unable to delete Compute Resource/Deassociate Compute ProfileClosed2014-01-29
Related to Foreman - Bug #4235: EC2 compute profile loses Security Group setting.New2014-02-03
Related to Foreman - Feature #4250: Expose compute profiles via APIClosed2014-02-04
Related to Foreman - Bug #4330: Can't remove network interface or volume from compute profileNew2014-02-12
Related to Foreman - Bug #4375: Kickstart provisioning is on a loop when using compute profiles with ovirt Compute Resource.Closed2014-02-18

Associated revisions

Revision c6e02bd3 (diff)
Added by Joseph Magen over 5 years ago

fixes #3178 - add feature for compute profiles for hostgroups and hosts

History

#1 Updated by Dominic Cleal almost 6 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

#2 Updated by Dmitri Dolguikh almost 6 years ago

  • Target version set to 1.10.0

#3 Updated by Dominic Cleal almost 6 years ago

  • Target version changed from 1.10.0 to 1.9.3

#4 Updated by Ohad Levy over 5 years ago

  • Status changed from Assigned to Ready For Testing

#5 Updated by Dmitri Dolguikh over 5 years ago

  • Target version changed from 1.9.3 to 1.9.2

#6 Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Dominic Cleal over 5 years ago

  • Legacy Backlogs Release (now unused) set to 2

#8 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #3980: Compute profiles not rendering Openstack attributes correctly added

#9 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #4126: libvirt network selection doesn't work when editing compute profiles added

#10 Updated by Ewoud Kohl van Wijngaarden over 5 years ago

  • Related to Bug #4159: Thin provisioning for VMware disks in compute profiles can't be saved added

#11 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #4221: Unable to delete Compute Resource/Deassociate Compute Profile added

#12 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #4235: EC2 compute profile loses Security Group setting. added

#13 Updated by Dominic Cleal over 5 years ago

  • Related to Feature #4250: Expose compute profiles via API added

#14 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #4330: Can't remove network interface or volume from compute profile added

#15 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #4375: Kickstart provisioning is on a loop when using compute profiles with ovirt Compute Resource. added

Also available in: Atom PDF