<?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"
	>
<channel>
	<title>Comments on: Xen and Heartbeat</title>
	<atom:link href="http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/</link>
	<description>Linux, politics, and other interesting things</description>
	<pubDate>Sun, 07 Sep 2008 15:57:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Amos Shapira</title>
		<link>http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/#comment-11041</link>
		<dc:creator>Amos Shapira</dc:creator>
		<pubDate>Mon, 26 Nov 2007 22:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/#comment-11041</guid>
		<description>1. I heard about people running entire Xen clusters on single physical servers with, e.g., a firewall on one guest, a mail server on another, a web server on yet another etc.

2. You can communicate with xend over a socket. See "xend-http-server" in xend-config.sxp(5).

3. To create a limited access to ssh I'd suggest considering use of special ssh private/public keys (without a pass-phrase) and a command="" parameter in authorized_keys. That way only the holder of the private key can invoke the command and the server can limit the command to be invoked by that key (look for "AUTHORIZED_KEYS" in sshd(8)).

About (2) - you can't pass arguments to the command but I'm pretty confident it is allowed to read from standard input. Otherwise you can create different key-pairs for different commands if you have to.

--Amos</description>
		<content:encoded><![CDATA[<p>1. I heard about people running entire Xen clusters on single physical servers with, e.g., a firewall on one guest, a mail server on another, a web server on yet another etc.</p>
<p>2. You can communicate with xend over a socket. See &#8220;xend-http-server&#8221; in xend-config.sxp(5).</p>
<p>3. To create a limited access to ssh I&#8217;d suggest considering use of special ssh private/public keys (without a pass-phrase) and a command=&#8221;" parameter in authorized_keys. That way only the holder of the private key can invoke the command and the server can limit the command to be invoked by that key (look for &#8220;AUTHORIZED_KEYS&#8221; in sshd(8)).</p>
<p>About (2) - you can&#8217;t pass arguments to the command but I&#8217;m pretty confident it is allowed to read from standard input. Otherwise you can create different key-pairs for different commands if you have to.</p>
<p>&#8211;Amos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sadegh</title>
		<link>http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/#comment-10579</link>
		<dc:creator>sadegh</dc:creator>
		<pubDate>Wed, 14 Nov 2007 13:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/06/24/xen-and-heartbeat/#comment-10579</guid>
		<description>Hi,
very good.
my question is if we have only one domu on each machine
(VMM) and our mechanism for failover is Migration how about Changes on Heartbeat and Xen?

Thank you.
Sadegh</description>
		<content:encoded><![CDATA[<p>Hi,<br />
very good.<br />
my question is if we have only one domu on each machine<br />
(VMM) and our mechanism for failover is Migration how about Changes on Heartbeat and Xen?</p>
<p>Thank you.<br />
Sadegh</p>
]]></content:encoded>
	</item>
</channel>
</rss>
