1. Proposed title of this feature request

Allow option to deploy hosts from Satellite with GOFERLESS configuration from Satellite 6


2. What is the nature and description of the request?

The redhat_register snippet need to have additional codes included so that customer can mention a parameter called "goferless" with value "true" or "false", have have their systems build with goferless or gofer-based packages installed.


3. Why does the customer need this? (List the business requirements here)

Currently the redhat_register snippet is configured in a way that It will always install katello-agent when activation key is selected in the hostgroup or kt_activation_keys parameter is being used during host build anyway.

Since we highly recommend to use goferless infrastructure, There are customer requirements present to have an option to perform goferless build as well where katello-agent won't be installed but katello-host-tools will be installed.

4. How would the customer like to achieve this? (List the functional requirements here)

Adding a host or hostgroup parameter named "goferless" with value "true" or "false".

It's an easy implementation with a small code modification inside "redhat_register.erb".

~~~
  <%
    atomic = @host.operatingsystem.respond_to?(:atomic) ? @host.operatingsystem.atomic? : host_param_true?('atomic')

    if host_param('kt_activation_keys') 
        if host_param_true?('goferless')
          subscription_manager_certpkg_url = subscription_manager_configuration_url(@host)
          subscription_manager_atomic_url = subscription_manager_configuration_url(@host, false)
          subscription_manager_org = @host.rhsm_organization_label
          activation_key = host_param('kt_activation_keys')
          redhat_install_agent = false
          redhat_install_host_tools = true
          redhat_install_host_tracer_tools = true
        else 
          subscription_manager_certpkg_url = subscription_manager_configuration_url(@host)
          subscription_manager_atomic_url = subscription_manager_configuration_url(@host, false)
          subscription_manager_org = @host.rhsm_organization_label
          activation_key = host_param('kt_activation_keys')
          redhat_install_agent = true
          redhat_install_host_tools = true
          redhat_install_host_tracer_tools = false
        end
    else
      subscription_manager_certpkg_url = host_param('subscription_manager_certpkg_url')
      subscription_manager_atomic_url = host_param('subscription_manager_atomic_url')
      subscription_manager_org = host_param('subscription_manager_org')
      activation_key = host_param('activation_key')
      redhat_install_agent = host_param_true?('redhat_install_agent')
      redhat_install_host_tools = host_param_true?('redhat_install_host_tools')
      redhat_install_host_tracer_tools = host_param_true?('redhat_install_host_tracer_tools')
    end
  %>
~~~

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- Build a Satellite.
- Configire the satellite to be able to perform PXEBased deployments.
- Confiugred a hostgroup to be able to use during host deployments and add "goferless" paremeter with value set to "true".
- Deploy a host using the same hostgroup and observe which packages are getting installed i.e. katello-agent or katello-host-tools or both.

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.


7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

Latest minor release of satellite 6.7 or upcoming release Satellite 6.8 or as soon as possible.


8. Is the sales team involved in this request and do they have any additional input?
No.


9. List any affected packages or components.
- foreman
- /usr/share/foreman/app/views/unattended/provisioning_templates/snippet/redhat_register.erb


10. Would the customer be able to assist in testing this functionality if implemented?
Yes.


11. Additional information:

* Currently customers either need to re-configure the redhat_register snippet as mentioned above at point 4. This is highly recommended.

* Or else workaround could be,

~~
** If using hostgroup for host deployments,

--> Don't select any activation keys in the "Activation Keys" tab of HostGroup

--> Add following parameters in the "Paremeters" tab of the Hostgroup as exactly mentioned
    NAME                                              VALUE
    -------------------                               -----
    subscription_manager                              true
    activation_key                                    mykey
    subscription_manager_org                          My_Organization
    subscription_manager_certpkg_url                  http://<%= @host.content_source.name %>/pub/katello-ca-consumer-latest.noarch.rpm
    redhat_install_agent                              false
    redhat_install_host_tools                         true
    redhat_install_host_tracer_tools                  true

-->  Build the host using that hostgroup.
~~