<div dir="ltr">I vote for <non_descriptive_name_of_function> as a hostname, first of all.<br><br>But to keep with the theme of what we have, I vote for engine01 or manager01 or whatever.<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Apr 3, 2013 at 12:41 AM, Ewoud Kohl van Wijngaarden <span dir="ltr"><<a href="mailto:ewoud+ovirt@kohlvanwijngaarden.nl" target="_blank">ewoud+ovirt@kohlvanwijngaarden.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Mar 25, 2013 at 06:05:07AM -0400, Eyal Edri wrote:<br>
> I'm guessing we'd want to give the instance a proper fqdn -><br>
> "<a href="http://manager01.ovirt.org" target="_blank">manager01.ovirt.org</a>", "<a href="http://engine.ovirt.org" target="_blank">engine.ovirt.org</a>" ?<br>
<br>
</div>I dislike those options. manager01 (to me) implies a cluster where each<br>
managerXX is a node. engine implies there is only one which won't be<br>
true since we'll set up another engine at rackspace. I'd prefer to have<br>
one, but as far as I know this is currently not possible (and maybe due<br>
to latency even a bad idea).<br>
<br>
How about <a href="http://engine.alterway.ovirt.org" target="_blank">engine.alterway.ovirt.org</a>, <a href="http://engine-alterway.ovirt.org" target="_blank">engine-alterway.ovirt.org</a> or<br>
<a href="http://alterway-engine.ovirt.org" target="_blank">alterway-engine.ovirt.org</a>?<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>/Alexander Rydekull
</div>