Permalink
Browse files

comments in payload_template

  • Loading branch information...
ianedwardthomas committed Mar 25, 2014
1 parent 70bf50d commit 068aa241ced6539b8fa96802de68fc6dbfade13a
View
@@ -1,15 +1,25 @@
# This Makefile provides an API through which the Chiminey server
# sets-up execution environment, executes domain-specific programs and
# monitor setup and execution progress. Therefore, the contents of the
# Makesfiles should not be changed, else Chiminey will be unable to
# drive the payload.
PAYLOAD_NAME='process_payload'
IDS='proc_ids'
# start execution of the bootstrapping procedure
start_bootstrap:
@echo bootstrap starting
@sh ./start_bootstrap.sh >& bootstrap.output &
# indicate whether bootstrapping procedure is finished
bootstrap_done:
@sh ./bootstrap_done.sh
# start execution of the scheduling procedure
start_schedule:
@sh ./start_schedule.sh $(PAYLOAD_NAME) $(IDS)
# indicate wthether scheduling procedure has finished
schedule_done:
@sh ./schedule_done.sh $(IDS)
@@ -1,6 +1,8 @@
#!/bin/sh
# version 2.0
# indictates whether the bootstrap processes have finished by echoing
# Environment Setup Completed. If not, then process will be rechecked.
# e.g.,
#command -v f95 >/dev/null 2>&1 || { echo >&2 "f95 not installed Aborting."; exit 1; }
echo Environment Setup Completed
@@ -1,13 +1,23 @@
# This Makefile provides an API through which the Chiminey server
# sets-up execution environment, executes domain-specific programs and
# monitor setup and execution progress. Therefore, the contents of the
# Makesfiles should not be changed, else Chiminey will be unable to
# drive the payload.
# start execution of the schedule process
start_process_schedule:
@sh ./start_process_schedule.sh
# indicate whether schedule process is finished.
process_schedule_done:
@sh ./process_schedule_done.sh
# start execution of domain-specific code
start_running_process:
@echo running
@sh ./start_running_process.sh
# indicates whether domain-specific code has finished.
process_running_done:
@echo checking for running
@sh ./process_running_done.sh
@@ -1,3 +1,4 @@
#!/bin/sh
# indicates whether the processes has completed by outputing the string "stopped"
echo stopped
@@ -1,3 +1,5 @@
#!/bin/sh
# indicates whether the configuring and setting up of individual processes
# has finished.
echo Process Setup Completed
@@ -1 +1,3 @@
#!/bin/sh
# contains configurations for configuring and setting up of individual
# processes
@@ -1,4 +1,5 @@
#!/bin/sh
# starts execution of the domain-specific process
#e.g. python -c 'import random; print random.random()' >& output & echo "$!" > "run.pid"
@@ -1,5 +1,7 @@
#!/bin/sh
# Checks that the schedule execution task is complete.
IDS=$1
completed=0
completed_procs=""
@@ -1,4 +1,7 @@
#!/bin/sh
# Starts the processes of making separate execution environments for all
# processes that will run on this VM. Normally, this code should not need to be
# changed.
PAYLOAD_NAME=$1
IDS=$2

0 comments on commit 068aa24

Please sign in to comment.