[Pulp-list] Pulp init.d script

[Jeff Ortel]

On 07/25/2012 08:40 AM, Jay Dobies wrote:
> On 07/25/2012 09:35 AM, Chris St. Pierre wrote:
>> Might I suggest that there should be neither Pulp nor Katello init
>> scripts?  After all, those init scripts just call other init scripts,
>> which is confusing (witness OP) and can be difficult to manage.  Keep
>> it simple -- starting Apache starts Pulp, so we already have a Pulp
>> init script.  It's called "httpd" (and "mongod" and "qpidd").
>
> That's a possibility too. The intention was to simplify things for
> users; in theory it's easier to tell them to run one script (with pulp
> in the name) instead of three.
>
> But if telling people about the three feels better that might be the
> right approach. That script already has problems in systemd, so removing
> it entirely would make life easier than trying to find a way to replace it.
>
> Alternatively, the *-service script suggested earlier might be the
> compromise. It's outside of the systemd/initd infrastructure but still
> available to those who care about it.

I like this approach.  Having an init.d/systemd script/unit that just 
aggregates other /true/ services has always felt wrong and (as Jay 
mentioned) problematic.  Most users will configure httpd, mongod and 
qpidd to start automatically.  Also, when users need to bounce one of 
the services, it's usually to solve a particular issue that is related 
to the service being restarted.  Using pulp's current init.d script has 
the unwanted side effect of bouncing the other services unnecessarily.

Another suggestion would be to symlink init.d/pulpd -> init.d/httpd. 
Not sure it's necessary but does have a certain symmetry with the 
symlink we create for the agent init.d/goferd -> init.d/pulp-agent.  Not 
convinced this is a good idea but thought I'd throw it out there.

>
>> On Wed, Jul 25, 2012 at 9:11 AM, Jay Dobies <jason.dobies at redhat.com>
>> wrote:
>>> On 07/25/2012 05:36 AM, Miroslav Suchý wrote:
>>>>
>>>> I encountered one problem with Pulp init.d script:
>>>>
>>>> When we start or stop Katello using
>>>>    katello-service stop
>>>> then httpd is stopped twice (the same for starting).
>>>>
>>>> I believe that Pulp init.d script should not start or stop other
>>>> services.
>>>> It is valid scenario that I may want to stop just Pulp, but not Apache,
>>>> which should e.g. serve "Sorry we are in maintace" page.
>>>>
>>>> If you want to have script which start/stop all services, which Pulp
>>>> use, you can steal:
>>>>    /usr/bin/katello-service
>>>> from Katello (which we steal from Spacewalk).
>>>>
>>>> May I kindly ask you to edit Pulp init.d script to start just Pulp?
>>>
>>>
>>> The thing is, there is no Pulp outside of Apache. That script takes
>>> care of
>>> mongo, apache, and qpid. If you don't stop Apache, Pulp keeps running.
>>>
>>> I'm confused at your maintenance page example though. If the issue is
>>> that
>>> Apache is started/stopped by Katello as well, how is that need met by us
>>> removing Apache from that init.d script?
>>>
>>> I'm open to suggestions. We've talked about a *-service type script,
>>> but at
>>> the end of the day that's going to be the same thing where Apache is
>>> started/stopped/restarted to accomplish the Pulp notions of those
>>> operations.
>>>
>>> --
>>> Jay Dobies
>>> Freenode: jdob @ #pulp
>>> http://pulpproject.org | http://blog.pulpproject.org
>>>
>>>
>>> _______________________________________________
>>> Pulp-list mailing list
>>> Pulp-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
>>
>>
>
>