[chef-dev] Re: Re: Fwd: How do I know if my application has really been "provisioned"? a suggestion

[Peter Donald < >]

Hi,

We use a couple of strategies to tackle this problem. 

* Firstly we generate our init scripts to block until the service is "up" for some definition of up. Typically this means that the service is listening on all the correct ports on the correct interfaces.

* Secondly we use some outside-in test that will test the service as if it was a client and make sure we get the correct response. i.e. Ensure a HTTP service responds with correct status code when you hit particular URLs.

* Thirdly we monitor some local system to wait for some impact the service has on the machine (i.e. scan logs for keys, look for files created etc).

In most cases we use execute blocks or LWRPs to ensure the service is up which is why ...

On Mon, Dec 10, 2012 at 6:32 AM, Steven Danna < " target="_blank"> > wrote:

I'm wondering if, rather than tying this to the service resource in
particular, a "lock" resource might be more useful.  The API might look
something like:

    lock "wait for foobar" do
      until { some_ruby_code}
      timeout 30 # default to nil to never timeout
    end

    lock "wait for wombats" do
      until "some shell command"
    end

That sounds like a neat idea!

--
Cheers,

Peter Donald