JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for TB-SUPPORT Archives


TB-SUPPORT Archives

TB-SUPPORT Archives


TB-SUPPORT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TB-SUPPORT Home

TB-SUPPORT Home

TB-SUPPORT  January 2009

TB-SUPPORT January 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Glite Middleware Rollback proposal.

From:

Steve Fisher <[log in to unmask]>

Reply-To:

Testbed Support for GridPP member institutes <[log in to unmask]>

Date:

Thu, 29 Jan 2009 13:56:47 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (200 lines)

That would be a lot of effort to implement as it would require
releasing RPMs with higher version numbers just in case they were
needed. Also if there is a need to rollback it would normally not be
all RPMs that were involved.

I think it is better to treat each case individually. For those RPMs
that were generated via ETICS and where the internal ETICS package
mangement system its used it is very easy to produce RPMs with a
higher version number but based on an old CVS tag.

Steve

2009/1/29 Coles, J (Jeremy) <[log in to unmask]>:
> Hi Paul
>
> I would need to find out how the build system internally deals with
> release numbers.
>
> I guess in " When X.6 is released the production release points
> to X.6 and if there is a problem it is then re-pointed to X.6.1." The
> last part should be X.5.1 if I understand your proposal.
>
> Thanks for the suggestion. I'll add it to methods to consider - unless
> anyone counters!
>
> Cheers,
> Jeremy
>
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Paul Kyberd
> Sent: 29 January 2009 13:39
> To: [log in to unmask]
> Subject: Re: Glite Middleware Rollback proposal.
>
> I have a damn silly question. At the point at which a release is created
> is it possible to create an identical "roll back release".
> So X.5 is created and at the same time X.6.1 - the pointer to production
>
> release points to X.5. When X.6 is released the production release
> points
> to X.6 and if there is a problem it is then re-pointed to X.6.1.
> X.6 is clearly released with X.7.1 and so on.
>
> I have a feeling I must be missing something, and if this is a silly
> idea
> I apologise for wasting people's time
>
> Paul Kyberd
>
>
> -----Original Message-----
> From: Testbed Support for GridPP member institutes on behalf of Coles, J
> (Jeremy)
> Sent: Thu 1/29/2009 12:38
> To: [log in to unmask]
> Subject: Re: Glite Middleware Rollback proposal.
>
> Dear All
>
> Thank you for responses posted to TB-SUPPORT so far. As mentioned at our
> UKI ops meeting this morning, I have got extra information from Markus
> on the background to the proposal after putting a few questions back to
> him. I am posting this below and would be grateful if you could consider
> the content and post your suggestions if this alters what you have
> already suggested. Noting that Markus needs concrete proposals from
> sites on how things might be done, please keep your responses
> constructive so that the UK reaction I will compose (for Markus, Oliver
> and the GDB) is not just moaning (I wouldn't start from here is not
> going to help). I will make a point that the build systems could/should
> be improved first... but we need to work from where we are. How could
> something best be implemented bearing in mind the constraints on the
> build side?
>
> I'll compile the responses early next week, so responses by Monday would
> be appreciated.
>
> Thanks,
> Jeremy
>
>
> From Markus:
>
> " there are a some problems for EGEE to follow the common Linux
> distribution approach with rollback by re-tagging and rebuilding the
> older code base.
>
> There is no uniform way the gLite components manage their versions
>    a) Some use the "classic" approach via CVS
>    b) Some depend on the configuration management in the ETICS package
> manager
>
> There is no uniform way the information for the creating the RPM spec
> files is managed.
> This is critical, because to create from the old version an RPM with a
> higher version number this information has to be changed.
>
> While ETICS stores a lot of traces about what has been created how and
> this can be used to create a replica of the produced RPMs, it is
> technically difficult to create from this starting point an identical
> RPM with a newer version number. The two above mentioned extra degrees
> of freedom for gLite developers doesn't help here.
>
> As a result in most cases neither the integration nor the rollout team
> is technically in a position to  handle the "old code higher version"
> build without
> interaction with the developers. Which as a result creates significant
> delays, not only for the rollback release, but in addition for the work
> on the bug fixes.
> These delays can be substantial, because in several teams the release
> build with ETICS is done by the same person and that person's
> availability can't be guaranteed. In addition developers have been quite
> reluctant to invest in recreating old material while believing that the
> "real" fix is just
> 5 lines of code away.
>
> The third alternative approach to just stop the rollout and rush for the
> real fix has been demonstrated to not working. The VOMS experience where
> we had to iterate with the developers for 6+ months until we had a
> version that had no obvious bugs is a very good example. It has to be
> noted that during this period we had to ad extra manpower to test new
> VOMS releases as quickly as possible to make progress at all.
>
> In addition the goal of a rollback is to contain a situation until a
> proper fix is available. This means that the reaction time should be as
> low as possible.
> We certainly don't suggest to roll back for trivial reasons.
>
> With these constraints in mind, a strategy based on the already existing
> previous RPMs was tempting, but we are open to suggestions on how to do
> this properly, but please give us advice that is a bit more practical
> and concrete than "Do it the RedHat, Debian or Ubuntu"-way, I would
> appreciate suggestions that don't require to move the developers to a
> different build system.....
>
>
>     markus
>
>
> ps:
>  There is another problem  with higher versioned old RPMS.
>  It has the disadvantage in rollout that in most cases problems are
> spotted after less than 20% of the infrastructure has moved to the new
> (bad) version.
> If we could follow the standard Linux approach at the moment any real
> update happens to the repository  80% of the sites would roll forward to
> the same version at which they already run.  Especially when the
> additional change requires a rerun of YAIM this can create some problems
> when the site uses some modification of the standard setup."
>
>
>
>
>
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Peter Gronbech
> Sent: 26 January 2009 11:28
> To: [log in to unmask]
> Subject: Glite Middleware Rollback proposal.
>
> At the January GDB meeting Markus Schultz and Andreas Unterkircher
> outlined a new proposed method for handling emergency rollback of a
> release once a bug has been found.
>
> In particular on page 6 of Andreas talk they suggest having a production
> repository and a previous version repository for the rpms.
> In the event of a problem a link would be switched back to point at the
> previous release thus stopping any more downloads of a faulty release,
> but this does leave the institutes that have already upgraded with an
> awkward manual reversal procedure.
>
> My suggestion of just releasing an higher numbered rpm with the bug
> removed was not favoured.
>
> We would like to ask you your opinions of this scheme so a UK feedback
> response can be made.
>
> Thanks Pete
>
> GDB meeting http://indico.cern.ch/conferenceDisplay.py?confId=45461
>
> Andreas Unterkircher's talk
> http://indico.cern.ch/getFile.py/access?sessionId=5&resId=1&materialId=1
> &confId=45461
> --
> ----------------------------------------------------------------------
> Peter Gronbech  Senior Systems Manager and      Tel No. : 01865 273389
>              SouthGrid Technical Co-ordinator  Fax No. : 01865 273418
>
> Department of Particle Physics,
> University of Oxford,
> Keble Road, Oxford  OX1 3RH, UK  E-mail : [log in to unmask]
> ----------------------------------------------------------------------
> --
> Scanned by iCritical.
> --
> Scanned by iCritical.
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager