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:
I am noticing a trend toward deprecation in favor of ansible. There is nothing wrong with ansible and ansible has its strengths and can address things on a one time basis easily, however, it must be reissued/reasserted to maintain a configuration. Ansible also has the luxury of having wide adoption of python coders, and support on Windows.
Puppet which uses an agent on the clients with a polling cycle that will refresh the config, and ensure a configuration without being pushed, and it will reassert its config on boot. Ansible has no idea when a machine boots as it runs no agent on the box.
I am suggesting at this point that we stop trying to get rid of puppet on the Satellite product, and if anything we upgrade puppet to version 7 (on Satellite 6.11 minimally).
If we don't stop, I will be needing to split off puppet onto a standalone server, which I'm already doing for some things, and I was doing my own standalone puppet before Satellite 6 came into being. I found it nice to be able to pull my puppet yaml into the Satellite product with no serious issues.
I've never used puppet the way foreman and Red Hat has envisioned. I like the idea of ansible for its ability to do hierarchical style management, but I'm doubting I will ever use ansible the way Red Hat/IBM envisions.
I'm suggesting both will play a role for some time to come, and the more Red Hat tries to deprecate it, the more some will simply look for their own solution that may not involve Red Hat.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: