Feature Overview

Extend the functionalities of level of connectivity to cover additional use cases

• Set the feature level as a pre-registration step
• Change the feature level of a connected systems, without re-registration
• Recognize where the system is connected/connecting to and allow the level of connectivity supported for that scenario

Goals

• Further simplify the user experience around client tools by making rhc a more complete tool.
• Avoid scenarios where users re-register their system, causing potential duplication of host records and loss of historical information in HCC.
• Encourage customer to try the Analytics and Remote-Management levels by making it easy to change after the registration. 

Requirements

• As a user, I can change the level of connectivity of a system that is already registered, without having the un-register and re-register the system.
• As a user, I can easily change the level of connectivity of a system after it's been registered so that I can try additional features (increase the level) or easily reduce the amount of data being collected (decrease the level).
• As a user, I expect the cli to achieve a change of connectivity level only if it's currently supported by the current connection move
  • While support for Satelite is not in scope for this feature (See ), 

Note: For a system already registered, there is no plan to support changing its server.
i.e.: if a system is registered to console.dot and wants to be registered to a Satellite, a un-registration would have to be done first, and then a reconfigure + registration will be needed. 

Acceptance Criteria: 

• MVP requirements are verified
• QE test coverage expanded to include the new feature expectations 
• Relevant documentations ( HCC Or RHEL) are updated to match the improved experiences.