Hide Forgot
Description of problem: Scenario: Deployment in a closed network environment where only select systems have external access (e.g lab environment, cluster environment). Consumer systems will not necessarily be able to reach out to talk to the pulp server to register. In this instance it would be beneficial for the pulp-cds server to have a defined allotment of consumers that it can register and communicate with. It would then pass this consumer information back to the server during sync operations. Version-Release number of selected component (if applicable): pulp-cds-1.0.0-7.el6.noarch How reproducible: Always Steps to Reproduce: 1. Deploy pulp outside lab 2. Deploy pulp-cds inside lab. lab machines have no external network access 3. Consumer registration fails Actual results: 1. Consumer confidence plummets 2. Political unrest begins 3. Economic collapse ensues as spending ceases, banks fail, and admins are forced to horde hot pockets and beer. Expected results: 1. Consumers successfully register with the pulp-cds 2. Free universal hot pocket coverage mandated for all admins 3. Microwave clinics for the underprivileged. Additional info:
+1, but we don't care how many consumers register to each CDS instance. Just want the proxy magic. And hot pockets.
The "node" feature in current stable facilitates this scenario, because the local node is a full pulp server to which you register the local consumers. Please open a new request if there are additional things you need from the node feature.