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

[RFE] Alternative method to register client systems to the Satellite server using katello-ca-consumer package and not by Global Registration method.

XMLWordPrintable

      1. Proposed title of this feature request

      • [RFE] Alternative method to register client systems to the Satellite server using katello-ca-consumer package and not by Global Registration method.

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

      • As of now, the default way to register 1 or more client systems to the satellite server we have 3 ways i.e
        a) Global Registration Method
        b) Download and install the consumer RPM (i.e katello-ca-consumer-latest.noarch.rpm and then run Subscription Manager.
        c) Bootstrap Script. (Deprecated)

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

      The customer has a use case to use katello-ca-consumer directly.

      USER CASE:
      ------------------
      So this customer has 2 teams like the first team only manages the Satellite Web UI part and the second team manages the client systems but not with the satellite web ui or API.

      They use the old method of having the katello-ca-consumer pacakge installed which is a one-time setup for team 2 and they don't need satellite web UI or command-line to get this piece of information again and again. Since the package is the same for all the client systems.
      And then they register using the activation key.

      Now, since in the future Global Registration template will be the only option left with us and we will be removing the katello-ca-consumer package completely in Satellite 7, then they will face issues, in such cases.
      ------------------

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

      Either do not remove the katello-ca-consumer package or else there should be an alternative approach that works with the above use case.

      5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

      Anyone can we test it.

      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)?

      It's better if this is fixed before katello-ca-consumer package is removed.

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

      NA

      9. List any affected packages or components.

      katello-ca-consumer

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

      Yes

      11. Additional information:

            jira-bugzilla-migration RH Bugzilla Integration
            jira-bugzilla-migration RH Bugzilla Integration
            Shweta Singh Shweta Singh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: