Hey Jeff, Thanks for doing the switchover. I'm forwarding this mail to the
appropriate folks at ETSU and will probably add a thankyou block to the
docs or something like that.
I going to cut one more beta for 4.2 and do a little testing and then
switch over to 5.0 stuff.
-- John
On Thu, 6 Oct 2005, Jeff Squyres wrote:
Anyone watching the commits yesterday may have noticed that DongInn converted
all the config.xml files on his database development branch to a slightly
different format. This is the result of work at ORNL to make a "better" XML
specification for our config.xml files -- the format is stricter and more
defined than the current set of config.xml files (I'm afraid that I don't
remember the names of the people at ORNL who helped with this -- John Mugler
can cite the appropriate credits here). It allows us to "verify" a
config.xml file before attempting to read it in an parse it.
The new format is roughly the same, but you'll notice three things
immediately:
- the header at the top is different
- the XML tag names are longer
- the filter specifications are slightly different
John Mugler can provide a much better description of exactly what changed and
why. The short version is that we'll be changing the OSCAR code base to
validate a config.xml before attempting to parse it and read it into the
database. If the file does not validate properly, we'll skip the entire
package (thanks for playing!).
For example, check out what happened to LAM's config.xml:
http://svn.oscar.openclustergroup.org/websvn/filedetails.php?
repname=OSCAR&path=%2Fbranches%2Foscar-db-
devel3%2Fpackages%2Flam%2Fconfig.xml&rev=0&sc=0
As part of the the ORNL/IU meeting a month or two ago, John and I spent an
hour and wrote a perl scripty-foo to convert the current config.xml's to the
new, stricter format. DongInn ran that on all the config.xml's in his branch
yesterday, and is working on updating the code to parse in this new format.
It should be done soon.
I don't think that John committed all his notes / the verification code in (I
remember writing the conversion script based on a file that strictly
specified the format for the OSCAR config.xml files, but I can't find that
now). Hopefully, we'll get that soon.
We anticipate bringing this stuff over to the trunk once 4.2 stabilizes and
we start working on 5.0 (i.e., Real Soon Now).
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
