Could a time/date for the upgrade be selected so that it can happen unattended? So, at 3am on Saturday upgrade the system?
Also, if this is a distributed system can all systems be upgraded in a rolling fashion? Thanks, Mike > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sipx-dev- > [EMAIL PROTECTED] On Behalf Of Damian Krzeminski > Sent: Thursday, October 16, 2008 11:30 AM > To: [EMAIL PROTECTED] > Subject: [sipX-dev] supporting sipXecs upgrades from sipXconfig > > http://track.sipfoundry.org/browse/XCF-2817 > > Martin added a list of things to this issue - but before we jump deep > into > discussions of yum updates and repository structure I would like to > step > back and talk about the use cases. > > I think we want to support 2 stories here. > > "Minor version upgrade" - from 4.0.2 to 4.0.3 (but not to 4.2) > > Helen is a sipXconfig admin. She comes to work checks her e-mail. There > is > a new e-mail "sipXecs upgrade available". > > There is a link in the e-mail. Helen clicks on a link and it takes her > to > sipXconfig UI. At the top of the page there is a "new update available" > message with a link to an Update screen. She click on a link. > > There is a message on an update screen: > > "You are currently running sipXecs 4.0.2, there is a 4.0.3 version > available. Do you want to: > > - upgrade now > - upgrade later (selecting this keeps the reminder on all screens but > takes > admin back to Home screen.) > - skip this upgrade (selecting this makes reminder message disappear > until > the next update.)" > > > Helen decides to select "Upgrade Now". sipXconfig suggests that the > backup > should be performed. Helen skips the backup since there are nightly > backups > configured on this system. sipXconfig displays upgrading screen with a > throbber and a vague message that system is not available while it's > being > upgraded. What Helen does not know that sipXconfig actually stopped > itself > and the rest of the sipXecs processes and the system is now performing > an > upgrade script. Once the upgrade is completed the sipXecs is restarted > automatically and the upgrade page reconnects to the login screen. > After > Helen logs in she sees the confirmation message on the Home screen "You > are > now now running sipXecs 4.0.3. No updates available at the moment". > > > "Major version upgrade" - from 4.0 to 4.2 > > This is very similar to the previous story but sipXconfig does not bug > Helen that there is a new version available. > > Helen finds out about it from users list, from sipfoundry announcement, > call from a company that supports her sipXecs installation etc. (same > way > people find out about new Fedora relase). > Once she decides to upgrade the system, she goes to Upgrade page and > selects "Show available versions" link. > > That makes sipXconfig to check some (preconfigured) location for a new > repository data. Usually there will be just one version to upgrade to - > but > in some cases, if the system has not been upgraded for a while there > can be > 2 or 3 (ie. 4.2, 4.4 etc.) > Helen decided which version she wants to upgrade too (the latest is the > default). sipXconfig retrieves and installs new repository info and > proceeds with an upgrade as described in the previous story. > > > Comments, questions, suggestions? > D. > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
