Project

General

Profile

Actions

Feature #5790

closed

Default "Deploy on" value for host groups.

Added by Martin Hovmöller almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Host creation
Target version:
Difficulty:
Triaged:
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 11 (3 open8 closed)

Related to Foreman - Bug #11050: Host Groups do not allow to specify image-based buildsNew07/08/2015Actions
Related to Foreman - Bug #22424: Add compute resource into apipie doc for hostgroupClosedOndřej Pražák01/25/2018Actions
Related to Foreman - Bug #22543: Deploy on set via hostgroup does not work with compute profileNew02/09/2018Actions
Related to Foreman - Bug #22544: Deploy on field for hostgroup can't be set through API and hammerClosed02/09/2018Actions
Related to Foreman - Bug #22792: Trying to delete compute resource associated with hostgroup gives PG::ForeignKeyViolation: ERRORResolvedActions
Related to Foreman - Bug #24072: "Deploy on" hostgroup option doesn't work properly with network insterfaces and compute profilesClosedIvan Necas06/26/2018Actions
Related to Foreman - Bug #25799: Bare-metal host 'Deploy On' setting doesn't persistNewActions
Has duplicate Foreman - Feature #13538: Including the Compute Resource in the Hostgroup configurationDuplicateKoen Torfs02/03/2016Actions
Has duplicate Foreman - Feature #15318: Default of orchestration type should be configurableDuplicate06/07/2016Actions
Has duplicate Foreman - Feature #16832: add "Deploy On" compute resource value to either host group or compute profileDuplicate10/07/2016Actions
Has duplicate Foreman - Feature #23854: Assign Compute Resource to HostgroupDuplicate06/08/2018Actions
Actions #1

Updated by Dominic Cleal almost 10 years ago

  • Category changed from Web Interface to Host creation
Actions #2

Updated by Dominic Cleal over 8 years ago

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

Updated by Dominic Cleal almost 8 years ago

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

Updated by Dominic Cleal almost 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Koen Torfs
Actions #5

Updated by Dominic Cleal almost 8 years ago

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

Updated by Dominic Cleal over 7 years ago

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

Updated by Anonymous almost 7 years ago

Koen, what's the status here?

Actions #8

Updated by Koen Torfs almost 7 years 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 :)

Actions #9

Updated by The Foreman Bot over 6 years ago

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

Updated by Anonymous over 6 years ago

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

Updated by Marek Hulán about 6 years ago

  • translation missing: en.field_release set to 330
Actions #12

Updated by Anonymous about 6 years ago

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

Updated by Tomer Brisker about 6 years ago

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

Updated by Marek Hulán about 6 years ago

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

Updated by Marek Hulán about 6 years ago

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

Updated by Ivan Necas about 6 years ago

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

Updated by Ondřej Pražák almost 6 years ago

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

Updated by Ivan Necas almost 6 years ago

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

Updated by Tomer Brisker about 5 years ago

  • Related to Bug #25799: Bare-metal host 'Deploy On' setting doesn't persist added
Actions

Also available in: Atom PDF