<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 28, 2017 at 7:34 PM, Sven Kieske <span dir="ltr"><<a href="mailto:s.kieske@mittwald.de" target="_blank">s.kieske@mittwald.de</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 28/03/17 17:58, Martin Sivak wrote:<br>
> I actually like the radical option Didi mentioned -> using Ansible for<br>
> the whole deploy flow. A simple host-deploy dir with playbooks (and<br>
> builtin roles) is something most people would understand easily.<br>
><br>
> And it would even remove all the infrastructure burden from us, oVirt<br>
> would not be the host management solution, Ansible would take the role<br>
> and we would just invoke it when deploying a new host much like we do<br>
> with host deploy now (except Ansible manages its own ssh connection<br>
> too).<br>
<br>
</span>+1<br>
<br>
but some drawback (actual ansible user here):<br>
<br>
you in fact need _some_ libs on the managed hosts for certain ansible<br>
features to work (e.g. if you want to respect selinux settings on the<br>
host), so you would also need to provide these or list them as<br>
prerequisites.<br>
<br>
I understand ovirt can't just provide config mgmt solutions for every<br>
tool out there (puppet, chef, ansible, saltstack, etc.).<br>
<br>
the best approach would be, if it is pluggable, like foreman did this<br>
with it's smart proxys and plugins:<br>
<br>
<a href="https://theforeman.org/plugins/" rel="noreferrer" target="_blank">https://theforeman.org/<wbr>plugins/</a></blockquote><div><br></div><div>Ah, that's a different story altogether. </div><div>You can use Forman/Satellite to manage your hosts life-cycle. </div><div>It's a great, quite well integrated solution we are very fond of.</div><div>We support both discovered hosts (from bare-metal) as well as hosts added already to Foreman.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
so you could provide a plugin infrastructure and maybe write the ansible<br>
integration yourself and the community can add their own<br>
plugins like puppet or chef modules at will. If they mature enough<br>
you could even ship those (optional).<br>
<br>
I really think there would be some value in this, because many small<br>
deployments use tools like puppet or ansible, while these do not scale<br>
well for large environments, where you tend to have things like salt or<br>
chef.<br>
<br>
PS: if you want to annoy some users you could even declare a hard<br>
dependency on foreman and use foreman for the host deployment (a tool<br>
that's actually written for exact this scope), others might find this<br>
higher integration nice. I'm not sure if I would like it or not.<br></blockquote><div><br></div><div>I'd be happy to do that in the future. Right now there are some obstacles to doing that.</div><div>Remember that there are huge benefits to using Foreman not just for host life-cycle, but also VM life-cycle.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
</font></span><div class="HOEnZb"><div class="h5">Mit freundlichen Grüßen / Regards<br>
<br>
Sven Kieske<br>
<br>
Systemadministrator<br>
Mittwald CM Service GmbH & Co. KG<br>
Königsberger Straße 6<br>
32339 Espelkamp<br>
T: <a href="tel:%2B495772%20293100" value="+495772293100">+495772 293100</a><br>
F: <a href="tel:%2B495772%20293333" value="+495772293333">+495772 293333</a><br>
<a href="https://www.mittwald.de" rel="noreferrer" target="_blank">https://www.mittwald.de</a><br>
Geschäftsführer: Robert Meyer<br>
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen<br>
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen<br>
<br>
</div></div><br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div></div>