Re: Short info about today's IRC meeting (2021-05-19)

If we plan to do it in Ansible why not do it in RPM?  If it's policy holding us back why not recommend a change to the policy before we go down the path of requiring Ansible on top of RPM.  Packages are one of the biggest benefits to application deployment.   My proposal is that there are two RPMs for each service daemon.  One to enable and start the service and another to open the firewall.  I have built many of these for our own deployments.  The "{service}-on" package would enable/start the service where the "{service}-on-firewall" package would open the firewall.  Most are simple wrapper RPMs that only need requires and post sections.   Having packages provide the correctly running service eliminates the need for yet another layer/tool on top of RPM. $ rpm -qa | grep -- -on-rabbitmq-server-on-0.08-1.el7.xxx.noarchmariadb-server-on-0.06-1.el7.xxx.noarchhttpd-on-0.23-1.el7.xxx.noarchmemcached-on-0.04-1.el7.xxx.noarchpostgis-on-0.08-1.el7.xxx.noarchpostgresql-server-on-0.11-1.el7.xxx.noarch Michael R. Davis