Project

General

Profile

Bug #4734

Provisioning templates should be seeded for every organization

Added by Ivan Necas over 8 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Hosts
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

In previous version, the provisioning templates were marked to be shared across organizations, for simplicity reasons.

We probably want to keep orgs separated as possible, but we should prepare
independent set of provisioning templates then for provisioning of synced repos
to work out of the box


Related issues

Has duplicate Katello - Bug #5618: Provisioning templates should be set for all locations in FortelloDuplicate2014-05-07

Associated revisions

Revision fe33ad93 (diff)
Added by Stephen Benjamin almost 8 years ago

fixes #4734 - make katello templates available in all taxonomies

This change uses a new feature in foreman to mark templates as defaults
supplied by a third-party. We mark our templates as such, as well as
some Foreman templates we require.

The end result is that (a) these templates are made available in all
orgs and locations at creation, and (b) the templates can't be deleted
or modified, so we are free to update them at will. Users may clone a
template into their own org to customize it.

Revision ed0f057a
Added by Stephen Benjamin almost 8 years ago

Merge pull request #4450 from stbenjam/4734

fixes #4734 - make katello templates available in all taxonomies

History

#1 Updated by Mike McCune over 8 years ago

  • Triaged set to Yes

#2 Updated by Mike McCune over 8 years ago

  • Triaged deleted (Yes)

#3 Updated by Mike McCune over 8 years ago

  • Assignee set to Ivan Necas
  • Triaged set to No

#4 Updated by Mike McCune over 8 years ago

  • Triaged changed from No to Yes

#5 Updated by Justin Sherrill about 8 years ago

I would argue that we should make our templates Read-only, and then add all the readonly templates to every org on creation. That way there is a single base template that all orgs share (that can't be edited), and every org can copy a template for their own use.

Thoughts?

#6 Updated by Stephen Benjamin about 8 years ago

That does have the advantage of making upgrades easier. We can update the templates without worrying a user has edited them. I don't see a Clone button at first glance, we'll probably need to add that.

#7 Updated by Justin Sherrill about 8 years ago

Yeah, there is an open RFE in foreman to support that: http://projects.theforeman.org/issues/1646 We could add that feature as part of this.

#8 Updated by Stephen Benjamin almost 8 years ago

  • Bugzilla link set to 1116082

#9 Updated by Stephen Benjamin almost 8 years ago

I submitted a PR to enable cloning in #1646. We also need to do #3103.

Do we really need to seed the template in each org? It'd be better if all read-only templates without taxonomy were available everywhere, should be possible with just a tweak to with_taxonomy_scope in Foreman. What do you think?

#10 Updated by Justin Sherrill almost 8 years ago

  • Assignee changed from Ivan Necas to Justin Sherrill
  • Legacy Backlogs Release (now unused) set to 13
  • Difficulty set to medium

#11 Updated by Eric Helms almost 8 years ago

  • Target version set to 49

#12 Updated by Stephen Benjamin almost 8 years ago

  • Has duplicate Bug #5618: Provisioning templates should be set for all locations in Fortello added

#13 Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4450 added

#14 Updated by Eric Helms almost 8 years ago

  • Target version changed from 49 to 54

#15 Updated by Anonymous almost 8 years ago

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

Also available in: Atom PDF