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.
1. Proposed title of this feature request :
Need a way to install and manage Capsule from Satellite itself.
2. Who is the customer behind the request?
Account name/no: ******
TAM customer: No
SRM customer: No
Strategic: No
3. What is the nature and description of the request?
Request for feature where Capsule installation can be initiated from Satellite and later on Capsule configuration would be managed by Satellite too. Managing NTP, DNS, DHCP etc services of Capsule from Satellite would be great feature.
It would be a vast improvement if Capsules can be built by the SAT6 server itself and the OS of the capsule still get its puppet directives from the Satellite server itself.
This might be accomplished by possibly a second agent that maybe has a separate/alternate config directory OR the ability for Capsules to have a unique directory for their puppet config and a unique port they use to talk to the hosts under them that is separate from what the Sat6 server uses to communicate with and manage the Capsules server.
4. Why does the customer need this? (List the business requirements here)
In case customer needs multiple Capsules, need 10+ Capsules that is a lot of servers/VMs to have not managed needing manual work/changes. This gets worse if you add in the possible inclusion of cloud services like aws, rackspace, etc. Satellite needs to be able to
manage/build infrastrucure like RHEV servers as well as Capsules.
5. How would the customer like to achieve this? (List the functional requirements here)
Installing and managing Capsule from Satellite itself, so no manual work on Capsule system.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Confirm new functionality allows to initiate installation of Capsule from Satellite and later allows to manage, maintain configuration files from Satellite.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No.
9. Is the sales team involved in this request and do they have any additional input?
No.
10. List any affected packages or components.
Unknown.
11. Would the customer be able to assist in testing this functionality if implemented? Already working on it.
Yes.
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 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.