Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-39790

[SPIKE] Prepare for decision on feature enabling

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 6.19.0
    • None
    • Installation
    • None
    • sat-rocket
    • False
    • Satellite Rocket Sprint 9
    • None

      https://github.com/theforeman/foremanctl/pull/188 opened the discussion on enabling/disabling features. Feature enabling is when something is disabled by default in foremanctl, but the user can enable that feature. For example, a default deployment doesn't have DHCP integration but users can enable that.

      This spike is about figuring out how we present that to the user. The initial focus is mostly on enabling, but ideally the recommendation for a design doesn't make disabling impossible.

      When researching this, it's good to look at which kind of features a user can enable. If you don't consider enough features then you may miss the options.

      Some examples for today:

      • OpenShift Virtualization is a tech preview and can be enabled by the user (which is a Foreman plugin)
      • DHCP/DNS/Realm are all Foreman Proxy modules, each has its own set of providers
      • TFTP is a Foreman Proxy module without any providers

      Upstream we have more options because there we don't enable all compute resources by default. If we think about a vanilla Foreman and adding Katello to that, it would be similar to Foreman Proxy modules with providers. Each has its own options, some mandatory. All of that isn't required in this spike, but ideally we can think of a design that doesn't make it impossible to implement.

      The expected outcome is:

      • A list of possible features that you considered
      • A recommendation on how to implement the feature enabling

              egolov@redhat.com Evgeni Golov
              ekohlvan@redhat.com Ewoud Kohl van Wijngaarden
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: