Allow setting a priority for remotes #316
Description
Is your feature request related to a problem? Please describe.
I have the following scenario:
The Pulp instance should be configured to cache both Registry 1 and Registry 2.
The Pulp instance should prioritize the direct pull from Registry 1 rather than the pull through Registry 2, because Registry 2 is on cloud and there are associated costs to traffic.
The architecture of the scenario cannot be modified, hence the need of setting the priority among remotes.
Describe the solution you'd like
When creating/modifying a remote, there should be an option to set the priority of the remote.
When asking the Pulp instance for a package that is not in a repository, it should search the package through the available remotes by ordering them by priority, stopping at the first repository with the package that has the highest priority.
Describe alternatives you've considered
Modifying the scenario is not allowed, so there are no alternatives.