Merge branch 'master' into typed-os-requirements

4 files changed, 51 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...
+"""]]
diff --git a/doc/automated_spins/comment_2_d0b3cfce5e37727f5b17c14d0f4214d2._comment b/doc/automated_spins/comment_2_d0b3cfce5e37727f5b17c14d0f4214d2._comment
new file mode 100644
index 00000000..c95ae691
--- /dev/null
+++ b/doc/automated_spins/comment_2_d0b3cfce5e37727f5b17c14d0f4214d2._comment
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2016-03-19T18:49:26Z"
+ content="""
+Yes, that was the main reason to add
+[Propellor.Property.Concurrent](http://hackage.haskell.org/package/propellor-2.16.0/docs/Propellor-Property-Concurrent.html)
+
+It should be able to parallelize any properties using the combinators in
+there. Including `Propellor.Property.Conductor.conducts`
+
+For example:
+
+	conducts hostfoo `concurrently` conducts hostbar `concurrently` conducts hostbaz
+
+Or, something like this to conduct a whole list of hosts in parallel
+(have not tried to compile it, may need minor tweaking):
+
+	concurrentList (pure 10) "conduct web servers in parallel" $
+		PropList $ map toProp $ conduct webservers
+
+	webservers :: [Host]
+
+Note that concurrent output will be serialized, so you'll probably see propellor
+running live on the first host and then the ones that were conducted in the
+background will have their output dumped the console later on.
+"""]]
diff --git a/doc/automated_spins/comment_3_31fee6824f4f22f8f4fc8e77bf8f8d69._comment b/doc/automated_spins/comment_3_31fee6824f4f22f8f4fc8e77bf8f8d69._comment
new file mode 100644
index 00000000..dd2e0986
--- /dev/null
+++ b/doc/automated_spins/comment_3_31fee6824f4f22f8f4fc8e77bf8f8d69._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="arnaud@30aba4d9f1742050874551d3ddc55ca8694809f8"
+ nickname="arnaud"
+ subject="comment 3"
+ date="2016-03-19T22:10:42Z"
+ content="""
+Nice! Need to revisit latest changes to propellor as I may be missing some really cool stuff...
+"""]]
diff --git a/doc/automated_spins/comment_4_0e6a73215c72286ef0053b5d762537ab._comment b/doc/automated_spins/comment_4_0e6a73215c72286ef0053b5d762537ab._comment
new file mode 100644
index 00000000..1a031e9c
--- /dev/null
+++ b/doc/automated_spins/comment_4_0e6a73215c72286ef0053b5d762537ab._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="arnaud@30aba4d9f1742050874551d3ddc55ca8694809f8"
+ nickname="arnaud"
+ subject="comment 4"
+ date="2016-03-20T11:03:01Z"
+ content="""
+Is there a straightforward way to do that from command-line?
+"""]]