summaryrefslogtreecommitdiff
path: root/doc/automated_spins
diff options
context:
space:
mode:
authorarnaud@30aba4d9f1742050874551d3ddc55ca8694809f82016-03-19 17:52:05 +0000
committeradmin2016-03-19 17:52:05 +0000
commit6789411e43a451aeb2246d4b686a7b37097b95df (patch)
tree6f2792fb7e43416ccdc40d3d4e082f799eb8a74f /doc/automated_spins
parent527e813bea1afb5f3146285c19741583b207b256 (diff)
Added a comment: Spinning hosts in parallel
Diffstat (limited to 'doc/automated_spins')
-rw-r--r--doc/automated_spins/comment_1_1976b145c519b575c1b0454611036055._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/automated_spins/comment_1_1976b145c519b575c1b0454611036055._comment b/doc/automated_spins/comment_1_1976b145c519b575c1b0454611036055._comment
new file mode 100644
index 00000000..24298db9
--- /dev/null
+++ b/doc/automated_spins/comment_1_1976b145c519b575c1b0454611036055._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="arnaud@30aba4d9f1742050874551d3ddc55ca8694809f8"
+ nickname="arnaud"
+ subject="Spinning hosts in parallel"
+ date="2016-03-19T17:52:04Z"
+ content="""
+I just noticed the existence of this conductor property, which seems really interesting. I was trying to understand if and how it would be possible to spinning hosts in parallel. This could be done either as part of a conductor's run, e.g. by traversing the graph in parallel, or from command-line. It seems to me I could use directly `spin` or `spin'` functions to do that from forked threads or processes, with the master process doing the spin commit, but I may be overlooking some potential issues...
+"""]]