On Fri, Dec 12, 2008 at 09:01:21PM -0000, Evan Broder wrote:
> invirt-cluster-config expects $hostname-internal to exist for all of the
> host machines, which XVM accomplishes with an /etc/hosts file. This file
> is not packaged.
>
> We could either treat this as site-local configuration that should be
> handled in an XVM-specific way, or we could argue that the information
> is required by Invirt, so Invirt should generate the /etc/hosts file
> from additional config fields.
I don't think $hostname-internal should be required/assumed by Invirt;
it's just a convention that happens to make sense for us as we're
running on a backend network. Probably the right answer is to add a
field to each host in the config file saying how clustering should
address it, and default to the normal hostname.
On Fri, Dec 12, 2008 at 09:01:21PM -0000, Evan Broder wrote: cluster- config expects $hostname-internal to exist for all of the
> invirt-
> host machines, which XVM accomplishes with an /etc/hosts file. This file
> is not packaged.
>
> We could either treat this as site-local configuration that should be
> handled in an XVM-specific way, or we could argue that the information
> is required by Invirt, so Invirt should generate the /etc/hosts file
> from additional config fields.
I don't think $hostname-internal should be required/assumed by Invirt;
it's just a convention that happens to make sense for us as we're
running on a backend network. Probably the right answer is to add a
field to each host in the config file saying how clustering should
address it, and default to the normal hostname.
Greg