Description of problem: As a user of Satellite 6, I would like the ability to have a 'lightweight' version of the Satellite capsule. I have remote sites with limited resources and little disk space. I'd like to deploy a capsule there with all the other features (DNS, DHCP, TFTP, Templates, etc) BUT proxy all content related items (RPMs, etc) back to the Satellite itself.
Moving 6.2 bugs out to sat-backlog.
Created redmine issue http://projects.theforeman.org/issues/17421 from this bug
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
For this idea of "lightweight", do you mean: a) lightweight storage (no RPMs/content stored on the Capsule) b) lightweight software (no Pulp/mongodb running on the Capsule) c) both
(In reply to Eric Helms from comment #11) > For this idea of "lightweight", do you mean: > > a) lightweight storage (no RPMs/content stored on the Capsule) > b) lightweight software (no Pulp/mongodb running on the Capsule) > c) both In a perfect world c) both (since that is one less service to manage, one less DB to backup, etc), but at a minimum a). Especially if a) is a new download policy in Pulp. Then the user can switch to/from any other policy (such as immediate or on-demand) to proxy-only.
*** Bug 1148370 has been marked as a duplicate of this bug. ***
The Pulp upstream bug status is at CLOSED - DUPLICATE. Updating the external tracker on this bug.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.