maas-devel team mailing list archive

[Andres Rodriguez <andres.rodriguez@xxxxxxxxxxxxx>]

I don't have any strong opinions on what the possible fix might be, but I'm
wondering if an appropriate fix for this should better be made on the
actual postgresql charm? I mean, we have other services that do not have
these type of issues, so it seems to me that the appropriate place to have
a fix for this, is on the charm side.

Thoughts?


On Wed, Feb 5, 2014 at 10:42 AM, Raphaël Badin
<raphael.badin@xxxxxxxxxxxxx>wrote:

> Why do we have custom hostnames? They're pretty, but we're ought to be
>> thinking big, and nobody is going to try and give meaningful names for
>> 1000+ nodes.
>>
>> If folk want pretty names for specific nodes, let that happen either
>> outside of MAAS, or let us to have a separate feature in MAAS for
>> assigning a pretty alias to a node.
>>
>
> I agree, but we already have support for custom hostnames for historical
> reasons so let's keep it.  Apart from that I agree with you and that's why
> I suggest we make the generated hostname the default hostname handed out to
> clients.
>
>
>
> --
> Mailing list: https://launchpad.net/~maas-devel
> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maas-devel
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Andres Rodriguez
Engineering Manager, HWE Team
Canonical USA, Inc.