Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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.