<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Great, thanks, Sarah.<div><br></div><div>How about using etc/sites (which exists) for the templates. No sub directories for now (I think we can move all the current subdirs to OLD/ )<br><br></div><div>- Mike</div><div><br></div><div><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;">i can do this most quickly in python if that's ok with others...david, could you work on gathering the (working) templates from the testing suite into a directory under etc/ (and commmit to svn) where i can pull them from?<br>
<br><div class="gmail_quote">On Fri, Feb 11, 2011 at 8:49 AM, Michael Wilde <span dir="ltr"><<a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Sarah, David,<br>
<br>
While there has been no response on the email list on this, Justin tells me that he's OK with it. He wont be able to work on it due to other priorities, though.<br>
<br>
Can you both collaborate to implement it? Its very similar to what you did with swiftconfig, David.<br>
<br>
Lets first resolve: should it be in shell, python, or perl? (I favor these in the order listed)<br>
<br>
I think we need this asap. Can the two of you work together to make it happen?<br>
<br>
Lets use this email thread and the wiki page to work out the details, on swift-devel.<br>
<br>
The main steps are:<br>
<br>
- create the initial command<br>
- create and test a library of templates<br>
(drawing the templates from the test suite?)<br>
- create the doc page content (wiki) for end users:<br>
<div> <a href="http://www.ci.uchicago.edu/wiki/bin/view/SWFT/GenSites" target="_blank">http://www.ci.uchicago.edu/wiki/bin/view/SWFT/GenSites</a><br>
</div> -- should describe the command(s) and conventions<br>
-- should describe the templates, perhaps with comments in each template<br>
-- gensites -T # lists all template<br>
-- gensites -h # gives basic help<br>
-- gensites -h template # gives the help for specific template(s)<br>
- add any support for genapps? (gentc.sh)<br>
<br>
Do you want to do a voice call or txt chat to get this going, or should we do it all in email?<br>
<br>
- Mike<br>
<div><div></div><div><br>
<br>
----- Original Message -----<br>
> Based on discussions in the last 2 weekly meetings, I want to propose<br>
> this for 0.92, based on Justin's page<br>
> <a href="http://www.ci.uchicago.edu/wiki/bin/view/SWFT/CoastersCookbook" target="_blank">http://www.ci.uchicago.edu/wiki/bin/view/SWFT/CoastersCookbook</a> under<br>
> "Script snippets".<br>
><br>
> Im proposing here a few name changes, specific file location<br>
> conventions, but basically staying in the spirit of Justin's scripts.<br>
><br>
> gensites.sh -> etc/gensites<br>
> settings.sh -> merged into a local swift.properties file<br>
><br>
> The swift command "sites" will generate a sites.xml file in the<br>
> current directory based on the users "site settings" (obtained from<br>
> swift.properties) and one or more template files that are provided in<br>
> the Swift release and which can be augmented with the user's own<br>
> template collection(s).<br>
><br>
> User selects a site template from $SWIFT/etc/sites<br>
><br>
> gensites templates >sites.xml<br>
><br>
> gensites -p sites.properties templates >sites.xml<br>
><br>
> gensites -L template.dir templates >sites.xml<br>
><br>
> The user typically runs gensites only once per run directory<br>
><br>
> Templates are searched for in the following locations:<br>
><br>
> - current directory<br>
> - etc/sites in the Swift directory<br>
> - $HOME/.swift/sites in the user's home directory<br>
> - any -L directories specified on the gensites command line<br>
><br>
> The user's sites-related properties are obtained from:<br>
><br>
> - sites.properties in the current directory<br>
> - the -p file specified on the gensites command line<br>
> - $HOME/.swift/sites.properties<br>
> - $HOME/.swift/swift.properties lines with starting with #site<br>
><br>
> Obviously the fine details of this need to be nailed down; there's<br>
> some room for discussion for how simple and/or flexible to make this.<br>
> As long as the search and editing rules are clearly stated, I think<br>
> users will be well served and happy.<br>
><br>
> Each template should have comments describing its use, nature, and<br>
> user-changeable settings and defaults.<br>
><br>
> The command should flag required parameters that were not specified in<br>
> the user's settings. The generated sites.xml file could contain<br>
> comments stating where the options and templates came from.<br>
><br>
> Im putting this text in:<br>
><br>
> <a href="http://www.ci.uchicago.edu/wiki/bin/view/SWFT/GenSites" target="_blank">http://www.ci.uchicago.edu/wiki/bin/view/SWFT/GenSites</a><br>
><br>
> and we can document specific site file templates in:<br>
><br>
> <a href="http://www.ci.uchicago.edu/wiki/bin/view/SWFT/SiteFiles" target="_blank">http://www.ci.uchicago.edu/wiki/bin/view/SWFT/SiteFiles</a><br>
><br>
> - Mike<br>
><br>
><br>
> --<br>
> Michael Wilde<br>
> Computation Institute, University of Chicago<br>
> Mathematics and Computer Science Division<br>
> Argonne National Laboratory<br>
><br>
> _______________________________________________<br>
> Swift-devel mailing list<br>
> <a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a><br>
> <a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel" target="_blank">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a><br>
<br>
--<br>
Michael Wilde<br>
Computation Institute, University of Chicago<br>
Mathematics and Computer Science Division<br>
Argonne National Laboratory<br>
<br>
</div></div></blockquote></div><br>
</blockquote><br><span><br><br>-- <br><span name="x"></span>Michael Wilde<br>Computation Institute, University of Chicago<br>Mathematics and Computer Science Division<br>Argonne National Laboratory<br><span name="x"></span><br></span></div></div></body></html>