<?xml version="1.0" encoding="UTF-8"?>
<wiki>
  <body>&lt;p&gt;PoolParty has baked in verification for your clouds. This way, you can test if your cloud deployment is working from within the same method used to start the clouds.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;
cloud :app_server do
  verify do
    ping 80
  end
end
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will ping the remote host after everything else in your clouds.rb has run  (ToDo:  everything for one node or after everything for all nodes?) . If it fails, it will try to reconfigure (ToDo:  what specifically is reconfigured or re-tried?) . If the reconfiguration fails again, something is probably wrong your clouds.rb recipe.&lt;/p&gt;
&lt;p&gt;Currently, ping is the only verification baked in to PoolParty.&lt;/p&gt;
&lt;p&gt;(ToDo:  ping uses &lt;span class=&quot;caps&quot;&gt;ICMP&lt;/span&gt; so it has no port; why does the above code have &amp;#8220;ping 80&amp;#8221;?)&lt;/p&gt;
&lt;p&gt;(ToDo:  if, in code above, &lt;code&gt;:app_server&lt;/code&gt; implies more than one machine, they are all pinged; good to emphasize; and what amount of delay is used to give a machine time to come up?   after how long is the instance abandoned )&lt;/p&gt;
&lt;p&gt;(ToDo:  what about periodic verification for later repair?  Should that be distinct from startup verification?)&lt;/p&gt;</body>
  <created-at type="datetime">2009-11-21T21:25:51-08:00</created-at>
  <id type="integer">199013</id>
  <permalink>verification</permalink>
  <repository-id type="integer">29471</repository-id>
  <title>Verification</title>
  <updated-at type="datetime">2009-08-26T18:06:53-07:00</updated-at>
  <user-id type="integer">119855</user-id>
</wiki>
