Project

General

Profile

Feature #5790

Default "Deploy on" value for host groups.

Added by Martin Hovmöller over 4 years ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Category:
Host creation
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

It would be great if it was possible to set the default value for "Deploy on" for host groups, to avoid having to choose that from the drop down every time a machine is provisioned.


Related issues

Related to Foreman - Bug #11050: Host Groups do not allow to specify image-based buildsNew2015-07-08
Related to Foreman - Bug #22424: Add compute resource into apipie doc for hostgroupClosed2018-01-25
Related to Foreman - Bug #22543: Deploy on set via hostgroup does not work with compute profileNew2018-02-09
Related to Foreman - Bug #22544: Deploy on field for hostgroup can't be set through API and hammerClosed2018-02-09
Related to Foreman - Bug #22792: Trying to delete compute resource associated with hostgroup gives PG::ForeignKeyViolation: ERRORNew2018-03-06
Related to Foreman - Bug #24072: "Deploy on" hostgroup option doesn't work properly with network insterfaces and compute profilesClosed2018-06-26
Has duplicate Foreman - Feature #13538: Including the Compute Resource in the Hostgroup configurationDuplicate2016-02-03
Has duplicate Foreman - Feature #15318: Default of orchestration type should be configurableDuplicate2016-06-07
Has duplicate Foreman - Feature #16832: add "Deploy On" compute resource value to either host group or compute profileDuplicate2016-10-07
Has duplicate Foreman - Feature #23854: Assign Compute Resource to HostgroupDuplicate2018-06-08

Associated revisions

Revision d5d2d63f (diff)
Added by Ondřej Pražák 10 months ago

Fixes #5790 - Add compute resource to hostgroup (#4593)

History

#1 Updated by Dominic Cleal over 4 years ago

  • Category changed from Web Interface to Host creation

#2 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #11050: Host Groups do not allow to specify image-based builds added

#3 Updated by Dominic Cleal over 2 years ago

  • Has duplicate Feature #13538: Including the Compute Resource in the Hostgroup configuration added

#4 Updated by Dominic Cleal over 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Koen Torfs

#5 Updated by Dominic Cleal over 2 years ago

  • Has duplicate Feature #15318: Default of orchestration type should be configurable added

#6 Updated by Dominic Cleal about 2 years ago

  • Has duplicate Feature #16832: add "Deploy On" compute resource value to either host group or compute profile added

#7 Updated by Michael Moll over 1 year ago

Koen, what's the status here?

#8 Updated by Koen Torfs over 1 year ago

Hey Michael, it's certainly still on my to do. I hoped I could close this feature request last foreman construction day in Belgium (Feb 2017). I was prepared to work on this... 1 detail I however forgot, the code which was ready to be continued from the year before was based on a 1.12 dev branch while at the time of the construction day the dev branch was versions ahead and the code from before didn't fit in anymore (too much had already changed). The only part which still needed to be looked at was the frontend javascript so I initially thought it was as good as finished :(

So I first need to review all I have and then try to remake it in the current dev branch. (fyi, tbrisker helped me with the initial code in 2016)
The whole foreman code in itself is still quite unfamiliar terrain for me, nevertheless I am interesting in solving it (even though im not really a developer)

My priorities at work however limit me from working on this further for the time being. In 2016 I was playing with Foreman in a sandbox environment and it was there all these ideas for enhancements originated in case we would decide to start using it here. Nowadays the decision has been made to actually use foreman to replace a custom made provisioning tool which was developed in-house to exactly match the customer. Replacing this combined with transitioning from Puppet Enterprise to OpenSource Puppet takes a lot of time. My management first wants to have provisioning moved from the old tool to foreman for the 1500 servers or so we have here.

As soon as the basics are working, I plan to continue on the enhancements like this feature request.

In short: this is not forgotten :)

#9 Updated by The Foreman Bot over 1 year ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4593 added

#10 Updated by Michael Moll about 1 year ago

  • Assignee changed from Koen Torfs to Ondřej Pražák

#11 Updated by Marek Hulán 10 months ago

  • Legacy Backlogs Release (now unused) set to 330

#12 Updated by Anonymous 10 months ago

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

#13 Updated by Tomer Brisker 9 months ago

  • Related to Bug #22424: Add compute resource into apipie doc for hostgroup added

#14 Updated by Marek Hulán 8 months ago

  • Related to Bug #22543: Deploy on set via hostgroup does not work with compute profile added

#15 Updated by Marek Hulán 8 months ago

  • Related to Bug #22544: Deploy on field for hostgroup can't be set through API and hammer added

#16 Updated by Ivan Necas 8 months ago

  • Related to Bug #22792: Trying to delete compute resource associated with hostgroup gives PG::ForeignKeyViolation: ERROR added

#17 Updated by Ondřej Pražák 5 months ago

  • Has duplicate Feature #23854: Assign Compute Resource to Hostgroup added

#18 Updated by Ivan Necas 4 months ago

  • Related to Bug #24072: "Deploy on" hostgroup option doesn't work properly with network insterfaces and compute profiles added

Also available in: Atom PDF