[katello-devel] katello-upgrade restarting services

[Jason Rist]

On 07/25/2012 07:22 AM, Jordan OMara wrote:
> On 25/07/12 14:19 +0200, Lukas Zapletal wrote:
>> On Tue, Jul 24, 2012 at 09:48:21AM -0400, Eric Sammons wrote:
>> In the original request/bug there was no mention of interactivity. At
>> least I did not see it. I am totally fine with a script that would
>> report required services should be down, just like Justin said.
>>
>> I just don't like the idea of script shutting down any services. If you
>> ever did production upgrade of anything, you know that the sysadmin want
>> to have everything under his control. Specifically he wants to minimize
>> the outage time frame if possible.
>>
>> If there is an interactivity, that is another story. You can always say
>> No if you don't feel while we provide seamless experience for those who
>> want upgrade fast. Together with --assume-yes / -y options this would
>> give you what you want.
>>
>> My personal opinion would be to stop if services are still up printing
>> some info about what to do to successfully continue without any
>> interactivity. But that is my opinion, I can live with yes/no questions.
>>
>
> I think, lzap, you would be OK with this behavior
>
> katello-upgrade (no arguments)
> ------------------------------
> Upgrade stopped! Please stop the following services before continuing:
> katello
> tomcat6
> postgresql
>
> katello-upgrade --auto-stop
> -----------------------------
> The following services are being stopped for the upgrade process:
> katello
> tomcat6
> postgresql
>
> Everyone else like that? It provides an automatic option if you want
> it but defaults to a more expected behavior for sysadmins
>
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel

+1 again

-- 
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist