<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Introducing the Scalr Scheduler</title>
	<atom:link href="http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/</link>
	<description>software to auto-scale the world&#039;s websites</description>
	<lastBuildDate>Wed, 01 Feb 2012 23:13:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sebastian</title>
		<link>http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/comment-page-1/#comment-536</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Tue, 24 Aug 2010 05:15:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scalr.net/?p=128#comment-536</guid>
		<description>You simply schedule the job to be executed, and Scalr is in charge of finding an instance to execute the job on. If an instance has been terminated or simply is unresponsive, Scalr will ask another instance of the same Role to run it. Easy!</description>
		<content:encoded><![CDATA[<p>You simply schedule the job to be executed, and Scalr is in charge of finding an instance to execute the job on. If an instance has been terminated or simply is unresponsive, Scalr will ask another instance of the same Role to run it. Easy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joey Novak</title>
		<link>http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/comment-page-1/#comment-531</link>
		<dc:creator>Joey Novak</dc:creator>
		<pubDate>Mon, 23 Aug 2010 16:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scalr.net/?p=128#comment-531</guid>
		<description>What happens if you schedule a recurring job on an instance, and that instance is terminated?</description>
		<content:encoded><![CDATA[<p>What happens if you schedule a recurring job on an instance, and that instance is terminated?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/comment-page-1/#comment-388</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 19 Jul 2010 19:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scalr.net/?p=128#comment-388</guid>
		<description>Yep, this is perfect for this use-case.</description>
		<content:encoded><![CDATA[<p>Yep, this is perfect for this use-case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Traffic Exchange</title>
		<link>http://blog.scalr.net/announcements/introducing-the-scalr-scheduler/comment-page-1/#comment-385</link>
		<dc:creator>Blog Traffic Exchange</dc:creator>
		<pubDate>Mon, 03 May 2010 13:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scalr.net/?p=128#comment-385</guid>
		<description>How about adding the ability to run on just one instance of a certain role?
And in the mysql role be able to run just against the master.

I have a cron setup on the master that this would be very useful for in terms of not having to remember to reset the cron is the master db goes down and a slaves is promoted.</description>
		<content:encoded><![CDATA[<p>How about adding the ability to run on just one instance of a certain role?<br />
And in the mysql role be able to run just against the master.</p>
<p>I have a cron setup on the master that this would be very useful for in terms of not having to remember to reset the cron is the master db goes down and a slaves is promoted.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

