Overview

Satellite customers who wish to use the Subscription Service (aka Subscription Watch) at console.redhat.com object to using it as they are concerned about data security and thus want to ship only the bare minimum data required for subscription reporting. 

Background and Strategic Fit

Customers, particularly those in the Hybrid Committed Spend program have difficulty in reporting. Red Hat would like to make it easy for these customers to do such. As such, we would like to remove any blockers to adopting the hosted subscription services. 

In research conducted by the Hybrid Cloud Subscription Experience team, we have identified that many customers who aren't using our hosted subscription services would if we minimized the data collected. 

Additionally, with Satellite 6.16 being the first release that supports Simple Content Access as its only operating mode, customers will become increasingly dependent on the hosted counting tools, so removing blockers to their usage is an imperative. 

Goals

1. Who benefits from this feature, and how?

All Satellite users, particularly those in the HCS program. 

1. What is the difference between today's current state and a world with this feature?

Currently, the `rh_cloud` plugin provides some controls to allow a user to redact data (such as hostnames, ipv4 addresses, and package profiles). This is insufficient for data sensitive customers, as the list is exclusionary (select what you don't want to send) versus inclusionary (select what you do want to send). 

At the completion of this feature, the ideal state will allow the `rh_cloud` plugin to have two selectable options:

Minimal - The minimal set of facts required for systems to be counted in Swatch. `rhsm-conduit` has established this set (https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/swatch-system-conduit/src/main/java/org/candlepin/subscriptions/conduit/InventoryController.java#L82) and I would generally expect this fact payload to be the same within Satellite, though this should be reviewed. 

Optional - This set of facts would include the facts (like RPM payload, ipv4/ipv6 addresses, etc) needed for our analytics platform (Insights) to deliver value-added services (like vulnerability reporting or compliance reporting). The current "line-item veto" that we give the customer to redact hostnames, ipv4, and package profiles can be either removed in entirety or be allowed, but only in this option (not the minimal). 

Open ended questions - Completed

Mockup request sent to Maria - Finished

QE things to test:

• End to end tests minimal data collection with regular hosts
• End to end tests minimal data collection with a hypervisor
• Investigate test coverage for changes in the UI
• Negative test to make sure it works as expected if we toggle the settings on from the settings page

[vagrant@ip-10-0-168-90 foreman]$ cat 98ddd709-5014-4ac8-8470-59237e2da677.json | jq
{
  "report_slice_id": "98ddd709-5014-4ac8-8470-59237e2da677",
  "hosts": [
    {
      "bios_uuid": "203F234F-58C7-4237-8DDF-A17A2838A66C",
      "bios_vendor": "SeaBIOS",
      "bios_version": "1.16.1-1.el9",
      "cpu_socket(s)": "1"
    },
    {
      "bios_uuid": "B3C7F8DB-47B6-4F30-9AF4-6A5485EF2FCC",
      "bios_vendor": "SeaBIOS",
      "bios_version": "1.16.1-1.el9",
      "cpu_socket(s)": "6"
    }
  ]
} 

If a host is a hypervisor:

hypervisor::type
hypervisor::version