dwradcliffe changed the topic of #rubygems-aws to: RubyGems.org Ops | Log: http://irclog.whitequark.org/rubygems-aws | https://github.com/rubygems/rubygems-aws
<drag00n> interesting concept
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on lb01.staging.rubygems.org (recipe[rubygems]) with: https://gist.github.com/db0886c352fa2ba81cf8
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on repo01.common.rubygems.org (recipe[rubygems]) with: https://gist.github.com/4a0f36b18a31532b90cf
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on repo01.common.rubygems.org (recipe[rubygems]) with: https://gist.github.com/ae63cb6a3552168faaca
rubygems-chef has quit [Client Quit]
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/5c4888f3fb42d74051c2
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on cache01.staging.rubygems.org (recipe[rubygems-cache]) with: https://gist.github.com/a5798baf264f165ac9a5
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on repo01.common.rubygems.org (recipe[rubygems]) with: https://gist.github.com/4e3ab2a46e023b460e0d
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/5e1cf48b357e70bcc30e
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on cache01.staging.rubygems.org (recipe[rubygems-cache]) with: https://gist.github.com/64bf061044e5bd2824b0
rubygems-chef has quit [Client Quit]
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/6001b2ed214e0c23c2aa
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on lb01.staging.rubygems.org (recipe[rubygems]) with: https://gist.github.com/86d31706a7bc1a3f9e76
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on cache01.staging.rubygems.org (recipe[rubygems-cache]) with: https://gist.github.com/d2efb31dac1f162017bd
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/d025b89d3dc57fc2c90c
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on monitoring01.common.rubygems.org (recipe[rubygems-monitoring]) with: https://gist.github.com/a762a5116dbfc469ebc2
rubygems-chef has quit [Client Quit]
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on repo01.common.rubygems.org (recipe[rubygems]) with: https://gist.github.com/08fbbe2ca864d70f7422
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on lb01.staging.rubygems.org (recipe[rubygems]) with: https://gist.github.com/021391b3b08d49bb684c
rubygems-chef has joined #rubygems-aws
rubygems-chef has quit [Client Quit]
<rubygems-chef> Chef failed on cache01.staging.rubygems.org (recipe[rubygems-cache]) with: https://gist.github.com/3e2b82c6f99741c0b5d9
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/da5f66823146a8effd9d
rubygems-chef has quit [Client Quit]
rubygems-chef has joined #rubygems-aws
<rubygems-chef> Chef failed on bastion01.staging.rubygems.org (recipe[rubygems-bastion]) with: https://gist.github.com/ea0e78761cd517afda38
<samkottler> the exception is all fixed now
<samkottler> we've got a sensu node running with all the instances connected up to it
<drag00n> samkottler: Nice!
<drag00n> Is that also hosted on bluebox?