<div dir="ltr">The nice thing about the RPM is that it sets your systemd automatically. The container can be used to access SSH, that should still work.<div><br></div><div>But either way works.</div><div><br></div><div>- Luis<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 31, 2017 at 12:19 PM, Raghavendra Talur <span dir="ltr"><<a href="mailto:rtalur@redhat.com" target="_blank">rtalur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, May 26, 2017 at 2:32 AM, Luis Pabon <<a href="mailto:lpabon@chrysalix.org">lpabon@chrysalix.org</a>> wrote:<br>
</span><span class="">> What do you guys feel about just not having an RPM anymore, instead always<br>
> use the container to run it? You can even document how to start the<br>
> container on startup. Here would be an example using docker:<br>
> <a href="https://docs.docker.com/engine/admin/host_integration/" rel="noreferrer" target="_blank">https://docs.docker.com/<wbr>engine/admin/host_integration/</a><br>
<br>
</span>Well, need not even be a container. The awesomeness of golang is that<br>
it is a single binary.<br>
Is it ok if we ask the users to do a simple wget? All they need is the<br>
binary and json config.<br>
<br>
Sample files for whatever is their init system.<br>
<span class="HOEnZb"><font color="#888888"><br>
Talur<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> - Luis<br>
><br>
> On Thu, May 25, 2017 at 11:08 AM, Jose A. Rivera <<a href="mailto:jarrpa@redhat.com">jarrpa@redhat.com</a>> wrote:<br>
>><br>
>> Hey folks,<br>
>><br>
>> I'm gonna try to spend today working on the long-overdue heketi<br>
>> packaging for Fedora and CentOS. Part of that will involve writing<br>
>> down the entire process, so that I can better remember how to do it<br>
>> and so others can join in as well. :)<br>
>><br>
>> Once I have that documentation down, should we publish it on the wiki?<br>
>> I ask because I haven't seen other projects publicly publish their<br>
>> distro-specific packaging guides, so it seems like it'd be weird to do<br>
>> it ourselves. Would it make sense to maintain some project-internal<br>
>> documentation, and if so where? It seems unfair to just keep it<br>
>> internal to Red Hat.<br>
>><br>
>> Cheers,<br>
>> --Jose<br>
>> ______________________________<wbr>_________________<br>
>> heketi-devel mailing list<br>
>> <a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
>> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> heketi-devel mailing list<br>
> <a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
><br>
______________________________<wbr>_________________<br>
heketi-devel mailing list<br>
<a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
</div></div></blockquote></div><br></div>