There are several nice user stories that could be implemented if 1) the system sent its redhat.repo file to candlepin (kind of like system facts are sent), and 2) if candlepin could in turn change settings and send it back down.
Example stories...
As a SAM user, I would like to know which repos are enabled on a system. As a SAM user, I would like to enable a repo on a system. As a SAM user, I would like to inspect the redhat.repo file on a system. As a SAM user, I would like to add 'excludes' and other redhat.repo options for a system.
On 09/19/2012 10:29 AM, Tom McKay wrote:
There are several nice user stories that could be implemented if 1) the system sent its redhat.repo file to candlepin (kind of like system facts are sent), and 2) if candlepin could in turn change settings and send it back down.
Example stories...
As a SAM user, I would like to know which repos are enabled on a system. As a SAM user, I would like to enable a repo on a system. As a SAM user, I would like to inspect the redhat.repo file on a system. As a SAM user, I would like to add 'excludes' and other redhat.repo options for a system.
The main question I would have, especially around katello, is how much of this does/should pulp do vs candlepin.
-- bk
candlepin@lists.fedorahosted.org