On 07/01/2017 06:47 AM, Valentin Vidic wrote: > On Fri, Jun 30, 2017 at 12:46:29PM -0500, Ken Gaillot wrote: >> The challenge is that some properties are docker-specific and other >> container engines will have their own specific properties. >> >> We decided to go with a tag for each supported engine -- so if we add >> support for rkt, we'll add a <rkt> tag with whatever properties it >> needs. Then a <bundle> would need to contain either a <docker> tag or a >> <rkt> tag. >> >> We did consider a generic alternative like: >> >> <container type="docker"> >> <meta_attributes id="docker-meta"> >> <nvpair id="docker-meta-1" name="image" value="pcmk:httpd"/> >> ... >> </meta_attributes> >> ... >> </container> >> >> But it was decided that using engine-specific tags would allow for >> schema enforcement, and would be more readable. >> >> The <network> and <storage> tags were kept under <bundle> because we >> figured those are essential to the concept of a bundle, and any engine >> should support some way of mapping those. > > Thanks for the explanation, it makes sense :) > > Now I have a working rkt resource agent and would like to test it. > Can you share the pcmk:httpd image mentioned in the docker example?
Sure, we have a walk-through on the wiki that I was going to announce after 1.1.17 final is released (hopefully later this week), but now is good, too :-) https://wiki.clusterlabs.org/wiki/Bundle_Walk-Through _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org