[Swift-commit] r3556 - in usertools/swift/swiftconfig: bin etc etc/sites/local etc/sites/local-pbs etc/sites/local-pbs-coasters etc/sites/pads-local-pbs etc/sites/pads-local-pbs-coasters etc/sites/pads-remote-pbs-coasters-ssh etc/sites/pads-remote-ssh etc/sites/ssh etc/sites/teraport-local-pbs etc/sites/teraport-local-pbs-coasters etc/sites/teraport-remote-pbs-coasters-ssh etc/sites/teraport-remote-ssh lib/perl

noreply at svn.ci.uchicago.edu noreply at svn.ci.uchicago.edu
Wed Aug 18 22:46:23 CDT 2010


Author: davidk
Date: 2010-08-18 22:46:23 -0500 (Wed, 18 Aug 2010)
New Revision: 3556

Added:
   usertools/swift/swiftconfig/etc/sites/local/swift.properties
Removed:
   usertools/swift/swiftconfig/etc/sites/local-pbs-coasters/tc.data
   usertools/swift/swiftconfig/etc/sites/local-pbs/tc.data
   usertools/swift/swiftconfig/etc/sites/local/tc.data
   usertools/swift/swiftconfig/etc/sites/pads-local-pbs-coasters/tc.data
   usertools/swift/swiftconfig/etc/sites/pads-local-pbs/tc.data
   usertools/swift/swiftconfig/etc/sites/pads-remote-pbs-coasters-ssh/tc.data
   usertools/swift/swiftconfig/etc/sites/pads-remote-ssh/tc.data
   usertools/swift/swiftconfig/etc/sites/ssh/tc.data
   usertools/swift/swiftconfig/etc/sites/teraport-local-pbs-coasters/tc.data
   usertools/swift/swiftconfig/etc/sites/teraport-local-pbs/tc.data
   usertools/swift/swiftconfig/etc/sites/teraport-remote-pbs-coasters-ssh/tc.data
   usertools/swift/swiftconfig/etc/sites/teraport-remote-ssh/tc.data
Modified:
   usertools/swift/swiftconfig/bin/swiftconfig
   usertools/swift/swiftconfig/bin/swiftrun
   usertools/swift/swiftconfig/etc/TODO
   usertools/swift/swiftconfig/etc/sites/local/sites.xml
   usertools/swift/swiftconfig/lib/perl/SwiftConfig.pm
Log:
App editing improvements
Handle swift.properties
Remove tc.data files from template directories


Modified: usertools/swift/swiftconfig/bin/swiftconfig
===================================================================
--- usertools/swift/swiftconfig/bin/swiftconfig	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/bin/swiftconfig	2010-08-19 03:46:23 UTC (rev 3556)
@@ -95,7 +95,7 @@
     );
     write_file( "$output_directory/sites.xml", $xml_out_ref );
 
-    update_site_applications($new_sitename);
+    update_site_applications($new_sitename, $option_default);
 
     # Handle SSH
     if ( $xml_ref->{execution}{provider} eq 'ssh' ) {
@@ -141,7 +141,7 @@
         SuppressEmpty => 1,
     );
     write_file( "$output_directory/sites.xml", $xml_out_ref );
-    update_site_applications($option_edit);
+    update_site_applications($option_edit, $option_default);
     
     # Add/modify/remove ssh entries as needed
     if ( $xml_ref->{execution}{provider} eq 'ssh' ) {
@@ -228,7 +228,7 @@
            }
            open(APPFILE, ">$dotswift_directory/apps/$application_set.apps")
                || die "Unable to create file $dotswift_directory/apps/$application_set.apps";
-           print "$application_set set created\n\n";
+           print "$application_set set created\n";
            close(APPFILE);
        }
        

Modified: usertools/swift/swiftconfig/bin/swiftrun
===================================================================
--- usertools/swift/swiftconfig/bin/swiftrun	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/bin/swiftrun	2010-08-19 03:46:23 UTC (rev 3556)
@@ -42,8 +42,10 @@
 my ($run_number) = $run_directories[-1] =~ m{(\d+)};
 $run_number++;
 my $run_directory = getcwd() . "/" . sprintf "run.%04s", $run_number;
+create_directory($run_directory);
 my @sites_xml;
-create_directory($run_directory);
+
+# Copy over needed files
 copy_file( "$option_script", "$run_directory" );
 
 # Sites.xml for 'all'
@@ -55,6 +57,11 @@
         if ( !-e "$all_site/sites.xml" ) {
             die "Unable to find sites.xml for $all_site\n";
         }
+        my $properties_file = "$dotswift_directory/sites/$all_site/swift.properties";
+        if( -e "$properties_file") {
+            copy_file( $properties_file, "$run_directory/swift.properties");
+        }
+
         open(CURRENT_SITE, "$all_site/sites.xml")
             || die "Unable to open $all_site/sites.xml";
         my @current_site_data = <CURRENT_SITE>;
@@ -106,7 +113,10 @@
         my @current_site_data = <CURRENT_SITE>;
         close(CURRENT_SITE);
         push(@sites_xml,  @current_site_data);
-        
+        my $properties_file = "$dotswift_directory/sites/$site/swift.properties";
+        if( -e "$properties_file") {
+            copy_file( $properties_file, "$run_directory");
+        }
         # Add applications
         my @all_apps;
         if(-e "$dotswift_directory/sites/$site/apps") {
@@ -167,10 +177,16 @@
     . "-sites.file $run_directory/sites.xml "
     . "-tc.file $run_directory/tc.data "
     . "$option_script ";
+if(-e "$run_directory/swift.properties") {
+    $system_command .= "-config $run_directory/swift.properties ";
+}
+else {
+    print "No such file $run_directory/swift.properties\n";
+}
 
 # Add unknown options
 foreach my $unknown_argument (@ARGV) {
-    $system_command = "$system_command $unknown_argument ";
+    $system_command .= "$unknown_argument ";
 }
 
 # Execute

Modified: usertools/swift/swiftconfig/etc/TODO
===================================================================
--- usertools/swift/swiftconfig/etc/TODO	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/TODO	2010-08-19 03:46:23 UTC (rev 3556)
@@ -4,4 +4,3 @@
 Have swiftrun be flexible enough to work for new users, as well as advanced users 
 Site aliases
 Ability to "undo" edits
-Replace $HOST in app templates with something else

Modified: usertools/swift/swiftconfig/etc/sites/local/sites.xml
===================================================================
--- usertools/swift/swiftconfig/etc/sites/local/sites.xml	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/local/sites.xml	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,6 +1,7 @@
 <pool handle="local">
   <execution provider="local" />
   <gridftp url="local://localhost" />
-  <profile key="jobThrottle" namespace="karajan">0</profile>
+  <profile namespace="karajan" key="initialScore">10000</profile>
+  <profile key="jobThrottle" namespace="karajan">.31</profile>
   <workdirectory>$HOME/swiftwork</workdirectory>
 </pool>

Added: usertools/swift/swiftconfig/etc/sites/local/swift.properties
===================================================================
--- usertools/swift/swiftconfig/etc/sites/local/swift.properties	                        (rev 0)
+++ usertools/swift/swiftconfig/etc/sites/local/swift.properties	2010-08-19 03:46:23 UTC (rev 3556)
@@ -0,0 +1,352 @@
+#sites.file=${swift.home}/etc/sites.xml
+#tc.file=${swift.home}/etc/tc.data
+
+#
+# The host name of the submit machine is used by GRAM as a callback
+# address to report the status of submitted jobs. In general, Swift
+# can automatically detect the host name of the local machine. 
+# However, if the machine host name is improperly configured or if
+# it does not represent a valid DNS entry, certain services (such as
+# GRAM) will not be able to send job status notifications back to 
+# the client. The value of this property can be an IP address.
+#
+# Format:
+#    hostname=string
+#
+
+
+#hostname=localhost
+
+#
+# A TCP port range can be specified to restrict the ports on which GRAM
+# callback services are started. This is likely needed if your submit
+# host is behind a firewall, in which case the firewall should be 
+# configured to allow incoming connections on ports in the range.
+#
+# Format:
+#     tcp.port.range=start,end
+#
+
+#tcp.port.range=50000,50100
+
+#
+# false	- means an error will be immediately reported and cause the
+# 		workflow to abort. At this time remote jobs that are already
+#		running will not be canceled
+# true	- means that Swift will try to do as much work as possible and 
+#		report all errors encountered at the end. However, "errors"
+#		here only applies to job execution errors. Certain errors
+#		that are related to the Swift implementation (should such 
+#		errors occur) will still be reported eagerly.
+#
+# Default: false
+#
+lazy.errors=false
+
+#
+# What algorithm to use for caching of remote files. LRU (as in what
+# files to purge) is the only implementation right now. One can set
+# a target size (in bytes) for a host by using the swift:storagesize 
+# profile for a host in sites.xml
+#
+# Default: LRU
+#
+caching.algorithm=LRU
+
+#
+# true       - generate a provenance graph in .dot format (Swift will
+#			 choose a random file name)
+# false      - do not generate a provenance graph 
+# <filename> - generate a provenange graph in the give file name
+#
+# Default: false
+#
+pgraph=false
+
+
+#
+# graph properties for the provenance graph (.dot specific) 
+#
+# Default: splines="compound", rankdir="TB"
+#
+pgraph.graph.options=splines="compound", rankdir="TB"
+
+
+#
+# node properties for the provenance graph (.dot specific) 
+#
+# Default: color="seagreen", style="filled"
+#
+pgraph.node.options=color="seagreen", style="filled"
+
+#
+# true	- clustering of small jobs is enabled. Clustering works in the 
+#       following way: If a job is clusterable (meaning that it has the
+#       GLOBUS::maxwalltime profile specified in tc.data and its value
+#       is less than the value of the "clustering.min.time" property) it will
+#       be put in a clustering queue. The queue is processed at intervals 
+#       specified by the "clustering.queue.delay" property. The processing
+#       of the clustering queue consists of selecting compatible jobs and
+#		grouping them in clusters whose max wall time does not exceed twice
+#       the value of the "clustering.min.time" property. Two or more jobs are 
+#       considered compatible if they share the same site and do not have
+#       conflicting profiles (e.g. different values for the same environment
+#       variable). 
+# false	- clustering of small jobs is disabled.
+#
+# Default: false
+#
+clustering.enabled=false
+
+
+#
+# <seconds>	- the intervals at which the clustering queue is processed
+#
+# Default: 4
+#
+clustering.queue.delay=4
+
+#
+# <seconds>	- the threshold time for clustering
+#
+# Default: 60
+#
+clustering.min.time=60
+
+#
+# Kickstart is a useful tool that can be used to gather various information
+# about a remote process. Before it can be used it must be installed on the
+# remote site and the corresponding entry be set in the sites file.
+# This option allows controlling of how Swift uses Kickstart. The following
+# values are possible:
+# false - do not use Kickstart
+# true  - use Kickstart. If a job is scheduled on a site that does not have
+#       Kickstart installed, that job will fail.
+# maybe - Use Kickstart if installed (i.e. the entry is present in the sites
+#       file) 
+#
+# Default: maybe
+#
+
+kickstart.enabled=maybe
+
+#
+# Indicates when Kickstart records should be fetched from the remote site:
+# true	- always transfer Kickstart records if Kickstart was used (see
+#		kickstart.enabled)
+# false	- only transfer Kickstart records if the job fails
+#
+# Default: false
+#
+
+kickstart.always.transfer=false
+
+#
+# Indicates when wrapper logs should be fetched from the remote site:
+# true	- always transfer wrapper logs
+# false	- only transfer wrapper logs if the job fails
+#
+# Default: false
+#
+
+wrapperlog.always.transfer=true
+
+###########################################################################
+#                          Throttling options                             #
+###########################################################################
+#
+# For the throttling parameters, valid values are either a positive integer
+# or "off" (without the quotes).
+#
+
+#
+# Limits the number of concurrent submissions for a workflow instance. This
+# throttle only limits the number of concurrent tasks (jobs) that are being
+# sent to sites, not the total number of concurrent jobs that can be run.
+# The submission stage in GRAM is one of the most CPU expensive stages (due
+# mostly to the mutual authentication and delegation). Having too many 
+# concurrent submissions can overload either or both the submit host CPU
+# and the remote host/head node causing degraded performance.     
+#
+# Default: 4
+#
+
+throttle.submit=4
+#throttle.submit=off
+
+#
+# Limits the number of concurrent submissions for any of the sites Swift will
+# try to send jobs to. In other words it guarantees that no more than the 
+# value of this throttle jobs sent to any site will be concurrently in a state
+# of being submitted.
+#
+# Default: 2
+#
+
+throttle.host.submit=2
+#throttle.host.submit=off
+
+#
+# The Swift scheduler has the ability to limit the number of concurrent jobs
+# allowed on a site based on the performance history of that site. Each site
+# is assigned a score (initially 1), which can increase or decrease based
+# on whether the site yields successful or faulty job runs. The score for a
+# site can take values in the (0.1, 100) interval. The number of allowed jobs
+# is calculated using the following formula: 
+# 	2 + score*throttle.score.job.factor
+# This means a site will always be allowed at least two concurrent jobs and
+# at most 2 + 100*throttle.score.job.factor. With a default of 4 this means
+# at least 2 jobs and at most 402.
+#
+# Default: 4
+#
+
+throttle.score.job.factor=0.2
+#throttle.score.job.factor=off
+
+
+#
+# Limits the total number of concurrent file transfers that can happen at any
+# given time. File transfers consume bandwidth. Too many concurrent transfers
+# can cause the network to be overloaded preventing various other signalling
+# traffic from flowing properly.
+#
+# Default: 4
+#
+
+throttle.transfers=4
+#throttle.transfers=off
+
+# Limits the total number of concurrent file operations that can happen at any
+# given time. File operations (like transfers) require an exclusive connection
+# to a site. These connections can be expensive to establish. A large number
+# of concurrent file operations may cause Swift to attempt to establish many 
+# such expensive connections to various sites. Limiting the number of concurrent
+# file operations causes Swift to use a small number of cached connections and
+# achieve better overall performance. 
+# 
+# Default: 8
+#
+
+throttle.file.operations=8
+#throttle.file.operations=off
+
+# Indicates whether the working directory on the remote site should be
+# left intact even when the workflow completes successfully. This can be
+# used to inspect the site working directory for debugging purposes.
+#
+# Default: false
+#
+
+sitedir.keep=true
+
+# number of time a job will be retried if it fails (giving a maximum of 
+# 1 + execution.retries attempts at execution)
+#
+
+execution.retries=1
+
+
+# Enables/disables replication. Replication is used to deal with jobs sitting
+# in batch queues for abnormally large amounts of time. If replication is enabled
+# and certain conditions are met, Swift creates and submits replicas of jobs, and
+# allows multiple instances of a job to compete.
+#
+
+replication.enabled=false
+
+# If replication is enabled, this value specifies the minimum time, in seconds,
+# a job needs to be queued in a batch queue in order to be considered for 
+# replication
+#
+
+replication.min.queue.time=60
+
+# The maximum number of replicas that Swift should attempt.
+
+replication.limit=3
+
+#
+# WARNING: This option is deprecated. Please use the hostname option.
+#
+# The IP address of the submit machine is used by GRAM as a callback
+# address to report the status of submitted jobs. In general, Swift
+# can automatically detect the IP address of the local machine. 
+# However, if the machine has more than one network interface, Swift
+# will pick the first one, which may not be the right choice. It is
+# recommended that this property is set properly before attempting to
+# run jobs through GRAM.
+#
+# Format:
+#    ip.address=x.y.z.w
+#
+
+#ip.address=127.0.0.1
+
+
+# Controls how Swift will communicate the result code of running user programs
+# from workers to the submit side. In files mode, a file
+# indicating success or failure will be created on the site shared filesystem.
+# In provider mode, the execution provider job status will
+# be used. Notably, GRAM2 does not return job statuses correctly, and so
+# provider mode will not work with GRAM2. With other
+# providers, it can be used to reduce the amount of filesystem access compared
+# to files mode.
+#
+# status.mode=files
+
+# Controls how swift will supply parameters to the remote wrapper script.
+# 'args' mode will pass parameters on the command line
+# 'files' mode will pass parameters through an additional input file
+#
+# valid values: args, files
+# Default: files
+#
+# wrapper.parameter.mode=args
+
+# Determines if Swift remote wrappers will be executed by specifying an
+# absolute path, or a path relative to the job initial working directory
+#
+# valid values: absolute, relative
+# wrapper.invocation.mode=absolute
+
+#
+# Limits the number of concurrent iterations that each foreach statement
+# can have at one time. This conserves memory for swift programs that 
+# have large numbers of iterations (which would otherwise all be executed
+# in parallel).
+#
+# Default: 1024
+#
+
+foreach.max.threads=16384
+
+# controls whether the log file will contain provenance information
+# enabling this will increase the size of log files, sometimes
+# significantly.
+
+provenance.log=false
+
+# Controls whether file staging is done by swift or by the execution 
+# provider. If set to false, the standard swift staging mechanism is
+# used. If set to true, swift does not stage files. Instead, the 
+# execution provider is instructed to stage files in and out.
+# 
+# Provider staging is experimental.
+#
+# When enabled, and when coasters are used as an execution provider,
+# a staging mechanism can be selected for each site
+# using the swift:stagingMethod site profile in sites.xml. The
+# following is a list of accepted mechanisms:
+#
+# * file:  Staging is done from a filesystem accessible to the 
+#          coaster service (typically running on the head node) 
+# * proxy: Staging is done from a filesystem accessible to the
+#          client machine that swift is running on, and is proxied
+#          through the coaster service
+# * sfs:   (short for "shared filesystem") Staging is done by
+#          copying files to and from a filesystem accessible
+#          by the compute node (such as an NFS or GPFS mount).   
+ 
+
+use.provider.staging=false

Deleted: usertools/swift/swiftconfig/etc/sites/local/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/local/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/local/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,8 +0,0 @@
-# sitename  transformation  path   INSTALLED  platform  profiles
-local	echo	/bin/echo	INSTALLED	INTEL32::LINUX	null
-local	cat	/bin/cat	INSTALLED	INTEL32::LINUX	null
-local	ls	/bin/ls	INSTALLED	INTEL32::LINUX	null
-local	grep	/bin/grep	INSTALLED	INTEL32::LINUX	null
-local	sort	/bin/sort	INSTALLED	INTEL32::LINUX	null
-local	paste	/bin/paste	INSTALLED	INTEL32::LINUX	null
-local	tr	/usr/bin/tr	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/local-pbs/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/local-pbs/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/local-pbs/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-local-pbs 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-local-pbs  	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-local-pbs  	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-local-pbs  	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-local-pbs  	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-local-pbs  	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/local-pbs-coasters/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/local-pbs-coasters/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/local-pbs-coasters/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-local-pbs-coasters 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-local-pbs-coasters 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-local-pbs-coasters 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-local-pbs-coasters 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-local-pbs-coasters 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-local-pbs-coasters 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/pads-local-pbs/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/pads-local-pbs/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/pads-local-pbs/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-pads-local-pbs 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-pads-local-pbs 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/pads-local-pbs-coasters/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/pads-local-pbs-coasters/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/pads-local-pbs-coasters/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-pads-local-pbs-coasters 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs-coasters 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs-coasters 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-pads-local-pbs-coasters 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs-coasters 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-pads-local-pbs-coasters 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/pads-remote-pbs-coasters-ssh/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/pads-remote-pbs-coasters-ssh/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/pads-remote-pbs-coasters-ssh/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-pads-remote-pbs-coasters 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-pads-remote-pbs-coasters 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-pads-remote-pbs-coasters 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-pads-remote-pbs-coasters 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-pads-remote-pbs-coasters 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-pads-remote-pbs-coasters 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/pads-remote-ssh/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/pads-remote-ssh/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/pads-remote-ssh/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-pads-remote-ssh 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-pads-remote-ssh 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-pads-remote-ssh 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-pads-remote-ssh 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-pads-remote-ssh 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-pads-remote-ssh 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/ssh/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/ssh/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/ssh/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-ssh	echo	/bin/echo	INSTALLED	INTEL32::LINUX	null
-ssh	cat	/bin/cat	INSTALLED	INTEL32::LINUX	null
-ssh	ls	/bin/ls	INSTALLED	INTEL32::LINUX	null
-ssh	grep	/bin/grep	INSTALLED	INTEL32::LINUX	null
-ssh	sort	/bin/sort	INSTALLED	INTEL32::LINUX	null
-ssh	paste	/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/teraport-local-pbs/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/teraport-local-pbs/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/teraport-local-pbs/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-teraport-local-pbs	echo	/bin/echo	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs	cat	/bin/cat	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs	ls	/bin/ls	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs	grep	/bin/grep	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs	sort	/bin/sort	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs	paste	/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/teraport-local-pbs-coasters/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/teraport-local-pbs-coasters/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/teraport-local-pbs-coasters/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-teraport-local-pbs-coasters 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs-coasters 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs-coasters 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs-coasters 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs-coasters 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-teraport-local-pbs-coasters 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/teraport-remote-pbs-coasters-ssh/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/teraport-remote-pbs-coasters-ssh/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/teraport-remote-pbs-coasters-ssh/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-localhost 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-localhost 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-localhost 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-localhost 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-localhost 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-localhost 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Deleted: usertools/swift/swiftconfig/etc/sites/teraport-remote-ssh/tc.data
===================================================================
--- usertools/swift/swiftconfig/etc/sites/teraport-remote-ssh/tc.data	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/etc/sites/teraport-remote-ssh/tc.data	2010-08-19 03:46:23 UTC (rev 3556)
@@ -1,17 +0,0 @@
-#This is the transformation catalog.
-#
-#It comes pre-configured with a number of simple transformations with
-#paths that are likely to work on a linux box. However, on some systems,
-#the paths to these executables will be different (for example, sometimes
-#some of these programs are found in /usr/bin rather than in /bin)
-#
-#NOTE WELL: fields in this file must be separated by tabs, not spaces; and
-#there must be no trailing whitespace at the end of each line.
-#
-# sitename  transformation  path   INSTALLED  platform  profiles
-teraport-remote-ssh 	echo 		/bin/echo	INSTALLED	INTEL32::LINUX	null
-teraport-remote-ssh 	cat 		/bin/cat	INSTALLED	INTEL32::LINUX	null
-teraport-remote-ssh 	ls 		/bin/ls		INSTALLED	INTEL32::LINUX	null
-teraport-remote-ssh 	grep 		/bin/grep	INSTALLED	INTEL32::LINUX	null
-teraport-remote-ssh 	sort 		/bin/sort	INSTALLED	INTEL32::LINUX	null
-teraport-remote-ssh 	paste 		/bin/paste	INSTALLED	INTEL32::LINUX	null

Modified: usertools/swift/swiftconfig/lib/perl/SwiftConfig.pm
===================================================================
--- usertools/swift/swiftconfig/lib/perl/SwiftConfig.pm	2010-08-18 04:43:10 UTC (rev 3555)
+++ usertools/swift/swiftconfig/lib/perl/SwiftConfig.pm	2010-08-19 03:46:23 UTC (rev 3556)
@@ -34,7 +34,7 @@
 sub create_directory {
     my $directory = $_[0];
     if ( !-d "$directory" ) {
-        mkdir "$directory", 0700
+        mkdir "$directory"
             or die "Unable to create directory $directory\n";
     }
 }
@@ -88,8 +88,8 @@
                 $error_message = $error_message . $allowable . ' ';
             }
             print 'Invalid value selected. Please select from: '
-                . "$error_message\n";
-            $entry_value = get_entry( $entry_description, $entry_value,
+                . "$error_message\n\n";
+            $entry_value = get_entry( $entry_description, $entry_value, 0, 
                 @allowable_values, );
         }
     }
@@ -549,7 +549,7 @@
 
 # Associate application sets with a configuration
 sub update_site_applications {
-    my ($site) = @_;
+    my ($site, $use_defaults) = @_;
     my $apps = '';
     
     if(! -d "$ENV{'HOME'}/.swift/sites/$site") {
@@ -573,24 +573,34 @@
        }       
     }
     
-    my @all_available_appsets = glob("$ENV{'HOME'}/.swift/apps/*.apps");
-    print "Available application sets: ";
-    foreach(@all_available_appsets) {
-        $_ = strip_directory($_);
-        ($_, my $junk) = split('\.');
-        print "$_ ";
+    if(!$use_defaults) {
+        my @all_available_appsets = glob("$ENV{'HOME'}/.swift/apps/*.apps");
+        print "Available application sets: ";
+        foreach(@all_available_appsets) {
+           $_ = strip_directory($_);
+           ($_, my $junk) = split('\.');
+            print "$_ ";
+        }
+        print "\n";
     }
-    print "\n";
     
-    $apps = get_entry("Select application sets for $site", $apps, 0);    
+    if(!$apps) {
+        $apps = "linux";
+    }
+    
+    $apps = get_entry("Select application sets for $site", $apps, $use_defaults);    
     my @all_list = split(/ /, $apps);
     open(APPFILE, ">$ENV{'HOME'}/.swift/sites/$site/apps")
         || die "Unable to open $ENV{'HOME'}/.swift/sites/$site/apps for writing!\n";
+        
     foreach(@all_list) {
         print APPFILE "$_\n";
     }
     close(APPFILE);
-    print "Successfully saved application sets for $site\n\n";
+    
+    if(!$use_defaults) {
+        print "Successfully saved application sets for $site\n\n";
+    }
 }
 
 # Import existing XML file into swiftconfig style format
@@ -723,4 +733,31 @@
     
 strip_directory($fullpath)
     Given a string like "/foo/blah/file.txt", return "file.txt"
+    
+add_application($filename)
+    Add an application to an application set
+    
+remove_application($filename)
+    Remove an application from an application set
+    
+list_applications($filename)
+    List all applications contained in $filename
+
+edit_application($filename)
+    Edit an application in $filename
+
+initialize_swiftconfig()
+    Set up swiftconig directory structure and copy required files
+
+update_site_applications($site, $use_defaults)
+    Associate application sets with a configuration
+    $site is the name of the configuration
+    If $use_defaults > 0, it will save without prompting
+    
+import_xml($filename)
+    Import existing site configuration(s) from $filename
+    
+import_tc($filename)
+    Import an application set from an existing tc.data file
+    
 =cut




More information about the Swift-commit mailing list