<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-quoteHeader">
<div><b>From:</b> Andrew Beekhof <a class="moz-txt-link-rfc2396E" href="mailto:andrew@beekhof.net"><andrew@beekhof.net></a></div>
<div><b>Sent:</b> 2014-08-31 23:16:10 EDT </div>
<div><b>To:</b> The Pacemaker cluster resource manager
<a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@oss.clusterlabs.org"><pacemaker@oss.clusterlabs.org></a></div>
<div><b>Subject:</b> Re: [Pacemaker] pacemaker-remote container as
a clone resource</div>
<br>
</div>
<blockquote
cite="mid:08F69422-1185-4590-8861-DD0981C9D084@beekhof.net"
type="cite">
<pre wrap="">
On 1 Sep 2014, at 12:41 pm, Patrick Hemmer <a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@feystorm.net"><pacemaker@feystorm.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">From: Andrew Beekhof <a class="moz-txt-link-rfc2396E" href="mailto:andrew@beekhof.net"><andrew@beekhof.net></a>
Sent: 2014-08-31 19:57:43 EDT
To: The Pacemaker cluster resource manager <a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@oss.clusterlabs.org"><pacemaker@oss.clusterlabs.org></a>
Subject: Re: [Pacemaker] pacemaker-remote container as a clone resource
</pre>
<blockquote type="cite">
<pre wrap="">On 31 Aug 2014, at 6:09 pm, Patrick Hemmer <a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@feystorm.net"><pacemaker@feystorm.net></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm interested in creating a resource that will control host containers running pacemaker-remote. The catch is that I want this resource to be a clone, so that if I want more containers, I simply increase the `clone-max` property.
</pre>
</blockquote>
<pre wrap="">What kind of container?
</pre>
</blockquote>
<pre wrap="">Well I would hope the solution is generic enough to work with any container. But in my specific case, EC2 instances. Plus maybe docker for development work.
</pre>
<blockquote type="cite">
<pre wrap="">Most development was done with VirtualMachine which needs a unique name anyway (ie. cant be cloned).
</pre>
</blockquote>
<pre wrap="">With EC2 (and docker), you create an instance/container and the name & address is returned after creation.
</pre>
</blockquote>
<pre wrap="">
Thats going to be challenging then.
Since there is no way to know which containers are allowed to be attempting a connection or even which ones match up to the implicit connection managers we have started.
</pre>
</blockquote>
That was the reason for my thought about setting an attribute on the
clone child from within the resource agent. The resource agent would
start the container, the container management service would respond
with the address, and the resource agent would call `crm_attribute`
on itself (the clone child) to set the `remote-node` property to the
address of the container (like master/slave resource agents do for
setting scores).<br>
<br>
Though I don't follow on what you mean on "which containers are
allowed to be attempting a connection". The pacemaker-remote
connection is initiated by the host, not the remote. So no container
should be connecting, and the resource agent will instruct the host
who it should be connecting to.<br>
<br>
<blockquote
cite="mid:08F69422-1185-4590-8861-DD0981C9D084@beekhof.net"
type="cite">
<pre wrap="">
I assume all of these containers are doing the same thing?</pre>
</blockquote>
Basically yes. They'll all be capable of running resources as
instructed by pacemaker.<br>
<br>
<blockquote
cite="mid:08F69422-1185-4590-8861-DD0981C9D084@beekhof.net"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Interesting concept though, I'm sure we can figure out some way to get it done.
</pre>
<blockquote type="cite">
<pre wrap="">The problem is that the `remote-node` meta parameter is set on the clone resource, and not the children. So I can't see a way to tell pacemaker the address of all the clone children containers that get created.
The only way I can see something like this being possible is if the resource agent set an attribute on the clone child when the child was started.
Is there any way to accomplish this? Or will I have to create separate resources for every single container? If this isn't possible, would this be considered as a future feature?
Thanks
-Patrick
_______________________________________________
Pacemaker mailing list:
<a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home:
<a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started:
<a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs:
<a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Pacemaker mailing list:
<a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home:
<a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started:
<a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs:
<a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<br>
</body>
</html>