Proposed F19 Feature: PreUpgrade Assistant

[Jaroslav Reznik]

= Features/PreUpgrade Assistant =
https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant

Feature owner(s): Nils Philippsen <nils(a)redhat.com&gt;, Phil Knirsch 
<pknirsch(a)redhat.com&gt;

The PreUgrade assistant is a tool to help people upgrade from one release to 
another and be sure to track important manual configuration changes they 
performed. 

== Detailed description ==
The idea behind the The PreUpgrade assistant came from the notion that even 
during the rather short release cycles in Fedora occasionally there are 
changes that are incompatible between releases and which are either hard or 
nearly impossible to cover during a standard package upgrade. Examples would 
be major version upgrades of applications or services that change configuration 
file syntax or on-disk date format changes.

The assistant works by analyzing the source system and will generate a report 
which will offer information and configuration files for typically changed 
settings and services. It offers a plugin architecture where component or 
functional area owners can contribute and write their on plugins in python 
that can generate additional information for the report.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

[Rahul Sundaram]

Hi


On Tue, Jan 29, 2013 at 11:37 AM, Jaroslav Reznik <jreznik(a)redhat.com&gt;wrote:

>  = Features/PreUpgrade Assistant =
>  https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant
>
>  Feature owner(s): Nils Philippsen <nils(a)redhat.com&gt;, Phil Knirsch
>  <pknirsch(a)redhat.com&gt;
>
>  The PreUgrade assistant is a tool to help people upgrade from one release
>  to
>  another and be sure to track important manual configuration changes they
>  performed.
>  

Don't confuse users unnecessarily.  Call this fedup-assistant or something
else entirely.

Rahul

[Jóhann B. Guðmundsson]

On 01/29/2013 04:37 PM, Jaroslav Reznik wrote:
>  = Features/PreUpgrade Assistant =
>  https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant
>
>  Feature owner(s): Nils Philippsen <nils(a)redhat.com&gt;, Phil Knirsch
>  <pknirsch(a)redhat.com&gt;
>
>  The PreUgrade assistant is a tool to help people upgrade from one release to
>  another and be sure to track important manual configuration changes they
>  performed.
>
>  == Detailed description ==
>  The idea behind the The PreUpgrade assistant came from the notion that even
>  during the rather short release cycles in Fedora occasionally there are
>  changes that are incompatible between releases and which are either hard or
>  nearly impossible to cover during a standard package upgrade. Examples would
>  be major version upgrades of applications or services that change configuration
>  file syntax or on-disk date format changes.
>
>  The assistant works by analyzing the source system and will generate a report
>  which will offer information and configuration files for typically changed
>  settings and services. It offers a plugin architecture where component or
>  functional area owners can contribute and write their on plugins in python
>  that can generate additional information for the report.
>  _______________________________________________ 
An tool that presents the release notes to the enduser is it not simpler 
to just ship it as an pdf or something?

JBG

[Phil Knirsch]

On 01/29/2013 05:57 PM, Rahul Sundaram wrote:
>  Hi
>
>
>  On Tue, Jan 29, 2013 at 11:37 AM, Jaroslav Reznik <jreznik(a)redhat.com
>  <mailto:[e-mail]>> wrote:
>
>      = Features/PreUpgrade Assistant =
>      https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant
>
>      Feature owner(s): Nils Philippsen <nils(a)redhat.com
>      <mailto:[e-mail]>>, Phil Knirsch
>      <pknirsch(a)redhat.com <mailto:[e-mail]>>
>
>      The PreUgrade assistant is a tool to help people upgrade from one
>      release to
>      another and be sure to track important manual configuration changes they
>      performed.
>
>
>
>  Don't confuse users unnecessarily.  Call this fedup-assistant or
>  something else entirely.
>
>  Rahul
>
>  
Yep, thats actually what we have in mind, just need to discuss and 
coordinate that with Will Woods and the anaconda team. Just wanted to 
make sure folks know about this planed "extension" of fedup.

Thanks & regards, Phil

-- 
Philipp Knirsch              | Tel.:  [phone]
Manager Core Services        | Fax.:  [phone]
Red Hat GmbH                 | Email: Phil Knirsch <pknirsch(a)redhat.com&gt;
Wankelstrasse 5              | Web:   http://www.redhat.com/
D-70563 Stuttgart, Germany

[Ryan Lerch]

On 01/29/2013 01:05 PM, Phil Knirsch wrote:
>  On 01/29/2013 05:57 PM, Rahul Sundaram wrote:
> > Hi
> >
> >
> > On Tue, Jan 29, 2013 at 11:37 AM, Jaroslav Reznik <jreznik(a)redhat.com
> > <mailto:[e-mail]>> wrote:
> >
> >     = Features/PreUpgrade Assistant =
> >     https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant
> >
> >     Feature owner(s): Nils Philippsen <nils(a)redhat.com
> >     <mailto:[e-mail]>>, Phil Knirsch
> >     <pknirsch(a)redhat.com <mailto:[e-mail]>>
> >
> >     The PreUgrade assistant is a tool to help people upgrade from one
> >     release to
> >     another and be sure to track important manual configuration 
> > changes they
> >     performed.
> >
> >
> >
> > Don't confuse users unnecessarily.  Call this fedup-assistant or
> > something else entirely.
> >
> > Rahul
> >
> >
>
>  Yep, thats actually what we have in mind, just need to discuss and 
>  coordinate that with Will Woods and the anaconda team. Just wanted to 
>  make sure folks know about this planed "extension" of fedup.
>
>  Thanks & regards, Phil
>  
It appears that some work has already been done on this by wwoods in the 
fedup repo. I have been helping him out a bit with the UI.

https://github.com/wgwoods/fedup

There is a prototype GUI in there that steps the user though process of 
preparing for the upgrade.
Presently the GUI allows the user to choose where to install from 
(Online Repos, Optical Media or USB Media), Shows them the release 
notes, etc.

It is mostly fairly similar in concept to the old preupgrade GUI.

cheers,
ryanlerch

[Kevin Fenzi]

Additionally, what about adding 'postupgrade' hooks or assistance? 

Ie, after a fedup upgrade you could run and note to users packages
which are orphaned and could be removed, etc

kevin