Yeah. I've been working on OSCAR with the ORNL guys for a couple of years now. Usually I'm on site there, although I won't be until May this year.
Michael Edwards wrote: > I assume this is separate from the Google summer of code? > > On 3/11/07, Wesley Bland <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Last Summer I worked on the Command Line Interface at ORNL with Thomas and >> such. This year, I'm working on a Package Set Manager as a Senior Project. >> I just wanted to put out a rough description of what Thomas and I have been >> talking about so I can get the feedback from the group. This is also posted >> on the trac wiki at >> http://svn.oscar.openclustergroup.org/trac/oscar/wiki/SetManager >> >> This semester, I will be working on implementing a package set manager for >> OSCAR. This will be done in a few stages: >> >> I will need to create a system for describing the packages which will be >> installed and which sets they belong to. This will most likely be done in >> XML. The information in the XML file will include the package set name, the >> packages in the set, and descriptive information about the package including >> (but not limited to) package name and version. >> >> The packages will need to be in the "new" OSCAR package (opkg) format where >> there is an rpm (or set of rpms) which will be installed as well as a noarch >> rpm which holds all the the other things that currently are installed along >> with the rpm (tests, scripts, config.xml, docs). This rpm will be compiled by >> the OSCAR developers using the opkgc compiler. Hopefully I will be able to >> leverage the package information that will be stored in the noarch package to >> acquire dependency/conflict information. >> >> These dependencies will have to be resolved among the packages to be >> installed, then the images to be pushed to the nodes, then the actual remote >> machines themselves. This will be done hopefully with either depman or >> packman or, if these two are outdated, smartman. >> >> I will write the new code as a separate library which will have a CLI to >> interact with the user. If time allows, I will take a look at the GUI code to >> see if this can be a simple addition to the existing library. >> >> Feel free to send me feedback on the lists or by posting something in the >> wiki. Thanks in advance for any assistance you guys give me this semester >> and into the Summer. >> >> Wesley Bland >> [EMAIL PROTECTED] >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Oscar-devel mailing list >> Oscar-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oscar-devel >> > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Oscar-devel mailing list > Oscar-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list Oscar-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-devel
