Bug 1871180

1. Proposed title of this feature request
   [RFE] Provide Satellite/Ansible feature parity to current Puppet integration

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

   At the moment all Ansible modules are stored in /etc/ansible/roles or
   /usr/share/ansible/roles.

   There is no separation between Organizations and no release management 
   available for Ansible modules as it is with the current Puppet integration.

4. Why does the customer need this? (List the business requirements here)
   Customers need to replace Puppet configuration management with Ansible in 7.x

5. How would the customer like to achieve this? (List the functional requirements here)
   Customers require that:
   - Ansible modules used in Satellite needs to be separate for each organization
   - Ansible modules should be uploaded to an Ansible repository within a Product
   - More than one Ansible module version must be possible in a repository
   - Ansible modules need to be able to be added to Content Views
   - Content Views with Ansible modules should be synced to Capsules
   - Only Ansible modules within an assigned CV (Hostgroup or individual client) 
     must be available for execution on a client

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
   See current implementation of Puppet in Satellite 6

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
   There is already an Ansible plugin for Pulp3

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
   With the release of Satellite 7.0 or with the removal of the Puppet integration

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

10. List any affected packages or components.
    pulp3

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