|
Hi Dave, The only thing I would add, is that the install team has talked a little bit about externalizing some of the "knowledge" that is currently hard coded into some of the scripts. Things like ports, rpm dependencies etc, and it may make sense to use a common repository file for all of this. If we do so, we may have to go to an yaml or xml format so that we might be able to convey more information in a standard way - anyway, I think this proposal is a great start, and we can just expand as needed.. Lars On 8/15/2014 12:11 PM, Birdsall, Dave
wrote:
Hi Trafodion folk, Recently we've encountered the following situation:Some folks have downloaded the 0.8.3 versions of Trafodion together with the 0.8.3 versions of the installer and have run into certain installer bugs. The bugs have been fixed in newer versions of the installer but those versions today can't always run with the 0.8.3 versions of Trafodion core. So, users who try 0.8.3 still run into the bugs, and installer developers answer the same questions as before. We could back-fit fixes into the 0.8.3 installer, but we've come up with a better idea. We'll describe that here: We will add a new file, "installInfo.txt" somewhere within the Trafodion core directory tree (the precise location is TBD; the install team will make a proposal). The purpose of this file is to tell install what features to expect in this version of core. For example, recently a change to core was checked in to turn on TLOG by default. The installer required a corresponding change. By noting this feature in this file, the installer can figure out whether TLOG should be turned on by default or not, and so will work with both newer and older versions of core. A new entry will be required in this file whenever a change goes into core that requires a corresponding change in the installer. So, in the future, when a core developer asks an install developer to make a corresponding change, the install developer will ask what the identifier is for this change in the InstallInfo.txt file. The format of "installInfo.txt" will be simple. A line beginning with '#' is a comment and will be ignored. A line consisting of a single identifier (that is, some string of letters and numbers, starting with a letter) will be considered a feature name. The installer will raise a warning when it finds a feature name that it doesn't know about. That will clue you in that you are using an old installer that doesn't understand a new core. If the file is missing, this is interpreted by the installer as the lack of any new features. That will allow new installers to work with 0.8.3 core, for example. We are aware of only two changes so far in 0.8.4 that required corresponding installer changes. So, the initial version of the InstallInfo.txt file will contain just two identifiers, one for each. Please add new identifiers to the end of the file. We imagine that if the file gets big, we'll "age out" the older identifiers from the beginning of the file. You'll be seeing this change show up in core shortly; one of us will follow up with another e-mail when that happens. By the way, if you have a better idea of how to solve this problem, feel free to respond. Thanks, Dave Birdsall, Marvin Anderson, Steve Varnau, Yves Cadieux --
Lars Fredriksen Hewlett-Packard Company lars.fredrik...@hp.com Office +1 630-968-9904 Cell +1 630-215-7672 PC +1 512-319-3265 HP-BIS |
-- Mailing list: https://launchpad.net/~trafodion-development Post to : trafodion-development@lists.launchpad.net Unsubscribe : https://launchpad.net/~trafodion-development More help : https://help.launchpad.net/ListHelp
